ceph
/
ceph-ansible
mirror of https://github.com/ceph/ceph-ansible.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
ceph-ansible/roles/ceph-docker-common/tasks/fetch_image.yml

27 lines
1.4 KiB
YAML
Raw Normal View History

Allow running on local dev docker images Docker makes it difficult to use images that are not on signed registries. This is a problem for developers, who likely won't have access to a registry with proper signed certificates. This allows the ability to use any docker image on the machine running vagrant/ansible. The way it works is that the image in question is exported locally, then sent to each target box and imported there. Signed-off-by: Daniel Gryniewicz <dang@redhat.com>
2016-03-24 21:21:07 +08:00
---
# Normal case - pull image from registry
docker: use a better method to pull images We changed the way we declare image. Prior to this patch we must have a "user/image:tag" format, which is incompatible with non docker-hub registry where you usually don't have a "user". On the docker hub a "user" is also identified as a namespace, so for Ceph the user was "ceph". Variables have been simplified with only: * ceph_docker_image * ceph_docker_image_tag 1. For docker hub images: ceph_docker_name: "ceph/daemon" will give you the 'daemon' image of the 'ceph' user. 2. For non docker hub images: ceph_docker_name: "daemon" will simply give you the "daemon" image. Infrastructure playbooks have been modified as well. The file group_vars/all.docker.yml.sample has been removed as well. It is hard to maintain since we have to generate it manually. If you want to configure specific variables for a specific daemon simply edit group_vars/$DAEMON.yml Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1420207 Signed-off-by: Sébastien Han <seb@redhat.com>
2017-02-09 22:16:39 +08:00
- name: "pull {{ ceph_docker_image }} image"
command: "docker pull {{ ceph_docker_registry}}/{{ ceph_docker_image }}:{{ ceph_docker_image_tag }}"
Allow running on local dev docker images Docker makes it difficult to use images that are not on signed registries. This is a problem for developers, who likely won't have access to a registry with proper signed certificates. This allows the ability to use any docker image on the machine running vagrant/ansible. The way it works is that the image in question is exported locally, then sent to each target box and imported there. Signed-off-by: Daniel Gryniewicz <dang@redhat.com>
2016-03-24 21:21:07 +08:00
changed_when: false
when: ceph_docker_dev_image is undefined or not ceph_docker_dev_image
# Dev case - export local dev image and send it across
- name: export local ceph dev image
Support for docker image tags Signed-off-by: Ivan Font <ivan.font@redhat.com>
2016-07-09 09:38:13 +08:00
local_action: command docker save -o "/tmp/{{ ceph_docker_username }}-{{ ceph_docker_imagename }}-{{ ceph_docker_image_tag }}.tar" "{{ ceph_docker_username }}/{{ ceph_docker_imagename }}:{{ ceph_docker_image_tag }}"
Allow running on local dev docker images Docker makes it difficult to use images that are not on signed registries. This is a problem for developers, who likely won't have access to a registry with proper signed certificates. This allows the ability to use any docker image on the machine running vagrant/ansible. The way it works is that the image in question is exported locally, then sent to each target box and imported there. Signed-off-by: Daniel Gryniewicz <dang@redhat.com>
2016-03-24 21:21:07 +08:00
when: ceph_docker_dev_image is defined and ceph_docker_dev_image
run_once: true
- name: copy ceph dev image file
copy:
Support for docker image tags Signed-off-by: Ivan Font <ivan.font@redhat.com>
2016-07-09 09:38:13 +08:00
src: "/tmp/{{ ceph_docker_username }}-{{ ceph_docker_imagename }}-{{ ceph_docker_image_tag }}.tar"
dest: "/tmp/{{ ceph_docker_username }}-{{ ceph_docker_imagename }}-{{ ceph_docker_image_tag }}.tar"
Allow running on local dev docker images Docker makes it difficult to use images that are not on signed registries. This is a problem for developers, who likely won't have access to a registry with proper signed certificates. This allows the ability to use any docker image on the machine running vagrant/ansible. The way it works is that the image in question is exported locally, then sent to each target box and imported there. Signed-off-by: Daniel Gryniewicz <dang@redhat.com>
2016-03-24 21:21:07 +08:00
when: ceph_docker_dev_image is defined and ceph_docker_dev_image
- name: load ceph dev image
Support for docker image tags Signed-off-by: Ivan Font <ivan.font@redhat.com>
2016-07-09 09:38:13 +08:00
command: "docker load -i /tmp/{{ ceph_docker_username }}-{{ ceph_docker_imagename }}-{{ ceph_docker_image_tag }}.tar"
Allow running on local dev docker images Docker makes it difficult to use images that are not on signed registries. This is a problem for developers, who likely won't have access to a registry with proper signed certificates. This allows the ability to use any docker image on the machine running vagrant/ansible. The way it works is that the image in question is exported locally, then sent to each target box and imported there. Signed-off-by: Daniel Gryniewicz <dang@redhat.com>
2016-03-24 21:21:07 +08:00
when: ceph_docker_dev_image is defined and ceph_docker_dev_image
- name: remove tmp ceph dev image file
Support for docker image tags Signed-off-by: Ivan Font <ivan.font@redhat.com>
2016-07-09 09:38:13 +08:00
command: "rm /tmp/{{ ceph_docker_username }}-{{ ceph_docker_imagename }}-{{ ceph_docker_image_tag }}.tar"
Allow running on local dev docker images Docker makes it difficult to use images that are not on signed registries. This is a problem for developers, who likely won't have access to a registry with proper signed certificates. This allows the ability to use any docker image on the machine running vagrant/ansible. The way it works is that the image in question is exported locally, then sent to each target box and imported there. Signed-off-by: Daniel Gryniewicz <dang@redhat.com>
2016-03-24 21:21:07 +08:00
when: ceph_docker_dev_image is defined and ceph_docker_dev_image