16:20:59 <noonedeadpunk> #startmeeting openstack_ansible_meeting
16:21:01 <openstack> Meeting started Tue Apr 21 16:20:59 2020 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:21:03 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:21:05 <openstack> The meeting name has been set to 'openstack_ansible_meeting'
16:21:06 <noonedeadpunk> #topic office hours
16:21:51 <noonedeadpunk> jrosser: redrobot sorry for the delay - with this summer time got a bit lost in time
16:22:33 <redrobot> noonedeadpunk, no worries
16:22:46 <noonedeadpunk> so, what do we have except broken tempest thing (again)?
16:23:03 <redrobot> I was hoping mnaser would be here so we can talk about
16:23:05 <redrobot> #link https://review.opendev.org/#/c/721348/
16:23:29 <mnaser> hi redrobot , sorry its exactly at 12pm so i grabbed something quick to eat
16:23:34 * mnaser clicks
16:23:38 <mnaser> oh yes hi
16:24:11 * redrobot waves all around
16:24:14 <mnaser> redrobot: yeah maybe the ansible sig might be a good home for those, it's not that i "Dont want them" but just feel like its not fair for y'all considering we don't really touch/see those roles :)
16:24:28 <redrobot> Hehe, no worries
16:24:42 <redrobot> I _think_ we originally asked y'all because it was all Ansible
16:24:56 <redrobot> but I would not be opposed to moving them all under the Barbican umbrella
16:26:37 <noonedeadpunk> I think those days there was no ansible sig, but now it is. So indeed I agree with evrardjp and mnaser that it's probably better to place these roles under ansible sig ubrella (as it is all about ANsible :))
16:27:27 <noonedeadpunk> as we kinda know ansible but not realy aware of the functional part of these hsm roles
16:28:00 <noonedeadpunk> so really hard to judge on them while voing on patches
16:28:05 <noonedeadpunk> *voting
16:28:14 <redrobot> Ansible SIG != OpenStack Ansible Team?
16:28:53 <redrobot> I think ultimately the Barbican team will need to have core review permissions on these since we have access to the hardware to test them.
16:29:28 <noonedeadpunk> nope. OpenStack-Ansible is project for deploying openstack with ansible :)
16:30:38 <noonedeadpunk> so it's more like deployment tool project along with tripleo, kolla, etc
16:30:44 <redrobot> gotcha
16:30:53 <redrobot> https://wiki.openstack.org/wiki/Ansible_SIG then?
16:31:11 <noonedeadpunk> yeah and #openstack-ansible-sig
16:31:35 <redrobot> cool, I'll talk to them and see if that might be a good home for our *-hsm roles.
16:31:40 <redrobot> thanks! :D
16:31:48 <noonedeadpunk> sure, no problems:)
16:33:51 <noonedeadpunk> ok, what I though about today, if should we offer providing a zookeeper cluster installation as a part of infra role?
16:34:52 <noonedeadpunk> Like some of the projects make use it for coordination (not only telemetry ones) so it might be a nice idea having it.
16:35:40 <noonedeadpunk> Like I know that the roles is already exist, so as for implementation we will just need to add env.d file and sample to documentation
16:36:25 <noonedeadpunk> As a second step we might add defaults to the roles so in case of existing zookepeer projects would use it for coordination by default
17:15:11 <openstackgerrit> Jonathan Rosser proposed openstack/openstack-ansible-os_tempest master: Refactor tempest plugin install from source  https://review.opendev.org/721645
17:15:29 <jrosser> noonedeadpunk: i have massively simplified the tempest source install now
17:15:51 <noonedeadpunk> #endmeeting