Thursday, 2014-06-26

*** SumitNaiksatam has joined #openstack-meeting-300:01
*** mestery has quit IRC00:04
*** sankarshan is now known as sankarshan_away00:06
*** cjellick has quit IRC00:14
*** yamahata has joined #openstack-meeting-300:14
*** banix has joined #openstack-meeting-300:24
*** jamiehannaford has quit IRC00:24
*** gduan has joined #openstack-meeting-300:34
*** garyduan has quit IRC00:35
*** Kanzhe has quit IRC00:40
*** seizadi has quit IRC00:42
*** yamamoto has joined #openstack-meeting-300:46
*** beyounn has quit IRC00:47
*** pballand has quit IRC00:49
*** yamamoto has quit IRC00:51
*** shakamunyi has quit IRC00:52
*** baojg has joined #openstack-meeting-300:53
*** baojg_ has joined #openstack-meeting-301:01
*** baojg has quit IRC01:02
*** markmcclain has quit IRC01:03
*** baojg_ has quit IRC01:05
*** Kanzhe has joined #openstack-meeting-301:11
*** Sukhdev has quit IRC01:14
*** armax has left #openstack-meeting-301:15
*** SumitNaiksatam has quit IRC01:17
*** markmcclain has joined #openstack-meeting-301:26
*** markmcclain has quit IRC01:28
*** samchoi has quit IRC01:42
*** yamamoto_ has joined #openstack-meeting-301:46
*** yamamoto_ has quit IRC01:51
*** yamamoto_ has joined #openstack-meeting-301:57
*** prad_ has quit IRC02:06
*** yamamoto_ has quit IRC02:12
*** otherwiseguy has joined #openstack-meeting-302:12
*** SumitNaiksatam has joined #openstack-meeting-302:18
*** Kanzhe has quit IRC02:23
*** Kanzhe has joined #openstack-meeting-302:24
*** mestery has joined #openstack-meeting-302:30
*** pballand has joined #openstack-meeting-302:31
*** carl_baldwin has joined #openstack-meeting-302:31
*** yamamoto_ has joined #openstack-meeting-302:33
*** pballand has quit IRC02:34
*** HenryG has joined #openstack-meeting-302:36
*** baojg has joined #openstack-meeting-302:45
*** yamahata has quit IRC02:52
*** yamahata has joined #openstack-meeting-302:53
*** eghobo has quit IRC03:07
*** banix has quit IRC03:19
*** sankarshan_away is now known as sankarshan03:29
*** Kanzhe has quit IRC03:31
*** garyduan has joined #openstack-meeting-303:37
*** gduan has quit IRC03:38
*** baojg has quit IRC03:50
*** baojg has joined #openstack-meeting-303:50
*** gduan has joined #openstack-meeting-303:53
*** garyduan has quit IRC03:54
*** baojg has quit IRC03:55
*** banix has joined #openstack-meeting-303:57
*** eghobo has joined #openstack-meeting-303:57
*** nati_ueno has quit IRC04:03
*** garyduan has joined #openstack-meeting-304:06
*** eghobo has quit IRC04:06
*** eghobo has joined #openstack-meeting-304:06
*** cuddyt has joined #openstack-meeting-304:07
*** baojg has joined #openstack-meeting-304:08
*** baojg has quit IRC04:08
*** baojg has joined #openstack-meeting-304:08
*** gduan has quit IRC04:09
*** cuddyt has quit IRC04:12
*** Kanzhe has joined #openstack-meeting-304:28
*** nelsnelson has joined #openstack-meeting-304:35
*** thinrichs has quit IRC04:35
*** otherwiseguy has quit IRC04:37
*** nelsnelson has quit IRC04:42
*** amitpp has joined #openstack-meeting-304:57
*** armax has joined #openstack-meeting-305:03
*** carl_baldwin has quit IRC05:05
*** shakamunyi has joined #openstack-meeting-305:07
*** banix has quit IRC05:08
*** chuckC has quit IRC05:09
*** chuckC has joined #openstack-meeting-305:10
*** shakamunyi has quit IRC05:12
*** shakamunyi has joined #openstack-meeting-305:13
*** Kanzhe has quit IRC05:16
*** Kanzhe has joined #openstack-meeting-305:16
*** armax has quit IRC05:17
*** chuckC has quit IRC05:21
*** Kanzhe_ has joined #openstack-meeting-305:21
*** Kanzhe has quit IRC05:21
*** Kanzhe_ is now known as Kanzhe05:21
*** chuckC has joined #openstack-meeting-305:24
*** coolsvap|afk is now known as coolsvap05:27
*** Kanzhe has quit IRC05:28
*** Kanzhe has joined #openstack-meeting-305:30
*** mrunge has joined #openstack-meeting-305:49
*** mrunge has quit IRC05:49
*** mrunge has joined #openstack-meeting-305:49
*** Kanzhe has quit IRC05:59
*** zehicle_at_dell has joined #openstack-meeting-306:21
*** nati_ueno has joined #openstack-meeting-306:23
*** iovadia has joined #openstack-meeting-306:28
*** baojg has quit IRC06:34
*** baojg has joined #openstack-meeting-306:36
*** jamiehannaford has joined #openstack-meeting-306:57
*** eguz has joined #openstack-meeting-307:11
*** ttrifonov_zZzz is now known as ttrifonov07:14
*** eghobo has quit IRC07:15
*** jcoufal has joined #openstack-meeting-307:16
*** jamiehannaford has quit IRC07:17
*** jamiehannaford has joined #openstack-meeting-307:18
*** mrunge is now known as Ka-Null07:24
*** Ka-Null is now known as mrunge07:24
*** jamiehan_ has joined #openstack-meeting-307:26
*** ttrifonov is now known as ttrifonov_zZzz07:28
*** eguz has quit IRC07:29
*** ttrifonov_zZzz is now known as ttrifonov07:29
*** jamiehannaford has quit IRC07:30
*** jamiehan_ has quit IRC07:33
*** jamiehannaford has joined #openstack-meeting-307:39
*** lcheng has joined #openstack-meeting-307:54
*** zz_johnthetubagu is now known as johnthetubaguy08:00
*** nati_ueno has quit IRC08:04
*** jtomasek has joined #openstack-meeting-308:05
*** nacim has joined #openstack-meeting-308:05
*** shakamunyi has quit IRC08:15
*** shakamunyi has joined #openstack-meeting-308:15
*** shakamunyi has quit IRC08:20
*** yamamoto_ has quit IRC08:28
*** yamamoto_ has joined #openstack-meeting-308:28
*** amitpp has quit IRC08:35
*** MaxV has joined #openstack-meeting-308:37
*** yamamoto_ has quit IRC08:39
*** igordcard has joined #openstack-meeting-308:42
*** igordcard has quit IRC08:47
*** safchain has joined #openstack-meeting-308:54
*** yamamoto_ has joined #openstack-meeting-309:01
*** igordcard has joined #openstack-meeting-309:05
*** shakamunyi has joined #openstack-meeting-309:16
*** shakamunyi has quit IRC09:20
*** sankarshan is now known as sankarshan_away09:28
*** yamamoto_ has quit IRC09:35
*** amitpp has joined #openstack-meeting-309:43
*** baojg has quit IRC10:05
*** baojg has joined #openstack-meeting-310:06
*** jackib has joined #openstack-meeting-310:07
*** shakamunyi has joined #openstack-meeting-310:09
*** yamamoto has joined #openstack-meeting-310:11
*** yamamoto has quit IRC10:13
*** yamamoto_ has joined #openstack-meeting-310:13
*** shakamunyi has quit IRC10:13
*** yamamoto_ has quit IRC10:17
*** zehicle_at_dell has quit IRC10:18
*** zehicle_at_dell has joined #openstack-meeting-310:18
*** MaxV has quit IRC10:36
*** yamamoto has joined #openstack-meeting-310:57
*** MaxV has joined #openstack-meeting-311:07
*** coolsvap is now known as coolsvap|afk11:07
*** shakamunyi has joined #openstack-meeting-311:10
*** MaxV has quit IRC11:12
*** amitpp has quit IRC11:13
*** shakamunyi has quit IRC11:14
*** yamahata has quit IRC11:21
*** MaxV has joined #openstack-meeting-311:34
*** lcheng has quit IRC11:44
*** amitpp has joined #openstack-meeting-311:46
*** jpomero has joined #openstack-meeting-311:51
*** jackib has quit IRC11:51
*** lcheng has joined #openstack-meeting-311:57
*** baojg has quit IRC12:02
*** baojg has joined #openstack-meeting-312:03
*** yamamoto has quit IRC12:03
*** baojg_ has joined #openstack-meeting-312:05
*** baojg_ has joined #openstack-meeting-312:06
*** baojg has quit IRC12:06
*** jackib has joined #openstack-meeting-312:07
*** SridarK has quit IRC12:09
*** devvesa has joined #openstack-meeting-312:10
*** shakamunyi has joined #openstack-meeting-312:10
*** baojg_ has quit IRC12:10
*** enykeev has quit IRC12:11
*** erecio has joined #openstack-meeting-312:13
*** shakamunyi has quit IRC12:15
*** sankarshan_away is now known as sankarshan12:18
*** lblanchard has joined #openstack-meeting-312:34
*** shakamunyi has joined #openstack-meeting-312:37
*** shakamunyi has quit IRC12:38
*** shakamunyi has joined #openstack-meeting-312:39
*** yamamoto has joined #openstack-meeting-312:42
*** shakamunyi has quit IRC12:43
*** yamamoto has quit IRC12:46
*** MaxV has quit IRC12:54
*** baojg has joined #openstack-meeting-312:56
*** thomasem has joined #openstack-meeting-312:57
*** jcoufal has quit IRC12:58
*** yamamoto has joined #openstack-meeting-313:11
*** edleafe has quit IRC13:12
*** edleafe has joined #openstack-meeting-313:13
*** jackib has quit IRC13:14
*** yamamoto has quit IRC13:16
*** julim has joined #openstack-meeting-313:16
*** otherwiseguy has joined #openstack-meeting-313:20
*** safchain has quit IRC13:23
*** MaxV has joined #openstack-meeting-313:24
*** jcoufal has joined #openstack-meeting-313:25
*** peristeri has joined #openstack-meeting-313:28
*** seizadi has joined #openstack-meeting-313:29
*** safchain has joined #openstack-meeting-313:31
*** mfer has joined #openstack-meeting-313:33
*** amitpp has quit IRC13:33
*** banix has joined #openstack-meeting-313:36
*** iovadia has quit IRC13:36
*** jackib has joined #openstack-meeting-313:38
*** shakamunyi has joined #openstack-meeting-313:40
*** shakamunyi has quit IRC13:44
*** nelsnelson has joined #openstack-meeting-313:59
*** armax has joined #openstack-meeting-314:00
*** chuckC has quit IRC14:01
*** markmcclain has joined #openstack-meeting-314:02
*** chuckC has joined #openstack-meeting-314:02
*** jcoufal has quit IRC14:03
*** nacim has quit IRC14:04
*** jcoufal has joined #openstack-meeting-314:07
*** yamamoto has joined #openstack-meeting-314:11
*** tmc3inphilly has joined #openstack-meeting-314:12
*** nati_ueno has joined #openstack-meeting-314:13
*** shakamunyi has joined #openstack-meeting-314:13
*** tmc3inphilly has left #openstack-meeting-314:13
*** prad_ has joined #openstack-meeting-314:14
*** yamamoto has quit IRC14:16
*** yamamoto has joined #openstack-meeting-314:18
*** lblanchard has quit IRC14:21
*** david-lyle has joined #openstack-meeting-314:27
*** jamiehannaford has quit IRC14:36
*** baojg has quit IRC14:39
*** salv-orlando has joined #openstack-meeting-314:40
*** eghobo has joined #openstack-meeting-314:41
*** carl_baldwin has joined #openstack-meeting-314:42
*** tmorin has joined #openstack-meeting-314:45
*** zehicle_at_dell has quit IRC14:48
*** eghobo has quit IRC14:48
*** nacim has joined #openstack-meeting-314:50
*** mrsmith has joined #openstack-meeting-314:51
*** shakamunyi has quit IRC14:57
*** juliashapovalova has left #openstack-meeting-314:58
*** cuddyt has joined #openstack-meeting-314:58
carl_baldwinhi all14:59
*** pcm_ has joined #openstack-meeting-315:00
carl_baldwinSwami: armax: safchain roaet seizadi jvoss pcm nextone92 devvesa ping15:00
armaxyello15:00
pcm_hi15:00
mrsmithhey carl15:00
carl_baldwinmrsmith: hi15:01
carl_baldwinarmax: blue15:01
yamamotohi15:01
*** jcoufal has quit IRC15:01
chuckChi15:01
carl_baldwinyamahata__: chuckC: hi15:01
carl_baldwin#startmeeting neutron_l315:01
openstackMeeting started Thu Jun 26 15:01:22 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
armaxcarl_baldwin: come on don’t be :)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
*** awang has joined #openstack-meeting-315:01
carl_baldwin#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
carl_baldwinMid-cycle sprint is coming up in almost two weeks.15:02
tmorinhi15:02
carl_baldwin#link https://etherpad.openstack.org/p/neutron-juno-mid-cycle-meeting15:02
salv-orlandoaloha15:03
carl_baldwinJuno-2 is well underway.  I think it is July 24th.15:03
carl_baldwintmorin: salv-orlando: hi15:03
carl_baldwinOur big priority is to get DVR code merged by then.15:03
carl_baldwin#topic neutron-ovs-dvr15:04
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:04
carl_baldwinDo we expect Swami today?15:04
mrsmithdoubtful - he is OOO15:05
carl_baldwinYeah, just hoping.  :)15:05
mrsmith+115:05
carl_baldwinMany of the patches have seen a lot of improvement in the last week.15:05
carl_baldwin#link https://review.openstack.org/#/q/topic:bp/neutron-ovs-dvr,n,z15:06
carl_baldwinAll but one were passing Jenkins yesterday.  That is a big improvement over just one week ago.15:06
armaxcarl_baldwin: I expect to make further progress by the end of the week15:07
*** xuhanp has joined #openstack-meeting-315:07
carl_baldwinI’m mostly happy with https://review.openstack.org/84223 now.  That is the first one that needs to merge.15:07
mrsmithcarl - one note on that patch15:08
armaxcarl_baldwin: there are still a few weaknesses that I think we can address, but all in all I am pleased to see the amount of work that went in to give the patches a better structure15:08
mrsmithone of the reviewers on the l3-agent patch15:08
mrsmithnoticed some snat functionality is missing from the l3-extension patch15:08
carl_baldwinarmax: ++15:08
*** kashyap is now known as kashyap_bbiab15:08
mrsmithI'll add a comment to the same on the l3-ext patch15:08
*** mrunge has quit IRC15:10
carl_baldwinmrsmith: Thanks for pointing that out.  I agree that there are some weaknesses but I feel like the patch is ready for broader reviewing.15:10
armaxmrsmith: is it a result of a bad merge or revision gone sour, or is it something that was never there in the first place?15:10
carl_baldwinmrsmith: Is this something you know how to address?15:10
mrsmithyes - we changed the snat port communication late in the game15:10
mrsmithwe just need to update the patch with what we have locally15:10
*** jpomero_ has joined #openstack-meeting-315:10
mrsmithnot a big deal15:10
armaxmrsmith: cool15:10
carl_baldwinmrsmith: Thanks.15:11
mrsmithnp15:11
mrsmithand it only effects DVR snat15:11
mrsmithnot legacy/regression15:11
armaxmrsmith: are you going to push a new revision to swami’s patch or shall we coordinate amongst the larger group?15:11
*** jpomero has quit IRC15:11
mrsmithno sure - I haven't been tracing the progress of that patch as much as others15:12
mrsmithwe can chat offline15:12
armaxok15:12
mrsmith*not sure15:12
armaxlet’s take this offline than15:12
armaxyou know how to find me or carl_baldwin15:12
mrsmithyup :)15:12
carl_baldwinmrsmith: Once we get that part in shape then I’d like to ping one more core to review the patch for another perspective.15:13
mrsmithyes - even now... I think the core stuff is there15:13
carl_baldwinmrsmith: Great.15:14
*** erecio has quit IRC15:14
armaxmrsmith: so we might want to consider to have the addition closer to a downstream patch15:14
mrsmithpossibly...15:14
carl_baldwinarmax: ?15:14
armaxmrsmith: I mean where it’s used, but then again, let’s talk later15:14
mrsmithit comes back to carl (and other's) wish to pull the patches together as-is and have DVR work15:14
mrsmithlegacy may work - but DVR will not15:15
carl_baldwinOkay.  Let’s move on.15:15
armaxmrsmith: right, but legacy is the deafult code path being tested15:15
mrsmithagreed15:16
armaxyup, let’s move on15:16
carl_baldwinarmax: Nice work splitting up 87730 in to multiple patches.15:16
carl_baldwinWhat is the status of those patches?  I’ve been through a couple of review cycles but I lost track of it yesterday.15:16
armaxcarl_baldwin: I need to push one more revision to update the one on the models15:17
armaxcarl_baldwin: but it won’t take me long15:17
armaxcarl_baldwin: I just need to find the time ;)15:17
carl_baldwinUnderstood.  I’ll watch for the updates and try to get my feedback up promptly.15:18
carl_baldwinOther reviewers are welcome too.  Please try to do comprehensive reviews.15:18
armax++15:19
carl_baldwinmrsmith: How is https://review.openstack.org/#/c/89413/ ?15:19
armaxyes, the fewer revisions we can do the better15:19
mrsmithgoing well15:20
mrsmithI plan to create a new dvr_util.py file15:20
mrsmithto hold some of the pure dvr methods15:20
carl_baldwinmrsmith: Great work on the tests.  Jenkins has been passing which relieves some concern.15:20
mrsmithas suggested by armax15:20
mrsmitha few other cleanups to do15:20
armaxmrsmith: yes, let’s see how it looks15:20
mrsmithotherwise pretty stable15:20
armaxyesterday I was speaking with Murali and I have some doubts15:21
mrsmithI hope to update again soon15:21
armaxon some of the config options made available there15:21
carl_baldwinWill you have time to do another turn-around on it?15:21
armaxI wonder whether we can consolidate some of them15:21
mrsmithI hop so15:21
carl_baldwinarmax: made where?  In Murali’s patch?15:21
armaxno mrsmith15:21
armax's15:21
armaxthree bool options have been defined15:21
carl_baldwinmrsmith: Please reach out if you think I can help.  I’ll make time for whatever I can do.15:21
mrsmiththanks15:22
mrsmitharmax - doubts on the config?15:22
armaxhowever of the 8 combinations available only a handful would make sense15:22
armaxso I wonder if we can abstract soem of them, instead of talking binary we can talk English15:22
carl_baldwinarmax: +1 I’ve wondered about that.15:22
armaxmrsmith: I’ll take that on the review, it’s the best place to discuss this15:22
mrsmithI'm open to suggestions15:22
armaxmrsmith: sure15:23
mrsmithwe tried to keep things simple and yet support many setups15:23
armaxI am open to giving them :)15:23
*** lblanchard has joined #openstack-meeting-315:23
mrsmithfor example - single node setup may not make sense15:23
carl_baldwinWe’ll look for that discussion on the review.15:23
mrsmithbut we may need to support it for tests15:23
armaxagreed, but I had a hard time wrapping my head around them, I wonder what an operator would do  if he does not want to dive in the code15:23
mrsmithsure15:24
armaxmrsmith: I think my concern is more an usability issue rather than correctness of the solution proposed15:24
armaxs/an/a15:24
armaxanyhoo let’s move past thsi15:24
mrsmitharmax: ok - we want usability (aka ease of use)15:24
armax*this15:24
carl_baldwinIs Murali on IRC?  I don’t know his nick.15:25
mrsmithdon't think so..15:25
*** lblanchard has quit IRC15:25
mrsmithprobably woulda chimed in by now15:25
armaxcarl_baldwin: maybe I can help15:26
armaxI spoke with him last nite15:26
carl_baldwinI’m most concerned about https://review.openstack.org/#/c/89694/.15:26
armaxcarl_baldwin: what do you wanna know?15:26
carl_baldwinThe Jenkins failures mostly.  I fear that reviewers are not giving it any attention because of the failiures.15:26
armaxcarl_baldwin: correct15:27
armaxthis is the only patch that has never passed tests so far15:27
armaxI have a pretty good understanding why Tempest tests are failing15:27
armaxI can look at the UT too15:27
carl_baldwinRight.  From one perspective, that is great progress.15:28
armaxso if Murali doesn’t beat me to it I’ll bash the patch into shape later today15:28
carl_baldwinarmax: Would you like some help with the UTs?15:28
*** cjellick has joined #openstack-meeting-315:28
armaxyesterday we had a different failure mode as of today15:28
armaxso I need to look at it again15:28
carl_baldwinarmax: What is up with the Tempest tests?15:28
armaxcarl_baldwin: if you can spare a few minutes that’d be great15:29
carl_baldwinYes, I can make time for it.15:29
armaxcarl_baldwin: fundamentally Murali’s patch depends on mrsmith’s15:29
armaxthat said…15:29
carl_baldwinI did follow your rebase.  Good move.15:29
armaxthat is only true for the ‘distributed’ code path15:29
mrsmitharmax: right15:29
armaxthe centralized code path shouldn’t be affected15:30
mrsmithlegacy shouldn't be affected15:30
armaxbut it looks like the scheduler code being proposed alters that15:30
armaxand when a tempest test tries to add a rotuer to an agent15:30
carl_baldwinarmax: alters it how?15:30
*** nacim has quit IRC15:30
armaxneutron is not able to find an eligible agent15:30
armaxit alters the election logic to find a suitable agent to move the router on15:31
armaxI pinpointed the problem in the code when speaking with Murali15:31
armaxthen he pushed another patch but it doesn’t seem it did any effect so I need to see at the diff he pushed15:32
*** julim has quit IRC15:32
carl_baldwinarmax: Since you have a handle on that.  I’ll leave you to it but I will plan to get to the UTs later today.15:32
armaxgreate15:32
armaxgreat15:32
armaxthanks15:32
carl_baldwinSorry to take the whole meeting for DVR but I have one more thing.15:33
carl_baldwinWe have 7 interdependent patches in flight.15:33
carl_baldwinI prefer this over the larger patches but it does present problems of its own.15:34
armaxif there’s nothing else, maybe we can move on15:34
*** nati_ueno has quit IRC15:35
carl_baldwinWith different authors on different patches it is easy to clobber things.15:35
armaxcarl_baldwin: true, but that’s the nature of collaborative open source business :)15:36
armaxcarl_baldwin: can’t argue with the fact that things could’ve been simpler15:36
carl_baldwinI think uploading patches with —no-rebase is a good idea.  The problem this avoids is that otherwise, uploading a patch rebases the dependent patches which another author may be working on.15:36
armaxcarl_baldwin: but there’s always a lesson to be learned15:37
carl_baldwinBut, this means that we’ll need to think about rebasing consciously because we can’t get behind by more than a day or two.15:37
carl_baldwinThoughts?15:38
*** markmcclain has quit IRC15:38
armaxcarl_baldwin: it’s difficult because it depends on the punctual state the patches are in15:38
armaxand how trunk moves forward15:38
armaxin theory we can have people do git-review with --no-rebase15:39
armaxand have a person that does a single sweep twice a week for instances15:39
armaxbut then what happens if the root patch goes sour and merge conflicts arise?15:39
armaxso maybe we can use —no-rebase as the committer’s default action15:40
carl_baldwinI’d prefer that.  I am willing to watch the patches and ping authors when they need to rebase.15:40
armaxand if a merge conflict arises we you or I can do a global sweep15:40
armaxyou as in carl_baldwin15:40
carl_baldwinMerge conflicts are inevitable.  They will happen either way.  I’d just prefer they happen when the author is ready.15:41
carl_baldwinYes, I am willing to handle it because I think it will be better for authors to not have their patches moved out from under them.15:41
*** erecio has joined #openstack-meeting-315:42
carl_baldwinI’ll watch daily for any patch that is two days out of date from its upstream.15:42
armaxcool15:43
carl_baldwinOkay.  Anything else on DVR?15:43
*** nacim has joined #openstack-meeting-315:43
carl_baldwin#topic l3-svcs-vendor-*15:44
*** openstack changes topic to "l3-svcs-vendor-* (Meeting topic: neutron_l3)"15:44
carl_baldwinpcm_: hi15:44
pcm_Hi15:44
carl_baldwinAny update here?15:44
pcm_Have reference implementation out for review #link https://review.openstack.org/#/c/102351/415:44
pcm_Having a Jenkins failure, 'process-returncode'. Not sure where the error is on that. Could use some ides.15:45
pcm_ideas.15:45
carl_baldwinprocess-returncode is not interesting by itself.  Are there other failures?15:45
pcm_Have a Cisco patch ready for review, but waiting, until I can get the ref one clean.15:45
yamamotoisn't the real failure is another one?15:45
yamamotoie. test_reference_driver_used15:45
carl_baldwinYes, the other failure is the interesting one.15:46
pcm_It shows two failures in the summary, but only FAIL line I see is for process-returncode15:46
pcm_odd15:46
pcm_#link http://logs.openstack.org/51/102351/4/check/gate-neutron-python27/a757b36/console.html15:46
carl_baldwinYeah, there isn’t much in the report at all.15:46
yamamotolook at testr_results15:46
pcm_yamamoto: OK will do.15:47
*** xuhanp has quit IRC15:47
carl_baldwinI looked and it doesn’t have much.15:47
carl_baldwinpcm_: Does that test pass locally for you?15:47
*** eghobo has joined #openstack-meeting-315:47
*** eghobo has quit IRC15:48
*** eghobo has joined #openstack-meeting-315:48
pcm_On the last run (in a VM) I get the same result, though I occasionally get unrelated errors on runs.15:48
pcm_Rerunning again to see.15:48
carl_baldwinWe should probably take this out of the meeting.  Ping me later today on it.15:49
pcm_will do15:49
carl_baldwinYou’ll want to have Jenkins passing fully to get on reviewers radar.  Anything else?15:49
carl_baldwin#topic l3-high-availability15:49
*** openstack changes topic to "l3-high-availability (Meeting topic: neutron_l3)"15:49
pcm_Nope. I had it working in V2, but made a change and it failed.15:49
carl_baldwinsafchain: Are you around?15:49
*** Rajeev has joined #openstack-meeting-315:50
carl_baldwin#topic bgp-dynamic-routing15:51
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:51
carl_baldwinnextone92: devvesa: hi15:51
devvesao/15:51
carl_baldwinI didn’t quite finish my review of your bp.  I need to finish that today.15:51
carl_baldwinI wanted another look at the diagrams.15:52
devvesaok, great15:52
carl_baldwinDid you see my comments?15:52
devvesayes15:52
devvesathanks for respond the questions15:52
carl_baldwinCould those points be worked in to the bp to make things a little clearer?15:53
devvesayes, sure15:53
devvesaI'll wait your today's review and I'll prepare another patch15:53
carl_baldwinOkay.  I don’t promise I’ll get to it early.15:54
*** awang has quit IRC15:54
carl_baldwinBut, I will get to it.15:54
devvesa6pm here. today's review will be tomorrow for me :)15:54
carl_baldwinOkay.15:54
carl_baldwinAnything else?15:54
tmorinlast week, yamamoto was wanting an intro on bagpipe15:54
tmorinI'm avail if people have questions15:55
carl_baldwintmorin: Thanks.  I’m sorry I haven’t given that thread any attention yet.  It is still in my queue.15:55
tmorinwell, I guess the question is the choice of BGP speaker for bgp dynamic routing15:56
tmorinwe are working to implement the bgp vpn connectivity blueprint with bagpipe15:56
carl_baldwinOnly for the reference implementation.  I think there will be multiple implementations given the interest that I’ve seen.15:56
tmorinyes, possibly so15:57
carl_baldwintmorin: Are you working with Nachi on that?15:57
tmorinon the bgp vpn connection bp ? yes15:57
carl_baldwinGreat.15:58
devvesakeshava also seemed to be interested in bgp-vpn15:58
tmorinyes15:58
tmorinwe had a discuss on the list15:58
carl_baldwinYes.  There is plenty of interest.15:58
tmorinanyways, if people want to investigate bagpipe for the dynamic (non-VPN) routing bp, feel free to ping me15:59
carl_baldwinWe’re almost out of time.  Let’s keep the ML threads going.  I will add my thoughts soon.15:59
tmorinthe non-VPN case should be easy to add to bagpipe15:59
tmorinok15:59
tmorinthanks15:59
devvesatmorin: I'll take into account for sure15:59
carl_baldwin#topic neutron-ipam15:59
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:59
tmoringreat, we're open15:59
*** awang has joined #openstack-meeting-315:59
carl_baldwinWe have 10 seconds.  :)15:59
*** shakamunyi has joined #openstack-meeting-315:59
carl_baldwinI just wanted to say I haven’t forgotten about this topic.16:00
carl_baldwinI am part way through a review of the bp but other priorities have starved it.16:00
seizadiHi - I'll be short I have all changes in bp and we are still on track for juno-216:00
carl_baldwinI encourage reviewers with interest to go add their comments and keep it going.16:00
*** tmorin has quit IRC16:00
carl_baldwinseizadi: Thanks for keeping the momentum going.16:00
*** igordcard has quit IRC16:01
*** pballand has joined #openstack-meeting-316:01
carl_baldwinThat is all we have time for.16:01
carl_baldwin#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
openstackMeeting ended Thu Jun 26 16:01:06 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-06-26-15.01.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-06-26-15.01.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-06-26-15.01.log.html16:01
carl_baldwinThanks, all!  Great work!16:01
pcm_bye16:01
*** devvesa has quit IRC16:01
*** pcm_ has left #openstack-meeting-316:01
yamamotobye16:01
*** mrsmith has quit IRC16:01
*** seizadi has left #openstack-meeting-316:05
*** chuckC has quit IRC16:07
*** pballand has quit IRC16:07
*** jackib has quit IRC16:08
*** awang has quit IRC16:11
*** jackib has joined #openstack-meeting-316:14
*** amitpp has joined #openstack-meeting-316:19
*** erecio has quit IRC16:20
*** erecio has joined #openstack-meeting-316:27
*** awang has joined #openstack-meeting-316:31
*** pballand has joined #openstack-meeting-316:31
*** nacim has quit IRC16:34
*** beyounn has joined #openstack-meeting-316:35
*** awang has quit IRC16:35
*** MaxV has quit IRC16:36
*** jpomero_ is now known as jpomero16:40
*** catherine_d has joined #openstack-meeting-316:43
*** sankarshan is now known as sankarshan_away16:49
*** chuckC has joined #openstack-meeting-316:50
*** nati_ueno has joined #openstack-meeting-316:55
*** sarob has joined #openstack-meeting-316:57
*** Rajeev has quit IRC16:58
*** jackib has quit IRC16:59
*** kashyap_bbiab is now known as kashyap17:00
*** jackib has joined #openstack-meeting-317:00
*** kashyap is now known as kashyap_bbiab17:01
*** david-lyle has quit IRC17:01
*** david-lyle has joined #openstack-meeting-317:02
*** kashyap_bbiab is now known as kashyap17:02
*** praveen_dell has joined #openstack-meeting-317:02
*** david-lyle has quit IRC17:03
*** peristeri has quit IRC17:04
*** david-lyle has joined #openstack-meeting-317:04
*** jackib has quit IRC17:04
*** catherine_d has left #openstack-meeting-317:06
praveen_dellis the meeting going on today?17:06
sarob No david?17:07
*** praveen_dell has quit IRC17:08
sarobDavidlenwell?17:08
davidlenwellyes17:09
davidlenwellmeetings have changed to mondays at 3pm17:10
sarobAh, irc ical hasn't updated yet17:10
sarobThx17:10
davidlenwellsee ya monday17:11
*** peristeri has joined #openstack-meeting-317:12
*** jackib has joined #openstack-meeting-317:12
sarobRoger17:12
*** markmcclain has joined #openstack-meeting-317:16
*** safchain has quit IRC17:17
*** sarob has quit IRC17:17
*** markmcclain1 has joined #openstack-meeting-317:18
*** lsmola__ has quit IRC17:19
*** thinrichs has joined #openstack-meeting-317:20
*** markmcclain has quit IRC17:20
*** peristeri has quit IRC17:25
*** jaypipes has joined #openstack-meeting-317:30
*** otherwiseguy has quit IRC17:33
*** Cathy_ has joined #openstack-meeting-317:38
*** kenhui has joined #openstack-meeting-317:41
*** shakamunyi has quit IRC17:41
*** MarkAtwood has joined #openstack-meeting-317:42
*** yamamoto has quit IRC17:42
*** Cathy_ has quit IRC17:43
*** LouisF has joined #openstack-meeting-317:47
*** ivar-lazzaro has joined #openstack-meeting-317:50
*** peristeri has joined #openstack-meeting-317:50
*** amitpp has quit IRC17:52
*** LouisF has quit IRC17:53
*** LouisF has joined #openstack-meeting-317:54
*** johnthetubaguy is now known as zz_johnthetubagu17:56
*** markmcclain1 has quit IRC17:57
*** rkukura has joined #openstack-meeting-318:00
SumitNaiksatamhi Neutron Group Policy folks!18:00
SumitNaiksatamrkukura: ah nice to see you online18:00
*** david-lyle has quit IRC18:00
rkukurahi18:01
banixhi18:01
*** s3wong has joined #openstack-meeting-318:01
rkukuraSumitNaiksatam: back home for today, traveling again tomorrow18:01
SumitNaiksatami guess people are still recovering from the dying minutes of the game!18:01
*** david-lyle has joined #openstack-meeting-318:01
SumitNaiksatamrkukura: ok good, twins have been dispatced? ;-)18:01
rkukuraalmost tied it up18:01
SumitNaiksatam*dispatched18:01
*** OSM has joined #openstack-meeting-318:01
rkukuratwins are in Israel18:01
SumitNaiksatambanix: hi18:01
SumitNaiksatamrkukura: sweet18:01
*** Cathy_ has joined #openstack-meeting-318:01
*** OSM is now known as songole18:02
SumitNaiksatamok lets get started18:02
SumitNaiksatam#startmeeting networking_policy18:02
openstackMeeting started Thu Jun 26 18:02:42 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
SumitNaiksatam#info agenda: https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy18:02
SumitNaiksatam#topic API/Resource Model patches18:03
*** openstack changes topic to "API/Resource Model patches (Meeting topic: networking_policy)"18:03
*** jackib has quit IRC18:03
SumitNaiksatamso as in the past week, there was decent amount of review acitvity on these patches18:03
SumitNaiksatambtw, for the links to all the patches see: #link https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy#June_26.2C_19.2C_12.2C_201418:04
SumitNaiksatamhad been planning to put the above in a wiki page18:04
*** david-lyle has quit IRC18:04
*** david-ly_ has joined #openstack-meeting-318:04
SumitNaiksatami still need to respond to HenryG and enikanorov’s comments on the DB patch, but nothing major there18:04
SumitNaiksatamother than that, the API patch for the classifier, actions and rules was also posted:18:05
SumitNaiksatam#link https://review.openstack.org/#/c/10181618:05
*** shakamunyi has joined #openstack-meeting-318:05
rkukuraSumitNaiksatam: Should I wait for you to update the gp-*-1 patches before rebasing mine?18:05
SumitNaiksatamrkukura: if you can that will be good, i will try to do it asap after the meeting (my plan was to have done that yesterday itself)18:05
SumitNaiksatamrkukura: i will drop you a note as soon as i am done18:06
*** MarkAtwood has quit IRC18:06
rkukuraOK, want to minimize churn, so I’ll wait18:06
SumitNaiksatamrkukura: ok cool18:06
SumitNaiksatamthats pretty much my update, open to questions/comments18:06
SumitNaiksatamif no questions then we can move to the mapping update18:07
SumitNaiksatam#topic Mapping api/driver/data path patches18:07
*** openstack changes topic to "Mapping api/driver/data path patches (Meeting topic: networking_policy)"18:07
SumitNaiksatamrkukura: over to you18:08
rkukuraI’m on PTO yesterday through next Wednesday (7/2), but am trying to finish up the two driver patches18:08
SumitNaiksatamrkukura: i updated the agenda with the links to the patches18:08
rkukuraI’ll rebase the exisitng patches on SumitNaiksatam’s upcoming update, and post those today18:08
LouisFrkukura: when an EPG is created, does a network and subnet also get created?18:09
rkukuraI hope to have the implicit policy driver patch posted today18:09
SumitNaiksatamrkukura: nice!18:09
rkukuraLouisF: The resource mapping driver will take care of creating the subnet for the EPG18:09
rkukuraThe implicit policy driver will create the L2P for the EPG if one isn’t passed in explciitly18:10
s3wongrkukura: these patches will be using the python-clients?18:10
LouisFrkukura: and network also?18:10
rkukuraand the resource mapping driver will create the network for the L2P18:10
rkukuraThe plan is for the resource mapping driver to use the python client for non-GP APIs18:10
SumitNaiksatamLouisF: L2P maps to the network18:10
rkukuraThe implicit policy driver is currently calling the plugin directly18:11
LouisFrkukura: when will use of python client be added?18:12
rkukuraIt turns out the PoC code in these drivers needs significant work to be ready to review and merge, like deletion of resources, unit tests, etc.18:12
SumitNaiksatams3wong: i believe you will need to use the python client for the security group mapping18:12
s3wongSumitNaiksatam: yes - hence the question to rkukura :-)18:12
rkukuraLouisF: That will be added to the resource mapping driver before its posted for review, hopefully in the next couple days18:12
SumitNaiksatams3wong: i realized that, hence reiterating :-)18:12
LouisFrkukura: will look out for it18:12
rkukuraOK18:13
rkukuraLouisF: Do you see any problem with calling the GP plugin directly in the implicit policy driver?18:13
LouisFrkukura: no18:14
SumitNaiksatamrkukura: perhaps having a very high level block diagram with the different pieces (implicit driver, mapping driver, etc) might help in review18:14
LouisF+118:14
rkukuraOK, great18:14
SumitNaiksatamrkukura: and posting on our GP wiki18:14
SumitNaiksatamrkukura: will you have time at all for this, or we can see if someone else can put it there18:14
*** zehicle_at_dell has joined #openstack-meeting-318:14
rkukuraI’ll see if I can come up with something, but I’m on PTO, so I can’t get away with too much time on work18:14
s3wongrkukura: why not :-) ?18:15
rkukuraSomeone else doing the diagram would be great18:15
*** shakamunyi has quit IRC18:15
rkukuraworking while snorkeling or ziplining would not go well18:15
SumitNaiksatam#action SumitNaiksatam to put block diagram for mapping driver (or delegate to someone else :-P)18:15
rkukurawhile flying is fine18:16
*** kenhui has quit IRC18:16
* SumitNaiksatam rkukura has planned an adventorous vacation! :-)18:16
SumitNaiksatamrkukura: any other questions for rkukura?18:17
rkukuraSumitNaiksatam: this is what we’ve been waiting for since the twins were born 16 years ago18:17
SumitNaiksatamrkukura: you absolutely deserve it!18:17
LouisFenjoy18:17
rkukurathanks18:17
rkukuraany other mapping questions18:17
rkukura?18:17
*** kenhui has joined #openstack-meeting-318:17
LouisFmapping of policy rules to security groups?18:18
SumitNaiksatams3wong: perhaps you want to give a quick update on the security groups mapping (to the extent that you have thought about it)?18:18
SumitNaiksatamLouisF: ah LouisF right on cue :-)18:18
LouisFworking on my timing...18:18
s3wongSumitNaiksatam: still reading rkukura 's code to understand the structure of the current mapping driver18:19
SumitNaiksatams3wong: sure18:19
SumitNaiksatams3wong: whats the high level plan?18:19
SumitNaiksatams3wong: for the benefit of everyone here18:20
rkukuras3wong: I’ll probably be adding some tables in the driver, and maybe we could store the SG_id there18:20
rkukuras3wong: Assuming we don’t want to expose the SG in the API like we do for the port, network, subnet, and router18:20
SumitNaiksatamrkukura: probably not18:21
s3wongrkukura: yes, we certainly don't want to make SG visible in the API18:21
rkukuras3wong, SumitNaiksatam: Is the rationale that we need complete control of the SG, and can’t let users muck with it?18:22
*** pballand has quit IRC18:22
SumitNaiksatamrkukura: that has been the thinking until this point18:22
s3wongrkukura: we should, right?18:22
rkukuraI agree we need complete control, since SG rule ordering is important, so we should not expose it in the API18:23
SumitNaiksatamrkukura: i think differnt backends can enforce the contract rules in different ways, so in that sense SG mapping is an implementation detail here18:23
rkukuraright, even if a backend exposes networks, subnets, and ports, it may not be using SGs for policy rendering18:23
SumitNaiksatamrkukura: yeah18:23
rkukuraseems we all agree to keep the SGs internal to the mapping driver, right?18:24
s3wongrkukura: yes18:24
SumitNaiksatamrkukura: that said, to your point, i believe if the user really wants to muck around with the mapped SGs he would still be able to do it, right?18:24
SumitNaiksatamrkukura: i mean the mapped SGs would be visible to him18:24
rkukuraUnless we create them with a different tenant, the user can discover and update/delete them18:25
SumitNaiksatamrkukura: ok, so s3wong something to think about18:25
LouisFwill this SG that is "owned" by GBP appear in the SG list?18:25
SumitNaiksatamLouisF: we hadnt planned a separate “GBP” tenant until this point18:25
s3wongrkukura: can a SG created by a different tenant be apply to traffic in the other tenant?18:26
*** lenrow has joined #openstack-meeting-318:26
rkukuraI think we should stick with using the client’s tenant for now, but keep the option open to change that later. But SGs may need to be the same tenant as the port - not sure18:26
SumitNaiksatamrkukura: +118:26
*** zehicle_at_dell has quit IRC18:26
SumitNaiksatamwe can perhaps evolve with a new role, like what is being propose with the “adv services” role18:27
*** zehicle_at_dell has joined #openstack-meeting-318:27
SumitNaiksatam#link https://review.openstack.org/10128118:27
s3wongSumitNaiksatam: the "adv services" role gets admin previleges, right?18:27
SumitNaiksatamthe above was FYI for the advsvs role18:27
SumitNaiksatams3wong: yes18:27
SumitNaiksatamon a slightly different note18:28
SumitNaiksatamregarding the stacking of patches18:28
SumitNaiksatammay be i will change the topic18:28
SumitNaiksatambefore that any other questions for s3wong on SG mapping (he just started looking at this, so be kind to him)18:28
s3wongso kind :-)18:29
SumitNaiksatams3wong: is there anything more that you need to sort out?18:29
SumitNaiksatamok moving on18:30
s3wongSumitNaiksatam: just generally understand what there currently, and how/when to invoke python-clients18:30
SumitNaiksatams3wong: ok18:30
s3wongSumitNaiksatam: so need more investigation before I can ask proper questions :-)18:30
SumitNaiksatam#topic Stacking of patches18:30
*** openstack changes topic to "Stacking of patches (Meeting topic: networking_policy)"18:30
SumitNaiksatams3wong: ok18:30
SumitNaiksatamso initially we had the plan to make progress in “bread” and “depth” fashion wih regards to stacking the patches18:31
s3wongbreath?18:31
SumitNaiksatamwhere depth goes from API to the driver/data path level18:31
*** peristeri has quit IRC18:31
SumitNaiksatamand breadth traverses the resources in the GP model18:31
SumitNaiksatams3wong: ^^^18:31
s3wong:-)18:32
SumitNaiksatamto that end we have the depth series with EP, EPG, L2/3P18:32
SumitNaiksatami started the breadth series with the classifier, action, rules18:32
*** sarob has joined #openstack-meeting-318:32
*** kenhui has quit IRC18:33
* SumitNaiksatam thinks needs rkukura’s help for 3 lettter acronymys for classifier, actions, rules18:33
rkukuraCARs18:33
SumitNaiksatamso the classifier, … API patch is currently based of the GP-plugin-1 patch18:34
SumitNaiksatamrkukura: :-)18:34
*** erecio has quit IRC18:34
SumitNaiksatambut when you pull that GP-API-2 patch, you dont get any of the mapping stuff18:34
SumitNaiksatamor the anticipated driver stuff18:34
SumitNaiksatamand the SG mapping would need that18:34
SumitNaiksatamso the question is, should we have one linear series of patches?18:35
SumitNaiksatami guess its unavoidable, but it will be one long series!18:35
rkukuraI think we’ll eventually need to make it linear, but short term can have forks18:35
rkukurahopefully we can get the gp-*-1 series merged before too long18:36
Cathy_SumitNaiksatam: a side question on this. Is there any sync-up on the classifier between GBP and Traffic Steering when they are both used for support of service chaining?18:36
rkukurafor now, both gpm-*-1 and gp*-2 are based off gp-api-1, right18:37
rkukura?18:37
SumitNaiksatamrkukura: that was the hope that we would get it merged sooner18:37
SumitNaiksatamrkukura: yes, GP-API-2 is based off GP-Plugin-118:37
rkukurathat’s what I meant18:38
SumitNaiksatamrkukura: yeah18:38
SumitNaiksatamCathy_: thanks for bringing that up18:38
rkukuraso we could rebase gp-*-2 off of gpm-plugin-1 at any point18:38
SumitNaiksatamrkukura: yeah, actuall i would think GPM-Driver-*?18:38
rkukurathen later rebase them off gpm-rmd-118:39
SumitNaiksatamrkukura: RMD?18:39
rkukuragp-api-1, gp-db-1, gp-plugin-1, gpm-api-1, gpm-db-1, gpm-plugin-1, gpm-ipd-1, gpm-rmd-1, gp-api-2, …?18:40
rkukuraresource mapping driver18:40
rkukuragpm-ipd-1 is implicit policy driver18:40
SumitNaiksatamrkukura: yeah, got that! :-)18:40
Cathy_SumitNaiksatam: sure. If  you need any help on the part related to service chaining, please let me know.18:40
SumitNaiksatamrkukura: acronym czar! :-)18:40
SumitNaiksatamCathy_: thats the next topic18:41
SumitNaiksatam#topic Services’ integration18:41
*** openstack changes topic to "Services’ integration (Meeting topic: networking_policy)"18:41
SumitNaiksatami was hoping mandeep would be around to discuss the service chaining18:42
SumitNaiksatamis cgoncalves around?18:42
Cathy_I hope so18:42
*** openstackstatus has joined #openstack-meeting-318:42
*** ChanServ sets mode: +v openstackstatus18:42
SumitNaiksatami dont see mandeep in this channel though18:42
*** armax has quit IRC18:42
s3wongSumitNaiksatam: too late at night for folks in Europe18:42
s3wong(not mandeep)18:42
*** armax has joined #openstack-meeting-318:43
*** yamamoto has joined #openstack-meeting-318:43
SumitNaiksatamyeah, so both cgoncalves and mandeep are not around18:43
SumitNaiksatamCathy_: the way i understand it, the service chaining bp was written to be independent of the implementation menchanism18:44
SumitNaiksatamCathy_: which means that the TS is not strictly required for implementing the service chaining18:44
SumitNaiksatamCathy_: also the intial focus of the service chaining bp is on the services which are exposed in neutron18:45
*** seizadi has joined #openstack-meeting-318:45
Cathy_SumitNaiksatam: Yes, I understand, but when it is used for service chaining, the API should not cause any conflict between the API in GBP or the other way around18:45
SumitNaiksatamCathy_: in the GP reference implementation, we will point to a service or a service chain UUID in the redirect action18:45
SumitNaiksatamCathy_: that is a good point18:45
*** lenrow has quit IRC18:46
*** s3wong has quit IRC18:46
*** jaypipes has quit IRC18:46
*** thinrichs has quit IRC18:46
*** cjellick has quit IRC18:46
*** garyduan has quit IRC18:46
*** davidlenwell has quit IRC18:46
*** glenc has quit IRC18:46
*** leifz has quit IRC18:46
*** armax has quit IRC18:46
*** david-ly_ has quit IRC18:46
*** prad_ has quit IRC18:46
*** banix has quit IRC18:46
*** mfer has quit IRC18:46
*** lcheng has quit IRC18:46
*** jtomasek has quit IRC18:46
*** SumitNaiksatam has quit IRC18:46
*** haleyb has quit IRC18:46
*** gothicmindfood has quit IRC18:46
*** sarob has quit IRC18:46
*** eghobo has quit IRC18:46
*** edleafe has quit IRC18:46
*** wendar has quit IRC18:46
*** dolphm has quit IRC18:46
*** russellb has quit IRC18:46
*** vishy has quit IRC18:46
*** Adri2000 has quit IRC18:46
*** zigo has quit IRC18:46
*** notmyname has quit IRC18:46
*** briancurtin has quit IRC18:46
*** ttx has quit IRC18:46
*** abramley has quit IRC18:46
*** armax has joined #openstack-meeting-318:46
*** sarob has joined #openstack-meeting-318:46
*** lenrow has joined #openstack-meeting-318:46
*** david-ly_ has joined #openstack-meeting-318:46
*** s3wong has joined #openstack-meeting-318:46
*** jaypipes has joined #openstack-meeting-318:46
*** thinrichs has joined #openstack-meeting-318:46
*** eghobo has joined #openstack-meeting-318:46
*** cjellick has joined #openstack-meeting-318:46
*** prad_ has joined #openstack-meeting-318:46
*** banix has joined #openstack-meeting-318:46
*** mfer has joined #openstack-meeting-318:46
*** edleafe has joined #openstack-meeting-318:46
*** lcheng has joined #openstack-meeting-318:46
*** jtomasek has joined #openstack-meeting-318:46
*** garyduan has joined #openstack-meeting-318:46
*** SumitNaiksatam has joined #openstack-meeting-318:46
*** briancurtin has joined #openstack-meeting-318:46
*** gothicmindfood has joined #openstack-meeting-318:46
*** haleyb has joined #openstack-meeting-318:46
*** davidlenwell has joined #openstack-meeting-318:46
*** glenc has joined #openstack-meeting-318:46
*** wendar has joined #openstack-meeting-318:46
*** leifz has joined #openstack-meeting-318:46
*** dolphm has joined #openstack-meeting-318:46
*** russellb has joined #openstack-meeting-318:46
*** ttx has joined #openstack-meeting-318:46
*** notmyname has joined #openstack-meeting-318:46
*** zigo has joined #openstack-meeting-318:46
*** abramley has joined #openstack-meeting-318:46
*** Adri2000 has joined #openstack-meeting-318:46
*** vishy has joined #openstack-meeting-318:46
*** markmcclain has joined #openstack-meeting-318:46
SumitNaiksatamCathy_: the port-chaining API in the TS bp is useful for chaining services which are realized in VMs and which Neutron is not aware of18:47
*** david-ly_ has quit IRC18:47
SumitNaiksatami hope we still have everyone here after the split18:47
LouisFhere18:47
Cathy_SumitNaiksatam: could you clarify what is meant by point to a "service" in the redirect?18:47
*** s3wong_ has joined #openstack-meeting-318:47
*** david-lyle has joined #openstack-meeting-318:47
s3wong_I was kicked out18:48
banixy18:48
rkukuraI’m here18:48
*** yamamoto has quit IRC18:48
*** jeblair has quit IRC18:48
*** dansmith has quit IRC18:48
*** lifeless has quit IRC18:48
*** dansmith has joined #openstack-meeting-318:48
*** jeblair has joined #openstack-meeting-318:48
s3wong_topic still intact, or maybe that's just my client18:48
*** lifeless has joined #openstack-meeting-318:48
Cathy_SumitNaiksatam: does that mean user can specify a sequence of service instance IDs after the "redirect"?18:49
SumitNaiksatamCathy_: is you question whethe we will allow the port-chain to be used in the redirect action?18:49
*** david-lyle has quit IRC18:49
Cathy_SumitNaiksatam: not really18:49
*** nati_ueno has quit IRC18:49
*** peristeri has joined #openstack-meeting-318:49
s3wong_Cathy_: we don't. Just ONE UUID for now18:49
SumitNaiksatam*whether18:50
Cathy_s3wong_: thanks. How about in the future? since SumitNaiksatam mentions "service" for redirect too?18:50
*** david-lyle has joined #openstack-meeting-318:50
s3wong_Cathy_: for now we are thinking that if you want a chain, the chain would be created by service chaining APIs18:51
*** shakamunyi has joined #openstack-meeting-318:51
*** ttrifonov is now known as ttrifonov_zZzz18:51
s3wong_since it is highly unlikely that the user of GBP APIs (app-owners) would want to chain his own service chains18:51
SumitNaiksatams3wong banix Cathy_ LouisF: still there?18:52
Cathy_I think it is not chain his own service chain. It is redirect a flow to a service chain which consists of a sequence of service function instances, right?18:52
s3wong_SumitNaiksatam: hi18:52
LouisFyes18:52
banixyes18:52
*** jackib has joined #openstack-meeting-318:52
s3wong_Cathy_: in that case, can the service functions be chained by the service chaining APIs?18:53
*** nati_ueno has joined #openstack-meeting-318:53
Cathy_s3wong_: not sure what you meant by that?18:53
*** sarob has quit IRC18:53
Cathy_s3wong_: are you taking about the service chaining API in advanced service BP?18:53
s3wong_Cathy_: yes18:54
Cathy_here is my thought18:54
SumitNaiksatamare we all back?18:54
Cathy_The service chaining API can specify the sequence of service function instances which is identified by a unique chain-ID and this chain-ID can be used in GBP for the "redirect"18:55
LouisFCathy_: https://review.openstack.org/#/c/9352418:55
s3wong_Cathy_: yes18:55
Cathy_good, so now the issues is18:55
*** jaypipes_ has joined #openstack-meeting-318:55
SumitNaiksatams3wong banix rkukura songole Cathy_ LouisF: there?18:55
Cathy_we only need one place to specify the classifier18:56
s3wong_SumitNaiksatam: hello?18:56
Cathy_SumitNaiksatam: yes I am here.18:56
rkukurayes18:56
banixSumitNaiksatam: been here all along :)18:56
LouisFSumitNaiksatam: here18:56
s3wong_my nic has changed though, from s3wong -> s3wong_18:56
SumitNaiksatamoh i think i was on the other side of the split18:56
*** jaypipes_ has quit IRC18:56
*** ttrifonov_zZzz is now known as ttrifonov18:56
*** lenrow has quit IRC18:56
*** s3wong has quit IRC18:56
*** jaypipes has quit IRC18:56
*** thinrichs has quit IRC18:56
*** cjellick has quit IRC18:56
*** garyduan has quit IRC18:56
*** davidlenwell has quit IRC18:56
*** glenc has quit IRC18:56
*** leifz has quit IRC18:56
SumitNaiksatami did not see any of the conversation until now18:57
*** s3wong_ is now known as s3wong18:57
s3wongyes, back to s3wong instead s3wong_ :-)18:57
*** shakamunyi has quit IRC18:57
Cathy_s3wong_: but based on existing traffic steeing API and the GBP API, they are two places to specify the classiffier which can cause inconsistency.18:57
*** cuddyt has quit IRC18:57
s3wongCathy_: so the classifier in GBP is used to apply policy18:57
Cathy_s3wong: yes, but the policy consists of the redirect and chain-ID18:58
*** shakamunyi has joined #openstack-meeting-318:58
Cathy_and classifier18:58
s3wongCathy_: the classifier in policy-rule does NOT need to be the same as TS'18:58
Cathy_and the chain-ID also carries over the classifier designed in the TS18:58
SumitNaiksatamCathy_: lets not confuse the classifier in the TS with GBP18:58
SumitNaiksatamCathy_: right now the thinking is very simple, the GBP has a redirect action18:59
SumitNaiksatamCathy_: that redirect action has a value field18:59
*** shakamunyi has quit IRC18:59
s3wongCathy_: in fact, the TS' classifier is way more specific18:59
SumitNaiksatamCathy_: that value field takes a UUID18:59
s3wongCathy_: it has a src-ip and dst-ip fields to them18:59
SumitNaiksatamCathy_: that UUID can either be a Neutron service (FWaaS, LBaaS, or VPNaaS)19:00
LouisFCathy_: the chaining BP https://review.openstack.org/#/c/93524 does not have as classifier19:00
SumitNaiksatamCathy_: or it can be a Service Chain UUID19:00
*** davidlenwell has joined #openstack-meeting-319:00
*** shakamunyi has joined #openstack-meeting-319:00
Cathy_s3wong: if the classifiers are not the same which one identifies the flow that will go through the service chain and what is the other classifier used for? Maybe I miss something here.19:00
s3wongCathy_: so what I can see possible, in the future - is that the mapping driver for 'redirect' COULD potentially use the TS python-clients to steer traffic to a service19:00
SumitNaiksatamCathy_: where service chain UUID is as per the spec #link https://review.openstack.org/#/c/9352419:00
banixCathy_: even if a GBP implementation uses TS then it will set the classifier appropriately19:00
Cathy_LouisF: we are talking about TS API, not service chaining API19:01
s3wongCathy_: in the case of GBP mapping driver using TS, the TS parameters will be set up by GBP mapping driver to redirect traffic to a service (as specified by the UUID)19:01
banixhave to run unfortunately… see you all later19:02
*** shakamunyi has quit IRC19:02
SumitNaiksatambanix: thanks for the reminder19:02
SumitNaiksatamwe are 2 mins over19:02
s3wongCathy_: IF the UUID specified happens to be a service chain - which also happens to use TS APIs (chains can use TS APIs too), then the chain's usage of the TS classifier is indpendent of how even the mapping driver is using the classifier19:02
s3wongbanix: have fun!19:03
Cathy_s3wong: I will talk  with you off line. thanks19:03
Cathy_SumitNaiksatam: thanks for discussing this.19:03
SumitNaiksatamCathy_: just pinged you on IM as well19:04
*** shakamunyi has joined #openstack-meeting-319:04
*** kenhui has joined #openstack-meeting-319:04
SumitNaiksatamCathy_: we can discuss this further offline19:04
Cathy_SumitNaiksatam: sure19:04
Cathy_SumitNaiksatam: how to reach you?19:04
SumitNaiksatamCathy_: check your IRC chat :-)19:04
SumitNaiksatamCathy_: i just pinged you19:05
*** lcheng has quit IRC19:05
SumitNaiksatamis songole still here?19:05
SumitNaiksatam#topic CLI and client19:05
*** openstack changes topic to "CLI and client (Meeting topic: networking_policy)"19:05
SumitNaiksatamwanted to get a quick update from songole since hemanthravi is away19:06
*** lcheng has joined #openstack-meeting-319:06
SumitNaiksatamtalked to songole and he will be updating the CLI/Client patch at the earliest19:06
SumitNaiksatamto sync with GP-API-119:06
*** seizadi has quit IRC19:06
SumitNaiksatam#topic open discussion19:07
*** openstack changes topic to "open discussion (Meeting topic: networking_policy)"19:07
SumitNaiksatamanytning else?19:07
SumitNaiksatamnot sure who else is still in the meeting19:07
SumitNaiksatamok lets wrap it up19:08
*** erecio has joined #openstack-meeting-319:08
SumitNaiksatam#endmeeting19:08
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:08
openstackMeeting ended Thu Jun 26 19:08:24 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:08
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-06-26-18.02.html19:08
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-06-26-18.02.txt19:08
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-06-26-18.02.log.html19:08
*** jaypipes has joined #openstack-meeting-319:08
*** Cathy_ has quit IRC19:09
*** kenhui has quit IRC19:11
*** yamamoto has joined #openstack-meeting-319:11
*** songole has quit IRC19:13
*** rkukura has left #openstack-meeting-319:14
*** yamamoto has quit IRC19:16
*** lenrow has joined #openstack-meeting-319:19
*** thinrichs has joined #openstack-meeting-319:19
*** cjellick has joined #openstack-meeting-319:19
*** garyduan has joined #openstack-meeting-319:19
*** glenc has joined #openstack-meeting-319:19
*** leifz has joined #openstack-meeting-319:19
*** dickson.freenode.net changes topic to "Services’ integration (Meeting topic: networking_policy)"19:19
*** pballand has joined #openstack-meeting-319:19
*** lcheng has quit IRC19:21
*** s3wong has left #openstack-meeting-319:22
*** lcheng has joined #openstack-meeting-319:22
*** jackib has quit IRC19:30
*** peristeri has quit IRC19:30
*** david-lyle has quit IRC19:38
*** kenhui has joined #openstack-meeting-319:39
*** erecio has quit IRC19:42
*** kenhui has quit IRC19:43
*** yamamoto has joined #openstack-meeting-319:44
*** david-lyle has joined #openstack-meeting-319:47
*** TravT has joined #openstack-meeting-319:47
*** kenhui has joined #openstack-meeting-319:49
*** shakamunyi has quit IRC19:52
*** jackib has joined #openstack-meeting-319:53
*** david-lyle has quit IRC19:54
*** eghobo has quit IRC19:57
*** david-lyle has joined #openstack-meeting-319:58
*** eghobo has joined #openstack-meeting-320:01
*** erecio has joined #openstack-meeting-320:03
*** kenhui has quit IRC20:04
*** zehicle_at_dell has quit IRC20:11
*** TravT has quit IRC20:12
*** TravT has joined #openstack-meeting-320:13
*** david-lyle has quit IRC20:20
*** david-lyle has joined #openstack-meeting-320:21
*** yamamoto_ has joined #openstack-meeting-320:24
*** david-lyle has quit IRC20:25
*** shakamunyi has joined #openstack-meeting-320:25
*** sarob has joined #openstack-meeting-320:27
*** erecio has quit IRC20:30
*** yamamoto_ has left #openstack-meeting-320:33
*** lenrow has quit IRC20:42
*** david-lyle has joined #openstack-meeting-320:44
*** sarob has quit IRC20:49
*** lenrow has joined #openstack-meeting-320:50
*** david-lyle has quit IRC20:57
*** david-lyle has joined #openstack-meeting-320:57
*** seizadi has joined #openstack-meeting-320:58
*** david-lyle has quit IRC20:58
*** david-lyle has joined #openstack-meeting-320:58
*** otherwiseguy has joined #openstack-meeting-321:02
*** yamamoto has quit IRC21:04
*** seizadi has quit IRC21:09
*** seizadi has joined #openstack-meeting-321:14
*** gduan has joined #openstack-meeting-321:15
*** garyduan has quit IRC21:16
*** shakamunyi has quit IRC21:17
*** shakamunyi has joined #openstack-meeting-321:18
*** otherwiseguy has quit IRC21:18
*** otherwiseguy has joined #openstack-meeting-321:19
*** jackib has quit IRC21:20
*** thomasem has quit IRC21:21
*** beyounn has quit IRC21:24
*** gduan has quit IRC21:24
*** david-lyle has quit IRC21:26
*** david-lyle has joined #openstack-meeting-321:27
*** lcheng has quit IRC21:27
*** david-lyle has quit IRC21:28
*** david-lyle has joined #openstack-meeting-321:28
*** armax has left #openstack-meeting-321:30
*** LouisF has quit IRC21:30
*** lcheng has joined #openstack-meeting-321:31
*** markmcclain has quit IRC21:35
*** ttrifonov is now known as ttrifonov_zZzz21:39
*** Sukhdev has joined #openstack-meeting-321:41
*** yamamoto has joined #openstack-meeting-321:41
*** armax has joined #openstack-meeting-321:44
*** kenhui has joined #openstack-meeting-321:45
*** yamamoto has quit IRC21:46
*** sarob has joined #openstack-meeting-321:58
*** armax has left #openstack-meeting-322:02
*** sarob has quit IRC22:04
*** Sukhdev has quit IRC22:06
*** Sukhdev_ has joined #openstack-meeting-322:06
*** iovadia has joined #openstack-meeting-322:12
*** kenhui has quit IRC22:20
*** carl_baldwin has quit IRC22:25
*** david-lyle has quit IRC22:27
*** david-lyle has joined #openstack-meeting-322:28
*** chuckC has quit IRC22:29
*** david-lyle has quit IRC22:32
*** terryw has joined #openstack-meeting-322:39
*** otherwiseguy has quit IRC22:39
*** terryw is now known as otherwiseguy22:39
*** yamamoto has joined #openstack-meeting-322:41
*** rhagarty has quit IRC22:41
*** rhagarty has joined #openstack-meeting-322:41
*** kenhui has joined #openstack-meeting-322:45
*** lcheng has quit IRC22:46
*** yamamoto has quit IRC22:46
*** kenhui has quit IRC22:46
*** kenhui has joined #openstack-meeting-322:47
*** kenhui has quit IRC22:49
*** markmcclain has joined #openstack-meeting-322:52
*** sarob has joined #openstack-meeting-322:53
*** markmcclain1 has joined #openstack-meeting-322:53
*** markmcclain has quit IRC22:56
*** sarob has quit IRC22:57
*** Sukhdev has joined #openstack-meeting-322:59
*** sarob has joined #openstack-meeting-322:59
*** otherwiseguy has quit IRC22:59
*** Sukhdev_ has quit IRC23:00
*** david-lyle has joined #openstack-meeting-323:02
*** chuckC has joined #openstack-meeting-323:03
*** sarob has quit IRC23:04
*** SumitNaiksatam has quit IRC23:04
*** shakamunyi has quit IRC23:04
*** armax has joined #openstack-meeting-323:11
*** david-lyle has quit IRC23:13
*** banix has quit IRC23:15
*** pballand has quit IRC23:18
*** pballand has joined #openstack-meeting-323:19
*** pballand has quit IRC23:20
*** yamamoto has joined #openstack-meeting-323:41
*** seizadi has quit IRC23:42
*** thinrichs has quit IRC23:45
*** yamamoto has quit IRC23:46
*** armax has quit IRC23:51
*** iovadia has quit IRC23:52
*** sarob has joined #openstack-meeting-323:53
*** sarob has quit IRC23:58
*** yamahata has joined #openstack-meeting-323:59
*** sarob has joined #openstack-meeting-323:59

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