16:03:21 <mnaser> #startmeeting openstack_ansible_meeting
16:03:21 <openstack> Meeting started Tue Apr  2 16:03:21 2019 UTC and is due to finish in 60 minutes.  The chair is mnaser. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:03:22 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:03:23 <mnaser> o/
16:03:25 <openstack> The meeting name has been set to 'openstack_ansible_meeting'
16:03:32 <guilhermesp> o/
16:03:58 <mnaser> hi all
16:04:12 <noonedeadpunk> o/ - means smth like "I'm here"? :)
16:04:13 <mnaser> https://etherpad.openstack.org/p/osa-train-ptg
16:04:15 <mnaser> reminder as per usual ;)
16:04:35 <chandankumar> \o/
16:06:02 <nicolasbock> o/
16:06:31 <jrosser> o/
16:10:42 <evrardjp> o/
16:11:12 <mnaser> #topic office hours
16:11:25 <mnaser> I mean, yay, we have stein, it's production ready, I trust it
16:11:32 <mnaser> our sjc1 region is running it, openstack CI is using it now :)
16:12:41 <mnaser> so I think we should be able to confidently release on release day
16:15:13 <guilhermesp> that's awesome mnaser !
16:15:16 <evrardjp> thanks for everyone involved
16:15:22 <guilhermesp> nothing better then testing in production
16:16:33 <mnaser> other than that does anyone have any particular things they want to discuss?
16:17:04 <evrardjp> guilhermesp:  :D
16:17:08 <evrardjp> it's called CI/CD
16:17:13 <noonedeadpunk> :D
16:17:25 <evrardjp> mnaser: yes
16:17:41 <evrardjp> I think we should, if possible, timebox the ptg: https://review.openstack.org/#/c/648947/
16:17:43 <evrardjp> woops
16:17:50 <evrardjp> https://etherpad.openstack.org/p/osa-train-ptg
16:18:11 <evrardjp> but there is no urgent need for it, just saying
16:18:24 <mnaser> yes that would be good for us who have to jump around
16:18:38 <evrardjp> next to that, the list of bugs grows. I didn't generate it this week, but it's massive
16:18:52 <guilhermesp> i think now we have just some role to retire too
16:18:54 <evrardjp> so I think it would be nice to cleanup the bugs before release
16:19:01 <guilhermesp> but I think it's not too urgent
16:19:12 <evrardjp> yeah and that take a few cycles
16:19:13 <evrardjp> :P
16:19:39 <mnaser> yeah hmm
16:19:47 <mnaser> wanna build a list anyways so we can see what we're working with?
16:20:03 <evrardjp> guilhermesp: ^ ?
16:20:17 <guilhermesp> the roles to retire are here https://etherpad.openstack.org/p/osa-python-build-simplification
16:20:26 <guilhermesp> but we can make a different etherpad tho
16:21:16 <mnaser> I think non integrated roles should no longer exist with our new CI infra
16:21:24 <mnaser> its either integrated and tested with integrated or its not
16:21:32 <guilhermesp> I agree
16:21:48 <guilhermesp> afaik monasca* are not integrated yet
16:22:23 <guilhermesp> we also have a leftover of the python_venv simplification https://review.openstack.org/#/c/648583/
16:23:07 <guilhermesp> actually, this is use-integrated-repo-for-all-tests topic
16:23:08 <mnaser> yeah I had no idea what to do with trove at that point
16:23:40 <guilhermesp> yes, it is requiring some overrides in role tests, and as we are doing integrated tests
16:23:51 <guilhermesp> I also have no idea how to define those overrides in integrated repo
16:25:41 <mnaser> guilhermesp: we can use the user_variables.aio.j2 or something like that
16:25:44 <mnaser> its in the bootstrap host role
16:26:18 <guilhermesp> huum good call mnaser so I think worth it to take care of this before we release?
16:27:11 <guilhermesp> trove required trove_service_net_setup to true but it's false by default, is that expected to be in defaults?
16:27:27 * guilhermesp asks to trove maintainers :)
16:28:25 <mnaser> yeah im not sure, maybe whoever added that role can bring it up
16:28:50 <guilhermesp> or I can push up a patch and set it to true and then everyone is happy
16:30:33 <mnaser> guilhermesp: if its only for aio it probably doesn't hurt
16:31:25 <guilhermesp> if is only for aio I think just defining to true in user.variables.aio.j2 would be good
16:32:36 <guilhermesp> let me patch it here and add a depends-on
16:35:01 <mnaser> ok great
16:37:28 <mnaser> other that that I think its the quiet after the storm :)
16:41:15 <openstackgerrit> Guilherme  Steinmuller Pimentel proposed openstack/openstack-ansible master: Add trove_service_net_setup to aio deploy  https://review.openstack.org/649397
16:41:17 <guilhermesp> mnaser: ^
16:41:40 <mnaser> guilhermesp: good stuff
16:42:14 <mnaser> im pretty happy, we'll have a good wind-down after rc1
16:42:14 <guilhermesp> now depends-on here and let's see https://review.openstack.org/#/c/648583/
16:42:38 <openstackgerrit> Mohammed Naser proposed openstack/openstack-ansible-os_trove master: Test using integrated build  https://review.openstack.org/648583
16:42:46 <mnaser> maybe we can do rc2 if we land the trove stuff
16:43:18 <guilhermesp> yeah, as is the last thing related integrated tests I believe
16:44:13 <guilhermesp> mnaser: I think you added the wrong link in the depends-on
16:44:28 <mnaser> ah yikes
16:44:29 <mnaser> you're right
16:44:51 <openstackgerrit> Mohammed Naser proposed openstack/openstack-ansible-os_trove master: Test using integrated build  https://review.openstack.org/648583
16:45:23 <guilhermesp> nice, let's sit and watch
16:46:36 <mnaser> other than that I'm very happy and satisfied of our release.  I think the next one will be ever better with some of the role clean up ideas I have
16:47:09 <guilhermesp> I will do my best to be even better
16:47:34 <mnaser> I think decreasing the # of variables
16:47:39 <mnaser> to make it easier to configure
16:47:49 <mnaser> get rid of any `shell` references
16:48:08 <noonedeadpunk> Probably we may improve work with hosts?
16:48:28 <mnaser> and proper ordering: deploy venv, configure db and sync, start services, add in keystone
16:48:39 <mnaser> sometimes the order is wrong and then the logs are spammed with like "Service down"
16:48:41 <mnaser> or something like that
16:48:50 <mnaser> noonedeadpunk: what do you mean about that?
16:49:13 <noonedeadpunk> Like moving from generating it with bash script to generating with ansible template
16:49:19 <noonedeadpunk> or smth like that
16:50:11 <mnaser> yeah
16:51:29 <mnaser> oh you mean the /etc/hosts file
16:51:30 <mnaser> ah yesss
16:51:36 <noonedeadpunk> Yep:)
16:51:45 <mnaser> I think the idea of generating it was because it was some performance thing
16:51:45 <guilhermesp> so those ideas already in etherpad mnaser ?
16:51:52 <mnaser> I put some there yes
16:51:55 <mnaser> noonedeadpunk: maybe you wanna add that one
16:51:56 <guilhermesp> nice
16:52:02 <mnaser> https://etherpad.openstack.org/p/osa-train-ptg
16:52:45 <guilhermesp> so I believe the some of the role retirement are going to be done next cycle... but not sure if is too important to add as a discussion item
16:52:50 <guilhermesp> in etherpad
16:53:21 <noonedeadpunk> mnaser: if it was some previos decision I'm not really aware of (especially in terms of performance), than there's probably no reason for that?
16:53:35 <mnaser> noonedeadpunk: well a lot of the stuff in OSA was to optimize for older releases of ansible
16:53:40 <mnaser> ansible has come a long way and it has a lot of new things now
16:53:52 <mnaser> like for example, action_modules .. we can use one to build the /etc/hosts locally, and then ship it out
16:54:06 <noonedeadpunk> Yeah, for older realeases it even might be even not really possible///
16:54:07 <mnaser> I think logan- knows some of these things
16:54:22 <jrosser> i think we should have a really good bash at getting mitogen to work
16:54:44 <mnaser> jrosser: yes, I added that too
16:54:45 <guilhermesp> mitogen ++
16:54:53 <jrosser> becasue with the best will in the world the amount of work that needs to be done in the tasks is finite and can't be reduced much
16:55:06 <jrosser> but the ansible overhead is another matter
16:55:08 <mnaser> its in the ideas of like eliminating stuff that we're maintaining and deferring to tools that are really good at doing what they do
16:55:28 <mnaser> so why maintain our own ssh connection driver when mitogen can give us what we want for example
16:55:35 <mnaser> in a much more efficient manner too
16:56:00 <jrosser> we need to engage with dw a bit, there are still some things to fix on his side
17:02:36 <mnaser> jrosser: im up for us to start doing that, I think he'll be happy to see an open source consumer
17:02:40 <mnaser> #endmeeting