Standalone Ceph Ansible role repositories have been deleted

[dmsimard]

The OpenStack-Ansible project has been relying on standalone ceph Ansible role repositories for deployments on stable releases of OpenStack (< Queens) while newer releases have been using ceph-ansible exclusively.

See: https://github.com/openstack/openstack-ansible/blob/f4c7cd442cedf723792ec4c01dd64c041129c0f8/ansible-role-requirements.yml#L181-L204

Removing these repositories all of a sudden is impacting CI jobs and deployments.

Is it possible to bring those repositories back while we work out what's the right way forward ? Thanks.

cc @leseb @guits @alfredodeza

[leseb]

Hey @dmsimard,

Sorry about that, a couple of months ago I marked these repos as deprecated in the galaxy. Last day when doing some cleaning on the Ceph org I removed these repositories.

However, everything is still present here: https://galaxy.ansible.com/ceph/ceph_ansible
You still have all the tags with the right content, so we haven't lost anything.

I believe you can recover from there.
Thanks.

[robled]

Is it still possible to install the ceph roles via the ansible-galaxy command? I'm not using mazer since it's tech-preview only at the moment.

[odyssey4me]

@robled I spent some time trying to make it work today, and it doesn't. Even if you provide the git source to ansible-galaxy, it does not just clone the repo - it modifies it, rendering an unusable role folder as a result.

[leseb]

@odyssey4me did you try with mazer?

[robled]

mazer is a no-go for me, due to this:

Mazer is experimental, and currently only available for tech-preview. Use with lots of caution! It is not intended for use in production environments, nor is it currently intended to replace the ansible-galaxy command-line tool.

Restoring ansible-galaxy support would help those who would like to use ceph-ansible in production.

[odyssey4me]

@leseb I did not. We now just git clone down the combined repo and add the path of that clone to the role paths. We've been doing that for newer builds anyway, but the old galaxy roles were still being used for old (stable) environments which had not made the switch.

[seronline]

@odyssey4me Could you please elaborate what repo you are cloning (assume https://github.com/ceph/ceph-ansible) and where you are making changes to the role paths? I'm stuck with deploying OS Ocata at this particular step (other repos have also slightly changed which I managed to fix myself)

[odyssey4me]

@seronline We use a playbook to clone down the ceph-ansible repo as specified in our ansible-role-requirements.yml file and then have the library path, action plugin path, callback plugin path, and role path set appropriately. Each of those can be set via env vars as we do, or in ansible.cfg depending on what you prefer.

[seronline]

@odyssey4me thanks for the quick and detailed response. My fear is though that OS Ansible for Ocata requires cepth version 2.2.9, as configured in my ansible-role-requirements.yml. I created a new ceph-ansible repository on my private git with version 2.2.9 which was obtained via mazer first:

~/$ mazer install ceph.ceph_ansible,2.2.9

The repo can be found here https://github.com/seronline/ceph-ansible

Going to go through the steps described in your comment and will report if it worked. If successful, I'll try to feed this back to the OpenStack Ansible group (given that Ocata is still stable and used by folks out there).

[odyssey4me]

@seronline OSA implemented changes to use the new repo correctly - if you just update your checkout, then you should be able to run a normal minor upgrade procedure for OSA.

[seronline]

@odyssey4me When checking out OSA 15.1.28 this fix does not exist: https://github.com/openstack/openstack-ansible/blob/15.1.28/ansible-role-requirements.yml and the Ocata documentation mentions that this particular release is required for Ocata to run. So cloning the latest and reverting (not upgrading) back to 15.1.28 doesn't quite help. Anyway, I managed to overcome the issue thanks to your help!

[odyssey4me]

@seronline Yes, it won't be in the last release because Ocata is in extended maintenance - meaning that there are no more releases. You'll have to use the SHA or just use the head of the branch. I would recommend that you upgrade to pike ASAP - and, in fact, upgrade through Queens to Rocky too!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.