20:00:39 #startmeeting octavia 20:00:39 Meeting started Wed Apr 22 20:00:39 2015 UTC and is due to finish in 60 minutes. The chair is xgerman. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:40 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:43 The meeting name has been set to 'octavia' 20:00:48 o/ 20:00:52 o/ 20:00:52 o/ 20:00:55 o/ 20:01:01 Agenda: https://wiki.openstack.org/wiki/Octavia/Weekly_Meeting_Agenda#Meeting_2015-04-22 20:01:05 #link https://wiki.openstack.org/wiki/Octavia/Weekly_Meeting_Agenda#Meeting_2015-04-22 20:01:22 #topic Announcements 20:01:50 Octavia/LBaaS/VPNaaS/FWaaS Midcycle: https://etherpad.openstack.org/p/LBaaS-FWaaS-VPNaaS_Summer_Midcycle_meetup 20:02:01 #link https://etherpad.openstack.org/p/LBaaS-FWaaS-VPNaaS_Summer_Midcycle_meetup 20:02:11 o/ sorry for being late I was in the wrong channe;;;;;;;l 20:02:22 bo worries it's jus 120s 20:02:29 o/ 20:02:35 please vote on date and location with +1 20:02:41 o/ 20:02:55 the MN location was offered by mestery, fyi. 20:03:05 im here! 20:03:09 Lake of the Woods is beautiful in the summer, trust me. 20:03:24 ive never been to minnesota 20:03:31 are we only voting if we can actually go to it? 20:03:41 I have a tent and sleeping bags ;-) 20:03:45 we won't know if we can go to it until a while 20:03:47 because if so, RAX is going to have to hold off on any votes until about 2 weeks before 20:03:47 rm_work: i'd think yes. 20:03:53 o/ 20:03:58 all of tax? 20:03:59 rax? 20:04:02 sheesh, then vote. 20:04:13 you guys can't hust rent a minvan? Roadtrip? 20:04:17 I mean, we still won't know if any of us can go until about 2-3 weeks 20:04:19 someone go spin up a rax server, so they have a travel budget. 20:04:25 T_T 20:04:38 those proceeds go to the marketing budget 20:04:38 lol 20:05:04 I'm only going to Vancouver because I am handling all of my own lodging and no per diem :P 20:05:15 but at least I'll be there 20:05:21 panhandling 20:05:28 rm_work: It will great to have you there 20:05:35 do I need to bring a tent, rm_work? 20:05:42 sballe +1 20:05:43 thanks sballe :P might just have to beg for food periodically 20:06:00 I will make sure to forward party invites to you 20:06:05 hehe 20:06:05 I thought the food was included int he conference fee 20:06:14 sballe: LUNCH is :) 20:06:19 rm_work Sorry to hear that. We can probably help get you some food and beer at the events 20:06:20 and yeah we now have to go to all the parties 20:06:32 Ah! Thanks sballe, gave me a great idea -- I'll just bring tupperware -- lunch for dinner! :P 20:06:39 -) 20:06:54 anywho 20:07:02 next announcement: 20:07:04 LBaaS Vancouver Topics: https://etherpad.openstack.org/p/lbaas-vancouver-planning 20:07:04 we will look at that list and vote :) 20:07:16 #link https://etherpad.openstack.org/p/lbaas-vancouver-planning 20:07:28 I assume dougwing and blogan started that 20:07:41 dougwig 20:07:45 xgerman: yes 20:07:48 i was told to expect to working group sessions for lbaas. one will be for lbaas feature planning, the other for "octavia as the ref driver". fyi. 20:07:52 /to/two/ 20:08:02 excellent 20:08:05 awesome 20:08:12 +1 20:08:26 Do we know when they will be? 20:08:38 mestery? 20:08:49 * mestery reads backscrool 20:08:50 i'm not sure if it's final yet. 20:09:01 I'm still working on the schedule, so not yet 20:09:05 Hopefully by next Monday, but we'll see. 20:09:10 ok, cool 20:09:20 xo we need to add Octavia topics to that pad? 20:09:37 mestery: +1 20:09:40 yes, but start a new section at the bottom or something. 20:09:46 ok, will do 20:10:07 next 20:10:08 Neutron Vancouver topics: https://etherpad.openstack.org/p/liberty-neutron-summit-topics 20:10:20 #link https://etherpad.openstack.org/p/liberty-neutron-summit-topics 20:10:28 my eyes! 20:11:03 and lastly I think an RC2 is being prepared... blogan, dougwig, mestery any details? 20:11:29 i think that's all the details. if you need a fix in rc2, propose a cherry-pick to stable/kilo 20:11:39 RC is in the works, will be cut tomorrow. 20:11:50 so be quick with proposing 20:11:50 I spent an hour with ttx yesterday, we're just doign rechecks to get the final patches in 20:11:55 getting something in would have to be very important right? 20:12:03 It's actually too late to propose now. 20:12:17 Unless it's a legitimate, "holy crap the relase will burn with this!" type of bug 20:12:46 given the overall flakiness of openstack, that is a very high bar indeed. 20:13:08 lol 20:13:25 chair blogan 20:13:30 #chair blogan 20:13:31 Current chairs: blogan xgerman 20:13:43 #topic Brief progress reports 20:14:19 johnsom? 20:14:38 neutron-lbaas driver - initial coding done, not tested *at all*, needs update for writable ids. WIP is here: 20:14:39 #link https://review.openstack.org/#/c/174114/ 20:14:40 I have been testing out controller worker on devstack (beating head against gerrit outages, back pypi packages, etc.) merging patchsets, etc. 20:14:41 3 big things are controller worker, network driver, and amphora driver 20:15:09 Right now I have it up building through load balancers and plugging the networks 20:15:20 that's something 20:15:32 so building the amphorae? and plugging the networks on those? 20:15:49 sound slike it 20:15:56 I want to test through config generation, then might propose a merge and many bug fixes from there 20:15:58 are you using the devstack private network as the management network? 20:16:04 blogan, yes 20:16:31 okay cool 20:16:39 blogan, yes, private for management, public for vip (just for giggles) 20:16:50 demo-quality 20:17:25 well i think the vip should be on an isolated network, and then just point a flip to that port to get public accessibility (but the vip network is controlleed by the user) 20:17:31 not yet demo quality, we have some bugs and I'm doing some manual DB stuff, but getting there. 20:17:36 so that should be relatively easy 20:18:27 Just to provide a little update from myself. I tested the ssh_driver thus far with ubuntu 14.04, looks good on most recent patchset. Please comment if you find otherwise 20:18:46 Trevor_V: looks good for all methods? 20:18:52 Yep. 20:18:59 great 20:19:11 I am working/testing on patch for Al's devstack plugin to build the mgmt network and start the api. Also, tempest stuffs 20:19:24 cool 20:19:44 and network driver should be ready to go for a non vrrp setup, it needs some work to get multiple vrrp instances to work 20:19:55 I updated the Amphora API spec and the whole REST stuff is coded... more testing needed though 20:20:29 Yeah, I'm really targeting non-vrrp at the moment, but it's cool that it is seeing progress too 20:20:40 for vrrp, which would be icing on the cake for a demo, the amphora driverw ould need an update 20:21:00 well, we need something for Sunday night ;-) 20:21:12 this sunday night? 20:21:23 Sunday night before the talk 20:21:27 i know lol 20:22:06 blogan dougwig It would be handy to get this merged: https://review.openstack.org/#/c/172558 It's -1 dougwig 20:22:13 okay then we should get controller worker tested out, reviewed, and merged, which would also need tobe tested out with the network driver and amphora drivers 20:22:19 The neutron driver depends on it 20:22:48 dougwig: would you be okay with merging that in with a later review that would fix for vrrp? 20:23:01 yes. 20:23:54 Problem solved... 20:23:56 that would leave the controller worker and amphora driver then 20:24:14 and then we'd need to merge the stevedore loading of the handler ptoohill did 20:24:30 i thought I +2'd that 20:24:42 so blogan merge ahead 20:24:43 lol well then i'll +A it 20:24:45 lol 20:24:47 You did, but adam only +1 20:24:58 i need to test it out first 20:25:01 yeah, he's cautious 20:25:40 #topic Sticker - Pick a design 20:25:41 oh it may need to add soemthing 20:25:47 D 20:25:54 its a super simple change, and stevedore does what its supposed to. Theres no real logic there 20:25:56 #link https://s3.amazonaws.com/uploads.hipchat.com/8522%2F409388%2FzzvhUeiZJPki7iZ%2Foctavia_logo_revs3.pdf 20:26:09 #link https://docs.google.com/drawings/d/1PvJj_8A6oFRdUN9xAgm9Z8joM33Z7CuTJUzCQn3GoCM/edit 20:26:13 alright, can +2, but i prefer to try RUNNING code like that :P 20:26:20 what does it need to add blogan 20:26:27 NOT "your load is our job" 20:26:29 add the queue producer to the setup.cfg 20:26:37 oh 20:27:10 so the s3 link is our corporate artist 20:27:21 I did notice you guys completely disregarded our sticker ideas from last week. 20:27:25 That's fine I guess. 20:27:32 "Balance is our Business" +1 20:27:34 Oh pfff 20:27:40 I didn't see the link to our stuff 20:27:50 wtg Trevor_V 20:27:53 I linked it 20:28:05 https://docs.google.com/drawings/d/1PvJj_8A6oFRdUN9xAgm9Z8joM33Z7CuTJUzCQn3GoCM/edit 20:28:07 I thought someone at HP was going to mock up our sticker stuffs with some tweaks of your own, my b 20:28:18 lol @ "Your load is our job" 20:28:48 Not happening... We aint hookers 20:29:10 Or sewage treatment workers... 20:29:43 Drop your load. 20:29:51 Stop fnaval... just stop 20:29:59 lol 20:30:43 lol 20:30:45 Ok, I think we need to decide on a design and then pick a slogan 20:31:12 is it imperative to have this done today? 20:31:15 I like the Rax design for "D" 20:31:31 #vote Design: A, B, C, RAX-A, RAX-B, RAX-C, D, E, F, G 20:32:03 D 20:32:12 xgerman, we want rax-D in there 20:32:14 #vote A 20:32:18 #startvote Design: A, B, C, RAX-A, RAX-B, RAX-C, D, E, F, G 20:32:19 Unable to parse vote topic and options. 20:32:19 Or is that just "d"? 20:32:22 #startvote 20:32:23 Only the meeting chair may start a vote. 20:32:25 yep, just D 20:32:28 got it 20:32:36 #vote A 20:32:36 D 20:32:39 A 20:32:51 #startvote Which design? A, B, C, RAX-A, RAX-B, RAX-C, D, E, F, G 20:32:51 Only the meeting chair may start a vote. 20:32:59 :P 20:33:08 #startvote Which design? A, B, C, RAX-A, RAX-B, RAX-C, D, E, F, G 20:33:09 Begin voting on: Which design? Valid vote options are A, B, C, RAX-A, RAX-B, RAX-C, D, E, F, G. 20:33:11 Vote using '#vote OPTION'. Only your last vote counts. 20:33:12 Yeah, what he said 20:33:14 #vote d 20:33:19 #vote A 20:33:22 #vote D 20:33:23 #vote D 20:33:24 #vote D 20:33:24 #vote d 20:33:27 #vote D 20:33:34 #vote a 20:33:36 #vote D 20:33:49 i actually prefer A, except for the two-tone. 20:33:51 #vote B 20:33:55 #vote A 20:34:07 #vote D 20:34:14 which is D? 20:34:14 #vote B 20:34:19 Its on our link ptoohill 20:34:22 D is on the RAX sheet 20:34:23 ptoohill: the nice one 20:34:23 oh 20:34:28 #vote D 20:34:28 pff ijw 20:34:50 * ijw is only lurking in the background, really, but I'm trying to save you from yourselves ;) 20:35:05 thanks we need that 20:35:08 ijw 20:35:17 #endvote 20:35:18 Voted on "Which design?" Results are 20:35:19 A (3): johnsom, ajmiller, ptoohill 20:35:20 B (2): xgerman, jwarendt 20:35:20 ijw: lol 20:35:21 D (9): Aish, fnaval, ijw, dougwig, Trevor_V, madhu_ak, bharath, mwang2_, blogan 20:35:31 ok, D it is 20:35:33 Octavia gets the D 20:35:38 Woot 20:35:45 Now time to drop a load 20:35:47 aww missed it 20:35:48 ah well 20:35:50 lol 20:35:51 (damnit fnaval) 20:35:52 Trevor_V: tmi 20:36:05 so do we need a different tagline then "Openstack Loadbalancing" 20:36:05 ?? Trevor_V 20:36:05 it matched too well ijw 20:36:07 nii 20:36:17 I honestly don't think so xgerman 20:36:35 xgerman: i'm worried that if we tag it as openstack that might be a problem, then again it probably wont witht eh big tent approach now 20:36:40 Up to other suggestions for sure 20:37:54 ok, blogan has a valid point 20:38:27 its a low probability chance 20:38:45 i just want to use "Your load, our job" or whatever that was 20:38:52 Stop it blogan 20:38:54 lol 20:40:08 moving on? 20:40:08 yeah i like openstack load balancing 20:40:14 #topic Open Discussion 20:40:15 Balancing at work. 20:40:41 I've been doing bunches of devstack/vagrant stuff for both neutron-lbaas and octavia. Would appreciate reviews on: 20:40:50 #link https://review.openstack.org/173438 20:41:02 #link https://review.openstack.org/175174 20:41:15 possible topic: octavia under mestery's dictatorship (big tent discussion)? 20:41:17 #link https://review.openstack.org/167796 20:41:24 ajmiller i can adjust my vote now ;) 20:41:29 ajmiller: is a pinata of reviews 20:41:39 The first two are for neutron-lbaas and I think are ready for +2/A 20:41:42 blogan: ++, I think that makes sense, see russellb's email about the other networking-foo projects today and my response 20:41:53 The third is octavia. 20:42:20 mestery: i do too, even with you being a ruthless dictator, but i'd like to guage everyone else's ideas 20:42:27 blogan: let's ship some code first. 20:42:34 lol 20:42:40 * mestery makes a note to have blogan walk the plank 20:42:40 nah, let's be like congress 20:42:53 * blogan sinks like a witch 20:43:06 i think projects should be considered "one of us" without having to be in production already, we need to change that outlook 20:43:18 when a project is under development in our community, it's already a part of hte openstack community, IMO 20:43:32 i like that thinking 20:43:32 nicely put russelb 20:43:50 that's how the TC has been looking at projects as of late 20:43:51 hmm, i'd like to see a team gel and prove itself before we rush to inclusiveness. 20:43:59 ok, so move under mestery;s iron fist immediately 20:44:01 russellb: so everything is openstack that is stackforge then? 20:44:09 but i've been wrong plenty of times before. 20:44:12 blogan: most of it, i expect 20:44:24 dougwig: party pooper 20:44:24 ;) 20:44:27 dougwig: yes agree that there should be some level of "yes, this appears to be a real thing" 20:44:56 people seem to care, people are participating 20:44:58 russellb: any discussion on how that will be done? 20:45:01 and they are doing it in the openstack way 20:45:05 blogan: lots of it :) 20:45:20 http://governance.openstack.org/reference/new-projects-requirements.html 20:45:22 russellb: lol i mean any solid solutions? 20:45:29 given this, do folks want to move earlier? is mestery in favor of that? 20:45:31 solid solutions to what 20:45:31 ah thanks 20:45:37 dougwig +1 20:45:52 +2 20:46:00 russellb: to what quality the project has to be in before it can be considered openstack (not just code quality) 20:46:06 i think that link will answer my questiosn though 20:46:13 yeah, it should answer it 20:46:14 hopefully 20:46:28 and then we're defining higher optional bars for project to reach with "tags" 20:46:34 russellb: will the ptl have to lead every meeting and manage the releases for every project under him? 20:46:38 him/her 20:46:55 like, a project *may* be given a tag indicating that its participation has a diverse affiliation -- http://governance.openstack.org/reference/tags/team_diverse-affiliation.html 20:47:01 blogan: they already don't. 20:47:06 +1 20:47:13 we can have a delegate 20:47:31 aka mestery can send an envoy 20:47:40 okay, as long as mestery's soul isn't sucked out of him 20:47:45 lol 20:48:08 russellb: one more question then, what role would the ptl have in these projects then? 20:48:14 mestery absorbs open-source souls into his body, via an expanding empire, i think. 20:48:24 that's project specific 20:48:27 so mestery is the vampire 20:48:31 PTL can be involved or delegate as much as they'd like 20:48:31 That's an image I can't scrub from my eyes now dougwig, thanks. 20:48:54 * russellb hand waves 20:49:07 lol 20:49:08 * blogan noticed 20:49:10 lol 20:49:54 sounds like an agile process 20:50:02 ok, so do we need to vote when to move? 20:50:24 i'd say give people some time to think about it 20:50:41 yeah + the earliest after the demo to minimize distractions 20:50:52 let's let russellb's ML thread play out, too. he can pave the way. :) 20:51:06 * russellb just trying to help 20:51:18 russellb: thanks for answering questions btw 20:51:22 +1 20:51:23 dougwig: really nice comments in gerrit pointing out questions that need to be answered 20:52:04 russellb: there's a spec for this? 20:52:09 russellb: thanks for taking the initiative on this. i like it. 20:52:20 link to the spec please? 20:52:30 dougwig +1 20:53:05 no spec 20:53:09 i started a ML thread that's related 20:53:22 http://lists.openstack.org/pipermail/openstack-dev/2015-April/062310.html 20:53:37 blogan: there was an early gerrit review, since abandoned: https://review.openstack.org/#/c/175952/3 20:53:45 the ML is where it's at now. 20:53:52 yeah, my gerrit reviews were a little ahead of the bigger question 20:53:58 so i dropped them for now 20:54:16 dougwig, russellb: alright thanks! 20:54:46 ok, 6 minutes left - anything else? 20:55:15 code review needed for tempest 20:55:20 #link https://review.openstack.org/#/c/173542/ 20:55:40 would like to clarify the lb_network_name that is currently in the config 20:55:50 same here as well. #link: https://review.openstack.org/#/c/171832/ 20:56:10 thanks blogan 20:56:15 This question kinda ties in with Al's debstack plugin review and amp_network_list. But suppose we can talk about this later 20:56:17 ptoohill I put that in because for network)id you need some extension HP didn't have 20:56:18 ptoohill I think that is going away as I added a controller config for that 20:56:26 it was just bad timing 20:56:41 so that option should live in the controller_worker group? 20:56:43 as a list? 20:56:46 blogan: you're quite welcome, thanks for letting me drop in :) 20:57:17 ptoohill yep 20:57:24 [controller_worker] 20:57:24 amp_network_list = 62a63520-7bf1-47e0-b90d-5918d4dc45d4 20:57:47 yea, i seen that and was just curious. Then we should remove the option under networking group 20:57:48 johnsom: is that the management network? 20:57:55 this works for me, i was just confused 20:57:58 Yes 20:58:10 okay, amp_network is probably a better name 20:58:27 and i believe itll need to be updated in the compute worker also 20:58:45 russellb: like dougwig said, thanks for leading the effort 20:59:26 being thats a list im sure we need to define logic on which one to use from the list? 20:59:33 all 20:59:34 all? 20:59:38 i would assume all 20:59:52 or select at random 20:59:53 thats works also 20:59:56 I welcome comments on the ocde 21:00:10 we 21:00:12 right now all is a good bet, random would cause issues later 21:00:13 we're past time 21:00:23 stop ruining meeting time! 21:00:23 #endmeeting