20:00:03 #startmeeting Octavia 20:00:04 Meeting started Wed Nov 16 20:00:03 2016 UTC and is due to finish in 60 minutes. The chair is johnsom. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:09 The meeting name has been set to 'octavia' 20:00:15 o/ 20:00:19 hey people :) 20:00:56 Hi there. We will see how many people get the DST right this week. I had a few messages after the meeting last wekk 20:01:21 Hi 20:01:22 hahaha :P 20:01:42 Let's jump right in 20:01:44 #topic Announcements 20:01:44 yeah it's interesting, I moved my meeting in calendar to remember that :P 20:01:50 hey 20:01:54 PTG registration is open 20:02:10 Yeah, I put it in Outlook as a UTC timezone so it will switch for me 20:02:17 #link http://www.openstack.org/ptg 20:02:35 There are limited slots, so if you want to go you should sign up soon. 20:02:51 DIB switch to xenial / systemd support 20:03:17 diskimage-builder (DIB) changed the default ubuntu release to xenial recently. 20:03:52 This impacted us with the amphora images, so I did a patch that merged last night (thanks cores) that enables support for systemd base images. 20:04:04 Will the Octavia team definitely represent at PTG? Some other off-cycle meetup? 20:04:35 There may be some impact to folks trying to run stable branch versions of Octavia as DIB does not do stable branches. More thinking on this is needed. 20:05:09 m-greene That is a good question. I have approval for travel to PTG, but I think we should talk as a team about that 20:05:36 Let's discuss in open discussion. 20:05:59 Last announcement I have is we have a new domain for the sonar gate: octavia.cloud 20:06:45 The octavia.io expired and the old owner did not want to renew. 20:07:11 octavia.io was expensive to have, so I switched to a more cost effective octavia.cloud 20:07:25 great :) 20:07:32 Ping me if you see any issues with the sonar gate. 20:07:50 #topic Brief progress reports / bugs needing review 20:08:13 We still have a number of open merge patches to review: 20:08:21 #link https://review.openstack.org/#/c/364655/ 20:08:29 #link https://review.openstack.org/#/c/265065/ 20:08:37 #link https://review.openstack.org/#/c/360794/ 20:08:45 #link https://review.openstack.org/#/c/382147/ 20:09:10 Also, vendors, please review the flavor support spec: 20:09:12 #link https://review.openstack.org/#/c/392485/ 20:09:56 Otherwise I was working on the xenial/systemd patch. 20:10:12 Also of note, the OpenStack Ansible spec for Octavia support merged. 20:10:26 Any other progress reports or bugs to highlight? 20:11:24 #topic Open Discussion 20:11:48 so there is still 373 tickets for PTG 20:11:56 I have partial allowance for going 20:11:58 So, PTG, non-PTG mid-cycle, or both. Any thoughts/comments? 20:12:03 Hard or soft deadline on reviewing ‘flavor support spec’? 20:13:12 Well, the Ocata-1 milestone is this week, but that spec is not tied to a milestone. 20:13:30 It is really getting it reviewed so folks can confidently start work 20:14:15 I really would like m-greene and kobis to comment on it 20:14:33 As I know you all were interested in the topic 20:14:42 re: PTG, if there is strong cross-team collaboration or co-design necessary, then PTG makes sense. If Octavia is mostly independent, then we have more flexibility. Are there any expectations for reporting roll-up into neutron (stadium or otherwise)? 20:15:21 Someone on my team should be reviewing. She just finished a broader analysis/comparison on neutron flavor and/or agent extension. 20:15:40 m-greene: we're not independent, we're using neutron, nova, barbican, keystone, glance, ... 20:15:49 I expect there will be discussions about out spin-out of neutron at the PTG. 20:16:15 We do have cross team discussions, but we have had those recently at the summit, so... 20:16:46 The real question is do we want to have a mid-cycle for Ocata and if so, should it be the PTG? 20:17:15 probably 20:17:25 it's really short release 20:17:27 Hahaha, helpful 20:17:38 Yes, it is a short release. 20:17:41 I understand that, was thinking more along the lines of dependencies on other projects to build new octavia functionality (do we need those other teams to also build new things) 20:17:46 #link https://releases.openstack.org/ocata/schedule.html 20:18:28 m-greene Not really, the only ask we have against other projects right now is with barbican/keystone around the ACLs. This was a topic at the summit. 20:19:43 I am thinking that I will go to the PTG. If nothing else to see how it goes and answer any questions that come up. 20:20:35 +1 20:20:54 like we discussed that a few weeks ago, we need to find out how it's gonna work 20:21:00 Yep 20:21:39 So, let me know if you are coming as well at a future meeting. 20:22:24 I suspect that I might have a hard time doing additional travel for a mid-cycle beyond the PTG. But I haven't asked either. 20:23:03 yeah, I have the same feeling that it may be problematic to get money for that 20:23:04 Not making a committment, but I have socialized up my chain the possiblity of hosting an octavia meetup at the F5 office (Boulder/Lousivlle, Colorado). There is interest, but I’d need some help figuring out expectations, possible participants, etc. We have 2 large conf rooms with a foldable wall that could accommodate 2 dozen-ish. 20:24:06 Ok, thanks for the info m-greene. We can also typically host at Rackspace in San Antonio as well. 20:24:42 Though it might be nice to go to Boulder for a change... grin 20:24:49 +1 20:25:02 first of all we need to find out who will be interested in going 20:25:17 Historically we alternated between San Antonio and Seattle, but our Seattle options are no longer options. 20:25:24 and the if we're planning to organize where and when 20:25:54 Go to PTG in Feb to see how it plays out, then look into Boulder/San Antontio the meetup after that? 20:26:08 probably it's the best option 20:26:09 Yeah, that is probably the best plan 20:27:01 Any other open discussion topics for today? 20:27:02 the mountains are nice here in August :) 20:27:11 -1 heat 20:27:18 The beer is better there too.... 20:27:21 Grin 20:27:27 I make my own.. but still true 20:27:46 i think most of who's left is rax, right? 20:28:35 Well, technically I am the only active Rackspace person at the moment, though blogan will be coming back for a bit as well 20:28:54 * blogan wakes up 20:28:56 yes! 20:29:08 plus from OSIC it's me and two additional people for now 20:29:10 dougwig: i need to get with you 20:29:32 blogan: aye. 20:29:35 Yeah, there are a few Intel folks in San Antonio as well. 20:30:02 blogan dougwig +1 on working on the shim 20:30:21 so the easiest will be to host this in Rax to get all of this people 20:30:42 sounds like. 20:31:10 True, but I think m-greene has a team that is going to be envolved as well, so maybe it balances. 20:31:21 yep 20:31:43 like we said, PTG and later we can talk again about mid-cycle 20:31:59 Yep, I think that is a good plan this round. 20:32:09 isn't PTG meant to replace midcycles? 20:32:14 * blogan probably missed that discussion 20:32:16 nope 20:32:29 it's additionall time to cooperated between projects 20:32:41 the first 2 days yeah 20:32:50 Well, yes that was the original idea, but if that will work in practice is a different question 20:33:17 i should educate myself on it more before i make my assumptions known :) 20:33:28 it's the first one also 20:33:28 Plus, as we just discussed, travel for everyone vs travel for some of the team may make the PTG less attractive 20:33:42 so we need to remember that it may be a fail :P 20:34:18 diltram: so pessimistic, thats a sign you're an openstack veteran 20:34:27 hahaha, thx :) 20:34:38 Hahaha 20:34:48 also limitation of 500 people is limiting access 20:34:48 blogan there is an FAQ: 20:34:50 #link http://www.openstack.org/ptg#tab_faq 20:35:06 i have to read? what is this the 2000s!?!? 20:35:18 Sigh 20:35:37 Just ignore it and work on the driver shim.... Grin 20:35:45 aye aye captain! 20:36:05 * blogan goes back to the darkness 20:36:09 Ok, any other discussion items today? 20:36:22 just one from me 20:36:28 none from me 20:36:29 start reviewing the code :P 20:36:55 Yes, yes, now that the scenario gates are running again. 20:37:52 ptg was supposed to be the split of the design summit and replace midcycles. it ended up managing to just add a third trip. 20:39:56 ok I have one questin 20:40:05 diltram go 20:40:14 what we're doing with this gunicorn? 20:40:55 Good question 20:41:11 #link https://review.openstack.org/#/c/386758/ 20:41:32 we know that werkzeug is not working for us 20:41:42 It's actually this: 20:41:44 #link https://review.openstack.org/#/c/386790/ 20:42:18 but we can just drop that patchset and manage gunicorn version in DIB on our own 20:42:34 dougwig I see Adam asked about this last week. Is it time to poke the bear again? 20:43:37 We technically could bypass this as it is used in the amphora image, but having it officially in the requirements is a good thing 20:45:05 especially that we already discussed about moving out amphora code to seperate repo, then this will be more must have than right now 20:45:47 Yeah. I am willing to give this a little more time with the requirements folks 20:46:00 It's not dead there yet (there are two +2s) 20:46:10 but probably we should ping them (ML, review)? 20:46:17 I know 20:46:26 because of that I would like to see this merged 20:46:56 Yeah, me too. I will wait until tomorrow (one week from Adam's last ping) and post a comment 20:47:08 ok 20:47:27 And/or see if I can track down the -1 20:47:43 Any other topics for today? 20:48:20 I'm good for today :) 20:48:34 Going once.... 20:48:50 Ok, thanks folks, have a good rest of your day! 20:48:55 #endmeeting