16:01:43 <noonedeadpunk> #startmeeting openstack_ansible_meeting
16:01:44 <openstack> Meeting started Tue Oct 15 16:01:43 2019 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:45 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:46 <noonedeadpunk> #topic office hours
16:01:47 <openstack> The meeting name has been set to 'openstack_ansible_meeting'
16:03:50 <guilhermesp> o/
16:04:31 <noonedeadpunk> ok, so we have train milestone:) https://opendev.org/openstack/openstack-ansible/src/tag/20.0.0.0b1
16:04:56 <noonedeadpunk> It's a bit old nowadays, but branching is really soon.
16:05:34 <spotz> o/
16:05:45 <noonedeadpunk> Actually we have patch for it https://review.opendev.org/#/c/686573/4 but there are some concerns about it
16:05:46 <guilhermesp> so the next steps is to branch and then we are ok noonedeadpunk ?
16:05:56 <jrosser> o/
16:06:24 <guilhermesp> oh evrardjp_ just gave us an example https://review.opendev.org/#/c/686583/
16:06:41 <noonedeadpunk> Yep, kind of:) IF we can consider as ok state when we're late and not everything planed has been done
16:07:22 <noonedeadpunk> yep, we'll need to place sha from 686573 there
16:07:43 <noonedeadpunk> actually evrardjp_ made everything needed for releasing, yes:)
16:07:57 <guilhermesp> evrardjp_: rocks ! \m/
16:08:29 <spotz> evrardjp_: Is supposed to be on vacation!
16:08:40 <guilhermesp> much deserved I guess
16:10:14 <noonedeadpunk> considering the sad suse part...
16:10:46 <spotz> He's ok I heard
16:11:16 <noonedeadpunk> that's good
16:13:20 <jrosser> i think we are in a much better position to branch with the code as is now vs. 1 week ago
16:13:38 <noonedeadpunk> that's absolutely true
16:13:39 <jrosser> so much has merged, that what is left unmerged for train is small and manageable
16:14:16 <noonedeadpunk> so another concern that mnaser said today, is that I've missed db migration part of the placement
16:14:39 <noonedeadpunk> but it's 1 commit which can be backported I guess
16:16:01 * mnaser is currently fighting fires so apologies
16:17:22 <noonedeadpunk> But tomorrow there's coordinated release
16:17:34 <noonedeadpunk> so I guess we should branch at least
16:17:56 <noonedeadpunk> otherwise we will start using ususri code with train roles
16:19:39 <noonedeadpunk> btw, we need to spread pdf patch across roles. I can handle it I guess
16:30:04 <jrosser> oh and also ansible 2.9 release day should be tomorrow
16:32:50 <noonedeadpunk> jrosser mnaser: so, would we use 2.9 in train?
16:33:03 <noonedeadpunk> I guess no
16:33:06 <jrosser> we have the choice if we want to
16:33:16 <jrosser> the patch is passing with the latest 2.9 rc
16:33:37 <noonedeadpunk> yep, I saw. Just not sure how everything is tested out.
16:33:52 <noonedeadpunk> We were developing for 2.8 anyway
16:34:22 <noonedeadpunk> But I'm not against this either
16:34:55 <jrosser> it's tricky, becasue the lifetime of ansible releases for getting bugfixes merged is much shorter than the lifetime of an openstack release
16:35:09 <jrosser> so being ahead is kinda better than being behind
16:37:14 <jrosser> also we are a cycle-trailing release, so we are only making a release candidate at this point as far as i know
16:37:32 <jrosser> mnaser should probably advise here tbh
16:37:57 <mnaser> cycle-trailing means we can release like up to 2 months after or so
16:38:50 <openstackgerrit> Dmitriy Rabotyagov (noonedeadpunk) proposed openstack/ansible-config_template master: PDF Documentation Build tox target  https://review.opendev.org/688753
16:40:00 <mnaser> so we're really open to do with whatever
16:40:11 <mnaser> if 2.9 works, i dont see why not
16:40:37 <jrosser> yeah, if things that the integrated repo test misses break, they are bugs and we can fix them
16:40:55 <jrosser> i would rather do that than be on an unsupported ansible sooner
16:42:37 <noonedeadpunk> So then let's use 2.9 and branch with it
16:43:03 <jrosser> but anyway, i think this release there is not a massive pile of outstanding stuff like there has been on other releases
16:43:18 <jrosser> so we should be able to get this done quite quickly
16:45:37 <cjloader> quick question, have you tested master on hardware or just aio?
16:49:18 <jrosser> only on AIO personally
16:50:30 <cjloader> because i'm trying hardware and running into issues with ansible_host: undefined, etc
16:50:55 <cjloader> and this is purely master
16:51:05 <cjloader> not my ironic patches
16:51:42 <cjloader> also, looks like bootstrap-host is using 2.7
16:51:50 <cjloader> not 3.x
16:51:53 <cjloader> py
16:52:06 <noonedeadpunk> on centos it's 2.7
16:52:25 <cjloader> no, i'm using ubuntu 18.04
16:52:32 <noonedeadpunk> hm
16:52:52 <jrosser> can you be more precise that bootstrap-host?
16:52:56 <jrosser> *than
16:53:19 <cjloader> i'm thinking we need to verify master works on hardware before relasing imho
16:53:31 <cjloader> releasing**
16:54:43 <jrosser> cjloader: where do you see it using python2.7?
17:05:23 <cjloader> https://github.com/openstack/openstack-ansible/tree/master/tests/roles/bootstrap-host
17:05:57 <cjloader> https://github.com/openstack/openstack-ansible/blob/master/tests/roles/bootstrap-host/vars/debian.yml#L30
17:08:12 <noonedeadpunk> #endmeeting