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-common/tasks/installs/debian_community_repository...

21 lines
674 B
YAML
Raw Normal View History

common: refactor installation method The installation process is now described as follow: * you still have to choose a 'ceph_origin' installation method. The origin can be a 'repository' (add a new repository), distro (it will use the packages provided by the native repo source of your distribution), local (only available on redhat system, it installs locally built packages). This option is not well tested, so use it carefully * if ceph_origin == 'repository' you will have to decide what kind of repository you want to enable: - community: corresponds to the stable upstream/community version - enterprise: corresponds to the stable enterprise/downstream version (basically you are a red hat customer) - dev: it will install ceph from packages built out of the github development branches Signed-off-by: Sébastien Han <seb@redhat.com> Co-Authored-by: Guillaume Abrioux <gabrioux@redhat.com> Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-08-03 21:30:25 +08:00
---
common: install dependencies for apt modules When using a minimal Debian/Ubuntu distribution there's no ca-certificates and gpg packages installed so the apt modules will fail: Failed to find required executable gpg in paths: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin apt.cache.FetchFailedException: W:https://download.ceph.com/debian-luminous/dists/bionic/InRelease: No system certificates available. Try installing ca-certificates. Resolves: #3994 Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
2019-05-17 22:31:46 +08:00
- name: install dependencies for apt modules
package:
common: use gnupg instead of gpg gpg package isn't available for all Debian/Ubuntu distribution but gnupg is. Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
2019-05-21 21:21:16 +08:00
name: ['apt-transport-https', 'ca-certificates', 'gnupg', 'software-properties-common']
common: install dependencies for apt modules When using a minimal Debian/Ubuntu distribution there's no ca-certificates and gpg packages installed so the apt modules will fail: Failed to find required executable gpg in paths: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin apt.cache.FetchFailedException: W:https://download.ceph.com/debian-luminous/dists/bionic/InRelease: No system certificates available. Try installing ca-certificates. Resolves: #3994 Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
2019-05-17 22:31:46 +08:00
update_cache: yes
register: result
until: result is succeeded
common: refactor installation method The installation process is now described as follow: * you still have to choose a 'ceph_origin' installation method. The origin can be a 'repository' (add a new repository), distro (it will use the packages provided by the native repo source of your distribution), local (only available on redhat system, it installs locally built packages). This option is not well tested, so use it carefully * if ceph_origin == 'repository' you will have to decide what kind of repository you want to enable: - community: corresponds to the stable upstream/community version - enterprise: corresponds to the stable enterprise/downstream version (basically you are a red hat customer) - dev: it will install ceph from packages built out of the github development branches Signed-off-by: Sébastien Han <seb@redhat.com> Co-Authored-by: Guillaume Abrioux <gabrioux@redhat.com> Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-08-03 21:30:25 +08:00
- name: configure debian ceph community repository stable key
apt_key:
data: "{{ lookup('file', role_path+'/files/cephstable.asc') }}"
state: present
lint: Remote package tasks should have a retry Make linter happy and add more robustness to remote tasks by retrying 3 times (the default) before failing. Signed-off-by: Sébastien Han <seb@redhat.com>
2018-12-20 17:00:26 +08:00
register: result
until: result is succeeded
common: refactor installation method The installation process is now described as follow: * you still have to choose a 'ceph_origin' installation method. The origin can be a 'repository' (add a new repository), distro (it will use the packages provided by the native repo source of your distribution), local (only available on redhat system, it installs locally built packages). This option is not well tested, so use it carefully * if ceph_origin == 'repository' you will have to decide what kind of repository you want to enable: - community: corresponds to the stable upstream/community version - enterprise: corresponds to the stable enterprise/downstream version (basically you are a red hat customer) - dev: it will install ceph from packages built out of the github development branches Signed-off-by: Sébastien Han <seb@redhat.com> Co-Authored-by: Guillaume Abrioux <gabrioux@redhat.com> Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-08-03 21:30:25 +08:00
- name: configure debian ceph stable community repository
apt_repository:
Use ansible_facts It has come to our attention that using ansible_* vars that are populated with INJECT_FACTS_AS_VARS=True is not very performant. In order to be able to support setting that to off, we need to update the references to use ansible_facts[<thing>] instead of ansible_<thing>. Related: ansible#73654 Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1935406 Signed-off-by: Alex Schultz <aschultz@redhat.com>
2021-03-03 22:43:50 +08:00
repo: "deb {{ ceph_stable_repo }} {{ ceph_stable_distro_source | default(ansible_facts['distribution_release']) }} main"
common: refactor installation method The installation process is now described as follow: * you still have to choose a 'ceph_origin' installation method. The origin can be a 'repository' (add a new repository), distro (it will use the packages provided by the native repo source of your distribution), local (only available on redhat system, it installs locally built packages). This option is not well tested, so use it carefully * if ceph_origin == 'repository' you will have to decide what kind of repository you want to enable: - community: corresponds to the stable upstream/community version - enterprise: corresponds to the stable enterprise/downstream version (basically you are a red hat customer) - dev: it will install ceph from packages built out of the github development branches Signed-off-by: Sébastien Han <seb@redhat.com> Co-Authored-by: Guillaume Abrioux <gabrioux@redhat.com> Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
2017-08-03 21:30:25 +08:00
state: present
ceph-common: update_cache whenever a new deb repo is added The use of a handler meant that the cache would be updated at the very end of the play, which doesn't work when adding a development repo and trying to install right after it. This mostly reverts 53cdddf88699263763b36643565e5f846d9d13a8 without an actual `git revert` because that caused other conflicts. Signed-off-by: Alfredo Deza <adeza@redhat.com>
2018-11-02 02:48:06 +08:00
update_cache: yes