19:01:50 #startmeeting infra 19:01:51 Meeting started Tue Apr 11 19:01:50 2017 UTC and is due to finish in 60 minutes. The chair is pabelanger. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01:52 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:01:55 The meeting name has been set to 'infra' 19:01:59 #link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting 19:02:01 #topic Announcements 19:02:19 not much to stay here, expect I'm standing in for fungi today 19:02:36 #topic Actions from last meeting 19:02:41 #link http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-04-04-19.03.html 19:02:47 fungi put forth proposal to flatten git namespaces 19:02:58 I took a look, and didn't see anything 19:03:16 and since fungi isn't here today, we can likely action again for next week 19:03:22 agreed 19:03:28 #action fungi put forth proposal to flatten git namespaces 19:03:33 pabelanger Open an Ubuntu SRU for bug 1251495 19:03:35 bug 1251495 in mailman (Ubuntu Trusty) "Lists with topics enabled can throw unexpected keyword argument 'Delete' exception." [High,Triaged] https://launchpad.net/bugs/1251495 19:03:50 I started looking into this, but have not created a bug yet. I will reaction and do so for next week 19:04:02 #action pabelanger Open an Ubuntu SRU for bug 1251495 19:04:11 and that was it 19:04:22 #topic Specs approval 19:04:29 Zuulv3 Executor Security Enhancement 19:04:31 #link https://review.openstack.org/444495 19:04:40 jeblair asked to put this on the meeting today. Is this something we are ready to move forward for a vote, or do we want to hold off until next week? 19:04:55 SpamapS: ^ 19:06:11 I think SpamapS is also in the afk boat in michigan 19:06:19 think so too 19:06:48 I read through it, I think its well put together. But personally prefer the alternative listed as its somethign we currently do with success and not much pain 19:07:42 Yes, I think it has some good options listed. 19:07:51 I'm not going to object strongly enough to move forward with it as proposed, just more comfortable when it comes to security being a little conservative and using a known good solution 19:07:56 I haven't been able to get bublewrap working locally yet myself 19:08:21 *er not objecting strongly enough that we can't move forward 19:09:15 so, if we want to open voting, I was thinking keeping it open until next tuesday. This just people that are away time to cast votes 19:09:28 other wise, I'm happy to defer to next week 19:09:29 seems reasonable 19:09:52 k, lets start voting 19:10:02 #info Infra Council voting is open for the "Zuulv3 Executor Security Enhancement" spec until 19:00 UTC on Tuesday, April 18 19:10:32 if nothing else, onwards to the next topic 19:10:44 #topic Priority Efforts 19:10:57 Seems to be the status quo for now 19:11:18 clarkb: did you want to add anything for gerrit upgrades? 19:12:11 uh I need to work with zaro to write up a manual upgrade plan since we require an offline index that is expected to take many hours, then perform that on review-dev to make sure it works. Then we test new gerrit on review-dev and then we upgrade prod 19:12:19 as for zuulv3, I believe zuulv3-dev.o.o is still offline pending a security fix 19:12:30 I started an etherpad, but its pretty bare bones let me find it 19:12:35 https://etherpad.openstack.org/p/gerrit-2.13.-upgrade-steps 19:12:53 #link https://etherpad.openstack.org/p/gerrit-2.13.-upgrade-steps 19:13:07 I am hoping to work on that more this week and hopefully have review-dev upgraded soon 19:13:18 ack 19:13:33 ohai 19:13:33 are we aiming for an upgrade for summit? or after 19:14:54 my guess is after. I don't expect we'll have all the testing done in the next couple weeks 19:15:09 just based on all the toehr things being juggled including the summit 19:15:33 ya, I wasn't sure if we picked a date yet or not. 19:15:37 works for me 19:16:16 and we move on to the next topic 19:16:20 #topic General topics 19:16:44 nothing on the wiki today, if anybody has something they want to add now, we have the time to talk. Otherwise, onto open discussion 19:16:44 oh it might be nice to have a second infra root on that just so more than one person is familiar with the process 19:17:29 pabelanger: any idea if/how the caching proxies are helping things that use rdo or docker hub? 19:17:46 * mordred also curious 19:17:59 clarkb: my understanding they are helping a lot. I don't think they have had a network issue since we added them 19:18:32 I am not sure about docker registry, patches are still in process for that 19:18:34 ya the rdo issues on e-r have definitely fallen off 19:18:46 i haven't got around to an email, but i plan to restart the dib meeting in earnest. there was a bit of confusion as to who was running it, and we got slack, but i'll start doing it regularly after easter 19:19:09 #topic Open discussion 19:19:14 ianw: by getting slack you mean like a rope not like the irc alternative? 19:19:28 all the topics now! 19:19:37 Review request: https://review.openstack.org/448786 Highlight POST_FAILURE same as FAILURE on Gerrit page 19:19:51 clarkb: lol 19:19:54 oh, yes, i mean we skipped it, not random web chat clients :) 19:20:09 on the citycloud front I've been told to make accounts then tell them what they are so they can comp them and edit quotas. So uh I just need to sit down and do that. 19:20:12 clarkb: I did want to talk do you about moving apache cache to afs, was curious what you meant about that. Currently osic-cloud only has 40GB root drive, our smallest 19:20:32 jlvillal: I'll try to review that today 19:20:38 clarkb, Thanks :) 19:20:52 pabelanger: basically we mount a cinder volume in most places for the afs cache but the entire volume is mounted at just the afs cache location 19:21:00 we also landed some of the work cmurphy has been doing to depuppet DIB images, so yay for that 19:21:15 pabelanger: I was thinking maybe we could either create two filesystems and mount one for apache or mount it a level above the apache and afs caches so they can share it 19:22:21 clarkb: interesting. Okay, happy to talk a more about that. I suspect docker registry we may need more then 2GB of cache 19:22:40 ya 2GB was a conservative limit to make sure we didn't break anything 19:22:46 so definitely open to raising that as we go 19:22:57 ++ 19:23:27 okay, unless anybody else wants to continue talking. I think we can wrap up early today 19:23:52 oh please bug me to do the citycloud thing. I keep putting it off because it requires things like web forms and credit cards 19:24:11 should we action? 19:24:16 yes 19:24:47 #action clarkb to add citycloud to nodepool 19:25:38 with that, lets end our meeting for today 19:25:43 thanks everybody 19:25:47 #endmeeting