16:01:14 <noonedeadpunk> #startmeeting openstack_ansible_meeting
16:01:15 <openstack> Meeting started Tue Apr  7 16:01:14 2020 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:16 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:18 <openstack> The meeting name has been set to 'openstack_ansible_meeting'
16:01:25 <noonedeadpunk> #topic office hours
16:01:59 <noonedeadpunk> Ok, so the first thing I'd lova to raise is reitrement of our roles
16:02:14 <noonedeadpunk> specifically repo_build and pip_install
16:02:35 <noonedeadpunk> So patches for them are ready for review https://review.opendev.org/#/c/716389/ https://review.opendev.org/#/c/717717/
16:03:46 <noonedeadpunk> the second thing is release highlights.
16:03:58 <noonedeadpunk> We should place them by thursday I guess
16:04:12 <noonedeadpunk> However I'm still not sure what we can write down into them
16:04:29 <noonedeadpunk> mnaser: maybe you have some ideas regarding that?
16:04:58 <mnaser> noonedeadpunk: i don't know if something sticks to me right now :X
16:05:39 <noonedeadpunk> yeah, the same thing... I guess we just tried to maintain things mostly
16:05:51 <noonedeadpunk> We can kinda... announce centos8 support....
16:05:52 <mnaser> i would have loved to put centos 8 on that but..
16:05:58 <noonedeadpunk> yeah lol
16:06:08 <mnaser> but i dont know in terms of resource and time how much we can do :X
16:08:14 <noonedeadpunk> py3 support is release goal so we can't place that I think
16:10:56 <jrosser> o/ hello
16:13:57 <noonedeadpunk> so, should be jsut skipp filling in highlights?
16:16:41 <noonedeadpunk> * should we just skip
16:17:36 <noonedeadpunk> Also I think we should bump ansible version to 2.9 for ansible and mariadb to 10.4.
16:17:58 <jrosser> ansible 2.9 looks do-able with the collection for rabbitmq
16:17:58 <noonedeadpunk> For ansible it may cost us first collection usage
16:18:11 <noonedeadpunk> yeah
16:18:16 <jrosser> perhaps we need ansible-collection-requirements file
16:18:37 <noonedeadpunk> actual mitogen usage might be smth to write down to highlights if we could merge that for U
16:18:50 <jrosser> becasue there is a new format for galaxy that splits it into roles and collections in the same file
16:18:55 <jrosser> yes i work all day today on mitogen
16:19:03 <noonedeadpunk> oh, cool
16:19:11 <jrosser> trying to reproduce what the gate fails on
16:19:57 <jrosser> i think we should make a choice on how we are going to list collection requirements
16:20:01 <jrosser> and where to install them
16:20:29 <noonedeadpunk> also this will obviously requie modification of our bump tooling but that's fine
16:20:51 <jrosser> https://docs.ansible.com/ansible/latest/user_guide/collections_using.html#install-multiple-collections-with-a-requirements-file
16:21:05 <jrosser> choice is if we keep the roles and collections in the same file, or not
16:21:18 <jrosser> particularly as we don't actually use galaxy at all to clone roles
16:22:05 <jrosser> so for things to finish, we should certainly try for ansible 2.9
16:22:27 <jrosser> mariadb 10.4 will be trickier becasue i think there is changed stuff beyond just bumping the package version
16:22:46 <jrosser> we ought to be able to land mitogen even if it's opt-in
16:22:54 <jrosser> and zun feels very close too
16:27:58 <jrosser> noonedeadpunk: actually ansible 2.9 is important as that then leads to ceph-ansible 5.0 which in turn now ceph octopus is released
16:28:42 <noonedeadpunk> Yes, ansible is pretty important.
16:28:56 <noonedeadpunk> So as we don't use galaxy I think it's probably should be another file?
16:29:28 <noonedeadpunk> Actually I'd love to use the same but not sure we can fit this format at the moment
16:29:46 <noonedeadpunk> so probably we should start from another one and then think about mergning them...
16:30:14 <jrosser> i would be happy to start with a second file that just lists collections
16:30:21 <jrosser> and use the galaxy cli to install them
16:30:32 <noonedeadpunk> ++
16:30:32 <jrosser> we can always change that all later if needed
16:31:26 <noonedeadpunk> maybe we'll decide to publish our roles one day....
16:32:17 <jamesdenton_wfh> o/
16:32:32 <jrosser> i think that the tricker bit is dealing with this in openstack-ansible-tests
16:33:19 <jrosser> the first place we need to do this is in the rabbitmq role which uses the tests repo for functional tests
16:33:37 <jrosser> and we would have to land a change there to use the collection first
16:36:35 <noonedeadpunk> yeah, which would be kinda different from what we have in openstack-ansible
16:37:14 <noonedeadpunk> or we can copy there boostrap-ansible script for ansible isntallation inside functional tests
16:38:00 <noonedeadpunk> which is probably pretty simmilar to https://opendev.org/openstack/openstack-ansible-tests/src/branch/master/test-ansible-env-prep.sh
16:38:20 <jrosser> perhaps the simplest thing is to just install all the needed at some early point in openstack-ansible-tests
16:38:38 <jrosser> not try to involve the specific roles in that
16:38:49 <jrosser> *needed collections
16:38:55 <noonedeadpunk> yeah, while isntalling ansible
16:39:30 <jrosser> ah grr i wish i knew how to make this mitogen job fail
16:40:27 <noonedeadpunk> maybe build image with dib?
16:40:42 <noonedeadpunk> in case it's smth specific for ci....
16:40:58 <jrosser> maybe its becasue i run the steps manually and not with gate-check-commit......
16:41:10 <noonedeadpunk> hm, might be...
16:41:28 <noonedeadpunk> but... like it runs one by one... except having some extra env set?
16:41:48 <jrosser> it's all under the same shell i guess from the script
16:42:09 <jrosser> i have to go afk now - will carry this on tomorrow
16:43:52 <noonedeadpunk> yeah sure
16:59:37 <noonedeadpunk> #endmeeting