Thursday, 2014-08-07

*** TravT has quit IRC00:06
*** sarob has joined #openstack-meeting-300:09
*** otherwiseguy has joined #openstack-meeting-300:10
*** Swami has quit IRC00:10
*** igordcard has quit IRC00:15
*** alexpilotti has joined #openstack-meeting-300:16
*** dkehn__ is now known as dkehnx00:19
*** yamamoto has joined #openstack-meeting-300:21
*** yamamoto has quit IRC00:26
*** jaypipes has quit IRC00:26
*** eghobo has quit IRC00:27
*** rudrarugge has quit IRC00:34
*** chuckC has quit IRC00:47
*** sarob has quit IRC00:48
*** carl_baldwin has joined #openstack-meeting-300:49
*** sarob has joined #openstack-meeting-300:51
*** yamamoto has joined #openstack-meeting-300:51
*** sarob has quit IRC00:54
*** yamamoto has quit IRC00:56
*** rudrarugge has joined #openstack-meeting-300:57
*** eghobo has joined #openstack-meeting-301:02
*** MarkAtwood has joined #openstack-meeting-301:12
*** alexpilotti has quit IRC01:13
*** baohua has joined #openstack-meeting-301:15
*** banix has joined #openstack-meeting-301:17
*** yamahata has joined #openstack-meeting-301:21
*** baohua has quit IRC01:23
*** baohua has joined #openstack-meeting-301:23
*** mfer has joined #openstack-meeting-301:26
*** yamamoto_ has joined #openstack-meeting-301:27
*** carl_baldwin has quit IRC01:27
*** MarkAtwood has quit IRC01:30
*** shwetaap has joined #openstack-meeting-301:35
*** stanzgy has joined #openstack-meeting-301:36
*** yamamoto_ has quit IRC01:36
*** carl_baldwin has joined #openstack-meeting-301:40
*** eghobo has quit IRC01:43
*** eghobo has joined #openstack-meeting-301:44
*** eghobo has quit IRC01:46
*** chuckC has joined #openstack-meeting-301:57
*** yamamoto_ has joined #openstack-meeting-301:57
*** thomasem has joined #openstack-meeting-301:59
*** thomasem has quit IRC02:04
*** carl_baldwin has quit IRC02:24
*** rudrarug_ has joined #openstack-meeting-302:27
*** banix has quit IRC02:27
*** banix has joined #openstack-meeting-302:31
*** rudrarugge has quit IRC02:31
*** rudrarug_ has quit IRC02:31
*** MarkAtwood has joined #openstack-meeting-302:34
*** baohua has quit IRC02:36
*** baohua has joined #openstack-meeting-302:36
*** sarob has joined #openstack-meeting-302:38
*** sarob has quit IRC02:38
*** sarob has joined #openstack-meeting-302:39
*** otherwiseguy has quit IRC02:39
*** shwetaap has quit IRC02:47
*** ivar-lazzaro has quit IRC02:49
*** MarkAtwood has quit IRC02:55
*** julim has quit IRC02:59
*** sarob has quit IRC03:00
*** sarob has joined #openstack-meeting-303:00
*** sarob has quit IRC03:05
*** lblanchard has quit IRC03:09
*** otherwiseguy has joined #openstack-meeting-303:11
*** HenryG is now known as HenryG_afk03:31
*** otherwiseguy has quit IRC03:34
*** otherwiseguy has joined #openstack-meeting-303:35
*** vkmc has quit IRC03:39
*** banix has quit IRC03:41
*** otherwiseguy has quit IRC03:41
*** otherwiseguy has joined #openstack-meeting-303:42
*** banix has joined #openstack-meeting-303:44
*** sankarshan_away is now known as sankarshan03:49
*** sankarshan is now known as sankarshan_away03:49
*** eghobo has joined #openstack-meeting-303:50
*** shwetaap has joined #openstack-meeting-303:51
*** marun has quit IRC03:54
*** marun has joined #openstack-meeting-303:56
*** sarob has joined #openstack-meeting-304:01
*** Longgeek has joined #openstack-meeting-304:05
*** sarob has quit IRC04:05
*** otherwiseguy has quit IRC04:10
*** Longgeek has quit IRC04:12
*** Longgeek has joined #openstack-meeting-304:13
*** banix has quit IRC04:14
*** Longgeek has quit IRC04:14
*** Longgeek has joined #openstack-meeting-304:14
*** Longgeek has quit IRC04:16
*** Longgeek has joined #openstack-meeting-304:17
*** Longgeek has quit IRC04:21
*** otherwiseguy has joined #openstack-meeting-304:21
*** amotoki has joined #openstack-meeting-304:21
*** jpomero_ has joined #openstack-meeting-304:25
*** davidlenwell_ has joined #openstack-meeting-304:28
*** dosaboy_ has joined #openstack-meeting-304:30
*** boltR_ has joined #openstack-meeting-304:31
*** ruhe2 has joined #openstack-meeting-304:34
*** vish1 has joined #openstack-meeting-304:34
*** SumitNaiksatam has quit IRC04:34
*** mfer has quit IRC04:35
*** vishy has quit IRC04:35
*** dosaboy has quit IRC04:35
*** anteaya has quit IRC04:35
*** jpomero has quit IRC04:35
*** boltR has quit IRC04:35
*** ruhe has quit IRC04:35
*** zz_johnthetubagu has quit IRC04:35
*** davidlenwell has quit IRC04:35
*** vish1 is now known as vishy04:35
*** ruhe2 is now known as ruhe04:35
*** anteaya has joined #openstack-meeting-304:43
*** Longgeek has joined #openstack-meeting-304:48
*** shwetaap has quit IRC04:51
*** k4n0 has joined #openstack-meeting-304:56
*** sarob has joined #openstack-meeting-305:01
*** otherwiseguy has quit IRC05:03
*** sarob has quit IRC05:06
*** tomoe_ has joined #openstack-meeting-305:11
*** Longgeek has quit IRC05:12
*** Longgeek has joined #openstack-meeting-305:12
*** Longgeek has quit IRC05:14
*** k4n0 has quit IRC05:21
*** sarob has joined #openstack-meeting-305:22
*** sarob has quit IRC05:26
*** k4n0 has joined #openstack-meeting-305:34
*** amotoki_ has joined #openstack-meeting-305:43
*** Longgeek has joined #openstack-meeting-305:45
*** Longgeek has quit IRC05:47
*** Longgeek has joined #openstack-meeting-305:47
*** Longgeek has quit IRC05:49
*** Longgeek has joined #openstack-meeting-305:53
*** Longgeek has quit IRC05:58
*** amotoki has quit IRC06:04
*** amotoki_ has quit IRC06:05
*** amotoki has joined #openstack-meeting-306:05
*** MarkAtwood has joined #openstack-meeting-306:11
*** k4n0 has quit IRC06:12
*** MarkAtwood has quit IRC06:21
*** sarob has joined #openstack-meeting-306:22
*** sarob has quit IRC06:27
*** k4n0 has joined #openstack-meeting-306:28
*** iovadia has joined #openstack-meeting-306:39
*** baohua_ has joined #openstack-meeting-306:40
*** mrunge has joined #openstack-meeting-306:42
*** yamamoto_ has quit IRC06:43
*** baohua has quit IRC06:44
*** eghobo has quit IRC06:46
*** Longgeek has joined #openstack-meeting-306:58
*** jtomasek has joined #openstack-meeting-306:59
*** pkoniszewski has joined #openstack-meeting-307:03
*** Longgeek has quit IRC07:03
*** zz_johnthetubagu has joined #openstack-meeting-307:04
*** zz_johnthetubagu is now known as johnthetubaguy07:04
*** flaper87|afk is now known as flaper8707:05
*** jamielennox is now known as jamielennox|away07:06
*** yamamoto_ has joined #openstack-meeting-307:07
*** iovadia has quit IRC07:09
*** sarob has joined #openstack-meeting-307:23
*** iovadia has joined #openstack-meeting-307:27
*** sarob has quit IRC07:27
*** flaper87 is now known as flaper87|afk07:36
*** yamahata has quit IRC07:45
*** SumitNaiksatam has joined #openstack-meeting-307:49
*** amotoki_ has joined #openstack-meeting-307:51
*** amotoki_ has quit IRC07:51
*** MaxV has joined #openstack-meeting-307:53
*** Longgeek has joined #openstack-meeting-307:59
*** Longgeek has quit IRC08:04
*** safchain has joined #openstack-meeting-308:06
*** yamamoto_ has quit IRC08:21
*** sarob has joined #openstack-meeting-308:24
*** flaper87|afk is now known as flaper8708:27
*** sarob has quit IRC08:28
*** baohua_ has quit IRC08:36
*** baohua has joined #openstack-meeting-308:37
*** tomoe_ has quit IRC08:43
*** jtomasek has quit IRC08:55
*** jtomasek has joined #openstack-meeting-309:01
*** igordcard has joined #openstack-meeting-309:05
*** baohua has quit IRC09:07
*** baohua has joined #openstack-meeting-309:08
*** amotoki has quit IRC09:16
*** sarob has joined #openstack-meeting-309:24
*** flaper87 is now known as flaper87|afk09:28
*** sarob has quit IRC09:29
*** Longgeek has joined #openstack-meeting-309:30
*** yamamoto_ has joined #openstack-meeting-309:35
*** Longgeek has quit IRC09:35
*** yamamoto_ has quit IRC09:40
*** baohua has quit IRC09:45
*** sarob has joined #openstack-meeting-310:25
*** sarob has quit IRC10:29
*** Longgeek has joined #openstack-meeting-311:01
*** Longgeek has quit IRC11:06
*** Longgeek has joined #openstack-meeting-311:10
*** yamamoto has joined #openstack-meeting-311:15
*** sarob has joined #openstack-meeting-311:26
*** sarob has quit IRC11:30
*** banix has joined #openstack-meeting-311:48
*** alexpilotti has joined #openstack-meeting-311:59
*** vkmc has joined #openstack-meeting-312:07
*** vkmc has joined #openstack-meeting-312:07
*** yamamoto has quit IRC12:15
*** HenryG_afk is now known as HenryG12:18
*** yamamoto has joined #openstack-meeting-312:22
*** banix has quit IRC12:24
*** banix has joined #openstack-meeting-312:24
*** sarob has joined #openstack-meeting-312:27
*** sarob has quit IRC12:31
*** stanzgy has quit IRC12:54
*** julim has joined #openstack-meeting-312:57
*** jpomero_ is now known as jpomero12:57
*** k4n0 has quit IRC12:59
*** lblanchard has joined #openstack-meeting-313:02
*** iovadia1 has joined #openstack-meeting-313:07
*** iovadia has quit IRC13:09
*** woodm1979 has joined #openstack-meeting-313:22
*** tomoe_ has joined #openstack-meeting-313:23
*** peristeri has joined #openstack-meeting-313:24
*** tomoe_ has quit IRC13:24
*** banix has quit IRC13:25
*** tomoe_ has joined #openstack-meeting-313:27
*** sarob has joined #openstack-meeting-313:27
*** julim_ has joined #openstack-meeting-313:30
*** sarob has quit IRC13:32
*** shwetaap has joined #openstack-meeting-313:32
*** julim has quit IRC13:33
*** shakamunyi has joined #openstack-meeting-313:50
*** thangp has joined #openstack-meeting-313:50
*** banix has joined #openstack-meeting-313:50
*** mfer has joined #openstack-meeting-313:50
*** banix has quit IRC13:54
*** thomasem has joined #openstack-meeting-313:59
*** otherwiseguy has joined #openstack-meeting-314:06
*** sankarshan_away is now known as sankarshan14:22
*** sankarshan is now known as sankarshan_away14:22
*** shakamunyi has quit IRC14:23
*** cbader has joined #openstack-meeting-314:27
*** sarob has joined #openstack-meeting-314:28
*** banix has joined #openstack-meeting-314:29
*** sarob has quit IRC14:33
*** banix has quit IRC14:34
*** pballand has quit IRC14:35
*** banix has joined #openstack-meeting-314:36
*** thangp has quit IRC14:37
*** shakamunyi has joined #openstack-meeting-314:37
*** thangp has joined #openstack-meeting-314:43
*** carl_baldwin has joined #openstack-meeting-314:43
*** johnthetubaguy is now known as zz_johnthetubagu14:43
*** markmcclain has joined #openstack-meeting-314:45
*** david-lyle has joined #openstack-meeting-314:48
*** markmcclain has quit IRC14:49
*** markmcclain has joined #openstack-meeting-314:49
*** Praveen_ has joined #openstack-meeting-314:50
*** Praveen_ has quit IRC14:50
*** PraveenSM has joined #openstack-meeting-314:51
carl_baldwinhi all14:59
yamamotohi14:59
*** pcm_ has joined #openstack-meeting-315:00
*** Swami has joined #openstack-meeting-315:00
*** Rajeev has joined #openstack-meeting-315:00
carl_baldwinSwami, mrsmith, viveknarasimhan, safchain, amuller, devvesa: ping15:00
carl_baldwinpcm_: hi15:00
safchainhi15:00
carl_baldwinRajeev: hi15:00
carl_baldwinSwami: hi15:00
Swamicarl_baldwin:hi15:00
RajeevHi15:01
pcm_hi15:01
carl_baldwin#startmeeting neutron_l315:01
openstackMeeting started Thu Aug  7 15:01:09 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
openstackThe meeting name has been set to 'neutron_l3'15:01
carl_baldwin#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
carl_baldwinJuno-3 is September 4th15:01
carl_baldwinFeatureProposalFreeze (FPF) is August 21st15:02
*** seizadi has joined #openstack-meeting-315:02
carl_baldwinThat is only two weeks away and you know how these weeks fly by.15:02
*** mrsmith has joined #openstack-meeting-315:02
carl_baldwin#link https://wiki.openstack.org/wiki/Juno_Release_Schedule15:02
carl_baldwin#topic neutron-ovs-dvr15:03
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:03
mrsmitho/15:03
Swamibug fixes are currently in full swing.15:04
carl_baldwin#link https://bugs.launchpad.net/neutron/+bugs?field.tag=l3-dvr-backlog15:04
SwamiI think most us are working on the bug fixes.15:04
mrsmithyup15:04
carl_baldwinYup15:04
Swamivivek had posted the fix for the critical L2 pop.15:05
carl_baldwinI’d like to get this one reviewed and merged very soon:  https://bugs.launchpad.net/neutron/+bug/135048515:05
carl_baldwinSwami: the same15:05
Swamicarl_baldwin: yes you are right.15:05
mrsmithyes15:05
mrsmithI think the ml2 prob is affecting lots of areas15:05
carl_baldwinI was looking at the UTs that were added (PS4) that had a problem.15:05
*** zz_johnthetubagu is now known as johnthetubaguy15:05
carl_baldwinI have not found the problem and so I trimmed the UTs down to a minimal set for the patch.15:06
carl_baldwinSo, you’ll see a big difference in UTs from PS4 to PS5.15:06
Swamicarl_baldwin: Yes I did see your message on that.15:06
carl_baldwinI think keeping the patch focused will help us to review and merge it more quickly.15:06
SwamiYour point is valid to just focus on the bug fix and the related UT for now to make the review easy.15:07
carl_baldwinThe UTs developed by Vivek can be worked on and proposed as a new patch at a later time.  They can still add much value.15:07
carl_baldwinI see there is a new bug 135388515:08
Rajeevbug 1353885 L2Pop on OVS broken due to DeferredBridge introduction : Vivek filed, is also in the related area. UTs will help.15:08
carl_baldwinRajeev: :)15:08
Swami#link https://bugs.launchpad.net/neutron/+bug/135388515:08
Rajeevcarl_baldwin: I ran into it yesterday :)15:08
carl_baldwinI actually ran in to the same thing yesterday and was getting ready to file a bug.15:09
carl_baldwin#link http://paste.openstack.org/show/91167/15:09
*** rudrarugge has joined #openstack-meeting-315:09
carl_baldwinI just added my trace to the bug.15:09
Rajeevcarl_baldwin: yes, same symptoms15:10
Swamiwas this Deferred bridge late introduction.15:10
carl_baldwinJust a little hint.  These stack traces don’t copy/paste well in to bug reports.  paste.openstack.org is a good way to get them in there.15:10
carl_baldwinI’ll review the patch (a one-liner) and see if it makes sense to add a UT.  I think this should merge quickly.15:11
*** lcheng_ has joined #openstack-meeting-315:12
Swamicarl_baldwin: thanks15:12
carl_baldwinSwami: Rajeev:  Do we know which patch introduced this bug?15:12
carl_baldwinIt would be good to note that in the bug report.15:12
Swamicarl_baldwin: no I am not sure.15:12
carl_baldwinNever mind, it is in the bug report.15:12
carl_baldwinI was snow blind because of the stack trace.  ;)15:13
*** sarob has joined #openstack-meeting-315:13
*** Rajeev_ has joined #openstack-meeting-315:13
*** rudrarugge has quit IRC15:14
Rajeev_carl_baldwin: sorry lost connection. don't know the patch # but came in last 2 days15:14
carl_baldwin#action carl_baldwin will shepherd bug 1353885 through15:14
*** Rajeev has quit IRC15:14
carl_baldwinRajeev_: np, the patch is reported in the bug report.  I had missed it.15:14
carl_baldwinOther progress?15:14
mrsmithcarl_baldwin: I am hitting an issue with delete namespaces15:15
mrsmiththe driver is throwing an error15:15
Swamiwe are progressing on the migration patch15:15
mrsmith"Device or resource not ready"15:15
mrsmithanyone seeing this?15:15
mrsmiththis is for #link https://bugs.launchpad.net/neutron/+bug/135328715:15
carl_baldwin“not ready”?  I’m not sure I’m seen that.15:15
mrsmithif I put a delay in after intefaces are unpluged and the delete namespace, no error15:16
mrsmithwe can rely on "delays"15:16
carl_baldwinmrsmith: you’re asking?15:16
mrsmiththis is causing tempest errors15:16
mrsmithI'm asking if anyone else has seen this error lately15:17
mrsmithin the community15:17
mrsmithit seems to be yet another "recent" problem15:17
mrsmithwe weren't seeing this before15:17
carl_baldwinI haven’t but others can speak up.15:17
mrsmithk15:18
mrsmithI'll keep digging15:18
carl_baldwinmrsmith: Could you paste some context around the error and link it to the bug?15:18
mrsmithsure15:18
*** pkoniszewski has quit IRC15:19
Rajeev_mrsmith: I just tried it and got this: Cannot remove /var/run/netns/qrouter-3f587793-02a6-4fc3-8b97-dc38581ef92a: Device or resource busy15:19
mrsmithright15:19
mrsmiththats it15:19
mrsmiththat looks like a plain router ns15:19
mrsmithI am hitting it with a fip ns15:19
mrsmithso - same possible issue in the driver?15:19
carl_baldwinmrsmith: Oh, that is different.  What OS are you on?15:20
mrsmithubuntu15:20
Rajeev_ubuntu here too15:20
mrsmith12.0415:21
carl_baldwinmrsmith: Rajeev_:  That is a known issue with the iproute package on 12.04.15:21
carl_baldwinI don’t remember all of the details but there are broad locks created by execing in the namespace.15:21
carl_baldwinThis problem is the whole reason why namespace deletion is off by default.15:22
Rajeev_carl_baldwin: good to know, any workarounds ?15:22
carl_baldwinUpdate iproute package.15:22
mrsmithso jenkins/gate/tempest runs with delete off?15:22
mrsmithor we need to support either regardless?15:23
carl_baldwinmrsmith: yes, but now that you mention it it could be turned on now that 14.04 is in the gate.15:23
mrsmith"could" or "might have"15:24
*** sarob has quit IRC15:24
*** sarob has joined #openstack-meeting-315:24
carl_baldwinmrsmith: I’m sure it is off in the gate because off is the default.15:25
carl_baldwin#link https://bugs.launchpad.net/neutron/+bug/105253515:25
mrsmithya - we've talked about this before15:25
mrsmithits an old bug15:25
mrsmithits just we've been deleting ns pretty reliably for months15:26
mrsmithand now it seems to be affecting us more15:26
*** woodm1979 has quit IRC15:26
mrsmithI'll look at how to work around this15:26
mrsmithin the code15:26
*** woodm1979 has joined #openstack-meeting-315:26
carl_baldwinSee my comment from 2013-10-0115:26
carl_baldwinI might be able to find you an update to iproute with the fix in it.15:27
carl_baldwinAny other DVR issues to discuss?15:27
mrsmithwell - updating iproute is easy enough15:27
mrsmithgetting the code to be more rubust is what I'm after15:27
mrsmith*robust15:27
mrsmithwe can move on -thanks15:27
SwamiI think that's all we have for now.15:28
carl_baldwinmrsmith: The problem is that if you hit the error, we’ve found that the system tends to get bad after.  So, simply handling the error gracefully isn’t really going to cut it.15:28
*** sarob has quit IRC15:29
mrsmithfair enough15:29
carl_baldwinSo, you’ve got to avoid hitting the error in the first place or your machine will not be the same until a reboot.15:29
carl_baldwinmrsmith: Let me know what you come up with.15:29
carl_baldwinKeep up the good work DVR team.15:30
PraveenSMHello All,15:30
PraveenSMWe have written a blueprint “DHCP Serivce LoadBalancing Scheduler”.15:30
PraveenSMThis blue print is written to address the problem of uneven scheduling of DHCP name spaces on multiple network nodes.  The problem we faced is,  Consider we have 1 Openstack Controller, 4 Network Nodes,100 Compute nodes.  We have created 200 Networks and booted 800VMs across 200 networks. When the VMs are booted across networks then DHCP namespaces pertaining to network will be created on Network Nodes.  However arou15:30
carl_baldwin#topic l3-high-availability15:30
*** openstack changes topic to "l3-high-availability (Meeting topic: neutron_l3)"15:30
carl_baldwinPraveenSM: We’ll catch you in Open Discussion.15:30
PraveenSMok thanks15:31
carl_baldwinsafchain: amuller: ping15:31
safchainhi15:31
carl_baldwinHow is this progressing?15:31
carl_baldwinI did some reviewing last week but some of it was WIP.  I’m happy to review this week.15:31
safchainbase classes and scheduler rebased, all UT work15:32
safchainamuller made a great job on the agent side15:32
safchainhe splitted the agent code into two classes15:32
carl_baldwinIs most of it ready for review?15:33
safchainsure15:33
carl_baldwinGreat, I’ll make a pass over them today.  Be sure that anything that may not be ready is marked WIP.15:34
carl_baldwinsafchain: anything else?15:34
safchainassaf is still working to add more functional test, but we can start the review15:34
safchainno everything is ok15:34
safchainok I'll check the WIP status15:34
carl_baldwinsafchain: thanks.15:35
carl_baldwin#topic l3-svcs-vendor-*15:35
*** openstack changes topic to "l3-svcs-vendor-* (Meeting topic: neutron_l3)"15:35
carl_baldwinpcm_: Is there anything outstanding on this topic?15:35
pcm_No all set. BP done, VPN implemented.15:36
carl_baldwinI saw that your Cisco impl was merged, I think.15:36
carl_baldwinpcm_: Great.  Shall I removed from the agenda?15:36
pcm_If other services want to do this, we can do as bugs.15:36
pcm_Sure.15:36
carl_baldwinpcm_: Okay, great work.15:36
pcm_thanks!15:36
carl_baldwin#topic bgp-dynamic-routing15:37
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:37
*** Rajeev_ has quit IRC15:37
carl_baldwindevvesa, nextone92: ping15:37
carl_baldwin#action carl_baldwin will review bgp code in progress15:37
carl_baldwinLooks like they’re not around.15:38
*** banix has quit IRC15:38
carl_baldwinyamamoto: do you have anything?15:38
yamamotonothing15:38
yamamoto#link https://review.openstack.org/#/q/topic:bp/bgp-dynamic-routing,n,z15:38
carl_baldwinOkay, I guess we’ll take the topic to gerrit.15:39
carl_baldwinyamamoto: thanks15:39
*** banix has joined #openstack-meeting-315:39
carl_baldwin#topic Reschedule routers from downed agents15:39
*** openstack changes topic to "Reschedule routers from downed agents (Meeting topic: neutron_l3)"15:39
carl_baldwinkevinbenton: are you around?15:39
kevinbentonhttps://review.openstack.org/#/c/110893/15:39
kevinbentonit’s now configuration enabled15:40
carl_baldwinkevinbenton: that is good.15:40
kevinbentondefault disabled so people concerned with zombie agents won’t have to worry15:40
carl_baldwinI’ll have another look.  There is one colleague here at HP who dealt with our rescheduling solution a lot.  He may be able to provide better feedback about the sorts of things that go wrong.15:41
carl_baldwinI also heard from some other HP guys who were working along the same lines.15:41
kevinbentoni’m aware of most of them. one of the guys from redhat already provided quite a bit on the bug report15:42
carl_baldwinI’m trying to nudge them to discuss it out in the open.  :)15:42
carl_baldwinkevinbenton: great.15:42
carl_baldwinkevinbenton: thanks for the update.  Anything else to discuss?15:42
kevinbentonthere is nothing more that can be done from the neutron side if we assume neutron is disconnected15:43
kevinbentoncarl_baldwin: nope, this patch probably isn’t going to change much now15:43
carl_baldwinkevinbenton: thanks.15:43
*** pballand has joined #openstack-meeting-315:43
carl_baldwin#topic Open Discussion15:44
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:44
PraveenSMWe have written a blueprint “DHCP Serivce LoadBalancing Scheduler”. https://review.openstack.org/#/c/111210/ https://blueprints.launchpad.net/neutron/+spec/dhcpservice-loadbalancing15:45
PraveenSMThis blue print is written to address the problem of uneven scheduling of DHCP name spaces on multiple network nodes.  The problem we faced is,  Consider we have 1 Openstack Controller, 4 Network Nodes,100 Compute nodes.  We have created 200 Networks and booted 800VMs across 200 networks. When the VMs are booted across networks then DHCP namespaces pertaining to network will be created on Network Nodes.15:45
PraveenSMHowever around 95% of DHCP namespaces will be created on only one Network Node and remaining 5% DHCP namespaces will be distributed among remaining 3 Network Nodes. Hence there will be excess load on only one Network Node.  To address this problem we have written the blueprint so that DHCP namespaces will be distributed equally among Network Nodes based on number of DHCP namespaces hosted on each Network node.15:45
PraveenSMPlease review it and give comments15:46
carl_baldwinLike LeastRouters?15:46
*** mrunge has quit IRC15:46
PraveenSMyes15:46
carl_baldwinPraveenSM: I will add it to my radar.  Thanks for bringing it up.15:46
PraveenSMthanks15:46
*** banix has quit IRC15:46
seizadiCan we register for Kilo Design Sessions?15:47
carl_baldwinseizadi: Good question.  I have not heard.15:47
carl_baldwinUsually that comes after summit talks (voting ended yesterday)15:47
seizadiHow do we track on twitter?15:48
*** iovadia1 has left #openstack-meeting-315:49
carl_baldwinseizadi: Not sure what you’re asking but I’ve never been on twitter so maybe that’s why.15:49
*** iovadia has joined #openstack-meeting-315:50
*** iovadia has left #openstack-meeting-315:50
*** eghobo has joined #openstack-meeting-315:50
seizadi:) A lot of the summit announcements are on #Openstack I am new and don't know how the process works.15:50
*** eghobo has quit IRC15:51
*** eghobo has joined #openstack-meeting-315:51
*** shakamunyi has quit IRC15:51
*** Rajeev has joined #openstack-meeting-315:52
carl_baldwinseizadi: I see.  I just sort of hear word of mouth or by email.15:52
seizadiOK, Thx15:54
carl_baldwinif that is all, I will close the meeting.15:54
carl_baldwinGreat work!15:54
carl_baldwin#endmeeting15:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:54
openstackMeeting ended Thu Aug  7 15:54:58 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-08-07-15.01.html15:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-08-07-15.01.txt15:55
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-08-07-15.01.log.html15:55
*** Swami has left #openstack-meeting-315:55
yamamotobye15:55
*** pcm_ has left #openstack-meeting-315:55
*** mrsmith has quit IRC15:55
*** PraveenSM has quit IRC15:56
*** amotoki has joined #openstack-meeting-315:58
*** safchain has quit IRC16:03
*** MarkAtwood has joined #openstack-meeting-316:08
*** Youcef has joined #openstack-meeting-316:13
*** lcheng_ has quit IRC16:15
*** tomoe_ has quit IRC16:18
*** MaxV has quit IRC16:19
*** MaxV has joined #openstack-meeting-316:20
*** MaxV has quit IRC16:25
*** banix has joined #openstack-meeting-316:25
*** sarob has joined #openstack-meeting-316:25
*** coolsvap has quit IRC16:26
*** sarob has quit IRC16:29
*** coolsvap has joined #openstack-meeting-316:31
*** reed has joined #openstack-meeting-316:40
*** lcheng_ has joined #openstack-meeting-316:45
*** rudrarugge has joined #openstack-meeting-317:02
*** coolsvap has quit IRC17:04
*** Longgeek has quit IRC17:05
*** markmcclain has quit IRC17:08
*** coolsvap has joined #openstack-meeting-317:10
*** sarob has joined #openstack-meeting-317:25
*** sarob has quit IRC17:30
*** otherwiseguy has quit IRC17:31
*** rudrarugge has quit IRC17:32
*** rudrarugge has joined #openstack-meeting-317:33
*** rudrarugge has quit IRC17:33
*** yamamoto has quit IRC17:33
*** rudrarugge has joined #openstack-meeting-317:34
*** s3wong has joined #openstack-meeting-317:36
*** SumitNaiksatam has quit IRC17:46
*** dconde has joined #openstack-meeting-317:50
*** salv-orlando has joined #openstack-meeting-317:51
*** marun has quit IRC17:54
*** LouisF has joined #openstack-meeting-317:55
*** ivar-lazzaro has joined #openstack-meeting-317:55
*** mscohen has joined #openstack-meeting-317:55
*** regXboi has joined #openstack-meeting-317:58
*** hemanthravi has joined #openstack-meeting-317:59
banixhaloooo18:00
*** rkukura has joined #openstack-meeting-318:00
rkukurahi18:00
hemanthravihi18:00
s3wongseems like SumitNaiksatam just left18:00
ivar-lazzarohi18:00
banixrkukura, hemanthravi, s3wong : hi18:00
s3wongobviously Sumit got tired o hosting this meeting :-)18:00
*** SumitNaiksatam_ has joined #openstack-meeting-318:00
s3wongbanix: hello18:00
LouisFhi18:01
banixLouisF: hi18:01
regXboimoo18:01
SumitNaiksatam_seems like i am having the same problem as yesterday18:01
SumitNaiksatam_lets get started18:01
* regXboi is sitting on two IRC meetings right now, so may be distracted18:01
banixSumitNaiksatam_: what? can’t hear you :)18:01
SumitNaiksatam_#startmeeting networking_policy18:01
s3wongSumitNaiksatam_: seems like it, probably good to appoint another chair then18:01
openstackMeeting started Thu Aug  7 18:01:34 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
*** jackmccann has joined #openstack-meeting-318:01
openstackThe meeting name has been set to 'networking_policy'18:01
SumitNaiksatam_banix: :-)18:01
*** QJ has joined #openstack-meeting-318:01
SumitNaiksatam_#chair rkukura banix s3wong18:02
openstackCurrent chairs: SumitNaiksatam_ banix rkukura s3wong18:02
SumitNaiksatam_whew! got that out of the way18:02
* regXboi notes SumitNaiksatam has learned well :)18:02
SumitNaiksatam_regXboi: ;-)18:02
SumitNaiksatam_#info agenda: https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy18:02
SumitNaiksatam_i hope everyone slept well yesterday! ;-)18:03
*** prasadv has joined #openstack-meeting-318:03
SumitNaiksatam_#topic Mailing list discussion on GBP18:03
*** openstack changes topic to "Mailing list discussion on GBP (Meeting topic: networking_policy)"18:03
SumitNaiksatam_so I think good arguments have been made in favor of doing this in-tree18:04
SumitNaiksatam_in the mailing list yesterday18:04
SumitNaiksatam_what does everyone else think?18:05
* regXboi has been waffling back and forth18:05
ivar-lazzaroSumitNaiksatam_: +1, there has been a good response.18:06
* banix surprisingly in good spirit :)18:06
SumitNaiksatam_banix: :-)18:06
yyywui am glad to know so many people are interesting on GBP.18:06
s3wong131 posts on that thread - finally quiet down for the last hour18:06
banixyyywu: or lack there of :)18:07
*** songole has joined #openstack-meeting-318:07
yyywui am impressed so many high quality discussion in one day!18:07
arosenHonestly, I feel like points of why GBP have been really been made/proven. I'm just trying to come from a point of understanding...18:07
* arosen haven't18:07
* arosen imho solely :)18:08
banixthat changes the statement :)18:08
SumitNaiksatam_arosen: honestly, i think its difficult to explain it any better than what kevinbenton already has18:08
SumitNaiksatam_arosen: i think we spoke at lenght about this at least a couple of times before as well18:09
hemanthravikevinbenton's last e-mail summarized it well18:09
arosenAt one point there was talk that GBP provides optimizations and preformance improvements though i don't think anyone has explained why.18:09
SumitNaiksatam_arosen: and every time the discussion seems to get reset18:09
banixarosen: I wish you were enaged a few monts ago (or may be even before that) but I ubderstand schedules/interests changes18:09
SumitNaiksatam_arosen: we could potentially take turns in relaying this to you in different ways, would that help?18:09
arosenI agree i wish i paid more attention to this.18:09
SumitNaiksatam_arosen: at this point myself and kevinbenton already tried18:09
SumitNaiksatam_arosen: the fundamental premise is not going to change though18:10
banixarosen: i dont think performance optimization is the main issue at all; that is in my opinion but others may have different views18:10
arosenOne sec*18:10
SumitNaiksatam_banix: agree, not sure where that came from18:10
* regXboi suspects people come to GP from different places and so see different aspects of the solution18:11
*** susaant has joined #openstack-meeting-318:11
SumitNaiksatam_regXboi: agree18:11
arosenI'd be interested in going through the points i commented here on the blueprint: http://lists.openstack.org/pipermail/openstack-dev/2014-August/042114.html18:11
arosenIf you guys are interested in having that discussion18:12
SumitNaiksatam_regXboi: hence the suggestion that we can take turns in explaining this, and present different perspectives :-)18:12
SumitNaiksatam_arosen: i am not sure that we can go through all the points in this meeting18:12
arosenbanix:  where do you see the benefit of the new model?18:12
SumitNaiksatam_arosen: but we can certainly pick a few of them18:13
arosenSumitNaiksatam_:  okay let me pick a point then .18:13
SumitNaiksatam_arosen: also for the records most if not all of those have been discussed at length in various different fora before18:13
rkukuraarosen: The optimization and performance oportunities are when things like ODL or vendor controllers can render the intent expressed in the contracts without necessarily using the same mechanisms needed for Neutron security groups, firewalls, etc.. The advantages to the user are that the API gives them a more natural way to express what they need to control.18:13
*** thinrichs has joined #openstack-meeting-318:13
SumitNaiksatam_arosen: we cannot keep rehashing the same discussion over and over again18:13
SumitNaiksatam_arosen: but defintiely go ahead18:14
banixarosen: some are listed on the spec, level of abstraction is the main factor in my view18:14
arosenrkukura:  neutron's api is a logical abstraction the backend implementation can be done however a vendor chooses. Why does moving to GBP allow ODL/vendor controllers a performance improvement?18:15
regXboiall: may I?18:15
SumitNaiksatam_regXboi: please18:15
*** seizadi has quit IRC18:16
regXboineutron's logical abstraction has some inherent assumptions baked into it18:16
ivar-lazzaroSumitNaiksatam_: hopefully we get time to discuss the agenda :) get arosen in sync is certainly very important but it may be better to move the discussion elsewhere? just asking18:16
regXboispecifically withing the concept of scoping that are not natural for an applicaiton programmer to think in18:16
mscohenarosen: do you want to talk to me now outside this meeting to go through some of these?18:16
rkukuraarosen: Because by expressing just the intent rather than describing a specific configuration of virtual appliances, there is a lot more flexibility in how the intent gets rendered.18:16
SumitNaiksatam_ivar-lazzaro: just a few minutes, i am still optimistic that arosen will be happy after this :-)18:17
arosenI don't want to take over your meeting perhaps following up in openstack-neutron later is a better option.18:18
regXboiall: sorry - I'm getting pulled into another discussion - I'll have to go split brain for a while18:19
SumitNaiksatam_arosen: we have certainly allocated some time on the agenda for this discussion18:19
arosenAlso, I'm just trying to just understand this new model and why. I definitely hate to make you guys rehash things you have hashed.18:19
SumitNaiksatam_arosen: if you anticipate that this is a much longer discussion then we can take it to a different place18:19
LouisFarosen: there is considerable literature and research work showing that providing higher level abstractions is the way forward on managing networks18:19
arosenMy question though is GBP really a higher level abstraction perhaps? I still see the same network primiatives in it similar to the model we have today.18:20
*** nbouthors has joined #openstack-meeting-318:20
LouisFarosen: gbp is a step is in that direction18:20
SumitNaiksatam_arosen: i think you are confusing the mapping with the GBP abstraction18:20
ivar-lazzaroSumitNaiksatam_: +118:21
SumitNaiksatam_arosen: the reference implementation mapping is one way to realize GBP18:21
SumitNaiksatam_arosen: i think you argument always starts at the mapping level18:21
SumitNaiksatam_arosen: at which point you have fundamentally side stepped the GBP abstraction in the first place18:22
SumitNaiksatam_arosen: there is not much to discuss in terms of differences at that point18:22
arosenSo are we saying the mapping implementation isn't very useful?18:22
SumitNaiksatam_arosen: of course it is18:22
arosen"Allow for automatic orchestration that can respond to changes in policy or infrastructure without requiring human interaction to translate intent to specific actions."18:23
arosencan we talk about that point?18:23
SumitNaiksatam_arosen: it helps you leverage the advantages of GBP when using the neutron reference implementation (involving ML2 etc)18:23
SumitNaiksatam_arosen: yes sure18:24
arosenwhat automatic orchestration does it do?18:24
SumitNaiksatam_arosen: that particular point was well articulated in kevinbenton's responses18:24
SumitNaiksatam_arosen: he also gave you the analogy by comparing puppet and bash scripts18:24
SumitNaiksatam_arosen: when you use the current neutron abstractions, you require - "human interaction to translate intent to specific actions"18:25
SumitNaiksatam_arosen: when you use GBP, you - "Allow for automatic orchestration that can respond to changes in policy or infrastructure"18:25
rkukuraarosen: It creates the networks, subnets, ports, routers, and security groups for you, and hooks all of these up properly to provide exactly the connectivity between EPGs described by the contracts.18:25
SumitNaiksatam_rkukura: and it maintains the consistency of those18:26
SumitNaiksatam_rkukura: without further human intervention18:26
arosenSumitNaiksatam_:  why do you say it requires, "human interaction to translate intent to specific actions"18:26
rkukuraRight, as the contracts change, new EPs added to EPGs, etc.18:26
*** rockyg has joined #openstack-meeting-318:26
SumitNaiksatam_arosen: i will paraphrase kevinbenton's examples for expediency here"18:27
SumitNaiksatam_create a network/subnet for each endpoint group allow all traffic on the security groups since the logging would need to be accomplished with FWaaS create an FWaaS instance attach the FWaaS to both networks add an FWaaS policy and the FWaaS rules to allow the correct traffic18:27
rkukuraManually, if you add a new VM to a pool providing some service, you need to go find all the SGs that reference that service and add the new VM’s IP (or subnet) to those SGs. This is all automatic with GBP.18:27
arosenSumitNaiksatam_:  sure i understand that's the current work flow.18:27
SumitNaiksatam_arosen: as rkukura pointed out above, and kevinbenton's example, thats the human interaction that we are referring to18:28
SumitNaiksatam_arosen: are we good?18:29
arosenSumitNaiksatam_:  cool, mind showing how one would deploy this same style of app but showing it done with group based policy?18:29
SumitNaiksatam_arosen: i thought you were digging into the PoC script, and we spent a couple of hours discussing it18:29
arosenrkukura:  i showed that you can use --remote-group-id with security groups to avoid updating any ips.18:29
*** rms_13 has joined #openstack-meeting-318:30
rkukuraarosen: Yes, that is one option, or you can reference subnet’s CIDRs, …18:30
ivar-lazzaroarosen: the point is that you don't have to choose between SG or FW depending on your needs… That is completely handled by the implementation.18:31
rockygLemme give it a try.  arosen:  suppose I'm an app developer and have deployed a db base app for a customer.  I've created my policies, etc.  Now I have a new customer and need to deploy pretty much the same on a new set of VMs.  I just refer to the original policy and the networking happens.  Am I naively correct here, guys?18:31
arosenrkukura:  so i don't see why your talking about a workflow with security groups that are hard.18:31
*** Cathy_ has joined #openstack-meeting-318:31
arosengoing to each security profile group etc.18:31
rkukuraarosen: I don’t think anyone is arguing that an experienced network engineer cannot do what they need with the current API, and with proper planning and best practices, do it efficiently.18:31
SumitNaiksatam_rockyg: yes18:32
*** marun has joined #openstack-meeting-318:32
arosenrockyg:  good example18:32
SumitNaiksatam_so at this point we are 30 mins into the meeting18:32
*** markmcclain has joined #openstack-meeting-318:33
SumitNaiksatam_one another point i wanted to bring in this context was with regards to the naming convention18:33
arosenwhy not write all of your policy in an external system like heat which is designed to do this kind of thing?18:33
rockygCool.  And if I want to change the network interactions, I modify the policy and restart the networks on all the vms that use it?18:33
SumitNaiksatam_arosen: you still abstractions at the network policy level to express this in heat18:33
regXboiSumitNaiksatam_: I think we need to change from endpoint18:34
*** yamamoto has joined #openstack-meeting-318:34
SumitNaiksatam_arosen: is it fair to say we have given enough time to this discussion?18:34
regXboiI don't know what to18:34
SumitNaiksatam_regXboi: exactly :-)18:34
regXboibut I think that's low hanging fruit we should seriously consider18:34
*** otherwiseguy has joined #openstack-meeting-318:34
SumitNaiksatam_so that was the next sub topic in this agenda item18:34
arosenivar-lazzaro:  also i'm not sure about your point about how a user doesn't have to choose about security groups and fwaas. These are two different points of enforcement no?18:35
ivar-lazzaroarosen: exactly.18:35
arosenivar-lazzaro:  you're saying with GBP the user doesn't have to decide18:35
SumitNaiksatam_arosen: ah, now you are getting it18:35
ivar-lazzaroarosen: that's why you don't want to understand about that, but just expressing your intent18:35
banixdid markmcclain joined the meeting os simply started his IRC client?18:35
SumitNaiksatam_arosen: i think we can leave the rest to you as a home work exercise ;-)18:36
*** yamamoto_ has joined #openstack-meeting-318:36
SumitNaiksatam_markmcclain: hi, you are welcome to join this meeting18:36
SumitNaiksatam_so regarding the endpoint terminology18:36
SumitNaiksatam_any suggestions?18:36
arosenivar-lazzaro:  If you are expressing your intent of doing enforcement at both points you do care then.18:36
rockygregXboi: Edgar Magana suggested using the IETF phrasing -- enforcement point18:37
*** markmcclain1 has joined #openstack-meeting-318:37
mscoheni was thinking “edgar point” would be good.  and we won’t have to change our slides from EP.18:37
arosenivar-lazzaro:  would be great to see an example using the CLI how one sets something up that in GBP that does enforcement at the instance and router.18:37
rockygmschoen ++18:37
SumitNaiksatam_rockyg: although enforcement point tends to be used in a slightly different context18:37
rockygmscohen ++18:38
regXboiI was involved in the early IETF policy days, and I'm not a big from of ep18:38
SumitNaiksatam_mscohen: we dont want to overload the terminology18:38
SumitNaiksatam_regXboi: +118:38
rkukuraI’m not entirely sure “enforcement point” is the same as our usage of endpoint18:38
SumitNaiksatam_rkukura: exactly18:38
mscohenSumitNaiksatam: i am joking of course18:38
SumitNaiksatam_mscohen: :-)18:38
rockygYeah.  that's the problem with endpoint.  It's right for networking, but it already has another definition in virtualization world.18:38
SumitNaiksatam_how about network-endpoint (someone else suggested that)?18:38
rkukuraI think enforcement point is more like the SG or FWaaS that is used to render the intent18:38
SumitNaiksatam_rkukura: agree18:39
regXboiso... let's hit the thesaurus18:39
rockygRkukara, agree18:39
*** yamamoto has quit IRC18:39
rkukuraI had always throught endpoint was the right word for both our usage and for keystone, with similar meanings, but different meta-levels18:39
*** markmcclain has quit IRC18:39
regXboirkukura: if we can find something different, let's consider it18:40
regXboithere is enough of a hill to climb18:40
regXboihow about terminus?18:40
* regXboi keeps reading synonyms18:40
*** yamamoto_ has quit IRC18:41
rms_13network-endpoint?18:41
regXboium... no18:41
*** SumitNaiksatam has joined #openstack-meeting-318:41
regXboiI think that won't help18:41
LouisFpolicy-point/policy groups?18:41
rkukuragroup member?18:42
*** SumitNaiksatam__ has joined #openstack-meeting-318:42
mscohentermination-point, gbp-id, policy point maybe18:42
SumitNaiksatamsorry i dropped off again!18:42
regXboiI think member18:42
regXboiunless that's already used somewhere18:42
SumitNaiksatami was saying earlier, what about policy-point?18:42
s3wong#chair SumitNaiksatam18:42
openstackCurrent chairs: SumitNaiksatam SumitNaiksatam_ banix rkukura s3wong18:42
rkukuraregXboi: Just “member” and “group”?18:42
SumitNaiksatams3wong: :-)18:42
s3wongSumitNaiksatam: so now either way works for you :-)18:43
regXboirkurkura: too general I think...18:43
nbouthorspolicy-provider, policy-consumer18:43
regXboier rkukura ... sorry18:43
yyywui still like endpoint better.18:43
rockygbourn or bourne 1  (bɔːn)18:43
rockyg18:43
rockyg— n18:43
rockyg1.  a destination; goal18:43
rockyg2.      a boundary18:43
regXboiI think policy-point and policy-group18:43
SumitNaiksatamyyywu: :-)18:43
*** SumitNaiksatam_ has quit IRC18:43
rockygBourne-point?18:43
SumitNaiksatamrockyg: :-)18:43
SumitNaiksatammore in favor of policy-point and policy-group?18:44
*** marun has quit IRC18:44
SumitNaiksatami thnk LouisF suggested as well18:44
*** marun has joined #openstack-meeting-318:44
mscohen+1 to policy-point18:44
rms_13+1 to policy-point and policy-group18:44
yyywu+118:44
nbouthorsSumitNaiksatam: +1 too18:44
rockyg+118:45
rms_13FINALLY... YEAH18:45
SumitNaiksatamokay so how about we float this in the ML?18:45
s3wong+118:45
*** marun_ has joined #openstack-meeting-318:45
prasadv+118:45
rms_13Yes... lets do that18:45
rkukura+118:45
SumitNaiksatamso that we dont end up picking up an overlapping terminology again18:45
SumitNaiksatamwho wants to do it? as in send to the ML?18:45
* SumitNaiksatam waiting to hand out an AI :-P18:46
SumitNaiksatamregXboi: ?18:46
rms_13I can do it18:46
regXboihmm?18:46
SumitNaiksatamrms_13: ah you put your hand up first18:46
* regXboi apologies - bouncing between multiple IRC meetings18:46
hemanthravipolicy-endpoint ?18:46
SumitNaiksatam#action rms_13 to send “policy-point” “policy-group” suggestion to mailing list18:46
rms_13NO END to the ENDPOINT :)18:47
SumitNaiksatamregXboi: ^^^ fine?18:47
banixhemanthravi: no wont work18:47
SumitNaiksatamrms_13: lol18:47
regXboiSumitNaiksatam: works for me18:47
SumitNaiksatamhemanthravi: see the AI above18:47
rkukuraI guess the acronyms PP and PG work18:47
regXboilet's get that complaint cleared up18:47
rms_13policy-point and policy-group. Final. Lets move to another topic ?18:47
LouisF+118:47
songole+118:47
SumitNaiksatami knew rkukura would be thinking acronyms, just waiting :-D18:47
SumitNaiksatamyeah lets move on18:48
* regXboi chants "... and there was much rejoicing ..."18:48
rockygHuzzah!18:48
SumitNaiksatam#topic Patch reviews18:48
*** openstack changes topic to "Patch reviews (Meeting topic: networking_policy)"18:48
SumitNaiksatam-2 still persists, markmcclain1 can hopefully chime on the thread on the ML and help us make progress here18:49
SumitNaiksatam#topic model update18:50
SumitNaiksatamnothing besides the endpoint naming convention18:50
regXboiSumitNaiksatam: I put +1s on the CLI ones earlier today - I reserve the right to change if I run into issues ;)18:50
SumitNaiksatam#topic mapping udpate18:50
regXboi(sorry about being late)18:50
SumitNaiksatamregXboi: sweet, getting to the CLI18:50
SumitNaiksatamrkukura: any updates on the mapping?18:50
SumitNaiksatamwe will SG mapping separately18:50
SumitNaiksatamdifferent agenda item18:50
*** jpomero_ has joined #openstack-meeting-318:50
*** openstack changes topic to "model update (Meeting topic: networking_policy)"18:50
*** openstack changes topic to "mapping udpate (Meeting topic: networking_policy)"18:50
rkukuraNo, just that I added code to reject changing a PG’s PP in the last rebase18:50
rkukuraI mean a PP’s PG, sorry18:50
SumitNaiksatamrkukura: nice catch on that18:50
SumitNaiksatamrkukura: :-)18:50
SumitNaiksatamrkukura: i think that was in response to reviewer’s comments?18:50
rkukurayes, on the API patch18:51
SumitNaiksatamrkukura: thanks for that18:51
SumitNaiksatam#topic SG mapping update18:51
*** openstack changes topic to "SG mapping update (Meeting topic: networking_policy)"18:51
SumitNaiksatams3wong: ?18:51
*** MaxV has joined #openstack-meeting-318:51
s3wongyes18:51
*** david-lyle has quit IRC18:51
markmcclain1sorry on flaky connection… I have reservations the API changes18:51
markmcclain1the changes leak out details of the underlay18:52
s3wongstill working on the patch, hopefully will send out a first patch sometimes this week (or weekend)18:52
SumitNaiksatammarkmcclain1: which API changes?18:52
*** marun has quit IRC18:52
*** marun_ is now known as marun18:52
SumitNaiksatams3wong: great, thanks18:52
*** david-lyle has joined #openstack-meeting-318:52
banixmarun: hi18:52
s3wongmarkmcclain1: please elaborate18:52
SumitNaiksatammarkmcclain1: this is the GBP meeting18:53
marunbanix: hi18:53
markmcclain1oops repasted wrong response18:53
SumitNaiksatammarkmcclain1: np, guessed as much18:53
*** jpomero has quit IRC18:53
markmcclain1so on the GPB discussion I was on jury duty yesterday18:53
SumitNaiksatammarkmcclain1: for a minute i thought, wow, we are making progress here! ;-)18:53
banixmarun: in the GBP meeting… wondering how you and markmcclain1 think of the discussion on the ML18:53
SumitNaiksatammarkmcclain1: we do understand you have personal committments18:54
*** thinrichs has quit IRC18:54
SumitNaiksatammarkmcclain1: is it appropriate to hold up an entire team of people for that reason though?18:54
marunbanix: I haven't fully caught up I'm afraid.18:54
rms_13SumitNaiksatam: I will reply on this http://lists.openstack.org/pipermail/openstack-dev/2014-August/042243.html  please confirm18:54
SumitNaiksatammarkmcclain1: i am referring to the -218:54
SumitNaiksatamrms_13: i think you can start separate thread18:55
banixmarun: sure; hope to hear from you soon.18:55
SumitNaiksatamrms_13: use [policy] in the subject header18:55
marunbanix: I've been talking a bunch with rkukura directly about the issue, so my input has been in play even if it appears not.18:55
banixmarun: i see18:55
rms_13SumitNaiksatam: Fine18:55
SumitNaiksatamrkukura: perhaps you can relay the input for the benefit of everybody, if you think its appropriate?18:55
SumitNaiksatams3wong: sorry for hijacking the SG mapping topic18:56
*** rudrarugge has quit IRC18:56
s3wongSumitNaiksatam: I am done with my update anyway, please change topic if you like :-)18:56
SumitNaiksatam#topic Input from markmcclain1 and marun18:56
*** openstack changes topic to "Input from markmcclain1 and marun (Meeting topic: networking_policy)"18:56
*** rudrarugge has joined #openstack-meeting-318:56
*** markmcclain1 has quit IRC18:56
*** david-lyle has quit IRC18:56
rkukuraSumitNaiksatam: I’d really rather marun summarize his own thoughts if he is here and thinks they will be valuable. We’ve discussed a number of things.18:56
SumitNaiksatamrkukura: sure18:57
SumitNaiksatammarun: do you feel comfortable doing that?18:57
rkukuraI don’t want to put words in his mouth he didn’t say18:57
marunWell, I've said alot of things.18:57
SumitNaiksatamrkukura: sure, i just asked because marun seemed to indicate that you were on the same page18:57
rkukuraOne area we’ve discussed is setting expectations properly about the stability of the API in an initial release18:57
marunRight18:57
SumitNaiksatamrkukura marun: agree18:58
*** markmcclain has joined #openstack-meeting-318:58
SumitNaiksatami believe that is the case with every new extension we add18:58
marunAllowing a new and as-yet unproven api into the tree would require some groundwork that hasn't been done yet.18:58
marunWe'd have to be able to address Mark's concerns about having to support unstable API's (and slowing down evolution in the process)18:58
SumitNaiksatammarun: how is it different from any other extension that has been introduced in neutron?18:58
rkukuraBut it wouldn’t be the first time we’ve done it, either18:59
marunSumitNaiksatam: I'm afraid we're playing catch-up here.18:59
marunSumitNaiksatam: The impression outside of the project is that things like lbass, vpnaas, and fwaas have been stabilized too soon.18:59
SumitNaiksatammarun: well, to some extent i can definitely say that we have tried to incorporate from those past experiences18:59
marunSumitNaiksatam: Whether or not we as a project believe that to be true, I think we need to consider that feedback.18:59
SumitNaiksatammarun: sure19:00
markmcclainso I've switched to a more stable conneciton… I'm actually working on a refinement to the plan19:00
markmcclainthat incorporates lots of feedback I've gotten and addresses LBaaSv2 too19:00
SumitNaiksatamwe have hit the hour, but we can continue until we are kicked out19:00
marunSumitNaiksatam: Going forward, I think we need to make sure that new APIs and features can continue to evolve and don't impose the burden of stabilization.19:00
SumitNaiksatammarun: seems like a reasonable thing to state19:00
marunSumitNaiksatam: I don't think this problem is unique to group policy, but we're having to confront it as part of the initiative.19:01
SumitNaiksatammarkmcclain: i am not too comfortable with you, as one person, making the plans for the rest of the project19:01
marunThe details of how we accomplish these goals would have to be determined.19:01
SumitNaiksatammarkmcclain: i am referring to - “I'm actually working on a refinement to the plan"19:01
SumitNaiksatammarkmcclain: we are having a discussion on the ML19:01
SumitNaiksatammarkmcclain: please participate19:02
marunSumitNaiksatam: He can propose plans.  And we as a community will give feedback and ultimately decide what to do.19:02
SumitNaiksatammarkmcclain: the plan has to evolve19:02
SumitNaiksatammarkmcclain: it cannot be one person handing out things19:02
marunSumitNaiksatam: Let's be clear - Mark is not acting alone.19:02
SumitNaiksatamand while at that we dont have the luxury of infinite time here19:02
markmcclainSumitNaiksatam: it is.. there were 90+ messages to catch up while on jury duty19:02
ivar-lazzaroSumitNaiksatam: +1. Also, this kind of planning should be referred to the next release without blocking what is already approved and implemented19:03
SumitNaiksatami can already see you coming back in a couple of weeks and saying that its too late now to review and i am goint to put a -219:03
rkukuraNot sure if its at all related to markmcclain’s plan, but marun, myself, and a couple others have kicked around the idea of labeling a feature as a “preview” until its API is declared stable. It would still be in-tree, subject to normal reviews, etc..19:03
marunivar-lazzaro: sorry, that's not what's going to happen.19:03
SumitNaiksatammarkmcclain: i totally sympathize with you, and appreciate you personal situation19:03
markmcclainrkukura: my plan would deal with all preview eligible APIs which is more than just policy19:03
SumitNaiksatammarkmcclain: however you have blocked this effort for more than a month19:03
SumitNaiksatammarkmcclain: without providing a single reason19:04
marunSumitNaiksatam: As I've expressed to rkukura, Mark is not blocking this out of being obstinate.19:04
ivar-lazzaromarun: as long as it's a community decision… I'm telling my point of view.19:04
markmcclainSumitNaiksatam: sorry I don't regret working to find a community solution to a very real problem19:04
SumitNaiksatammarkmcclain: and utilimately you come up with an unreasonable proposal to throw the whole thing under the bus19:04
marunSumitNaiksatam: He is the roadblock you see, but he has weight of numbers behind him whether you want to recognize it or not.19:04
regXboiwhoa folks19:04
SumitNaiksatammarun: what numbers are talking here?19:05
regXboilet's back up19:05
banixmarkmcclain: Mark, could you tell us a bit more about the revised plan you are going to suggest19:05
rms_13+1 regXboi19:05
salv-orlandofrom what I gather it seems unfair to blame a single person for the sticky -2 on the patch. If it weren’t him it probably were somebody else.19:05
regXboiI'm interested in hearing what the proposal is?19:05
regXboibanix: +119:05
SumitNaiksatamsalv-orlando: markmcclain marun: my point is not about the people19:05
banixyeah lets get back to the proposal19:05
SumitNaiksatammy point is about the process19:06
marunSumitNaiksatam: All the folks that have issues with this initiative whose voices are being ignored in favor of those that support it.19:06
markmcclainregXboi, banix: it's been something I've working on today19:06
SumitNaiksatamregXboi banix: yes sure19:06
SumitNaiksatammarun: that is a blatantly incorrect statement19:06
markmcclainit also clarifies lots of process items19:06
marunSumitNaiksatam: If you don't think that this is true, then you are uninformed.19:06
ivar-lazzaroSumitNaiksatam: +1 for the process19:06
regXboimarkmcclain: please go on19:06
marunSumitNaiksatam: It matters if you want to understand why this initiative is not moving forward as quickly as you would like.19:06
SumitNaiksatammarkmcclain: yes please go on19:06
regXboiI'm curious to hear it, even in draft form...19:06
salv-orlandoSumitNaiksatam: I hope so… actually I’m quite sure of that, but it’s still good to remind that it’s not about blaming individual. If that was the case, we would have eliminated markmcclain with potassium cyanide back in Atl19:07
marunSumitNaiksatam: This group does bear some responsibility for the situation they are in, whether it wants to recognize that or not.19:07
markmcclainI'll post it later today after finishing up the details19:07
SumitNaiksatamsalv-orlando: agree 100%, its not about blaming individual19:07
* regXboi is slightly disappointed, his curiosity was piqued19:07
SumitNaiksatammarun: i am still at a loss to understand19:07
marunSumitNaiksatam: That's kind of the point.19:08
SumitNaiksatamdoes anyone else here know what marun is referring to?19:08
marunSumitNaiksatam: You've been a core for how long?19:08
rockygmarkmcclain:  Can you give a quick outline, and would it allow GBP in the release?19:08
markmcclainunderstand everyone wants to see it, but I'd prefer to have a more intact proposal a sketch with lots of gaps19:08
SumitNaiksatammarun: how is that relevant?19:08
marunSumitNaiksatam: With respect, there are trust and relationship issues around this initiative that are causing lots of friction.19:08
SumitNaiksatammarun: are we getting personal details now?19:08
salv-orlandoI see a lot of argument, more or less opinionated, pro and cons this new API. Am I allowed to ask something as somebody who simply doesn’t care?19:08
marunSumitNaiksatam: No, it's simply an observation that open source is a messy human business.19:08
*** thinrichs has joined #openstack-meeting-319:08
regXboimarkmcclain: oh well, understood19:08
SumitNaiksatamsalv-orlando: please19:09
banixok i think let’s have this discussion on ML after markmcclain posts his comments19:09
salv-orlandowho loses if this is delayed for further discussion?19:09
salv-orlandoI mean is this going to hurt the user commnity?19:09
SumitNaiksatamjust a note to everyone, that we are past the meeting time, 10 mins over19:09
salv-orlandoSumitNaiksatam: sorry I did not even realized this was the meeting channel19:09
regXboisalv-orlando: there were several posts to the ML from folks who (I believe) are not here but are looking for GP to land in Juno19:09
marunI'm not committed to having it in vs out of the tree at this point.19:09
banixSumitNaiksatam: as you said let’s talk more unless there is another meeting19:09
SumitNaiksatamsalv-orlando: no worries, we are waiting until we get kicked out19:10
ivar-lazzaroregXboi: +1. A lot of them.19:10
SumitNaiksatamsalv-orlando: but i just wanted to make the process point that we are over19:10
regXboi"are not here" meaning "did not contribute to this process"19:10
regXboigack! s/process/project/19:10
banixSumitNaiksatam: yes, thanks.19:10
salv-orlandook so we have active users relying on this feature to be available in trunk in juno for their deployments?19:10
marunBut we need to solve the problem I spoke of earlier - minimizing the maintenance burden of an unstable api and allow it to evolve with minimal friction - if it is to go into the tree this cycle.19:10
ivar-lazzaroregXboi: not sure if they are taken into account though, together with all the work done to get this in place.19:10
marunIf we don't have an answer for this, then no, I don't think it should be merged.19:11
regXboisalv-orlando: I believe I can say that19:11
salv-orlandowe have some brave users out there ;)19:11
regXboisalv-orlando: I believe I can say that I am planning on using it as an operator, not as a vendor19:11
regXboiif it lands in Juno, that is19:11
regXboiif it doesn't then I have to go find another solution19:11
marunregXboi: echo chamber, much?19:11
banixmarun: how do you do that if in the tree?19:11
regXboimarun: didn't get the reference, sorry19:12
banixmarun: i mean minimizing the maintenance19:12
ivar-lazzaromarun: So you propose to do bug fixing in tree and literally everything else out of tree?19:12
marunbanix: One possibility would be putting it into an 'experimental' subtree, and an 'experimental' rest path.19:12
* regXboi not at best form - too many nights chasing defects19:12
marunbanix: This would allow us to clearly demarcate efforts that haven't been finalized, so that we wouldn't have to provide full support.19:12
banixmarun: is there any other project that do this?19:13
salv-orlandoregXboi: just saying, we’ve used stuff that was delayed off trunk in the past. But maybe our cloud is small and more manageable, so picking a package from somewhere else is easier.19:13
marunbanix: No.  Projects like nova are better at saying 'no'.19:13
rms_13marun: wouldnt that approach open up a kitchen sync for future?19:13
*** seizadi has joined #openstack-meeting-319:13
regXboisalv-orlando: yeah, I have all sorts of gates to go through if this lands outside the tree19:13
marunrms_13: We need to be able to fail-fast as per Mark's email.19:13
regXboinot that I can't go through them19:13
regXboiit just becomes a whole different ball game19:14
regXboibut that's neither here nor there19:14
marunrms_13: We could do it out of tree, as he suggests, but then re-integration is a problem (as you've experienced)19:14
rkukuramarun: The subtree the kind of thing you and I were discussing, and I could support this if labeled something like “preview” instead of “experimental” and if it really targets code that is working its way towards a stable API and does not end up being a long-term place to dump code.19:14
*** johnthetubaguy is now known as zz_johnthetubagu19:14
regXboirkukura: +119:14
marunrms_13: Ideally we would figure out a way to iterate faster in the tree but not accept a feature as something we want to keep until it's considered 'fully baked'19:14
SumitNaiksatamrkukura: i like the preview terminology19:14
*** Krishna_ has joined #openstack-meeting-319:14
regXboimarun: I could live with the idea rkukura just stated19:14
ivar-lazzarorkukura: +119:15
mscohen+1 rkukura.  I think this is good for neutron in general to have.  and works for this project.19:15
regXboimarkmcclain: you still around?19:15
marunI don't think the term is important, just the fact that things are clearly identified so there is no confusion on the part of users or developers.19:15
rockygI think the key will be how to schedule the integration testing so that it stays sync'ed19:15
rms_13marun: I understand but than what about services? Do they fall in the same bucket as well?19:15
marunrockyg: for out-of-tree?19:16
marunrms_13: it could be for anything we want time to stabilize19:16
marunrms_13: clearly there would be limitations though, since some changes would be very invasive19:16
salv-orlandowhat the technical difference when it comes to building a release between a subtree and another repository?19:16
rms_13marun: I understand that. But do we take action on them is the question. LBaaS, FWaas, VPNaas?19:16
rms_13salv-orlando: +1 to question19:17
rockygmarun: for branch.  You are trying to limit maintenance, so I owuld think that you would either have triggers for when something in the branch gets merged, or maybe a long job, or nightly/weekly19:17
marunI would expect, over time, that the need for modularity between subsystems would become obvious, and make it easier to make changes that would otherwise be invasive19:17
arosenfwiw the nova-docker virt driver was pulled out of the nova tree and you can plug it into nova very easily. I don't see why this can't work in a similar way.19:17
marunrockyg: you're talking about out-of-tree development?19:17
marunarosen: well, we need a stable api19:17
marunarosen: does docker introduce api changes?19:18
salv-orlandomarun: it’s a nova compute driver pretty much19:18
regXboihey all, wonderful discussion, but I gotta run (escalation calls) ... I'll check the minutes later19:18
rockygmarun:  no, just if there is a branch, would you want to run main integration for every review?19:18
regXboiand the ML19:18
marunarosen: I mean, we can already support out-of-tree plugins and drivers.  Is it as easy to add neutron services or extensions?19:18
arosenmarun:  I don't really see how an api couldn't be loaded in a similar way19:18
SumitNaiksatamregXboi: thanks for joining19:18
*** regXboi has left #openstack-meeting-319:18
arosenthe extension frame work in neutron actually has support for loading things through PATHS19:18
marunarosen: uh19:18
rkukuraAnything that was significantly invasive could be considered for future cycles. For the existing BPs that introduce new APIs that need to get into early adopters hands so they can stability, I hope we can come up with something simple but effective enough.19:19
arosenmarun: https://github.com/openstack/neutron/blob/master/etc/neutron.conf#L5219:19
salv-orlandomarun, arosen: I think we’ve been running 2 extensions like that until they merged in master19:19
rkukuras/stability/stabilize/19:19
marunrkukura: I don't think we can compromise on the need for separation.19:19
SumitNaiksatamok, so are we converging on the “preview” option that marun and rkukura are talking about?19:19
* salv-orlando we as our team19:19
marunsalv-orlando: so does that imply that group policy could be distributed in its current form out-of-tree?19:19
*** alexpilotti has quit IRC19:20
salv-orlandoI don’t know all the technical details and how entangled it is with other db models for instance19:20
*** QJ has quit IRC19:20
rkukuraI think we are talking in-tree, aren’t we?19:20
arosenmarun:  Sure I see now reason why you can't plug anything into neutron that is out of tree this way.19:20
salv-orlandowe need a developer to comment on that19:20
marunSumitNaiksatam: I think you need feedback from more than just the participants here to move forward in that way.19:20
SumitNaiksatammarun: completely agree19:20
marunSumitNaiksatam: this meeting != the community that it impacts19:20
arosenset core_plugin or service_plugin to the path and it loads19:20
banixare we atlking about vendor-specific extensions?19:20
*** seizadi has quit IRC19:20
salv-orlandomarun: I’d say it feasible but I can’t say how long it will take19:20
rockygMarun, So, suppose you run the branch like a 3rd party CI for voting on changes to main, but don't test reviews of the branch against main until the approve stage?  Trying to save on nodepool bw19:20
SumitNaiksatammarun: i was just going to say that we can take this option to the mailing list19:20
marunSumitNaiksatam: +119:21
SumitNaiksatammarun: assumign that we have some level of consensus here19:21
marunrockyg: that's out-of-tree, though.19:21
SumitNaiksatammarun: just trying to find out if we at least have consensus here19:21
marunSumitNaiksatam: fair enough, my apologies19:21
SumitNaiksatammarun: may be not consensus, just in some lose form19:21
*** seizadi has joined #openstack-meeting-319:21
rkukuraAs features aproach becoming stable APIs, we absolutely need them to be run as part of normal testing of the tree, so anything that breaks them is detected.19:21
SumitNaiksatammarun: no need to apologize, i did not take it negativel19:21
SumitNaiksatam*negatively19:21
marunrkukura: I think they need the same testing as early as possible19:22
rockygMarun:  no, it's in tree, but like the stable branches19:22
arosenrockyg:  i don't think this has anything to do with nodepool19:22
marunrkukura: we can add integration testing in-tree, if we want to btw19:22
marunrockyg: out-of-tree or feature branches are not a good idea except for things that can be distributed separately (plugins, drivers, etc)19:22
rockygmarun: ++19:22
SumitNaiksatammarun: we would love to experiment with that approach the integration testing in-tree approach19:23
*** pballand has quit IRC19:23
SumitNaiksatammarun: for now we are focussing on the tempest tests since that seems to be the fastest path to validation19:23
SumitNaiksatammarun: and also per your earlier suggestion on this19:23
rockygsmitnaiksatam: ++19:23
*** pballand has joined #openstack-meeting-319:24
SumitNaiksatami know we are discussing a larger process issue here19:24
rockygsumitnaiksatam:  sorry for the misspell19:24
marunSumitNaiksatam: There is some question as to whether the tests should be in Tempest if they aren't considered stable, but the same tests can exist and be run from either our repo or theirs.19:24
SumitNaiksatammarun: ah ok19:24
SumitNaiksatammarun: for now these are WIP patches in tempest19:24
SumitNaiksatammarun: not meant to be merged soon for obvious reasons19:25
SumitNaiksatammarun: but we can move it to wherever its more appropraite per the plan for the “preview” apis19:25
marunSumitNaiksatam: So long as they exist we can make them usable in whatever way ends up being necessary.19:25
marunSumitNaiksatam: agreed19:25
SumitNaiksatammarun: +119:25
SumitNaiksatamso let me ask again, rkukura marun do you feel comfortable bringing up this topic in the mailing list?19:25
markmcclainsorry was pulled away… my plan is very close to the preview idea19:26
markmcclainbut with a lot more clarity around processes19:26
rms_13how does other openstack project suppose to work with "preview" APIs? Just in normal fashion? (nova, glance, keystone OR horizon)19:26
SumitNaiksatammarkmcclain: thanks for joining again19:26
banixif i understand it, all this will be part of what markmcclain  will propose later today19:26
SumitNaiksatammarkmcclain: sure, preview of your proposal? ;-)19:27
marunSumitNaiksatam: If Mark's proposal encompasses similar concepts, I would like to see that before I comment.  I'm not entirely clear of all the details of how unstable APIs have hurt us and I think his insight is critical.19:28
SumitNaiksatammarun: ok19:28
ivar-lazzaroSumitNaiksatam: +1, very curious to have a preview :)19:28
rkukura+119:28
SumitNaiksatampreview of the preview19:28
markmcclainSumitNaiksatam: haha19:29
banixsounds like we will continue this discussion on the ML19:29
*** dconde has quit IRC19:30
rkukuraI’m happy to review a proposal from markmcclain on the ML today. If that doesn’t happen, I’d be happy to writeup some of my ideas on managing preview APIs and posting it for discussion.19:30
rockygWow!  Progress, and interim closure?19:30
SumitNaiksatamrkukura: thanks!19:31
SumitNaiksatamrockyg: :-)19:31
SumitNaiksatammarkmcclain: so no preview of the preview? :-P19:31
banixrkukura: i think if you have any ideas, putting them out for discussion would be helpful19:32
markmcclainSumitNaiksatam: not yet19:32
SumitNaiksatammarkmcclain: is it because the idea is not baked, or you dont feel this is the right forum to discuss it?19:33
SumitNaiksatammarkmcclain: sorry for pressing, i am just curious19:33
markmcclainSumitNaiksatam: not fully committed to text19:33
SumitNaiksatammarkmcclain: okay19:34
* markmcclain had lots of time to think while in the jury waiting room19:34
SumitNaiksatam#action markmcclain to send a proposal on GBP progress by eod Aug 7th 201419:34
*** woodm1979 has quit IRC19:34
SumitNaiksatammarkmcclain: lol19:34
rockygmarkmcclain:   looking forward to seeing the proposal19:34
SumitNaiksatammarkmcclain: hope that AI is fine19:34
*** woodm1979 has joined #openstack-meeting-319:34
banixmarun, markmcclain, arosen, salv-orlando and all others  thanks for joing this call today19:35
SumitNaiksatambanix: indeed19:35
SumitNaiksatammarkmcclain: marun arosen salv-orlando: thanks for gracing this meeting19:35
*** yamamoto has joined #openstack-meeting-319:35
SumitNaiksatamyou are welcome to stick around though :-)19:35
SumitNaiksatamdidnt think you were leaving19:35
SumitNaiksatamshould we go through the rest of the agenda for today?19:35
SumitNaiksatampeople have time to stick around for another 10 mins?19:35
SumitNaiksatammay be less19:35
arosengo for it. It looks like you have the room..19:35
banixSumitNaiksatam: yes please19:35
SumitNaiksatamarosen: yeah :-)19:36
rkukuraok with me19:36
SumitNaiksatam#topic CLI/Client update19:36
*** openstack changes topic to "CLI/Client update (Meeting topic: networking_policy)"19:36
SumitNaiksatamwe discussed the “profiled” API suggestion last week19:36
banixs3wong: had started his comments. no?19:36
SumitNaiksatambanix: i thought s3wong said he was done19:36
SumitNaiksatams3wong: ?19:37
banixok19:37
SumitNaiksatami think s3wong is close to posting the patch19:37
SumitNaiksatamunfortunately regxboi has left the meeting19:37
songoleprofiled API patch?19:37
SumitNaiksatambanix: or anyone else to update on that?19:37
SumitNaiksatamsongole: yeah, just checking if there are any developments or blockages to that idea19:38
banixnothing from me19:38
SumitNaiksatambanix: ok19:38
SumitNaiksatamso over to you songole19:38
SumitNaiksatamany updates on the CLI/Client patches?19:38
songoleI updated the wiki page with links to the patches19:38
songoleI see that regXboi removed -119:39
rms_13I have tested them19:39
rms_13Atleast they look ok API wise.19:39
songolerms_13: any issues?19:39
songoleok19:39
rms_13I still need to test l2pol, l3pol and endpoint19:39
SumitNaiksatamsongole: nice19:39
rms_13oops sorry19:39
SumitNaiksatamrms_13: thanks, thats great progress!19:39
rms_13policy-point :)19:39
SumitNaiksatamrms_13: wait, not so soon! :-)19:40
rms_13name of the day :)19:40
*** yamamoto has quit IRC19:40
rms_13alright....I need to head out19:40
SumitNaiksatamrms_13: we need your horizon update19:40
rms_13See you all in next meeting. Will send an email to the ML soon with name proposal19:40
songoleHow would you want to deal with mapping extension?19:40
songoleDoes it need to be part of CLI?19:40
rms_13Horizon update is I will open up my WIP update for people to look at and comment19:41
SumitNaiksatamrms_13: ok thanks!19:41
rms_13If the skeleton looks good19:41
rms_13we can add more resources19:41
SumitNaiksatamrkukura: you have thoughts on songole’s question?19:41
rkukurawhat needs to be dealt with?19:42
banixsongole: you mean the extra attributes?19:42
*** mscohen has quit IRC19:42
songolebanix: right19:42
rkukuraIs the question whether these should appear in horizon?19:42
*** rms_13 has left #openstack-meeting-319:42
songolerkukura: CLI in particular19:42
songoleextensions/group_policy_mapping.py19:43
rkukuraCertainly in the CLI I would think19:43
rkukuraHow else would a user get the port_id from a PP to pass to nova boot?19:44
rkukuraIn horizon, it might be nice to have an option to turn the mapping attributes on/off19:44
songoleHowever, this is an optional extension, right?19:44
SumitNaiksatamrkukura: i think songole’s question is whether to add these as optional attributes to the GBP CLI itself19:44
SumitNaiksatamrkukura: yeah, songole’s point about the optional extension19:45
rkukuraWe currently don’t provide any way to use the group-policy extension without the group-policy-mapping extension also being present, right?19:45
*** rockyg has quit IRC19:45
SumitNaiksatamrkukura: yes19:45
banixrkukura: right19:45
SumitNaiksatami believe the question is in cases where the mapping is slightly different (based on the mapping driver) how will this CLI handle that?19:46
songoleright19:46
rkukuraThe CLi should be prepared to handle the attributes as defined in the group-policy-mapping API (allow_put, allow_post, …)19:48
rkukuraIf the configured driver rejects an attempt to do something the API allows, the CLI users gets an exception.19:48
SumitNaiksatamrkukura: ok19:49
songoleok. Then, I will update the CLI to take those attributes as well.19:49
SumitNaiksatamsongole: i am wondering whether there is a pattern in the current CLI code to discover extensions19:49
*** SridharRamaswamy has joined #openstack-meeting-319:49
SumitNaiksatamsongole: this is done in the Horizon code19:49
songoleSumitNaiksatam: I don't think so. Will check19:49
rkukurawould be nice if extensions were negotiated19:49
rkukurathe user can use the CLI to query what extensions are supported19:50
SumitNaiksatamsongole: if there is then one could drive this based on discovering that19:50
SumitNaiksatamrkukura: yeah19:50
SumitNaiksatamsongole: perhaps you can keep it simple to begin with19:50
SumitNaiksatamsince like rkukura mentioned, we currently only have the reference mapping driver19:50
SumitNaiksatamokay with everyone?19:50
banixyes19:51
songoleok19:51
SumitNaiksatamok great19:51
SumitNaiksatam#topic Horizon update19:51
*** openstack changes topic to "Horizon update (Meeting topic: networking_policy)"19:51
SumitNaiksatami think rms_13 already indicated that he is getting the branch out of WIP pretty soon19:51
SumitNaiksatami believe the branch is #link https://review.openstack.org/9359019:52
SumitNaiksatam#topic Vendor Drivers19:52
*** openstack changes topic to "Vendor Drivers (Meeting topic: networking_policy)"19:52
SumitNaiksatamhas anyone started working on this; any questions for the team or any blockers?19:53
banixhave started working on the driver for sdn-ve19:53
SumitNaiksatambanix: cool, thanks for leading the way19:53
SumitNaiksatambanix: perhaps we can learn from your experience19:53
banixsure19:54
ivar-lazzaroI'm at early stage with the cisco driver, nothing blocking so far19:54
SumitNaiksatamivar-lazzaro: nice19:54
SumitNaiksatam#topic API intercept19:54
*** openstack changes topic to "API intercept (Meeting topic: networking_policy)"19:54
SumitNaiksatamkevinbenton: there?19:54
songolewe are making progress on our driver. no issues19:55
kevinbentonSumitNaiksatam: yeah, but might lose connection19:55
kevinbentonSumitNaiksatam: on the road19:55
banixkevinbenton: hopefully not driving :)19:55
kevinbentonSumitNaiksatam: still waiting on rkukura for feedback before opening it up19:55
SumitNaiksatamkevinbenton: oh okay, perhaps we can get an update in the next meeting then19:55
kevinbentonbanix: not while typing at lease :-)19:55
SumitNaiksatamkevinbenton: okay sure19:55
kevinbentonleast*19:55
SumitNaiksatamkevinbenton: thanks for joining!19:56
kevinbentonbanix: do you want to take a look at it?19:56
rkukurafeedback?19:56
banixsure will do19:56
rkukuraI might have missed something19:56
kevinbentonrkukura, banix: https://review.openstack.org/#/c/109901/19:56
SumitNaiksatamrkukura: i believe kevinbenton had send an email about a week back19:56
SumitNaiksatam*sent19:56
rkukuraOK, on the intercept!19:56
SumitNaiksatamrkukura: yeah19:56
rkukurasorry19:56
rkukuraI will review that in detail today or tomorrow.19:57
SumitNaiksatamrkukura: thanks19:57
kevinbentonrkukura: thx19:57
SumitNaiksatam#topic Tempest tests19:57
*** openstack changes topic to "Tempest tests (Meeting topic: networking_policy)"19:57
banixunfortuntely, i have to run; see you all later19:58
SumitNaiksatami dont have much update on this, its still at the same patch set: #link https://review.openstack.org/#/c/108234/19:58
SumitNaiksatam#topic open discussion19:58
*** openstack changes topic to "open discussion (Meeting topic: networking_policy)"19:58
SumitNaiksatambanix: thanks19:58
susaantI have posted patches for GBP heat resources https://review.openstack.org/#/c/111417/ & https://review.openstack.org/#/c/111419/19:58
SumitNaiksatamif no one has anything else to bring up, we can wrap up19:58
SumitNaiksatamsusaant: thats great19:58
SumitNaiksatamsusaant: sorry missed the heat update19:59
susaantwe will posting patches for remaining resources soon19:59
SumitNaiksatamsusaant: thanks much!19:59
SumitNaiksatamwe are exactly one hour over! :-)19:59
SumitNaiksatamwe can just pretend that we start an hour late!19:59
kevinbentonSumitNaiksatam: yeah, i figured i missed the meeting :-)19:59
SumitNaiksatamthanks all for joining, and I apologize for venting a little bit earlier19:59
SumitNaiksatamkevinbenton: :-)20:00
SumitNaiksatamalright thanks everyone!20:00
SumitNaiksatambye20:00
songolebye20:00
SumitNaiksatam#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
*** ivar-lazzaro has quit IRC20:00
rkukurabye20:00
openstackMeeting ended Thu Aug  7 20:00:28 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-08-07-18.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-08-07-18.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-08-07-18.01.log.html20:00
*** hemanthravi has quit IRC20:00
*** ivar-lazzaro has joined #openstack-meeting-320:01
*** susaant has quit IRC20:01
*** rkukura has left #openstack-meeting-320:01
*** LouisF has quit IRC20:05
*** songole has quit IRC20:06
*** banix has quit IRC20:08
*** thinrichs has quit IRC20:11
*** Krishna_ has quit IRC20:16
*** kashyap` has joined #openstack-meeting-320:17
*** MarkAtwood has quit IRC20:20
*** kashyap has quit IRC20:20
*** davidlenwell_ is now known as davidlenwell20:23
*** sarob has joined #openstack-meeting-320:28
*** lcheng_ has quit IRC20:33
*** markmcclain has quit IRC20:35
*** yamamoto has joined #openstack-meeting-320:35
*** seizadi1 has joined #openstack-meeting-320:37
*** seizadi has quit IRC20:37
*** yamamoto has quit IRC20:40
*** prasadv has quit IRC20:40
*** lcheng_ has joined #openstack-meeting-320:44
*** seizadi1 has quit IRC20:46
*** seizadi has joined #openstack-meeting-320:46
*** seizadi1 has joined #openstack-meeting-320:46
*** seizadi has quit IRC20:46
*** seizadi has joined #openstack-meeting-320:47
*** seizadi1 has quit IRC20:47
*** lcheng_ has quit IRC20:56
*** lcheng_ has joined #openstack-meeting-320:57
*** Cathy_ has quit IRC20:58
*** MarkAtwood has joined #openstack-meeting-321:01
*** lblanchard has quit IRC21:01
*** mfer has quit IRC21:06
*** amotoki has quit IRC21:13
*** yamamoto has joined #openstack-meeting-321:14
*** peristeri has quit IRC21:15
*** woodm1979 has left #openstack-meeting-321:15
*** woodm1979 has joined #openstack-meeting-321:16
*** jtomasek has quit IRC21:19
*** yamamoto has quit IRC21:20
*** thomasem has quit IRC21:20
*** cbader has quit IRC21:21
*** banix has joined #openstack-meeting-321:28
*** kashyap has joined #openstack-meeting-321:31
*** ivar-lazzaro has quit IRC21:33
*** markmcclain has joined #openstack-meeting-321:34
*** kashyap` has quit IRC21:34
*** marun has quit IRC21:46
*** dconde has joined #openstack-meeting-321:47
*** ivar-lazzaro has joined #openstack-meeting-321:48
*** julim_ has quit IRC21:50
*** SumitNaiksatam has quit IRC21:50
*** yamamoto has joined #openstack-meeting-321:50
*** SumitNaiksatam has joined #openstack-meeting-321:51
*** SumitNaiksatam__ has quit IRC21:51
*** otherwiseguy has quit IRC21:55
*** yamamoto has quit IRC21:57
*** yamamoto_ has joined #openstack-meeting-321:57
*** thinrichs has joined #openstack-meeting-321:59
*** dconde has quit IRC22:01
*** otherwiseguy has joined #openstack-meeting-322:03
*** thangp has quit IRC22:03
*** dconde has joined #openstack-meeting-322:03
*** MaxV has quit IRC22:04
*** seizadi has quit IRC22:06
*** seizadi has joined #openstack-meeting-322:07
*** yamamoto_ has quit IRC22:07
*** seizadi1 has joined #openstack-meeting-322:08
*** seizadi has quit IRC22:08
*** Rajeev has quit IRC22:12
*** jpomero_ is now known as jpomero22:14
*** carl_baldwin has quit IRC22:22
*** SumitNaiksatam has quit IRC22:25
*** SumitNaiksatam has joined #openstack-meeting-322:27
*** thinrichs has quit IRC22:30
*** SridharRamaswamy has quit IRC22:32
*** SridharRamaswamy has joined #openstack-meeting-322:32
*** SridharRamaswamy has quit IRC22:33
*** banix has quit IRC22:38
*** shwetaap has quit IRC22:38
*** marun has joined #openstack-meeting-322:40
*** SumitNaiksatam has left #openstack-meeting-322:45
*** pballand has quit IRC22:53
*** markmcclain has quit IRC22:56
*** dhellmann is now known as dhellmann_23:00
*** SridharRamaswamy has joined #openstack-meeting-323:01
*** arosen has quit IRC23:01
*** aaronorosen has joined #openstack-meeting-323:02
*** armax has joined #openstack-meeting-323:03
*** dconde has quit IRC23:03
*** dconde has joined #openstack-meeting-323:04
*** banix has joined #openstack-meeting-323:05
*** yamamoto has joined #openstack-meeting-323:05
*** lcheng_ has quit IRC23:06
*** dconde has joined #openstack-meeting-323:07
*** yamamoto has quit IRC23:10
*** jamielennox|away is now known as jamielennox23:23
*** magesh_ has joined #openstack-meeting-323:30
*** banix has quit IRC23:30
*** beagles has quit IRC23:32
*** edleafe has quit IRC23:32
*** edleafe has joined #openstack-meeting-323:33
*** lcheng_ has joined #openstack-meeting-323:33
*** lblanchard has joined #openstack-meeting-323:35
*** beagles has joined #openstack-meeting-323:36
*** beagles is now known as Guest8301323:37
*** marun has quit IRC23:40
*** ivar-lazzaro has quit IRC23:40
*** Guest83013 is now known as b3nt_pin23:41
*** magesh_ is now known as mageshgv23:41
*** lcheng_ has quit IRC23:46
*** lcheng_ has joined #openstack-meeting-323:46
*** dconde has joined #openstack-meeting-323:50
*** lcheng_ has quit IRC23:58

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