16:00:46 <mnaser> #startmeeting openstack_ansible_meeting
16:00:47 <openstack> Meeting started Tue Feb 12 16:00:46 2019 UTC and is due to finish in 60 minutes.  The chair is mnaser. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:48 <mnaser> #topic rollcall
16:00:49 <mnaser> o/
16:00:49 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:50 <guilhermesp> o/
16:00:51 <openstack> The meeting name has been set to 'openstack_ansible_meeting'
16:01:16 <kmadac> @fnpanic: patch basically adds environment variable REQUESTS_CA_BUNDLE to heat systemd service
16:01:45 <jrosser> o/
16:01:45 <evrardjp> p/
16:01:47 <odyssey4me> rpsene something to try - clear out the fact cache, then set the fact gathering subset to 'all', then try again, ie rm -rf /etc/openstack_deploy/ansible_facts; export ANSIBLE_GATHER_SUBSET='all'; ... execute the playbooks ...
16:01:51 <jamesdenton> o/
16:02:08 <spotz> o/
16:02:31 <mnaser> #topic Last week highlights
16:02:40 <mnaser> anyone gots some fun highlights they want to share from last week?
16:02:52 <odyssey4me> FOSDEM was interesting :)
16:03:29 <mnaser> i hear it was a mini ptg :)
16:03:53 <odyssey4me> mnaser haha, not quite - but there was much beer, and evrardjp and I managed to have a short chat about config_template
16:04:00 <prometheanfire> o/
16:04:17 <mnaser> fun times
16:04:28 <odyssey4me> more progress on that in https://review.openstack.org/#/q/topic:bug/1791258 and https://etherpad.openstack.org/p/osa-config-template-migration
16:05:16 <evrardjp> and releases too ! :p
16:05:41 <mnaser> sounds like a fun time
16:05:45 <evrardjp> (I was merely pushing my laziness agenda I guess?)
16:06:27 <mnaser> i support that agenda, hah
16:06:36 <odyssey4me> oh yes, he told me about https://review.openstack.org/#/q/topic:easier_osa_releases which is awesome :)
16:06:49 <mnaser> awesome, we're almost landing that
16:06:51 <fnpanic> https://bugs.launchpad.net/openstack-ansible/+bug/1815631
16:06:52 <openstack> Launchpad bug 1815631 in openstack-ansible "[Docs] all examples lacking correct horizon image upload mode" [Undecided,New]
16:07:04 <odyssey4me> with that merged, we'll never have to update openstack_release, ever again (from stein onwards)
16:07:04 <evrardjp> I will backport those
16:07:12 <mnaser> 🔥
16:07:23 <mnaser> i'm excited :)
16:08:45 <odyssey4me> oh, and we chatted a bit about the python build simplification - I got confirmation from evrardjp that my thinking was right - I'll do some updates to the existing patches on friday and will hopefully be able to spread the pattern across other roles if everyone's happy with them... so we should be able to chat about that next week in more detail
16:09:25 <odyssey4me> with that done, I'll circle back to using the integrated repo for all role tests - I think we should be able to get it done for stein
16:09:49 <mnaser> w00t, odyssey4me please let us know if you need any help with all of this :)
16:10:02 <evrardjp> During that conversation I pointed out the fact that we should branch when we feel this is ready
16:10:19 <odyssey4me> slightly tangential to that, I need another review for https://review.openstack.org/636297 to unblock the os_heat repo's integrated build tests: https://review.openstack.org/636297
16:10:36 <odyssey4me> urgh, sorry - I got a little over excited with copy/paste there
16:11:29 <fnpanic> how can i use the ansible inventory groups in my plays?
16:11:42 <guilhermesp> and this patch unblocked this https://review.openstack.org/#/c/634032/3 odyssey4me :)
16:11:52 <guilhermesp> it is still finishing but I see all green
16:12:19 <odyssey4me> yep, great - thanks guilhermesp
16:12:33 <odyssey4me> fnpanic we can discuss that after the meeting if you don't mind?
16:12:42 <fnpanic> ok sorry
16:12:46 <mnaser> coolio
16:12:54 <mnaser> that's some awesome updates over the weekends :)
16:12:56 <fnpanic> was not awarre thar is it that late
16:13:09 <mnaser> or the week rather ;)
16:13:15 <dmsimard> For the record, I filed a bug for the horizon -> cinder issue I had with my AIO https://bugs.launchpad.net/horizon/+bug/1815635
16:13:16 <openstack> Launchpad bug 1815635 in OpenStack Dashboard (Horizon) "Horizon is unable to retrieve Cinder API versions when it has a self-signed SSL certificate" [Undecided,New]
16:13:29 <guilhermesp> aaaand some clues about this https://review.openstack.org/#/c/627782/6 the workspace move maybe is not working as expected
16:14:14 <odyssey4me> oh, I see the placement role patch merged - is that all good to go? if so, then part of my work to use the integrated build for role testing will be to work on the upgrade path.... but someone will still need to change the nova role up to use the new placement role
16:14:39 <mnaser> odyssey4me: yes, my next step is doing os_nova to use os_placement
16:14:48 <odyssey4me> thanks dmsimard - we'll move to triage shortly and that'll likely come up
16:15:14 <dmsimard> odyssey4me: I filed the bug in horizon, but it looks like there are improvement opportunities for self-signed certificates in AIO in general
16:15:28 <odyssey4me> mnaser ok cool - just greenfield will be fine, we'll work on the upgrade path later and test it using the integrated build, hopefully in the gate :)
16:15:57 <openstackgerrit> Georgina Shippey proposed openstack/openstack-ansible-os_neutron stable/rocky: Add support for dns_domain_ports api extension  https://review.openstack.org/636368
16:16:24 <dmsimard> apologies, I wasn't aware a meeting was ongoing
16:17:13 <mnaser> we need to have a job that uses in-repo placement in os_nova
16:17:38 <mnaser> and then another one that uses the new os_placement role
16:17:45 <mnaser> (because nova wants to test in-repo placement using our jobs)
16:18:50 <mnaser> but yes indeed odyssey4me we'll figure it out for greenfield and then upgrade will be the tricky one
16:19:46 <mnaser> #topic bug squash day
16:19:53 <odyssey4me> mnaser heh, sounds like a bit of fun then
16:20:35 * mnaser #link https://etherpad.openstack.org/p/osa-bug-squash-q1
16:20:38 <mnaser> #link https://etherpad.openstack.org/p/osa-bug-squash-q1
16:20:45 <odyssey4me> dmsimard most definitely, that's an itch which no-one has really scratched yet unfortunately... although some reasonable work was done in the galera_server/galera_client roles which may be worth looking at
16:21:38 <mnaser> i came up with a little link to share and work on some of our progress
16:21:47 <mnaser> for tomororw hopeuflly
16:22:15 <jamesdenton> right on
16:22:17 <spotz> I'm working weird hours tomorrow but I'll work through the review list when I can for sure
16:23:04 <admin0> is removing old facts,  # in the config and  using inventroy-manage --remove  to delete enough to remove services .. like i want to not use aodh/gnocchi anymore
16:23:07 <mnaser> how does everyone feel about a high bandwidth way of chatting
16:23:19 <mnaser> zoom? hangouts? good o'l conference call? :P
16:23:28 <odyssey4me> I unfortunately won't be able to actively participate in the bug triage, other than to be available to answer questions and advise where I can via IRC.
16:23:40 <guilhermesp> I vote zoom
16:24:37 <odyssey4me> mnaser I would personally prefer IRC, because it's all logged and open - but it may make sense to use vid conf for small groups who're working together...
16:24:57 <mnaser> odyssey4me: yeah im thinking maybe like a subgroup to hack on a specific task if they feel like but *leaving* everything in irc
16:25:05 <odyssey4me> admin0 we can discuss that after the meeting
16:25:40 <admin0> sorry .. did not realized we are in a meeting ( just walked in)
16:25:45 <spotz> mnaser maybe create 2-3 zooms and have links in the ether that folks can check in and out?
16:25:47 <mnaser> and log all that stuff in the etherpad to track our progress
16:26:10 <guilhermesp> yeah I think would be good to divide and conquer in this way...main topics on irc and small groups discussing in a conference, then registering things on etherpad
16:26:11 <mnaser> i'll leave it as on-demand
16:26:15 <mnaser> we can get a good room anytime :)
16:26:28 <odyssey4me> mnaser yep, makes sense - and spotz' suggestion to have a few rooms to use for particular focus groups is a good one, I think.
16:26:32 <mnaser> hangouts or whatever can be really on demand
16:26:39 <mnaser> yeppers
16:26:58 <mnaser> does anyone have any other suggestions for that etherpad?
16:27:05 <mnaser> it's my first time running something like this so all advice is welcome
16:27:26 <spotz> Maybe just a note when something is merged so those of us focusing on reviews don't keep opening things?
16:27:29 <odyssey4me> zoom's a great way to get more eyes on the same console to see the same problem as the person doing the triage/fix
16:28:00 <odyssey4me> spotz I think that's what gerritbot is for. ;)
16:28:28 <spotz> odyssey4me: Bah, you know I tend to squirrel onto things in front of me!:)
16:28:53 <cloudnull> o/
16:29:21 <mnaser> i have fully carved out my day to dedicate for this :)
16:29:42 <mnaser> so it'll be fun except for the fact we can't go out after we're done some good work D:
16:30:01 <cjloader> o/
16:30:01 <evrardjp> I see what you did there
16:31:56 <spotz> Not that you managed to go out with us in Berlin mnaser.....:)
16:32:23 <guilhermesp> hahahah
16:32:26 <spotz> hey cloudnull and cjloader
16:32:28 <odyssey4me> mnaser True. I think I'd like to facilitate a virtual mid-cycle in Train for OSA where we can focus on achieving our goals, so I'm interested to see how this goes. I'm thinking it may also be useful to facilitate a regular bug/review smash for the Ansible OpenStack modules too, given that those reviews and bugs aren't getting enough attention either.
16:32:57 <mnaser> odyssey4me: i agree!  this will be a good attempt at seeing that
16:33:08 <cjloader> +1 odyssey4me
16:33:15 <mnaser> i would love for us to take a day or two to sprint and get all those super awesome things we discucsed at the ptg
16:33:16 <mnaser> we've done great progress
16:34:29 * redrobot sneaks into the meeting
16:34:51 <mnaser> so if anyone is around does anyone have a show of hands of who might be there tomorrow? :)
16:35:02 <jamesdenton> i'll do my best
16:37:07 <jrosser> we will be there
16:37:08 <guilhermesp> mnaser: o/
16:37:27 <spotz> o/ but at weird times
16:37:39 <mnaser> coolio
16:37:50 <mnaser> given we'll be doing a bunch of bug triage tomorrow i'll skip that :)
16:37:53 <mnaser> #topic open discussion
16:38:32 <redrobot> o/
16:38:45 <mnaser> hi redrobot :)
16:38:54 <redrobot> Hi mnaser!
16:39:13 <mnaser> something fun to share for our open discussion ? :P
16:39:15 <redrobot> looks like I snuck in here just in time :D
16:39:20 <redrobot> yes!
16:39:44 <redrobot> So, both HSM ansible roles are part of openstack-ansible now!
16:39:58 <redrobot> 🎉🎉🎉
16:40:09 <redrobot> Thanks to everyone who +1/+2 patches
16:40:23 <redrobot> There's only one outstanding thing in my todo
16:40:48 <redrobot> and that's adding myself and ade_lee (or barbican-core) to the review teams for those two roles
16:41:01 <redrobot> #link https://review.openstack.org/#/admin/groups/2005,members
16:41:10 <odyssey4me> redrobot personally, I'd be happy to see barbican-core in there
16:41:11 <redrobot> #link https://review.openstack.org/#/admin/groups/2005,members
16:41:46 <redrobot> mnaser, I believe you own both groups... so you'd be the one to add new members
16:41:46 <spotz> +1
16:42:16 <odyssey4me> I think we're all sensible enough to review on the basis of the things we understand.
16:42:29 <redrobot> odyssey4me, spotz 😁
16:42:30 <odyssey4me> I'd suggest also adding the openstack-ansible-core group there too.
16:42:38 <evrardjp> indeed
16:43:12 <mnaser> i agree with odyssey4me.
16:43:14 <redrobot> odyssey4me, +1 ... I agree sharing duties between our two teams seems ideal
16:43:23 <mnaser> redrobot: i added barbican-core and osa-core to that group
16:43:37 <evrardjp> good job mnaser
16:43:43 <mnaser> please don't shy from sending reviews as you start
16:43:58 <redrobot> mnaser, how about the other one? 😬
16:44:04 <mnaser> i see the same link twice D:
16:44:08 <redrobot> oh oops
16:44:09 <redrobot> my bad
16:44:21 <redrobot> #link https://review.openstack.org/#/admin/groups/2006,members
16:44:27 <redrobot> ^^ that's the second one
16:44:28 <odyssey4me> redrobot I'm not really all that familiar with the subject matter, so hopefully someone in the community will adopt them for their environment and start working on getting them working with our integrated build - or creating an appropriate user story and some openstack-ansible-ops playbooks to help people understand how to use them.
16:44:32 <spotz> bad redrobot!
16:44:57 <mnaser> voila redrobot :)
16:45:30 <redrobot> odyssey4me, agreed, the challenge there is to have both HSMs readily available for test.  We're working on downstream tests for sure, but I'll try to push for upstream testing as well.
16:46:02 <jamesdenton> I'm soliciting feedback on https://docs.openstack.org/openstack-ansible/latest/user/network-arch/example.html and https://docs.openstack.org/openstack-ansible/latest/user/prod/provnet_groups.html for those interested. Both new docs.
16:46:06 <odyssey4me> redrobot well, if there's some sort of downstream testing via external CI to provide active feedback to changes on the role, that'd be good enough in my books
16:46:11 <redrobot> (additionally, to complicate things some HSM client software may not have open source licenses. 😔
16:46:22 <evrardjp> tbh I am not too familiar with those, but I guess if we are a little trained with them we could review more efficiently. I can only review the ansible bits to see if they match the latest standards
16:46:24 <mnaser> you can still have 3rd party voting
16:46:25 <evrardjp> redrobot: I see
16:46:28 <redrobot> odyssey4me, ack, I will definitely keep that in mind.
16:46:33 <mnaser> s/3rd party voting/3rd party ci/
16:46:39 <redrobot> mnaser, much appreciated! :D
16:47:04 <odyssey4me> ooh jamesdenton you drew purdy pics :)
16:47:15 <redrobot> ok, that's all I have
16:47:39 <jamesdenton> just for you, odyssey4me
16:47:58 <spotz> hehe
16:48:19 <prometheanfire> Adri2000: plan on backporting I2a3e266e3066d6c271a29038e814ff8e3090fafb ? looks like nova has the same change in rocky (and queens, pike)
16:49:22 <mnaser> jamesdenton: i like those docs!
16:49:41 <mnaser> anyone else has any other proposed solutions?
16:49:47 <jamesdenton> thanks!
16:49:50 <odyssey4me> jamesdenton at a cursory glance, that's really nice work - great example configs and all
16:50:27 <odyssey4me> prometheanfire anyone can propose the backport :)
16:50:55 <odyssey4me> mnaser proposed solutions? I'm confused
16:51:04 <cjloader> mnaser: i'll be there tomorrow -- had to check w my manager
16:51:08 <mnaser> `ER
16:51:10 <mnaser> proposed topics
16:51:12 <mnaser> im sorry
16:51:15 <mnaser> :<
16:51:21 <prometheanfire> odyssey4me: there are other issues it looks like, how did both https://github.com/openstack/openstack-ansible-os_nova/commit/f67e610609df9f99778de00630c7e0db9b4295ed and https://github.com/openstack/openstack-ansible-os_nova/commit/a383124336dfc74b4d652be594f7bba0197c24b1 make it in, they both deleted the same section of the template
16:52:48 <odyssey4me> prometheanfire heh, I have no idea
16:53:19 <prometheanfire> ya, need to fix that up too
16:53:22 <odyssey4me> mnaser I have nothing for now.
16:53:41 <mnaser> cool, anyone else? :)
16:53:50 <guilhermesp> mnaser: I just have the upgrade jobs that we need some feedback of tempest guys
16:53:55 <guilhermesp> we already discussed about it too
16:53:56 <prometheanfire> backports would be incomplete so I might make a combined (correct) one.
16:54:35 <guilhermesp> also AFIK https://review.openstack.org/#/c/635579/3 depends on a fix that I don't fully remember now
16:54:39 <odyssey4me> guilhermesp oh, that workspace thing is odd - so running the 'move' command doesn't actually move it? perhaps we should just move it with 'mv' after the 'move' command?
16:54:54 <odyssey4me> prometheanfire yep, sounds good
16:55:10 <guilhermesp> maybe odyssey4me ... what I saw in the hold is that the old workspace is in the same place and the new one is empty
16:55:18 <guilhermesp> it's like nothing was moved, just in the api point of view
16:55:22 <Adri2000> prometheanfire: I think I didn't backport that because it's quite easy to override in the config, but feel free to submit a backport if needed
16:55:48 <guilhermesp> that's why we could be experiencing these nested venv issues when running tempest run -l between the two releases
16:55:52 <odyssey4me> guilhermesp I see other os_nova patches passing CI today - so perhaps that just needs a recheck now
16:56:04 <guilhermesp> odyssey4me: will do that now
16:56:45 <mnaser> shall i end? :>
16:57:29 <guilhermesp> for me it's ok mnaser
16:57:34 <mnaser> coolio
16:57:36 <mnaser> #endmeeting