Thursday, 2014-07-17

*** lcheng has quit IRC00:03
*** cjellick_ has quit IRC00:07
*** cjellick has joined #openstack-meeting-300:07
*** gduan has quit IRC00:10
*** garyduan has joined #openstack-meeting-300:10
*** cjellick has quit IRC00:11
*** tomoe_ has joined #openstack-meeting-300:15
*** Sukhdev has joined #openstack-meeting-300:21
*** seizadi has quit IRC00:22
*** seizadi has joined #openstack-meeting-300:22
*** rhagarty has quit IRC00:25
*** rhagarty has joined #openstack-meeting-300:25
*** banix has quit IRC00:32
*** pgpus has quit IRC00:34
*** pgpus has joined #openstack-meeting-300:41
*** yamamoto has joined #openstack-meeting-300:42
*** yamamoto has quit IRC00:47
*** gduan has joined #openstack-meeting-300:54
*** yamahata has joined #openstack-meeting-300:54
*** garyduan has quit IRC00:56
*** seizadi has quit IRC00:58
*** seizadi has joined #openstack-meeting-301:04
*** yzuo_ has quit IRC01:16
*** yamamoto_ has joined #openstack-meeting-301:18
*** yamamoto_ has quit IRC01:20
*** baohua has joined #openstack-meeting-301:41
*** gduan has quit IRC01:42
*** stanzgy has joined #openstack-meeting-301:45
*** yamamoto_ has joined #openstack-meeting-301:46
*** armax has quit IRC01:49
*** pgpus has quit IRC01:50
*** seizadi has quit IRC01:52
*** pgpus has joined #openstack-meeting-301:55
*** seizadi has joined #openstack-meeting-301:57
*** garyduan has joined #openstack-meeting-301:59
*** thomasem has joined #openstack-meeting-301:59
*** thomasem has quit IRC02:04
*** Sukhdev has quit IRC02:06
*** [1]m1dev is now known as m1dev02:23
*** hurgleburgler has quit IRC02:31
*** rfolco has quit IRC02:47
*** beyounn has quit IRC03:01
*** nelsnelson has quit IRC03:05
*** Longgeek has joined #openstack-meeting-303:10
*** dobson has joined #openstack-meeting-303:11
*** pgpus has quit IRC03:35
*** seizadi has quit IRC04:16
*** carl_baldwin has joined #openstack-meeting-304:18
*** nati_ueno has quit IRC04:26
*** carl_baldwin has quit IRC04:38
*** Sukhdev_ has joined #openstack-meeting-304:47
*** shwetaap has joined #openstack-meeting-304:55
*** shwetaap has quit IRC05:16
*** ivar-lazzaro has quit IRC05:23
*** nati_ueno has joined #openstack-meeting-305:34
*** seizadi has joined #openstack-meeting-305:38
*** chuckC has joined #openstack-meeting-305:43
*** seizadi1 has joined #openstack-meeting-305:45
*** seizadi has quit IRC05:45
*** jcoufal has joined #openstack-meeting-305:57
*** mrunge has joined #openstack-meeting-305:59
*** seizadi1 has quit IRC06:15
*** k4n0 has joined #openstack-meeting-306:22
*** Longgeek has quit IRC06:28
*** Sukhdev__ has joined #openstack-meeting-306:29
*** yisun_ has joined #openstack-meeting-306:31
*** dosaboy has joined #openstack-meeting-306:33
*** pleia2_ has joined #openstack-meeting-306:33
*** yisun has quit IRC06:33
*** yisun_ is now known as yisun06:34
*** SergeyLukjanov has quit IRC06:34
*** Sukhdev_ has quit IRC06:34
*** jtomasek has quit IRC06:34
*** d0ugal has quit IRC06:34
*** jrist has quit IRC06:34
*** dosaboy_ has quit IRC06:34
*** pleia2 has quit IRC06:34
*** k4n0 has quit IRC06:34
*** maurosr has quit IRC06:34
*** haleyb has quit IRC06:34
*** jtomasek has joined #openstack-meeting-306:34
*** SergeyLukjanov has joined #openstack-meeting-306:34
*** haleyb has joined #openstack-meeting-306:35
*** jrist has joined #openstack-meeting-306:35
*** d0ugal has joined #openstack-meeting-306:36
*** maurosr- has joined #openstack-meeting-306:36
*** maurosr- is now known as maurosr06:36
*** k4n0 has joined #openstack-meeting-306:36
*** Longgeek has joined #openstack-meeting-306:51
*** sankarshan_away is now known as sankarshan07:00
*** sankarshan is now known as sankarshan_away07:00
*** iovadia has joined #openstack-meeting-307:09
*** iovadia has quit IRC07:14
*** MaxV has joined #openstack-meeting-307:27
*** iovadia has joined #openstack-meeting-307:28
*** dansmith has quit IRC07:37
*** Sukhdev__ has quit IRC07:38
*** dansmith has joined #openstack-meeting-307:42
*** dansmith is now known as Guest5419907:43
*** nacim has joined #openstack-meeting-307:56
*** safchain has joined #openstack-meeting-308:00
*** pleia2_ is now known as pleia208:04
*** iovadia has left #openstack-meeting-308:06
*** zz_johnthetubagu is now known as johnthetubaguy08:37
*** tomoe__ has joined #openstack-meeting-308:48
*** tomoe_ has quit IRC08:48
*** yamahata has quit IRC09:25
*** alexpilotti has joined #openstack-meeting-309:26
*** yamamoto_ has quit IRC09:41
*** baohua has quit IRC09:45
*** tomoe__ has quit IRC09:47
*** stanzgy has quit IRC09:56
*** stanzgy has joined #openstack-meeting-309:58
*** stanzgy has quit IRC10:07
*** yamamoto has joined #openstack-meeting-310:18
*** MaxV has quit IRC11:07
*** MaxV has joined #openstack-meeting-311:08
*** MaxV has quit IRC11:12
*** julim has joined #openstack-meeting-311:15
*** jcoufal has quit IRC11:22
*** yamamoto has quit IRC11:26
*** lblanchard has joined #openstack-meeting-311:34
*** tomoe_ has joined #openstack-meeting-311:34
*** MaxV has joined #openstack-meeting-311:39
*** yamamoto has joined #openstack-meeting-311:57
*** yamamoto has quit IRC11:58
*** yamamoto has joined #openstack-meeting-311:58
*** yamamoto has quit IRC12:03
*** yamamoto has joined #openstack-meeting-312:07
*** mwagner_lap has quit IRC12:17
*** tomoe_ has quit IRC12:18
*** thomasem has joined #openstack-meeting-312:18
*** rfolco has joined #openstack-meeting-312:24
*** rfolco has quit IRC12:24
*** rfolco has joined #openstack-meeting-312:24
*** jcoufal has joined #openstack-meeting-312:44
*** tomoe_ has joined #openstack-meeting-312:47
*** thangp has joined #openstack-meeting-312:49
*** k4n0 has quit IRC13:01
*** thomasem has quit IRC13:20
*** thomasem has joined #openstack-meeting-313:21
*** yamamoto has quit IRC13:23
*** thomasem has quit IRC13:25
*** nacim has quit IRC13:26
*** peristeri has joined #openstack-meeting-313:29
*** peristeri has quit IRC13:35
*** peristeri has joined #openstack-meeting-313:35
*** shwetaap has joined #openstack-meeting-313:36
*** Guest54199 is now known as dansmith13:39
*** dansmith is now known as Guest891113:39
*** yamamoto has joined #openstack-meeting-313:40
*** lcheng has joined #openstack-meeting-313:41
*** kenhui has joined #openstack-meeting-313:42
*** Guest8911 has quit IRC13:43
*** dansmith_ has joined #openstack-meeting-313:44
*** otherwiseguy has joined #openstack-meeting-313:44
*** Youcef has joined #openstack-meeting-313:47
*** yamamoto has quit IRC13:47
*** thomasem has joined #openstack-meeting-313:48
*** tomoe_ has quit IRC13:53
*** mwagner_lap has joined #openstack-meeting-313:53
*** sankarshan_away is now known as sankarshan13:54
*** sankarshan is now known as sankarshan_away13:54
*** TravT has joined #openstack-meeting-313:55
*** johnthetubaguy is now known as zz_johnthetubagu13:57
*** zz_johnthetubagu is now known as johnthetubaguy14:06
*** nelsnelson has joined #openstack-meeting-314:11
*** yamamoto has joined #openstack-meeting-314:15
*** Youcef_ has joined #openstack-meeting-314:22
*** shwetaap1 has joined #openstack-meeting-314:22
*** xuhanp has joined #openstack-meeting-314:22
*** lcheng_ has joined #openstack-meeting-314:24
*** thomasem_ has joined #openstack-meeting-314:26
*** jgrimm has joined #openstack-meeting-314:27
*** thomasem has quit IRC14:31
*** Youcef has quit IRC14:31
*** lcheng has quit IRC14:31
*** shwetaap has quit IRC14:31
*** jcoufal has quit IRC14:32
*** nacim has joined #openstack-meeting-314:36
*** mrunge has quit IRC14:37
*** dansmith_ is now known as dansmith14:39
*** armax has joined #openstack-meeting-314:43
*** david-lyle has joined #openstack-meeting-314:46
*** carl_baldwin has joined #openstack-meeting-314:49
*** Youcef has joined #openstack-meeting-314:53
*** badveli has joined #openstack-meeting-314:54
*** alexpilotti has quit IRC14:54
*** armax_ has joined #openstack-meeting-314:54
*** armax_ has quit IRC14:54
*** terryw has joined #openstack-meeting-314:55
*** armax_ has joined #openstack-meeting-314:56
*** nelsnels_ has joined #openstack-meeting-314:58
*** SridarK has joined #openstack-meeting-314:59
carl_baldwinHi all14:59
yamamotohi14:59
SridarKHi15:00
badvelihello all15:00
*** pcm_ has joined #openstack-meeting-315:00
chuckChi15:00
pcm_hi15:00
carl_baldwinSwami: mrsmith: viveknarasimhan armax safchain seizadi jvoss pcm nextone92 devvesa ping15:00
armax_hi15:00
carl_baldwin#startmeeting neutron_l315:00
openstackMeeting started Thu Jul 17 15:00:57 2014 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"15: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-2 is in one week.15:01
*** dansmith_ has joined #openstack-meeting-315:01
*** viveknarasimhan has joined #openstack-meeting-315:01
carl_baldwinspec approval deadline (SAD) is in three days.15:01
carl_baldwinWhat an appropriate acronym.15:02
carl_baldwinThe mid-cycle sprint last week went well.  I enjoyed seeing some of you there.15:02
*** armax has quit IRC15:02
*** Youcef_ has quit IRC15:02
*** rfolco has quit IRC15:02
*** haleyb has quit IRC15:02
*** armax_ is now known as armax15:02
*** xuhanp has quit IRC15:02
*** nelsnelson has quit IRC15:02
*** otherwiseguy has quit IRC15:02
*** dansmith has quit IRC15:02
*** jtomasek has quit IRC15:02
*** dansmith_ is now known as dansmith15:02
pcm_+115:02
carl_baldwin#link https://etherpad.openstack.org/p/neutron-msp-sprint15:03
*** xuhanp has joined #openstack-meeting-315:03
carl_baldwinWe made good progress on DVR among other topics.15:03
carl_baldwinAny other announcements?15:04
carl_baldwin#topic neutron-ovs-dvr15:04
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:04
carl_baldwinOne patch merged yesterday.  I think we could be close on the L2 patch today.15:04
*** Swami has joined #openstack-meeting-315:05
carl_baldwinSwami: hi15:05
Swamihi carl15:05
carl_baldwinYour patch merged!15:05
SwamiGreat!, Thanks to Carl and Armando15:06
carl_baldwin#link https://wiki.openstack.org/wiki/Neutron/DVR/HowTo15:06
carl_baldwinWith the API patch in, we can work on getting the DB Models patch and the L3 Agent patch in.15:06
*** jtomasek has joined #openstack-meeting-315:07
*** haleyb has joined #openstack-meeting-315:07
SwamiIs sridharK here15:07
carl_baldwinI fell asleep before getting through the latest version of the DB patch but I plan to finish up my review this morning.15:07
*** haleyb_ has joined #openstack-meeting-315:07
viveknarasimhanthanks Carl for getting merged  the central patch for DVR merged15:07
SridarKSwami: yes15:07
carl_baldwinSwami: SridarK: you have the floor.15:08
armaxcarl_baldwin: I pushed another revision for the L2 models DB patch15:08
SridarKcarl_baldwin: thx15:08
*** rfolco has joined #openstack-meeting-315:08
armaxcarl_baldwin: I addressed Anna’s comments15:08
*** iovadia has joined #openstack-meeting-315:08
viveknarasimhani would like to mention something15:08
SridarKwe are working with the DVR team to address FWaaS - DVR integration issues15:08
SridarK#link https://review.openstack.org/#/c/106225/15:08
carl_baldwinarmax: I noticed it this morning.  Thanks.  We should be able to review that quickly.15:09
SridarKarmax: thanks for the review15:09
viveknarasimhanSince we merged Swami's patch which takes l3_dvr_db, we need upgrade the scheduler patch15:09
armaxcarl_baldwin: yeah…my bad I was careful in making sure to address the new needs of db migrations, but not so careful!15:09
viveknarasimhanto take the new mixin available there15:09
*** pcm_ has quit IRC15:09
viveknarasimhanwe found this out during our Unit Test upgrade for DVR scheduler15:09
armaxviveknarasimhan: can you be more detailed on the review itself?15:10
viveknarasimhanok, will add review lines there15:10
armaxviveknarasimhan: I am still waking up, so I am not sure I follow right now ;)15:10
viveknarasimhanfor dvr scheduler patch15:10
*** mrsmith has joined #openstack-meeting-315:10
*** haleyb_ has quit IRC15:10
armaxviveknarasimhan: please put a comment, a -1 if you need to and we’ll look into that15:10
viveknarasimhanok15:11
carl_baldwinviveknarasimhan: We’ve got a couple days before Murali’s patch his the top of the review-for-merge list.  But, the sooner the feedback gets in the better.15:11
viveknarasimhandoing so now15:11
Swamivivek: Are you saying that since we already merged the L3 extension patch , the scheduler patch should no longer have any dependency15:11
*** shwetaap1 has quit IRC15:11
viveknarasimhanno, am saying15:12
*** pcm_ has joined #openstack-meeting-315:12
viveknarasimhanscheduler should start using the new mixin in l3_dvr_db15:12
viveknarasimhanit is using the old NAT mixin15:12
viveknarasimhanfrom l3_db15:12
carl_baldwinSridarK: I have your spec at the top of my review list for today.15:12
Swamivivek: got it15:12
SridarKcarl_baldwin: thx15:12
Swamicarl_baldwin: Just give you heads up on the FWaaS15:13
SwamiAs per our discussion the current blue print will target the North South and not the East-West.15:13
carl_baldwinSwami: understood, thanks.15:13
*** pcm_ has quit IRC15:13
SwamiTo be backward compatible, the FWaaS will only apply the FWaaS rules to the non-distributed routers.15:14
SridarKcarl_baldwin: Swami have called that out this is targeting N - S in the spec15:14
*** Rajeev_ has joined #openstack-meeting-315:14
carl_baldwinSwami: So, no FWaaS for distributed routers at all?15:14
armaxSridarK: I believe it would be useful to really make it clear in the spec title or commit message15:14
SridarKarmax: i have addressed ur comments on that in the spec also15:15
viveknarasimhanFwaaS for distributed routers but only for15:15
viveknarasimhanN-S traffic15:15
SridarKviveknarasimhan: +115:15
viveknarasimhanfor the first phase carl15:15
armaxSridarK: thanks for that, but the commit or spec title is unchanged15:15
Swamicarl_baldwin: sorry if I have conveyed the message properly, FWaaS will be there for distributed routers, but only for the north-south traffic.15:15
SridarKarmax: ok will change that15:15
armaxlater on we’re gonna file other blueprints to address the other parts15:15
SridarKarmax: +115:16
carl_baldwinI’m a bit confused now by “FWaaS will only apply the FWaaS rules to the non-distributed routers” but I’ll read the blueprint and take the discussion there.15:16
*** mestery has quit IRC15:16
carl_baldwinSwami: I think I understand.15:16
SridarKcarl_baldwin: we only want to address the N - S cases and make sure we don't break E - W normal forwarding15:16
armaxSridarK: thanks, it’s only a suggestion but I think it’ll make the scope of the bp a lot more clear15:17
SridarK*address N - S FWaaS; no E - W FWaaS15:17
carl_baldwinSridarK: That sounds like what I’m thinking now.  So, I think I understand.15:17
carl_baldwinarmax: Good suggestion.  Making the scope of a bp clear is often the most important part.15:17
SridarKarmax: i agree too so there is no confusion on what is being addressed15:17
SridarKarmax: removed the Phase 2 part from the BP based on ur comments15:18
armaxSridarK: you may want to keep the same topic for all the fw/dvr bp's15:18
carl_baldwinSo, we’re good to go on this bp?  We will work hard to get this reviewed by the 20th.15:18
armaxSridarK: but I’d be definitely more descriptive in the commit messafge15:18
SridarKarmax: will change that15:18
armaxSridarK: so that’s easy to group them together and see what the overall effort is15:19
carl_baldwinI think we should spend a few minutes discussing DVR testing.15:19
SridarKcarl_baldwin: we have discussed with the DVR team and are on the same page with them on what needs to be done15:19
SridarKarmax: yes definitely agree15:19
carl_baldwinSridarK: great.15:19
SridarKcarl_baldwin: thanks for some "airtime" here15:20
SridarKcarl_baldwin: badveli will also be working on this15:20
carl_baldwinSridarK: yw, thanks for your work.15:20
Rajeev_SridarK: we like how you are approaching the design for DVR15:20
SridarKfrom the FWaaS sub team15:20
badveliyes on the implementation15:20
*** pcm_ has joined #openstack-meeting-315:21
carl_baldwinOn the testing front.  We’ve got a few things going on, I think.15:21
SridarKcarl_baldwin: Rajeev_ thx for to the DVR sub team and FWaaS subteam15:21
viveknarasimhancarl i am working on enhancing the Unit tests for scheduler15:21
viveknarasimhanand ml2 pluin (l2-pop side)15:21
armaxcarl_baldwin: I revised the tempest API tests15:22
carl_baldwinFirst, UT coverage has been called out in a few of the patches.  I spoke with all of the cores and Kyle at the sprint.  We’re okay merging the patches with the current coverage but we’ll need to follow up.15:22
viveknarasimhangreat... thanks Carl15:22
viveknarasimhanbut we will be shipping UT stuff as we improve coverge for review to you and armax15:22
armaxviveknarasimhan: great, sooner the better15:23
carl_baldwinWe’ll need the new coverage in order to finally say that DVR has been fully implemented.  Yes, the sooner the better.15:24
*** pballand has joined #openstack-meeting-315:25
carl_baldwin2) Tempest.  armax:  it sounds like you’ve got this covered?15:25
Swamicarl_baldwin: on the testing front, is there any option of introducing the multinode setup in the upstream or are we still targeting a single node.15:25
armaxcarl_baldwin: the Tempest API tests are now better designed and the review passed the existing test suite (w/o dvr)15:25
carl_baldwinarmax: Great.15:25
armaxcarl_baldwin: checking if they pass now with DVR now that swami’s patch merged15:26
carl_baldwinSwami: There is an infra bp to add multi-node testing.  It will take a little time so, for now, a single node is all we have.15:26
armaxcarl_baldwin: we also have a number of patches to add the CI jenkins job to address the single node tests15:26
armaxbut no love from the infra team yet15:26
carl_baldwin#link https://review.openstack.org/#/c/106495/15:27
carl_baldwin^ The infra spec for multi-node.15:27
armax#link https://review.openstack.org/#/c/106902/15:27
armax#link https://review.openstack.org/#/c/106901/15:28
armax#link https://review.openstack.org/#/c/103180/15:28
armaxthe last tree links should give us the ability to run an experimental job at will that has DVR enabled15:28
armaxbefore we can really do that though we’d need the entire dvr feature in the tree15:29
carl_baldwinarmax: Thanks for the links.  Right, we need at least the basic set of 7 patches merged, right?  1 down 6 to go.15:30
armaxcarl_baldwin: yes15:30
*** hurgleburgler has joined #openstack-meeting-315:31
carl_baldwinHopefully we can get the infra team’s attention before then.  I think they might be meeting in Germany this week.  They may be heads down.15:31
armaxok15:32
Swamigood to know.15:32
*** thangp has quit IRC15:32
carl_baldwinI have one more thing for DVR.  Is there a plan to enable GRE tunneling?  I’m told that would be easy.  What about VLAN?15:33
viveknarasimhanGRE tunneling can be enabled15:33
viveknarasimhandid a basic investigation and it needs change on the L2 OVS agent for most part15:33
carl_baldwinviveknarasimhan: Can you start a placeholder patch for that?15:34
viveknarasimhanyes, will do carl15:34
Swamicarl: we have a couple of items in the backlog and we need to prioritize15:34
*** shwetaap has joined #openstack-meeting-315:34
SwamiMigration, Services support, support VLAN, GRE tunnelling etc.,15:35
*** xuhanp has quit IRC15:35
SwamiI have a list I can pass it on to you offline.15:35
carl_baldwinSwami: great.  Let me know how that backlog gets prioritized.15:35
carl_baldwinSwami: It will be great to have that list.15:36
Swamicarl_baldwin: sure15:36
carl_baldwinAnything else for DVR?15:36
SwamiDo you want it right now.15:36
carl_baldwinSwami: If you have it, yes.15:36
Swamihold on a minute.15:36
carl_baldwinSwami: sure just email it.15:36
carl_baldwin#topic l3-high-availability15:37
*** openstack changes topic to "l3-high-availability (Meeting topic: neutron_l3)"15:37
Swami 1.Migration  a.Legacy to Distributed Router Migration i.With no Gateway and FloatingIP ii.With Gateway only iii.With no FloatingIP and  iv.With FloatingIP v.With FloatingIP and Gateway vi.Allow removing a distributed router from an agent binding even if it has FloatingIP.  b.Migration CLI Commands  i.Use existing CLI commands ii.Or Create new CLI commands to address the SNAT migration  2.Services a.LBaaS Sup15:37
armaxsafchain:  udere?15:37
carl_baldwinsafchain: armax: How are we doing here?  I saw that the bp merged.15:37
carl_baldwinSwami: thanks.15:37
armaxwe’re at risk here15:37
SwamiSorry it is not well formated.15:37
SwamiI will add one by one15:37
carl_baldwinSwami: no worries.15:38
armaxI don’t see Assaf15:38
armaxcarl_baldwin: safchain said he didn’t have cycles to work on it then he came back work on it a little and  then disappeared again15:38
*** jcoufal has joined #openstack-meeting-315:38
safchainarmax, carl, hi sorry to be late15:38
*** iovadia has quit IRC15:39
carl_baldwinsafchain: hi15:39
armaxcarl_baldwin: to make sure we make consistent progress here we’d need someone who steadily work on this feature15:39
carl_baldwinI was thinking about HA + DVR the other day.  The thing that came to my mind was that HA would need to be aware of the SNAT port that DVR allocates.15:39
safchainarmax, we are working on it with assaf15:40
Swamicarl_baldwin: I will send an email with the complete list.15:40
carl_baldwinsafchain: How do you feel about hitting juno-3?15:41
armaxsafchain: no much progress the last couple of days, is there anything we can do?15:41
armaxto help?15:41
safchaincarl_baldwin, armax Assaf reviewed all the patches, and we split the tasks in two part, API/scheduler - agent15:42
safchainarmax, yes any help is welcome15:42
*** shwetaap has quit IRC15:42
safchainarmax, please tell me if you want to work on a specific part, patch15:43
armaxsafchain: well we don’t want to step on each other toes15:43
armaxsafchain: we cannot work on the same patches at the same time15:43
safchainarmax, sure15:43
*** banix_ has joined #openstack-meeting-315:43
armaxsafchain: where do you feel you need help?15:44
safchainarmax, I think the current task split with assaf is ok, and I wil submit a new patch-set for API tomorrow15:44
armaxok15:45
*** rhagarty has quit IRC15:45
carl_baldwinWe’re short on time.  Anything else for HA?15:46
safchainarmax, If you have any time to work on the scheduler15:46
safchaincarl_baldwin, ok for me15:46
armaxsafchain: I can have a look15:46
carl_baldwinsafchain: armax: I’ll let you coordinate offline.15:46
carl_baldwin#topic l3-svcs-vendor-*15:46
*** openstack changes topic to "l3-svcs-vendor-* (Meeting topic: neutron_l3)"15:46
carl_baldwinpcm_: Some progress this week.  Anything to discuss?15:47
pcm_Sure :)15:47
pcm_Reference implementation is in.15:47
pcm_Could use review of Cisco implementation (https://review.openstack.org/#/c/107473/1)15:47
pcm_Since the Cisco one was dependent on the reference one, do I need to rebase the commit to master now>15:48
pcm_?15:48
carl_baldwinpcm_: My view of rebasing is that it should be done whenever Jenkins fails to merge it.15:48
carl_baldwinOthers may not share that view (yet).15:48
carl_baldwin;)15:48
carl_baldwinpcm_: Anything else?15:48
*** rhagarty has joined #openstack-meeting-315:49
pcm_No. Later (next week), I'll probably want to see if there are other services that need this validation too15:49
carl_baldwinpcm_: Thanks.15:50
pcm_Can work with vendors on applying this method to their service.15:50
carl_baldwin#topic bgp-dynamic-routing15:50
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:50
pcm_thanks for the reviews!15:50
carl_baldwinI don’t see devvesa or nextone92 on.15:50
carl_baldwinI do know that there has been some progress on this topic.15:50
carl_baldwinThe bp merged.15:50
yamamotoi have a short update on ryu bgp15:51
yamamotooutfilter patch has been merged to ryu master15:51
carl_baldwinyamahata__: Great.  You have the floor.15:51
carl_baldwingood to know.  Do you know if devvesa has been working with your code yet?15:52
yamamotoi think we completed features requested by devvesa15:52
yamamotomore requests and questions are welcome15:52
carl_baldwinI know that he has been working on implementation.  We discussed some model simplifications yesterday.  I’m not sure how much he has worked with Ryu code yet.15:52
yamamotoi don't know about devvesa's progress15:53
carl_baldwinI’ll ping him later today for progress.15:53
carl_baldwinAnything more to add?15:53
yamamotonothing from me15:53
carl_baldwin#topic neutron-ipam15:54
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:54
carl_baldwinSAD to say that IPAM won’t make the cut for Juno.15:55
carl_baldwinThis doesn’t mean that work has to stop by those who are interested.  I’d like to get an early start on this for K15:56
carl_baldwinJust means that review time will be diverted to other things.15:56
carl_baldwinI don’t see any of the ipam guys around.  So, that is all for now.15:57
carl_baldwin#topic Open Discussion15:57
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:57
carl_baldwinThanks everyone for the hard work that has been done.  I’ve seen good progress being made.15:59
*** jcoufal has quit IRC15:59
pcm_bye15:59
yamamotothank you15:59
*** pcm_ has left #openstack-meeting-315:59
SridarKThanks DVR folks for all the help on the FWaaS - DVR issues and special thanks to Swami for helping us understand DVR and for those fantastic pictures (although i can't convince him to do it in ASCII)15:59
carl_baldwinThat’s all I have.  Bye.15:59
*** jpomero has joined #openstack-meeting-315:59
SridarKbye15:59
carl_baldwin#endmeeting15:59
*** viveknarasimhan has left #openstack-meeting-315:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
armaxbte15:59
openstackMeeting ended Thu Jul 17 15:59:51 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-07-17-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-07-17-15.00.txt15:59
armaxbye15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-07-17-15.00.log.html15:59
Swamibye15:59
*** Swami has quit IRC16:00
*** mrsmith has quit IRC16:00
*** SridarK has quit IRC16:01
*** shwetaap has joined #openstack-meeting-316:04
*** Longgeek has quit IRC16:05
*** jcoufal has joined #openstack-meeting-316:08
*** badveli has quit IRC16:09
*** banix_ has quit IRC16:13
*** MaxV has quit IRC16:14
*** Rajeev_ has quit IRC16:23
*** TravT has quit IRC16:27
*** cjellick has joined #openstack-meeting-316:37
*** cjellick has quit IRC16:37
*** shwetaap has quit IRC16:37
*** cjellick has joined #openstack-meeting-316:38
*** seizadi has joined #openstack-meeting-316:42
*** pgpus has joined #openstack-meeting-316:46
*** MaxV has joined #openstack-meeting-316:52
*** banix has joined #openstack-meeting-316:56
*** shwetaap has joined #openstack-meeting-317:04
*** kenhui has left #openstack-meeting-317:08
*** banix has quit IRC17:12
*** thomasem has joined #openstack-meeting-317:13
*** thomasem_ has quit IRC17:15
*** yamamoto has quit IRC17:21
*** ivar-lazzaro has joined #openstack-meeting-317:28
*** chuckC has quit IRC17:30
*** lcheng_ has quit IRC17:31
*** banix has joined #openstack-meeting-317:36
*** m1dev has quit IRC17:38
*** m1dev has joined #openstack-meeting-317:39
*** beyounn has joined #openstack-meeting-317:39
*** shwetaap has quit IRC17:42
*** SumitNaiksatam has quit IRC17:43
*** shwetaap has joined #openstack-meeting-317:45
*** banix has quit IRC17:47
*** marun has joined #openstack-meeting-317:47
*** yamamoto has joined #openstack-meeting-317:52
*** banix has joined #openstack-meeting-317:52
*** LouisF has joined #openstack-meeting-317:53
*** johnthetubaguy is now known as zz_johnthetubagu17:56
*** rkukura has joined #openstack-meeting-317:56
*** yamamoto has quit IRC17:57
*** hemanthravi has joined #openstack-meeting-317:57
*** yamamoto_ has joined #openstack-meeting-317:57
*** SumitNaiksatam has joined #openstack-meeting-317:58
*** jcoufal has quit IRC17:58
*** terryw has quit IRC17:59
SumitNaiksatamhi neutron group policy team!17:59
kevinbentono/17:59
banixhallloooo17:59
hemanthravihi18:00
*** MaxV has quit IRC18:00
SumitNaiksatamok lets get started18:00
*** otherwiseguy has joined #openstack-meeting-318:00
LouisFhi18:00
SumitNaiksatam#startmeeting networking_policy18:00
openstackMeeting started Thu Jul 17 18:00:39 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
rkukurahi18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** s3wong has joined #openstack-meeting-318:00
*** openstack changes topic to " (Meeting topic: networking_policy)"18:00
openstackThe meeting name has been set to 'networking_policy'18:00
SumitNaiksatam#info agenda: https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy18:00
SumitNaiksatam#announcements Juno specification submission deadline: July 10th, specification approval deadline: july 20th18:01
SumitNaiksatamso the SAD is 20th and not 17th as i previously noted18:01
*** pgpus has quit IRC18:01
SumitNaiksatami erred to the conservative side, so it gives us a couple of more days18:01
*** yamamoto_ has quit IRC18:01
SumitNaiksatami know we have the vendor driver blueprints, and kevinbenton’s API intercept spec18:02
SumitNaiksatamanything other spec that is pending review?18:02
SumitNaiksatamwe will get to the vendor drivers later in the agenda (if we have time)18:02
*** shwetaap has quit IRC18:02
SumitNaiksatamokay18:02
banixdoes it look like ant of the vendor bps will get reviewed/approved?18:02
*** seizadi has quit IRC18:03
rkukuraI plan to spend much of the next few days reviewing specs, including these18:03
banixany18:03
SumitNaiksatamrkukura: thanks18:03
SumitNaiksatambanix: i plan to review as well18:03
SumitNaiksatambanix: at my end i will be able to review before SAD18:03
*** yyywu has joined #openstack-meeting-318:03
SumitNaiksatamrkukura: you feel comfortable about that as well?18:03
banixgreat. i have a question regarding our bp but will wait for tits time slot18:04
rkukurano, but I’ll review as much as I can as soon as I can18:04
SumitNaiksatamrkukura: okay18:04
SumitNaiksatambanix: thanks18:04
rkukuramy goal is to make a pass thru everything important on GP and ML2 by mid-day tomorrow18:05
SumitNaiksatami think the vendor driver specs are all pretty similar in that they proxy the group policy calls over to their respective backends18:05
SumitNaiksatamso i guess its pretty much like you review one, and the rest are all along similar lines18:05
SumitNaiksatamfolks correct me if i am wrong, or if any of the vendors are planning to do something different18:06
banixnow that you ask :)18:06
SumitNaiksatamif its a longer discussion we can take it up in the relevant part of the agenda18:06
banixwe wwant to have a new attribute for claasifiers and are not sure if that would the approval complicated or not18:06
banixi can wait; your call SumitNaiksatam18:07
SumitNaiksatambanix: thanks18:07
hemanthraviSumitNaiksatam: no, it's as you described for One Convergence GBP driver18:07
SumitNaiksatamhemanthravi: ok good18:07
SumitNaiksatam#topic Gerrit Reviews18:08
*** openstack changes topic to "Gerrit Reviews (Meeting topic: networking_policy)"18:08
*** sadasu_ has joined #openstack-meeting-318:08
SumitNaiksatam#link https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy/Patches18:08
*** seizadi has joined #openstack-meeting-318:09
kevinbentonSumitNaiksatam: can you comment in response to Eugene’s question on the intercept patch about why inter-plugin calls need to be intercepted?18:09
SumitNaiksatamkevinbenton: yes i will18:09
*** hurgleburgler1 has joined #openstack-meeting-318:09
SumitNaiksatamkevinbenton: sorry about the delay18:09
SumitNaiksatamjust posting the above link for the benefit of anyone who is not familiar with the series and the stacking18:10
*** chuckC has joined #openstack-meeting-318:10
*** MaxV has joined #openstack-meeting-318:10
*** hurgleburgler has quit IRC18:10
kevinbentonSumitNaiksatam: no problem. If anyone else is interested in the discussion around the intercept, the patch is here. #link https://review.openstack.org/#/c/105695/18:10
SumitNaiksatamkevinbenton: thanks18:10
SumitNaiksatamkevinbenton: i do have that as a separate agenda item18:11
SumitNaiksatamkevinbenton: your spec that is18:11
*** lcheng has joined #openstack-meeting-318:11
kevinbentonSumitNaiksatam: whoops :-)18:11
SumitNaiksatamany questions/comments on the series/stacking?18:11
SumitNaiksatamkevinbenton: np18:11
SumitNaiksatamkevinbenton: thanks for putting it out there, if we run out of time, we know what to skip :-)18:11
SumitNaiksatamok moving on18:11
SumitNaiksatam#topic Resource Model/API/DB/Plugin Update18:12
*** openstack changes topic to "Resource Model/API/DB/Plugin Update (Meeting topic: networking_policy)"18:12
SumitNaiksatamno major update here18:12
SumitNaiksatamrkukura pointed out today morning that gp-db-1 and gp-plg-1 were out of sync with the master and needed rebase18:12
SumitNaiksatamso those have been rebased18:12
rkukura+118:12
SumitNaiksatami have not added the db migration script yet since i did not want to introduces churn while rkukura was working on it18:13
SumitNaiksatambut i had to rebase anyway today18:13
SumitNaiksatamany questions on gp-api/db/plg/-1/2/3?18:13
rkukurahopefully next update after this to the gp-*-1 and gpm-*-1 series will have the DB migrations and be ready to merge18:14
SumitNaiksatamfor the naming conventions on the patches please refer to: #link https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy/Patches18:14
SumitNaiksatamrkukura: yes, db migration should be straightforward18:14
SumitNaiksatamalso banix is working on some of the advanced UTs for the drivers18:15
SumitNaiksatambanix: thanks for the update yesterday18:15
banixyes when appropriate i like to ask a couple of questions wrt UTs18:15
SumitNaiksatambanix: go ahead18:15
banixlooking at the comment rkukura left here: #link https://review.openstack.org/#/c/96393/9/neutron/tests/unit/services/grouppolicy/test_grouppolicy_plugin.py18:16
banixIn the tests I have added I use the dummy driver and patch it for each test accordingly18:16
banixDoes that make sense or I am missing something here?18:17
*** jackib has joined #openstack-meeting-318:17
SumitNaiksatamrkukura: ^^^18:17
rkukurabanix: makes sense to me18:17
banixok thanks; will share the code soon18:18
rkukurabanix: The ml2 tests probably could do something like that, but there is also some logic in the driver for the tests I think. Its been a while since I looked18:18
*** krotscheck has quit IRC18:18
SumitNaiksatambanix: thanks!18:18
SumitNaiksatamok moving on18:19
SumitNaiksatam#topic Mapping Model/Driver Update18:19
*** openstack changes topic to "Mapping Model/Driver Update (Meeting topic: networking_policy)"18:19
SumitNaiksatamrkukura: over to you18:19
rkukuraOK, I’ve been working to make the resource_mapping driver production-ready (relatively) so we can remove the WIP from gpm-rmd-1.18:19
SumitNaiksatamrkukura: whats the ETA on that?18:20
rkukuraIt now handles all the cleanup for implicitly created resources, and does not cleanup explicitly created resources18:20
SumitNaiksatamrkukura: nice18:20
SumitNaiksatamrkukura: thats using a db table?18:20
rkukuraI have a bit more work to do on this to handle updates (rejecting things that don’t make sense for this driver), and validating a few things for explicitly-created resources.18:21
rkukuraI hope to push the non-WIP update later today.18:21
SumitNaiksatamrkukura: sweet18:21
rkukuraI’ve already pushed updates to gpm-api-1, gpm-db-1, and gpm-plugin-1 rebasing on Sumit’s latest updates.18:21
*** jcoufal has joined #openstack-meeting-318:22
rkukuraI’ve got a couple minor review comments to address in gpm-ipd-1 and will push that update shortly.18:22
rkukurathen get back to finishing gpm-rmd-118:22
rkukuraAfter that, I’ll shift my focus to spec reviews until Sunday18:23
rkukuraThat’s it for me18:23
*** rms_13 has joined #openstack-meeting-318:23
SumitNaiksatamrkukura: thanks for the update18:23
SumitNaiksatamany questions for rkukura?18:23
LouisFSumitNaiksatam: i have question on EPG provided/consumed contract lists18:24
SumitNaiksatamrkukura: so the implicitly created resources are recorded in the db?18:24
rkukuraSumitNaiksatam: The resource_mapping driver uses DB tables to keep track of owned resources, just like the implicit_policy driver does.18:24
SumitNaiksatamrkukura: ok18:24
SumitNaiksatamLouisF: please go ahead18:24
LouisFin the scenario where a EPG has provided contracts 1-10 and the client now wants to send an update to remove contracts 9, 10 and add 11 and 12, should the client send an update that includes contracts 1-8, 11, 12?18:24
rkukuraLouisF: I think we need to define add_contract and remove_contract operations for this, similate to the router’s add_interface and remove_interface operations.18:25
LouisFin orher words an update must always include the itended list of contracts18:25
LouisFintended18:25
SumitNaiksatamLouisF rkukura: yes thats the plan18:25
rkukuraUpdating the entire list will work, but has race conditions of multiple clients try to update the same thing at the same time.18:26
SumitNaiksatamLouisF: i believe the way its currently structured you ahve to send the entire list18:26
SumitNaiksatamrkukura: yes agreed18:26
SumitNaiksatamLouisF: so we will add those extra API operations18:26
*** shwetaap has joined #openstack-meeting-318:26
SumitNaiksatamLouisF: add/remove, we do something similar for the router interfaces and firewall rules18:26
rkukuraSpeaking of these add/remove opetations, if anyone knows how to list all the interfaces of a router via the client API, please let me know.18:26
SumitNaiksatamLouisF: its not in the patch right now though18:26
SumitNaiksatamLouisF: does that answer your question?18:27
*** mlavalle has joined #openstack-meeting-318:27
mlavallehi18:27
LouisFwhat if an EPG potentially have 100s of contracts?18:27
SumitNaiksatammlavalle: thanks for joining18:28
mlavallenice to be here18:28
SumitNaiksatamLouisF: you will have both options18:28
SumitNaiksatamLouisF: of bulk update and well as single updates18:28
kevinbentonrkukura: query ports based on device_id = router_id18:28
SumitNaiksatamLouisF: however its questionable whether EPGs will have 100s of contracts18:28
LouisFok when will add/remove contract be added?18:29
rkukurakevinbenton: I was hoping not to have to resort to that, but didn’t see a better way18:29
*** Sukhdev has joined #openstack-meeting-318:29
SumitNaiksatamLouisF: i was planning to add that as a separate follow up patch18:29
rkukuramay need to do this in the UTs to verify subnets get added to routers18:29
SumitNaiksatamLouisF: i prefer to keep this patch series with the basic CRUD operations to faciliatate reviews18:30
kevinbentonrkukura: yes, i remember coming across in the code that unfortunately the only associate between ports and routers is held in that device_id field of the port18:30
LouisFSumitNaiksatam: ok18:30
SumitNaiksatamok moving on (since mlavalle is here)18:31
SumitNaiksatam#topic Functional/System testing18:31
*** openstack changes topic to "Functional/System testing (Meeting topic: networking_policy)"18:31
SumitNaiksatammlavalle: thanks again for joining at a short notice18:31
mlavalle:-)18:31
SumitNaiksatammlavalle: so the team here wants to be able to introduce some functional/system tests to be able to test the group policy API and workflow18:32
SumitNaiksatammlavalle: what do you recommend is the best path forward?18:32
*** pballand has quit IRC18:32
SumitNaiksatami was informed that the LBaaS folks have a patch for the new API?18:32
mlavalleyeah I developed that for them18:32
SumitNaiksatammlavalle: oh great, so we are approaching the right person!18:33
mlavalleif I understand coirrectly, we have a rest api here, correct?18:33
SumitNaiksatammlavalle: yes18:33
SumitNaiksatammlavalle: it starts with this patch #link https://review.openstack.org/#/c/9590018:33
mlavalleso we can definitely go ahead and develop a set of tempest tests, both at the api l;evel and at the scenario level18:33
SumitNaiksatammlavalle: ok good18:33
*** jackib has quit IRC18:34
SumitNaiksatammlavalle: i will jump on this right away, any pointers?18:34
SumitNaiksatammlavalle: we can take it offline if this is a longer discussion18:34
mlavallemoving ahead, we can folow the following approaches18:34
mlavalle1) I csn develop the tests for you18:34
SumitNaiksatammlavalle: sure18:34
mlavalle2) I can train someone in your team to develop the tests18:35
mlavalleor a combination of both18:35
mlavallewhicever you fill more comfortable18:35
rkukuramlavalle: One concern is that the juno version of GPM is likely to be considered “beta” without guaranteeing backward API compatability with the K release, but that tempest isn’t branced. Is this an issue?18:35
SumitNaiksatammlavalle: in the short term we will have to use (2)18:35
mlavallein any case, I will provide support18:35
SumitNaiksatammlavalle: thanks! lets first address rkukura’s question and then we can work out logistics18:36
mlavallerkukura: that's not a problem, we can evolve the tests as the api evolve18:36
rkukuramlavalle: I recall marun proposing developing tempest-like tests in the neutron or some other repo to deal with this.18:36
mlavallerkukura: yes, that's also a valid approach. however, since we will have a rest api, at some point in tume we will need tempest tests18:37
rkukuramlavalle: So if these tests get merged to tempest during juno and then the API changes in K, how do we deal with it?18:37
rkukuraWe don’t want to break running tempest against juno.18:38
SumitNaiksatammlavalle: rkukura’s question ^^^?18:39
mlavallerkukura: yeah….. I see your point…. maybe we should hold off developing the tests in tempest for the time being18:40
mlavallelet me bring this up with the tempest team and i'll get back to you next week18:40
mlavallehow's that?18:40
rkukuraI’m not arguing against putting our tests in tempest from the start, as long as that isn’t preventing us from making API changes that aren’t backwards compatible during K18:40
SumitNaiksatammlavalle: so how is this being addressed for the new lbaas api/resources?18:41
rkukuraShould we start with a WIP patch for tempest tests in the mean time?18:41
SumitNaiksatammlavalle: i am guessing the new api is beta over there are well?18:41
SumitNaiksatamrkukura: exactly18:41
mlavallerkukura: yeah, I understand…. in the case of LBaaS we are working with WIP patches18:41
SumitNaiksatamrkukura: i was thinking the same, at least the WIP will allow people to test18:41
mlavallewe can do the same here18:41
SumitNaiksatamrkukura: doesnt have to be merged18:41
SumitNaiksatammlavalle rkukura: ok great, lets have the WIP patch18:42
SumitNaiksatameveryone agree?18:42
rkukura+118:42
mlavalle+118:42
banix+118:42
SumitNaiksatamok great, so mlavalle i will sync with you, so that we have something at the earliest18:42
SumitNaiksatamour requirement is that something be ready by next week so that people can test it right away18:43
mlavallemoving forward with the tests, I think I can help extending the tempest rest clients and then have someone in your team develop the tests themselves18:43
SumitNaiksatamwe have a pending -2 and part of it is ostensibly for this18:43
SumitNaiksatammlavalle: nice18:43
SumitNaiksatammlavalle: since we are running short on time here, i will sync with you and we can report progress in the meeting next week?18:43
mlavallecool. I'll wait for your ping18:44
*** pballand has joined #openstack-meeting-318:44
mlavalle:-)18:44
rkukuraSumitNaiksatam: Can we target the tempest REST client at just the initial 4 resources in gp-*-1 to get this going quickly?18:44
SumitNaiksatammlavalle: thanks much!18:44
banixthanks mlavalle18:44
SumitNaiksatamrkukura: precisely, just those first four18:44
*** mandeep has joined #openstack-meeting-318:45
SumitNaiksatamrkukura: i was thinking for now we will do only what we need to for the first series18:45
rkukura+118:45
mandeep+118:45
SumitNaiksatamok moving on18:45
SumitNaiksatam#topic Security Groups mapping update18:46
*** openstack changes topic to "Security Groups mapping update (Meeting topic: networking_policy)"18:46
SumitNaiksatamwe needed more time for this18:46
SumitNaiksatams3wong: sorry about that!18:46
SumitNaiksatams3wong: but please go ahead18:46
s3wongin the interest of time, I will only give a four lines update:18:46
SumitNaiksatami know regxboi had commented18:46
SumitNaiksatams3wong: please18:46
s3wongthanks for LouisF and regXboi for their comments on doc, I responded to them and will update doc accordingly18:46
*** krotscheck has joined #openstack-meeting-318:47
s3wongI have an action item on checking multiple SG per port: turns out it is one of the basic operations according to OpenStack doc:18:47
LouisFs3wong: can you clarify what you mean about the FW?18:48
s3wonghttp://docs.openstack.org/admin-guide-cloud/content/securitygroup_workflow.html18:48
s3wongLouisF: Firewall as in FWaaS instance18:48
LouisFyes18:48
s3wongand the last line of update: I pulled a branch off of rkukura 's latest RM gerrit and will start coding some basic stuff18:49
s3wongthe goal is to have at least some starting point prior to next week's hackathon18:49
s3wongfour lines of update :-)18:49
banixthat was 7 actually18:50
rkukuras3wong: I’ll be in the bay area Monday-Thursday, and may be able to get together with you to work on this prior to the hack-a-thon if that helps18:50
s3wongbanix: well, you have to ignore LouisF 's question, that wasn't expected :-)18:50
*** seizadi has quit IRC18:50
s3wongrkukura: certainly. we can set this up offline later. That would be great18:51
SumitNaiksatams3wong: is everything in the document now?18:51
rkukuras3wong: OK, probably late Monday or sometime Wednesday is best for me18:51
SumitNaiksatams3wong: i did not read the latest update18:51
SumitNaiksatams3wong: just want to know before you start coding18:51
s3wongSumitNaiksatam: the content + my response to comments18:52
s3wongSumitNaiksatam: I will update the doc later also18:52
SumitNaiksatams3wong: okay i will check back, apologies for not getting back to you earlier18:52
s3wongSumitNaiksatam: it's alright - can't get mad at cores this week :-)18:52
SumitNaiksatams3wong: does it address regxboi’s comments?18:52
LouisFs3wong: i read the update18:53
s3wongSumitNaiksatam: yes18:53
SumitNaiksatams3wong: okay sweet18:53
s3wongLouisF: any further questions? (if so, please further comment on doc)18:53
LouisFs3wong: will do18:53
SumitNaiksatamok can we move to the vendor drivers? i know banix wanted to discuss18:53
*** lcheng has quit IRC18:53
s3wongwe would like to give 7 minutes to vendor drivers, I suppose18:53
SumitNaiksatamok moving on18:53
banixyes18:53
SumitNaiksatam#topic Vendor Drivers18:53
*** openstack changes topic to "Vendor Drivers (Meeting topic: networking_policy)"18:53
SumitNaiksatamwe have six vendor drivers’ specs in review18:54
SumitNaiksatamcheck #link https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy#July_17th.2C_10th.2C_2014 for the list18:54
SumitNaiksatambanix: go ahead18:54
SumitNaiksatamwe might be able to go a little over in this meeting (if we are not kicked out)18:54
banixas mentioned earlier we want to have a new attribte for classifiers; am wondering if adding that to the spec would cause any complications18:54
SumitNaiksatambanix: okay, yeah we had this disucssion last week with regxboi18:55
SumitNaiksatambanix: at this point i dont foresee any issues18:55
s3wongbanix: is that the mcast address match?18:55
SumitNaiksatambanix: that said, the leaner the spec the easier to review and approve18:55
banixso this will modify the model to add a new attribute18:55
banixs3wong: yes18:55
SumitNaiksatambanix: so add it only if you absolutely need it18:55
SumitNaiksatambanix: you dont need to modify the model, you extend it18:56
banixSumitNaiksatam: ok; ye, thatis what i menat18:56
banixmeant18:56
SumitNaiksatambanix: yes sure :-)18:56
SumitNaiksatamrkukura: what do you think?18:56
banixok thanks18:57
SumitNaiksatamsince you will be reviewing as well18:57
rkukuranot sure we want to go there, but I’ve been helping out on a spec for adding an ExtensionDriver API to ML2. We could do something similar.18:57
*** yamamoto has joined #openstack-meeting-318:57
SumitNaiksatamrkukura: the idea is that for the ibm driver, banix will be extending the classifier resource to be able to add a field for multicast protocol18:57
SumitNaiksatamrkukura: banix needs this in Juno, i believe18:58
SumitNaiksatamrkukura: so i dont think any dependency will work for him18:58
mandeeprkukura: The extension mech you are proposing is probably post Juno, correct?18:58
rms_13I would suggest to keep the framework here generic enough such that other vendor drivers can extend in future if rquire18:58
rkukuraNo, its needed for a spec already approved for Juno18:58
SumitNaiksatamrms_13: it is18:59
rms_13cool18:59
marunsorry I missed the mention, but was there any decision on merging tests to tempest for the new api?18:59
mandeeprkukura: In Juno for ML2, I was asking about the timeframe for a similar mech for GBP post Juno19:00
SumitNaiksatammarun: we will be posting a WIP patch19:00
marunSumitNaiksatam: sounds good.  I don't think experimental features should have tests in tempest (and we can have similar coverage in-tree anyway), but we can always rework the WIP to be in-tree instead of in tempest before merge.19:01
rkukuramarun: Whether merging the tempest patch would lock-down the API post-juno is an open question that mlavalle is going to look into19:01
SumitNaiksatammarun: exactly19:01
SumitNaiksatammarun: this will help whoever wants to test this19:01
marunrkukura: the discussions that I've had on the tempest side have indicated that api testing in tempest is for preventing backwards incompatible changes19:01
SumitNaiksatammarun: but does not have to be merged19:01
marunrkukura: i.e. stable APIs19:01
marunSumitNaiksatam: understood, definitely a good step.19:02
*** yamamoto has quit IRC19:02
SumitNaiksatammarun: ok thanks19:02
marunrkukura: so if we expect an API to not be stable, merging to tempest takes valuable qa cycles unnecessarily.19:02
marunmlavalle: ^^19:02
marun(it's also more expensive for us)19:03
SumitNaiksatamso we are over time, and we are here until we are kicked out19:03
rkukuramarun: That’s why we are asking these questions, but it seems a WIP tempest patch will let us get started quickest.19:03
marunrkukura: completely agree that it is a good starting point19:03
SumitNaiksatam#agreed Group Policy team will introduce WIP tempest patch to aid in end-to-end testing of the stacked patches19:04
marunrkukura: the retargetable spec was just merged and the code hasn't yet, so api testing in-tree is not ready yet.19:04
mandeepbanix: So back on the issue of extending resources for your plugin, my recommendation is that you should to do that. We can have a more generic mechanism in future (modeled on ML2, depending on that experience), but you should not depend on that for the Juno plugin.19:04
rkukuramarun: One consideration would be that if we know this won’t go into tempest anytime soon, maybe we should use python-neutronclient instead of the tempest REST client.19:05
*** krotscheck has quit IRC19:05
marunrkukura: but I do expect to have the ability to start merging in-tree API tests in juno-319:05
SumitNaiksatammandeep: thanks for directing back to the topic in discussion here19:05
marunrkukura: no, the tempest rest client is the way to go19:05
*** krotscheck has joined #openstack-meeting-319:05
SumitNaiksatamrkukura: see mandeep’s suggestion ^^^ , does that work for you?19:05
marunrkukura: I'm working with dkranz to refactor the tempest client so that we can implement it against the plugin api19:05
rkukuramandeep: agreed regarding the extension dricer19:05
rkukuradriver19:05
banixmandeep: ok19:05
marunrkukura: that would allow tests in the tempest tree written for the rest client to be trivially portable to our plugin api19:06
marunrkukura: that won't be possible with the native client19:06
*** jackib has joined #openstack-meeting-319:06
rkukuramarun: That is useful for API tests, but our initial focus is really on end-to-end system tests with nova, tempest, …19:06
marunrkukura:19:06
marunhttps://review.openstack.org/#/c/106916/19:06
rkukuras/tempest/keystone/19:06
SumitNaiksatamok banix mandeep rkukura so we are agreeing that banix you will use resource extension for now in your driver, and later resort to a more generic mechanism for drivers as and when that evolves19:06
marunrkukura: there's nothing stopping that from being maintained in our tree either19:07
rkukuraSumitNaiksatam: If he really wants an extension, he might need the kind of thing we are planning for ML219:07
banixSumitNaiksatam: sounds good19:07
mandeeprkukura: Yes, post Juno.19:07
marunrkukura: but I'm less clear on how scenario tests for experimental features should be handled by tempest19:08
rkukuraIt basically calls the extension driver to validate extended attributes, persistent them, and put them in resource dictionaries for Context objects and responses.19:08
marunrkukura: in any case, there has been discussion on the list about deprecating the use of the native python clients in scenario testing because they make debugging so much harder19:08
mlavallemarun: I will bring up the issue of scenario tests for experimental features during next week's tempest meeting19:08
SumitNaiksatamrkukura: i think given the short time frame for Juno, i would not want to block a vendor driver for a framework which is evolving in another part of the code base19:09
marunrkukura, mlavalle: http://lists.openstack.org/pipermail/openstack-dev/2014-July/039879.html19:09
SumitNaiksatamjust a note - we are currently discussing the “vendor driver” agenda item in our topic19:09
marunmlavalle: appreciated19:09
rkukuramarun: I’m not really concerned about which client is used for these tests, but just want to make sure we have a short term plan for end-to-end system tests were we really validate correct connectivity between VMs.19:10
marunrkukura: there's nothing stopping us doing that for VMs in functional tests.19:10
SumitNaiksatamthe tempest topic was discussed earlier, and we can circle back once we are done discussing the current agenda item19:10
marunrkukura: VMs -> fake VMs19:10
marunrkukura: I know I keep talking about this, I haven't had specific use cases to implement and I was supposed to get back to you about this a couple of weeks ago.19:10
*** lcheng has joined #openstack-meeting-319:11
SumitNaiksatamrkukura my earlier point - i think given the short time frame for Juno, i would not want to block a vendor driver for a framework which is evolving in another part of the code base19:11
rkukuramarun: Certainly need running neutron-server, l2-agent, l3-agent, and dhcp-agent at least.19:11
marunrkukura: I'd be up for proving this idea if I can get a detailed-enough description of test planning19:11
SumitNaiksatamrkukura: do you agree?19:11
marunrkukura: sounds entirely like overkill for a feature that rides on top of the existing infrastructure19:12
marunrkukura: it would be more valuable to write functional tests for those pieces without group policy and then add group policy to the mix19:12
rkukuraSumitNaiksatam: I think we’d have to incorporate the “extension” as part of the GP API.19:12
marunrkukura: imho19:12
SumitNaiksatamrkukura: i am not sure i understand that19:13
rkukuramarun: I’m not disagreeing with any of that, but we have a very short term requirement to have some sort of end-to-end system testing. Just trying to find the quickest path to that.19:13
SumitNaiksatamrkukura: the suggestion was to have a separate extension module which will extend the policy classifier resources19:13
SumitNaiksatam*resource19:13
mandeeprkukura: We are running out of time, so let us discuss this right after the meeting. At this stage, IMO it is too late to propose a chnage to GBP API for Juno.19:14
SumitNaiksatammandeep: i dont think a change to the GBP API is required19:14
marunrkukura: fair enoujgh19:14
SumitNaiksatamok i think we are having two separate meetings here19:14
rkukuraSumitNaiksatam: There would need to be code somewhere that handles these extended attributes. The extension driver is what we are proposing to do this in ML2.19:14
*** marun is now known as marun_afk19:15
SumitNaiksatamrkukura: that can be in the vendor’s driver, right?19:15
banixkeeping what s3wong mentioned about this week in mind.19:15
rkukuraLets not forget that this is an iterative process, and details in the specs will often get revisited/changed during development.19:15
mandeeprkukura: I believe that the right model is to implement it in ML2 in this cycle, and use that learning to extend GBP plugin in the next cycle19:15
SumitNaiksatamrkukura: sure19:16
rkukuraSumitNaiksatam: The drivers do not have a mechanism to handle the persistence of new attributes.19:16
rkukuramandeep: I agree, but I’m not sure there is a short term solution for banix for juno.19:16
SumitNaiksatamrkukura: i think what you are saying is that the resource extension cannot be supported if its not added to the GP plugin19:16
mandeeprkukura: OK, I understand your point now19:17
SumitNaiksatamok lets take this offline and see what is the best way to approach it in the short term19:17
banixrkukura: yes i understand your point and gree19:17
mandeepI was under the impression that the drivers  have a mechanism to handle this19:17
SumitNaiksatam#topic open discussion19:17
*** openstack changes topic to "open discussion (Meeting topic: networking_policy)"19:17
rkukuraThat’s what we’ve concluded on ML2, which whose mechanism drivers have the same model. Initially some changes to the mechanism driver API were proposed, but even that did not allow extended attribute values to be returned in REST responses.19:17
SumitNaiksatamwe skipped a couple of items19:18
SumitNaiksatamanything we wanted to discuss urgently?19:18
*** pballand has quit IRC19:18
banixextending the model will require changing the plugin which is itself under eview hence the complications19:18
banixok thanks for the commnts rkukura mandeep and SumitNaiksatam19:18
SumitNaiksatamkevinbenton earlier pointed out the API intercept spec patch: https://review.openstack.org/#/c/105695/19:18
SumitNaiksatambanix: yes19:18
rkukurabanix: If the extension driver gets into ML2 for juno, I’m confident copying it into GP would be trivial.19:19
SumitNaiksatambanix: there has to be some place to load the plugin19:19
SumitNaiksatam* load the extension19:19
SumitNaiksatamok so we are 20 mins over19:19
SumitNaiksatamanything else?19:19
*** pballand has joined #openstack-meeting-319:19
banixalternatively one could have a separate service plugin altogethr. right?19:19
SumitNaiksatambanix: yes19:19
SumitNaiksatamso just a reminder, we have the hackathon next week19:20
SumitNaiksatamso we will most likely not be doing this IRC meeting next week19:20
SumitNaiksatamhope to see you all these19:20
banixif possible google hangout will be good19:20
SumitNaiksatam*there19:20
rkukurabanix: That would let you add new resources, but not extend GBP resources19:20
SumitNaiksatambanix: yes sure, we will plan something along those lines19:20
SumitNaiksatamrkukura banix: lets take this offline and find a solution19:21
SumitNaiksatamthanks all, bye!19:21
rkukurabye19:21
SumitNaiksatam#endmeeting19:21
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:21
openstackMeeting ended Thu Jul 17 19:21:21 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:21
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-07-17-18.00.html19:21
banixbye19:21
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-07-17-18.00.txt19:21
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-07-17-18.00.log.html19:21
kevinbentonbye19:21
*** rms_13 has quit IRC19:22
*** hemanthravi has quit IRC19:22
*** rkukura has left #openstack-meeting-319:22
banixcore resources now gets extended by extensions. right? network getting extended by router extension for example19:23
*** LouisF has quit IRC19:30
*** banix_ has joined #openstack-meeting-319:32
*** banix__ has joined #openstack-meeting-319:36
*** banix_ has quit IRC19:37
*** nati_ueno has joined #openstack-meeting-319:39
*** thomasem has quit IRC19:40
*** thomasem_ has joined #openstack-meeting-319:40
*** nacim has quit IRC19:45
*** banix__ has quit IRC19:46
*** banix_ has joined #openstack-meeting-319:57
*** yamamoto has joined #openstack-meeting-319:57
*** pgpus has joined #openstack-meeting-319:58
*** banix_ has quit IRC19:58
*** nati_ueno has quit IRC20:00
*** mlavalle has quit IRC20:01
*** banix has quit IRC20:01
*** shwetaap has quit IRC20:02
*** yamamoto has quit IRC20:02
*** nati_ueno has joined #openstack-meeting-320:02
*** shwetaap has joined #openstack-meeting-320:02
*** nati_ueno has quit IRC20:05
*** sadasu_ has quit IRC20:06
*** nati_ueno has joined #openstack-meeting-320:07
*** mandeep has left #openstack-meeting-320:07
*** nati_ueno has quit IRC20:08
*** banix has joined #openstack-meeting-320:10
*** jtomasek has quit IRC20:11
*** seizadi has joined #openstack-meeting-320:16
*** banix has quit IRC20:20
*** banix has joined #openstack-meeting-320:28
*** Sukhdev has quit IRC20:29
*** lcheng has quit IRC20:29
*** erecio has joined #openstack-meeting-320:36
*** pgpus has quit IRC20:36
*** m1dev has quit IRC20:37
*** m1dev has joined #openstack-meeting-320:38
*** lcheng has joined #openstack-meeting-320:40
*** banix has quit IRC20:42
*** shwetaap has quit IRC20:46
*** SumitNaiksatam has quit IRC20:47
*** thomasem has joined #openstack-meeting-320:51
*** thomasem_ has quit IRC20:54
*** banix has joined #openstack-meeting-320:54
*** thomasem has quit IRC20:56
*** yamamoto has joined #openstack-meeting-320:57
*** yamamoto has quit IRC21:02
*** cjellick has quit IRC21:02
*** cjellick has joined #openstack-meeting-321:02
*** nati_ueno has joined #openstack-meeting-321:03
*** rfolco has quit IRC21:04
*** jackib has quit IRC21:04
*** SumitNaiksatam has joined #openstack-meeting-321:05
*** cjellick has quit IRC21:06
*** cjellick has joined #openstack-meeting-321:11
*** cjellick has quit IRC21:12
*** cjellick has joined #openstack-meeting-321:13
*** cjellick_ has joined #openstack-meeting-321:15
*** cjellick_ has quit IRC21:16
*** cjellick_ has joined #openstack-meeting-321:16
*** cjellick has quit IRC21:17
*** chuckC has quit IRC21:22
*** lcheng has quit IRC21:23
*** peristeri has quit IRC21:24
*** hurgleburgler1 has quit IRC21:24
*** hurgleburgler has joined #openstack-meeting-321:25
*** hurgleburgler has joined #openstack-meeting-321:25
*** erecio has quit IRC21:29
*** hurgleburgler has quit IRC21:29
*** banix has quit IRC21:38
*** Sukhdev has joined #openstack-meeting-321:38
*** seizadi has quit IRC21:38
*** nati_ueno has quit IRC21:41
*** mwagner_lap has quit IRC21:43
*** shwetaap has joined #openstack-meeting-321:43
*** shwetaap has quit IRC21:47
*** m1dev has quit IRC21:51
*** m1dev has joined #openstack-meeting-321:52
*** seizadi has joined #openstack-meeting-321:52
*** hurgleburgler has joined #openstack-meeting-321:54
*** yamamoto has joined #openstack-meeting-321:57
*** yamamoto_ has joined #openstack-meeting-321:59
*** yamamoto has quit IRC21:59
*** yamamoto_ has quit IRC22:03
*** jpomero has quit IRC22:10
*** chuckC has joined #openstack-meeting-322:23
*** m1dev has quit IRC22:24
*** m1dev has joined #openstack-meeting-322:25
*** david-lyle has quit IRC22:31
*** mwagner_lap has joined #openstack-meeting-322:35
*** MaxV has quit IRC22:39
*** s3wong has quit IRC22:44
*** mwagner_lap has quit IRC22:47
*** yyywu has quit IRC22:50
*** yyywu has joined #openstack-meeting-322:51
*** krotscheck has quit IRC22:51
*** nelsnels_ has quit IRC22:51
*** carl_baldwin has quit IRC22:51
*** boris-42 has quit IRC22:51
*** m1dev has quit IRC22:52
*** chuckC has quit IRC22:52
*** hurgleburgler has quit IRC22:52
*** otherwiseguy has quit IRC22:52
*** haleyb has quit IRC22:52
*** safchain has quit IRC22:52
*** garyduan has quit IRC22:52
*** jaypipes has quit IRC22:52
*** kevinbenton has quit IRC22:52
*** HenryG has quit IRC22:52
*** coolsvap has quit IRC22:52
*** zehicle has quit IRC22:52
*** zz_johnthetubagu has quit IRC22:52
*** abramley has quit IRC22:52
*** rharwood has quit IRC22:52
*** jomara has quit IRC22:52
*** davidlenwell has quit IRC22:52
*** m1dev has joined #openstack-meeting-322:53
*** chuckC has joined #openstack-meeting-322:53
*** hurgleburgler has joined #openstack-meeting-322:53
*** otherwiseguy has joined #openstack-meeting-322:53
*** haleyb has joined #openstack-meeting-322:53
*** safchain has joined #openstack-meeting-322:53
*** garyduan has joined #openstack-meeting-322:53
*** jaypipes has joined #openstack-meeting-322:53
*** kevinbenton has joined #openstack-meeting-322:53
*** HenryG has joined #openstack-meeting-322:53
*** coolsvap has joined #openstack-meeting-322:53
*** rharwood has joined #openstack-meeting-322:53
*** zehicle has joined #openstack-meeting-322:53
*** zz_johnthetubagu has joined #openstack-meeting-322:53
*** abramley has joined #openstack-meeting-322:53
*** jomara has joined #openstack-meeting-322:53
*** davidlenwell has joined #openstack-meeting-322:53
*** krotscheck has joined #openstack-meeting-322:53
*** nelsnels_ has joined #openstack-meeting-322:53
*** carl_baldwin has joined #openstack-meeting-322:53
*** boris-42 has joined #openstack-meeting-322:53
*** mikal has quit IRC22:54
*** ruhe has quit IRC22:54
*** mikal has joined #openstack-meeting-322:54
*** ruhe has joined #openstack-meeting-322:54
*** jrist has quit IRC22:54
*** SergeyLukjanov has quit IRC22:54
*** pleia2 has quit IRC22:54
*** dolphm has quit IRC22:54
*** russellb has quit IRC22:54
*** sarob has quit IRC22:54
*** zigo has quit IRC22:54
*** flaviof_zzz has quit IRC22:54
*** fungi has quit IRC22:54
*** enikanorov_ has quit IRC22:54
*** troytoman has quit IRC22:54
*** ttx has quit IRC22:54
*** rossella_s has quit IRC22:55
*** Adri2000 has quit IRC22:55
*** tteggel has quit IRC22:55
*** kashyap has quit IRC22:55
*** chuckC has quit IRC22:55
*** jrist has joined #openstack-meeting-322:55
*** SergeyLukjanov has joined #openstack-meeting-322:55
*** pleia2 has joined #openstack-meeting-322:55
*** sarob has joined #openstack-meeting-322:55
*** dolphm has joined #openstack-meeting-322:55
*** russellb has joined #openstack-meeting-322:55
*** zigo has joined #openstack-meeting-322:55
*** flaviof_zzz has joined #openstack-meeting-322:55
*** fungi has joined #openstack-meeting-322:55
*** enikanorov_ has joined #openstack-meeting-322:55
*** troytoman has joined #openstack-meeting-322:55
*** ttx has joined #openstack-meeting-322:55
*** rossella_s has joined #openstack-meeting-322:56
*** Adri2000 has joined #openstack-meeting-322:56
*** tteggel has joined #openstack-meeting-322:56
*** kashyap has joined #openstack-meeting-322:56
*** yamamoto has joined #openstack-meeting-322:57
*** yamamoto has quit IRC23:02
*** chuckC has joined #openstack-meeting-323:03
*** seizadi has quit IRC23:04
*** nati_ueno has joined #openstack-meeting-323:06
*** m1dev has quit IRC23:07
*** m1dev has joined #openstack-meeting-323:08
*** jgrimm has quit IRC23:10
*** yamamoto has joined #openstack-meeting-323:15
*** carl_baldwin has quit IRC23:19
*** yamamoto has quit IRC23:20
*** Sukhdev has quit IRC23:37
*** m1dev has quit IRC23:43
*** m1dev has joined #openstack-meeting-323:44
*** alexpilotti has joined #openstack-meeting-323:46
*** alexpilotti has quit IRC23:52
*** safchain has quit IRC23:55
*** yamamoto has joined #openstack-meeting-323:57
*** rhagarty has quit IRC23:57

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