Thursday, 2014-11-20

*** armax has joined #openstack-meeting-300:00
*** ycombinator_ has joined #openstack-meeting-300:00
*** pballand has joined #openstack-meeting-300:01
*** pballand has quit IRC00:02
*** SridharRamaswamy has quit IRC00:02
*** emagana has quit IRC00:03
*** pballand has joined #openstack-meeting-300:03
*** ycombinator_ has quit IRC00:03
*** emagana has joined #openstack-meeting-300:04
*** baoli has quit IRC00:06
*** pballand has quit IRC00:07
*** emagana has quit IRC00:08
*** Sukhdev has quit IRC00:08
*** yamamoto has joined #openstack-meeting-300:16
*** bpokorny has joined #openstack-meeting-300:19
*** wuhg has joined #openstack-meeting-300:20
*** yamamoto has quit IRC00:20
*** bpokorny_ has quit IRC00:22
*** jimhoagland has quit IRC00:25
*** yamamoto has joined #openstack-meeting-300:41
*** otherwiseguy has joined #openstack-meeting-300:46
*** etoews has joined #openstack-meeting-300:51
*** etoews has quit IRC00:51
*** jimhoagland has joined #openstack-meeting-300:51
*** hinnant_ has quit IRC00:58
*** reed has quit IRC01:05
*** yamamoto has quit IRC01:08
*** jimhoagland has quit IRC01:09
*** yamamoto has joined #openstack-meeting-301:09
*** yamamoto has quit IRC01:10
*** ivar-lazzaro has joined #openstack-meeting-301:17
*** otherwiseguy has quit IRC01:23
*** ivar-lazzaro has quit IRC01:31
*** sarob has quit IRC01:32
*** sarob_ has joined #openstack-meeting-301:32
*** gaitan_ has joined #openstack-meeting-301:51
*** gaitan_ has quit IRC01:52
*** gaitan_ has joined #openstack-meeting-301:52
*** gaitan_ has quit IRC01:53
*** bpokorny has quit IRC01:54
*** gaitan has quit IRC01:55
*** vkmc has quit IRC01:57
*** SumitNaiksatam has quit IRC01:57
*** vishwanathj has joined #openstack-meeting-301:58
*** alexpilotti has quit IRC01:58
*** alexpilotti has joined #openstack-meeting-302:00
*** alexpilotti has quit IRC02:01
*** alexpilotti has joined #openstack-meeting-302:02
*** alexpilotti has quit IRC02:03
*** mwang2 has quit IRC02:03
*** alexpilotti has joined #openstack-meeting-302:04
*** alexpilotti has quit IRC02:06
*** alexsyip has quit IRC02:21
*** otherwiseguy has joined #openstack-meeting-302:27
*** ivar-lazzaro has joined #openstack-meeting-302:28
*** Longgeek has joined #openstack-meeting-302:33
*** Longgeek has quit IRC02:40
*** sarob_ has quit IRC02:55
*** stanzgy has joined #openstack-meeting-302:58
*** HenryG has quit IRC03:15
*** HenryG has joined #openstack-meeting-303:18
*** yamahata has joined #openstack-meeting-303:26
*** ivar-laz_ has joined #openstack-meeting-303:31
*** ivar-lazzaro has quit IRC03:35
*** ivar-laz_ has quit IRC03:36
*** Longgeek has joined #openstack-meeting-303:36
*** Longgeek has quit IRC03:41
*** badveli has quit IRC03:41
*** yamamoto has joined #openstack-meeting-303:53
*** jgrimm is now known as zz_jgrimm03:54
*** sarob has joined #openstack-meeting-303:56
*** sarob has quit IRC04:00
*** banix has joined #openstack-meeting-304:08
*** SumitNaiksatam has joined #openstack-meeting-304:24
*** pcarver has quit IRC04:31
*** pcarver has joined #openstack-meeting-304:33
*** Longgeek has joined #openstack-meeting-304:37
*** yamamoto has quit IRC04:39
*** pcarver has quit IRC04:40
*** Longgeek has quit IRC04:42
*** pcarver has joined #openstack-meeting-304:57
*** sarob has joined #openstack-meeting-304:58
*** sarob has quit IRC05:02
*** yamamoto has joined #openstack-meeting-305:06
*** carl_baldwin has joined #openstack-meeting-305:10
*** SumitNaiksatam_ has joined #openstack-meeting-305:13
*** pcarver has quit IRC05:15
*** SumitNaiksatam has quit IRC05:16
*** SumitNaiksatam_ is now known as SumitNaiksatam05:17
*** carl_baldwin has quit IRC05:27
*** nelsnelson has quit IRC05:38
*** pcarver has joined #openstack-meeting-305:39
*** pcarver has quit IRC05:46
*** nelsnelson has joined #openstack-meeting-305:46
*** Longgeek has joined #openstack-meeting-306:01
*** banix has quit IRC06:01
*** Longgeek has quit IRC06:02
*** Longgeek has joined #openstack-meeting-306:03
*** pcarver has joined #openstack-meeting-306:14
*** SumitNaiksatam_ has joined #openstack-meeting-306:15
*** iovadia has joined #openstack-meeting-306:17
*** iovadia has left #openstack-meeting-306:18
*** SumitNaiksatam has quit IRC06:18
*** SumitNaiksatam_ is now known as SumitNaiksatam06:18
*** shwetaap has joined #openstack-meeting-306:27
*** shwetaap1 has joined #openstack-meeting-306:33
*** k4n0 has joined #openstack-meeting-306:33
*** shwetaap has quit IRC06:37
*** jimhoagland has joined #openstack-meeting-306:42
*** otherwiseguy has quit IRC06:44
*** SumitNaiksatam_ has joined #openstack-meeting-307:02
*** stanzgy has quit IRC07:04
*** SumitNaiksatam has quit IRC07:05
*** SumitNaiksatam_ is now known as SumitNaiksatam07:05
*** stanzgy has joined #openstack-meeting-307:10
*** armax has quit IRC07:12
*** jgallard has joined #openstack-meeting-307:20
*** mrunge has joined #openstack-meeting-307:24
*** evgenyf has joined #openstack-meeting-307:28
*** pcarver has quit IRC07:28
*** jcoufal has joined #openstack-meeting-307:35
*** mrmartin has joined #openstack-meeting-307:43
*** devvesa has joined #openstack-meeting-307:47
*** pcarver has joined #openstack-meeting-307:51
*** redrobot has quit IRC07:52
*** redrobot has joined #openstack-meeting-307:55
*** redrobot is now known as Guest2787907:55
*** sergef has joined #openstack-meeting-307:58
*** mwang2 has joined #openstack-meeting-307:59
*** SumitNaiksatam has quit IRC08:00
*** jtomasek has joined #openstack-meeting-308:02
*** mwang2 has quit IRC08:03
*** matrohon has joined #openstack-meeting-308:09
*** belmoreira has joined #openstack-meeting-308:10
*** jcoufal has quit IRC08:12
*** jcoufal has joined #openstack-meeting-308:12
*** b3nt_pin has quit IRC08:15
*** beagles has joined #openstack-meeting-308:16
*** beagles is now known as Guest2782508:16
*** stanzgy has quit IRC08:18
*** stanzgy has joined #openstack-meeting-308:22
*** zz_ttrifonov is now known as ttrifonov08:29
*** yamamoto has quit IRC08:29
*** pkarikh has joined #openstack-meeting-308:36
*** sarob has joined #openstack-meeting-308:36
*** bobmel has quit IRC08:40
*** devvesa has quit IRC08:41
*** sarob has quit IRC08:41
*** MaxV has joined #openstack-meeting-308:42
*** reed has joined #openstack-meeting-308:58
*** yamamoto has joined #openstack-meeting-308:58
*** safchain has joined #openstack-meeting-308:59
*** pkoniszewski has joined #openstack-meeting-309:02
*** pkoniszewski has quit IRC09:13
*** pcarver has quit IRC09:16
*** pcarver has joined #openstack-meeting-309:23
*** Guest27825 has quit IRC09:27
*** mwagner_lap has quit IRC09:30
*** Longgeek has quit IRC09:32
*** beagles has joined #openstack-meeting-309:32
*** beagles is now known as b3nt_pin09:33
*** lhcheng has joined #openstack-meeting-309:38
*** yamamoto has quit IRC09:39
*** Longgeek has joined #openstack-meeting-309:41
*** pkoniszewski has joined #openstack-meeting-309:44
*** pkoniszewski has quit IRC09:53
*** lhcheng_ has joined #openstack-meeting-310:00
*** pcarver has quit IRC10:00
*** lhcheng has quit IRC10:03
*** salv-orlando_ has joined #openstack-meeting-310:17
*** salv-orlando has quit IRC10:19
*** salv-orlando_ is now known as salv-orlando10:19
*** sarob has joined #openstack-meeting-310:26
*** pcarver has joined #openstack-meeting-310:29
*** sarob has quit IRC10:31
*** stanzgy has quit IRC10:33
*** yamamoto has joined #openstack-meeting-310:39
*** stanzgy has joined #openstack-meeting-310:42
*** yamamoto has quit IRC10:44
*** nelsnelson has quit IRC10:45
*** igordcard has joined #openstack-meeting-310:48
*** stanzgy has quit IRC10:56
*** matrohon has quit IRC10:58
*** evgenyf has quit IRC11:04
*** zz_jgrimm is now known as jgrimm11:06
*** jgallard has quit IRC11:07
*** jcoufal has quit IRC11:11
*** jcoufal has joined #openstack-meeting-311:12
*** yamahata has quit IRC11:26
*** jcoufal has quit IRC11:27
*** jcoufal has joined #openstack-meeting-311:27
*** yamahata has joined #openstack-meeting-311:29
*** flwang has quit IRC11:36
*** evgenyf has joined #openstack-meeting-311:38
*** Longgeek has quit IRC11:39
*** xuhanp has joined #openstack-meeting-311:39
*** [1]evgenyf has joined #openstack-meeting-311:40
*** flwang has joined #openstack-meeting-311:43
*** evgenyf has quit IRC11:43
*** [1]evgenyf is now known as evgenyf11:43
*** nfedotov has joined #openstack-meeting-311:54
*** Longgeek has joined #openstack-meeting-312:19
*** baoli has joined #openstack-meeting-312:27
*** xuhanp has quit IRC12:31
*** baoli has quit IRC12:31
*** baoli has joined #openstack-meeting-312:31
*** matrohon has joined #openstack-meeting-312:40
*** yamamoto has joined #openstack-meeting-312:41
*** jcoufal has quit IRC12:42
*** jcoufal has joined #openstack-meeting-312:43
*** yamamoto has quit IRC12:47
*** jcoufal has quit IRC12:51
*** matrohon has quit IRC12:56
*** jcoufal has joined #openstack-meeting-313:01
*** jgallard has joined #openstack-meeting-313:14
*** pkoniszewski has joined #openstack-meeting-313:15
*** mrunge has quit IRC13:21
*** pkoniszewski has quit IRC13:22
*** xuhanp has joined #openstack-meeting-313:25
*** matrohon has joined #openstack-meeting-313:29
*** k4n0 has quit IRC13:38
*** salv-orlando has quit IRC13:47
*** baoli has quit IRC14:01
*** julim has joined #openstack-meeting-314:03
*** dboik has joined #openstack-meeting-314:04
*** sarob has joined #openstack-meeting-314:05
*** sergef has quit IRC14:07
*** jacalcat has joined #openstack-meeting-314:09
*** amuller has joined #openstack-meeting-314:14
*** sarob has quit IRC14:14
*** jimhoagland has quit IRC14:17
*** asahlin has joined #openstack-meeting-314:17
*** david-lyle has quit IRC14:18
*** peristeri has joined #openstack-meeting-314:22
*** johnbelamaric_ has joined #openstack-meeting-314:22
*** shwetaap1 has quit IRC14:26
*** shwetaap has joined #openstack-meeting-314:27
*** sigmavirus24_awa is now known as sigmavirus2414:29
*** banix has joined #openstack-meeting-314:32
*** EranGampel has joined #openstack-meeting-314:40
*** bradjones has joined #openstack-meeting-314:46
*** bradjones has quit IRC14:46
*** bradjones has joined #openstack-meeting-314:46
*** yamamoto has joined #openstack-meeting-314:48
*** otherwiseguy has joined #openstack-meeting-314:48
*** jemangs has joined #openstack-meeting-314:51
*** sergef has joined #openstack-meeting-314:53
*** dtroyer has joined #openstack-meeting-314:54
*** silvrax has joined #openstack-meeting-314:54
*** carl_baldwin has joined #openstack-meeting-314:55
*** markmcclain has joined #openstack-meeting-314:57
*** salv-orlando has joined #openstack-meeting-314:57
*** Swami_ has joined #openstack-meeting-314:58
carl_baldwinhi all14:58
amullerhiya14:59
johnbelamaric_hi14:59
yamamotohi14:59
Swami_h14:59
ChuckChi14:59
*** yamahata has quit IRC14:59
*** otherwiseguy has quit IRC14:59
carl_baldwinamuller johnbelamaric_ yamamoto Swami_ ChuckC: hi15:00
*** yamahata has joined #openstack-meeting-315:00
*** markmcclain1 has joined #openstack-meeting-315:00
carl_baldwin#startmeeting neutron_l315:00
openstackMeeting started Thu Nov 20 15:00:20 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:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:00
openstackThe meeting name has been set to 'neutron_l3'15:00
*** pc_m has joined #openstack-meeting-315:00
carl_baldwin#topic Announcements15:00
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:00
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam#Announcements15:00
carl_baldwinMid-cycle sprint and the Neutron spec proposal/approval deadlines are on the calendar.15:01
*** markmcclain has quit IRC15:01
carl_baldwinAny other announcements?15:01
*** hareeshp has joined #openstack-meeting-315:01
*** rohit404 has joined #openstack-meeting-315:02
carl_baldwin#topic Bugs15:02
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:02
*** nelsnelson has joined #openstack-meeting-315:02
*** nelsnelson has quit IRC15:03
carl_baldwinOne new bug, bug 1388698, snuck in while we were at summit.15:03
carl_baldwin#link https://bugs.launchpad.net/neutron/+bug/138869815:03
*** mrsmith_ has joined #openstack-meeting-315:03
*** nelsnelson has joined #openstack-meeting-315:04
carl_baldwinAny other bugs that we need to discuss?15:04
amullerI don't understand the bug description15:05
*** markmcclain1 has quit IRC15:05
amullerCan you explain it Carl?15:05
*** johnbelamaric has joined #openstack-meeting-315:05
*** markmcclain has joined #openstack-meeting-315:05
*** johnbelamaric_ has quit IRC15:05
*** johnbelamaric_ has joined #openstack-meeting-315:06
carl_baldwinamuller: I have looked at it closely yet.  I may follow up with Eugene about it.15:06
*** SridharRamaswamy has joined #openstack-meeting-315:06
*** Swami_ has quit IRC15:06
amullerthere's a conflict in the bug description... anyway don't know if you want to spend any time on that bug right now15:06
carl_baldwin#action carl_baldwin will follow up on bug 1388698 with Eugene15:07
carl_baldwin#topic L3 Agent Restructuring15:07
*** openstack changes topic to "L3 Agent Restructuring (Meeting topic: neutron_l3)"15:07
carl_baldwin#link https://review.openstack.org/#/c/131535/ I update the BP15:08
carl_baldwinI haven’t seen much review action on it since the update.15:08
*** Swami has joined #openstack-meeting-315:09
Swamirejoining15:09
pc_mcarl_baldwin: Looks good15:09
*** johnbelamaric has quit IRC15:09
carl_baldwinpc_m: Thank you for your review!  The only one.15:10
SridharRamaswamycarl_baldwin: looks good, switching to inheritance for router types is great15:10
hareeshpcarl_baldwin: yes, I think you have fairly clearly explained the main points.15:10
Swamithe spec is very detailed, but I have not reviewed it completely. Will do.15:10
carl_baldwinSridharRamaswamy: hareeshp:  Thanks.  I look forward to any other feedback that you might have.15:11
carl_baldwinSwami: Thanks.15:11
pc_mcarl_baldwin: I'd like to mention the WIP I have up for review for people to comment on: https://review.openstack.org/#/c/135392/215:11
pc_mcarl_baldwin: It is a stab at taking a small step at teasing out the device driver loading.15:11
carl_baldwinpc_m: Thanks.  I’m sorry I’ve not been over it yet.  I will prioritize that for today.15:12
carl_baldwinI want to discuss functional testing today.15:12
pc_mLooking forward to peoples' thoughts. Trying to take it one piece at a time and hopefully keeping within the goal of the spec.15:12
SridharRamaswamycarl_baldwin: one related question - there are vendor codes in those device-drivers (for VPN, FW, LB) .. is it going to stay in tree and does it move to vendor repo (as proposed by Armando)15:13
carl_baldwinpc_m: Sounds good.15:13
hareeshppc_m: Do you expect this loader to be used by the L3 agent?15:13
SridharRamaswamys/and/or15:13
pc_mhareeshp: yes.15:14
carl_baldwinSridharRamaswamy: I think the ultimate goal is to enable them to move out of tree.  However, moving out of tree is not a goal of this BP.15:14
pc_mhareeshp: it will need to go through some iterations though.15:14
*** elmiko has joined #openstack-meeting-315:14
SridharRamaswamycarl_baldwin: sounds good, perhaps will stay in tree for kilo ?15:15
pc_mhareeshp: Wanted to get the logic out of the individual agents (which are in the L3 agent inheritance hierarchy right now)15:15
hareeshpcarl_baldwin: My understanding is that the vendor code will also be moved to the advanced services repo when that happens15:15
*** jcoufal has quit IRC15:15
carl_baldwinSridharRamaswamy: Not sure.  It could still move out for Kilo.15:15
hareeshppc_m: ok. thanks!15:16
SridharRamaswamycarl_baldwin: okay15:16
carl_baldwinhareeshp: That may be the case.  Moving it is out of scope for this BP.15:16
carl_baldwinamuller: What should be our next action toward getting the functional testing that we need?15:17
hareeshpcarl_baldwin: understood and agreed. I think the loader will be useful exactly for that15:17
pc_mhareeshp: My thoughts were that the L3 agent could call this advanced service loader, where ever it ends up living.15:17
carl_baldwinhareeshp: But, I do see that this work will be key to enabling it to move.15:18
amullercarl_baldwin: I haven't spoken to Adolfo yet. I understand he wrote d/s testing for DVR. We should setup a meeting where we match expectations of what kind of meeting we can push into Neutron right now, and what has to wait for John's full-stack white box testing, and what can go in Tempest15:18
amullerwhat kind of tests*15:18
hareeshpcarl_baldwin: agree15:18
Swamiamuller: agreed, I will ask adolfo to keep in touch with you15:18
amullerSwami: Thanks15:19
SwamiYesterday we had a brief chat about this with Armando as well.15:19
Swamiamuller: What would be the best time to reach you out. Do you prefer IRC meeting or a phone call with adolfo.15:20
amullerI think video chat would be best? Adolfo is based in the west coast? If so then his morning / my evening15:20
*** yamamoto_ has joined #openstack-meeting-315:20
amuller(I work Sunday to Thursday)15:20
SwamiOk, I will send you an update email on the logistics on how we can sync up.15:21
amulleralrighty15:21
carl_baldwinamuller: That limits the time frame down quite a bit.  How late in the evening are you comfortable with?15:21
*** yamamoto has quit IRC15:21
*** xuhanp has quit IRC15:21
amullerI guess 8pm Israel time15:22
*** devvesa has joined #openstack-meeting-315:22
*** seizadi has joined #openstack-meeting-315:22
amullershould be 10 hours ahead of the west coast, if daylight savings is synced nowadays15:22
Swamiamuller: Ok that helps.15:23
carl_baldwinYes, I think DST is all gone now for the year.15:23
*** hurgleburgler has joined #openstack-meeting-315:23
*** otherwiseguy has joined #openstack-meeting-315:23
amulleryeah it's 10 right now15:23
carl_baldwinSwami: Are you going to handle scheduling?  Could you invite me?  I’d like to know how I can help out.15:24
mrsmith_include me as well please15:24
Swamicarl_baldwin: sure15:24
amullerMaru would ideally be there as well but we should schedule the meeting early next week at the latest15:25
carl_baldwinSwami: Thanks.15:25
carl_baldwinamuller: +115:25
SwamiNext week is thanksgiving week. So probably we can have some thing scheduled for either Monday or Tuesday.15:25
carl_baldwinSwami: +1 I’m out Wednesday - Friday15:26
*** Rajeev has joined #openstack-meeting-315:26
carl_baldwinAnything else on refactoring?15:26
carl_baldwin#topic bgp-dynamic-routing15:27
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:27
carl_baldwindevvesa: ping15:27
devvesahello15:27
amullerCarl do you have actionable patches you had in mind that you can split out / paralelize to someone else?15:27
devvesabtw. I just connected now. I can help in refactoring too15:27
carl_baldwin#undo15:27
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x1fb4150>15:28
amullerThat was a weird way of asking if I can help with some of the grunt work of the refactoring15:28
amulleror anyone else15:28
*** hareeshp has quit IRC15:28
carl_baldwinamuller: Great question.  The first step is to break out the services from the L3 agent inheritence.  pc_m is working on VPNaaS.  FWaaS and metadata proxy are the other two.15:29
carl_baldwinamuller: I wonder if you could have a look at the patch by pc_m, provide feedback and look to also break out the metadata proxy.15:30
pc_mI'm trying to do some of the service stuff for all services.15:30
pc_mStarting with device drivers.15:30
*** dthakkar has joined #openstack-meeting-315:31
*** dthakkar has quit IRC15:31
amullerI can handle the metadata stuff, unless Paul you wanted to do that?15:31
*** dthakkar has joined #openstack-meeting-315:32
amullerGenerally though I'm saying maybe Carl you could try to enumerate a list of patches you had in mind,  then we could try to figure out if there are patches that are not dependent15:32
pc_mno go ahead (I don't know anything about it).15:32
amullerthen we hand some work out15:32
carl_baldwinI think we need to move on.  We’re half way through the meeting time.  amuller and pc_m: we’ll sync up on this in the reviews and on IRC.15:32
amullerok15:32
pc_m+115:33
carl_baldwin#topic bgp-dynamic-routing15:33
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:33
carl_baldwindevvesa: ping (again)15:33
*** lhcheng_ has left #openstack-meeting-315:33
devvesahello (again)15:33
devvesanot too much to say. I've been quite busy and I've just have had time to update the few nits from Mathieu15:33
devvesanext monday I will (re)start with the code15:34
carl_baldwinI sent a thread to the Neutron drivers team about the BP.  I got some questions back from them but no big unresolved concerns.15:34
devvesagood. Can I do something about it?15:35
*** zhipeng has joined #openstack-meeting-315:35
carl_baldwinThe biggest concern was that the L3 agent would be disruptive.  But, this BP doesn’t really touch the agent.15:35
devvesaNo, it doesn't.15:36
carl_baldwinI dropped the ball and missed the drivers meeting yesterday.  (I’m not used to the new time yet, I guess)  But, I will be sure to make the next meeting to discuss it.15:36
*** jgrimm is now known as zz_jgrimm15:36
devvesaAre the non-drivers/non-core allowed to participate? I can be there too15:37
carl_baldwindevvesa: It is a public meeting.  It just moved to 1530 on Wednesdays.  I would encourage you to be there too.15:37
devvesaOk. I'll be there15:37
carl_baldwinIt had been at 1500 UTC, same as this meeting.15:38
carl_baldwinThe IPv6 guys showed some interest in dynamic routing for IPv6.  I think that has helped to get some critical mass around it.  I’m hoping the drivers team sees it that way.15:39
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam#Blueprint:_bgp-dynamic-routing_.28devvesa.2C_yamamoto.2C_.2915:40
devvesaUhm.. Maybe I'll ping Sean Collins to take a glance to it then. His feedback can be so useful15:40
carl_baldwinThis link has a lot of good information on the work that devvesa, yamamoto_ and others have already done.15:40
*** asahlin has quit IRC15:40
carl_baldwindevvesa: Yes, that would be great.15:41
devvesa(the link is quite out of date... I will update it)15:41
carl_baldwinThe interest with IPv6 comes from the fact that we have no floating IPs and NAT.  So, we need plain routing to neutron networks.15:42
carl_baldwindevvesa: Updating would be great.  Try to check for out of date content there from time to time.15:42
*** Swami has quit IRC15:42
carl_baldwindevvesa: Anything else on this topic?15:42
*** markmcclain has quit IRC15:43
carl_baldwin#topic neutron-ipam15:43
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:43
carl_baldwinjohnbelamaric_: seizadi: ping15:43
johnbelamaric_hello15:43
devvesacarl_baldin: nothing else. thanks!15:43
johnbelamaric_i saw your comments from yesterday, i will take a closer look today15:44
carl_baldwinI think the discussion in the reviews has been going well.  Thanks for your timely feedback.15:44
johnbelamaric_yes. as you mentioned in the comment i think we may be using different words for the same thing15:44
johnbelamaric_we can discuss in detail on IRC later today or tomorrow after I review the new BP15:45
carl_baldwinI have an update to push.  I made the updates yesterday but didn’t push.  Let me look over it this morning and then push it.15:45
johnbelamaric_ok thansk15:45
*** banix has quit IRC15:45
johnbelamaric_also - i think our subnet allocation use cases is not critical for kilo - our current Icehouse/Juno implementation doesn't do that. but i think it's a useful thing in the long run15:46
carl_baldwinjohnbelamaric_: I’d still like to understand it.  I don’t want to do something to make it more difficult to implement something like that later.15:46
*** markmcclain has joined #openstack-meeting-315:46
johnbelamaric_agreed15:46
*** markmcclain has quit IRC15:46
*** markmcclain has joined #openstack-meeting-315:47
*** johnbelamaric has joined #openstack-meeting-315:47
*** johnbelamaric_ has quit IRC15:47
*** johnbelamaric_ has joined #openstack-meeting-315:48
carl_baldwinjohnbelamaric: I just posted a new version of the proposed interface.15:48
johnbelamaric_i need to try another IRC client - just lost connection - but I am back15:48
johnbelamaric_thanks, i will look today15:48
carl_baldwinjohnbelamaric: Find me on IRC later today.  Google Hangouts works well too.15:48
johnbelamaric_ok15:48
carl_baldwinjohnbelamaric: Anything else?15:48
johnbelamaric_nope15:49
carl_baldwinjohnbelamaric: Thanks!15:49
carl_baldwin#topic neutron-ovs-dvr15:49
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:49
carl_baldwinLooks like we lost Swami15:49
carl_baldwinmrsmith_: Do you have anything?15:49
mrsmith_yes15:50
mrsmith_just wanted to ask about l3 ha and dvr15:50
mrsmith_amuller - is there a patch currently or is this something you've started working on?15:50
mrsmith_or is this something I can help with?15:51
amullerI haven't started and I don't think I will in the next month or so15:51
mrsmith_do you mind if I look into it a bit?15:51
amullerI would kiss your feet15:51
* pc_m :)15:51
amullerSo no I wouldn't mind :)15:51
mrsmith_:)15:51
mrsmith_cool15:51
*** johnbelamaric has quit IRC15:51
carl_baldwinmrsmith_: So, I guess it depends on whether you like having your feet kissed.  ;)15:52
mrsmith_other than that, we are knocking off issues off the l3-dvr-backlog15:52
carl_baldwinmrsmith_: Great.15:52
carl_baldwinmrsmith_: We still need to discuss the manual move.  Will today be good?15:53
mrsmith_ah.. yes... today should be good15:53
mrsmith_I saw your comments on the re-schedule patch15:53
mrsmith_all seem resonable15:53
mrsmith_I am glad you like the new simple approach15:53
carl_baldwinI’ll need to take off for a short time after this meeting to get in to the office.15:53
mrsmith_ (me too)15:54
carl_baldwinmrsmith_: Funny, I can’t even remember making the comments.  I review too much.15:54
carl_baldwinmrsmith_: Okay, ping me later.15:54
carl_baldwin#topic Open Discussion15:54
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:54
mrsmith_I will ping you later on the manual move15:54
*** banix has joined #openstack-meeting-315:55
yamahataHi, I updated spec of module l3 router plugin and uploaded some (WIP) patches.15:55
yamahataI  also update the wiki page according to it.15:56
carl_baldwinyamahata: I saw the update.  Thanks for keeping that up to date.15:56
*** ryansb has joined #openstack-meeting-315:57
*** SridharRamaswamy has quit IRC15:57
*** pballand has joined #openstack-meeting-315:57
*** rohit404 has quit IRC15:57
*** johnbelamaric_ has quit IRC15:58
carl_baldwinI see that I was part way through reviewing the blueprint.  I will finish up that review.15:58
*** johnbelamaric_ has joined #openstack-meeting-315:58
*** eglynn has joined #openstack-meeting-315:59
carl_baldwinWe’re out of time.  Thanks for all your work, everyone.15:59
carl_baldwin#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Thu Nov 20 15:59:50 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-11-20-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-11-20-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-11-20-15.00.log.html15:59
*** ycombinator_ has joined #openstack-meeting-316:00
*** kaufer has joined #openstack-meeting-316:00
*** dboik_ has joined #openstack-meeting-316:01
*** dthakkar has quit IRC16:01
*** johnbelamaric_ has quit IRC16:02
*** carl_baldwin has quit IRC16:02
*** Rajeev has quit IRC16:02
*** dboik_ has quit IRC16:02
*** david-lyle has joined #openstack-meeting-316:02
*** dboik_ has joined #openstack-meeting-316:02
eglynnis this the right channel for the api wg meeting?16:02
elmikoi hope so =)16:03
dtroyerit is according to the calendar on G+16:03
*** pc_m has left #openstack-meeting-316:03
*** devvesa has left #openstack-meeting-316:03
*** dboik has quit IRC16:04
eglynnhmmm, nothing for today on http://eavesdrop.openstack.org/meetings/api_wg/2014/ as yet16:04
*** Ark has joined #openstack-meeting-316:05
*** jogo has left #openstack-meeting-316:05
*** Ark is now known as Guest5678916:05
*** armax has joined #openstack-meeting-316:05
eglynnjaypipes: is the Euro-friendly alternating slot for the API WG kicking off this week?16:05
salv-orlandoperhaps somebody should start the meeting with the appropriate command?16:05
ryansbeglynn: yes, according to the ML16:05
*** marun has joined #openstack-meeting-316:05
jaypipeseglynn, salv-orlando: sorry, I am on a call...16:06
eglynnjaypipes: np16:06
salv-orlandojaypipes: I can start the meeting or wait16:06
jaypipessalv-orlando: please do proceed16:07
salv-orlando#startmeeting api wg16:07
openstackMeeting started Thu Nov 20 16:07:05 2014 UTC and is due to finish in 60 minutes.  The chair is salv-orlando. Information about MeetBot at http://wiki.debian.org/MeetBot.16:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:07
*** openstack changes topic to " (Meeting topic: api wg)"16:07
openstackThe meeting name has been set to 'api_wg'16:07
*** EranGampel has quit IRC16:07
salv-orlandotoday’s agenda: https://wiki.openstack.org/wiki/Meetings/API-WG16:07
*** asahlin has joined #openstack-meeting-316:08
salv-orlandoam I doing a meeting with myself only?16:08
elmikoi hope not16:08
eglynnsalv-orlando: I'm here too16:08
dtroyero/16:09
ryansbI don't think so16:09
ycombinator_o/16:09
eglynnon https://wiki.openstack.org/wiki/API_Working_Group#Members I'm wondering about the proposed cut-off of Nov 15th16:09
eglynni.e. whether this should be extended to allow laggards to join up and get a vote16:10
salv-orlandoeglynn: membership cutoff?16:10
*** silvrax has left #openstack-meeting-316:10
elmikoeglynn: i think we should definitely extend to allow more folks with interest16:10
*** belmoreira has quit IRC16:10
eglynnsalv-orlando: https://review.openstack.org/#/c/131358/5/doc/source/process.rst line 4116:10
eglynnelmiko: ++16:11
dtroyerso pick another arbitrary date?16:11
*** alexpilotti has joined #openstack-meeting-316:11
salv-orlandoI tend to think membership should follow the same processes a getting core status16:11
elmikodtroyer: how about by the end of the first point release for kilo?16:11
eglynnsalv-orlando: currently it's pure self-selection, amiright?16:12
dtroyersalv-orlando: core seems a high bar, maybe ATC status?16:12
elmikoeglynn: that was my impression16:12
salv-orlandodtroyer: sorry I did not meant that one has to be core16:12
salv-orlandodtroyer: I meant membership should be granted/revoked using the same principle as the core teams16:12
dtroyerelmiko: I do like tying it to part of the release cycle, or a certain time following the summit, as that's probably where the bulk of new interest will come16:12
eglynnelmiko: i.e. the kilo-1 date? i.e. Dec 18th ... seems like fair notice16:12
dtroyersalv-orlando: understood, but that is still a high bar16:13
ryansbI think self-selection with recommended core status is a good system16:13
salv-orlandoand therefore the group should always be open to accept new members, and kick off inactive members16:13
*** adrian_otto has joined #openstack-meeting-316:13
salv-orlandosorry not kick off, kick out16:13
salv-orlandophrasal verbs, I’ll never get them right16:13
adrian_ottoo/16:13
dtroyermaybe use review counts as a threshold?16:13
dtroyerno reviews == not participating16:13
salv-orlandodtroyer: that is a good idea. Still with human oversight rather than automated16:14
dtroyersure, but having at least one metric should be helpful16:14
salv-orlandodtroyer: makes sense to me16:14
eglynndtroyer: yep, good to a first approximation at least16:14
elmikoi think it would be nice to see folks who are interested either reviewing or showing up to meetings16:14
dtroyeris the notion that there is a fixed membership for the release cycle part of what was intended there?16:15
eglynnunfortunately no api-wg stats on http://stackalytics.com16:15
eglynnI don't know, but the process seems to involve setting the bar at 80% of the votes16:16
dtroyeractually, maybe that is only for the first cycle, during L we can look at the history fro Kilo16:16
salv-orlandoeglynn: that can be sorted fairly easily I think. stackalytics I think uses russellb reviewstats code, I recall it was trivial to add new repos16:16
elmikodtroyer: i thought the intent was to have a list of people who had early committed to the goals of the wg, and use that list as the first group of "core", although i hate to say that, members16:16
*** dboik_ has quit IRC16:16
russellbsalv-orlando: nope, stackalytics is separate16:17
russellbthere is a file in the stackalytics repo you have to hack to add a project i think16:17
salv-orlandorussellb: ok. Then they’ve copied your idea and you should sue them!16:17
russellb:)16:17
russellbthey made it prettier at least16:17
salv-orlandorussellb: so it’s not that different from reviewstats16:17
russellbbut reimplemented16:17
*** dboik has joined #openstack-meeting-316:17
eglynn#action eglynn propose stackalytics patch to generate api-wg review stats16:18
salv-orlandogreat. Regarding cut off date for membership, if this is a measure for this release cycle only, I am ok with that. In any case I have no strong opinion16:19
*** sigmavirus24 is now known as sigmavirus24_awa16:19
salv-orlandoand also it’s not like my opinion counts that much ;)16:19
*** shwetaap has quit IRC16:20
elmikosalv-orlando: it counts as much as the rest of our +1s ;)16:20
salv-orlandoAs apparently I am chairing this meeting, I have now to ask you if we have consensus or if we want to go back to the ml16:21
eglynnsalv-orlando: I'm fine with a cut-off also if punted into the future by a few weeks and clearly signalled on the ML16:21
salv-orlandoas jaypipes, cyeoh, and everett are not part of the meeting I will follow up the discussion on the maling list and move on with the next topic16:22
elmikoaside from consensus here, it sounds like we need a patch to the https://review.openstack.org/#/c/131358/5/doc/source/process.rst review16:22
*** shwetaap has joined #openstack-meeting-316:22
jaypipessalv-orlando: thx man, sorry I can't participate right now :(16:23
salv-orlando#info decision on membership cut-off date and process deferred to mailing list16:23
eglynnelmiko: yep if no one objects on the ML to kilo-1 as the new date, that could be rolled into the next version of that patchset16:24
elmikoeglynn: i'm gonna add a comment to that review as well16:24
eglynnelmiko: cool, thanks!16:24
*** hinnant has joined #openstack-meeting-316:24
*** bpokorny has joined #openstack-meeting-316:24
salv-orlando#topic API impact reviews16:25
*** openstack changes topic to "API impact reviews (Meeting topic: api wg)"16:25
adrian_ottosorry if I missed it earlier, but is there a link to this gerrit review queue you can share?16:25
salv-orlandohttps://review.openstack.org/#/q/status:open+AND+(message:ApiImpact+OR+message:APIImpact),n,z16:25
*** dboik has quit IRC16:25
salv-orlandoadrian_otto: This is the gerrit review list for spec with an api impact flag16:26
dtroyeradrian_otto: the overall gerrit queue is at https://review.openstack.org/#/q/project:openstack/api-wg,n,z16:26
*** dboik has joined #openstack-meeting-316:26
adrian_ottotx16:26
*** dboik has quit IRC16:27
salv-orlandoany comment on specs with API impact flag?16:27
*** dboik has joined #openstack-meeting-316:28
*** otherwiseguy has quit IRC16:28
*** mrsmith_ has quit IRC16:28
adrian_ottohow will API WG members become aware of reviews with that flag set?16:28
ryansbadrian_otto: there's a gerrit query16:28
eglynnmanually running that query?16:29
eglynnyeap, that's what I assumed16:29
ryansbhttps://review.openstack.org/#/q/status:open+AND+(message:ApiImpact+OR+message:APIImpact),n,z16:29
*** dboik_ has joined #openstack-meeting-316:29
adrian_ottowhat about a system by which we can learn about them passively?16:29
*** zz_jgrimm is now known as jgrimm16:29
eglynnso should we concentrating on first creating the guidelines, as opposed to applying them to APIImpact reviews?16:29
ryansbhow would you want that to work. Do you just want an email every X days with a rollup of apiimpact reviews?16:29
*** sigmavirus24_awa is now known as sigmavirus2416:29
adrian_ottothanks ryansb16:29
elmikoi have also been telling the members of our project(Sahara) that they should post to the ML with [api] to request more eyeballs16:29
*** dboik_ has quit IRC16:30
adrian_ottosomething like that would be fine.16:30
*** dboik_ has joined #openstack-meeting-316:30
adrian_ottoI worry that we are focusing in our various areas of interest, and that important issues even properly flagged might not be noticed16:30
elmikoadrian_otto: good concern, at the same time though we aren't trying to create a gating process through the api-wg16:30
adrian_ottoAgreed, I am not suggesting a gate16:31
elmikoi think it's important for the individual projects to take initiative in contacting the wg for help16:31
dtroyereglynn: I'd say yes, but getting acquainted with the reviews out there now is useful to see where the current churn is and will help get the right people involved sooner.16:31
*** seizadi has quit IRC16:31
salv-orlandoI think even without guidelines the api wg team should strive to look at these apiimpact specs and make sure we don’t end with two projects doing the same thing in two different ways16:31
elmikosalv-orlando: +116:31
elmikoi really like ryansb's idea of posting to the ML every X days with a list of reviews16:32
*** carl_baldwin has joined #openstack-meeting-316:32
*** dboik has quit IRC16:32
adrian_ottoif part of our role was to act like a bird dog in situations where the guidelines are totally missed… perhaps that could result in a good outcome16:32
elmikoagreed16:33
adrian_ottowe can use a relatively high value of X to start with… maybe 7?16:33
ryansbNot sure if automatic mail to the whole ML is a great idea16:33
adrian_ottosomething you can opt in to?16:33
ryansbMuch rather have folks sign up (maybe to another ML?)16:33
elmikoryansb: that makes sense16:33
ryansbI think this is bikeshedding though, so can we take this to openstack-dev after the meeting?16:33
elmikowill it be too burdensome for infra to create/manage one more ML?16:34
salv-orlandoI have a script that reminds me everyday of the reviews I should do, tells me if somebody updated that review, and also tells me what to review according to the day of the week16:34
elmikoryansb: yea16:34
salv-orlandoso I don’t think we need any ml… there’s also a tool called gerrymander16:34
salv-orlandowhich pretty much does exactly this16:34
ryansbsalv-orlando: ah, I'd forgotten gerrymander. Would you be able to share your script?16:35
*** baoli has joined #openstack-meeting-316:36
salv-orlandoit’s somewhere on github.com/salv-orlando16:36
adrian_ottoso if we are lost in the bike shed, please lead us back to the house16:37
ryansbI'll scavenge later. Let's move on. The next thing on the agenda seems to be https://review.openstack.org/#/c/131358/516:37
salv-orlando#topic process for merging guideline changes16:38
*** openstack changes topic to "process for merging guideline changes (Meeting topic: api wg)"16:38
*** jgallard_ has joined #openstack-meeting-316:38
eglynnsounds a bit heavyweight TBH, all that voting16:38
eglynnand the TC approval would give me pause also16:39
salv-orlandoI think point #2 sums up fairly well the concept of lazy consensus. But I would add that -1s for spelling errors or grammar corrections can be ignored16:39
eglynn(seeing as TC seem to want to get out of the business of blessing things)16:39
*** jgallard has quit IRC16:39
elmikoeglynn: i dunno, if we are talking about guidelines for all projects i tend towards the more conservative approach. but i'm curious to hear alternative ideas.16:40
eglynnelmiko: if the consensus is that the TC will actively engage and either approve or give constructive feedback, then cool16:41
*** ChuckC has quit IRC16:41
elmikoeglynn: +2 that would be awesome. i agree about not just using them as a blessing operation for the guidelines.16:42
salv-orlandoeglynn: I don’t know… if the TC wants to be in the business of operators’ happiness maybe they should have a say on API guidelines. Or on other hand, they can trust the API wg16:42
ryansbI think that's a lot to ask of the tc. A veto system would probably be more workable16:42
*** johnbelamaric has joined #openstack-meeting-316:42
salv-orlandoryansb: that too is not such a bad idea16:42
ryansb(for guidelines)16:42
elmikoryansb: i think it would need to be veto with explanation though, not just a blanket16:42
salv-orlandolike the TC would be able to stop something when they think it’s a terrible idea16:42
salv-orlandoelmiko: yes they would not be like the US at the UN16:42
eglynnsalv-orlando: yep, I think they should just trust the WG as the "domain experts"16:42
elmikosalv-orlando: lol, true that ;)16:43
eglynnryansb: yep, silence means consent ... I like it! :)16:43
dtroyerI think the blessing from the TC would be of the form "WG is doing good work, we like that" rather than release-level approval16:43
adrian_ottoare we striving for unanimity in voting? Why?16:43
dtroyereglynn: ++16:43
salv-orlandook so what can we put as action items or info items for this topic?16:44
elmikoadrian_otto: according to the review we are striving for 80% approval16:44
eglynnadrian_otto: coz we, as a community, value consensus ... though perhaps in this case, we really do need to be opinionated?16:44
*** jgallard_ has quit IRC16:44
adrian_ottothis seems more complicated than it needs to be16:44
ryansbdtroyer: I'm not in the business of saying how TC should operate, but I do think that asking for a lot of approvals/supervision isn't a fair demand on them16:44
*** Longgeek has quit IRC16:45
elmikoadrian_otto: maybe, what would you like see for approval process?16:45
dtroyerryansb: exactly, they have been actively trying to back away from that sort of thing (see defcore)16:45
salv-orlandoryansb: I think dtroyer eas just saying that the TC will prefer to delegate the task of blessing guidelines to the api group16:46
elmikodtroyer, ryansb, doesn't that just add weight to the silence/veto-with-explanation option?16:46
eglynnthe graduation debates on say zaqar would give me pause on baking pass/fail release-level TC approval into the workflow16:47
eglynnelmiko: ++16:47
ryansbto be clear, I'm totally in favor of silence-or-veto16:47
eglynnryansb: cool16:47
salv-orlandoalso, about this veto thing… adding it as part of the process is ok, but in any case even if we did not do that16:47
elmikocool, sounds like we need another patch to that review16:48
salv-orlandoit’s not like if somebody like monty, for instance, came and told us: this is terrible, we’d ignore him/her because they’re not part of the group16:48
dtroyerelmiko: implicitly, yes.  From what I've seen though is that if TC is unhappy with something they'll either work individually to address the issue first16:48
*** hareeshp has joined #openstack-meeting-316:48
*** SridharRamaswamy has joined #openstack-meeting-316:49
elmikosalv-orlando: good point, but in that case i would still expect changes to percolate through the review process16:49
salv-orlandomake sense to me.16:49
elmikodtroyer: good info, i haven't worked directly with TC so i'm a little blind in terms of how they operate when something is important to them16:50
*** otherwiseguy has joined #openstack-meeting-316:50
elmikoi just like the idea of codifying the process for transparency sake16:50
salv-orlandoso can we be cool and agree that we welcome contribution and feedback from the TC, but we probably think it will be too much of a workload for them to have their approval as a prerequisite for every guideline16:50
elmikosalv-orlando: +116:50
salv-orlandoand that the api wg will however accepts vetos (with explanations) from the TC?16:51
eglynnthe important thing is for us not to get into a situation whereby the TC turn around to us at the end of kilo and say: "wait a minute, that's not what we were expecting at all!"16:51
dtroyersalv-orlando: I'd suggest just removing line 49.  the WG relationship to the TC should be described somewhere (I haven't looked) and that ought to cover this16:51
eglynnso we should build a "timely feedback" requirement into the silence-or-veto IMO16:51
elmikoeglynn: yea, that would be bad. but how do we increase their involvement without either loading them up to much, or making them the gate for all changes?16:52
eglynnelmiko: maybe milestone checkpoints?16:52
elmikoeglynn: i like that16:52
salv-orlandoanybody disagrees with dtroyer’s observation?16:52
dtroyerelmiko: I think some time before a release we get n the TC agenda and say "this is our RC, comments?"16:52
*** hareeshp has quit IRC16:52
eglynndtroyer: +1 on removing16:53
adrian_ottotime check16:53
salv-orlando#info attendees suggest to remove line 49 from https://review.openstack.org/#/c/131358/5/doc/source/process.rst (mandatory tc approval)16:53
elmikodtroyer: +1 to remove and clarify elsewhere16:53
adrian_otto+116:53
adrian_ottoI voted in Gerrit accordingly16:53
*** mageshgv has joined #openstack-meeting-316:53
eglynn#info stackalytics patch: https://review.openstack.org/13604616:53
salv-orlando#info attendees also suggest to clarify TC relationship with API WG elsewhere16:54
elmikodtroyer: and yea, i like the idea of giving them a time window in which we ask if they are cool with everything16:54
salv-orlandothanks eglynn16:54
adrian_ottoplus grammar is spelled wrong.16:54
adrian_ottounless that's a spelling from a language I don't speak16:54
*** shwetaap has quit IRC16:54
*** shwetaap has joined #openstack-meeting-316:55
salv-orlando5 minutes to go16:55
salv-orlando#topic open discussion16:55
*** openstack changes topic to "open discussion (Meeting topic: api wg)"16:55
salv-orlandothis is where one usually brings up crazy ideas or rants about random things...16:56
dtroyerhttps://review.openstack.org/#/c/131640/ was on the agenda, seems uncontroversial, should we #info stamp it?16:56
elmikojust as a follow-up from summit, i have been making some progress on implementing a swagger generator for sahara. i'm hoping to have a poc within a few weeks16:56
*** emagana has joined #openstack-meeting-316:57
salv-orlandodtroyer, yes if nobody disagrees with that. I have to admit I wilfully skipped it.16:58
*** amuller has left #openstack-meeting-316:58
dtroyersalv-orlando: np16:58
*** evgenyf has quit IRC16:59
*** dboik_ has quit IRC16:59
*** dboik has joined #openstack-meeting-317:00
salv-orlandotime’s up!17:00
eglynnthanks folks for a productive meeting!17:00
salv-orlando#info no attendees disagrees with approving 13164017:00
salv-orlandothanks for your time and goodbye17:00
salv-orlando#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Thu Nov 20 17:00:52 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2014/api_wg.2014-11-20-16.07.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2014/api_wg.2014-11-20-16.07.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2014/api_wg.2014-11-20-16.07.log.html17:00
elmikosalv-orlando: thanks for chairing =)17:01
*** dboik has quit IRC17:01
*** ryansb has left #openstack-meeting-317:01
*** kaufer has left #openstack-meeting-317:01
*** dboik has joined #openstack-meeting-317:01
*** Guest27879 is now known as redrobot17:04
*** MaxV has quit IRC17:06
*** markmcclain has quit IRC17:06
*** dtroyer has left #openstack-meeting-317:06
*** MaxV has joined #openstack-meeting-317:07
*** hareeshp has joined #openstack-meeting-317:07
*** banix has quit IRC17:07
*** yamamoto_ has quit IRC17:09
*** markmcclain has joined #openstack-meeting-317:11
*** hareeshp has quit IRC17:11
*** johnbelamaric has quit IRC17:12
*** johnbelamaric has joined #openstack-meeting-317:12
*** johnbelamaric has quit IRC17:12
*** dboik has quit IRC17:12
*** markmcclain has quit IRC17:15
*** yamahata has quit IRC17:16
*** rhagarty has quit IRC17:18
*** ChuckC has joined #openstack-meeting-317:19
*** rhagarty has joined #openstack-meeting-317:19
*** Viswanath has joined #openstack-meeting-317:24
*** safchain has quit IRC17:25
*** rhagarty has quit IRC17:25
*** baoli has quit IRC17:26
*** emagana has quit IRC17:27
*** Viswanath has quit IRC17:27
*** emagana has joined #openstack-meeting-317:27
*** emagana has quit IRC17:28
*** nelsnels_ has joined #openstack-meeting-317:28
*** nelsnels_ has quit IRC17:28
*** emagana has joined #openstack-meeting-317:29
*** nelsnels_ has joined #openstack-meeting-317:29
*** nelsnelson has quit IRC17:29
*** banix has joined #openstack-meeting-317:34
*** rhagarty has joined #openstack-meeting-317:34
*** otherwiseguy has quit IRC17:35
*** otherwiseguy has joined #openstack-meeting-317:36
*** baoli has joined #openstack-meeting-317:37
*** MaxV has quit IRC17:37
*** johnbelamaric has joined #openstack-meeting-317:42
*** s3wong has joined #openstack-meeting-317:42
*** mwang2 has joined #openstack-meeting-317:43
*** johnbelamaric has quit IRC17:43
*** matrohon has quit IRC17:43
*** johnbelamaric has joined #openstack-meeting-317:44
*** mwang2_ has joined #openstack-meeting-317:48
*** SridharRamaswamy has quit IRC17:51
*** mwang2 has quit IRC17:51
*** rkukura has joined #openstack-meeting-317:53
*** hemanthravi has joined #openstack-meeting-317:53
*** SumitNaiksatam has joined #openstack-meeting-317:55
*** emagana has quit IRC17:56
*** Guest56789 has quit IRC17:57
*** emagana has joined #openstack-meeting-317:57
*** elmiko has left #openstack-meeting-317:58
*** ycombinator_ has quit IRC18:00
*** Ark has joined #openstack-meeting-318:01
*** Ark has quit IRC18:01
SumitNaiksatamrkukura: igordcard hemanthravi s3wong banix: hi18:01
rkukurahi18:01
hemanthravihi18:01
igordcardHello SumitNaiksatam !18:01
s3wonghello18:01
*** emagana has quit IRC18:01
banixhi18:01
SumitNaiksatamlets get started18:01
SumitNaiksatam#startmeeting networking_policy18:02
openstackMeeting started Thu Nov 20 18:02:06 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: networking_policy)"18:02
openstackThe meeting name has been set to 'networking_policy'18:02
*** Youcef has joined #openstack-meeting-318:02
SumitNaiksatam#info meeting agenda https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy#Nov_20th.2C_201418:03
*** ivar-lazzaro has joined #openstack-meeting-318:03
s3wongno agenda for today's meeting :-)18:04
SumitNaiksatams3wong: refresh :-)18:04
SumitNaiksatamas we are getting closer to the wrapping up the features, we need to start tracking bugs, packaging, etc18:04
SumitNaiksatamso i have proposed a standing agenda for the meetings18:05
s3wongSumitNaiksatam: I need to drop off @10:30am, so if there is any update for me, would you mind putting me up earlier? Thanks18:05
SumitNaiksatam*standing items18:05
*** emagana has joined #openstack-meeting-318:05
SumitNaiksatams3wong: sure18:05
SumitNaiksatamwill try to get to that quickly18:05
*** ivar-lazzaro has quit IRC18:05
SumitNaiksatamplease feel free to add any other standing items as you deem relevant18:05
SumitNaiksatambtw, any announcements that anyone would ike to share?18:06
*** rms_13 has joined #openstack-meeting-318:06
*** ivar-lazzaro has joined #openstack-meeting-318:06
SumitNaiksatam#topics Bugs18:06
SumitNaiksatamwe have a long list of bugs that we need to start triaging and knocking off (by triaging i mean find owners)18:07
SumitNaiksatamit will be difficult to do that bug scrub in this meeting today18:07
SumitNaiksatambut i think as a practice we need to at least bring up the pending “critical” bugs in the meetings every week18:07
SumitNaiksatami would regard critical bugs as show stoppers, so they should be fixed asap18:08
SumitNaiksatam#link https://bugs.launchpad.net/group-based-policy/+bug/138863518:08
SumitNaiksatamivar-lazzaro: had posted a fix for this18:09
ivar-lazzaroSumitNaiksatam: thanks for bringing this up!18:09
SumitNaiksatam#bug 138863518:09
SumitNaiksatamoh wait, we probably dont have the bot for this meeting18:09
SumitNaiksatam“intra EPG connectivity not working"18:09
*** yamamoto has joined #openstack-meeting-318:10
SumitNaiksatamivar-lazzaro: did you link the patch to the LP bug?18:10
ivar-lazzaroSumitNaiksatam: checking18:10
mageshgvivar-lazzaro:wrong bugid is referenced on the patch18:11
SumitNaiksatamhttps://bugs.launchpad.net/group-based-policy/+bug/138863518:11
ivar-lazzaroSumitNaiksatam: yep, I have it linked to #1387981 and #138863518:11
SumitNaiksatammageshgv: ah18:11
mageshgvhttps://review.openstack.org/#/c/132485/18:11
SumitNaiksatammageshgv: thanks catching that, and also thanks for joining, its a fairly late hour for you!18:11
mageshgvsumitNaiksatam: no problem18:12
ivar-lazzaroOh that's the wrong topic18:12
SumitNaiksatamivar-lazzaro: gerrit link?18:12
ivar-lazzaro#link https://review.openstack.org/#/c/132485/18:12
banixi think the way bug is referred to is incorrect18:12
banixthat’s why it doesnt show on LP18:12
SumitNaiksatambanix: yeah, just dont need to prefix “bug/“18:13
ivar-lazzaroyup18:13
ivar-lazzaroI'll update asap18:13
*** dboik has joined #openstack-meeting-318:13
SumitNaiksatamok anyway, but ivar-lazzaro promptly posted this fix on nov 2nd, but we are delinquent on the reviews18:13
SumitNaiksatamnot a good idea to let a critical sit around for that long! :-(18:14
*** yamamoto has quit IRC18:14
SumitNaiksatamkindly help review18:14
mageshgvSumitNaiksatam: I will review it tomorrow18:15
SumitNaiksatammageshgv: great thanks, i will try to give it a shot today as well18:15
SumitNaiksatamwe will need at least one more core to look at it asap18:15
s3wongSumitNaiksatam: I will take a look also18:16
SumitNaiksatams3wong: your updates fix is a bug fix or a bp?18:16
SumitNaiksatams3wong: thanks18:16
hemanthraviSumitNaiksatam, i'll review ivar's fix18:16
SumitNaiksatamhemanthravi: thanks18:16
s3wongSumitNaiksatam: given that the fix has changes on resource mapping driver18:16
s3wongSumitNaiksatam: I think we classified it as a "bug"18:17
SumitNaiksatams3wong: okay18:17
SumitNaiksatams3wong: so that goes against #link https://bugs.launchpad.net/group-based-policy/+bug/1383941 ?18:17
*** david-lyle has quit IRC18:17
SumitNaiksatam“rmd update rules operations”18:17
s3wongSumitNaiksatam: yes, the description seems to fit18:17
SumitNaiksatams3wong: ok cool, so keep that in mind, that will be one high priority bug knocked off!18:18
s3wongSumitNaiksatam: and it is assigned to ivar-lazzaro :-)18:18
s3wongSumitNaiksatam: sure, working on it now with the latest branch (with the name changes)18:18
SumitNaiksatams3wong: sweet!18:18
SumitNaiksatamso in the next few days i will reach out to folks in the team and do some bug assignments18:19
SumitNaiksatamwe got scrub the entire list18:19
SumitNaiksatam*got to18:19
s3wongSumitNaiksatam: shooting for patch in gerrit early next week18:19
SumitNaiksatams3wong: good18:19
SumitNaiksatamso if you are uncomfortable with the assignment, please free to unassign it18:19
SumitNaiksatamany other bugs that we need to discuss right now?18:19
SumitNaiksatamok moving on18:20
*** johnbelamaric1 has joined #openstack-meeting-318:20
SumitNaiksatami will change the order of the agenda to accomodate s3wong’s request18:20
*** johnbelamaric has quit IRC18:20
SumitNaiksatam#topic New policy drivers18:20
*** openstack changes topic to "New policy drivers (Meeting topic: networking_policy)"18:20
*** johnbelamaric has joined #openstack-meeting-318:20
SumitNaiksatamon the ODL driver, some of us having been working in the background to get this going18:21
SumitNaiksatams3wong: based on the discussions we will need to update the spec18:21
s3wongSumitNaiksatam: yes18:21
SumitNaiksatams3wong: any other update from you on that front?18:21
*** dboik has quit IRC18:22
s3wongSumitNaiksatam: looked into ODL ML2 mechanism driver to see how OpenStack connects to ODL controller18:22
*** adrian_otto has left #openstack-meeting-318:22
SumitNaiksatams3wong: okay18:22
*** emagana has quit IRC18:22
*** hareeshp has joined #openstack-meeting-318:22
SumitNaiksatams3wong: we can discuss offline18:22
SumitNaiksatamNuage driver18:22
SumitNaiksatamrms_13: there?18:22
SumitNaiksatams3wong: thanks for the update18:22
rms_13yes18:22
*** emagana has joined #openstack-meeting-318:23
s3wongSumitNaiksatam: also, looked at ivar-lazzaro 's APIC driver to see how the gbp mapping db is being used for the L2/3 policy + EP/EPG mapping18:23
SumitNaiksatams3wong: feel free to take off whenever convenient ;-)18:23
SumitNaiksatams3wong: yes, also one convergence driver does something similar (overloading the resource mapping driver)18:23
s3wongSumitNaiksatam: sure, I have another meeting in 7 minutes.. have fun, guys!18:23
SumitNaiksatams3wong: thanks18:23
*** wuhg has quit IRC18:23
*** johnbelamaric2 has joined #openstack-meeting-318:23
*** johnbelamaric has quit IRC18:24
SumitNaiksatamrms_13: sorry, you planning another rev on the spec?18:24
rms_13Yes. ETA tomorrow.18:24
rms_13Hopefully the code will land by Monday as well18:24
*** johnbelamaric has joined #openstack-meeting-318:24
SumitNaiksatamrms_13: sweet, was just about to ask!18:24
rms_13Got caught up in some internal nuage thing18:24
SumitNaiksatamrms_13: np18:24
*** johnbelamaric1 has quit IRC18:24
rms_13No its on my TODO list...will get it18:24
SumitNaiksatamrms_13: any blockers for you, any additional information you need?18:24
rms_13None so far. Will have more questions probably starting tomorrow...will ask offline18:25
SumitNaiksatamrms_13: perhaps it might help for you to follow the ODL dicussion18:25
*** otherwiseguy has quit IRC18:25
SumitNaiksatamrms_13: ok sure18:25
rms_13cool. thx18:25
SumitNaiksatambanix: hi there18:25
SumitNaiksatambanix: any update on the IBM driver?18:25
banixSumitNaiksatam: i do not think it will be happening in this cycle18:25
SumitNaiksatambanix: okay np18:26
SumitNaiksatambanix: you can still submit the spec against kilo18:26
banixSumitNaiksatam: sure18:26
SumitNaiksatambanix: some other specs have already been submitted targeted for kilo18:26
SumitNaiksatambanix: thanks18:26
SumitNaiksatamanyone else planning anything around the vendor drivers?18:27
*** hareeshp has quit IRC18:27
SumitNaiksatamwe will touch on the driver extensions in the bp topic18:27
SumitNaiksatamok18:27
SumitNaiksatam#topic Feature blueprints18:27
*** openstack changes topic to "Feature blueprints (Meeting topic: networking_policy)"18:27
SumitNaiksatamso update at my end - the renaming on the client and server is completed18:28
SumitNaiksatamfor better or worse!18:28
*** johnbelamaric2 has quit IRC18:28
SumitNaiksatamso we can officially start talking in terms of PT, PTG and PRS!18:28
ivar-lazzaroSumitNaiksatam: yey!18:28
* SumitNaiksatam cant’ see to get contracts out of his system! :-(18:29
SumitNaiksatamivar-lazzaro: :-)18:29
SumitNaiksatamapologies to everyone else who had to rebase their patches on account of this change18:29
SumitNaiksatamivar-lazzaro: mostly they were your patches18:29
SumitNaiksatamHeat renaming patches are already in review18:30
SumitNaiksatamhemanthravi: are you on the hook for those?18:30
hemanthraviSumitNaiksatam, yes will review the heat patches18:30
SumitNaiksatamand osm?18:30
hemanthraviwill check with osm18:31
SumitNaiksatamhemanthravi: ok, lets get this rolling asap18:31
*** bpokorny_ has joined #openstack-meeting-318:31
*** SridharRamaswamy has joined #openstack-meeting-318:31
SumitNaiksatamthe horizon patches have not yet been submitted, i had expected them to be submitted today18:31
SumitNaiksatamthe renamin is however finished in uday’s branch18:32
SumitNaiksatami will update the devstack so that we can get horizon and heat working as well with the renaming18:32
SumitNaiksatamthere are three other major features/bps that we are targeting18:32
*** Ark has joined #openstack-meeting-318:32
SumitNaiksatamfirst one is resources’ sharing18:33
*** Ark is now known as Guest7626518:33
SumitNaiksatam#link https://review.openstack.org/13360318:33
*** bpokorny has quit IRC18:33
SumitNaiksatamsecond one is for external connectivity18:33
SumitNaiksatamthis spec has not been submitted18:33
SumitNaiksatamthe first one is required for the second18:33
SumitNaiksatamivar-lazzaro: you are leading both of those?18:33
ivar-lazzaroSumitNaiksatam: yes18:33
SumitNaiksatamivar-lazzaro: okay, brave! :-)18:34
ivar-lazzaroSumitNaiksatam: I've already posted a patch for the shared attribute, and I'm still working on a spec for the external connectivity18:34
SumitNaiksatamivar-lazzaro: the resources’ sharing spec has some review comments18:34
ivar-lazzaroSumitNaiksatam: :)18:34
ivar-lazzaroSumitNaiksatam: yes I'll address them by today18:35
SumitNaiksatami would like to make one high level clarification here18:35
*** hemanthm has left #openstack-meeting-318:35
SumitNaiksatamthe proposal is to make a change to the resource model (in terms of sharing of all resources)18:35
SumitNaiksatamhowever, it is not mandatory for all drivers to support this18:35
SumitNaiksatamif a particular driver does not support it, in this first iteration of GBP, the driver should throw an not-implemented exception18:36
*** dboik has joined #openstack-meeting-318:36
SumitNaiksatamivar-lazzaro: please capture this in the spec18:36
ivar-lazzaroSumitNaiksatam: sure18:36
*** eglynn has quit IRC18:37
SumitNaiksatamthis includes the neutron resource mapping driver, which has limited sharing capabilities18:37
SumitNaiksatamany questions/thoughts on the above two18:37
*** dboik_ has joined #openstack-meeting-318:37
SumitNaiksatami guess its difficult to talk about the external connectivity since there is no spec yet18:37
SumitNaiksatambut i believe the idea is to introduce additions to the model so as to model the “external world"18:38
SumitNaiksatamivar-lazzaro: is that fair summary?18:38
ivar-lazzaroSumitNaiksatam: perfect :)18:39
SumitNaiksatamok18:39
SumitNaiksatamthe third major feature is the “extensions loading via drivers"18:39
SumitNaiksatamrkukura: your turn18:39
rkukuranothing new on this - its been on hold, but I should be able to resume working on it today or tomorrow18:40
SumitNaiksatamrkukura: sweet!18:40
*** carl_baldwin has quit IRC18:40
SumitNaiksatamso if you are planning on using this in your vendor drivers, its coming soon! :-)18:40
*** dboik has quit IRC18:41
SumitNaiksatamthe other logistical detail that i wanted to bring up18:41
SumitNaiksatamyou should be seeing a “kilo” branch in the specs shortly18:41
SumitNaiksatamso the specs which are not targeting for Juno, and have already been submitted, should be moved to kilo18:42
SumitNaiksatamis louis or cathy here?18:42
SumitNaiksatamokay i will reach out to them18:42
SumitNaiksatam#action SumitNaiksatam to reach out to Louis to move gerrit specs to kilo18:43
igordcardSumitNaiksatam, the same goes for TS right?18:43
SumitNaiksatamigordcard: yes, and we will discuss right after this meeting as well18:43
SumitNaiksatamigordcard: thanks for bringing that up18:43
SumitNaiksatamanything else on the specs?18:43
*** markmcclain has joined #openstack-meeting-318:43
SumitNaiksatamok18:44
SumitNaiksatam#topic Packaging18:44
*** openstack changes topic to "Packaging (Meeting topic: networking_policy)"18:44
SumitNaiksatamrkukura: over to you18:44
rkukuraOK, I’ve been working on the Fedora packaging, which will then be the basis for RDO and RHOS packaging on RHEL18:44
SumitNaiksatamrkukura: nice!18:45
SumitNaiksatamrkukura: were you able to get past that setup issue?18:45
*** markmcclain has quit IRC18:45
rkukuraI’ve got server and client packages that install, but working on missing files that prevent the gbp-db-manage from succeeding18:45
rkukuraplus a bunch of other small packaging fixes18:45
rkukuraI’m currently using pre-rename commits, so I can do horizon and heat as well18:46
SumitNaiksatamrkukura: ah good18:46
rkukurabut will switch to latest once we have renaming complete18:46
SumitNaiksatamrkukura: so that you way you would have ironed out the packaging issues18:46
SumitNaiksatamrkukura: and then we can iterate with regards to actual contents of the packages18:47
rkukurathe packages then need to go through a formal Fedora review process, but I’ve been working with the reviewer, so it shouldn’t take long18:47
rkukuraMy goal is to make sure the API operations work with the initial packages that are reviewed18:47
*** markmcclain has joined #openstack-meeting-318:48
rkukuraI’ll be filing a bug and posting a fix for files missing in the groub-based-policy repo when “python setup.py install” is run.18:48
SumitNaiksatamrkukura: okay18:48
rkukurathats about it on Fedora18:48
rkukuraI will also put up an RDO wiki page with instructions18:48
SumitNaiksatamrkukura: so in terms of timelines, what is the latest that you can package fedora?18:49
rkukuraI can point these instructions initially at RPMs I’ve built and will put on fedorapeople.org18:49
SumitNaiksatamrkukura: i mean having to account for the review process, etc.18:49
rkukuraSumitNaiksatam: not sure what you mean by “latest”?18:49
rkukuraI will get at least the client and server into review this week, hopefully all four18:49
SumitNaiksatamrkukura: but between now and dev 19th we will be adding features and fixing bugs18:50
rkukuraRight, we can update the packages at any point to newer upstream commits18:50
SumitNaiksatamrkukura: so new packages will be generated for those?18:50
*** alexsyip has joined #openstack-meeting-318:51
*** jacalcat has left #openstack-meeting-318:51
SumitNaiksatamrkukura: okay good18:51
rkukuraThe initial packages will be 2014.2-0.1, then we bump to 2014.2.0.218:51
SumitNaiksatamrkukura: got it18:51
rkukuraOfficial Juno will be 2014.2-118:51
rkukuraso we can have as many pre-release versions as we need18:51
SumitNaiksatamrkukura: ok good, so they have a convention for this18:52
*** eglynn has joined #openstack-meeting-318:52
SumitNaiksatamrkukura: thanks for the update, looks promising! :-)18:52
rkukurayes - the ordering of the version strings is critical so newer always replaces older on updates18:52
SumitNaiksatamany questions for rkukura?18:52
SumitNaiksatamrkukura: got it, makes sense18:52
rkukuraOne thing - do we have an upstream version for python-gbpclient?18:53
SumitNaiksatamrkukura: by upstream you mean, pypi?18:53
rkukuraI mean like the 2.x.y version on python-neutronclient, etc.18:53
rkukuraThe client libs don’t use the 2014.2 release versioning18:53
*** dboik_ has quit IRC18:54
SumitNaiksatamrkukura: okay, but that 2.x.y is an consequence of the package being present in pypi?18:54
rkukuraI’m guessing we should call our initial python-gbpclient 1.0, or maybe 0.118:54
SumitNaiksatamrkukura: or is it just a setup thing18:54
rkukuraDon’t know about pypi18:54
*** dboik has joined #openstack-meeting-318:54
rkukuraI think this versioning is from the setup.py and setup.cfg18:54
rkukuraBut its not set in the gdbclient rep18:55
rkukurarepo18:55
SumitNaiksatamrkukura: yes there is a place where the version number gets set18:55
rkukuragbp18:55
SumitNaiksatamrkukura: its in the egginfo18:55
*** johnbelamaric1 has joined #openstack-meeting-318:55
*** johnbelamaric has quit IRC18:55
SumitNaiksatamrkukura: okay let me circle back to you offline on this18:55
rkukuraok18:55
*** johnbelamaric has joined #openstack-meeting-318:55
SumitNaiksatam#action rkukura and SumitNaiksatam to work on client version numbering18:55
SumitNaiksatamrkukura: any other updates?18:56
*** markmcclain1 has joined #openstack-meeting-318:56
rkukuraSumitNaiksatam: I’m seeing 2.3.9 in the egg-info18:56
SumitNaiksatamrkukura: yeah this is copied over from the neutron client :-)18:56
SumitNaiksatamrkukura: need to fix that18:56
rkukuraWe probably should start with 1.0 or 0.118:57
SumitNaiksatamrkukura: makes sense18:57
*** markmcclain has quit IRC18:57
*** eglynn has quit IRC18:57
SumitNaiksatamokay couple of mins left18:57
*** sarob has joined #openstack-meeting-318:57
*** LouisF has joined #openstack-meeting-318:57
SumitNaiksatamrkukura: thanks for the update18:57
SumitNaiksatam#topic Open Discussion18:57
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:57
SumitNaiksatamone quick logistical update18:58
rkukuraI’m a bit concerned that we will make siginficant changes in kilo and won’t have full backward CLI compatability18:58
SumitNaiksatamrkukura: okay18:58
SumitNaiksatamneutron is cleaning up the subteams18:58
SumitNaiksatamand we are listed in the meetings wiki page under the networking program18:58
SumitNaiksatamso we will update the meetings wiki page to move this meeting to show up independently18:59
ivar-lazzaroSumitNaiksatam: +118:59
rkukuraSumitNaiksatam: Have you considered just writing a charter so we can stay in networking (for now)?18:59
SumitNaiksatamwe can rearrange as things evolve18:59
*** johnbelamaric1 has quit IRC18:59
rkukuraI’ve drafted a chater for the ML2 subteam18:59
*** Viswanath has joined #openstack-meeting-319:00
SumitNaiksatamrkukura: i did draft one for adv services and fwaas19:00
*** dboik has quit IRC19:00
SumitNaiksatamrkukura: but i am not sure GBP19:00
*** dboik has joined #openstack-meeting-319:00
rkukuraI’m still thinking we networking GBP is similar to adv svcs in networking - just a separate repo19:00
SumitNaiksatamrkukura: since there are currently not patches or features being discussed on the neutron side in this context19:01
SumitNaiksatamrkukura: okay we can discuss further19:01
SumitNaiksatamwe are one minute over19:01
*** bpokorny has joined #openstack-meeting-319:01
SumitNaiksatamthanks all for joining19:01
SumitNaiksatambye!19:01
rkukurathanks SumitNaiksatam!19:01
rkukurabye19:01
igordcardcya all19:01
SumitNaiksatam#endmeeting19:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:01
openstackMeeting ended Thu Nov 20 19:01:39 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
banixbye19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-11-20-18.02.html19:01
mageshgvbye19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-11-20-18.02.txt19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-11-20-18.02.log.html19:01
*** mageshgv has quit IRC19:01
ivar-lazzarociao!19:02
*** dboik has quit IRC19:02
*** dboik has joined #openstack-meeting-319:02
*** bpokorny_ has quit IRC19:04
*** MarkAtwood has joined #openstack-meeting-319:04
*** igordcard has quit IRC19:04
*** eghobo has joined #openstack-meeting-319:06
*** Viswanath has quit IRC19:07
*** vishwanathj has quit IRC19:10
*** johnbelamaric has quit IRC19:12
*** johnbelamaric1 has joined #openstack-meeting-319:12
*** johnbelamaric has joined #openstack-meeting-319:12
*** salv-orlando has quit IRC19:12
*** jacalcat has joined #openstack-meeting-319:13
*** eghobo has quit IRC19:13
*** johnbelamaric has left #openstack-meeting-319:14
*** johnbelamaric has joined #openstack-meeting-319:15
*** baoli has quit IRC19:15
*** baoli has joined #openstack-meeting-319:16
*** baoli has quit IRC19:16
*** johnbelamaric1 has quit IRC19:16
*** hemanthravi has quit IRC19:18
*** eglynn has joined #openstack-meeting-319:20
*** hareeshp has joined #openstack-meeting-319:23
*** Sukhdev has joined #openstack-meeting-319:24
*** ycombinator_ has joined #openstack-meeting-319:25
*** Guest76265 has quit IRC19:25
*** eghobo has joined #openstack-meeting-319:26
*** bpokorny_ has joined #openstack-meeting-319:27
*** johnbelamaric has quit IRC19:28
*** hareeshp has quit IRC19:28
*** johnbelamaric has joined #openstack-meeting-319:28
*** bpokorny has quit IRC19:30
*** emagana has quit IRC19:32
*** emagana has joined #openstack-meeting-319:33
*** asahlin has quit IRC19:34
*** Ark has joined #openstack-meeting-319:34
*** Ark is now known as Guest2025219:34
*** emagana has quit IRC19:38
*** carl_baldwin has joined #openstack-meeting-319:38
*** jtomasek has quit IRC19:42
*** SridharRamaswamy has quit IRC19:45
*** asahlin has joined #openstack-meeting-319:47
*** alexsyip has quit IRC19:48
*** hareeshp has joined #openstack-meeting-319:49
*** s3wong has quit IRC19:49
*** johnbelamaric has quit IRC19:49
*** alexsyip has joined #openstack-meeting-319:50
*** hareeshp has quit IRC19:50
*** hareeshp has joined #openstack-meeting-319:51
*** hareeshp has quit IRC19:51
*** hareeshp has joined #openstack-meeting-319:51
*** dboik has quit IRC19:51
*** dboik has joined #openstack-meeting-319:52
*** Youcef has quit IRC19:54
*** hareeshpc has joined #openstack-meeting-319:57
*** Guest20252 has quit IRC19:59
*** hareeshp has quit IRC20:00
*** MarkAtwood has quit IRC20:04
*** emagana has joined #openstack-meeting-320:04
*** dboik has quit IRC20:04
*** dboik has joined #openstack-meeting-320:04
*** bpokorny has joined #openstack-meeting-320:05
*** johnbelamaric has joined #openstack-meeting-320:06
*** bpokorny_ has quit IRC20:08
*** markmcclain1 has quit IRC20:08
*** markmcclain has joined #openstack-meeting-320:08
*** MarkAtwood has joined #openstack-meeting-320:09
*** johnbelamaric has quit IRC20:11
*** johnbelamaric has joined #openstack-meeting-320:12
*** johnbelamaric has quit IRC20:13
*** johnbelamaric has joined #openstack-meeting-320:13
*** johnbelamaric has quit IRC20:14
*** johnbelamaric has joined #openstack-meeting-320:14
*** vishwanathj has joined #openstack-meeting-320:24
*** s3wong has joined #openstack-meeting-320:26
*** KrishnaK has joined #openstack-meeting-320:29
*** nelsnels_ has quit IRC20:34
*** nelsnelson has joined #openstack-meeting-320:39
*** salv-orlando has joined #openstack-meeting-320:44
*** dboik_ has joined #openstack-meeting-320:47
*** dboik has quit IRC20:47
*** otherwiseguy has joined #openstack-meeting-320:48
*** KrishnaK has quit IRC20:48
*** dboik_ has quit IRC20:51
*** hareeshpc has quit IRC20:51
*** dboik has joined #openstack-meeting-320:52
*** banix has quit IRC20:53
*** banix has joined #openstack-meeting-320:53
*** sarob has quit IRC20:57
*** LouisF has quit IRC20:59
*** emagana has quit IRC21:01
*** emagana has joined #openstack-meeting-321:01
*** sarob has joined #openstack-meeting-321:02
*** emagana has quit IRC21:04
*** emagana has joined #openstack-meeting-321:04
*** MarkAtwood has quit IRC21:05
*** mrmartin has quit IRC21:09
*** SridharRamaswamy has joined #openstack-meeting-321:11
*** david-lyle has joined #openstack-meeting-321:11
*** david-lyle has quit IRC21:12
*** yamamoto has joined #openstack-meeting-321:12
*** david-lyle has joined #openstack-meeting-321:13
*** bpokorny_ has joined #openstack-meeting-321:14
*** garyduan has quit IRC21:15
*** banix has quit IRC21:16
*** bpokorny has quit IRC21:16
*** yamamoto has quit IRC21:17
*** garyduan has joined #openstack-meeting-321:20
*** hurgleburgler has quit IRC21:21
*** hareeshp has joined #openstack-meeting-321:22
*** Sukhdev has quit IRC21:24
*** shwetaap has quit IRC21:25
*** ycombinator_ has quit IRC21:25
*** banix has joined #openstack-meeting-321:27
*** ttrifonov is now known as zz_ttrifonov21:29
*** hareeshp has quit IRC21:30
*** baoli has joined #openstack-meeting-321:32
*** baoli has quit IRC21:33
*** baoli has joined #openstack-meeting-321:33
*** igordcard has joined #openstack-meeting-321:38
*** Ark has joined #openstack-meeting-321:40
*** Ark is now known as Guest4082021:40
*** seizadi has joined #openstack-meeting-321:44
*** hurgleburgler has joined #openstack-meeting-321:44
*** peristeri has quit IRC21:46
*** eghobo has quit IRC21:46
*** bpokorny has joined #openstack-meeting-321:47
*** MarkAtwood has joined #openstack-meeting-321:48
*** bpokorny_ has quit IRC21:50
*** eghobo has joined #openstack-meeting-321:52
*** baoli has quit IRC21:57
*** emagana has quit IRC21:58
*** hurgleburgler1 has joined #openstack-meeting-321:58
*** emagana has joined #openstack-meeting-321:58
*** baoli has joined #openstack-meeting-321:59
*** hurgleburgler has quit IRC22:00
*** emagana has quit IRC22:01
*** baoli has quit IRC22:01
*** baoli has joined #openstack-meeting-322:01
*** emagana has joined #openstack-meeting-322:01
*** dkehn has quit IRC22:03
*** julim has quit IRC22:04
*** dkehn has joined #openstack-meeting-322:05
*** jgrimm is now known as zz_jgrimm22:06
*** banix has quit IRC22:07
*** hurgleburgler has joined #openstack-meeting-322:08
*** hurgleburgler1 has quit IRC22:09
*** sarob has quit IRC22:10
*** jacalcat has left #openstack-meeting-322:11
*** johnbelamaric has quit IRC22:12
*** sarob has joined #openstack-meeting-322:12
*** markmcclain has quit IRC22:13
*** baoli has quit IRC22:22
*** baoli has joined #openstack-meeting-322:23
*** sergef has quit IRC22:35
*** emagana has quit IRC22:36
*** sarob has quit IRC22:37
*** emagana has joined #openstack-meeting-322:37
*** sarob has joined #openstack-meeting-322:38
*** emagana has quit IRC22:41
*** eglynn has quit IRC22:46
*** emagana has joined #openstack-meeting-322:46
*** dkehn has quit IRC22:48
*** dkehn has joined #openstack-meeting-322:50
*** seizadi has quit IRC22:55
*** sarob has quit IRC22:56
*** otherwiseguy has quit IRC22:57
*** sarob has joined #openstack-meeting-322:58
*** eghobo has quit IRC23:00
*** igordcard has quit IRC23:02
*** dboik_ has joined #openstack-meeting-323:06
*** dboik_ has quit IRC23:06
*** FallenPegasus has joined #openstack-meeting-323:07
*** FallenPegasus has quit IRC23:07
*** emagana has quit IRC23:08
*** emagana has joined #openstack-meeting-323:08
*** dboik has quit IRC23:09
*** Guest40820 has quit IRC23:09
*** MarkAtwood has quit IRC23:10
*** emagana has quit IRC23:13
*** emagana has joined #openstack-meeting-323:13
*** yamamoto has joined #openstack-meeting-323:14
*** dkehn has quit IRC23:17
*** dkehn has joined #openstack-meeting-323:18
*** yamamoto has quit IRC23:19
*** vkmc has joined #openstack-meeting-323:21
*** vkmc has quit IRC23:21
*** vkmc has joined #openstack-meeting-323:21
*** banix has joined #openstack-meeting-323:22
*** sarob has quit IRC23:27
*** alexpilotti has quit IRC23:27
*** emagana has quit IRC23:32
*** emagana has joined #openstack-meeting-323:32
*** bpokorny_ has joined #openstack-meeting-323:35
*** banix has quit IRC23:36
*** emagana has quit IRC23:37
*** bpokorny has quit IRC23:39
*** emagana has joined #openstack-meeting-323:39
*** bpokorny has joined #openstack-meeting-323:47
*** igordcard has joined #openstack-meeting-323:49
*** bpokorny_ has quit IRC23:50
*** baoli has quit IRC23:50
*** reed has quit IRC23:51
*** seizadi has joined #openstack-meeting-323:51
*** seizadi has joined #openstack-meeting-323:53
*** baoli has joined #openstack-meeting-323:54
*** seizadi has quit IRC23:56
*** sarob has joined #openstack-meeting-323:57

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