19:01:13 <clarkb> #startmeeting infra
19:01:14 <openstack> Meeting started Tue Nov  6 19:01:13 2018 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:01:15 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:01:17 <openstack> The meeting name has been set to 'infra'
19:01:24 <clarkb> #link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting
19:01:51 <clarkb> The Summit is next week. This means that many of us will be traveling for that and otherwise distracted for the meeting next week
19:02:12 <clarkb> I'm going to go ahead and cancel the meeting next week
19:02:30 <clarkb> #link https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_aac97f1cbb6c61df&akey=b9e448b340787f0e Vote for OpenStack T release name
19:02:41 <clarkb> you have a day or two remaining to go vote for the openstack T release name if you wish to do so
19:03:18 <clarkb> #topic Announcements
19:03:43 <clarkb> I totally forgot to set the topic for the last bit, /me adds the link again
19:03:50 <clarkb> #link https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_aac97f1cbb6c61df&akey=b9e448b340787f0e Vote for OpenStack T release name
19:04:04 <clarkb> #topic Actions from last meeting
19:04:13 <clarkb> #link http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-10-30-19.01.txt minutes from last meeting
19:04:37 <fungi> next week we might want to mention the openstack mailing list combining since i keep getting questions about the schedule for that
19:05:01 * fungi didn't think to suggest it for announcements until just now
19:05:21 <fungi> oh, wait, next week... is the summit
19:05:24 <clarkb> as far as actiosn go https://etherpad.openstack.org/p/infra-to-opendev-messaging got written and feedback would be nice
19:06:13 <clarkb> I'm still waiting on the doc that lsell is goign to write and have pinged about that
19:06:52 <clarkb> #topic Specs approval
19:06:58 <clarkb> #link https://review.openstack.org/#/c/613753/ Zuul Priority Queues
19:07:07 <clarkb> corvus: ^ I think you added that to the agenda?
19:07:10 <ssbarnea> this is more for consultation
19:07:25 <clarkb> ah was ssbarnea? I didn't check the wiki edit history
19:07:27 <ssbarnea> i added it, but is just a note to look over it and to comment.
19:07:53 <ssbarnea> i would call it: in exploratory phase.
19:08:24 <clarkb> ok so not ready for approval (also zuul priority queus are a different approval body now) but looking for feedback
19:08:25 <ssbarnea> how can we make some changes more important (faster to test) than others.
19:08:57 <clarkb> #link https://review.openstack.org/#/c/607377/ Storyboard attachments
19:09:15 <clarkb> this spec is also not quite ready for review but it has done a round of review and it would be good to get eyeballs on it again
19:10:14 <clarkb> thank you to those of you that have done reviews, they have been helpful on that spec in particular
19:10:35 <clarkb> #topic Priority Efforts
19:10:42 <clarkb> #topic Update Config Management
19:11:02 <clarkb> corvus made progress proving that ansible only (no puppet) config management deployments do work
19:11:13 <clarkb> the new opendev dns servers are running on bionic deployed with ansible alone.
19:11:41 <clarkb> As part of the work done for ^ we updated our group configuration to use mordred's yamlgroup plugin which mostly worked (had to fix groups for the mirrors and logstash and etherpad)
19:12:02 <clarkb> the good news is that ansibel should run almost immediately now and not take several minutes to determine group membership \o/
19:12:13 <clarkb> this also unblocks ianw's work to use docker
19:12:27 <clarkb> ianw: ^ does that set of changes need rereview now that yamlgroup made it in?
19:13:21 <ianw> ummm, not yet; i have to loop back but i think we're in position now where we can get ci runs showing everything working
19:13:36 <corvus> that's awesome -- hopefully we can start running some zuul services from containers soon :)
19:13:58 <fungi> exciting!
19:14:00 <clarkb> yup starting to see some real progress on the theoretical bits of the spec which is exciting
19:14:39 <clarkb> Please do be on the lookout for any other group related mishaps that we missed in the transition
19:14:47 <clarkb> the fixes are typically "easy" update the groups to match what we had before
19:15:30 <clarkb> review on `topic:puppet-4 and topic:update-cfg-mgmt` continue to be much appreciated
19:15:45 <clarkb> Anything else we want to call out related to this effort?
19:15:48 <cmurphy> ++
19:16:01 <cmurphy> i added a few more future parser changes
19:16:22 <cmurphy> and there are still a few test updates and trivial fixes in topic:puppet-4
19:17:29 <cmurphy> nothing else from me
19:17:59 * diablo_rojo sneaks in lae
19:18:11 <diablo_rojo> and unable to spell
19:18:15 <clarkb> diablo_rojo: just in time :) storyboard is next if there is nothing else related to ansible docker and puppet
19:18:30 <clarkb> #topic Storyboard
19:18:35 <fungi> storyboard could also be related to ansible docker and puppet
19:18:49 <clarkb> I noted that there is a new version of the attachments spec earlier. Please do review that spec
19:18:53 <fungi> oh, on the last topic i was going to mention that mordred is investigating using podman instead of docker
19:19:15 <diablo_rojo> Yup that was all I really had atm- new patchset.
19:19:21 <clarkb> I think thats a fine thing to investigate but tripleo's use of it indicates to me its super pre alpha softawre
19:19:34 <clarkb> (it doesn't work)
19:19:49 <clarkb> diablo_rojo: have you had time to look at the neutron migration issues?
19:20:13 <clarkb> and is there anything the infra team should be doing to help wit hthat? you have access to all of the dev server logs iirc
19:20:51 <fungi> well, it wouldn't be logged there anyway. the migration script ends abruptly so we'd need it to provide more info on its stdout/stderr
19:20:53 <diablo_rojo> clarkb, not yet, but its the next thing on my list
19:21:43 <diablo_rojo> Yeah.. logs not so helpful unfortunately
19:21:53 <diablo_rojo> gonna have to poke around and read about the lp API
19:21:53 <clarkb> ah
19:22:36 <diablo_rojo> Yeah, jealous aren't you?
19:22:56 <clarkb> diablo_rojo: I'm just waiting to find out that the email api is the solution
19:23:05 <clarkb> (that is the fix for other api issues according to ttx iirc)
19:23:28 <clarkb> #topic General Topics
19:23:36 <clarkb> #link https://etherpad.openstack.org/p/WUNOTv8MuP draft email announcement
19:23:44 <clarkb> #undo
19:23:45 <openstack> Removing item from minutes: #link https://etherpad.openstack.org/p/WUNOTv8MuP
19:23:52 <clarkb> #link https://etherpad.openstack.org/p/WUNOTv8MuP OpenDev draft email announcement
19:24:18 <clarkb> that is written. We are still waiting on lsell's document. I'm hoping we can get that email sent out before the summit, but with all the other demands on everyone not sure that will happen
19:24:25 <diablo_rojo> I'm thinking it might be, but I'll do some digging first.
19:24:26 <clarkb> in any case please do review that document and provide feedback
19:24:46 <clarkb> corvus also got opendev dns servers running and the request to update NS records has been placed
19:24:54 <corvus> jimmy submitted the glue record request to the registrar
19:24:55 <clarkb> but I don't think it has taken effect yet (I actually haven't checked)
19:25:19 <corvus> my understanding is the registrar performs some of these actions manually, so i don't know what the expected timeframe is
19:25:37 <fungi> it has not taken effect yet that i can tell, i've been checking
19:25:44 <corvus> but whenever that happens, we should have self-hosted dns, and i imagine we can have a simple website up pretty quickly.
19:26:06 <corvus> maybe we should go ahead and set up some infrastructure for a static website so it's ready to go when the other pieces are in place?
19:26:07 <clarkb> managed through code review too
19:26:21 <clarkb> corvus: probably not the worst idea, and we can host the messaging stuff from lsell once it is ready
19:27:00 <corvus> yeah -- so maybe just copy what we do for zuul-website?
19:27:40 <clarkb> works for me. I like the gerrit based review for content that zuul website does
19:27:55 <fungi> that seems like a great next step
19:30:05 <clarkb> happy to help with that but unlikely to get to it before the summit
19:30:32 <clarkb> I guess if you are interested let us know and we'll go from there
19:30:59 <clarkb> Next on the list is the summit itself.
19:31:49 <clarkb> Mostly logistics. The conference venue is not near the hotels that were listed on the event website. Factor in commute time as necessary also you can get a 7 day transit pass for 30 euro which will get you too and from the airport on busses as well as transit to and from the conference center
19:32:06 <clarkb> if you are attending the board meeting it is in the center of town not at the conference venue too
19:32:20 <clarkb> basically be prepared to rely on transit of some sort and maps
19:32:50 <clarkb> #link https://etherpad.openstack.org/p/openstack-infra-berlin-onboarding User onboarding
19:33:07 <clarkb> I've been brainstorming ideas for using the infrastructure onboarding session as a user onboarding session
19:33:31 <clarkb> if you have a moment please look it over and add anything I may have missed. Isent an invitation out to the various development/discuss lists for top level projects too
19:34:36 <clarkb> The last thing is that Tuesday night is looking like the best night to do an infra dinner if we want to do one. Wednesday night has a pub crawl an thursday I expect some people are headed home? or headed home very early the next time
19:34:40 <clarkb> *the next day
19:35:20 <clarkb> Is there interest in doing a dart throw on map for restaurant tuesday night then finding out if they can accomdoate the group we end up with?
19:35:48 <AJaeger> frickler: are you around with a recommendation?
19:37:02 <clarkb> I typically try to keep these low effort, but maybe we pencil in tuesday and go from there? frickler let us know if you have suggestions :)
19:37:08 <corvus> ++
19:37:42 <clarkb> tuesday is the marketplace booth crawl but that ends at 7:30pm local time. So we can meet at 7pm or so after seeing the booths
19:37:49 <fungi> pick somewhere large, break into groups and try to get tables nearish one another has worked fairly well in the past
19:38:01 <fungi> try to get one large table, not so much
19:38:27 <clarkb> indeed
19:38:31 <fungi> restaurants with communal seating have worked better for that too
19:39:22 <clarkb> #info Try to meet at about 7pm Tuesday for informal team dinner at Summit. Let me know if you have suggestions for locations.
19:39:28 <clarkb> I think #info is valid
19:39:33 <clarkb> yup
19:39:52 <clarkb> #topic Open Discussion
19:39:53 <fungi> it is
19:39:56 <clarkb> Anything else?
19:41:15 <fungi> #link http://lists.openstack.org/pipermail/openstack-dev/2018-September/134911.html the openstack-discuss mailing list will be open for posting starting November 19 (the monday after the Summit)
19:42:38 <clarkb> I should go sign up
19:43:20 <fungi> we're at exactly 200 subscribers so far
19:43:32 <AJaeger> and how many on openstack-dev?
19:43:39 <AJaeger> meaning: How many do we miss? ;)
19:43:50 <fungi> 5382
19:43:58 <AJaeger> wow ;(
19:44:02 <corvus> i think we'll have some late signups :)
19:44:02 <fungi> for that matter, the general openstack ml has 9554 subscribers
19:44:16 <corvus> fungi: are you planning on sending more reminders?
19:44:18 <diablo_rojo> I haven't subscribed yet, but its on the todo list.
19:44:24 <fungi> yes, i'll send another this week
19:44:29 <corvus> ++
19:44:34 <fungi> i'm quite sure a lot of those are defunct subscriptions anyway
19:44:39 <clarkb> now 201 :)
19:44:47 <fungi> and just not bouncing for a variety of possible reasons so never scrubbed
19:49:05 <clarkb> Sounds like that is it. I'll go ahead and call the meeting now.
19:49:07 <clarkb> Thanks everyone
19:49:12 <clarkb> #endmeeting