Wednesday, 2014-07-30

*** sarob_ has joined #openstack-meeting-300:01
*** jpomero has joined #openstack-meeting-300:02
*** sarob_ has quit IRC00:05
*** jaypipes has quit IRC00:06
*** markmcclain has quit IRC00:06
*** lcheng has quit IRC00:09
*** banix has joined #openstack-meeting-300:13
*** banix has quit IRC00:21
*** yamahata_ has joined #openstack-meeting-300:22
*** julim has quit IRC00:23
*** sarob_ has joined #openstack-meeting-300:26
*** asahlin_ has quit IRC00:27
*** asahlin_ has joined #openstack-meeting-300:27
*** sarob_ has quit IRC00:30
*** yamahata_ has quit IRC00:31
*** yamahata_ has joined #openstack-meeting-300:31
*** armax has quit IRC00:38
*** banix has joined #openstack-meeting-300:44
*** sarob_ has joined #openstack-meeting-300:46
*** banix has quit IRC00:46
*** sarob_ has quit IRC00:50
*** banix has joined #openstack-meeting-300:50
*** dhellmann is now known as dhellmann_00:53
*** hurgleburgler has quit IRC00:55
*** carl_baldwin has quit IRC01:06
*** xuhanp has joined #openstack-meeting-301:07
*** beagles has quit IRC01:21
*** yamahata_ has quit IRC01:26
*** beagles has joined #openstack-meeting-301:26
*** yamahata_ has joined #openstack-meeting-301:27
*** stanzgy has joined #openstack-meeting-301:34
*** Sukhdev has quit IRC01:35
*** rudrarug_ has joined #openstack-meeting-301:37
*** rudrarugge has quit IRC01:40
*** rudrarug_ has quit IRC01:42
*** tomoe_ has quit IRC01:42
*** baohua has joined #openstack-meeting-301:44
*** eghobo has quit IRC02:04
*** armax has joined #openstack-meeting-302:04
*** sarob_ has joined #openstack-meeting-302:13
*** sarob_ has quit IRC02:18
*** armax has quit IRC02:20
*** briancurtin has quit IRC02:24
*** tomoe_ has joined #openstack-meeting-302:26
*** sankarshan_away is now known as sankarshan02:32
*** sankarshan is now known as sankarshan_away02:32
*** yamahata has quit IRC02:37
*** sarob_ has joined #openstack-meeting-302:46
*** otherwiseguy has joined #openstack-meeting-302:47
*** yamamoto_ has joined #openstack-meeting-302:48
*** sarob_ has quit IRC02:50
*** HenryG is now known as HenryG_afk02:53
*** briancurtin has joined #openstack-meeting-302:55
*** SumitNaiksatam has joined #openstack-meeting-302:55
*** briancurtin2 has joined #openstack-meeting-302:57
*** briancurtin has quit IRC03:00
*** briancurtin2 has quit IRC03:02
*** armax has joined #openstack-meeting-303:02
*** jamielennox is now known as jamielennox|away03:05
*** yamamot__ has joined #openstack-meeting-303:17
*** xuhanp has quit IRC03:19
*** carl_baldwin has joined #openstack-meeting-303:19
*** yamamoto_ has quit IRC03:20
*** carl_baldwin has quit IRC03:24
*** eghobo has joined #openstack-meeting-303:24
*** rfolco has quit IRC03:25
*** carl_baldwin has joined #openstack-meeting-303:29
*** terryw has joined #openstack-meeting-303:38
*** otherwiseguy has quit IRC03:40
*** armax has quit IRC03:48
*** terryw has quit IRC03:49
*** briancurtin has joined #openstack-meeting-303:51
*** armax has joined #openstack-meeting-303:55
*** briancurtin has quit IRC03:56
*** armax has quit IRC03:56
*** amotoki has joined #openstack-meeting-304:14
*** eghobo has quit IRC04:15
*** Longgeek has joined #openstack-meeting-304:16
*** asahlin_ has quit IRC04:16
*** asahlin_ has joined #openstack-meeting-304:17
*** Longgeek has quit IRC04:18
*** Longgeek has joined #openstack-meeting-304:18
*** armax has joined #openstack-meeting-304:18
*** Longgeek has quit IRC04:19
*** Longgeek has joined #openstack-meeting-304:19
*** banix has quit IRC04:20
*** asahlin_ has quit IRC04:25
*** asahlin_ has joined #openstack-meeting-304:25
*** otherwiseguy has joined #openstack-meeting-304:27
*** terryw has joined #openstack-meeting-304:35
*** eghobo has joined #openstack-meeting-304:36
*** eghobo has quit IRC04:36
*** eghobo has joined #openstack-meeting-304:36
*** otherwiseguy has quit IRC04:37
*** nelsnelson has quit IRC04:42
*** terryw has quit IRC04:44
*** briancurtin has joined #openstack-meeting-304:46
*** briancurtin has quit IRC04:50
*** otherwiseguy has joined #openstack-meeting-305:14
*** jcoufal has joined #openstack-meeting-305:28
*** jtomasek has joined #openstack-meeting-305:33
*** sarob_ has joined #openstack-meeting-305:36
*** tmazur has joined #openstack-meeting-305:37
*** sarob__ has joined #openstack-meeting-305:38
*** briancurtin has joined #openstack-meeting-305:40
*** sarob_ has quit IRC05:41
*** sarob__ has quit IRC05:42
*** briancurtin has quit IRC05:44
*** terryw has joined #openstack-meeting-306:02
*** otherwiseguy has quit IRC06:02
*** carl_baldwin has quit IRC06:06
*** tmazur has quit IRC06:13
*** tmazur has joined #openstack-meeting-306:26
*** terryw has quit IRC06:26
*** mrunge has joined #openstack-meeting-306:29
*** briancurtin has joined #openstack-meeting-306:30
*** briancurtin has quit IRC06:33
*** briancurtin has joined #openstack-meeting-306:33
*** briancurtin has joined #openstack-meeting-306:33
*** sarob_ has joined #openstack-meeting-306:36
*** briancurtin has quit IRC06:38
*** sarob_ has quit IRC06:41
*** eghobo has quit IRC06:56
*** iovadia has joined #openstack-meeting-306:59
*** iovadia has joined #openstack-meeting-306:59
*** iovadia has quit IRC07:04
*** armax has quit IRC07:04
*** asahlin_ has quit IRC07:07
*** asahlin_ has joined #openstack-meeting-307:08
*** sarob_ has joined #openstack-meeting-307:12
*** sarob_ has quit IRC07:17
*** iovadia has joined #openstack-meeting-307:20
*** sarob_ has joined #openstack-meeting-307:36
*** sarob_ has quit IRC07:41
*** MaxV has joined #openstack-meeting-307:55
*** asahlin_ has quit IRC07:56
*** yamamot__ has quit IRC07:56
*** asahlin_ has joined #openstack-meeting-307:57
*** safchain has joined #openstack-meeting-308:17
*** yamamoto_ has joined #openstack-meeting-308:18
*** igordcard has joined #openstack-meeting-308:18
*** sarob_ has joined #openstack-meeting-308:36
*** sarob_ has quit IRC08:41
*** claudiub has joined #openstack-meeting-308:44
*** baohua has quit IRC09:00
*** baohua has joined #openstack-meeting-309:01
*** iovadia1 has joined #openstack-meeting-309:04
*** iovadia has quit IRC09:06
*** asahlin_ has quit IRC09:12
*** asahlin_ has joined #openstack-meeting-309:12
*** asahlin_ has quit IRC09:13
*** asahlin_ has joined #openstack-meeting-309:13
*** iovadia1 has quit IRC09:20
*** iovadia has joined #openstack-meeting-309:20
*** baohua has quit IRC09:22
*** Longgeek_ has joined #openstack-meeting-309:31
*** claudiub has quit IRC09:33
*** Longgeek has quit IRC09:34
*** sarob_ has joined #openstack-meeting-309:36
*** sarob_ has quit IRC09:41
*** mikal_ has joined #openstack-meeting-309:44
*** cgoncalv1s has joined #openstack-meeting-309:44
*** stanzgy has quit IRC09:44
*** mikal has quit IRC09:44
*** dansmith has quit IRC09:44
*** sdague has quit IRC09:44
*** edhall has quit IRC09:44
*** cgoncalves has quit IRC09:44
*** sc68cal has quit IRC09:44
*** edhall has joined #openstack-meeting-309:44
*** dansmith has joined #openstack-meeting-309:44
*** sc68cal has joined #openstack-meeting-309:45
*** sdague has joined #openstack-meeting-309:45
*** dansmith is now known as Guest1715009:45
*** stanzgy has joined #openstack-meeting-309:49
*** asahlin has joined #openstack-meeting-309:54
*** asahlin_ has quit IRC09:54
*** asahlin has quit IRC10:22
*** asahlin has joined #openstack-meeting-310:23
*** igordcard has quit IRC10:27
*** amotoki has quit IRC10:29
*** sarob_ has joined #openstack-meeting-310:36
*** sarob_ has quit IRC10:41
*** asahlin has quit IRC11:00
*** asahlin has joined #openstack-meeting-311:00
*** asahlin has quit IRC11:01
*** asahlin has joined #openstack-meeting-311:01
*** igordcard has joined #openstack-meeting-311:10
*** asahlin has quit IRC11:12
*** asahlin has joined #openstack-meeting-311:12
*** yamahata_ has quit IRC11:13
*** MaxV has quit IRC11:24
*** MaxV has joined #openstack-meeting-311:24
*** MaxV has quit IRC11:29
*** sarob_ has joined #openstack-meeting-311:36
*** sarob_ has quit IRC11:41
*** MaxV has joined #openstack-meeting-311:51
*** mrunge has quit IRC12:14
*** rfolco has joined #openstack-meeting-312:14
*** xuhanp has joined #openstack-meeting-312:18
*** HenryG_afk is now known as HenryG12:23
*** cjellick has joined #openstack-meeting-312:24
*** xuhanp has quit IRC12:35
*** sarob_ has joined #openstack-meeting-312:36
*** sarob_ has quit IRC12:41
*** igordcard has quit IRC12:41
*** lblanchard has joined #openstack-meeting-312:45
*** briancurtin has joined #openstack-meeting-312:47
*** briancurtin has joined #openstack-meeting-312:47
*** harrisonkelly has joined #openstack-meeting-312:51
*** mrunge has joined #openstack-meeting-312:52
*** stanzgy has quit IRC12:52
*** igordcard has joined #openstack-meeting-312:53
*** nelsnelson has joined #openstack-meeting-312:54
*** briancurtin has quit IRC13:00
*** briancurtin has joined #openstack-meeting-313:00
*** tomoe_ has quit IRC13:03
*** mrunge has quit IRC13:05
*** briancurtin has quit IRC13:05
*** alexpilotti has joined #openstack-meeting-313:13
*** igordcard has quit IRC13:15
*** alexpilotti_ has joined #openstack-meeting-313:19
*** alexpilotti has quit IRC13:19
*** alexpilotti_ is now known as alexpilotti13:19
*** yamahata has joined #openstack-meeting-313:22
*** jtomasek has quit IRC13:25
*** peristeri has joined #openstack-meeting-313:26
*** thomasem has joined #openstack-meeting-313:27
*** banix has joined #openstack-meeting-313:31
*** mwagner_lap has joined #openstack-meeting-313:33
*** sarob_ has joined #openstack-meeting-313:36
*** thomasem_ has joined #openstack-meeting-313:40
*** thomasem has quit IRC13:40
*** thomasem_ has quit IRC13:40
*** sarob_ has quit IRC13:41
*** thomasem has joined #openstack-meeting-313:42
*** thomasem has quit IRC13:42
*** thomasem has joined #openstack-meeting-313:43
*** thomasem has quit IRC13:43
*** thomasem has joined #openstack-meeting-313:44
*** armax has joined #openstack-meeting-313:44
*** thomasem has quit IRC13:47
*** thomasem has joined #openstack-meeting-313:47
*** amotoki has joined #openstack-meeting-313:52
*** thangp has joined #openstack-meeting-313:54
*** rohit404 has joined #openstack-meeting-314:06
*** igordcard has joined #openstack-meeting-314:08
*** eghobo has joined #openstack-meeting-314:11
*** thomasem has quit IRC14:11
*** asahlin has quit IRC14:15
*** asahlin_ has joined #openstack-meeting-314:15
*** cloudtoad has quit IRC14:15
*** thomasem has joined #openstack-meeting-314:19
*** eghobo has quit IRC14:21
*** jlibosva has joined #openstack-meeting-314:25
*** otherwiseguy has joined #openstack-meeting-314:26
mesteryHi, for anyone who's here for the parity meeting, I was wondering if we should cancel it given a good # of folks are at the nova mid-cycle discussing parity in person.14:29
mesteryobondarev: ^^^14:30
mesteryobondarev: Of course, you and I could chat if you want, so let me know ;)14:30
obondarevI don't mind skipping14:30
obondarevmestery: thanks :)14:31
mesteryobondarev: OK, lets cancel.14:31
mesteryobondarev: I'll send email now.14:31
obondarevmestery: ok14:31
*** jlibosva has left #openstack-meeting-314:31
*** Swami has joined #openstack-meeting-314:32
*** sarob_ has joined #openstack-meeting-314:36
*** sarob_ has quit IRC14:41
*** tomoe_ has joined #openstack-meeting-314:49
*** mfer has joined #openstack-meeting-314:52
*** thomasem has quit IRC14:52
*** rohit404 has quit IRC14:53
*** rohit404 has joined #openstack-meeting-314:54
*** briancurtin has joined #openstack-meeting-314:56
*** briancurtin has joined #openstack-meeting-314:56
*** otherwiseguy has quit IRC14:57
*** Swami has left #openstack-meeting-314:58
*** carl_baldwin has joined #openstack-meeting-315:02
*** tmazur has quit IRC15:04
*** MarkAtwood has joined #openstack-meeting-315:12
*** david-lyle has joined #openstack-meeting-315:14
*** iovadia has quit IRC15:14
*** thomasem has joined #openstack-meeting-315:16
*** thomasem has quit IRC15:20
*** pballand has joined #openstack-meeting-315:21
*** mfer has quit IRC15:21
*** david-lyle has quit IRC15:22
*** david-lyle has joined #openstack-meeting-315:23
*** hurgleburgler has joined #openstack-meeting-315:29
*** Sukhdev has joined #openstack-meeting-315:34
*** briancurtin has quit IRC15:42
*** shakamunyi has joined #openstack-meeting-315:42
*** shakamunyi has quit IRC15:42
*** briancurtin has joined #openstack-meeting-315:42
*** briancurtin has joined #openstack-meeting-315:42
*** shakamunyi has joined #openstack-meeting-315:43
*** shakamunyi has quit IRC15:43
*** otherwiseguy has joined #openstack-meeting-315:43
*** trinaths has joined #openstack-meeting-315:47
*** briancurtin has left #openstack-meeting-315:51
*** harrisonkelly has quit IRC15:52
*** shakamunyi has joined #openstack-meeting-315:53
*** shakamunyi has quit IRC15:53
*** shakamunyi has joined #openstack-meeting-315:54
*** shakamunyi has quit IRC15:54
*** mfer has joined #openstack-meeting-315:54
*** nkubota_ has joined #openstack-meeting-315:57
*** briancurtin has joined #openstack-meeting-316:00
*** briancurtin has quit IRC16:01
*** briancurtin has joined #openstack-meeting-316:01
*** briancurtin has joined #openstack-meeting-316:01
*** markmcclain has joined #openstack-meeting-316:07
*** rohit404 has quit IRC16:07
*** eghobo has joined #openstack-meeting-316:07
*** igordcard has quit IRC16:13
*** pballand has quit IRC16:15
*** MaxV has quit IRC16:18
*** MaxV has joined #openstack-meeting-316:19
*** pkoniszewski has joined #openstack-meeting-316:22
*** MaxV has quit IRC16:23
*** jaypipes has joined #openstack-meeting-316:29
*** eghobo has quit IRC16:39
*** MarkAtwood has quit IRC16:45
*** harrisonkelly has joined #openstack-meeting-316:45
*** safchain has quit IRC16:46
*** pballand has joined #openstack-meeting-316:55
*** pkoniszewski has quit IRC16:55
*** MarkAtwood has joined #openstack-meeting-316:57
*** jcoufal has quit IRC16:58
*** MaxV has joined #openstack-meeting-316:59
*** Youcef has joined #openstack-meeting-317:01
*** briancurtin has quit IRC17:04
*** briancurtin has joined #openstack-meeting-317:05
*** briancurtin has joined #openstack-meeting-317:05
*** briancurtin has quit IRC17:05
*** briancurtin has joined #openstack-meeting-317:06
*** briancurtin has quit IRC17:06
*** briancurtin has joined #openstack-meeting-317:07
*** susaant has joined #openstack-meeting-317:07
*** tomoe_ has quit IRC17:08
*** MaxV has quit IRC17:09
*** MaxV has joined #openstack-meeting-317:10
*** chuckC has quit IRC17:12
*** tsufiev has joined #openstack-meeting-317:12
*** MaxV has quit IRC17:14
*** sarob_ has joined #openstack-meeting-317:19
*** ivar-lazzaro has joined #openstack-meeting-317:20
*** sarob_ has quit IRC17:21
*** MaxV has joined #openstack-meeting-317:21
*** yamahata_ has joined #openstack-meeting-317:24
*** tomoe_ has joined #openstack-meeting-317:26
*** anil_rao has joined #openstack-meeting-317:29
*** SridarK has joined #openstack-meeting-317:30
*** david-lyle has quit IRC17:30
*** david-lyle has joined #openstack-meeting-317:30
*** regXboi has joined #openstack-meeting-317:30
*** rudrarugge has joined #openstack-meeting-317:31
SumitNaiksatamSridarK: banix: hi!17:31
SumitNaiksatamcgoncalv1s: hi17:31
SumitNaiksatamlets get started17:31
SumitNaiksatam#startmeeting Networking Advanced Services17:31
openstackMeeting started Wed Jul 30 17:31:37 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at
*** s3wong has joined #openstack-meeting-317: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
*** natarajk has joined #openstack-meeting-317:31
SumitNaiksatam#info agenda:
SumitNaiksatamenikanorov__: there?17:32
SumitNaiksatam#info Juno 3, i believe is 2014-09-04 (#link
enikanorov__SumitNaiksatam: yes17:33
SumitNaiksatamwhich means we can expect code freeze a couple of weeks prior17:33
*** MaxV has quit IRC17:33
SumitNaiksatamso we should be aiming to be ready with our patches submitted say by aug 21st or thereabouts17:33
*** Sukhdev has quit IRC17:34
SumitNaiksatami think mestery will later annoce what the feature freeze deadline is17:34
*** MaxV has joined #openstack-meeting-317:34
*** songole has joined #openstack-meeting-317:34
SumitNaiksatamor he might have already, i missed it17:34
SumitNaiksatam#topic Flavors17:34
*** openstack changes topic to "Flavors (Meeting topic: Networking Advanced Services)"17:34
banixi think jun-3 is the feature freeze deadline17:34
*** anil_rao has quit IRC17:34
enikanorov__so, we're still waiting for spec update, while i've pushed first step implementation and CLI for that17:35
enikanorov__spec isn't approved still L:(17:35
SumitNaiksatambanix: true, but usually we dont allow new features to land a little before that actualy release milestone date17:35
SumitNaiksatambanix: so that poeple can review17:35
SumitNaiksatamenikanorov__: did notice that17:35
*** david-lyle has quit IRC17:35
SumitNaiksatamenikanorov__: but you seem to have removed your patch out of WIP17:35
banixSumitNaiksatam: yes by that day they should have landed meaning much earlier reviews as you mentioned17:35
*** david-lyle has joined #openstack-meeting-317:36
enikanorov__SumitNaiksatam: basically the flavors patch is ready for review17:36
enikanorov__technically there are few things to discuss17:36
SumitNaiksatammestery: there?17:36
*** anil_rao has joined #openstack-meeting-317:36
enikanorov__most noticable is the way driver configuration is pushed17:36
enikanorov__and it's mostly a question of what kind of API attribute to use for that17:36
mesterySumitNaiksatam: Here, reading backscroll around flavors.17:37
SumitNaiksatammestery: hi, was just pinging you :-)17:37
SumitNaiksatammestery: so the my question for you was is it okay for the team here to review enikanorov__’s flavor’s implementation patch?17:38
SumitNaiksatammestery: i believe he is making good progress17:38
*** MaxV has quit IRC17:38
mesteryWe really need that spec approved, that spec and the rootwrap ones are the only ones I'm currently going to allow exceptions for at this point.17:38
SumitNaiksatammestery: however the spec has not been updated since july 2nd to the best of my recollection17:38
mesteryBut we need them to close fast, this week, as we're 5 weeks out from the end.17:38
SumitNaiksatammestery: agree17:38
enikanorov__correct. that still waiting markmcclain's participation17:39
mesteryLets see if we can close this by Friday17:39
SumitNaiksatammestery: ok, meanwhile let people review enikanorov__’s implementation patch as well?17:39
enikanorov__SumitNaiksatam: i think some folks already started reviewing17:40
*** LouisF has joined #openstack-meeting-317:40
*** cathy_ has joined #openstack-meeting-317:40
mesterySumitNaiksatam: There is no harm in that, sure.17:40
SumitNaiksatamenikanorov__: yes sure, just wanted to make sure we are all on the same page in terms of the process17:41
SumitNaiksatammestery: ok great17:41
SumitNaiksatami did not want to get into a situation where people spend a lot of time reviewing the implementation, and then we have to reset it because something else changes in the spec17:41
SumitNaiksatamenikanorov__: definitely commend your persistence on this and for making progress17:41
SumitNaiksatammestery: thanks for that direction, and for jumping in :-)17:42
SumitNaiksatammestery: one more questions17:42
SumitNaiksatammestery: is Aug 21st the feature freeze deadline?17:42
mesteryYes, that's correct.17:42
SumitNaiksatammestery: okay, so aug 21st is the last day that we can post a review for a feature related patch?17:43
mesteryYes sir17:43
banixwow so earlier than i thought17:43
SumitNaiksatammestery: ok great, thanks, wanted to clarify for the rest of the folks here, so there is no confusion17:43
*** Guest17150 is now known as dansmith17:43
SumitNaiksatammestery: bug fixes can go in after that, right?17:43
SumitNaiksatammestery: ok, thanks17:44
mesterySumitNaiksatam: your welcome :)17:44
SumitNaiksatammestery: :-)17:44
SumitNaiksatamenikanorov__: sorry to distract from the focus on the flavors discussion17:44
banixso nw features could get merged upto juno-3 or that is not correct?17:44
SumitNaiksatamenikanorov__: are there any questions for enikanorov__?17:44
SumitNaiksatambanix: yes they will, and until 09/0417:45
*** badveli has joined #openstack-meeting-317:45
banixso what is the aug 21st then?17:45
SumitNaiksatambanix: however a patch can be only submitted against a blueprint by aug 21st17:45
SumitNaiksatambanix: subsequently it will be in review until 09/0417:45
banixnot revised afterward… i see17:45
banixok thx17:46
SumitNaiksatambanix: or it can be approved until 09/0417:46
SumitNaiksatambanix: it can be definitely revised17:46
banixok got it thx17:46
SumitNaiksatambanix: just that you can post a new patch that references a blueprint (so its an implementtion of a new feature) post aug 21st17:46
SumitNaiksatamcan -> cant17:46
SumitNaiksatamenikanorov__: hopefully you and the rest of the team can be out of the limbo by this weekend17:47
SumitNaiksatamwishful thinking! :-)17:47
enikanorov__that would be great17:47
banixi think nova mid-cycle is ongoing so perhaps wont hear from Mrk right away17:47
SumitNaiksatamenikanorov__: thanks for the update17:47
*** mwagner_lap has quit IRC17:48
SumitNaiksatamis s3wong here?17:48
s3wongSumitNaiksatam: hello17:48
*** Longgeek has joined #openstack-meeting-317:48
SumitNaiksatamalso SridarK?17:48
SumitNaiksatam#topic Service base and insertion implementation update17:48
*** openstack changes topic to "Service base and insertion implementation update (Meeting topic: Networking Advanced Services)"17:48
*** harrisonkelly has quit IRC17:48
*** briancurtin has left #openstack-meeting-317:49
SumitNaiksatams3wong: hi, any update for the team on this topic?17:49
mariosso i have been disctracted this week by something else i'm involved in17:49
SumitNaiksatammarios: as well17:49
s3wongNot much update for me, unfortunately. This past week and this week I am focusing on GBP - so nothing, sorry17:49
SumitNaiksatammarios: ok, np17:49
mariosi haven't progressed my side as i wanted to (still wip patch)17:49
SumitNaiksatams3wong: okay17:49
mariosi kinda anticipated this hapening which is why i started the very early wip a few weeks back17:49
marioshopefully i get some update for next week17:49
SridarKSumitNaiksatam: just got back from PTO yesterday17:49
SumitNaiksatammarios: good17:49
mariosand also looking forward to seeing the base class definitions17:50
mariosfrom whoever does that17:50
mariosso i can rebase onto17:50
SumitNaiksatamSridarK: okay, so all of you conspired to not work! :-)17:50
LouisFis kanzhe on?17:50
SumitNaiksatammarios: yes, i agree that there is a dependency for you17:50
s3wongSumitNaiksatam: have we made a decision on how the serviceInterfacePlugin will get the service instance UUID yet?17:50
SumitNaiksatamLouisF: kanzhe is on vacation17:50
mariosSumitNaiksatam: (dependency yeah but definitely not a blocker by any measure at this point)17:50
SumitNaiksatammarios: ok17:50
SumitNaiksatams3wong: i had some ideas on that, which i had run by the team last week17:51
LouisFSumitNaiksatam: who else is working on service base and insertion?17:51
*** hemanthravi has joined #openstack-meeting-317:51
SumitNaiksatamLouisF: kanzhe is expected to back on this soon17:51
*** Longgeek_ has quit IRC17:51
SumitNaiksatamLouisF: besides him, s3wong, marios, SridarK, and kevinbenton are working on it17:51
s3wongmarios: when it becomes available, the base class code will be here #link
SumitNaiksatamLouisF: myself as well17:52
marioss3wong: perfect thx mate17:52
SumitNaiksatams3wong: to your earlier questions17:52
SumitNaiksatams3wong: we can maintain a table in the new service insertion plugin, that will hold a reference to the uuids against their service type17:52
SumitNaiksatams3wong: and we can leverage the notification mechanism (say when a firewall is created, a notification is sent), to learn that a service is created, and then populate the table accordingly17:53
SumitNaiksatams3wong: the notifications already exist today, and are being used ceilometer, etc17:54
SumitNaiksatams3wong: i think kevinbenton had raised some issue with this, but it slips my mind17:54
mariosSumitNaiksatam: is that really for J though? ^^^17:54
*** MaxV has joined #openstack-meeting-317:54
SumitNaiksatammarios: yes, we would need to do this17:54
SumitNaiksatammarios: do you anticipate any issue?17:54
mariosi.e. is that the proposed implementation. i see. no i had thought (from the comments) that interfacing with the service plugins would come later.17:55
SumitNaiksatammarios: this will have the least amount of code churn among other options17:55
banixmarios: the notification mechanism is there already17:55
mariosi guess this way, the plugins can still remain unaware17:55
SumitNaiksatambanix: right17:55
marios(of service insertion code/framework)17:55
SumitNaiksatammarios: exactly17:55
*** songole has quit IRC17:55
SumitNaiksatammarios: the other goal was to be as less intrusive as possible17:55
s3wongmarios: that is the goal, we don't want every service to separately implement and maintain service interface info17:56
SumitNaiksatami think we will still need the services to implement the service base, but that might be minor refactoring of existing code17:56
SumitNaiksatams3wong: agree17:56
SumitNaiksatamokay, anything else to discuss on this topic?17:57
SumitNaiksatamfor this week that is17:57
SumitNaiksatami think we need to churn out some code for the rest of the team to understand17:57
SumitNaiksatamLouisF: you had some questions earlier?17:58
*** briancurtin2 has joined #openstack-meeting-317:58
SumitNaiksatamLouisF: not sure if we answered those17:58
*** briancurtin2 has left #openstack-meeting-317:58
SumitNaiksatamok moving on17:58
LouisFyes thx17:58
SumitNaiksatamhemanthravi: there?17:59
hemanthraviSumitNaiksatam: hi17:59
SumitNaiksatam#topic Service Chaining implementation update17:59
*** openstack changes topic to "Service Chaining implementation update (Meeting topic: Networking Advanced Services)"17:59
SumitNaiksatamhemanthravi: do you have an update on this?17:59
SumitNaiksatami dont see songole17:59
hemanthravistarted working on the patch loosely based on GBP plugin/driver model and expect to have the first patch by Mon18:00
SumitNaiksatamhemanthravi: ah good18:00
hemanthravisongole here with me18:00
hemanthravithis will be a WIP patch18:00
SumitNaiksatamhemanthravi: okay, so who is working on this patch, you, songole, or both?18:00
hemanthravisongole and me18:01
*** pballand has quit IRC18:01
SumitNaiksatamhemanthravi: okay, got it, just want to make sure that the rest of the team knows18:01
SumitNaiksatamhemanthravi: are there are any blockers for you at this point?18:01
*** Longgeek has quit IRC18:01
hemanthravinot yet, will be pinging you with questions later this week18:02
SumitNaiksatamany questions for hemanthravi on this topic?18:02
SumitNaiksatamok moving on then18:03
LouisFwhen will the horizon work for chaining be done?18:03
SumitNaiksatami believe this is all we have approved in terms of blueprints for Juno18:03
SumitNaiksatamlets shift gears to our features which are currently targeted for Kilo18:03
SumitNaiksatam#topic Traffic steering update18:04
*** openstack changes topic to "Traffic steering update (Meeting topic: Networking Advanced Services)"18:04
SumitNaiksatamcgoncalv1s: hi18:04
*** cgoncalv1s is now known as cgoncalves18:04
cgoncalvesSumitNaiksatam: hi18:04
*** mfer has quit IRC18:04
SumitNaiksatamcgoncalv1s: i know this is a little difficult to discuss here since its a kind of a limbo situation18:04
hemanthraviLouisF: haven't planned on horizon for chaining, will look at this as we make progress18:04
cgoncalvesnot much to report this week again18:04
SumitNaiksatamcgoncalves: no worries18:05
cgoncalvesSumitNaiksatam: internally we've been testing it, and myself been out of office on business travels18:05
SumitNaiksatamcgoncalves: my suggestion is that we work towards a plan on what we want to do prior to the specs opening up for Kilo, so that we dont lose momentum here18:05
cgoncalvesnext two weeks I'll be on vacation so don't expect much activity from my end18:06
SumitNaiksatamcgoncalves: sure well deserved break! :-)18:06
cgoncalvesSumitNaiksatam: sure18:06
SumitNaiksatamany questions or suggestions for cgoncalves before takes off on vacation? ;-P18:06
cgoncalvesI should keep lurking around, don't worry.18:07
SumitNaiksatamcgoncalves: sure, i guess one of the suggestions would have been not to - enjoy your time off! :-)18:07
SumitNaiksatamalright moving on18:07
cgoncalvesSumitNaiksatam: I also need to reach out to you and some other folks offline soon.18:07
SumitNaiksatamcgoncalves: sure18:07
SumitNaiksatamanil_rao: there?18:07
anil_raoyes :)18:07
SumitNaiksatam#topic Tap as a Service18:08
*** openstack changes topic to "Tap as a Service (Meeting topic: Networking Advanced Services)"18:08
SumitNaiksatamanil_rao: hi18:08
SumitNaiksatami dont see vinay_yadhav here18:08
anil_raoHi. Vinay can't join us today but I can give an update18:08
SumitNaiksatamanil_rao: same questions as cgoncalves for you18:08
SumitNaiksatamanil_rao: sure go ahead18:08
anil_raoWe are planing on how to proceed, most likely another small revision to the spec18:09
SumitNaiksatamanil_rao: sure18:09
anil_raoHowever, we need some help on how to address the objection to the *-aaS issue.18:09
SumitNaiksatammarios: thanks, sorry i should have been posting the links during the discussion18:09
SumitNaiksatammarios: true, except that its not funny to hold up the spec for this reason! :-(18:10
mariosSumitNaiksatam: np (i just had it open so pasted). yes this is true.18:10
SumitNaiksatamanil_rao: please proceed18:10
anil_raoWe are also looking into starting the implementation and uploading some initial code for review as WIP18:11
SumitNaiksatamanil_rao: i do understand the motivation and need for choosing that name18:11
SumitNaiksatami belive the rest of the team is also aware of that18:11
mariosplus the *-aas issue is much wider reaching than tap-aas (as in the comments, lb, vpn, fw etc)18:12
SumitNaiksatammarios: true, there is already a precedent!18:12
SumitNaiksatami believe the itention was to expose a rich set of features behind this service endpoint18:12
SumitNaiksatamport-mirroring is the first capablity18:12
anil_raoPerhaps we will make our intentions more explicit in the spec so that there is no confusion going forward18:13
SumitNaiksatamanil_rao: sure18:13
anil_raoOne question if I may.18:13
SumitNaiksatamthe predicament for the authors here is that if they pack too many features they will be dinged for putting too much in18:14
SumitNaiksatamanil_rao: please go ahead18:14
*** briancurtin has joined #openstack-meeting-318:14
*** briancurtin has joined #openstack-meeting-318:14
anil_raoWe are currently referencing an older BP called Port-Mirroring Extension. Perhaps that is what is causing the confusion. Do you all suggest that we drop that BP and create a new one for our Spec.18:14
SumitNaiksatamanil_rao: ah, i did not realize that18:15
*** MaxV has quit IRC18:15
SumitNaiksatamanil_rao: perhaps, however the new BP should have enough in it to suggest that is it sufficiently different or encompasses the existing one18:16
SumitNaiksatamanil_rao: you have done the right thing by referencing and trying to reuse an existing body of work18:16
*** MaxV has joined #openstack-meeting-318:16
SumitNaiksatamanil_rao: however if it is causing issues, perhaps something worth considering18:16
*** lblanchard has quit IRC18:16
anil_raoOk. I'll discuss this with Vinay.18:17
SumitNaiksatamanil_rao: it might also be good to send out an email to the -dev mailer explaining this explicitly18:17
anil_raoSure. That is a good idea.18:17
cathy_SumitNaiksatam: Sorry to chime in late. May I ask one question. Regarding our comment about the direction of the chain on service chaining BP, I did not see a reply on the latest comment.18:17
cathy_That is, supposing user request FW then IDS, the service chaining API reqires specifying the port for applying the service and the BP gives an example of a Neutron port between a router and network X. But without the direction, it is ambigous whether the traffic flows through Router->FW->IDP->Network X or the reverse sequence.18:18
SumitNaiksatamcathy_: sure, i think we have some spare time18:18
SumitNaiksatamcathy_: can you hold that question while we wrap up the Tap update?18:18
SumitNaiksatamanil_rao: anything else you wanted to discuss?18:19
SumitNaiksatamany questions for anil_rao on Tap?18:19
anil_raoNo at this time. Thanks18:19
SumitNaiksatamanil_rao: thanks18:19
SumitNaiksatam#topic Open Discussion18:19
*** openstack changes topic to "Open Discussion (Meeting topic: Networking Advanced Services)"18:19
SumitNaiksatamhemanthravi: still there?18:20
*** jcoufal has joined #openstack-meeting-318:20
SumitNaiksatamcathy_: did you post the comment on the approved spec?18:20
*** banix has quit IRC18:20
marioscathy_: i believe the list of nodes is intended to be ordered18:20
cathy_yes, I posted. Then Louis posted on a new updated version18:20
SumitNaiksatammarios: true, that was my understanding as well (and the original intent)18:21
*** MaxV has quit IRC18:21
SumitNaiksatamcathy_: ah ok18:21
SumitNaiksatami dont see mandeep here18:21
marios"This creates the ordered-list ["FW", "LB"] as the list of services in the196 chain.18:21
SumitNaiksatamhemanthravi: can you take a stab at answering cathy_’s question?18:21
hemanthravicurrently it's an ordered list and traffic in reverse will the list reversed18:22
SumitNaiksatamcathy_: i believe your question is that you want only traffic from one direction to hit the service chain in that order?18:22
mariosthe latest version actually is updated to be more explicit about the direction/ordering
SumitNaiksatammarios: true18:23
cathy_SumitNaiksatam: what is needed is the explicit, If the latest has that, we cna take a look.18:23
SumitNaiksatamcathy_: ok, we can circle back to this if your query is not satisified18:24
cathy_But from the API, how could the user spacify two different sequences of service chain (one the forward sequence, the other the reverse sequence)?18:24
LouisFin the lates there is no defintion of what "ingress" and "egress" traffic is18:24
SumitNaiksatam#action hemanthravi to report back on cathy_’s question “from the API, how could the user spacify two different sequences of service chain (one the forward sequence, the other the reverse sequence)?”18:24
SumitNaiksatamLouisF: got it18:25
SumitNaiksatamhemanthravi: see the above action item ^^^ :-)18:25
cathy_SumitNaiksatam: hemanthravi : Thanks!18:25
hemanthraviwill do, need to work through some of the scenarios18:25
SumitNaiksatamcathy_: np, thanks for brining it up18:25
SumitNaiksatamwe are getting close to our time here18:26
LouisFhemanthravi: look at my comments on previous patches18:26
hemanthraviLouisF: ok18:26
SumitNaiksatamanything else we need to discuss?18:26
s3wong3 minutes early!!!18:27
mariosgoodnight all :)18:27
SumitNaiksatams3wong: yay!18:27
SumitNaiksatamthanks all for attending18:27
SumitNaiksatamkeep up the good work18:27
regXboi@SumitNaiksatam: a last suggestion18:27
SumitNaiksatamregXboi: just in time18:27
SumitNaiksatamregXboi: shoot18:27
*** asahlin_ has quit IRC18:28
regXboisend an email out to openstack-dev with the link to the minutes and a note of any #agreed items18:28
regXboijust to be friendly18:28
SumitNaiksatamregXboi: ah ok18:28
regXboiI'm going to send mail suggesting that across the board18:28
SumitNaiksatamregXboi: did not have any “agreed” items today18:28
regXboihaving spent time cross-indexing minutes with ML18:28
SumitNaiksatamregXboi: but good suggestion18:28
SumitNaiksatamregXboi: i have tried not to bombard the mailing list with too many emails about routine items18:29
SumitNaiksatamregXboi: since i think there is already an overload18:29
SumitNaiksatamregXboi: but will definitely keep that in mind in the context that you mentioned18:29
regXboiunderstood - but a note about a "hey we met, here are the minutes" keeps all abreast18:29
SumitNaiksatamand right on dot18:29
SumitNaiksatamregXboi: sure18:29
*** openstack changes topic to "OpenStack Meetings ||"18:29
openstackMeeting ended Wed Jul 30 18:29:44 2014 UTC.  Information about MeetBot at . (v 0.1.4)18:29
openstackMinutes (text):
*** anil_rao has quit IRC18:29
*** cathy_ has quit IRC18:30
SumitNaiksatamSridarK: yisun gduan badveli natarajk: there?18:30
SumitNaiksatamlets get started18:30
SumitNaiksatam#startmeeting Networking FWaaS18:31
openstackMeeting started Wed Jul 30 18:31:06 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:31
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:31
openstackThe meeting name has been set to 'networking_fwaas'18:31
*** regXboi has left #openstack-meeting-318:31
SumitNaiksatambadveli: hi18:31
*** otherwiseguy has quit IRC18:31
SumitNaiksatam#topic Action items review18:32
*** openstack changes topic to "Action items review (Meeting topic: Networking FWaaS)"18:32
badvelisorry was discussing some ting18:32
SumitNaiksatamour pending action item is a logistical one, we had to set up a f2f with the DVR team18:32
SumitNaiksatamSridarK: we were waiting for you to get back18:32
SridarKSumitNaiksatam: yes i am good lets figure out a day18:33
badvelii had got two servers for my installation18:33
SridarKbadveli: great18:33
SumitNaiksatam#action SumitNaiksatam to start a thread in fwaas team to schedule f2f meeting with DVR team18:33
badvelisridar we can try the installation, going through the wiki18:33
*** s3wong has quit IRC18:33
SumitNaiksatambadveli: thats great18:33
badvelithanks sumit18:34
SridarKSumitNaiksatam: so maybe badveli and i will spend some time on this later this week18:34
*** tomoe_ has quit IRC18:34
SumitNaiksatambadveli: can you hold to that discussion when we bring up that agenda item?18:34
SridarKso we will have some more context b4 the mtg with DVR18:34
SumitNaiksatamSridarK: ^^^?18:34
SridarKoops sorry18:34
*** hemanthravi has quit IRC18:34
SumitNaiksatamthough we can definitely treat badveli’s activity as a pending action item ;-)18:35
SumitNaiksatamSridarK: no worries18:35
SumitNaiksatamSridarK: btw, belated, but welcome back! :-)18:35
SridarKSumitNaiksatam: glad to be back :-)18:35
SumitNaiksatamSridarK: the team definitely missed you last week18:35
SumitNaiksatam#topic Bugs18:36
*** openstack changes topic to "Bugs (Meeting topic: Networking FWaaS)"18:36
SridarKSumitNaiksatam: thx18:36
SumitNaiksatami did not find anything critical or high that is pending18:36
SridarKSumitNaiksatam: quick scan on bugs nothing new18:36
SumitNaiksatamSridarK badveli: did you get a chance to bug scrub?18:36
SridarKSumitNaiksatam: yes18:36
SumitNaiksatamSridarK: ah ok18:36
badvelilooked at the link,18:36
SumitNaiksatambadveli: ok good18:37
SumitNaiksatamat some point we have to make a push towards get a grasp on how the pending bugs are going to be closed18:37
*** eghobo has joined #openstack-meeting-318:37
SumitNaiksatami am saying in the context of juno-318:37
SridarKSumitNaiksatam: yes once we get our patches moving - we will try to wrap up on some of these bugs18:38
SumitNaiksatamwe will have time to get big fixes in even after juno-3 but they will have to only critical fixes18:38
SumitNaiksatamSridarK: that sounds like a good plan18:38
SridarKSumitNaiksatam: mostly we have some low priority issues now18:39
SumitNaiksatamSridarK: i was suggesting that we need to track down the folks who are not in this meeting but are owning the patches for those bugs18:39
badveliyes sumit, after the patches we can wrap the bugs18:39
SumitNaiksatamSridarK: yes, thankfully18:39
SridarKSumitNaiksatam: let me take a stab at that18:39
SumitNaiksatamSridarK: great18:39
badvelidid we get any feed back from sridargaddam18:39
SumitNaiksatamwe can essentially split the bugs between us, and follow up with the relevant folks18:39
SumitNaiksatamSridarK: i know you are already doing that18:40
SridarKSumitNaiksatam: sounds good18:40
SumitNaiksatambadveli: we did, and he posted a new patch as well18:40
badveliok, thanks sumit18:40
badveliyes we can split up the bugs and go after the relevant bugs18:40
SumitNaiksatami believe Sridargaddam needs to post a new rev18:40
SumitNaiksatamto respond to carl_baldwin’s -118:41
SumitNaiksatamok anything else on bugs?18:41
SridarKSumitNaiksatam: nothing from me - i am not caught up on last week yet either18:41
SumitNaiksatamwe were discussing #link
SumitNaiksatamSridarK: ok sure18:41
SumitNaiksatam#topic FWaaS support for DVR18:41
*** openstack changes topic to "FWaaS support for DVR (Meeting topic: Networking FWaaS)"18:42
SumitNaiksatamSridarK: badveli yisun: ?18:42
SumitNaiksatambadveli: you already mentioned that you set up the servers, thats great18:42
badveliyes sumit18:42
SumitNaiksatambadveli: so you have a working DVR setup?18:42
SridarKSumitNaiksatam: i believe the plan was badveli and i will get together to go over the changes once we have a DVR setup18:42
*** lblanchard has joined #openstack-meeting-318:43
badvelisumit:i have the two servers , initially it was tough to have the servers i think we needed atleast two. so got it and trying to set up18:43
SumitNaiksatambadveli: so you have a DVR installation?18:43
badvelisumit: i did not had enough servers, just got two servers18:44
SumitNaiksatambadveli: nice, completely appreciate the difficulty in getting the two servers, its not easy with resource constraints and what not18:44
SumitNaiksatambadveli: i am guessing two should be enough?18:44
badveliyes sumit18:44
SumitNaiksatambadveli: SridarK we should check with Swami on this18:44
SridarKSumitNaiksatam: yes 2 was recommended by Rajeev18:44
SumitNaiksatamalso regarding the f2f meeting, i think its better if we do some amount of home work before we schedule the meeting18:45
SridarKSumitNaiksatam: i think once we this moving we can reach out to Swami18:45
SumitNaiksatamthat way we can have more informed conversation18:45
SridarKSumitNaiksatam: yes that will be beneficial18:45
SumitNaiksatamSridarK: great18:45
badvelisridar: i think once we set up the things and start playing with it we might get more idea18:45
SridarKSumitNaiksatam: badveli ideally once we have DVR we can look at the FWaaS failure cases18:46
SridarKas a first step18:46
SumitNaiksatambadveli: SridarK so you plan to sync up this week?18:46
SridarKyes we will18:46
badveliyes sumit18:46
SumitNaiksatamok great, thanks18:46
SumitNaiksatamalso do we have any dependencies on the DVR team?18:46
SumitNaiksatamif so, we can start tracking them here18:46
*** Longgeek has joined #openstack-meeting-318:47
SridarKSumitNaiksatam: good question - while doing the spec 2 or 3 patches were yet to merge18:47
SridarKSumitNaiksatam: will follow thru on that18:47
SumitNaiksatamSridarK: ah ok18:47
SumitNaiksatami believe the suggestion was that we used the private repo18:47
SumitNaiksatamfor that reason18:47
badveliSumit:  patches from dvr, should we go through them to understand more, there were some couple of changes we might need to understand more18:47
SridarKSumitNaiksatam: yes that is correct18:47
SridarKSumitNaiksatam: particularly the L3 agent was still in review but i need to check now18:48
SridarKSumitNaiksatam: my sense is that our changes are going to be in the Agent and the driver - we will try to scope this out to get a sense of the scope18:49
SumitNaiksatamSridarK badveli can we create a new wiki page for FWaaS DVR support and link it from the FWaaS wiki page?18:49
SridarKSumitNaiksatam: sure will do18:49
*** MaxV has joined #openstack-meeting-318:49
badveliyes sumit, sridark we can add details independently18:49
SridarKbadveli: and i can discuss this18:49
SumitNaiksatamon that wiki page, lets list provide links to our patches and to all the dependencies18:50
badvelifine sridark18:50
SridarKSumitNaiksatam: sounds good18:50
SumitNaiksatamonce this is done, lets send an email to the mailer, so that its known to all what we are working on, and what are dependencies18:50
SridarKSumitNaiksatam: ok18:50
SumitNaiksatam#action SridarK badveli to setup FWaaS DVR support wiki page, provide spec/impl/dependency links, send email to -dev with pointer to this wiki page18:51
badvelisridark is already on top of it, we can add it18:51
SumitNaiksatambadveli: great18:51
SumitNaiksatamanything else to discuss on this topic?18:51
SumitNaiksatamany blockers here?18:51
badvelithanks sridark and sumit18:51
SridarKSumitNaiksatam: no blockers seen as of now18:52
badvelithe scope of the code changes18:52
SridarKSumitNaiksatam: i am sure something will come up18:52
SumitNaiksatamSridarK: badveli thanks for the update18:52
SumitNaiksatam#topic Service Objects18:52
*** openstack changes topic to "Service Objects (Meeting topic: Networking FWaaS)"18:52
badvelii am working on the reference implementation18:52
SumitNaiksatamah seems like i have the wrong link18:53
SumitNaiksatambadveli: can you post the link to your patch here18:53
badvelii am tryiing to update the link in the wiki18:53
badvelinot able to update it18:53
SumitNaiksatambadveli: was just going to say18:53
SumitNaiksatameveryone please keep: #link updated18:54
SumitNaiksatambadveli: you might have not logged in before you tried to update18:54
SumitNaiksatambadveli: else i dont see any reason why you would not be able to update18:54
badvelinot sure i tried some time back18:55
badvelii will update again18:55
badvelithree patches18:56
badvelithe reference implementation is not yet done18:56
badvelii am working on it and would be finishing sooner18:56
SumitNaiksatambadveli: good18:57
SridarKbadveli: i have not looked yet either - will do so18:57
badvelithanks sridark and sumit18:57
SumitNaiksatambadveli: sorry for having to take the drastic step of -2ing the patch18:57
badvelino problem18:57
badvelii was a bit confused18:57
SumitNaiksatambadveli: if i did not, someone else would have done it for that reason18:57
badvelion the process, for some reason18:57
badveliok, no problem sumit18:58
SumitNaiksatambadveli: also your second patch needs to be dependent of the first one18:58
SumitNaiksatambadveli: the process is documented in the gerrit workflow18:58
badvelithere was some last minute updates that happened18:58
badvelithanks sumit18:58
SumitNaiksatambadveli: you shoud have been able to search this on google, but here is a ready reference: #link
badveliyes sumit the second is dependent on first18:59
SumitNaiksatambadveli: also, i had earlier sent you a link on how the commit messages need to be formatted18:59
SumitNaiksatambadveli: please follow those guidelines, as i still see some descrepancies18:59
badvelisumit, i followed it for the second patch18:59
SumitNaiksatambadveli: i know this is not as much technical, but it does turn off reviewers18:59
badveliyes sumit, the first and last patch were uploaded before18:59
badvelii will also correct them19:00
SumitNaiksatambadveli: for one, “Implements: blueprint fwaas-customized-service for customized service” is not a suggested a commit message title19:00
SumitNaiksatambadveli: ah i see, you updated
SumitNaiksatambadveli: good19:00
badveliyes sumit19:00
badveliAdd service group as a firewall customized service19:00
SridarKbadveli: i can also help offline if u need - SumitNaiksatam has explained a lot of this to me earlier on the dependencies etc19:00
badvelithe second one was updated after you send the link19:01
badvelii am adding the reference implementation so will update the rest of the two19:01
badvelibut i am a bit not sure how does all this patches work19:01
SumitNaiksatambadveli: great, i also notice you added the UTs in the first patch19:01
SumitNaiksatambadveli: i have removed my -219:01
badvelithanks sumit19:02
badveliinitially at the last minute19:02
SumitNaiksatambadveli: please go ahead, why do you say - “i am a bit not sure how does all this patches work"19:02
badveliyes, you mentioned the first patch19:02
badveliis cli and it will go in after the patches in19:02
badvelisumit: you had mentioned it will be reviewed after the patches in neutron19:03
SumitNaiksatambadveli: you mean the client patch?19:03
badvelifor example i will try to get the reviewers in second patch19:03
badveliyes, the cli part19:03
badveliif some reviewers approve second patch19:03
SumitNaiksatambadveli: yeah, there is no way that the CLI will be approved and merged before the neutron patches19:04
*** QJ has joined #openstack-meeting-319:04
SumitNaiksatambadveli: because it does not make sense to have CLI for a feature that does not exist19:04
SumitNaiksatambadveli: typically the rewiew happens in parallel19:04
SumitNaiksatambadveli: but you will recieve more attention on the CLI patches once its clear that the neutron patches are almost ready19:04
badvelifine sumit: how does this dependency is explicit19:05
SumitNaiksatambadveli: but you do have to keep the CLI patch ready, since people wil ltry to install devstack and test the neutron patches using your CLI patches19:05
SumitNaiksatambadveli: you cannot setup a dependency across projects19:05
badvelii meant to say if i get some approvals for the second and third patch19:06
SumitNaiksatambadveli: which means, in this case, you cannot setup a dependency from your CLI patch on your neutron patch19:06
badvelioh..thanks sumit19:06
SumitNaiksatambadveli: i am a little cofused as to which are your second and third patches19:06
SumitNaiksatambadveli: lets not refer to them that way19:06
badvelidoes this mean we cannot ask the reviewers for reviewing the cli19:06
SumitNaiksatambadveli: i believe you have one CLI patch and two neutron patches19:06
SumitNaiksatambadveli: i already answered that19:06
SumitNaiksatambadveli: you can ask, and you should, but realistically you will not get much attention19:07
badvelifine sumit, i will actively work on the neutron patches19:07
badvelifor the reviews19:07
badvelito happen19:07
SumitNaiksatambadveli: the way you want to go about is by saying - here are the neutron patches, please review them; and here is the CLI patch which will help you to review those19:07
badveligot it sumit19:08
SumitNaiksatambadveli: that way you point to both these sets of patches, with due priority given to the neutron patch19:08
badvelifine sumit19:09
badvelialso the wiki link has some tempest and horizon19:09
*** chuckC has joined #openstack-meeting-319:09
SumitNaiksatamanother suggestion, and pretty for everyone here - we can assign some identifier names to our patches19:09
SumitNaiksatamfor example in the group policy work, i go GP-API-1, GP-DB-1,…, GP-API-2, GP-DB-2, etc19:10
SumitNaiksatamthat way it becomes easier to refer to patches when we are talking19:10
badvelifine sumit19:10
SumitNaiksatamthese can be mentioned in the commit message19:10
SumitNaiksatamyou can see the group policy patch: #link
SumitNaiksatamthis is just a personal preference, there is no precedence in neutron for this19:11
SumitNaiksatamso feel free to ignore19:11
*** briancurtin has left #openstack-meeting-319:11
*** LouisF has quit IRC19:11
*** nelsnelson has quit IRC19:11
*** mestery has quit IRC19:12
badvelifine sumit19:12
SumitNaiksatamanything else to discuss on service objects?19:12
SumitNaiksatammy fingers are aching now! :-(19:12
*** mestery has joined #openstack-meeting-319:12
badvelithe wiki link is also capturing about the heat19:12
badvelisumit, i think we are done but last one19:13
badvelithe wiki link has tempest horizon19:13
SumitNaiksatambadveli: yeah sure19:13
SridarKSumitNaiksatam: :-) we need voice to text convertors for IRC19:13
SumitNaiksatambadveli: yes19:13
SumitNaiksatamSridarK: :-)19:13
SumitNaiksatambadveli: very good point to bring up19:13
badveliwikik has horizon,tempest,heat19:13
SumitNaiksatambadveli: we need the tempest API patch to be in review as well19:13
badveliok, this is what i need19:14
SumitNaiksatambadveli: the neutron patch will not merge without the tempest API patch19:14
*** mestery has quit IRC19:14
SumitNaiksatambadveli: let me hook you up with miguel19:14
badvelithanks sumit19:14
badveliappreciate your help19:14
SumitNaiksatambadveli: and ideally we should have a tempest scenario patch as well19:14
*** mestery has joined #openstack-meeting-319:14
badvelii will go through it, but the scenario patch is compulsary19:15
SumitNaiksatam#action SumitNaiksatam to reach out to mlavalle regarding tempest patches for upcoming fwaas features, cc rest of the fwaas team19:15
SumitNaiksatambadveli: lets check with mlavalle19:15
badvelithanks sumit19:15
SumitNaiksatambadveli: but even if its not, its better to have it, since it wil strengthen our case19:15
SumitNaiksatambadveli: lets do all we can (assuming we have the time) so that our reviews get smoother19:16
badvelifine sumit, let me go through it19:16
badveliyes sumit19:16
SumitNaiksatam#topic FWaaS metering19:16
*** openstack changes topic to "FWaaS metering (Meeting topic: Networking FWaaS)"19:16
SumitNaiksatamis prad here?19:16
SumitNaiksatamSridarK: i believe prad got his spec approved in ceilometer19:17
SumitNaiksatamSridarK: thats great19:17
SridarKSumitNaiksatam: oh great19:17
SridarKSumitNaiksatam: i will sync with prad19:17
SumitNaiksatamif prad, needs any help we are here to help19:17
SumitNaiksatam#topic open discussion19:17
*** openstack changes topic to "open discussion (Meeting topic: Networking FWaaS)"19:17
SridarKSumitNaiksatam:  to make sure on any requirements on neutron side19:17
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x2d0c350>19:17
SumitNaiksatamSridarK: yes19:18
SumitNaiksatam#topic Vendor blueprints19:18
*** openstack changes topic to "Vendor blueprints (Meeting topic: Networking FWaaS)"19:18
SumitNaiksatamnatarajk: SridarK: anything you want to bring up?19:18
SridarKSumitNaiksatam: sorry done with what i had to say on the pref topic19:18
natarajkSumitNaiksatam:Nothing much. We are fixing our CI server to l3 plugin.19:18
natarajkto -> for19:19
SumitNaiksatamnatarajk: ah ok, sorry i havent been able to get to it19:19
SumitNaiksatamnatarajk: review i mean, i have a big stack19:19
SumitNaiksatamSridarK: anything at your end?19:19
SridarKSumitNaiksatam: not much to report on our side - we need the vendor dependent patch to merge19:19
SridarKSumitNaiksatam: we will have the FWaaS piece ready19:20
SumitNaiksatamSridarK: sweet19:20
SumitNaiksatam#topic open discussion19:21
*** openstack changes topic to "open discussion (Meeting topic: Networking FWaaS)"19:21
SridarKSumitNaiksatam: will reach out to u and s3wong to discuss service insertion19:21
SumitNaiksatamgduan: are you tracking the flavor impleemenation from enikanorov__?19:21
SumitNaiksatamSridarK: sure, we are a bit behind on that19:21
SridarKSumitNaiksatam: will discuss over email19:21
SumitNaiksatambadveli: can you check with gduan?19:22
badvelifine sumit19:22
SumitNaiksatambadveli gduan: we need to keep track since we might not get a whole lot of time to react once the spec is approved19:23
SumitNaiksatamgduan: ^^^19:25
gduanI am actually fine with the patch19:25
SumitNaiksatamok good19:25
gduanbut spec is not approved yet19:25
SumitNaiksatamgduan: yeah19:25
SumitNaiksatamgduan: we have to be ready on the fwaas side to jump in when the spec is approved19:25
SumitNaiksatamgduan: probably this weekend19:25
SumitNaiksatamanything else to discuss?19:25
gduanthe patch is the data model patch19:26
SumitNaiksatamgduan: okay19:26
gduanthe implementation is not submitted yet,19:26
gduanI mean enikanorov's patch19:27
SumitNaiksatamgduan: for what?19:27
gduanenikanorov's current patch is for data model only19:27
gduanI guess dispatching part will be another one19:28
SumitNaiksatamgduan: ah ok, lets check with him, on provide comment on the patch19:28
SumitNaiksatamgduan: glad that you have been tracking ;-)19:28
SumitNaiksatamokay if nothing else, lets wrap up19:28
gduanok. I will discuss with him.19:28
SumitNaiksatamgduan: thanks19:28
SumitNaiksatamthanks all!19:28
SridarKthanks all19:29
*** openstack changes topic to "OpenStack Meetings ||"19:29
openstackMeeting ended Wed Jul 30 19:29:04 2014 UTC.  Information about MeetBot at . (v 0.1.4)19:29
openstackMinutes (text):
*** natarajk has left #openstack-meeting-319:29
*** gothicmindfood has left #openstack-meeting-319:32
*** banix has joined #openstack-meeting-319:34
*** SumitNaiksatam has quit IRC19:34
*** pballand has joined #openstack-meeting-319:44
*** thangp has quit IRC19:45
*** otherwiseguy has joined #openstack-meeting-319:57
*** lblanchard has quit IRC20:00
*** alexpilotti has quit IRC20:09
*** thomasem has joined #openstack-meeting-320:17
*** thomasem has quit IRC20:19
*** jcoufal has quit IRC20:26
*** SridarK has quit IRC20:30
*** cjellick_ has joined #openstack-meeting-320:38
*** s3wong has joined #openstack-meeting-320:39
*** tomoe_ has joined #openstack-meeting-320:39
*** cjellick_ has quit IRC20:41
*** cjellick_ has joined #openstack-meeting-320:41
*** cjellick has quit IRC20:42
*** pballand has quit IRC20:42
*** MaxV has quit IRC20:43
*** MaxV has joined #openstack-meeting-320:44
*** pballand has joined #openstack-meeting-320:44
*** cjellick_ has quit IRC20:46
*** MaxV_ has joined #openstack-meeting-320:47
*** MaxV has quit IRC20:48
*** MarkAtwood has quit IRC20:51
*** QJ has quit IRC20:57
*** julim has joined #openstack-meeting-321:07
*** iovadia has joined #openstack-meeting-321:11
*** Longgeek has quit IRC21:13
*** jcoufal has joined #openstack-meeting-321:16
*** jcoufal has quit IRC21:23
*** briancurtin has joined #openstack-meeting-321:27
*** MaxV_ has quit IRC21:28
*** MaxV has joined #openstack-meeting-321:29
*** MaxV has quit IRC21:33
*** julim has quit IRC21:37
*** susaant has quit IRC21:42
*** tomoe_ has quit IRC21:42
*** markmcclain has quit IRC21:49
*** briancurtin has quit IRC21:53
*** briancurtin has joined #openstack-meeting-321:53
*** MaxV has joined #openstack-meeting-321:54
*** SumitNaiksatam has joined #openstack-meeting-321:56
*** briancurtin has quit IRC21:58
*** MaxV has quit IRC22:04
*** MaxV has joined #openstack-meeting-322:05
*** eghobo has quit IRC22:08
*** eghobo has joined #openstack-meeting-322:09
*** MaxV has quit IRC22:09
*** Youcef has quit IRC22:12
*** banix has quit IRC22:12
*** armax has quit IRC22:19
*** peristeri has quit IRC22:20
*** david-lyle has quit IRC22:42
*** david-lyle has joined #openstack-meeting-322:42
*** yamahata has quit IRC22:46
*** carl_baldwin has quit IRC22:46
*** david-lyle has quit IRC22:47
*** MaxV has joined #openstack-meeting-322:47
*** MarkAtwood has joined #openstack-meeting-322:47
*** thomasem has joined #openstack-meeting-322:50
*** Sukhdev has joined #openstack-meeting-322:50
*** pballand has quit IRC22:51
*** thomasem has quit IRC22:52
*** thomasem has joined #openstack-meeting-322:53
*** nelsnelson has joined #openstack-meeting-322:54
*** nelsnelson has quit IRC22:55
*** armax has joined #openstack-meeting-322:55
*** thomasem has quit IRC22:55
*** nelsnelson has joined #openstack-meeting-322:55
*** thomasem has joined #openstack-meeting-322:56
*** jaypipes has quit IRC22:58
*** briancurtin has joined #openstack-meeting-323:01
*** briancurtin has joined #openstack-meeting-323:01
*** iovadia has quit IRC23:06
*** yamamoto_ has quit IRC23:12
*** yamamoto has joined #openstack-meeting-323:12
*** flaviof is now known as flaviof_zzz23:14
*** pballand has joined #openstack-meeting-323:15
*** yamamoto has quit IRC23:17
*** yamamoto has joined #openstack-meeting-323:17
*** banix has joined #openstack-meeting-323:19
*** pballand has quit IRC23:21
*** briancurtin2 has joined #openstack-meeting-323:21
*** briancurtin has quit IRC23:25
*** carl_baldwin has joined #openstack-meeting-323:34
*** otherwiseguy has quit IRC23:36
*** thomasem has quit IRC23:41
*** briancurtin2 has quit IRC23:44
*** briancurtin has joined #openstack-meeting-323:44
*** ivar-lazzaro has quit IRC23:45
*** briancurtin has quit IRC23:49
*** jamielennox|away is now known as jamielennox23:53
*** MaxV has quit IRC23:54
*** carl_baldwin has quit IRC23:55
*** MaxV has joined #openstack-meeting-323:55
*** amotoki has quit IRC23:56
*** banix has quit IRC23:57
*** MaxV has quit IRC23:59

Generated by 2.14.0 by Marius Gedminas - find it at!