Wednesday, 2014-07-16

*** rhagarty_ has joined #openstack-meeting-300:04
*** rhagarty has quit IRC00:05
*** xuhanp has joined #openstack-meeting-300:06
*** yamahata has quit IRC00:09
*** thangp has joined #openstack-meeting-300:10
*** asahlin has quit IRC00:14
*** yamamoto has joined #openstack-meeting-300:18
*** yamamoto_ has joined #openstack-meeting-300:21
*** yamamoto has quit IRC00:23
*** yamamoto_ has quit IRC00:23
*** yamamoto has joined #openstack-meeting-300:25
*** yamamoto has quit IRC00:27
*** carl_baldwin has joined #openstack-meeting-300:28
*** otherwiseguy has quit IRC00:36
*** Sukhdev has quit IRC00:38
*** Sukhdev has joined #openstack-meeting-300:38
*** carl_baldwin has quit IRC00:45
*** hurgleburgler has quit IRC00:46
*** SumitNaiksatam has quit IRC00:47
*** otherwiseguy has joined #openstack-meeting-300:47
*** carl_baldwin has joined #openstack-meeting-300:49
*** pballand has quit IRC00:51
*** gugl2 has quit IRC00:51
*** carl_baldwin has quit IRC00:59
*** chuckC has quit IRC01:03
*** xuhanp has quit IRC01:05
*** yamahata has joined #openstack-meeting-301:09
*** seizadi has joined #openstack-meeting-301:21
*** baohua has joined #openstack-meeting-301:23
*** clu_ has quit IRC01:25
*** tomoe_ has joined #openstack-meeting-301:26
*** stanzgy has joined #openstack-meeting-301:35
*** yamamoto_ has joined #openstack-meeting-301:37
*** yamamoto_ has quit IRC01:42
*** Sukhdev has quit IRC01:44
*** yamamoto_ has joined #openstack-meeting-301:47
*** thomasem has joined #openstack-meeting-301:59
*** thomasem has quit IRC01:59
*** yamamoto_ has quit IRC01:59
*** pballand has joined #openstack-meeting-302:03
*** eghobo has quit IRC02:13
*** banix has joined #openstack-meeting-302:13
*** SumitNaiksatam has joined #openstack-meeting-302:15
*** chuckC has joined #openstack-meeting-302:17
*** SumitNaiksatam has quit IRC02:19
*** yamamoto_ has joined #openstack-meeting-302:32
*** pgpus has quit IRC02:32
*** ivar-lazzaro1 has quit IRC02:36
*** cjellick has quit IRC02:47
*** cjellick has joined #openstack-meeting-302:48
*** cjellick has quit IRC02:52
*** pballand has quit IRC02:55
*** nati_ueno has quit IRC02:57
*** Sukhdev has joined #openstack-meeting-303:00
*** pballand has joined #openstack-meeting-303:12
*** sankarshan_away is now known as sankarshan03:16
*** sankarshan is now known as sankarshan_away03:17
*** carl_baldwin has joined #openstack-meeting-303:30
*** hurgleburgler has joined #openstack-meeting-303:33
*** thangp has quit IRC03:36
*** baohua_ has joined #openstack-meeting-303:38
*** pballand has quit IRC03:39
*** baohua has quit IRC03:40
*** seizadi has quit IRC03:43
*** carl_baldwin has quit IRC03:46
*** carl_baldwin has joined #openstack-meeting-303:52
*** eghobo has joined #openstack-meeting-304:09
*** Sukhdev has quit IRC04:11
*** eghobo has quit IRC04:14
*** eghobo has joined #openstack-meeting-304:15
*** tomoe__ has joined #openstack-meeting-304:16
*** cjellick has joined #openstack-meeting-304:18
*** banix has quit IRC04:19
*** tomoe_ has quit IRC04:19
*** tomoe_ has joined #openstack-meeting-304:20
*** tomoe__ has quit IRC04:20
*** cjellick has quit IRC04:22
*** eghobo has quit IRC04:27
*** carl_baldwin has quit IRC04:39
*** pballand has joined #openstack-meeting-305:04
*** cjellick has joined #openstack-meeting-305:19
*** cjellick has quit IRC05:23
*** tmazur has joined #openstack-meeting-305:24
*** marios_ has quit IRC05:27
*** pballand has quit IRC05:42
*** tomoe__ has joined #openstack-meeting-305:44
*** tomoe_ has quit IRC05:48
*** tomoe__ has quit IRC05:49
*** tomoe_ has joined #openstack-meeting-305:49
*** chuckC has quit IRC05:51
*** chuckC has joined #openstack-meeting-305:52
*** tomoe_ has quit IRC06:00
*** SumitNaiksatam has joined #openstack-meeting-306:18
*** cjellick has joined #openstack-meeting-306:19
*** MaxV has joined #openstack-meeting-306:22
*** cjellick has quit IRC06:23
*** nati_ueno has joined #openstack-meeting-306:26
*** MaxV has quit IRC06:31
*** MaxV has joined #openstack-meeting-306:31
*** MaxV has quit IRC06:32
*** ndipanov_gone is now known as ndipanov06:34
*** jcoufal has joined #openstack-meeting-306:38
*** tomoe_ has joined #openstack-meeting-306:44
*** arosen has quit IRC06:51
*** mrunge has joined #openstack-meeting-306:51
*** arosen has joined #openstack-meeting-306:51
*** mrunge has quit IRC06:52
*** mrunge has joined #openstack-meeting-306:57
*** jtomasek has joined #openstack-meeting-307:06
*** d0ugal has quit IRC07:07
*** d0ugal has joined #openstack-meeting-307:07
*** iovadia has joined #openstack-meeting-307:34
*** iovadia has quit IRC07:38
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"07:54
*** iovadia has joined #openstack-meeting-307:54
*** nati_ueno has quit IRC07:56
*** igordcard has joined #openstack-meeting-308:05
*** nacim has joined #openstack-meeting-308:08
*** tomoe__ has joined #openstack-meeting-308:10
*** zz_johnthetubagu is now known as johnthetubaguy08:11
*** tomoe_ has quit IRC08:13
*** alexpilotti has joined #openstack-meeting-308:13
*** tomoe__ has quit IRC08:14
*** tomoe_ has joined #openstack-meeting-308:14
*** baohua_ has quit IRC08:16
*** safchain has joined #openstack-meeting-308:17
*** arosen has quit IRC08:26
*** MaxV has joined #openstack-meeting-308:36
*** baohua has joined #openstack-meeting-308:37
*** iovadia1 has joined #openstack-meeting-308:38
*** iovadia has quit IRC08:38
*** iovadia1 has quit IRC08:43
*** overlayer has joined #openstack-meeting-308:50
*** baohua_ has joined #openstack-meeting-308:55
*** baohua has quit IRC08:55
*** iovadia has joined #openstack-meeting-308:58
*** yamahata has quit IRC09:04
*** igordcard has quit IRC09:10
*** tmazur has quit IRC09:18
*** cjellick has joined #openstack-meeting-309:21
*** cjellick has quit IRC09:26
*** tmazur has joined #openstack-meeting-309:30
*** iovadia has quit IRC09:51
*** tomoe_ has quit IRC09:52
*** iovadia has joined #openstack-meeting-310:04
*** alexpilotti has quit IRC10:09
*** tmazur has quit IRC10:26
*** tmazur has joined #openstack-meeting-310:26
*** nacim has quit IRC10:35
*** overlayer has quit IRC10:49
*** yamamoto_ has quit IRC11:06
*** MaxV has quit IRC11:22
*** MaxV has joined #openstack-meeting-311:29
*** yamamoto has joined #openstack-meeting-311:37
*** yamamoto has quit IRC11:38
*** sankarshan_away is now known as sankarshan11:42
*** sankarshan is now known as sankarshan_away11:43
*** Longgeek has joined #openstack-meeting-311:49
*** yamahata has joined #openstack-meeting-311:49
*** rfolco has joined #openstack-meeting-311:57
*** nacim has joined #openstack-meeting-311:58
*** lblanchard has joined #openstack-meeting-312:11
*** yamamoto has joined #openstack-meeting-312:12
*** yamahata has quit IRC12:25
*** yamahata has joined #openstack-meeting-312:30
*** mwagner_lap has quit IRC12:30
*** xuhanp has joined #openstack-meeting-312:35
*** mattg__ has joined #openstack-meeting-312:48
*** mattg__ has left #openstack-meeting-312:49
*** julim has joined #openstack-meeting-312:49
*** cjellick has joined #openstack-meeting-313:05
*** cjellick has quit IRC13:06
*** cjellick has joined #openstack-meeting-313:06
*** thomasem has joined #openstack-meeting-313:13
*** peristeri has joined #openstack-meeting-313:15
*** krotscheck has quit IRC13:28
*** MaxV_ has joined #openstack-meeting-313:32
*** MaxV has quit IRC13:34
*** krotscheck has joined #openstack-meeting-313:34
*** [1]m1dev has joined #openstack-meeting-313:40
*** [1]m1dev has quit IRC13:41
*** mwagner_lap has joined #openstack-meeting-313:42
*** thangp has joined #openstack-meeting-313:42
*** [1]m1dev has joined #openstack-meeting-313:43
*** baohua_ has quit IRC13:47
*** jcoufal has quit IRC13:50
*** jcoufal has joined #openstack-meeting-313:51
*** yamahata has quit IRC13:54
*** yamahata has joined #openstack-meeting-313:54
*** seizadi has joined #openstack-meeting-313:57
*** nati_ueno has joined #openstack-meeting-314:00
*** nelsnelson has joined #openstack-meeting-314:00
*** s1rp_ has left #openstack-meeting-314:10
*** baohua has joined #openstack-meeting-314:19
*** stanzgy has quit IRC14:25
*** armax has joined #openstack-meeting-314:29
*** Longgeek has quit IRC14:34
*** jcoufal has quit IRC14:35
*** nacim has quit IRC14:35
*** mrunge has quit IRC14:43
*** nati_ueno has quit IRC14:45
*** rm_work has quit IRC14:47
*** rm_work|away has joined #openstack-meeting-314:48
*** rm_work|away is now known as rm_work14:49
*** rm_work has joined #openstack-meeting-314:49
*** jgrimm has joined #openstack-meeting-314:51
*** seizadi has quit IRC14:57
*** ijw has joined #openstack-meeting-315:00
*** carl_baldwin has joined #openstack-meeting-315:03
*** thinrichs has joined #openstack-meeting-315:05
*** otherwiseguy has quit IRC15:06
*** Sukhdev has joined #openstack-meeting-315:07
*** ndipanov has quit IRC15:08
*** thinrichs has quit IRC15:08
*** amitpp has joined #openstack-meeting-315:16
*** shakamunyi has joined #openstack-meeting-315:17
*** shakamunyi has quit IRC15:17
*** david-lyle has joined #openstack-meeting-315:20
*** shakamunyi has joined #openstack-meeting-315:24
*** shakamunyi has quit IRC15:24
*** shakamunyi has joined #openstack-meeting-315:24
*** shakamunyi has quit IRC15:24
*** nati_ueno has joined #openstack-meeting-315:28
*** rhagarty_ has quit IRC15:32
*** ijw is now known as ijw-away15:33
*** rhagarty has joined #openstack-meeting-315:34
*** nati_ueno has quit IRC15:35
*** baohua has quit IRC15:37
*** nati_ueno has joined #openstack-meeting-315:38
*** nati_ueno has quit IRC15:43
*** nati_ueno has joined #openstack-meeting-315:43
*** otherwiseguy has joined #openstack-meeting-315:46
*** yamahata has quit IRC15:47
*** HenryG is now known as HenryG_afk15:49
*** banix has joined #openstack-meeting-315:53
*** pballand has joined #openstack-meeting-315:54
*** tmazur has quit IRC15:55
*** pballand has quit IRC15:59
*** MaxV_ has quit IRC16:02
*** nacim has joined #openstack-meeting-316:02
*** pballand has joined #openstack-meeting-316:06
*** peristeri has quit IRC16:06
*** xuhanp has quit IRC16:08
*** yamahata has joined #openstack-meeting-316:08
*** nati_ueno has quit IRC16:09
*** ijw-away has quit IRC16:09
*** chuckC has quit IRC16:10
*** MaxV has joined #openstack-meeting-316:11
*** MaxV has quit IRC16:16
*** pgpus has joined #openstack-meeting-316:17
*** yamahata has quit IRC16:21
*** tjones has joined #openstack-meeting-316:28
tjones#startmeeting novabugscrub16:30
openstackMeeting started Wed Jul 16 16:30:18 2014 UTC and is due to finish in 60 minutes.  The chair is tjones. Information about MeetBot at http://wiki.debian.org/MeetBot.16:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:30
*** openstack changes topic to " (Meeting topic: novabugscrub)"16:30
openstackThe meeting name has been set to 'novabugscrub'16:30
*** safchain has quit IRC16:30
*** nacim has quit IRC16:47
*** cjellick_ has joined #openstack-meeting-316:49
*** pballand has quit IRC16:51
*** cjellick has quit IRC16:52
tjones#endmeeting16:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:52
*** tjones has left #openstack-meeting-316:52
openstackMeeting ended Wed Jul 16 16:52:57 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-07-16-16.30.html16:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-07-16-16.30.txt16:53
openstackLog:            http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-07-16-16.30.log.html16:53
*** HenryG_afk is now known as HenryG16:56
*** terryw has joined #openstack-meeting-317:01
*** otherwiseguy has quit IRC17:01
*** peristeri has joined #openstack-meeting-317:05
*** pballand has joined #openstack-meeting-317:05
*** pballand has quit IRC17:05
*** Sukhdev has quit IRC17:07
*** SumitNaiksatam has quit IRC17:09
*** nati_ueno has joined #openstack-meeting-317:11
*** jaypipes has quit IRC17:12
*** rudrarugge has joined #openstack-meeting-317:16
*** rudrarugge has quit IRC17:17
*** ivar-lazzaro has joined #openstack-meeting-317:19
*** shakamunyi has joined #openstack-meeting-317:20
*** shakamunyi has quit IRC17:20
*** shakamunyi has joined #openstack-meeting-317:21
*** shakamunyi has quit IRC17:21
*** hemanthravi has joined #openstack-meeting-317:23
*** SumitNaiksatam has joined #openstack-meeting-317:25
*** MaxV has joined #openstack-meeting-317:25
*** LouisF has joined #openstack-meeting-317:26
*** vinay_yadhav has joined #openstack-meeting-317:27
*** anil_rao has joined #openstack-meeting-317:28
*** iovadia has quit IRC17:29
*** Swami has joined #openstack-meeting-317:30
SumitNaiksatamhi neutron adv services’ team!17:30
vinay_yadhavHi17:30
hemanthravihi17:30
ivar-lazzarohi17:30
*** jaypipes has joined #openstack-meeting-317:30
dougwigo/17:30
Swamihi all17:30
*** natarajk has joined #openstack-meeting-317:30
*** pcm_ has joined #openstack-meeting-317:30
cgoncalveshi, everyone!17:31
pcm_hi17:31
SumitNaiksatamokay lets get started17:31
natarajkhi17:31
SumitNaiksatam#startmeeting Networking Advanced Services17:31
openstackMeeting started Wed Jul 16 17:31:24 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.17:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:31
*** openstack changes topic to " (Meeting topic: Networking Advanced Services)"17:31
openstackThe meeting name has been set to 'networking_advanced_services'17:31
*** SridarK has joined #openstack-meeting-317:31
SumitNaiksatam#info agenda: https://wiki.openstack.org/wiki/Meetings/AdvancedServices17:31
SumitNaiksatam#info Juno specification submission deadline: July 10th, specification approval deadline: july 20th17:31
SumitNaiksatami think i had earlier mentioned SAD to be july 17th17:32
SumitNaiksatamits actually july 20th!17:32
SumitNaiksatamso we have a little more time than we thought we had17:32
SumitNaiksatamthat said, i think we are definitely starved on the reviewer attention from neutron cores17:33
SumitNaiksatamso its an uphill task17:33
SumitNaiksatamso a few people are not able to make it today for different reasons and provided their updates17:33
*** regXboi has joined #openstack-meeting-317:33
*** pballand has joined #openstack-meeting-317:33
SumitNaiksatam#topic Flavors17:33
*** openstack changes topic to "Flavors (Meeting topic: Networking Advanced Services)"17:33
SumitNaiksatamenikanorov_ cannot make it, and i believe mark is on a vacation17:34
SumitNaiksatam#link https://review.openstack.org/10272317:34
*** shwetaap has joined #openstack-meeting-317:34
*** cjellick_ has quit IRC17:34
SumitNaiksatamthere is also on an ongoing mailing list thread on this:17:35
SumitNaiksatam#link http://lists.openstack.org/pipermail/openstack-dev/2014-July/040336.html17:35
SumitNaiksatamfor the latest set of discussions17:35
*** cjellick has joined #openstack-meeting-317:35
SumitNaiksatamper enikanorov_ he has posted a WIP patch #link https://review.openstack.org/#/c/10598217:35
SumitNaiksatamthe above is for the implementation, and makes certain assumptions on the spec17:36
*** hareeshpc has joined #openstack-meeting-317:36
*** cjellick has quit IRC17:36
SumitNaiksatamfrom enikanorov_’s point of view the main pending item is the exposing of extensions list17:36
*** cjellick has joined #openstack-meeting-317:36
banixhi everybody (sorry for being late)17:36
SumitNaiksatambanix: np, welcome17:37
*** terryw has quit IRC17:37
SumitNaiksatami think enikanorov_ and mark are not in agreement on the extensions list17:37
SumitNaiksatamanything we want to discuss here in that regard?17:38
SumitNaiksatami know we have beaten this horse to death, so i dont know what to say :-)17:38
dougwigwe could argue a bunch, just so it really feels like a flavors update.17:38
SumitNaiksatamon the topic of flavors that is17:38
regXboiis there any way we can get those two to agree on something and go forward with it?17:39
*** shakamunyi has joined #openstack-meeting-317:39
SumitNaiksatamregXboi: :-)17:39
*** shakamunyi has quit IRC17:39
SumitNaiksatamthats what we have been trying17:39
regXboiI was afraid that would be the answer17:39
SumitNaiksatamdougwig: you had a specific point that you wanted to discuss or you were making the point, that we should move ahead17:39
*** mandeep has joined #openstack-meeting-317:39
cgoncalvesnot much to say from my end. personally I've been not following closely the ongoing discussion. enikanorov_ and mark should first agree on the flavor proposal and then we can continue reviewing it17:40
dougwigi was just being snarky; no point.17:40
*** shakamunyi has joined #openstack-meeting-317:40
SumitNaiksatamall i can say is that if we have a strong preference in terms of one approach versus the other, please make it known on the review17:41
SumitNaiksatamthat might help in getting two opinions to reconcile17:41
cgoncalvesSumitNaiksatam: good point17:41
*** shakamunyi has quit IRC17:42
garyduanI think in the meeting dedicated to Flavor, we kind of make an agreement, right?17:42
SumitNaiksatamthere was also the other discussion on the service type but i think there is a better chance of consensus on that17:42
SumitNaiksatamgaryduan: apparently not on exposing the extensions’s list17:42
garyduanright. I saw discussion on the spec review17:42
SumitNaiksatamalright, so can i request everyone to weigh on the review: #link https://review.openstack.org/10272317:43
SumitNaiksatamin the next day or so, more specifically in the context of the extensions discussion17:43
SumitNaiksatamperhaps looking at #link https://review.openstack.org/#/c/10598217:43
SumitNaiksatammight help you to understand better17:43
SumitNaiksatamper the neutron project goals, flavors has a priority among the adv services’ blueprints, so please prioritize accordingluy17:44
SumitNaiksatamok moving on17:44
SumitNaiksatamsince cgoncalves is here17:45
SumitNaiksatam#topic Traffic steering17:45
*** openstack changes topic to "Traffic steering (Meeting topic: Networking Advanced Services)"17:45
SumitNaiksatam#link https://review.openstack.org/#/c/9247717:45
cgoncalvesnot much to report this week. there is no blockers17:46
SumitNaiksatamcgoncalves: ok good17:46
banixSumitNaiksatam: i think salvatore is essentially suggesting posponing the flavor work to next cycle.17:46
SumitNaiksatamthat said, salvatore has put a comment that he prefers that this be deferred to K17:46
*** marios has joined #openstack-meeting-317:46
cgoncalvesSalvatore -1'ed suggesting postponing it to K cycle17:47
SumitNaiksatambanix: you mean flavors or traffic steering?17:47
banixSumitNaiksatam: i was referring to flavors17:47
*** bmelande has joined #openstack-meeting-317:47
marioso/ sorry am late, am still on another call17:47
*** johnthetubaguy is now known as zz_johnthetubagu17:47
SumitNaiksatambanix: ah ok, i did not catch that comment17:47
*** amitpp has quit IRC17:47
cgoncalvesbanix: so salvatore is suggesting deferring at least three BPs to K? mmm17:47
cgoncalvesTS, flavors and TAPaaS17:48
banixcgoncalves: i think so17:48
SumitNaiksatamwhat does the team here feel about the TS spec, are there any major disagreeents?17:48
SumitNaiksatamcgoncalves actually has the implementation in place for a long time17:49
mariosservice base &  insertion still a possibility for J3 right? Or is that also k17:49
mandeepNo technical concerns that I have heard of.17:49
cgoncalvesregarding TS work, we should not be able to implement OVS support in time. we've internally a working ODL and ODL driver implementation. not sure we could open-source it as of now17:49
banixhe is saying even if this is implemented (wrt flavors) it wont be used in code in this cycle so postpone to next cycle17:50
SumitNaiksatammarios: thats next in the agenda17:50
mariosk thx sorry17:50
LouisFcgoncalves: have you considered the case of using the classifiers to branch to different ports?17:50
SumitNaiksatammarios: np17:50
cgoncalvesSumitNaiksatam: yes. this week we integrated openstack+ODL. I've been testing it today17:50
cgoncalvesLouisF: I did not forget your suggestion, although I've been trying to keep on track internally with the implementation side17:51
SumitNaiksatamany other questions for cgoncalves?17:51
cgoncalvesLouisF: I *promise* I will not overlook your suggestion and will get back to you17:51
LouisFcgoncalves: thx17:52
*** cjellick has quit IRC17:52
cgoncalvesLouisF: sorry for that17:52
*** cjellick has joined #openstack-meeting-317:52
mandeepBut the process is that if we do not approve it in this cycle, we have to go over the approval process all over again for K. That seems like a significant waste of resources.17:52
LouisFcgoncalves: i would like to see that added to the bp17:53
SumitNaiksatammandeep: i believe you are referring to: #link https://wiki.openstack.org/wiki/NeutronJunoProjectPlan17:53
banixmandeep: i think even if we approve, if code doesnt merge we need to get spec approved again. my understanding. need to verify.17:53
cgoncalvesmandeep: if most non-core reviewers keep their +1 votes, it should be fast to get +2s17:53
SumitNaiksatambanix: i think that is correct17:54
cgoncalvesbanix: yeah, my understanding as well17:54
SumitNaiksatamcgoncalves: if only!17:54
banixcgoncalves: is the optimist today!17:54
*** cathy_ has joined #openstack-meeting-317:54
cgoncalveshehe :D17:54
SumitNaiksatamok any other questions for cgoncalves?17:54
mandeepcgoncalves: I am told that it is not how it has typically happened in past17:54
mandeepcgoncalves: :-(17:54
SumitNaiksatam#topic Service base definition and Insertion17:55
*** openstack changes topic to "Service base definition and Insertion (Meeting topic: Networking Advanced Services)"17:55
SumitNaiksatam#link https://review.openstack.org/#/c/9312817:55
SumitNaiksatamboth kanzhe and s3wong are not able to make it today17:55
SumitNaiksatamthe latest update from s3wong was that he had posted a new patchset and there are no outstadanding comments17:56
SumitNaiksatams3wong also has been working on the implementation based on what Kanzhe had done before with the API and DB code17:56
*** cjellick has quit IRC17:57
SumitNaiksatamthere was an action item from last week for s3wong and marios to reachout to the VPNaaS team on the removal of the router_id attribute from the VPNaaS model (in the context of this spec)17:57
SumitNaiksatami think the plan for now is to not remove it17:57
SumitNaiksatammarios: is that right?17:57
SumitNaiksatamat least not being suggested in the spec17:57
SumitNaiksatamand put it on the deprecation path if we make progress with this service insertion model17:58
*** shwetaap has quit IRC17:58
SumitNaiksatamany other questions on this?18:00
mariosSumitNaiksatam: right, sorry, still on a call18:00
mariosSumitNaiksatam: its not a blocker but something to think about18:00
SumitNaiksatammarios: no worries18:00
*** maurosr has quit IRC18:00
SumitNaiksatammarios: yes definitely18:00
SumitNaiksatam#topic Service Chaining18:00
*** openstack changes topic to "Service Chaining (Meeting topic: Networking Advanced Services)"18:00
SumitNaiksatam#link https://review.openstack.org/#/c/9352418:01
SumitNaiksatammandeep: there?18:01
mandeepNo significant updates this week.18:01
SumitNaiksatammandeep: ok, i felt that this was pretty well speced out18:01
SumitNaiksatammandeep: and the only -1 was from me for not having an example18:01
mandeepThere was a request for CLI example, and I will work with songle to add that18:01
SumitNaiksatamsongle -< songole18:02
mandeepSumitNaiksatam: Thanks@18:02
SumitNaiksatami believe he needs to be added to the spec as well?18:02
SumitNaiksatamany questions for mandeep on the service chaining spec?18:02
mandeepYes, the plan was to add both at the same time18:02
LouisFmandeep: what is plan for horizon chnages?18:03
cathy_I have a quesiton on the port, needs Mandeep to confirm18:03
SumitNaiksatamcathy_: go ahead18:03
cathy_So from the replies, it seems the port is the ingress port of the service chain, right?18:03
*** shwetaap has joined #openstack-meeting-318:03
mandeepLouisF: No plan yet on horizon18:03
mandeepcathy_: The port identifies the traffic to which the services apply, it does not require that be the ingress/egress port18:04
mandeepcathy_: That is left to the implementation18:04
*** pballand has quit IRC18:04
*** pgpus has quit IRC18:04
hemanthravimandeep: can we view the chain itself as a service, in which case it could18:05
LouisFmandeep: but is does represent the start of the service chain - right?18:05
*** s3wong has joined #openstack-meeting-318:05
hemanthravihave attachment ports (multiple) like a service18:05
LouisFit18:05
mandeephemanthravi: YEs you could, but then it would have to inherit from serviceBase and that implies service ports etc.18:05
hemanthravimandeep: and those could be ingress/egress18:05
cathy_This classifier will identify the traffic, what do you mean by the port identify the traffic? every service port along the service chain needs to identify the traffic18:05
mandeepLouisF: It can be implemented that way18:05
mandeepcathy_: There is no service port specified, or required, in the chaining API18:06
LouisFmandeep: or the port can be ignored and a gbp redirect action to steer traffic to the service chain18:07
mandeepcathy_: Also, no classifier is specified in the chaining spec18:07
*** maurosr has joined #openstack-meeting-318:07
mandeepLouisF: That would depend on GBP's usage of service chain, that would be covered in GBP spec (still work in progress)18:08
SumitNaiksatammandeep: so all traffic that hits the particular port is subject to the chain?18:08
mandeepSumitNaiksatam: Correct. There is no other classifier or service port18:08
cathy_I am saying that becasue you said the port is for idnetifying the traffic. I think the spec might need to explain more clearly about what that port refers to? Maybe in more concrete examples so people will not misunderstand it since "port" is used in many places and mean differently in different scenarios18:08
mandeepcathy_: In the example, bullet #3 tries to do exactly that18:09
SumitNaiksatammandeep: and you could potentially use a classifier and steering to direct traffic to that port (but thats independent of this spec)?18:09
mandeepSumitNaiksatam: That is probably better handeled in the service spec (for example by TS)18:09
mandeepSumitNaiksatam: And it does not help to recreate that functionality in chaining spec18:10
*** cjellick has joined #openstack-meeting-318:10
SumitNaiksatammandeep: okay, yeah that is how i understood this18:10
SumitNaiksatamcathy_: does that answer your question?18:10
mandeepcathy_: When we add CLI, perhaps that will be clearer?18:11
mandeepcathy_: When we add CLI for the example, perhaps that will be clearer?18:11
cathy_not really. There are so many ports involves in a service chain (I am not talking about the API), it is still not clear which port this "port" in the API refers to?18:11
cathy_OK, let's see the CLI18:11
cathy_Thanks18:11
SumitNaiksatamcathy_: if i understand what mandeep is saying, the use of classifier and steering is complementary to this service chaining spec18:11
mandeepcathy_: The spec has only one type of port - neutron port. There is NO other port in the spec.18:12
mandeepcathy_: Where did you see reference to any other port in the BP?18:12
cathy_But there are multiple neutron ports involved in a service chain, right?18:12
cathy_Each service funciton could have a attachment neutron port, right?18:12
mandeepcathy_: No. Not in this spec. That is an impelentation choice (and one may choose not to implement any service ports)18:13
LouisFmandeep: you mean item 2 on line 14818:13
cathy_I am not talking about the port in BP. I am talking about in general, a service chain consists of a sequence of service function instances and each instance has a port.18:13
hemanthraviodl gbp chaining (https://meetings.opendaylight.org/opendaylight-group-policy/2014/gbp_usecase/opendaylight-group-policy-gbp_usecase.2014-07-14-20.03.html) refers to a in/out terminal for a chain18:13
mandeepcathy_: Do not confuse a specific provider's choice with the API intent18:13
*** igordcard has joined #openstack-meeting-318:14
mandeephemanthravi: This is not refering to ODL chain, that is a different project18:14
hemanthravimandeep: thought the disc could be useful for the model18:14
mandeepLouisF: Let me check the line numbers18:14
mandeephemanthravi: ODL chain is closer to TS implementation of this spec18:15
cgoncalvesthe ODL SFC is a whole new beast :-)18:15
SumitNaiksatammandeep: yeah i believe cgoncalves has mapped that to ODL18:15
cathy_mandeep: looks like people have confusion about the "port" in SC BP. I think more examples could help to make it clear, such as in the scenario that a chain is composed of multiple service instances, then which port does thi "SC BP port" refers to?18:15
hemanthravimandeep: got it18:15
mandeephemanthravi: This is a declarative spec (what I want), not a imperative spec (how to do it) - like TS or ODL are18:15
cgoncalvesSumitNaiksatam: yes. we've extended ODL and added Neutron TS API as well as its implementation18:16
SumitNaiksatami believe the cloud abstraction is different from a network controller abstraction18:16
SumitNaiksatamwhich i believe is being reflected in mandeep’s spec (say as compared to the ODL spec)18:16
mandeepAs in the example, the port refers to a an existing neutron port. No new types of ports are specified18:17
mandeepcathy_: (that was the example that I refered to in bullet #3 above)18:17
SumitNaiksatamokay, cathy perhaps you can put the comment on the spec, i believe mandeep is already planning a new rev to address that (i had a similar comment on the spec)18:17
cathy_SumitNaiksatam: OK, sure, will do18:18
SumitNaiksatamcathy_: thanks18:18
*** pballand has joined #openstack-meeting-318:18
*** wenzhe has joined #openstack-meeting-318:18
SumitNaiksatammoving on18:18
cgoncalvesmandeep: I've not had time to review your latest SC bp patchset, but 'port' is an existing neutron port associated to a e.g. neutron service or a SC entry point for traffic?18:18
SumitNaiksatam#topic Tap as a Service spec18:18
*** openstack changes topic to "Tap as a Service spec (Meeting topic: Networking Advanced Services)"18:18
SumitNaiksatam#undo18:18
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x2648790>18:18
mandeepcgoncalves: Yes, that is exactly right.18:19
vinay_yadhavWe found some opposition form Salvatore Orlando18:19
cgoncalvesmandeep: which one of the two options? :-)18:19
SumitNaiksatamvinay_yadhav: one sec18:19
vinay_yadhavsorry18:19
SumitNaiksatamvinay_yadhav: lets wrap this one18:19
mandeepcgoncalves: And that was what I was trying to explain to cathy_, the port refers to an existing neutron port (as in the example) and not a service port18:19
SumitNaiksatamvinay_yadhav: no worries18:19
SumitNaiksatamcathy_: sound okay?18:20
cgoncalvesmandeep: ok. I will definitly need to to review it to get a better looking of it. thanks18:20
cgoncalvesSumitNaiksatam, vinay_yadhav: sorry for that. please continue18:20
SumitNaiksatamoh it was cgoncalves who had the question18:20
SumitNaiksatamok moving on18:20
SumitNaiksatam#topic Tap as a Service spec18:20
*** openstack changes topic to "Tap as a Service spec (Meeting topic: Networking Advanced Services)"18:20
SumitNaiksatam#link https://review.openstack.org/#/c/9614918:21
SumitNaiksatamvinay_yadhav: sorry, go ahead18:21
vinay_yadhavArmando and Salvatore had some objections to the spec18:21
cathy_SumitNaiksatam: I have the same question as cgoncalves , looks like the "port" in SC is the entry point for traffic?18:21
cathy_anyway I will post the comment again18:22
SumitNaiksatamcathy_: thanks :-)18:22
vinay_yadhavthey basically do not want 'tap' aas but as a port mirror extension18:22
vinay_yadhavbut i guess we have discussed this in the last summit and decided to have it as a service18:22
SumitNaiksatamvinay_yadhav: i dont have any strong feelings on that18:22
SumitNaiksatamis anil_rao here?18:23
vinay_yadhavi guess so18:23
anil_raoTap-aaS is more generic in my opinion because other possible implementations can be done in the future18:23
anil_raofor the first version we are planning to rely on port-mirorring but this doesn't have to be the case for other situations.18:23
*** beyounn has joined #openstack-meeting-318:24
SumitNaiksatamanil_rao: yes, i believe port mirroring in this case is one/first feature18:24
SumitNaiksatamanil_rao: if i understand your comment correctly18:24
mandeepIMO, When you start extending TaaS with de-dup or time-stamps, it really becomes more of a service and less of a port "feature"18:25
anil_raothat is correct.18:25
cgoncalvesvinay_yadhav: in cloud, everything is (or should be) *aaS so I see not much reason in suffixing it with "as a service". 'port mirroring' though potentially be more self-explanatory18:25
vinay_yadhavcorrect18:25
SumitNaiksatami dont see what the big issue is with the name though18:25
cgoncalvesvinay_yadhav: having said that, expect no -1 vote just because of that18:26
SumitNaiksatamthe point is whether this is being offere as a service abstraction or not18:26
mandeepcgoncalves: IMO *aaS is cosmetic matter, I guess we could have called FWaaS as FW and VPNaaS as VPN ...18:26
SumitNaiksatamyou can call it tap as a service or just a tap18:26
SumitNaiksatammandeep: ah, just the point i was trying to make18:26
vinay_yadhavmandeep: agreed18:26
cgoncalvesmandeep: in the end, it's all about fancy names18:27
mandeepcgoncalves: The real question is, is it a "service" with a distinct resource API or "feature" that extends an existing resource18:27
vinay_yadhavalso i want to know the opinion of other reviewers on whether we should have it as service or a extension API18:27
SumitNaiksatammandeep: exactly, and i believe what is being proposed is a service, right?18:28
mandeepvinay_yadhav: Is that "new resource" vs. "extending existing resources" question?18:28
SumitNaiksatamthat was not meant for mandeep specifically, that was a question for vinay_yadhav and anil_rao18:28
vinay_yadhavyes18:28
vinay_yadhavwe are proposing Tap as a resource18:28
*** badveli_ has joined #openstack-meeting-318:28
SumitNaiksatamchanging the name does not change the fact that this is a service interface, if that is the approach we want to take18:28
vinay_yadhavyes18:29
anil_raoThe service abstraction allows more room for growth, so I will recommend that we stay with it.18:29
SumitNaiksatamanil_rao: i tend to agree18:29
vinay_yadhavanil: agreed, that was the idea18:29
SumitNaiksatamanil_rao vinay_yadhav: can you please provide a response on the review to that effect18:29
anil_raoSure will do18:29
SumitNaiksatamand we can hopefully move on from there18:29
vinay_yadhavyes we will18:29
SumitNaiksatamvinay_yadhav anil_rao: thanks18:30
SumitNaiksatamok we have hit our time18:30
SumitNaiksatam#topic open discussion18:30
*** openstack changes topic to "open discussion (Meeting topic: Networking Advanced Services)"18:30
mandeepanil_rao: Specifically handling something like (distributed) de-dup is probably not representable as an extension to existing resources18:30
SumitNaiksatamif there is nothing else, we can wrap up here18:30
SumitNaiksatammandeep: agree18:30
anil_raomandeep: exactly.18:30
SumitNaiksatamok lets wrap it up18:30
SumitNaiksatamthanks for all your reviews and work on the patches18:30
banixthanks18:31
SumitNaiksatamlets keep up the momentum and hopefully we can get the specs approved in time18:31
SumitNaiksatamthanks all, bye!18:31
cgoncalvescya!18:31
anil_raoBye!18:31
*** hareeshpc has quit IRC18:31
mandeepbye18:31
SumitNaiksatam#endmeeting18:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:31
openstackMeeting ended Wed Jul 16 18:31:39 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:31
pcm_bye18:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-07-16-17.31.html18:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-07-16-17.31.txt18:31
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-07-16-17.31.log.html18:31
vinay_yadhavbye18:31
*** mandeep has left #openstack-meeting-318:31
ivar-lazzarobye18:31
SumitNaiksatamhi FWaaS team!18:31
SridarKHi All18:32
SumitNaiksatamSridarK yisun garyduan badveli_ natarajk: there18:32
SumitNaiksatam?18:32
natarajkhi18:32
*** hemanthravi has quit IRC18:32
* pcm_ lurking, as usual18:32
SumitNaiksatampcm_: hi thanks for joining as well18:32
badveli_yes18:32
SumitNaiksatamlets get started18:32
pcm_nothing better to do :)18:32
SumitNaiksatam#startmeeting Networking FWaaS18:32
openstackMeeting started Wed Jul 16 18:32:56 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:32
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:32
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:32
openstackThe meeting name has been set to 'networking_fwaas'18:33
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/FWaaS18:33
SumitNaiksatam#topic Action Item follow up18:33
*** openstack changes topic to "Action Item follow up (Meeting topic: Networking FWaaS)"18:33
SumitNaiksatamthe pending action item was to set up a meeting with the DVR folks18:33
*** wenzhe has quit IRC18:33
*** Swami has quit IRC18:33
SumitNaiksatamthanks SridarK  for leading on this, i believe we had two meetings with the DVR team, and we are making good progress18:34
beyounnhi18:34
SumitNaiksatamwe will get to that specific topic in the DVR related update18:34
SridarKSumitNaiksatam: no worries - spec is out - and thanks to Yi & badveli_ as well18:34
SumitNaiksatamlets jump to that18:34
SumitNaiksatam#topic DVR discussion18:34
*** openstack changes topic to "DVR discussion (Meeting topic: Networking FWaaS)"18:34
*** regXboi has left #openstack-meeting-318:35
SumitNaiksatam#link https://review.openstack.org/10622518:35
SumitNaiksatamthanks SridarK badveli_ and yisun for getting posted18:35
*** vinay_yadhav has quit IRC18:35
*** anil_rao has quit IRC18:35
*** aihuaedwardli_ has joined #openstack-meeting-318:35
SridarKSumitNaiksatam: will address ur comment and reflect the minor changes suggested by DVR team18:35
SumitNaiksatamthanks to swami as well for his support and being the liason on the DVR side18:35
SumitNaiksatamSridarK: great18:36
SumitNaiksatamanother procedural matter, we need to make sure that this gets discussed in the L3 team meeting as well18:36
SumitNaiksatamthe one that is tomorrow18:36
SumitNaiksatami will send out an email18:36
SumitNaiksatambeyounn: you will be attending that meeting?18:36
beyounnI have a conflict meeting18:37
SumitNaiksatamok, SridarK badveli_?18:37
beyounnWed morning 8:00 is not good for me18:37
SridarKSumitNaiksatam: i can attend18:37
badveli_yes18:37
SumitNaiksatamSridarK badveli_: nice18:37
badveli_i will attend18:37
SumitNaiksatam#action SumitNaiksatam to inform Swami to bring up the FWaaS support proposal in the L3 team meeting18:38
beyounnbadveli_: you can also help on the implementation, right?18:38
badveli_yes18:38
*** yzuo_ has joined #openstack-meeting-318:38
SumitNaiksatambadveli_: nice18:38
SumitNaiksatamSridarK: can you summarize today morning’s discussion for everyone’s benefit here?18:38
SumitNaiksatamSridarK: sorry to put you on the spot18:39
SridarKSumitNaiksatam: sure18:39
SridarKWe will cover N - S usecase18:39
SumitNaiksatami dont think yapeng is here18:39
SridarKWe will not break E -W usecases18:39
SridarKTarget FW rules on the SNAT namespace on network Node18:39
SridarKTarget FW rules on FIP/IR namespace on the Compute Nodes18:40
SridarKWe will not try to optimize FW rules for distribution18:40
SridarKFocus on correctness18:41
SridarKok that is the rough summary18:41
SumitNaiksatamSridarK: so for FIP, we decided to apply in the IR namespace, right?18:42
SridarKSumitNaiksatam: i think Swami's suggestion was to keep that open but yes we will target IR namespace18:42
SridarKSumitNaiksatam: mainly for the purposes of the spec but initial attempt is to get it on the IR NS with a tag for traffic on the interface associated with the FIP NS18:44
SumitNaiksatamSridarK: wasnt the suggestion to keep the specifics of the interface names open?18:44
SridarKSumitNaiksatam: that as well18:44
SumitNaiksatamSridarK: but we agreed on the IR namespace18:44
SumitNaiksatamSridarK: ah ok18:44
SumitNaiksatamis garyduan here?18:44
SridarKSumitNaiksatam: yes but just for now to name it as FIP/IR NS to give us some options just in case ...18:45
beyounnGary is in meeting until now18:45
SumitNaiksatamSridarK: okay18:46
beyounnSorry, he is still in meeting18:46
SumitNaiksatambeyounn: i wanted to check with garyduan if he is comfortable with the approach we are taking18:46
SumitNaiksatamnatarajk: have you looked at the proposal?18:46
natarajkyes18:47
beyounnSumit: I had a quick chat with him, he is fine18:47
natarajkI have been reviewing the DVR FWaas spec udpate18:47
SumitNaiksatambeyounn natarajk: ok18:47
SumitNaiksatamthere was also a suggestion from swami for a f2f meeting18:48
SumitNaiksatami believe after july 25th18:48
SumitNaiksatamlets discuss that offline and decide on date18:48
SridarKSumitNaiksatam: +1 - i think that will be useful18:49
SumitNaiksatamso on this topic, our first focus has to be get the spec approved18:49
SumitNaiksatamSridarK badveli_: perhaps good to attempt a DVR installation with the links that were sent out earlier18:50
badveli_fine sumit18:51
SridarKSumitNaiksatam: Will get the updates in and reach out to FWaaS, DVR team and cores for review by late afternoon18:51
SridarKSumitNaiksatam: will try that - badveli_ and i can sync up on this18:51
SumitNaiksatamSridarK badveli_: thanks!18:52
SumitNaiksatamis there anything else we need to discuss on this?18:52
SridarKno worries, i think i am good18:52
SumitNaiksatamSridarK: thanks18:52
*** yamamoto has quit IRC18:52
SumitNaiksatam#topic Service Objects18:52
badveli_we need to figure out the fip interface18:52
*** openstack changes topic to "Service Objects (Meeting topic: Networking FWaaS)"18:52
*** mwagner_lap has quit IRC18:53
badveli_sorry, will send out a mail on fip interface after testing18:53
badveli_please continue18:53
SumitNaiksatam#link https://review.openstack.org/9413318:54
SumitNaiksatambeyounn: there?18:54
badveli_yes, he is in a meeting18:54
SumitNaiksatamokay, i have +2’ed the patch18:54
badveli_thanks sumit18:54
SumitNaiksatamwe need to reach out to nachi, kyle and akihiro18:55
beyounnSumit: Gary sent eamil to akihiro. I will reach out nachi and kyle after my current meeting18:55
SumitNaiksatambeyounn: nice18:55
SumitNaiksatambeyounn: any blockers for you?18:55
beyounnhop, I'm real good now18:56
beyounnAnd thanks everyone for the helps !!!!!!18:56
*** yamamoto has joined #openstack-meeting-318:57
SumitNaiksatamok moving on18:57
SumitNaiksatam#topic flavors support18:57
*** openstack changes topic to "flavors support (Meeting topic: Networking FWaaS)"18:57
SumitNaiksatami wanted to garyduan’s opinion on this18:57
SumitNaiksatamsalvatore has asked a question on the flavor’s spec whether it is feasible for implementation in the juno time frame if the spec is approved18:58
SumitNaiksatamof course this depends on what gets approved18:58
SridarKSumitNaiksatam: by the looks of the discussion i wonder if we will be able to move to this18:58
SumitNaiksatamSridarK: okay18:58
SumitNaiksatambut i would like garyduan to respond to that question in the review18:59
SridarKeven if it gets approved - our time line will be quite tight i guess18:59
SumitNaiksatamSridarK: however garyduan really wanted this to land to enable vendor driver support19:00
SridarKSumitNaiksatam: but if it gets delayed we will be asking the same question in K19:00
SridarKSumitNaiksatam: my fear19:00
SumitNaiksatambeyounn badveli_: can you please convey to garyduan my earlier request?19:00
*** seizadi has joined #openstack-meeting-319:00
badveli_yes i will talk to him19:01
*** yamamoto has quit IRC19:01
SumitNaiksatambadveli_: ok thanks this has to be done today19:01
badveli_ok, will talk to him19:01
SumitNaiksatam#action garyduan to respond to salvatore’s question on implementation feasiblity in #link https://review.openstack.org/#/c/102723/19:02
SumitNaiksatam#topic Bugs19:02
*** openstack changes topic to "Bugs (Meeting topic: Networking FWaaS)"19:02
garyduanHi, I am back. Sorry about that.19:03
SridarKenikanorov_: has assigned one of the new bugs to himself19:03
SumitNaiksatamSridarK: link?19:03
SumitNaiksatamgaryduan: hopefully you can scroll to the discussion earlier on flavors19:04
SridarK#link https://bugs.launchpad.net/neutron/+bug/134073519:04
SridarKanother issue on tempest: #link https://bugs.launchpad.net/tempest/+bug/1342516 - review is out19:05
SridarKthose i believe were the new bugs for this week19:05
SumitNaiksatami dont think we can do anything about #link https://bugs.launchpad.net/neutron/+bug/134073519:05
SumitNaiksatamsince we are at the mercy of the l3 agent kicking in for the firewall deletion19:05
SridarKyes19:06
SridarKanother old one:19:06
SridarK#link https://bugs.launchpad.net/neutron/+bug/131085719:06
SumitNaiksatamSridarK: enikanorov_ might have assigned it to himself for triaging purposes19:06
SridarKSumitNaiksatam: yes i think so too19:06
SumitNaiksatamSridarK: he probably does not intend to implement it19:06
SumitNaiksatamSridarK: i will comment on the bug report19:06
SridarKok cool19:07
SridarK#link https://review.openstack.org/#/c/90575/ for #link https://bugs.launchpad.net/neutron/+bug/131085719:07
badveli_sridark info  how do you look at the bugs assigned in fwaas, is there any link that you have created19:07
SridarKi think we are good19:07
SridarKon that needs mark to chime in on his comment19:07
badveli_sridark or are we search it19:08
SumitNaiksatambadveli_: i have posted a link on the wiki19:08
badveli_sumit:new bugs filed that are coming19:08
SumitNaiksatambadveli_: the link is #link https://bugs.launchpad.net/openstack/+bugs?field.searchtext=fwaas&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package19:08
SumitNaiksatamthis gives everything related to FWaaS across all the projects19:08
badveli_thanks sumit19:08
SumitNaiksatamSridarK: on https://bugs.launchpad.net/tempest/+bug/134251619:09
SumitNaiksatamits probably not specific to fwaas right?19:09
SridarKnothing really specific to us19:09
SridarKyes19:09
SridarKjust lands up on our radar19:10
SridarKbecause of fwaas string19:10
SumitNaiksatamits probably just the case that in this example it shows up with the fwaas test19:10
SumitNaiksatamyeah19:10
SumitNaiksatamSridarK: so for #link https://review.openstack.org/#/c/90575/ mark’s comment has been responded to, right?19:12
SridarKSumitNaiksatam: yes19:12
SumitNaiksatamthankfully the -2 is not there any more!19:12
SridarKthe assignee has fixed it19:12
SridarKand Mark took out his -219:12
SridarKand now there is a -119:13
SumitNaiksatamwow, i think that must be a first!19:13
SridarKbut this looks good19:13
SridarK:-)19:13
SumitNaiksatamwe are blessed!19:13
SridarKI will ping SridharG (the submitter) to reach out19:13
SumitNaiksatamSridarK: thanks much19:13
SridarKno worries19:14
SumitNaiksatamanything else on the bugs radar?19:14
SridarKSumitNaiksatam: nothing major to report19:14
SumitNaiksatamSridarK: thanks19:14
SridarKnp at all19:14
SumitNaiksatam#topic Vendor Blueprints19:15
*** openstack changes topic to "Vendor Blueprints (Meeting topic: Networking FWaaS)"19:15
SumitNaiksatamSridarK natarajk: can you add your blueprint specs here: https://wiki.openstack.org/wiki/Meetings/FWaaS#Blueprint_Tracking19:15
natarajksure19:16
SridarKSumitNaiksatam: will do19:16
SumitNaiksatamnatarajk SridarK: thanks19:16
SumitNaiksatamSridarK: link to your bp?19:16
SridarKSumitNaiksatam: #link #link https://review.openstack.org/#/c/105373/19:16
SumitNaiksatamSridarK: thanks19:16
SumitNaiksatamSridarK: so we have a dependency here on Bob’s patch?19:16
SridarKSumitNaiksatam: also the dependency that i was waiting on just got approved 2 mins ago19:16
SumitNaiksatamSridarK: oh good19:17
SumitNaiksatamSridarK: i can look at it then19:17
SridarKSumitNaiksatam:  so we are good on the dependency - i will respond to Kyle's -1 and hopefully we will get this moving19:17
SridarKSumitNaiksatam: thanks much for ur help on this19:17
SumitNaiksatamSridarK: actually kyle removed his -119:17
SridarKaah great19:17
SridarKok i just seer that too19:18
SridarK*see19:18
SumitNaiksatamnatarajk: link to your blueprint spec?19:18
SridarKwe are on real time19:18
natarajkSumit, i am still going through l3 plugin review19:19
*** otherwiseguy has joined #openstack-meeting-319:19
SumitNaiksatamnatarajk: ah ok19:19
natarajkI'll submit the spec, but i am also waiting for flavors framework19:19
SumitNaiksatamnatarajk: ok19:19
SumitNaiksatamnatarajk: i believe its too late now to submit a new blueprint spec19:20
SumitNaiksatamnatarajk: that dealine was on july 10th19:20
natarajkSumit, my focus has been to get the l3 spec and code approved19:20
SumitNaiksatamthe spec approval deadline is July 20th19:20
SumitNaiksatamnatarajk: sure, sounds like the right priority19:20
*** LouisF has quit IRC19:21
SumitNaiksatami was earlier misreporting the SAD to be july 17th19:21
SumitNaiksatamthat means that we have a couple of more days than we expected19:21
SumitNaiksatamso its a good thing19:21
SumitNaiksatamanything else on the vendor blueprints19:22
SumitNaiksatam?19:22
natarajkif l3 code get approved, i can work on firewall plugin (if vendor extensions or flavor is accepted by the community)19:22
SumitNaiksatamnatarajk: sure, that i believe will be for K release then19:22
natarajkSumit, yes19:23
SumitNaiksatamnatarajk: good19:23
SumitNaiksatam#topic open discussion19:24
*** openstack changes topic to "open discussion (Meeting topic: Networking FWaaS)"19:24
SridarKSumitNaiksatam: will also reach out to s3wong on plans for service insertion19:24
SumitNaiksatamSridarK: yeah sure, thanks19:24
SridarKSumitNaiksatam: will be great if we can get that in19:25
SumitNaiksatamSridarK: yeah! its very frustrating19:25
*** tzumainn has joined #openstack-meeting-319:25
*** tzumainn has left #openstack-meeting-319:25
SridarKSumitNaiksatam: the third time is a charm so lets hope that works :-(19:25
SumitNaiksatamSridarK: yeah!19:26
SumitNaiksatamgaryduan: so you will respond on the flavors review?19:26
garyduanyes19:27
garyduanI will add my comment to the spec19:27
SumitNaiksatamgaryduan: thanks19:28
SumitNaiksatamokay, if nothing else, lets call it a wrap19:28
SumitNaiksatamthanks everynone for attending, bye!19:28
SridarKthanks19:28
SridarKbye19:28
natarajkbye19:28
SumitNaiksatamnot to forget that we have immediate work to do on the DVR front19:28
SumitNaiksatam#endmeeting19:28
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:28
SridarKSumitNaiksatam: yes19:28
openstackMeeting ended Wed Jul 16 19:28:55 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-07-16-18.32.html19:28
garyduanthanks19:28
*** natarajk has left #openstack-meeting-319:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-07-16-18.32.txt19:29
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-07-16-18.32.log.html19:29
garyduanbye19:29
SumitNaiksatamSridarK: thanks19:29
SridarKnp at all thanks19:29
*** pcm_ has left #openstack-meeting-319:29
*** chuckC has joined #openstack-meeting-319:38
*** seizadi has quit IRC19:41
*** yamamoto has joined #openstack-meeting-319:42
*** chuckC has quit IRC19:44
*** ivar-lazzaro1 has joined #openstack-meeting-319:46
*** yamamoto has quit IRC19:47
yzuo_Hello. Does anyone know if there is a way to include a Django application in Horizon without modifying the settings.py?19:49
*** ivar-lazzaro has quit IRC19:50
*** jpomero has joined #openstack-meeting-320:08
*** banix has quit IRC20:14
*** banix has joined #openstack-meeting-320:16
*** cjellick_ has joined #openstack-meeting-320:22
*** yamahata has joined #openstack-meeting-320:23
*** cjellick has quit IRC20:25
*** chuckC has joined #openstack-meeting-320:35
*** aihuaedwardli_ has quit IRC20:36
*** thomasem has quit IRC20:40
*** peristeri has quit IRC20:40
*** yamamoto has joined #openstack-meeting-320:42
*** shwetaap has quit IRC20:43
*** yamamoto has quit IRC20:47
*** SumitNaiksatam has quit IRC20:54
*** chuckC has quit IRC20:56
*** mwagner_lap has joined #openstack-meeting-320:58
*** Sukhdev has joined #openstack-meeting-321:06
*** lblanchard has quit IRC21:07
*** SridarK has quit IRC21:09
*** SumitNaiksatam has joined #openstack-meeting-321:09
*** jpomero has quit IRC21:12
*** pballand has quit IRC21:15
*** seizadi has joined #openstack-meeting-321:23
*** seizadi has quit IRC21:30
*** shwetaap has joined #openstack-meeting-321:32
*** thangp has quit IRC21:35
*** thomasem has joined #openstack-meeting-321:42
*** yamamoto has joined #openstack-meeting-321:42
*** pgpus has joined #openstack-meeting-321:46
*** shwetaap has quit IRC21:46
*** julim has quit IRC21:46
*** yamamoto has quit IRC21:47
*** igordcard has quit IRC21:51
*** ivar-lazzaro1 has quit IRC21:51
*** otherwiseguy has quit IRC21:51
*** otherwiseguy has joined #openstack-meeting-321:55
*** carl_baldwin has quit IRC22:00
*** david-lyle has quit IRC22:00
*** carl_baldwin has joined #openstack-meeting-322:00
*** david-lyle has joined #openstack-meeting-322:01
*** MaxV has quit IRC22:02
*** pballand has joined #openstack-meeting-322:03
*** shwetaap has joined #openstack-meeting-322:13
*** shwetaap has quit IRC22:17
*** jgrimm has quit IRC22:25
*** pgpus has quit IRC22:26
*** otherwiseguy has quit IRC22:34
*** beyounn has quit IRC22:38
*** yamamoto has joined #openstack-meeting-322:42
*** ivar-lazzaro has joined #openstack-meeting-322:42
*** beyounn has joined #openstack-meeting-322:45
*** cuddyt has joined #openstack-meeting-322:45
*** yamamoto has quit IRC22:47
*** cuddyt has quit IRC22:48
*** pballand has quit IRC22:48
*** thomasem has quit IRC22:53
*** thomasem has joined #openstack-meeting-322:53
*** thomasem has quit IRC22:57
*** thomasem has joined #openstack-meeting-323:03
*** yamahata has quit IRC23:03
*** beyounn has quit IRC23:04
*** carl_baldwin has quit IRC23:05
*** Sukhdev has quit IRC23:06
*** thomasem has quit IRC23:07
*** beyounn has joined #openstack-meeting-323:09
*** badveli_ has quit IRC23:12
*** seizadi has joined #openstack-meeting-323:14
*** lcheng has joined #openstack-meeting-323:14
*** gduan has joined #openstack-meeting-323:16
*** garyduan has quit IRC23:16
*** bmelande has quit IRC23:17
*** david-lyle has quit IRC23:19
*** pballand has joined #openstack-meeting-323:30
*** s3wong has quit IRC23:38
*** yamamoto has joined #openstack-meeting-323:42
*** pballand has quit IRC23:43
*** yamamoto has quit IRC23:44
*** yamamoto has joined #openstack-meeting-323:44
*** yamamoto has quit IRC23:49
*** cathy_ has quit IRC23:51
*** pgpus has joined #openstack-meeting-323:58

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