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_dev_repository.yml

13 lines
497 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
---
- name: fetch ceph debian development repository
uri:
common,iscsi: don't use the shaman search endpoint In commits 39649f0 and bf8cdad we switch from using the shaman /repos endpoint to the /search endpoint for using the architecture filter. In fact that filter is also available with the /repos endpoint, which requires less ansible tasks. This also adds back a condition remove in 5801171 on the ceph-iscsi repository and that repository doesn't need to filter on the architecture because the ceph-iscsi project is noarch. Both ceph-iscsi and tcmu-runner shaman URLs were using the ceph_dev_branch and ceph_dev_sha1 variables which doesn't make sense. Those variables are only useful for the ceph core repository. Signed-off-by: Dimitri Savineau <dsavinea@redhat.com>
2021-03-27 03:14:15 +08:00
url: "https://shaman.ceph.com/api/repos/ceph/{{ ceph_dev_branch }}/{{ ceph_dev_sha1 }}/{{ ansible_facts['distribution'] | lower }}/{{ ansible_facts['distribution_release'] }}/repo?arch={{ ansible_facts['architecture'] }}"
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
return_content: yes
register: ceph_dev_deb_repo
- name: configure ceph debian development repository
apt_repository:
repo: "{{ ceph_dev_deb_repo.content }}"
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