16:00:03 #startmeeting neutron lbaas 16:00:04 Meeting started Tue Dec 2 16:00:03 2014 UTC and is due to finish in 60 minutes. The chair is dougwig. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:07 The meeting name has been set to 'neutron_lbaas' 16:00:11 #topic Roll call and Agenda and general waking up... 16:00:21 o/ 16:00:22 here 16:00:24 o/ 16:00:24 agenda: 16:00:26 #link https://wiki.openstack.org/wiki/Network/LBaaS#Meeting_02.12.2014 16:00:34 Morning! 16:00:37 o/ 16:00:42 anyhting form the Neutron meeting I tend to skip? 16:00:49 \o/ 16:00:53 yep, but that's later in the agenda. 16:01:01 suspensew 16:01:47 Hi 16:01:52 o/ 16:01:57 #topic Announcements 16:02:05 Review of the week: 16:02:07 #link https://review.openstack.org/#/c/123487/ 16:02:17 that's the first half of the agent-less ref driver. needs eyes. 16:02:26 any other announcements from anyone? 16:02:38 needs to rerun the testst oo 16:02:40 too 16:02:51 jenkins was unhappy last night 16:02:57 is it recheck or recheck no bug? 16:03:01 recheck 16:03:01 used to be recheck no bug 16:03:04 ajmiller discovered that one of the Neutron changes broke our migrations 16:03:06 they changed it 16:03:29 you can check status.openstack.org/zuul to see if it re-queues. 16:03:34 #topic Flavors 16:03:40 #link https://review.openstack.org/#/c/102723 16:03:53 the spec has been resurrected. whether it is undead or reanimated remains to be seen. 16:04:05 lol 16:04:07 spec approval deadline is 12/14, so please weigh in with feedback. 16:04:34 any flavors questions/comments/feedback now? 16:04:56 need to refresh my memory 16:05:10 same here 16:05:12 ok, i'll ping again next week. 16:05:27 #topic Advanced services split discussion 16:05:32 #link https://review.openstack.org/#/c/136835/ 16:05:37 Some discussion at the neutron meeting this morning, at timestamp 14:26:13 16:05:41 #link http://eavesdrop.openstack.org/meetings/networking/2014/networking.2014-12-02-14.01.log.html 16:06:10 current spec creates four teams (neutron, lbaas, fwaas, vpnaas), and current decision is to share the neutron database with separate tables/migration chains. 16:06:31 we need that spec to solidify this week if we're going to get it in early in the cycle. 16:06:45 sounds ambitious given all the comments 16:07:03 Doug is doing a good job of addressing what he can in the comments. 16:07:12 yes he is 16:07:27 +100 16:07:28 But yes, there are probably a few things that others in the group are simply not going to agree on. 16:07:29 i think the extensions decision and the same db will speed up the acceptance though 16:07:43 I guess we'll see how willing people are to compromise. 16:08:11 Yeah, there are a lot of trade-offs which are being made in the interest in speeding up acceptance. 16:08:22 indeed. 16:08:47 Even if we can't come to terms on the governance issue, having a technical plan to get split repositories is a step in the right direction, IMO. 16:09:10 did governace get even discussed today? 16:09:26 I think we are doing a good job dancing around that :-) 16:09:29 governance is pretty simple, actually. either we're in the networking program, and it's up to mestery, or we go to stackforge, with all that entails. both are viable options. 16:09:42 ++ 16:09:48 Oh hey! 16:10:05 I won't call you the devil this time. ;) 16:10:22 (You know, speak of the devil...) 16:10:47 Sorry, it's early and my brain is trying hard to humor. 16:10:49 if we're insulting kyle, we say kyle, not mestery, so his irc client doesn't light up. 16:11:03 lol 16:11:04 i think there's a gerrit spec about that somewhere. 16:11:12 lol 16:11:12 Ha! 16:11:32 alright, any split comments/feedback/questions? meeting slots on this topic have been pretty quiet, which is either awesome or worrisome. 16:11:46 we just want it done -) 16:11:52 Actually, I feel like we're in a pretty good place with that spec... 16:11:56 im just interested in getting progress done, path of least resistance at this point 16:11:57 +1 on done 16:11:58 Let's push hard for consensus. 16:12:49 I don't think there is much we can do except +1 16:13:10 i can +1000 16:13:15 ok, then please leave some comments or whatnot on the gerrit spec, and let's get this rolling. it'll get an update this morning for the decisions from today's neutron meeting. 16:13:25 +1000 16:13:30 mestery: I would like to attend the neutron meetup remote. Anything around taht yet? 16:13:35 i'll post in channel when it's ready for action again. 16:13:56 sballe: he mentioned in the meeting this morning that he's working on it. see the beginning of that chat log, in announcements. 16:13:58 sballe: +1 16:13:59 sballe: We will have remote participation, the plan for people coding is to have an etherpad where people can pick items, and we'll be in-channel on #openstack-neutron 16:14:03 I'll see about Hangouts as well 16:14:10 Though that depends on what Adobe can offer there too :) 16:14:28 they can't photoshop everyone in? 16:14:31 i can offer a webex if it helps. 16:14:31 dougwig: I know I was there. I just wanted mestery to know that I am interested in attendign even thought I didn;t put my name onthe wiki 16:14:43 blogan: +1 16:14:47 sballe: Got it 16:14:52 blogan: lol 16:15:06 #topic Open discussion 16:15:09 I wonder - if vendor code is pushed out of neutron, will the *aas repos include vendor code? 16:15:30 kobis: it will icnlude the vendor drivers 16:15:32 kobis: that is mentioned in the spec. yes, because we're still trying to grow community 16:15:35 kobis: Yes, according to the latest spec. 16:15:47 Heh! 16:15:48 ok 10x 16:15:54 yep, we also said so at the summit 16:16:04 i would expect the long-term to look similar to neutron, though. 16:16:10 me, too 16:16:35 any other topics for today? 16:16:37 yes 16:16:42 neutron lbaas meetup 16:16:50 #topic neutron lbaas meetup 16:16:52 go 16:17:49 blogan? 16:17:56 does everyone feel it is worth having it separate from an octavia meetup? I'm sure we want octavia to focus on octavia, but just getting everyone's thoughts 16:18:11 no, we should combine 16:18:18 dougwig - time for #vote 16:18:30 well we need to get everyone's thoughts on it first 16:18:46 What do we hope to accomplish at the neutron LBaaS meetup? 16:18:48 if we combine will we have another face 2 face in January? LBaaS/Octavia? 16:18:48 neutron lbaas this time aroudn will have a lot to do, especially with the split 16:18:58 i think there's quite a bit of v2 work left, and having folks in the same room, with enough cores to make a difference, would help a lot. 16:19:12 Ok. 16:19:14 plus, it needs to be later than december, to give the split time to settle 16:19:15 I agree 16:19:17 i agree with that 16:19:33 IMO 16:19:34 I'm in favor having it separate 16:19:42 Given those requirements. 16:19:45 however, i worry that having another meetup may cause a low attendance outcome 16:19:50 Or objectives, rather. 16:19:57 blogan +10 16:20:20 Well, we likely won't get a second Octavia face to face this cycle then. 16:20:23 i wouldn't object to an octavia/lbaas meetup in late january. the holidays and the split is just making the december meetup tough. 16:20:25 also there is the advanced services meetup 16:20:25 and markmcclain will be at the Octavia one. We could use him to do some +2 on LBaaS stuff 16:20:39 As long as people are OK with some folks working on Octavia stuff at the Neutron LBaaS meetup, I'm OK with that. 16:20:45 it'd need the full 5 days, and we'd want to schedule some of those days for lbaas only, and some for octavia only, IMO. 16:21:00 xgerman: im not sure there will be one now, though I am not sure 16:21:12 sbalukoff: as long as octavia doesn't prevent v2 from making progress, they're the same teams. 16:21:20 True 16:21:21 dougwig: +1 16:21:23 ok, with the family I am waty to be gone two weeks in January 16:21:39 Folks: Any reason not to just have a single meetup for lbaas in december? Why are two needed? 16:21:44 * mestery goes back to lurking 16:21:44 Let's have our employers rent out a conference center for the whole month of January and meet there and work on both. 16:21:45 ;) 16:21:58 sbalukoff: +1 16:22:00 mestery: the main reason is there is a lot to do on both fronts 16:22:10 Yep. 16:22:13 sbalukoff: thinks this is a good idea. not distractions or meetings 16:22:23 mestery: because the current december date is holidays for many (me!), and the split won't be done yet. 16:22:33 Ah, got it dougwig and blogan. Just curious 16:22:34 sballe: Unfortunately totally impractical. ;) 16:22:51 sbalukoff I know 16:22:55 well rackspace can host this meeting if it is determined we want it 16:22:56 mestery: curiosity will be punished. 16:23:02 I'm on the road nearly all of January… so I won't be able to attend either in person/remote 16:23:03 lol 16:23:11 blogan; I'm pretty sure we want it. 16:23:18 Also, Texas is nice in January. 16:23:31 so is Seattle :-) 16:23:43 or Boise :-) 16:23:45 xgerman: In January? 16:23:48 seattle is cold and possibly snowy in January :P 16:23:49 is it worth having without mestery and markmcclain there? if we can't get fast +2 eyes? 16:23:55 how about Boston ;-) 16:23:57 yep, we can go to the slopes and ski 16:24:09 blogan: By then LBaaS will be it's own repo with at least you and dougwig as +2 :) 16:24:09 Haha! 16:24:12 but if I need to stay in WA longer let me know so I can cancel my return flight :) 16:24:28 mestery: That's very optimistic of you. ;) 16:24:34 rm_work just move there and start RAX west 16:24:37 mestery: good point, that totally escaped me 16:24:46 lol 16:24:55 xgerman: RAX West is called the SFO office :) 16:25:17 … which would be awesome to work out of, I think 16:25:22 okay so are we in agreement that we want one in January? 16:25:30 alright, where's consensus at on this point? merged or separate? 16:25:31 ha, jinx 16:25:37 or shoudl we aim for later in case the plit gets dealyes... 16:25:47 later would be nearing the end of kilo 16:26:06 but we could make the last big push 16:26:18 * dougwig would prefer some soak time. 16:26:51 but if we have specs approved and mestery and markmcclain are okay with some exceptions to a late spec, then I'd be fine with later 16:26:53 i'd think the last push should be for making octavia 1.0 be the ref. IMO. 16:27:11 which implies we need v2 solid earlier. 16:27:19 yep 16:27:38 oh god, 1.0 by Kilo *and* made the ref for n-lb? 16:27:39 >_> 16:27:44 that might too ambitious. :) 16:27:53 but you've gotta have goals. 16:28:00 Heh! 16:28:04 couldn't 0.5 be the ref impl? 16:28:06 honestly not sure what I think of Octavia being the ref driver for n-lb still... 16:28:09 adn then it gets upgraded to 1.0 16:28:10 Big Hairy Audacious Goals? 16:28:13 blogan: i thought 0.5 wasn't scalable? 16:28:20 its not 16:28:29 depends on the hardware 16:28:38 I like the idea of the "reference" driver being something SIMPLE so it can be easily updated when the API changes 16:28:46 better or worse than the agent-ified haproxy namespace driver? 16:28:49 Also, Neutron LBaaS v1 reference is not scalable. 16:28:54 Octavia seems a bit complex (and out of tree) 16:29:05 sbalukoff: it is 16:29:09 it's scalable with the agent on other machines. just not pleasantly. 16:29:11 let's not get too far off topic 16:29:25 IMO leave the namespace driver as the ref <_< 16:29:29 thank you, back to topic. 16:29:38 well thats antoehr discussion at a later time 16:29:43 back to meetup 16:29:47 what's the vote syntax? 16:29:59 #startvote 16:30:00 Only the meeting chair may start a vote. 16:30:06 well, we should find out if the adv services meetup is happening 16:30:20 I mean, what are we voting on? 16:30:29 .#startvote question? Yes No Maybe 16:30:33 Just "Yes/No" to "have two meetings"? 16:30:35 xgerman: im almost certain that was going to happen with adv svc was spinning out as one 16:30:40 i was just going to take the temperature of the room. 16:30:48 or something more specific 16:31:17 #startvote Are you ok with two meetups? Yes No Maybe 16:31:18 ok, and that was split related also -- so we will have two split related meetups in jan 16:31:18 Begin voting on: Are you ok with two meetups? Valid vote options are Yes, No, Maybe. 16:31:19 Vote using '#vote OPTION'. Only your last vote counts. 16:31:24 #vote Yes 16:31:25 #vote Yes 16:31:29 i am a LITTLE worried about making everyone travel so often 16:31:35 auto-correct changed meetups to metopes. that is some high end dictionary action. 16:31:38 #vote Maybe 16:31:44 #vote yes 16:31:44 #vote Maybe 16:31:45 #vote yes 16:31:49 #vote maybe 16:31:54 #vote Maybe 16:32:06 switzerland 16:32:12 #vote maybe 16:32:22 good heavens, commit people. :) 16:32:26 #endvote 16:32:26 "If I don't make it, tell my wife I said -- Hello." 16:32:27 Voted on "Are you ok with two meetups?" Results are 16:32:28 Maybe (5): xgerman, rm_work, ptoohill, johnsom, TrevorV 16:32:29 Yes (4): dougwig, sballe, sbalukoff, blogan 16:33:08 blogan: this is your topic. did you get what you needed? 16:33:20 well if that vote is a binding contract 16:33:24 rm_work: Those who don't want to / can't travel can always attend remotely. 16:33:28 which i dont think it is 16:33:33 it is not 16:33:37 https://www.youtube.com/watch?v=ussCHoQttyQ https://www.youtube.com/watch?v=fpaQpyU_QiM 16:33:40 i guess if its here im fine with it. anywhere else we cant go. and on that note im interested how the remote aspect for the upcoming meetup is going to work 16:33:43 so if we had it in January 16:33:58 does the week of the 19th work for people? 16:34:03 I'm OK with having it in Texas. 16:34:13 blogan: AFAIK, yes. 16:34:27 sballe is checking her calendar 16:35:01 Can we have it in Austin if it is Texas? 16:35:21 I would love to have it in Austin 16:35:27 heh, yeah, me too 16:35:31 sballe: is HP volunteering space in Austin? 16:35:40 I think I would only be able to make the first three days the week of the 19th 16:35:46 though we'd have to start later so we have time to take the shuttle in the morning from SA :P 16:35:47 we have space everywhere :-) 16:35:55 EVERYWHERE 16:36:01 rm_work: or we could carpool together :) 16:36:04 I know RAX has space in Auston too. But HP we have space too 16:36:05 can it be a week long replay of the hp paris party? 16:36:07 monday the 19th is MLK day, fyi. 16:36:07 I'm not gonna lie, I'm probably not going to travel to Austin daily for that. 16:36:12 jorgem: gah 16:36:21 Oh... 16:36:30 Yeah, let's avoid the week of the 19th then. 16:36:33 meetup proposal is 20-22, i think. 16:36:43 well what about just start on Tuesday the 20th 16:36:51 I think that week is anyway pretty close to the other meetup 16:36:52 I would do anything to get out of SA daily 16:37:06 Have it be a 3-day thing? 16:37:10 blogan then you only get 4 days 16:37:10 That works. 16:37:16 I can't attend the 23rd either. 16:37:49 so 36-39 would be better for sbalukoff 16:37:54 most meetups are only 3 days anyway, so people dont ahve to travel on weekends 16:37:55 23-29 16:37:56 xgerman: Which other meetup? 16:38:03 adv services 16:38:06 Aah. 16:38:10 xgerman: i dont think they're having one 16:38:26 I thought you said they would 16:38:37 when we were going to split out as one yes, but now we're not 16:38:52 If the split entails 4 different repositories, the need for an advanced services meetup starts to make less sense. 16:38:53 I am not available 26-30 I will be in Sunnyvale and Seattle 16:38:58 that message should be talked about a bit louder 16:39:18 sbalukoff: indeed 16:39:54 if the toher advanced services want to have a meetup, then they may choose that 16:39:55 let's go for some closure here. if we don't have consensus on good timing/location here, let's fire up an etherpad. 16:40:06 dougwig +1 16:40:12 dougwig +1 16:40:13 =1 16:40:16 +1 16:40:54 ill fire one up 16:41:04 #action blogan setup lbaas meetup etherpad 16:41:13 thank you 16:41:14 #topic Open discussion 16:41:18 Sweet. 16:41:19 other topics? 16:41:22 sure 16:41:41 just a PSA we founbd that one of the lastest Neutron topics breaks our feature branch 16:41:59 do we need to fix a merge conflict? 16:42:07 or is it a functional break? 16:42:07 There is a problem when upgrading the neutron database. 16:42:18 I am working on suggesting a patch. 16:42:34 do we just need another merge from master? 16:42:44 what is the break? 16:42:45 if so, mestery needs to submit it. 16:43:12 Merge from master would probably fix it. There has been a database upgrade on master, and that breaks the neutron upgrade. 16:43:41 is it just bc another db migration came in? 16:43:46 yep 16:43:47 blogan yes 16:44:09 oh okay well thats expected, if its just an alembic sequence issue 16:44:17 yes 16:44:19 im not sure if thats something we always want to merge master for 16:44:21 ok, i'll ask for another merge. i found out the hard way last time that only someone in the neutron release group can submit the patch. 16:44:48 Eew. 16:44:49 if we merge master for every new migration, thats a lot of contacting neutron release group to merge 16:45:04 well, once the split happends 16:45:08 ... 16:45:09 is the feature branch broken, or just swapping between feature and master on the same install? 16:45:14 There is that. 16:45:22 because if it's the latter, i agree with blogan. wipe and reset 16:45:24 yeah so why dont we wait until the split is ready, then do one merge 16:45:40 +1 16:46:26 But inquisitive minds want to try out LbaaS v2 16:46:30 ... 16:46:31 the feature branch should still work on its own 16:47:14 hopefully inquisitive minds can do a git checkout feature/lbaasv2 and restart? 16:47:25 unless they need some features that are in master as well 16:47:45 xgerman: use neutron-db-manage to rollback to feature back alembic and then go forward. 16:47:51 /back/branch 16:47:58 i can add instructions for that to the devstack wiki 16:48:00 oh yeah that too 16:48:04 lol 16:48:15 well, so we decided to not track master with our feature branch? 16:48:27 Just making sure we are on the same page 16:48:46 xgerman: i think waiting until the split to do one final merge is the best option 16:48:49 I am ok with that -- I just like it spelled out 16:49:11 when the branch was created, folks wanted to minimize the number of master merges. if there's something broken between them (which happened with jenkins jobs once), we merge. if it's just diverging migrations, we'll reset the chain for the final merge. 16:49:31 that was our earlier plan, at least. 16:50:34 any other issues there, or any other topics for today? 16:50:45 I am good -- 16:51:14 alright, thanks folks, and goodbye 16:51:21 o/ 16:51:22 adios 16:51:25 bye 16:51:29 o/ 16:51:34 #endmeeting