20:00:18 #startmeeting Octavia 20:00:19 Meeting started Wed Jan 14 20:00:18 2015 UTC and is due to finish in 60 minutes. The chair is sbalukoff. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:23 The meeting name has been set to 'octavia' 20:00:24 Howdy folks! 20:00:24 o/ 20:00:29 #topic Roll Call 20:00:34 o/ again 20:00:35 present 20:00:46 o/ 20:01:03 o/ 20:01:06 I/ 20:01:14 dougwig is a cone head 20:01:14 Here's our agenda for today: 20:01:18 #link https://wiki.openstack.org/wiki/Octavia/Weekly_Meeting_Agenda#Agenda 20:01:23 o/ 20:01:25 o/ 20:01:31 o/ 20:01:45 Let's also see if we can get through it fairly quickly so people can get back to being productive. :D 20:02:05 #topic Brief progress reports 20:02:20 Ok, so! We got a lot of stuff merged this last week which is great. 20:02:31 +100 20:02:43 o/ 20:02:45 On the amphora API: I'm sorry to report no progress this last week; Should have more time for this this week. 20:03:11 off with his head 20:03:15 On the client side, I've got a little bit more testing to write, but it should be updated per the current spec 20:03:15 I will integrate TrevorV's code into the flows + test it 20:03:20 However the spec needs updated 20:03:27 I also notice that we've got a ton of WIP reviews, so I consider that a good sign that people are working on stuff and committing early and often. :) 20:03:36 i submitted a start on the haproxy driver and was working on some taskflow/taskflow testing. Will probably work on neut-lbaas ref-impl ext 20:03:45 TrevorV: Yes, spec needs updating. I'll do that before adding more code. 20:03:57 kk sbalukoff I'll update accordingly as well 20:04:19 a2hill: I understand you're blocked on the spec updates, right? 20:04:28 Anything else anyone is blocked on presently? 20:04:30 a2hill: don't hesitate to contact me directly to review your haproxy driver :) 20:05:09 Kinda blocked on the requirements cr I linked 20:05:15 bedis sbalukoff you might want to talk with each other about the backend of the amphora API as well 20:05:40 I have seen the comments by sbalukoff and blogan regarding the housekeeping manager spec https://review.openstack.org/#/c/142633/9. I will reply with some comments and a new patch today or tomorrow. 20:05:42 rm_mobile: Could you like it here? 20:05:45 link 20:05:52 Correct sbalukoff, some of the answers there will help decide driver logic 20:05:59 ajmiller: Thanks! that's great! 20:06:12 bedis, the driver itself is very simple mostly because things like the api is abstracted from it. 20:06:20 a2hill: Ok, I will do what I can to prioritize getting those answers done. 20:06:21 sbalukoff rm_work will be joining soon 20:06:32 Thank you sbalukoff 20:06:41 a2hill, bedis: except building the haproxy config 20:06:59 +1 20:07:02 ajmiller: good to know 20:07:03 well yea, and in that case its sorta ready for review inside here: 20:07:12 sbalukoff: https://review.openstack.org/#/c/146231/ 20:07:17 https://review.openstack.org/#/c/144348/ 20:07:22 sbalukoff: linked in the meeting overview thing too 20:07:23 blogan: Yeah, but that's basically just a template. ;) 20:07:31 ^ 20:07:39 jinja template I hope 20:07:42 #link https://review.openstack.org/#/c/146231/ 20:07:50 #link https://review.openstack.org/#/c/144348/ 20:07:59 Thank you TrevorV ;) 20:08:06 xgerman: You can -1 it if it isn't. (It is.) ;) 20:08:08 #link https://review.openstack.org/#/c/142633/9 20:08:26 rm_work: Aah! Right. 20:08:28 Unicorn Template, what is this 'jinja' you speak of 20:08:33 I was just checking :-) 20:09:25 Heh! 20:09:49 Ok! Any other progress reports people would like to share at this time and/or blockers / requests for help people want to bring up? 20:10:25 rm_mobile: you don't have to wait for that review. Our req file is already in violation. And while that needs to be fixed, you can make progress 20:10:31 (FWIW, I'm pretty happy with the velocity we've achieved since the new year...) 20:10:57 guess that was everybody's new year resolution ;-) 20:11:11 dougwig: it breaks the gate 20:11:14 dougwig: jenkins -1s 20:11:20 oh wait shit 20:11:35 I think I am thinking of a neutron-lbaas CR >_< nm ignore me 20:12:02 So just import blindly for now, and try wrap 20:12:14 Ok 20:12:17 im pretty sure he's talking about neutron-lbaas 20:12:20 yep 20:12:25 which is the only reason it matters 20:12:27 so ignore me 20:12:32 always do :) 20:12:42 forgot which meeting i was in T_T 20:12:44 That's not stack forge, so has less leeway 20:12:48 it's all the same people... 20:13:02 :) 20:13:05 No worries, eh. 20:13:10 Ok, so! 20:13:16 Let's move on to the next topic. 20:13:20 Infra rules vary. 20:13:20 #topic Closing in on an alpha release 20:13:44 define "closing ini" 20:13:51 i mean "closing in" 20:13:57 Basically, with this I just wanted to say that I'd like to put together a list of the last to-do's and whatnot's we'll need to get an alpha release going. Something akin to the 0.25 release. 20:14:12 But something which spins up an amphora, plumbs it, and can configure listeners on it. 20:14:27 we can spin up amphora today 20:14:30 I'm going to try to coordinate / document this via launchpad (as much as I hate it.) 20:14:33 we can't end to end 20:14:46 kk, but only on the condition that when we release our 0.5 version, we code-name it '50-cent' 20:14:52 xgerman: I'm looking for something people can really start playing with that will actually do some load balancing. 20:14:53 Geting a create end to end would be a nice milestone 20:15:13 Rm-work +1 20:15:19 jorgem: I also know you want to see features, etc. tied to milestones. 20:15:34 I'll try to do this, but again, I think launchpad is a very hamfisted tool for this kind of thing, to put it nicely. 20:15:47 sbalukoff: correct 20:16:05 On this front, if y'all have insights that are not obvious, or know of things we will need to do that are not presently covered in a blueprint, please let me know! 20:16:10 (Outside of this meeting) 20:16:40 ok, we should probably define what end-to-end mean 20:17:01 you want to use the neutron/open stack client create?? 20:17:22 end-to-end to me means octavia api request spins up a vm with haproxy loaded that can accept traffic and load balance 20:17:39 so no neutron lbaas integration? 20:17:42 no 20:17:54 just using the octavia api 20:18:07 I'll write a quick neutron driver. 20:18:16 thanks dougwig 20:18:28 #action dougwig to write a quick Neutron driver for Octavia 20:18:39 hes good at writing drivers 20:18:44 Indeed! 20:18:50 (in .rb) 20:18:56 HAHA 20:18:57 Quick and neutron in the same sentance. Cool! 20:18:58 T_T 20:19:09 Yes yes in rb!! 20:19:11 he should have said neutron-lbaas 20:19:18 bedis dont encourage dougwig 20:19:36 I'm challenging him 20:19:42 Ok, anyway, I just wanted to get that out there, and let you know where my intentions lie for the next few weeks-- we're so close, I feel like we should be able to have an alpha pretty quickly. 20:20:09 (Obviously, the Neutron LBaaS meet-up is in those next few weeks-- and that work will take priority then, of course.) 20:20:20 Ok, next topic; 20:20:24 #topic Summit talk proposals 20:20:27 well, next end-to-end question: Our goal is devstack? 20:20:40 xgerman: Not necessarily. 20:20:45 it would be a nice to have 20:20:47 glad I asked :-) 20:20:54 blogan: true dat 20:21:02 but its not end to end to me 20:21:28 jorgem: Did you have any particular summit talk proposals in mind? 20:21:34 Well... 20:21:50 since we spoke in Paris I was wondering what kind of talk WOULD make sense for Vancouver 20:21:53 I want to submit another version of what we did in Paris 20:21:59 I wanted to get some thoughts on that 20:21:59 >< 20:22:03 dougwig: for neutron-lbaas? 20:22:23 dougwig: Should it be more Octavia based this time? 20:22:25 Yes, but we could bundle in the mew reference, Octavia 20:22:29 New 20:22:41 I think it makes sense to have a Neutron LBaaS v2 talk in any case. I also think Octavia should be at a state where we can show people "Look! It does stuff!" 20:22:43 well, we can have two talks -- espeically if we announce Octavia .5 there 20:22:46 On phone and walking 20:23:08 dougwig: Hell yeah! 20:23:13 I'd like to demo DSL and Octavia. Could be 2 20:23:22 dsl? 20:23:22 Ssl 20:23:24 ohh 20:23:29 Agreed. 20:23:31 you mean tls 20:23:32 Dya 20:23:34 Cable modems? 20:23:38 HAHA 20:23:54 sounds like udp load balancing 20:23:54 how to LB modems with HAProxy :) 20:24:03 ;p 20:24:09 haproxy.rb :) 20:24:12 of course 20:24:15 >< 20:24:15 XD 20:24:27 okay so two talk proposals then. On on Neutron LBaaS and one on Octavia? 20:24:31 One* 20:24:32 the only person stopping us from udp load balancing is bedis 20:24:42 jorgem +1 20:24:54 I guess part of the reason to discuss this in this group is to collaborate between our companies on who is going to be giving these talks, right? 20:25:10 sbalukoff: that would be nice 20:25:15 +1 20:25:24 Well, I'm game for helping out with both of those talks. :D 20:25:24 i figure dougwig and i will be doing a neutron-lbaas talk 20:25:24 I'm planning on going this time around and I love speaking :) 20:25:40 (Especially since I somehow ended up on stage even though I wasn't a speaker last time.) 20:25:46 (Again, I'm a jerk) 20:25:55 I went up there, too 20:25:58 Who would like to talk? 20:26:01 Indeed! 20:26:03 me 20:26:03 i doubt i'll go to this one, again 20:26:09 Let's get names and then split up talks? 20:26:10 vivek somehow ended up on stage and we hadn't talked to him prior ot that 20:26:24 he did the best demo there though! 20:26:28 Somehow blogan got on stage 20:26:30 Haha! True! 20:26:30 since if blogan and jorgem are going, they probably won't send a third, and i don't want to push my luck since i REALLY want to go to Tokyo 20:26:33 I want to try again, but others may want to hang me or themselves before letting me do it again 20:26:35 me as well 20:26:56 i would love to do one in Tokyo 20:27:00 :D 20:27:00 Vancouver is practically in our back yard. Expect a lot of Blue Box people there. 20:27:10 same for HP Cloud 20:27:15 Yep! 20:27:35 Ok, I would definitely like to talk, it sounds like german would, as well as jorgem and blogan. 20:27:45 And dougwig, right? 20:27:45 + johnsom 20:28:11 Ok, perhaps we can take it offline to refine the talk ideas and who is probably most appropriate to be speaking for which? 20:28:22 well ill definitely do a neutron-lbaas one but if a lot want to do octavia i dont ahve to do that one 20:28:29 (Though we are doing well on time here-- we could continue to discuss this here.) 20:28:52 It probably makes sense for me to do the Octavia one. 20:28:59 yep 20:29:09 after all you are the PTL :-) 20:29:11 Until y'all rise up in a bloody coup. 20:29:18 ;) 20:29:45 (Or, you know, we do an actual PTL election.) 20:30:58 ok, two talks lots of people 20:31:00 so so far 4 people would like to talk? 20:31:16 I counted 6 20:31:17 I count 6 with dougwig and johnsom 20:31:28 ah yes didn't see those lines 20:31:35 Man no respect, no respect at all... 20:31:38 lol 20:31:39 HAHA 20:31:49 johnsom should change his name to dangerfielr 20:31:57 XD 20:32:03 we will most likely ad several people during the talk anyways 20:32:10 Yup. 20:32:14 +1 20:32:18 add* gosh I can't type today 20:32:37 we are fond of calling people on stage for a demo 20:32:39 Does it make sense to have separate talks in Neutron LBaaS land for: v2, and TLS? 20:32:47 (ie. three talk ideas?) 20:33:05 I don't think so 20:33:06 sbalukoff: I'm going with not really 20:33:06 well i would say no if we were guaranteed to get both accepted 20:33:07 +1 20:33:16 two talsk areenough 20:33:21 blogan: That was what I was getting at. 20:33:27 yeah but octavia getting accepted is probably low 20:33:36 sadly, you are right 20:33:40 Though I suppose more proposals is just likely to dillute th vote. 20:33:41 since the masses dont know much about it 20:33:42 the. 20:33:44 Openstack has many pieces, and limited talk slots. Lbaas isn't that huge to anyone but us to warrant half a dozen talks. 20:34:00 we should have a whole track 20:34:04 dougwig: You're right. 20:34:10 Let's call it "Neutron LBaaS Drivers" and then only talk about Octavia :) 20:34:15 XD 20:34:19 And A10, right? 20:34:30 *That* won't piss any vendors off at all. 20:34:32 I still think that a neutron lbaas plus Octavia, with demos, would make a very focused 40 minutes. 20:34:43 add a "pr0n" keyword inside ;) 20:34:46 dougwig: A very full 40 minutes. 20:34:54 Especially if "with demos" happens. 20:34:58 dougwig: yeah we sped through the neutorn lbaas talk in paris and had way too much time at the end 20:35:11 We only used 30 last time, with an ad hoc demo. 20:35:24 yeah because ya'll talked SUPER fast 20:35:25 but now you could demo v2 calls 20:35:27 slow it down :P 20:35:27 Aah, that's right. 20:35:37 That, too. 20:35:52 fail the demo 20:35:54 then fix it 20:36:10 Each demo is about 5 minutes. 15 minutes to talk about lbaas and split, 15 minutes for an Octavia diagram and overview? 20:36:21 jorgem: Do you want to coordinate the talk proposals? 20:36:37 well, it seems there is only one 20:36:52 can we have 6+ people in one talk? 20:37:06 or does OpenStack limit us? 20:37:10 hard :/ 20:37:12 xgerman isn't that just a panel then? 20:37:17 Lightning mode. We had four last time. 20:37:18 yep 20:37:22 I doubt they'd give us all speaker credit. 20:37:39 But if most of us have ATC anyway... what's the harm? 20:37:49 xgerman doesnt 20:37:59 sbalukoff: Are we saying 1 or 2 talks? 20:38:00 xgerman: Get on that, yo! 20:38:06 I say 2 to hedge our bets 20:38:06 yep, dougwig let me down some hollow path 20:38:22 i think we should go with two proposal, one neutorn lbaas and one octavia, if octavia gets accepted then neutorn lbaas has enough material to just mention octavia 20:38:22 Let's find out what the submission allows, then figure it out 20:38:33 It sounds like we could do one-- but I think I'd like to do two. I think we could do one just on Octavia and have more than enough to talk about for 40 minutes. 20:38:34 xgerman: we will still get that in 20:38:35 alright I'll check in on that 20:38:37 if octavia doesn't neutorn lbaas can expand on octavia 20:38:43 yeah 20:38:53 blogan: +1 20:39:05 Fine by me. I can coordinate the neutron talk? 20:39:07 blogan +1 20:39:08 #action jorgem to check on speaker limit 20:39:18 dougwig: Sounds good. 20:39:19 sbalukoff: I think you need to give me the action item 20:39:21 dougwig: go 20:39:25 also RAX can always rent a suite so we can give more talsk ;-) 20:39:30 #action: jorgem to check on speaker limit 20:39:39 xgerman: HP better have an amazing party 20:39:46 #action: dougwig to coordinate on Neutron LBaaS talk. 20:39:51 HAHA 20:39:54 lol 20:40:03 jorgem: Did you want to coordinate on the Octavia talk, or leave that to me? 20:40:04 The bar is set 20:40:29 I will be very surprised if that bar gets even closely approached for a long time. 20:40:34 sbalukoff: I guess you can. I'd just like to participate in the speaking. But I can work with you on the outline 20:40:39 Epic doesn't even begin to describe that party. 20:40:46 jorgem: Sounds good! 20:40:55 #action: sbalukoff to coordinate on Octavia talk. 20:40:59 Ok! 20:41:03 Moving on... 20:41:07 #topic Open Discussion 20:41:39 Er... anyone have anything they'd like to discuss in the group here? 20:41:44 I have a question for anyone! Does anyone have any knowledge of "responses", a library used to mock the "requests" library? 20:41:51 nope 20:41:56 nope 20:41:59 nope 20:42:02 nope 20:42:04 I do. 20:42:07 Just kidding. I don't 20:42:07 heyo! 20:42:11 lol 20:42:11 I usually used mock 20:42:11 lel 20:42:44 xgerman responses seems to make it really really simple 20:42:58 hmm 20:42:59 yeah, go for it :-) 20:43:02 no idea 20:43:07 just to let you know I should come to San Antonio meetup 20:43:07 TrevorV: Yep! Give it a shot. 20:43:17 bedis: Excellent! 20:43:19 Oh I wasn't looking for permission ha ha, I was wondering if someone could be a source of a question or two :D 20:43:34 permission will be rejected with a -2 20:43:40 :) 20:43:44 bedis: awesome! 20:44:02 Ok, anyone have anything else they'd like to ask or discuss? 20:44:31 it's a wrap 20:44:50 \0 20:44:52 Ok, folks! Looks like we're done for today. Thanks, y'all! 20:45:00 o/ 20:45:03 #endmeeting