19:04:38 <fungi> #startmeeting infra
19:04:39 <openstack> Meeting started Tue Feb  7 19:04:38 2017 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:04:40 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:04:42 <openstack> The meeting name has been set to 'infra'
19:04:46 <fungi> #link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting
19:04:52 <fungi> #topic Announcements
19:05:04 <fungi> #info Big thanks to ianw for chairing last week while I was otherwise occupied
19:05:10 <fungi> i read through the logs later in the week and looks like it was a productive mee
19:05:12 <fungi> ting
19:05:39 <fungi> #info Please muster a hearty welcome to David Shrewsbury as our newest Infra root sysadmin and returning core reviewer
19:05:49 <mordred> \o/
19:05:55 <AJaeger> welcome!
19:05:57 * mordred hands Shrews a somewhat unused pie
19:05:59 <fungi> he was actually in infra-core before we renamed ourselves "infra" (and before i joined the project for that matter)
19:06:01 <jhesketh> Yay!
19:06:03 <pabelanger> Shrews: congrats
19:06:06 <persia> \o/
19:06:14 <jeblair> Shrews: yay!
19:06:30 <Shrews> danke
19:06:31 <SotK> congrats!
19:06:34 <ianw> cool
19:06:43 <jeblair> reboot all the things
19:06:51 <pabelanger> old is new again
19:06:59 <fungi> as i understand it, he's planning to focus mostly on nodepool for now, but has been instrumental so far in shade and the latest improvements on the road to zuul v3 support in nodepool (among many other things)
19:07:14 <clarkb> darn I was hoping he would deal with Gerrit again
19:07:16 <fungi> also he loves writing java ;)
19:07:17 <clarkb> :P
19:07:22 <fungi> jinx!
19:07:31 * jeblair takes cover
19:08:05 <fungi> (for those who missed our early history, he was the author of our original "work in progress" implementation for gerrit)
19:08:25 * Shrews glares menacingly
19:08:36 <mordred> that work can be directly blamed for Shrews going and doing non-infra things for quite some time :)
19:08:46 <Zara> :)
19:08:52 * fungi wonders what ever happened to libra
19:09:10 <fungi> #action Shrews propose a change adding yourself to modules/openstack_project/manifests/users*.pp in system-config
19:09:51 <Shrews> ack
19:10:32 <fungi> i suspect we're going to chew up a lot of time on ptg discussion today, so i'll move on with the meeting
19:10:36 <fungi> as always, feel free to hit me up with announcements you want included in future meetings
19:10:49 <fungi> #topic Actions from last meeting
19:10:55 <fungi> #link http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-01-31-19.01.html
19:11:03 <fungi> ianw ensure gerritbot upgrade is deployed for new release (0.3.0)
19:11:08 <fungi> fungi@review:~$ pip list|grep bot
19:11:12 <fungi> gerritbot (0.3.0)
19:11:14 <ianw> yep, that's all working
19:11:17 <mordred> \o/
19:11:17 <fungi> lgtm, thanks ianw!
19:11:31 <ianw> gerritbot messages now have the branch in them
19:11:44 <fungi> i noticed, very nice
19:11:50 <AJaeger> I wonder whether we should remove the "master" - otherwise it's nice.
19:11:52 <fungi> that was your handiwork, right jlvillal?
19:12:16 <fungi> pabelanger update on zuul-launcher to openstack-ci move and zuul-dev for gerrit upgrade
19:12:19 <fungi> we can probably talk about this in just a sec during the priority efforts part of the agenda instead
19:12:23 <jlvillal> That was my first patch to not display master.
19:12:36 <jlvillal> But was suggested to always display branch
19:12:47 <pabelanger> fungi: I am working on that now, for our PTG zuul effort, same code will apply for zaro
19:12:51 <AJaeger> jlvillal: ok
19:13:00 <fungi> jlvillal: yeah, i expect it's a matter of personal taste. i could go either way
19:13:04 <jlvillal> AJaeger, I'm happy to change if consensus
19:13:21 <fungi> explicitness there doesn't bother me, and the implementation is simpler for it
19:13:41 <mordred> I like it
19:13:42 <jlvillal> Yes implementation is simpler
19:13:53 <fungi> pabelanger: oh, thanks! we can skip adding it to the priority efforts discussion today then
19:13:55 <ianw> (it was my comment, and i figured it's better to be consistent with the message, especially if people might have a regex etc)
19:14:20 <fungi> agreed
19:14:31 <fungi> #topic Specs approval
19:14:43 <fungi> we don't seem to have anything new up this week, which is good since the ptg is bearing down on us
19:15:07 <fungi> #topic Priority Efforts
19:15:26 <fungi> nothing on the agenda for these today, though we'll talk about zuul v3 stuff for the ptg next anyway
19:15:40 <fungi> #topic Zuul related PTG prep (jeblair)
19:15:48 <fungi> #link https://etherpad.openstack.org/p/pike-ptg-zuul
19:16:01 <jeblair> oh whew i was just looking up that link
19:16:11 <fungi> this is a continuation/rehoming of the discussion from the zuul meeting yesterday
19:16:41 <jeblair> yeah, we talked a bit out what we need to do to prepare for the ptg, and hopefully meet our goal of actually running some sort of zuulv3 job
19:16:58 <jeblair> that etherpad has a list of things to get done before we arrive
19:17:43 <fungi> that's an attractive approach in my opinion. i like the idea that we have a solid goal for something we can show coming out of our two days
19:17:57 <jeblair> hopefully it's fairly self-explanatory; one thing on there i have signed up for is to write some notes on what we'll have in place, what still needs to be done, and what building a job at the ptg might look like.
19:18:17 <jeblair> so we should all be on the same page, or maybe the same chapter, when we get there
19:18:32 <jeblair> i'll try to do that this week
19:19:00 <fungi> a few of us assigned prep tasks from that pad to ourselves
19:19:54 <pabelanger> I have some patches up already for nodepool-launcher (nl01.o.o) that could use some reviews
19:20:01 <fungi> if there's anything anyone else thinks about that is probably a prerequisite for making it happen (even if you won't be at the ptg yourself), add it to the prep list and feel free to solve/research/whatever to help us for when we get there
19:20:20 <jeblair> ++
19:20:42 <fungi> it's definitely a way to be involved even if you won't be present
19:22:15 <fungi> anything else we want to cover about zuul prep for the ptg before we move on to more general last-minute ptg planning?
19:22:34 <fungi> or are people still digesting that etherpad?
19:23:02 * mordred is digesting a bowl of taco meat
19:23:19 * fungi pictures mordred face-down in a bowl of taco meat
19:23:34 * jeblair wonders whether the taco was raised humanely
19:23:39 * mordred wonders if fungi has a camera aimed at him
19:24:28 * fungi distracts everyone from his surveillance activities by spontaneously changing the topic of conversation
19:24:30 <fungi> #topic General PTG planning (fungi)
19:24:43 <fungi> #link https://etherpad.openstack.org/p/infra-ptg-pike
19:25:11 <fungi> i like that more of the community has started throwing things at this
19:25:49 <fungi> ildikov, sdague and mriedem want to collaborate on localrc to local.conf conversion in devstack-gate, for example
19:27:12 <fungi> my plan so far is to chunk monday and tuesday up into a total of four large blocks (before/after lunch each day)
19:27:53 <fungi> and do brief unconference pitching at the start, with wrap-up regrouping discussions either at the end of each or at the beginning of the next block
19:28:51 <mordred> fungi: the localrc/local.conf discussion might also be a good time to get those folks visibility on to v3 job structure and stuff
19:29:30 <fungi> oh, excellent point
19:29:32 <jeblair> yeah, the discussion this morning has given us more data to help shape what a good v3 config for devstack would look like
19:29:32 <fungi> this is mostly uncharted territory... i'm hoping it works out more or less like the unstructured time we've had at design summits in the past, but since it's longer we cat get better group arcs over the duration more like some of our focused mid-cycle events have been
19:29:56 <fungi> s/cat/can/
19:30:58 <mordred> if we come out of the week with a running v3 job and sdague understanding how v3 relates to devstack-gate I'll be over the moon
19:31:04 <fungi> it's a little hard to know what the dynamic will be in the room and how we'll be able to break out within the space and/or taking over various corners of lounge areas or reserving short blocks in some of the cross-project spaces
19:31:13 <mordred> agree
19:31:20 <jeblair> fungi: right, and i think that we should try to focus on things where we can make a big difference having a bunch of people in a room together
19:31:32 <fungi> absolutely
19:31:44 <jhesketh> +1
19:32:22 <fungi> i'd like to accommodate items that only a handful of people are interested in collaborating on, but odds are they'll need to do it in other spaces to keep the main room for large efforts
19:32:49 <jeblair> sounds reasonable
19:32:49 <jhesketh> I'm wondering how we can best be helpful to other projects for the rest of the week. With no schedules it'll be difficult to know which rooms/discussions to attend
19:33:38 <jhesketh> Should we be trying to schedule 'infra time' with groups?
19:33:41 <clarkb> jhesketh: I think the plan/goal/hope is to use the new ethercalc server to advertise when large chunks of things are hjappening and where
19:33:49 <fungi> jhesketh: yep, i've wondered that myself. one method which will _probably_ work is if people in infra have a general affinity for a particular vertical then hang out with them and alert others if our help is needed
19:34:05 <jeblair> possibly shouting on irc could be a thing
19:34:06 <clarkb> We should have backups working today and I was planning to send mail to list tomorrow about it once I confirmed backups happened
19:34:15 <fungi> also if a lot of us are hanging out in #openstack-ptg then we can be raised easily
19:34:27 <fungi> er, what jeblair said ;)
19:34:47 <jeblair> that even lets us hang out in a bar on thursday and show up when needed :)
19:35:03 * fungi bets there is a hotel bar
19:35:04 <jhesketh> Yep, I'm guess it's going to be a learning experience and something we iterate on but that seems like a fine place to start :-)
19:35:47 <fungi> right, i'm setting my expectations to "reasonable" for this first ptg, since we'll be feeling a lot of it out for the first time (all of our community, not just infra)
19:35:51 <mordred> jeblair: can we hang out in a bar monday-wednesday too?
19:36:31 * fungi wonders if we could talk erin into just making the lounge into a bar ;)
19:36:37 * jhesketh nods
19:39:18 <fungi> okay, so anyway, throw anything you want to collaborate on into the etherpad
19:39:57 <fungi> it might be software development, or planning type things that benefit from having a lot of faces in one room
19:40:19 <fungi> a little variety will also probably help us avoid falling asleep as much
19:41:19 <clarkb> ++
19:41:22 * fungi thinks some of us may be falling asleep now
19:41:32 <mordred> wait - we're allowed to sleep at these things?
19:41:53 <fungi> if you don't mind waking up with things written on your face in permanent marker, sure ;)
19:42:07 * fungi notes to pack permanent markers
19:42:58 <clarkb> I am distracted by all the colors on the etherpad
19:43:55 <Shrews> I'm glad I'm only staying for the first half of PTG. I hear Atlanta really lets you down for any second half things.
19:44:07 <fungi> ouch
19:44:10 <fungi> the owl
19:44:12 <bswartz> burn!
19:44:13 <mordred> wow
19:44:15 <clarkb> wow
19:44:33 <pabelanger> I get that reference
19:44:39 <fungi> Shrews: that's why we're headed to boston for the summit, of course
19:44:46 <Shrews> yay sportsball
19:44:48 <clarkb> fungi: double wow
19:45:10 <jeblair> even i get that since i read about it in my newspaperotron
19:45:57 <fungi> certainly a strange coincidence that we booked our events into the two towns who sent their gladiators to the big event
19:46:45 <fungi> well, anyway, does anyone have any specific items on the planning etherpad they want to discuss during the last 15 minutes of our meeting today?
19:47:03 <fungi> otherwise we can go to open discussion (since we mostly seem to have done at this point)
19:47:16 <clarkb> we really need to light a fire under the "stop using precise" task
19:47:22 <clarkb> since precise has like 2 more months of life
19:47:42 <fungi> right, i wondered if some people wanted to maybe work together on moving mailman
19:48:02 <pabelanger> ya, sign me up for that to help
19:48:14 <fungi> puppetboard is the only other one, right? and it's already broken anyway
19:48:28 <pabelanger> ya, not sure the status of that to be honest
19:48:30 <clarkb> we can ask ansible for the listing
19:48:46 <clarkb> I think once I can get zanata upgrades behind me I will try to focus on ^
19:49:09 <jeblair> i'd like to do this one as a virtual sprint
19:49:26 <fungi> i could get behind that option as well
19:49:44 <jeblair> i would volunteer for that
19:49:44 <fungi> it may not really benefit from ptg-ness anyway
19:49:49 <pabelanger> it worked out well last time
19:50:46 <fungi> i was also recently taking a fresh look at mm3 but seems like the packaging story there is still a little meh
19:50:55 <clarkb> wfm
19:51:11 <jeblair> fungi: mm3 is still the future of mailman?
19:51:20 <fungi> great question
19:51:41 <mordred> Mailman 3.0 was released on April 28, 2015.
19:52:11 <mordred> http://docs.mailman3.org/en/latest/ fwiw
19:52:23 <fungi> i think the point is it's been called into question whether mm3 is too dissimilar and people will stick woth a continuation of more traditional 2.x
19:52:35 <fungi> s/woth.with/
19:53:00 <jeblair> i don't really know what the word on the street is.
19:53:23 * jeblair assumes mailman is whatever apt-get installs
19:53:50 <clarkb> fungi: its not different like google groups is different is it?
19:53:55 <clarkb> I can still send email and get email?
19:54:36 <mordred> clarkb: maybe?
19:54:42 <fungi> i get the impression it's a heavy rewrite, but since it's not really packaged by any distros (there is ongoing drama trying to get the dependencies into debian for example) i have no experience using any lists running on it
19:54:53 <mordred> here's a fun bug: https://bugs.launchpad.net/mailman/+bug/965532
19:54:53 <openstack> Launchpad bug 965532 in GNU Mailman "Need a script to upgrade from MM2 to MM3" [Critical,Confirmed] - Assigned to Richard Wackerbarth (wacky)
19:55:20 <mordred> reading the description of hte thoughts, it seems like mm3 is just a new piece of software
19:55:39 * persia has heard good things about ponymail and frustrsting stories about mailmanv3, but has deployed neither.
19:56:05 <fungi> #link https://bugs.debian.org/799281
19:56:05 <openstack> Debian bug 799281 in wnpp "ITP: mailman3-core -- Mailing list management system" [Wishlist,Open]
19:56:08 <fungi> (for the record)
19:56:27 <fungi> something called "hyperkitty"
19:56:31 <ttx> mordred: yes, it's different enough
19:57:14 <fungi> in positive news, it's still python-based
19:57:22 <fungi> py3k-only in fact
19:57:26 <ttx> and still written by Barry last I checked
19:58:32 <jeblair> persia: ponymail requires a mailing list system, such as mailman3
19:58:48 <fungi> #topic Open discussion
19:59:01 <fungi> (with one minute left!)
19:59:02 <persia> Apologies for the noise then.
19:59:07 <AJaeger> fungi, what needs to be done to redirect http to https on docs.o.o and developer.o.o?
19:59:23 <fungi> AJaeger: a change updating the vhost configs for them
19:59:42 <fungi> AJaeger: assuming everyone's okay with serving only https versions of those sites going forward
19:59:52 <fungi> i didn't see much else out of the docs team on that item
20:00:00 <fungi> and we're out of time
20:00:01 * AJaeger will ask again
20:00:03 <fungi> thanks everyone!
20:00:07 <fungi> #endmeeting