Thursday, 2014-09-04

*** vishy has quit IRC00:02
*** vishy has joined #openstack-meeting-300:05
*** emagana has joined #openstack-meeting-300:07
*** yamamoto_ has joined #openstack-meeting-300:07
*** flaper87 is now known as flaper87|afk00:08
*** tgraf has joined #openstack-meeting-300:08
*** glebo has joined #openstack-meeting-300:09
*** devananda has joined #openstack-meeting-300:11
*** emagana_ has quit IRC00:12
*** yamamoto has quit IRC00:12
*** ekarlso has quit IRC00:12
*** dhellmann_ has quit IRC00:12
*** devanand1 has quit IRC00:12
*** eguz has joined #openstack-meeting-300:12
*** eguz has quit IRC00:12
*** ekarlso- has joined #openstack-meeting-300:12
*** dhellmann has joined #openstack-meeting-300:12
*** glebo has quit IRC00:12
*** eghobo has quit IRC00:16
*** emagana has quit IRC00:16
*** emagana has joined #openstack-meeting-300:16
*** emagana has quit IRC00:21
*** SumitNaiksatam has joined #openstack-meeting-300:21
*** otherwiseguy has quit IRC00:23
*** hurgleburgler has quit IRC00:28
*** yamahata has joined #openstack-meeting-300:33
*** SumitNaiksatam has quit IRC00:33
*** lcheng_ has joined #openstack-meeting-300:37
*** pettori has joined #openstack-meeting-300:38
*** yamahata has quit IRC00:39
*** yamahata has joined #openstack-meeting-300:39
*** SumitNaiksatam has joined #openstack-meeting-300:51
*** cjellick has quit IRC00:52
*** cjellick has joined #openstack-meeting-300:53
*** eghobo has joined #openstack-meeting-300:54
*** eghobo has quit IRC00:55
*** eghobo has joined #openstack-meeting-300:55
*** eghobo has quit IRC00:56
*** cjellick has quit IRC00:57
*** pettori has left #openstack-meeting-301:06
*** alexsyip has quit IRC01:09
*** stanzgy has joined #openstack-meeting-301:17
*** baohua has joined #openstack-meeting-301:42
*** yamamoto_ has quit IRC01:51
*** HenryG has quit IRC01:51
*** dkehnx1 has joined #openstack-meeting-302:06
*** prasoon has joined #openstack-meeting-302:25
*** prasoon has quit IRC02:30
*** yamamoto_ has joined #openstack-meeting-302:32
*** lcheng_ has quit IRC02:35
*** dougwig has quit IRC02:36
*** dougwig_ has joined #openstack-meeting-302:39
*** HenryG has joined #openstack-meeting-302:40
*** banix has quit IRC02:41
*** david-lyle has joined #openstack-meeting-302:59
*** mitarun has joined #openstack-meeting-303:01
*** prasoon has joined #openstack-meeting-303:20
*** vkmc has quit IRC03:23
*** ivar-lazzaro1 has quit IRC03:23
*** mitarun has left #openstack-meeting-303:27
*** david-lyle has quit IRC03:44
*** tomoe_ has joined #openstack-meeting-303:45
*** prasoon_ has joined #openstack-meeting-303:49
*** prasoon has quit IRC03:49
*** eghobo has joined #openstack-meeting-304:02
*** mitarun has joined #openstack-meeting-304:12
*** mitarun has quit IRC04:17
*** mitarun has joined #openstack-meeting-304:53
*** nelsnelson has quit IRC05:04
*** lcheng_ has joined #openstack-meeting-305:39
*** Longgeek has joined #openstack-meeting-305:44
*** mitarun has quit IRC05:49
*** mitarun has joined #openstack-meeting-305:50
*** mitarun has quit IRC05:50
*** mitarun has joined #openstack-meeting-305:50
*** yisun has joined #openstack-meeting-305:50
*** tmazur has joined #openstack-meeting-305:57
*** mrunge has joined #openstack-meeting-306:01
*** yisun has quit IRC06:09
*** pkoniszewski has joined #openstack-meeting-306:09
*** emagana has joined #openstack-meeting-306:12
*** Longgeek has quit IRC06:12
*** emagana has quit IRC06:12
*** flaper87|afk is now known as flaper8706:12
*** Longgeek has joined #openstack-meeting-306:18
*** seizadi has joined #openstack-meeting-306:19
*** yamamoto_ has quit IRC06:21
*** Longgeek_ has joined #openstack-meeting-306:21
*** Longgeek_ has quit IRC06:22
*** Longgeek_ has joined #openstack-meeting-306:23
*** Longgeek has quit IRC06:24
*** Longgeek has joined #openstack-meeting-306:24
*** Youcef has joined #openstack-meeting-306:25
*** amotoki has joined #openstack-meeting-306:25
*** Longgeek_ has quit IRC06:26
*** shwetaap has quit IRC06:27
*** seizadi1 has joined #openstack-meeting-306:34
*** seizadi has quit IRC06:34
*** seizadi1 has quit IRC06:35
*** marun_ has joined #openstack-meeting-306:49
*** yamamoto_ has joined #openstack-meeting-306:55
*** sunrenjie6 has joined #openstack-meeting-307:01
*** flaviof_zzz has quit IRC07:03
*** sarob has quit IRC07:03
*** wendar has quit IRC07:04
*** wendar_ has joined #openstack-meeting-307:04
*** sunrenjie6 has quit IRC07:05
*** eghobo has quit IRC07:06
*** sunrenjie6 has joined #openstack-meeting-307:07
*** lcheng_ has quit IRC07:08
*** yamamoto_ has quit IRC07:10
*** sunrenjie6 has quit IRC07:11
*** sunrenjie6 has joined #openstack-meeting-307:14
*** sunrenjie6 has quit IRC07:19
*** Longgeek has quit IRC07:20
*** Longgeek has joined #openstack-meeting-307:21
*** jcoufal has joined #openstack-meeting-307:21
*** Longgeek_ has joined #openstack-meeting-307:26
*** Longgeek_ has quit IRC07:27
*** sarob has joined #openstack-meeting-307:27
*** Longgeek_ has joined #openstack-meeting-307:27
*** flaviof_zzz has joined #openstack-meeting-307:28
*** itzikb has joined #openstack-meeting-307:28
*** Longgeek has quit IRC07:29
*** mitarun has quit IRC07:30
*** mitarun has joined #openstack-meeting-307:31
*** sunrenjie6 has joined #openstack-meeting-307:32
*** pkoniszewski has quit IRC07:33
*** Longgeek has joined #openstack-meeting-307:33
*** pkoniszewski has joined #openstack-meeting-307:33
*** mitarun has quit IRC07:36
*** sunrenjie6 has quit IRC07:36
*** Longgeek_ has quit IRC07:36
*** Longgeek has quit IRC07:37
*** Longgeek has joined #openstack-meeting-307:38
*** bauzas has quit IRC07:39
*** prasoon has joined #openstack-meeting-307:49
*** prasoon_ has quit IRC07:50
*** Guest60909 is now known as Adri200007:50
*** Adri2000 has joined #openstack-meeting-307:50
*** yamamoto_ has joined #openstack-meeting-307:54
*** prasoon has quit IRC07:54
*** prasoon has joined #openstack-meeting-307:55
*** yamamoto_ has quit IRC07:58
*** yamamoto_ has joined #openstack-meeting-307:59
*** yamamoto_ has quit IRC08:01
*** bauzas has joined #openstack-meeting-308:04
*** pkoniszewski has quit IRC08:05
*** pkoniszewski has joined #openstack-meeting-308:06
*** iovadia has joined #openstack-meeting-308:06
*** mrunge has quit IRC08:10
*** mrunge_ has joined #openstack-meeting-308:10
*** mrunge_ is now known as mrunge08:10
*** beagles has quit IRC08:13
*** safchain has joined #openstack-meeting-308:13
*** prasoon has quit IRC08:31
*** beagles has joined #openstack-meeting-308:31
*** beagles is now known as Guest5365108:31
*** mitarun has joined #openstack-meeting-308:31
*** prasoon has joined #openstack-meeting-308:32
*** mitarun has quit IRC08:36
*** MaxV has joined #openstack-meeting-308:37
*** prasoon has quit IRC08:45
*** prasoon has joined #openstack-meeting-308:45
*** yamamoto_ has joined #openstack-meeting-308:46
*** mitarun has joined #openstack-meeting-308:50
*** yamamoto_ has quit IRC08:50
*** yamamoto_ has joined #openstack-meeting-308:54
*** yamamoto_ has quit IRC08:59
*** jpomero has quit IRC09:03
*** jpomero has joined #openstack-meeting-309:03
*** m1dev has quit IRC09:04
*** m1dev has joined #openstack-meeting-309:04
*** sankarshan is now known as sankarshan_away09:05
*** Longgeek_ has joined #openstack-meeting-309:13
*** MaxV has quit IRC09:14
*** MaxV has joined #openstack-meeting-309:14
*** Longgeek has quit IRC09:15
*** Longgeek_ has quit IRC09:17
*** Longgeek has joined #openstack-meeting-309:18
*** mrunge has quit IRC09:24
*** mrunge has joined #openstack-meeting-309:27
*** mitarun has quit IRC09:28
*** yamamoto_ has joined #openstack-meeting-309:30
*** mitarun has joined #openstack-meeting-309:34
*** yamamoto_ has quit IRC09:34
*** itzikb has quit IRC09:38
*** Longgeek_ has joined #openstack-meeting-309:43
*** Longgeek has quit IRC09:46
*** baohua has quit IRC09:53
*** yamamoto_ has joined #openstack-meeting-309:54
*** yamamoto_ has quit IRC09:59
*** tmazur has quit IRC09:59
*** Adri2000 has quit IRC10:05
*** Adri2000 has joined #openstack-meeting-310:05
*** itzikb has joined #openstack-meeting-310:06
*** Adri2000 is now known as Guest7150310:06
*** MaxV has quit IRC10:13
*** yamahata has quit IRC10:16
*** tmazur has joined #openstack-meeting-310:19
*** mitarun has quit IRC10:19
*** mitarun has joined #openstack-meeting-310:20
*** mitarun has quit IRC10:25
*** tmazur has quit IRC10:31
*** k4n0_ has quit IRC10:33
*** prasoon has quit IRC10:34
*** k4n0 has joined #openstack-meeting-310:35
*** tmazur has joined #openstack-meeting-310:51
*** Guest71503 is now known as Adri2000_10:51
*** Adri2000_ has joined #openstack-meeting-310:51
*** tmazur has quit IRC10:53
*** yamamoto_ has joined #openstack-meeting-310:54
*** yamamoto_ has quit IRC10:59
*** jab has joined #openstack-meeting-311:18
*** jab has quit IRC11:18
*** jab has joined #openstack-meeting-311:18
*** MaxV has joined #openstack-meeting-311:19
*** jab is now known as bradjones11:21
*** banix has joined #openstack-meeting-311:28
*** banix has quit IRC11:32
*** lblanchard has joined #openstack-meeting-311:37
*** mwagner_lap has quit IRC11:40
*** MaxV has quit IRC11:45
*** sandr8_ has joined #openstack-meeting-311:46
*** MaxV has joined #openstack-meeting-311:47
*** vkmc has joined #openstack-meeting-311:47
*** vkmc has quit IRC11:47
*** vkmc has joined #openstack-meeting-311:47
*** alaski_ has joined #openstack-meeting-311:50
*** sandr8 has quit IRC11:51
*** alaski has quit IRC11:51
*** MaxV has quit IRC11:51
*** MaxV has joined #openstack-meeting-311:51
*** yamamoto has joined #openstack-meeting-311:54
*** yamamoto has quit IRC11:59
*** mwagner_lap has joined #openstack-meeting-312:01
*** prasoon has joined #openstack-meeting-312:06
*** flaper87 is now known as echo12:11
*** echo is now known as flaper8712:11
*** Guest53651 is now known as beagles12:12
*** yamamoto has joined #openstack-meeting-312:22
*** iovadia has left #openstack-meeting-312:25
*** Adri2000_ is now known as Adri200012:33
*** igordcard has joined #openstack-meeting-312:37
*** dosaboy_ is now known as dosaboy12:38
*** flaper87 is now known as flaper87|afk12:40
*** flaper87|afk is now known as flaper8712:42
*** flaviof_zzz is now known as flaviof12:47
*** stanzgy has quit IRC12:53
*** lcheng_ has joined #openstack-meeting-312:54
*** lcheng_ has quit IRC12:54
*** baohua has joined #openstack-meeting-312:54
*** baohua has quit IRC12:57
*** yamahata has joined #openstack-meeting-312:58
*** baohua has joined #openstack-meeting-312:59
*** marun_ has quit IRC13:07
*** jcoufal has quit IRC13:08
*** banix has joined #openstack-meeting-313:08
*** enykeev has quit IRC13:09
*** jcoufal has joined #openstack-meeting-313:11
*** k4n0 has quit IRC13:12
*** sankarshan_away is now known as sankarshan13:12
*** mitarun has joined #openstack-meeting-313:13
*** mestery has quit IRC13:17
*** mestery has joined #openstack-meeting-313:21
*** mestery has quit IRC13:21
*** mestery has joined #openstack-meeting-313:22
*** shwetaap has joined #openstack-meeting-313:25
*** marun_ has joined #openstack-meeting-313:25
*** julim has joined #openstack-meeting-313:27
*** peristeri has joined #openstack-meeting-313:31
*** amotoki_ has joined #openstack-meeting-313:35
*** shwetaap has quit IRC13:36
*** shwetaap has joined #openstack-meeting-313:37
*** thomasem has joined #openstack-meeting-313:38
*** thangp has joined #openstack-meeting-313:44
*** alexpilotti has joined #openstack-meeting-313:48
*** dougwig_ is now known as dougwig14:00
*** yamahata has quit IRC14:02
*** yamahata has joined #openstack-meeting-314:02
*** nelsnelson has joined #openstack-meeting-314:04
*** jpomero_ has joined #openstack-meeting-314:05
*** yamamoto_ has joined #openstack-meeting-314:07
*** garyduan has joined #openstack-meeting-314:07
*** markmcclain has joined #openstack-meeting-314:10
*** pkoniszewski has quit IRC14:14
*** MaxV_ has joined #openstack-meeting-314:14
*** mfer has joined #openstack-meeting-314:15
*** yamahata has quit IRC14:17
*** yamamoto has quit IRC14:17
*** jpomero has quit IRC14:17
*** dkehnx1 has quit IRC14:17
*** ekarlso- has quit IRC14:17
*** lsmola has quit IRC14:17
*** gduan has quit IRC14:17
*** leifz has quit IRC14:17
*** MaxV has quit IRC14:17
*** yamahata has joined #openstack-meeting-314:20
*** otherwiseguy has joined #openstack-meeting-314:21
*** dkehnx1 has joined #openstack-meeting-314:21
*** ekarlso- has joined #openstack-meeting-314:23
*** lsmola has joined #openstack-meeting-314:24
*** zz_jgrimm is now known as jgrimm14:25
*** ajo is now known as ajo|call14:28
*** david-lyle has joined #openstack-meeting-314:31
*** mitarun has quit IRC14:32
*** iovadia1 has joined #openstack-meeting-314:32
*** mitarun has joined #openstack-meeting-314:32
*** lsmola is now known as 18VAAT2X414:33
*** iovadia1 has left #openstack-meeting-314:33
*** dkehnx1 is now known as 6A4AAKD1O14:33
*** 17SAA4MFR has joined #openstack-meeting-314:33
*** yamamoto has joined #openstack-meeting-314:33
*** jpomero has joined #openstack-meeting-314:33
*** dkehnx1 has joined #openstack-meeting-314:33
*** 17SAA4BEV has joined #openstack-meeting-314:33
*** lsmola has joined #openstack-meeting-314:33
*** gduan has joined #openstack-meeting-314:33
*** 17SAA4BEV has quit IRC14:33
*** leifz has joined #openstack-meeting-314:33
*** 17SAA4MFR has quit IRC14:33
*** yamamoto has quit IRC14:33
*** jpomero has quit IRC14:33
*** dkehnx1 has quit IRC14:33
*** lsmola has quit IRC14:34
*** gduan has quit IRC14:34
*** jaypipes has joined #openstack-meeting-314:34
*** 6A4AAKD1O is now known as dkehnx114:35
*** mitarun_ has joined #openstack-meeting-314:35
*** hurgleburgler has joined #openstack-meeting-314:36
*** mitarun has quit IRC14:37
*** mitarun_ has quit IRC14:40
*** mitarun has joined #openstack-meeting-314:45
*** gholler has joined #openstack-meeting-314:45
*** igordcard has quit IRC14:50
*** carl_baldwin has joined #openstack-meeting-314:50
*** baohua has quit IRC14:56
*** mfer has quit IRC15:00
*** pcm_ has joined #openstack-meeting-315:00
*** mrsmith has joined #openstack-meeting-315:00
*** mfer has joined #openstack-meeting-315:00
carl_baldwinhi all.  L3 meeting.15:00
pcm_hi15:00
carl_baldwinpcm_: hi15:01
yamamoto_hi15:01
*** jcoufal has quit IRC15:01
carl_baldwinyamamoto_: hi15:01
carl_baldwin#startmeeting neutron_l315:01
openstackMeeting started Thu Sep  4 15:01:36 2014 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:01
carl_baldwin#topic Announcements15:01
openstackThe meeting name has been set to 'neutron_l3'15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
*** amuller has joined #openstack-meeting-315:01
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:01
*** seizadi has joined #openstack-meeting-315:02
carl_baldwinI’d like a short meeting today.15:02
carl_baldwinJuno-3 should be available today.  I know the cut-offs are always difficult.15:02
carl_baldwinI did not get a chance to update the agenda on the wiki.  I don’t know where the week went (actually I do, I took two days off.).15:03
carl_baldwinAny other announcements?15:03
yamamoto_nothing from me15:04
carl_baldwin#topic neutron-ovs-dvr15:04
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:04
carl_baldwinSwami: mrsmith: viveknarasimhan: armax:  What is the latest on DVR?15:04
carl_baldwinthe backlog was getting down and has creeped up a little bit in the last week or two.  It still is pretty much under control though.15:06
carl_baldwinI think the reason for the creep was that we had our attention diverted to getting new features in to juno-3.15:07
yamamoto_i wonder if there's much point to discuss dvr progress here while it has its own dedicated meeting15:07
carl_baldwinyamamoto_: We’ve needed it in the past but now that it is slowing and stabilizing, you may be right.15:07
mrsmithreal quick - I am focused on the migration patch and the newly split up snat fixes patch15:08
mrsmithto me those are priorities15:08
carl_baldwinyamamoto_: Still, we report progress up through the L3 team so it is good to touch on it.15:08
*** Rajeev has joined #openstack-meeting-315:08
yamamoto_carl_baldwin: fine.  just wondering15:08
mrsmiththe migration patch depends on the snat fixes so hopefully we will get those thru soon15:08
carl_baldwinmrsmith: Right.  I think I will take my co-author line off of the snat patches so that I can +2 them.  I’ve been thruogh them pretty thoroughly.15:09
mrsmithdepends = it needs the fixes to fully function15:09
mrsmithcarl_baldwin: gotcha15:09
carl_baldwinmrsmith: understood.  I will be hitting DVR bugs again as a priority (only behind wrapping up L3 HA).15:09
yamamoto_carl_baldwin: isn't it better to find another core reviewer if you are actually a co-author?15:10
mrsmithI believe carl mostly just split up the big patch into smaller ones15:10
carl_baldwinyamamoto_: I was only an author in the sense that I split the original patch up and did very minor fixups.  It was a bit of a stretch to add the co-author line, I’ll admit.15:10
yamamoto_carl_baldwin: ok it makes sense.  thank you15:11
carl_baldwinyamamoto_: You’re right though.  Credit should be given where it is due.15:11
*** cjellick has joined #openstack-meeting-315:12
*** pballand has joined #openstack-meeting-315:12
carl_baldwinOn the other hand, “It is amazing what you can accomplish if you do not care who gets the credit.” - Harry S. Truman (I think)15:12
carl_baldwin:)15:12
carl_baldwinAnyway, back to the meeting.15:12
carl_baldwinAnything more on DVR?15:12
*** itzikb has quit IRC15:13
yamamoto_nothing from me15:13
carl_baldwin#topic l3-high-availability15:13
*** openstack changes topic to "l3-high-availability (Meeting topic: neutron_l3)"15:13
carl_baldwinamuller: Do you have a report?15:13
amullerSylvain is addressing comments on the server side patches15:14
*** amotoki has quit IRC15:14
*** amotoki_ is now known as amotoki15:14
carl_baldwinWelcome back, safchain15:14
safchainhi15:14
amullerI'm working on the agent patches, improving our functional tesitng15:14
amullertesting*15:14
safchainI'm addressing comments about the vr_ids management15:14
*** mrunge has quit IRC15:14
amullerMaru and John Schwarz have been dealing with the inconsistent failures at the gate, and have already fixed it, but it'll take a while to merge because of the gate15:15
carl_baldwinsafchain: Which patch?  I didn’t notice the comments.15:15
safchainbase classes15:15
safchainaround the _set_vr_id method15:15
*** MaxV_ has quit IRC15:15
*** mitarun has quit IRC15:16
safchaincarl_baldwin, https://review.openstack.org/#/c/6455315:16
carl_baldwinsafchain: right.  I see it.15:16
*** Longgeek has joined #openstack-meeting-315:17
*** mitarun has joined #openstack-meeting-315:17
*** peristeri has quit IRC15:17
carl_baldwinThat is good feedback.15:17
safchaincarl_baldwin, so I introduced a new table for the allocations15:17
amullerDarragh O'Reilly reported an issue in the keepalived.conf after we add FIPs, trying to reproduce and test it15:18
safchainI mean vr_id allocation per ha network15:18
carl_baldwinsafchain: Feel free to ping me if you need anything or when you have something ready for review.15:19
amullerAlso we have a bug tag now and a bunch of bugs to go with: https://bugs.launchpad.net/neutron/+bugs?field.tag=l3-ha15:19
*** peristeri has joined #openstack-meeting-315:19
amullersome are closer to RFE15:19
safchaincarl_baldwin, ok, thx15:19
*** Longgeek_ has quit IRC15:20
carl_baldwinamuller: I will start to work on triage and assigning importance.15:20
carl_baldwinamuller: Thanks for gathering them together and posting the query.15:20
amullercarl_baldwin: the feature is targeted to RC115:21
amullerwhen do we expect to merge the original 3 feature patches?15:21
amullerRC1 is too late imo15:21
*** mitarun has quit IRC15:21
amullerwe need to deal with stability, bugs, testing15:21
amullerRC1 is on the 25th15:22
carl_baldwinamuller: I agree.  This is now my top priority to turn these reviews around.15:22
amulleralright15:22
carl_baldwinI feel the base classes patch is in pretty decent shape.15:23
amullernow that Sylvain is back it should go faster too15:23
carl_baldwinFor the other two, I made my comments and I don’t feel that there are any hard issues in there from my perspective.15:23
safchainamuller, yes I hope15:23
carl_baldwinPlease ping me as soon as new patches are ready for review so that we can turn them around quickly.15:24
amullerSounds good15:24
carl_baldwinamuller: anything else?15:24
amullerworking with Maru on the agent side failover functional test15:24
carl_baldwin#action carl_baldwin will triage L3 HA bugs15:25
amullerI think it's pretty cool, it's a step to having multiple L3 agents on a single machine15:25
amullerso we can test this in Tempest as well15:25
amulleralso we've been talking about integration testing in-tree15:25
carl_baldwinamuller: That sounds cool.15:25
amullerif we can get multiple L3 agents up it'll help with that as well, should help DVR and L2pop as well15:25
amullerother features that require multiple agents15:25
safchainamuller, carl_baldwin yes that is really something that we need15:26
carl_baldwinI hope you can raise the bar for testing in the project.15:26
amullerit's all marun_ guiding things15:26
amullerAiming for the failover testing in the next week-ish, and in-tree integration testing probably for early Kilo15:27
amullerThat's it for me15:27
carl_baldwinamuller: Great, thanks for the update.15:28
carl_baldwin#topic bgp-dynamic-routing15:28
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:28
yamamoto_was it deferred to kilo?15:29
carl_baldwindevvesa: ping15:29
amulleryamamoto_: it was15:29
yamamoto_why?15:29
carl_baldwinyamamoto_: Reviewer bandwidth, really.15:30
carl_baldwinI guess it was more than that.  Juno had a lot of work done in it and we can only pack so much in.15:30
carl_baldwinThis will be our first priority to open up Kilo development.15:31
*** peristeri has quit IRC15:32
yamamoto_is it a candidate of neutron-incubator?15:32
*** Swami has joined #openstack-meeting-315:32
carl_baldwinyamamoto_: It was a candidate but I’ll admit that I’ve fallen a bit behind in the neutron incubator discussion.15:32
*** MaxV has joined #openstack-meeting-315:32
yamamoto_i just hope neutron-incubator stuff doesn't defer this further.15:33
amotokiit really depends on the community discussion. we also need to consider L3 is tightly coupled with L2 and many folks regard it as a part of core.15:34
carl_baldwinyamamoto_: If neutron-incubator is not ready, I will continue with dynamic routing in the main repository.15:34
yamamoto_carl_baldwin: it makes sense15:35
carl_baldwin#topic Kilo15:36
*** openstack changes topic to "Kilo (Meeting topic: neutron_l3)"15:36
*** MaxV has quit IRC15:37
carl_baldwinI don’t have much time to get in to it today but we should probably have Kilo in the back of our minds and start discussing what we would like the main themes to be.  So, I’m going to add a Kilo topic to the weekly agenda.15:37
seizadiThe design sessions are still not open, http://summit.openstack.org/15:38
amullerRedesign the L3 agent, since we added distributed and HA routers it's an unmaintainable mess15:38
yamamoto_seizadi: when it will?15:38
amullerI think that's a strong candidate for early Kilo15:38
mrsmithamuller: +1 refactor l3-agent15:39
yamamoto_amuller: +115:39
carl_baldwinamuller: +1, I have had some refactors in mind myself.15:39
amullerstructure it somehow, add more classes, enough with these 'if distributed, if not distributed, if ha, if not ha' nonsense15:39
carl_baldwinHopefully we can have a good idea of where to start when Kilo opens.15:40
amotokiamuller: +1. I hope it includes vpn-agent merging into l3-agent.15:40
carl_baldwinamuller: Exactly.15:40
Swami+115:40
carl_baldwinamotoki: vpn merging noted15:41
*** devvesa has joined #openstack-meeting-315:41
mrsmithsplitting up process_router() is another candidate15:42
mrsmithit is getting huge15:42
amullerwe could start with that yeah15:42
seizadiyamamoto: I will post when I see it open, I thought if Carl finds out design summit schedule for Kilo through Openstack communication, we can discuss on this topic.15:42
carl_baldwinmrsmith: +115:42
carl_baldwinThe ML will probably be the best place to watch for it to open.15:43
yamamoto_mrsmith: +115:43
carl_baldwinIt can’t be too much longer.  We’ve only got two months until the summit.15:43
carl_baldwin#topic Open Discussion15:44
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:44
carl_baldwinAnything else?15:44
*** eghobo has joined #openstack-meeting-315:44
yamamoto_nothing from me15:44
amotokione question on relationship between DVR and L3-HA.15:44
amotokiAre they exclusive? just confirmation.15:44
amullerfor now, yes15:44
amullerwe just didn't get to it yet15:45
carl_baldwin#link https://bugs.launchpad.net/neutron/+bug/136547315:45
amotokiI am now planning to write a small patch in horizon and I need some constraint check for them.15:45
amotoki*small patch to support L3-HA15:45
amullernext patchset for the models patch should block the creation of a rotuer that's both HA and distributed15:45
amullerrouter*15:45
seizadiIf anyone is on the IPv6 subcommittee I like to talk to them we are having trouble with IPv6 integration. I looked at their meeting notes but not much notes.15:46
mrsmithrajeev wanted me to ask for reviewers on a couple of his patches15:46
*** MaxV has joined #openstack-meeting-315:46
mrsmithhttps://review.openstack.org/#/c/116412/15:47
mrsmithhttps://review.openstack.org/#/c/112146/2315:47
amotokii think sc68cal is the right contact.15:48
carl_baldwinmrsmith: noted15:48
*** MaxV_ has joined #openstack-meeting-315:48
carl_baldwinOkay, my time is up.  I’ll be back online in a bit.15:49
carl_baldwin#endmeeting15:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:49
openstackMeeting ended Thu Sep  4 15:49:15 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-09-04-15.01.html15:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-09-04-15.01.txt15:49
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-09-04-15.01.log.html15:49
yamamoto_bye15:49
*** mrsmith has quit IRC15:49
*** pcm_ has left #openstack-meeting-315:49
carl_baldwinthanks everyone.15:50
*** MaxV has quit IRC15:51
*** amuller has left #openstack-meeting-315:51
*** MaxV_ has quit IRC15:53
*** markmcclain has quit IRC15:53
amotokibye15:55
*** MaxV has joined #openstack-meeting-316:00
*** seizadi has quit IRC16:02
*** mitarun has joined #openstack-meeting-316:03
*** yamahata has quit IRC16:06
*** marun_ is now known as marun_afk16:06
*** banix has quit IRC16:17
*** MaxV has quit IRC16:20
*** devvesa has quit IRC16:21
*** gholler has quit IRC16:30
*** s3wong has joined #openstack-meeting-316:45
*** banix has joined #openstack-meeting-316:49
*** stevpier has quit IRC16:50
*** dtroyer_zz has joined #openstack-meeting-317:03
*** johnthetubaguy is now known as zz_johnthetubagu17:09
*** banix has quit IRC17:10
*** banix has joined #openstack-meeting-317:14
*** Longgeek_ has joined #openstack-meeting-317:16
*** stevpier has joined #openstack-meeting-317:17
*** Longgeek has quit IRC17:19
*** SumitNaiksatam has quit IRC17:22
*** ivar-lazzaro has joined #openstack-meeting-317:24
*** pballand has quit IRC17:28
*** amotoki has quit IRC17:29
*** pballand has joined #openstack-meeting-317:29
*** reed has joined #openstack-meeting-317:30
*** pballand has quit IRC17:30
*** MaxV has joined #openstack-meeting-317:31
*** MaxV has quit IRC17:36
*** marun_afk has quit IRC17:36
*** SumitNaiksatam has joined #openstack-meeting-317:36
*** SridharRamaswamy has joined #openstack-meeting-317:36
*** rms_13 has joined #openstack-meeting-317:40
*** lcheng_ has joined #openstack-meeting-317:46
*** markmcclain has joined #openstack-meeting-317:48
*** Youcef has quit IRC17:50
*** thangp has quit IRC17:54
*** shwetaap has quit IRC17:55
*** yyywu has joined #openstack-meeting-317:55
*** LouisF has joined #openstack-meeting-317:56
*** 6A4AAKDJG has joined #openstack-meeting-317:58
*** emagana has joined #openstack-meeting-317:58
*** shwetaap has joined #openstack-meeting-317:59
*** RG has joined #openstack-meeting-317:59
SumitNaiksatamhi18:00
*** songole has joined #openstack-meeting-318:00
6A4AAKDJGhi18:00
yyywuhi18:00
LouisFhi18:01
songolehello18:01
SumitNaiksatamok lets get started18:01
ivar-lazzaroyo18:01
SumitNaiksatam#startmeeting networking_policy18:01
openstackMeeting started Thu Sep  4 18:01:17 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: networking_policy)"18:01
openstackThe meeting name has been set to 'networking_policy'18:01
SumitNaiksatam#info agenda: https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy18:01
6A4AAKDJGAm I showing up as 6A4AAKDJG ? Its rkukura, actually.18:01
*** susaant has joined #openstack-meeting-318:01
SumitNaiksatam6A4AAKDJG: wow! how did you manage that? ;-)18:02
6A4AAKDJGSumitNaiksatam: No idea! I’m going to disconnect and reconnect.18:02
*** 6A4AAKDJG has quit IRC18:02
SumitNaiksatamwanted to do a quick status update on the patches which are in gerrit18:02
SumitNaiksatam#link https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy/Patches18:02
SumitNaiksatam#topic Neutron patches18:02
*** openstack changes topic to "Neutron patches (Meeting topic: networking_policy)"18:02
*** rkukura has joined #openstack-meeting-318:03
SumitNaiksatams3wong had been working on the SG mapping piece18:03
rkukurahi again18:03
SumitNaiksatamrkukura: no we recognize you, welcome back18:03
SumitNaiksatams3wong: any update from last week?18:03
rkukuraidentity crisis ;)18:03
SumitNaiksatami think s3wong is wrapping up a few things on the GPM-RMD-SG patch18:04
SumitNaiksatammeanwhile, the series had gotten messed up because of some rebases18:04
SumitNaiksatamyesterday night we fixed that18:05
SumitNaiksatamso now everything should be back where we left off18:05
SumitNaiksatamand is rebased with the latest18:05
*** Youcef has joined #openstack-meeting-318:05
ivar-lazzaronice!18:05
rkukuraSumitNaiksatam: Thanks! I’ll sanity check my patches when I get a chance.18:06
SumitNaiksatamrkukura: yes definitely18:06
SumitNaiksatamivar-lazzaro: thanks for pointing it out18:06
*** prasadv has joined #openstack-meeting-318:06
SumitNaiksatamthe last patch in the series is #link https://review.openstack.org/#/c/11377518:06
SumitNaiksatamso s3wong mentioned that there was something wrong with the UTs which he did not catch earlier18:07
SumitNaiksatamhence its failing18:07
SumitNaiksatami did not have a chance to look in the details18:07
SumitNaiksatam#topic Client/CLI18:07
*** openstack changes topic to "Client/CLI (Meeting topic: networking_policy)"18:07
SumitNaiksatamsongole: there?18:07
songoleHi18:08
SumitNaiksatamsongole: any updates, or the current set of patches is stable?18:08
songoleNo updates to CLI.18:08
songoleNaming changes need to be done.18:08
SumitNaiksatamsongole: so its rebased and everything?18:08
SumitNaiksatamsongole: naming changes have not happened at the backend18:08
songoleNeed to rebase.18:09
songoleok18:09
SumitNaiksatamsongole: so you wont be able to do it anyway :-)18:09
songoleok18:09
SumitNaiksatamsongole: okay, it will be great if you can rebase when you get a chance18:09
songoleAnyone had a chance to test CLI?18:09
SumitNaiksatamsongole: plan to give that a shot, but i thought horizon was already leveraging the client18:10
rms_13songole: I did two weeks back18:10
SumitNaiksatamsongole: so some level of automatic validation already done18:10
SumitNaiksatamrms_13: yes, thanks18:10
rms_13and it looked ok18:10
songoleok. thanks18:10
s3wongsorry, in late18:10
SumitNaiksatamsongole: thanks for the update18:10
SumitNaiksatams3wong: no worries, i provided update on your behalf18:11
rms_13Didnt get to test all of it but whatever is there in horizon so far was working fine after rebase18:11
SumitNaiksatams3wong: but feel free to chime in18:11
SumitNaiksatamrms_13: thanks, will come to the Horizon update next as well18:11
s3wongyes, as SumitNaiksatam said, I believe all the test failures indicates that the unit test is probably broken, so I will look into that18:11
SumitNaiksatams3wong: yes, no worries18:11
SumitNaiksatams3wong: thanks18:12
SumitNaiksatamsongole: thanks as well for the update on CLI/client18:12
SumitNaiksatam#topic Horizon18:12
*** openstack changes topic to "Horizon (Meeting topic: networking_policy)"18:12
SumitNaiksatamrms_13: go ahead18:13
SumitNaiksatamany updates?18:13
rms_13I need to rebase my patch18:13
SumitNaiksatamrms_13: ah, was just saying18:13
rms_13Somebody needs to review the baseline changes18:13
*** dtroyer_zz has left #openstack-meeting-318:13
SumitNaiksatamrms_13: but other than that, to what extent is the UI functional?18:13
rms_13So that grunt work can start as part of add-on patches18:13
rms_13Policy-Group, Policy-rules, Contract, Action (CRUD)18:14
rms_13Update is not part of the current patch but have it ready in private patch. Once that looks good to all, as I said earlier, other resources can be added in similar fashion18:15
SumitNaiksatamrms_13: was abishek helping you with the reviews?18:15
*** otherwiseguy has quit IRC18:15
rms_13So far no updates from him18:15
SumitNaiksatamrms_13: ok18:16
rms_13Nati also wanted to take a look...no updates from him either18:16
*** emagana has quit IRC18:16
SumitNaiksatamrms_13: so you are looking for input from a code review perspective, or feedback on the UI organization?18:16
*** qj has joined #openstack-meeting-318:16
*** emagana has joined #openstack-meeting-318:17
SumitNaiksatamrms_13: i am guessing its both18:17
rms_13Both together...basically I think the organization is correct. But than; I dont want to code another 3000 lines and get -2 saying the org is wrong :)18:17
SumitNaiksatamrms_13: true18:17
rms_13First major validation/approval I need is that Group Policy tab can seat in main panel rather than network's panel (as we demoed at Atlanta)18:18
SumitNaiksatamrms_13: that said i think it will be difficult to get reviewer attention late in the Juno cycle18:18
*** otherwiseguy has joined #openstack-meeting-318:18
SumitNaiksatamrms_13: okay, valid concerns18:19
rms_13I understand. Have some idea about that. Will share it on the email for more discussion18:19
SumitNaiksatamrms_13: yeah, i was going to suggest that if you can summarize your concerns and the items that you are soliciting feedback on, that will be great18:19
SumitNaiksatamrms_13: we can then try to close on those online/offline18:20
rms_13sure will do...18:20
SumitNaiksatamrms_13: great, thanks!18:20
SumitNaiksatam#topic Heat18:20
*** openstack changes topic to "Heat (Meeting topic: networking_policy)"18:20
SumitNaiksatamsusaant: hi there18:20
SumitNaiksatamsusaant: any updates at your end?18:20
susaantI dont have any updates on heat patches18:21
*** emagana has quit IRC18:21
SumitNaiksatamsusaant: okay, the patch seems to have failed some UTs18:21
*** banix has quit IRC18:21
SumitNaiksatamsusaant: is that a minor issue?18:21
susaantyes. Thats because the GBP neutron resources are not present..18:22
SumitNaiksatamsusaant: ah got it18:22
SumitNaiksatamsusaant: so in a private devstack setup, this works18:22
SumitNaiksatamprivate -> local18:22
s3wonghmm... obviously we bored banix enough for him to leave :-)18:22
susaantthat is correct.18:22
SumitNaiksatamsusaant: okay great thanks18:22
*** eghobo has quit IRC18:23
SumitNaiksatam#topic GBP repo/home discussion18:23
*** openstack changes topic to "GBP repo/home discussion (Meeting topic: networking_policy)"18:23
*** eghobo has joined #openstack-meeting-318:23
SumitNaiksatam#link http://lists.openstack.org/pipermail/openstack-dev/2014-September/044834.html18:23
SumitNaiksatamthe above email was sent on behalf of the team18:24
SumitNaiksatamand captures some of the options that were or have been suggested18:24
SumitNaiksatamany thoughts?18:24
prasadvSumitNaiksatam: thanks for the email.18:25
*** otherwiseguy has quit IRC18:25
s3wongSumitNaiksatam: the Neutron feature idea never picked up any momentum, are we still considering it?18:25
rkukuras3wong: Do you mean the “feature branch” idea?18:26
rms_13I was reading on the incubator program wiki (https://wiki.openstack.org/wiki/Network/Incubator)18:26
SumitNaiksatams3wong: i am not aware what the current status on that is18:26
s3wongrkukura: yes (sorry for mssing a word)18:26
rkukuras3wong: Or the preview subtree idea, which isn’t even listed.18:26
s3wongrkukura: feature branch18:26
rkukuraI spoke with our PTL, mestery, yesterday, and he indicated that feature branches are being planned18:26
s3wongrkukura: oh, really?18:27
rkukuraThat’s what I said18:27
prasadvrkukura: when would the planned branch happen18:27
s3wongrkukura: in that case, it is only applicable for Neutron features that can be packaged and lived completely isolated from Neutron18:27
prasadvwould it have same non dterministic behaviour as incubaotr18:28
s3wongrkukura: which GBP so far is18:28
LouisFs3wong: what sort of features?18:28
s3wongLouisF: something like GBP, I believe18:28
rkukuraTo me, advantage of the feature branch option are: 1) clear path into neutron on graduation, 2) no loss of git history on graduation18:29
LouisFs3wong: is there precedent for feature branches?18:29
*** emagana has joined #openstack-meeting-318:29
rms_13What is the procedure on code review on feature branch? Any decision on that yet?18:30
s3wongLouisF: as rkukura said above, it is an idea from mestery at this point18:30
rkukuraConcerns I’ve heard raised are: 1) no CI for existing non-master branches (stable branches), and 2) not clear if existing packaging for stable branches is applicable/adequate for feature branches18:30
SumitNaiksatamrkukura: until “graduation” would the feature live in isolation (that is the feature branch, if packaged, has to be packaged all by itself, essentially a fork)?18:31
prasadvrkukura: wont (1) and (2) be the same for incubation or stackforge?18:31
rkukuraSumitNaiksatam: I think that depends if the branch is purely additive or modifies code from master/stable branches18:32
LouisFs3wong: rkukura so feature branches are a completely new idea?18:32
s3wongLouisF: yes, it doesn't exist today18:32
SumitNaiksatamrkukura: true, so for example if two features are developed in paralled features branches, then you can essentially only deploy one of them from a package, right?18:33
rkukuraI’m only familiar with Red Hat’s packaging process (worked there previously), but I see no reason any number of purely additive feature branches could not be packaged to depend on the normal neutron packages.18:34
SumitNaiksatamprasadv: to your question, #link http://ci.openstack.org/stackforge.html states that stackforge projects have jenkins continuous integration support18:34
rms_13In all these approaches, I am very concern about the merge into neutron (so called graduation time). There possibly would be huge patches needed to be reviewed and regressed (one for every feature) and that will take lot of review time of cores. Any clear path defined to handle those?18:35
s3wongSumitNaiksatam: my take is that the way people have been discussing incubator, it sounds like they want it to be separate package also - though perhaps everything in incubator is one package, instead of say a GBP package and a LBaaSv2 package18:35
SumitNaiksatamrkukura: okay, but probably related features are likely to have some overlap18:36
rkukurarms_13: I think either the incubator or feature branch option involves core reviews on the way in, so re-review on graduation would be minimal18:36
*** tomoe_ has quit IRC18:36
rms_13rkukura: thats a good hope. But typically everybody is excited to see a new kid and wants to give blessings or two :)18:37
s3wongrkukura: in that case, what is the major difference between incubator and feature branches - that each feature will occupy a branch (and separate packaging)?18:37
rms_13Unless there is a stringent requirement that re-review MUST be minimal (or by those cores only involved from incubation phase); I am not too confident that that would happen.18:38
rkukuras3wong: Main difference is that graduation of a feature branch is just a merge, preserving git histrory (I think)18:38
rms_13All I want to suggest is that we should push hard for strict rules on that front. Nothing else18:38
s3wongrms_13: Agreed. I can definitely see another "-2: too large" or "-2: lack consensus" type situation18:39
rms_13s3wong: +10018:39
rkukuras3wong, rms_13: The graduation hurdle is definitely a risk with any of the options, but only the feature branch option preserves history.18:40
songolerkukura: in that sense, stackforge is not an option18:40
SumitNaiksatamso it seems like the only difference between the feature branch and the incubator is with the ease in preservation of git history18:40
rkukuraI think the hurdle to get into neutron is signfiicantly higher with the stackforge option than any of the others.18:41
rkukuraBut there are no guarantees with any of them, meaning we could end up as a separate project.18:41
*** markmcclain has quit IRC18:41
*** markmcclain has joined #openstack-meeting-318:41
SumitNaiksatamthe process and policies would be similar for both (i am just summarizing based on the information presented above, i havent seen a wiki yet)18:41
rms_13rkukura: Agree. If and only if the merging guidelines is clearly defined (including review scheme)18:41
SumitNaiksatamrms_13: i dont think anyone can gaurantee a merge :-)18:42
SumitNaiksatamrms_13: it is an inherently subjective area18:42
rms_13SumitNaiksatam: Than better do it on stackforge18:42
SumitNaiksatamthe principle of loose consensus allows for negative votes at any time in the liefcycle18:42
rkukuraThe one thing I think there is agreement on in all of these discussions is that forking into a separate repo is way easier than merging into an existing one.18:43
s3wongrkukura: SumitNaiksatam: if the main goal is to allow users to use it, is GBP being part of Neutron really that important?18:43
SumitNaiksatams3wong: that is good point, and Octavia, I believe has taken that view18:43
*** aleksandr_null has quit IRC18:43
SumitNaiksatams3wong: they want to iterate faster, and provide something useable and put it into people’s hands18:44
rkukuras3wong: If we see tight coupling, as in living in the same process as neutorn, intercepting neutron requests, and ML2 mechanism drivers working closely with policy drivers, being part of neutron seems essential.18:44
SumitNaiksatami also think that the approaches we are discussing are perhaps not mutually exclusive18:44
rms_13s3wong, SumitNaiksatam: Good points. Lets say we take octavia like route. How does interaction with other openstack system works in that case?18:45
rkukuraBut as I understand it, octavia is a separate thing, basically a reference implementation of a load balancer datapath.18:45
SumitNaiksatamrms_13: in the same way, taht for example nova interacts with neutron18:45
rkukuraTo me the neutron/octavia interface isn’t that different than the neutron/ODL interface or even the nova/KVM interface.18:46
SumitNaiksatamrkukura: i agree, octavia is not in the same zip code as a feature as GBP is18:47
SumitNaiksatamrkukura: i brought up the analogy from a process perspective (in terms of being able to iterate faster and deliver to something usable) in response to s3wong’s point18:47
rkukuraWe could certainly decide that GBP should be a separate project with its own server than uses neutron via python-neutronclient, and go  in that direction18:47
s3wongrkukura: people in Octavia project (and LBaaSv2 project) has plan to spin out the entire LBaaS from Neutron18:48
s3wongrkukura: and what is missing is a clean interface for how LBaaS uses Neutron18:48
SumitNaiksatams3wong: and we tried hard to fix that :-)18:48
rkukuras3wong: Or how neutron uses LBaaS (if neutron is policy-based and controls load balancing via actions)18:49
s3wongrkukura: thinking of NOT having GBP in Neutron can also get us to think about what external interfaces does Neutron lack18:49
*** itzikb has joined #openstack-meeting-318:50
rms_13s3wong: +118:50
prasadvs3wong: That is a good point18:50
rkukuraTo me, separate projects implies separate servers in separate processes with separate REST APIs. Is that others’ understanding as well?18:51
s3wongrkukura: yes18:51
SumitNaiksatamrkukura: you are asking the GBP context?18:52
SumitNaiksatamrkukura: or a general question?18:52
rms_13rkukura: yes18:52
rkukuraSumitNaiksatam: general, but with implications for GBP if we were to decide graduation into neutron was no longer a goal.18:53
prasadvSumitNaiksatam: would stackforge imply also we could get GBP into J timeframe. Seems like the other options might not make it within J timeframe isnt it18:53
SumitNaiksatamrkukura: okay18:53
rkukuraI would think setting up a new project with its own WSGI/REST framework would take significant time, and not be anything but a WIP at Juno release.18:54
s3wongprasadv: well, stackforge will take at least two cycles to go from incubation to mainline18:54
SumitNaiksatamprasadv: i havent worked through a stackforge myself, there is an application process involved (i believe its just a gerrit review)18:54
s3wongprasadv: but then again, we aren't making it to J timeframe anyway18:55
rkukuraOr are we talking about a service plugin in stackforge, that is not a separate project/server/process from neutron?18:55
SumitNaiksatamrkukura: yes, i think we need to work through those options better18:55
rkukuraMy view is that we could merge our stuff to a fearture branch off of Juno-3 or Juno-RC1, then rebase this to Juno at about the time Juno ships.18:56
SumitNaiksatams3wong: if i understood prasadv correctly, he was not asking about incubatiio, he was just asking when can you get a package ready? :-)18:56
SumitNaiksatam*incubation and graduation18:56
rkukuraSo is “stackforge” really two different options: service plugin vs. stand-alone service?18:56
SumitNaiksatamrkukura: perhaps18:57
SumitNaiksatamrkukura: so lets if lbaas were to spin out today18:57
songoleis lbaasv2 being implemented as a service plugin in stackforge?18:58
SumitNaiksatamrkukura: i think they would have to consider the same choice, right?18:58
SumitNaiksatamsongole: currently lbaasv2 is not in stackforge18:58
SumitNaiksatamsongole: it was proposed in neutron, but its in the same boat as GBP18:58
SumitNaiksatamsongole: they are evaluating the options18:58
songoleok18:59
s3wongsongole: it isn't in stackforge yet18:59
rkukuraSumitNaiksatam: I agree for the LBaSSv2 REST API, but octavia as a datapath is inherently a separate process (or VM?) isn’t it?18:59
SumitNaiksatamsongole: what is in stackforge is Octavia, which is more of a driver/reference implemenation for lbaas18:59
SumitNaiksatamrkukura: true18:59
SumitNaiksatamrkukura: but i was saying in the context of the discussion in the ML19:00
SumitNaiksatamrkukura: wherein people are accepting that the different services will be spun out into separate projects19:00
SumitNaiksatamrkukura: eventually19:00
s3wongSumitNaiksatam: yep, only Octavia is in stackforge, but Octavia follows LBaaSv2, and therefore it is a bit hairy19:00
SumitNaiksatams3wong: yes thanks19:01
SumitNaiksatamokay folks we have hit the hour19:01
s3wongSumitNaiksatam: so there is a LBaaS email thread that is talking about whether they should pull LBaaSv2 off there also19:01
rkukuraSumitNaiksatam: Do you mean as service plugins in separate projects, or new as new services?19:01
SumitNaiksatamwas only hoping to seed the discussion19:01
s3wongSumitNaiksatam: yeah, no way to finalize on our plan during this meeting :-)19:01
SumitNaiksatamrkukura: i am not sure, but what i meant was that they will be faced with the same choice or dilema that we have are discussing now19:01
rkukuraMy view is that neutron-server (and the neutron project) should be the API and orchestration layer, and not include any datapaths.19:02
SumitNaiksatams3wong: yes there is an email thread to that effect19:02
SumitNaiksatamrkukura: true, but neutron has also has a narrow defintion of what that API should be19:02
SumitNaiksatamrkukura: so that opens up bigger questions19:02
SumitNaiksatamalrighty folks19:03
SumitNaiksatamlets wrap it here19:03
prasadvSumitNaiksatam: seems like we need to decide soon on the options soon right?19:03
SumitNaiksatamand continue on the ML19:03
SumitNaiksatamprasadv: yes sure19:03
SumitNaiksatamprasadv: lets leverage the ML as well19:03
s3wongprasadv: yes, but I believe any option would at least take two cycles19:03
rkukuraIt sounds to me like mestery and markmcclain are trying to nail down feature branch details like CI and packaging as we speak19:03
prasadvs3wong: for graduation right?19:03
*** eghobo has quit IRC19:03
SumitNaiksatamit will be good to let the community know where the GBP is leaning (or what the technical choices and pros/cons are)19:04
s3wongincubator as defined by markmcclain takes two cycles to graduate19:04
s3wongprasadv: yes19:04
prasadvs3wong: ok. But which option will get us in front of customers faster19:04
*** markmcclain has quit IRC19:04
prasadvI think that should be important19:04
SumitNaiksatamprasadv: point well taken19:05
SumitNaiksatamon that note, lets end for today19:05
SumitNaiksatam#endmeeting19:05
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:05
rkukuraprasadv: agreed that’s a major consideration19:05
openstackMeeting ended Thu Sep  4 19:05:10 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:05
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-09-04-18.01.html19:05
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-09-04-18.01.txt19:05
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-09-04-18.01.log.html19:05
rkukurabye19:05
SumitNaiksatamthanks all for joining19:05
songolebye19:05
rkukurathanks SumitNaiksatam !19:05
s3wongprasadv: I think all three options, you can bundle a different package and ship it to customers19:05
*** prasadv has quit IRC19:05
SumitNaiksatamrkukura: apologies for cutting that thought19:05
s3wongthanks, guys19:05
*** songole has left #openstack-meeting-319:05
rkukuralets move this to the ML, right?19:05
SumitNaiksatamrkukura: yes sure19:06
*** lcheng_ has quit IRC19:06
*** otherwiseguy has joined #openstack-meeting-319:06
*** susaant has quit IRC19:07
*** rkukura has left #openstack-meeting-319:07
*** eghobo has joined #openstack-meeting-319:08
*** terryw has joined #openstack-meeting-319:09
*** eghobo has quit IRC19:09
*** eghobo has joined #openstack-meeting-319:10
*** otherwiseguy has quit IRC19:11
*** MaxV has joined #openstack-meeting-319:11
*** s3wong has quit IRC19:13
*** s3wong has joined #openstack-meeting-319:13
*** mitarun has quit IRC19:15
*** emagana has quit IRC19:16
*** LouisF has quit IRC19:16
*** mitarun has joined #openstack-meeting-319:16
*** emagana has joined #openstack-meeting-319:16
*** mitarun has quit IRC19:20
*** emagana has quit IRC19:21
*** Sukhdev has joined #openstack-meeting-319:22
*** banix has joined #openstack-meeting-319:25
*** Longgeek_ has quit IRC19:29
*** cjellick has quit IRC19:31
*** RG has quit IRC19:32
*** markmcclain has joined #openstack-meeting-319:32
*** cjellick has joined #openstack-meeting-319:32
*** mwagner_lap has quit IRC19:33
*** itzikb has quit IRC19:34
*** cjellick has quit IRC19:37
*** banix has quit IRC19:41
*** emagana has joined #openstack-meeting-319:42
*** Jim_ has joined #openstack-meeting-319:44
*** Jim_ has quit IRC19:45
*** MaxV has quit IRC19:47
*** prasoon has quit IRC19:49
*** aleksandr_null has joined #openstack-meeting-319:50
*** shwetaap has quit IRC19:51
*** banix has joined #openstack-meeting-319:52
*** johnbelamaric has joined #openstack-meeting-319:52
*** terryw has quit IRC19:54
*** MaxV has joined #openstack-meeting-319:57
*** shwetaap has joined #openstack-meeting-319:58
*** otherwiseguy has joined #openstack-meeting-320:04
*** emagana has quit IRC20:05
*** emagana has joined #openstack-meeting-320:05
*** emagana has quit IRC20:05
*** emagana has joined #openstack-meeting-320:06
*** banix has quit IRC20:06
*** otherwiseguy has quit IRC20:09
*** banix has joined #openstack-meeting-320:14
*** eghobo has quit IRC20:17
*** johnbelamaric has quit IRC20:18
*** dkehnx1 has quit IRC20:19
*** david-lyle is now known as david-lyle_afk20:22
*** david-lyle_afk has quit IRC20:23
*** flaper87 is now known as flaper87|afk20:24
*** david-lyle_afk has joined #openstack-meeting-320:28
*** julim has quit IRC20:28
*** yamamoto_ has quit IRC20:28
*** Swami has quit IRC20:29
*** david-lyle_afk has quit IRC20:29
*** david-lyle_afk has joined #openstack-meeting-320:30
*** david-lyle_afk has quit IRC20:30
*** lcheng_ has joined #openstack-meeting-320:30
*** david-lyle_afk has joined #openstack-meeting-320:30
*** david-lyle has joined #openstack-meeting-320:32
*** david-lyle_afk has quit IRC20:32
*** igordcard has joined #openstack-meeting-320:35
*** jtomasek has quit IRC20:36
*** eghobo has joined #openstack-meeting-320:39
*** cjellick has joined #openstack-meeting-320:45
*** jtomasek has joined #openstack-meeting-320:56
*** emagana has quit IRC20:58
*** david-lyle has quit IRC20:58
*** david-lyle has joined #openstack-meeting-320:58
*** emagana has joined #openstack-meeting-321:00
*** johnbelamaric has joined #openstack-meeting-321:12
*** emagana has quit IRC21:12
*** emagana has joined #openstack-meeting-321:12
*** marun_afk has joined #openstack-meeting-321:14
*** emagana has quit IRC21:17
*** Sukhdev has quit IRC21:22
*** thomasem has quit IRC21:23
*** peristeri has joined #openstack-meeting-321:23
*** qj has quit IRC21:24
*** eghobo has quit IRC21:27
*** eghobo has joined #openstack-meeting-321:27
*** yamamoto has joined #openstack-meeting-321:29
*** peristeri has quit IRC21:31
*** Rajeev has quit IRC21:32
*** david-lyle has quit IRC21:34
*** lcheng_ has quit IRC21:34
*** yamamoto has quit IRC21:34
*** johnbelamaric has quit IRC21:35
*** johnbelamaric has joined #openstack-meeting-321:35
*** johnbelamaric has quit IRC21:37
*** johnbelamaric has joined #openstack-meeting-321:37
*** dkehnx1 has joined #openstack-meeting-321:37
*** lcheng_ has joined #openstack-meeting-321:38
*** david-lyle has joined #openstack-meeting-321:40
*** johnbelamaric has quit IRC21:41
*** lcheng_ has quit IRC21:42
*** Youcef has quit IRC21:43
*** markmcclain has quit IRC21:45
*** jpomero_ is now known as jpomero21:46
*** stevpier has quit IRC21:47
*** ivar-lazzaro1 has joined #openstack-meeting-321:52
*** ivar-lazzaro has quit IRC21:53
*** MaxV has quit IRC22:02
*** jgrimm is now known as zz_jgrimm22:04
*** emagana has joined #openstack-meeting-322:13
*** jtomasek has quit IRC22:16
*** emagana has quit IRC22:18
*** chuckC has quit IRC22:18
*** rockyg has joined #openstack-meeting-322:22
*** yamamoto has joined #openstack-meeting-322:24
*** Youcef has joined #openstack-meeting-322:24
*** alexpilotti has quit IRC22:25
*** mfer has quit IRC22:25
*** david-lyle has quit IRC22:27
*** yamamoto has quit IRC22:29
*** emagana has joined #openstack-meeting-322:33
*** emagana has quit IRC22:34
*** emagana has joined #openstack-meeting-322:34
*** emagana has quit IRC22:39
*** spongewindbag has joined #openstack-meeting-322:40
*** shwetaap has quit IRC22:41
*** flaviof has quit IRC22:42
*** sarob has quit IRC22:42
*** emagana has joined #openstack-meeting-322:42
*** emagana has quit IRC22:47
*** spongewindbag has quit IRC22:54
*** emagana has joined #openstack-meeting-322:55
*** amazingdeveloper has joined #openstack-meeting-322:56
*** carl_baldwin has quit IRC23:00
*** rockyg has quit IRC23:01
*** amazingdeveloper has quit IRC23:01
*** chuckC has joined #openstack-meeting-323:07
*** ivar-lazzaro1 has quit IRC23:09
*** Youcef has quit IRC23:12
*** yamamoto has joined #openstack-meeting-323:24
*** yamamoto has quit IRC23:29
*** lcheng_ has joined #openstack-meeting-323:29
*** emagana has quit IRC23:42
*** emagana has joined #openstack-meeting-323:42
*** emagana has quit IRC23:47
*** yamamoto has joined #openstack-meeting-323:54
*** tomoe_ has joined #openstack-meeting-323:54
*** yamamoto has quit IRC23:59

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!