Wednesday, 2014-07-02

*** david-lyle has quit IRC00:05
*** david-lyle has joined #openstack-meeting-300:06
*** chuckC has quit IRC00:07
*** yamamoto has joined #openstack-meeting-300:07
*** lblanchard has joined #openstack-meeting-300:09
*** david-lyle has quit IRC00:10
*** cjellick_ has joined #openstack-meeting-300:16
*** cjellick has quit IRC00:20
*** briancurtin_away is now known as briancurtin00:21
*** tomoe_ has quit IRC00:23
*** briancurtin is now known as briancurtin_away00:30
*** hurgleburgler has quit IRC00:35
*** banix has joined #openstack-meeting-300:35
*** banix has quit IRC00:40
*** shakamunyi has quit IRC00:42
*** banix has joined #openstack-meeting-300:43
*** pgpus has joined #openstack-meeting-300:49
*** TravT|2 has quit IRC00:57
*** nati_ueno has quit IRC00:59
*** shakamunyi has joined #openstack-meeting-301:00
*** nati_ueno has joined #openstack-meeting-301:01
*** briancurtin_away is now known as briancurtin01:07
*** nati_ueno has quit IRC01:09
*** nati_ueno has joined #openstack-meeting-301:10
*** nelsnelson has joined #openstack-meeting-301:19
*** Sukhdev has quit IRC01:20
*** yamamoto has quit IRC01:20
*** shakamunyi has quit IRC01:20
*** Sukhdev has joined #openstack-meeting-301:22
*** lblanchard has quit IRC01:22
*** tomoe_ has joined #openstack-meeting-301:22
*** nelsnelson has quit IRC01:23
*** nelsnelson has joined #openstack-meeting-301:24
*** otherwiseguy has quit IRC01:27
*** otherwiseguy has joined #openstack-meeting-301:27
*** nelsnelson has quit IRC01:34
*** stanzgy has joined #openstack-meeting-301:35
*** armax has quit IRC01:35
*** MarkAtwood has joined #openstack-meeting-301:39
*** yamamoto has joined #openstack-meeting-301:40
*** clu_ has quit IRC01:41
*** briancurtin is now known as briancurtin_away01:41
*** otherwiseguy has quit IRC01:51
*** pgpus has quit IRC01:56
*** thomasem has joined #openstack-meeting-301:59
*** thomasem has quit IRC01:59
*** briancurtin_away is now known as briancurtin02:00
*** nati_ueno has quit IRC02:07
*** nati_ueno has joined #openstack-meeting-302:10
*** otherwiseguy has joined #openstack-meeting-302:12
*** lenrow has joined #openstack-meeting-302:18
*** MarkAtwood has quit IRC02:18
*** dlenrow has quit IRC02:21
*** nati_ueno has quit IRC02:21
*** nati_ueno has joined #openstack-meeting-302:21
*** nati_ueno has quit IRC02:22
*** pgpus has joined #openstack-meeting-302:26
*** scott-millward has quit IRC02:42
*** chuckC has joined #openstack-meeting-302:44
*** pballand has joined #openstack-meeting-302:45
*** Sukhdev has quit IRC02:46
*** jpomero__ has quit IRC02:47
*** armax has joined #openstack-meeting-302:47
*** ivar-lazzaro has quit IRC02:48
*** pballand has quit IRC02:49
*** cjellick_ has quit IRC02:57
*** cjellick has joined #openstack-meeting-302:58
*** otherwiseguy has quit IRC02:58
*** cjellick_ has joined #openstack-meeting-303:00
*** nati_ueno has joined #openstack-meeting-303:02
*** cjellick has quit IRC03:02
*** cjellick_ has quit IRC03:04
*** otherwiseguy has joined #openstack-meeting-303:04
*** mwagner_ has quit IRC03:15
*** carl_baldwin has joined #openstack-meeting-303:18
*** armax has left #openstack-meeting-303:20
*** armax has quit IRC03:20
*** sankarshan_away is now known as sankarshan03:23
*** mwagner_ has joined #openstack-meeting-303:27
*** cjellick has joined #openstack-meeting-303:30
*** carl_baldwin has quit IRC03:34
*** cjellick has quit IRC03:39
*** otherwiseguy has quit IRC03:39
*** otherwiseguy has joined #openstack-meeting-303:40
*** pgpus has quit IRC03:41
*** carl_baldwin has joined #openstack-meeting-303:42
*** TravT has joined #openstack-meeting-303:45
*** coolsvap|afk is now known as coolsvap03:53
*** stanzgy has quit IRC04:02
*** lcheng has joined #openstack-meeting-304:02
*** TravT has quit IRC04:03
*** nelsnelson has joined #openstack-meeting-304:11
*** banix has quit IRC04:11
*** Sukhdev has joined #openstack-meeting-304:12
*** briancurtin is now known as briancurtin_away04:23
*** carl_baldwin has quit IRC04:26
*** carl_baldwin has joined #openstack-meeting-304:28
*** stanzgy has joined #openstack-meeting-304:32
*** gothicmindfood has quit IRC04:56
*** otherwiseguy has quit IRC05:08
*** carl_baldwin has quit IRC05:13
*** otherwiseguy has joined #openstack-meeting-305:15
*** marun is now known as marun_afk05:16
*** amitpp has joined #openstack-meeting-305:21
*** otherwiseguy has quit IRC05:21
*** eghobo has joined #openstack-meeting-305:30
*** shakamunyi has joined #openstack-meeting-305:31
*** shakamunyi has quit IRC05:32
*** shakamunyi has joined #openstack-meeting-305:32
*** amitpp has quit IRC05:35
*** briancurtin_away is now known as briancurtin05:37
*** otherwiseguy has joined #openstack-meeting-305:38
*** amitpp has joined #openstack-meeting-305:40
*** lcheng has quit IRC05:41
*** shakamunyi has quit IRC05:42
*** otherwiseguy has quit IRC05:42
*** briancurtin is now known as briancurtin_away05:47
*** otherwiseguy has joined #openstack-meeting-305:48
*** shakamunyi has joined #openstack-meeting-305:50
*** shakamunyi has quit IRC05:50
*** otherwiseguy has quit IRC05:52
*** eguz has joined #openstack-meeting-305:53
*** eghobo has quit IRC05:57
*** iovadia has joined #openstack-meeting-305:58
*** mrunge has joined #openstack-meeting-305:58
*** nati_ueno has quit IRC06:03
*** Sukhdev has quit IRC06:11
*** nati_ueno has joined #openstack-meeting-306:16
*** tmazur has joined #openstack-meeting-306:35
*** tmazur has quit IRC06:40
*** nati_ueno has quit IRC06:51
*** tmazur has joined #openstack-meeting-306:53
*** eguz has quit IRC06:55
*** jamiehannaford has joined #openstack-meeting-307:04
*** briancurtin_away is now known as briancurtin07:16
*** briancurtin is now known as briancurtin_away07:25
*** otherwiseguy has joined #openstack-meeting-307:26
*** otherwiseguy has quit IRC07:31
*** otherwiseguy has joined #openstack-meeting-307:32
*** otherwiseguy has quit IRC07:37
*** jcoufal has joined #openstack-meeting-307:38
*** yamamoto has quit IRC07:49
*** mestery has quit IRC07:51
*** lcheng has joined #openstack-meeting-307:53
*** mestery has joined #openstack-meeting-307:55
*** lsmola__ has joined #openstack-meeting-307:56
*** nacim has joined #openstack-meeting-308:02
*** ChanServ sets mode: +o SergeyLukjanov08:06
*** SergeyLukjanov changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:06
*** MaxV has joined #openstack-meeting-308:12
*** amitpp has quit IRC08:14
*** amitpp has joined #openstack-meeting-308:14
*** lcheng has quit IRC08:21
*** safchain has joined #openstack-meeting-308:25
*** lcheng has joined #openstack-meeting-308:26
*** otherwiseguy has joined #openstack-meeting-308:32
*** otherwiseguy has quit IRC08:36
*** yamamoto has joined #openstack-meeting-308:41
*** jamiehannaford has quit IRC08:44
*** jamiehannaford has joined #openstack-meeting-308:44
*** MaxV has quit IRC08:46
*** jcoufal has quit IRC08:48
*** yamamoto has quit IRC08:48
*** jamiehannaford has quit IRC08:52
*** MaxV has joined #openstack-meeting-308:53
*** yamamoto has joined #openstack-meeting-308:54
*** jamiehannaford has joined #openstack-meeting-308:56
*** Longgeek has joined #openstack-meeting-309:03
*** NikitaKo_ has joined #openstack-meeting-309:03
*** Longgeek has quit IRC09:03
*** Longgeek has joined #openstack-meeting-309:04
*** jtomasek has joined #openstack-meeting-309:06
*** jtomasek has quit IRC09:10
*** zz_johnthetubagu is now known as johnthetubaguy09:17
*** overlayer has joined #openstack-meeting-309:25
*** MaxV has quit IRC09:27
*** yamamoto has quit IRC09:28
*** MaxV has joined #openstack-meeting-309:29
*** jtomasek has joined #openstack-meeting-309:47
*** tomoe_ has quit IRC09:47
*** nacim has quit IRC09:48
*** stanzgy has quit IRC09:54
*** nacim has joined #openstack-meeting-309:58
*** briancurtin_away is now known as briancurtin09:58
*** yamamoto has joined #openstack-meeting-309:59
*** Longgeek has quit IRC10:03
*** Longgeek has joined #openstack-meeting-310:03
*** sankarshan is now known as sankarshan_away10:04
*** yamamoto has quit IRC10:06
*** Longgeek has quit IRC10:07
*** briancurtin is now known as briancurtin_away10:08
*** jcoufal has joined #openstack-meeting-310:13
*** stanzgy has joined #openstack-meeting-310:20
*** Longgeek has joined #openstack-meeting-310:21
*** lcheng has quit IRC10:22
*** MaxV has quit IRC10:23
*** NikitaKo_ has quit IRC10:24
*** lcheng has joined #openstack-meeting-310:27
*** tomoe_ has joined #openstack-meeting-310:40
*** sankarshan_away is now known as sankarshan10:45
*** tomoe_ has quit IRC10:46
*** tomoe_ has joined #openstack-meeting-310:51
*** yamamoto has joined #openstack-meeting-310:55
*** tomoe_ has joined #openstack-meeting-311:04
*** Longgeek has quit IRC11:10
*** Longgeek has joined #openstack-meeting-311:10
*** stanzgy has quit IRC11:11
*** tomoe_ has quit IRC11:12
*** otherwiseguy has joined #openstack-meeting-311:15
*** tomoe_ has joined #openstack-meeting-311:15
*** otherwiseguy has quit IRC11:19
*** MaxV has joined #openstack-meeting-311:23
*** coolsvap is now known as coolsvap|afk11:23
*** tomoe_ has quit IRC11:28
*** yamamoto has quit IRC11:35
*** julim has joined #openstack-meeting-311:45
*** briancurtin_away is now known as briancurtin11:47
*** amitpp has quit IRC11:50
*** markmcclain has joined #openstack-meeting-311:53
*** NikitaKo_ has joined #openstack-meeting-311:54
*** NikitaKo_ has quit IRC11:55
*** briancurtin is now known as briancurtin_away11:56
*** NikitaKo_ has joined #openstack-meeting-311:56
*** markmcclain1 has joined #openstack-meeting-311:59
*** markmcclain has quit IRC11:59
*** markmcclain1 has quit IRC12:02
*** Longgeek_ has joined #openstack-meeting-312:02
*** Longgeek has quit IRC12:06
*** Longgeek_ has quit IRC12:07
*** Longgeek has joined #openstack-meeting-312:08
*** banix has joined #openstack-meeting-312:10
*** otherwiseguy has joined #openstack-meeting-312:14
*** alexpilotti has joined #openstack-meeting-312:15
*** otherwiseguy has quit IRC12:18
*** lblanchard has joined #openstack-meeting-312:22
*** banix has quit IRC12:24
*** yamamoto has joined #openstack-meeting-312:30
*** stanzgy has joined #openstack-meeting-312:33
*** yamamoto_ has joined #openstack-meeting-312:34
*** yamamoto has quit IRC12:34
*** mestery has quit IRC12:35
*** mestery has joined #openstack-meeting-312:39
*** otherwiseguy has joined #openstack-meeting-312:39
*** erecio has joined #openstack-meeting-312:43
*** thomasem has joined #openstack-meeting-312:47
*** julim has quit IRC12:53
*** MaxV has quit IRC12:53
*** MaxV has joined #openstack-meeting-312:53
*** lenrow has quit IRC12:54
*** MaxV has quit IRC12:54
*** julim has joined #openstack-meeting-312:54
*** stanzgy has quit IRC12:56
*** kenhui has joined #openstack-meeting-312:58
*** MaxV has joined #openstack-meeting-313:01
*** mfer has joined #openstack-meeting-313:02
*** MarkAtwood has joined #openstack-meeting-313:08
*** yamamoto_ has quit IRC13:12
*** MarkAtwood has quit IRC13:13
*** MarkAtwood has joined #openstack-meeting-313:14
*** yamamoto has joined #openstack-meeting-313:14
*** MarkAtwood has quit IRC13:20
*** NikitaKo_ has quit IRC13:23
*** jackib has joined #openstack-meeting-313:24
*** peristeri has joined #openstack-meeting-313:29
*** julim has quit IRC13:34
*** prad has joined #openstack-meeting-313:35
*** briancurtin_away is now known as briancurtin13:35
*** julim has joined #openstack-meeting-313:35
*** peristeri has quit IRC13:36
*** lcheng has quit IRC13:37
*** lcheng has joined #openstack-meeting-313:38
*** jackib has quit IRC13:40
*** peristeri has joined #openstack-meeting-313:40
*** yamamoto has quit IRC13:45
*** tomoe_ has joined #openstack-meeting-313:46
*** prad has quit IRC13:47
*** kenhui has quit IRC13:49
*** kenhui has joined #openstack-meeting-313:50
*** kenhui has quit IRC13:50
*** armax has joined #openstack-meeting-313:50
*** thomasem has quit IRC13:50
*** kenhui has joined #openstack-meeting-313:51
*** lcheng has quit IRC13:53
*** amitpp has joined #openstack-meeting-313:57
*** NikitaKo_ has joined #openstack-meeting-313:58
*** mestery_ has joined #openstack-meeting-313:59
*** mestery has quit IRC14:00
*** mestery_ is now known as mestery14:00
*** xuhanp has joined #openstack-meeting-314:00
*** amitpp has quit IRC14:00
*** lcheng has joined #openstack-meeting-314:01
*** tomoe_ has quit IRC14:02
*** julim has quit IRC14:03
*** julim has joined #openstack-meeting-314:04
*** MarkAtwood has joined #openstack-meeting-314:07
*** MarkAtwood has quit IRC14:08
*** erecio has quit IRC14:10
*** tomoe_ has joined #openstack-meeting-314:16
*** thomasem has joined #openstack-meeting-314:18
*** NikitaKo_ has quit IRC14:25
*** kenhui has quit IRC14:25
*** yamamoto has joined #openstack-meeting-314:28
*** nelsnelson has quit IRC14:30
*** nelsnelson has joined #openstack-meeting-314:30
*** kenhui has joined #openstack-meeting-314:31
*** yamamoto has quit IRC14:32
*** jcoufal has quit IRC14:34
*** prad has joined #openstack-meeting-314:34
*** jtomasek has quit IRC14:36
*** jcoufal has joined #openstack-meeting-314:36
*** otherwiseguy has quit IRC14:44
*** armax has left #openstack-meeting-314:47
*** armax has joined #openstack-meeting-314:48
*** jtomasek has joined #openstack-meeting-314:50
*** mfer has quit IRC14:52
*** coolsvap|afk is now known as coolsvap14:53
*** mfer has joined #openstack-meeting-314:55
*** tomoe_ has quit IRC14:56
*** pgpus has joined #openstack-meeting-314:56
*** yisun has quit IRC14:58
*** yamamoto has joined #openstack-meeting-314:59
*** carl_baldwin has joined #openstack-meeting-315:01
*** jtomasek has quit IRC15:03
*** yamamoto has quit IRC15:04
*** jaypipes-GOOAL has quit IRC15:06
*** tmazur has quit IRC15:06
*** iovadia has quit IRC15:14
*** nacim has quit IRC15:16
*** MarkAtwood has joined #openstack-meeting-315:17
*** samchoi has joined #openstack-meeting-315:21
*** MaxV has quit IRC15:27
*** thomasem_ has joined #openstack-meeting-315:29
*** yamamoto has joined #openstack-meeting-315:29
*** thomasem has quit IRC15:30
*** hurgleburgler has joined #openstack-meeting-315:30
*** thomasem_ has quit IRC15:31
mfer#startmeeting openstack-sdk-php15:31
openstackMeeting started Wed Jul  2 15:31:26 2014 UTC and is due to finish in 60 minutes.  The chair is mfer. Information about MeetBot at http://wiki.debian.org/MeetBot.15:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:31
*** thomasem has joined #openstack-meeting-315:31
*** openstack changes topic to " (Meeting topic: openstack-sdk-php)"15:31
openstackThe meeting name has been set to 'openstack_sdk_php'15:31
mferIf you couple please state your name along with any applicable association15:31
mferMatt Farina, HP15:31
samchoiSam Choi, HP15:31
*** yisun has joined #openstack-meeting-315:32
*** MaxV has joined #openstack-meeting-315:32
*** cjellick has joined #openstack-meeting-315:33
mfersamchoi I'll give it a few more minutes and call it if no one else comes15:33
*** cjellick has quit IRC15:34
samchoimfer sure, sounds good15:34
*** cjellick has joined #openstack-meeting-315:34
*** pgpus has quit IRC15:34
mfersamchoi i'm calling it.15:36
mfer#endmeeting15:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:36
openstackMeeting ended Wed Jul  2 15:36:23 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-07-02-15.31.html15:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-07-02-15.31.txt15:36
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-07-02-15.31.log.html15:36
*** jcoufal has quit IRC15:42
*** otherwiseguy has joined #openstack-meeting-315:42
*** markmcclain has joined #openstack-meeting-315:45
*** briancurtin is now known as briancurtin_away15:49
*** nati_ueno has joined #openstack-meeting-315:50
*** pballand has joined #openstack-meeting-315:55
*** Sukhdev has joined #openstack-meeting-315:58
*** otherwiseguy has quit IRC15:58
*** pballand has quit IRC16:00
*** otherwiseguy has joined #openstack-meeting-316:00
*** mestery has quit IRC16:02
*** eghobo has joined #openstack-meeting-316:03
*** briancurtin_away is now known as briancurtin16:03
*** pballand has joined #openstack-meeting-316:03
*** banix has joined #openstack-meeting-316:06
*** eghobo has quit IRC16:08
*** eghobo has joined #openstack-meeting-316:08
*** armax has quit IRC16:08
*** lcheng has quit IRC16:10
*** coolsvap is now known as coolsvap|afk16:12
*** otherwiseguy has quit IRC16:16
*** xuhanp has quit IRC16:18
*** mestery has joined #openstack-meeting-316:19
*** MaxV has quit IRC16:20
*** jcoufal has joined #openstack-meeting-316:20
*** jackib has joined #openstack-meeting-316:24
*** overlayer has quit IRC16:28
*** tjones has joined #openstack-meeting-316:31
tjones#startmeeting novabugscrub16:31
openstackMeeting started Wed Jul  2 16:31:17 2014 UTC and is due to finish in 60 minutes.  The chair is tjones. Information about MeetBot at http://wiki.debian.org/MeetBot.16:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:31
*** openstack changes topic to " (Meeting topic: novabugscrub)"16:31
openstackThe meeting name has been set to 'novabugscrub'16:31
tjonesanyone here today?16:31
dansmith\o/16:31
tjoneshey dansmith :-D16:31
dansmithyo16:32
*** david-lyle has joined #openstack-meeting-316:32
*** vinay_yadhav has joined #openstack-meeting-316:32
tjonesso using the script that the infra team has been using, jogo's changes, and more changes from me i have a web page that helps with understanding issues like stale bugs, bugs in the wrong state, etc.  All i need is a place to host it.  do you know where the right place to do that would be?16:33
tjonessome external web server that openstack already has?16:33
dansmithlike, you have raw HTML?16:33
*** nati_ueno has quit IRC16:33
tjonesi have a json file with all of the bug data, html and javascript to parse it.16:33
dansmithah16:34
*** lsmola__ has quit IRC16:34
tjonesyeah - not a raw file that i can just post.  i need a web server16:34
dansmithI think most people just throw that kinda thing up on a personal machine, which I can surely do for you if you want16:34
tjonesit's a work in progress so i would want to tweak it.  I have something on aws i can use for this probably (blush)16:35
dansmithheh, okay16:35
tjoneswas hoping to have that done before the meeting today.  oh well.16:35
tjonesi've already tagged the untagged except a couple i could use a hand with.  they have to do with packaging and stuff16:35
tjones#link https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW16:36
tjones#link https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW16:36
tjonesoops16:36
tjones#link https://bugs.launchpad.net/nova/+bug/133607716:36
tjones#link https://bugs.launchpad.net/nova/+bug/133668416:36
dansmithheh, that one seems like it's a sles bug not something for us16:37
tjonesno wonder…  how do i give it to them?16:37
dansmithclose it as invalid and tell them to talk to suse?16:38
tjonesor - better - who does packaging for sles that i could ask to take a look?16:38
dansmithno idea16:38
tjonesok i'll try that.16:38
*** thangp has joined #openstack-meeting-316:39
dansmithjust marked the second one as incomplete and asked for some detail16:39
*** yisun has quit IRC16:40
tjonesthe limits one?16:40
dansmithyeah16:40
tjonesok so for new ones that don't have assignees - this ssh one looks like it needs some attention.16:41
tjoneshttps://bugs.launchpad.net/nova/+bug/129847216:41
tjonesi mean it is getting attention16:42
dansmithtjones: yeah, the ssh one is the top gate offender right now I think,16:42
dansmithand lots of people have it on their radar16:42
dansmithtjones: I also marked that one from phil with some detail and assigned it to him16:42
tjonesok great - that is really all to talk about util i get my page up for comments.  I think it will really help16:43
*** vinay_yadhav has quit IRC16:43
dansmithcool16:43
tjonesthanks for attending today.  any other bugs i should know about other than ssh?16:43
dansmithnot that I know of16:44
tjonesme either :-D16:44
*** pgpus has joined #openstack-meeting-316:46
tjonesgoing to end early then16:46
dansmithso are we done here?16:46
tjonesc ya16:46
dansmithsweet16:46
tjones#endmeeting16:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:46
openstackMeeting ended Wed Jul  2 16:46:40 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-07-02-16.31.html16:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-07-02-16.31.txt16:46
openstackLog:            http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-07-02-16.31.log.html16:46
*** otherwiseguy has joined #openstack-meeting-316:46
*** markmcclain has quit IRC16:48
*** markmcclain has joined #openstack-meeting-316:58
*** markmcclain has quit IRC16:58
*** markmcclain has joined #openstack-meeting-316:59
*** vinay_yadhav has joined #openstack-meeting-317:02
*** Longgeek has quit IRC17:02
*** otherwiseguy has quit IRC17:03
*** anil_rao has joined #openstack-meeting-317:04
*** otherwiseguy has joined #openstack-meeting-317:05
*** vinay_yadhav has quit IRC17:06
*** SumitNaiksatam has quit IRC17:09
*** garyduan has quit IRC17:09
*** garyduan has joined #openstack-meeting-317:10
*** thomasem has quit IRC17:10
*** dkehnx has joined #openstack-meeting-317:12
*** eghobo has quit IRC17:14
*** johnthetubaguy is now known as zz_johnthetubagu17:15
*** sankarshan is now known as sankarshan_away17:19
*** SridarK has joined #openstack-meeting-317:21
*** dkehn__ has joined #openstack-meeting-317:21
*** otherwiseguy has quit IRC17:21
*** dkehn__ has quit IRC17:23
*** dkehn__ has joined #openstack-meeting-317:24
*** SumitNaiksatam has joined #openstack-meeting-317:24
*** dkehnx has quit IRC17:25
*** vinay_yadhav has joined #openstack-meeting-317:26
*** dkehn__ is now known as dkehnx17:26
*** s3wong has joined #openstack-meeting-317:26
*** LouisF has joined #openstack-meeting-317:28
SumitNaiksatamhi Neutron Adv service team!17:30
s3wonghello17:30
banixhi17:30
vinay_yadhavHi17:30
marioso/17:30
cgoncalveshi, everyone17:30
LouisFhi17:31
SumitNaiksatams3wong banix vinay_yadhav cgoncalves: hi17:31
SumitNaiksatamok lets get started17:31
SumitNaiksatam#startmeeting Networking Advanced Services17:31
openstackMeeting started Wed Jul  2 17:31:25 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
anil_raoHi17: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
SumitNaiksatam#info agenda: https://wiki.openstack.org/wiki/Meetings/AdvancedServices17:31
dougwigo/17:31
vinay_yadhavcan we start with TaaS today17:31
SridarKHi17:32
SumitNaiksatam#info announcement: Juno specification submission deadline: July 10th, specification approval deadline: july 17th17:32
mariostapas for starter?17:32
cgoncalvesmarios: yeah, I'm starving :)17:32
s3wongYes, let's do tapas as a starter :-)17:32
vinay_yadhav:)17:32
banixjust a couple of minutes on flavor to get going ;)17:32
banixjust kidding17:32
*** briancurtin is now known as briancurtin_away17:32
SumitNaiksatamwe switch the agenda order today per last week’s request17:32
marioscgoncalves: me too mate just got home :)17:33
SumitNaiksatamso we have a week to submit any new blueprint specs (i think we are good here)17:33
*** songole has joined #openstack-meeting-317:33
SumitNaiksatamand we have a couple of weeks to converge on teh specs we have in review, and have them approved17:33
*** briancurtin_away is now known as briancurtin17:34
SumitNaiksatamthe later is of course subject to reviewer feedback17:34
enikanorov__here17:34
SumitNaiksatamwanted to make sure that everyone is aware of the time timelines17:34
s3wongSumitNaiksatam: sure17:34
SumitNaiksatamenikanorov__: hi, switiching the agenda order a bit today to be fair to everyone17:34
enikanorov__SumitNaiksatam: sure!17:34
vinay_yadhavthanx17:35
SumitNaiksatamok drumroll…17:35
s3wongenikanorov__: can't just have your flavor all the time :-)17:35
SumitNaiksatam#topic TaapAAS17:35
*** openstack changes topic to "TaapAAS (Meeting topic: Networking Advanced Services)"17:35
SumitNaiksatamhttps://review.openstack.org/#/c/9614917:35
SumitNaiksatam#link https://review.openstack.org/#/c/9614917:35
*** tjones has left #openstack-meeting-317:35
SumitNaiksatamvinay_yadhav: you have the stage!17:35
*** mwagner_ has quit IRC17:35
vinay_yadhavthe last patch(Patch 5) got good reviews17:36
mariosvinay_yadhav: apologies didnt get chance to review latest17:36
*** mandeep has joined #openstack-meeting-317:36
SumitNaiksatamvinay_yadhav: ok, my apologies i hae not been as active either17:36
*** pcm_ has joined #openstack-meeting-317:36
vinay_yadhavi have address some editorial comment and added afew clarification in the new patch17:36
SumitNaiksatami believe anil_rao has also been responding to the reviews17:36
anil_raoYes17:36
vinay_yadhavyes17:36
SumitNaiksatamone high level question - why do we have the “Tap_service” table?17:37
vinay_yadhavthat is the data model that represents the service17:37
vinay_yadhavto which u can add flows (ports) that u want to mirror17:37
SumitNaiksatamvinay_yadhav: can this not be collapsed into the “tap_flow"17:38
vinay_yadhavthe Tap_Service will set up the destination of the mirror17:38
SumitNaiksatamwe could call it something else17:38
mariosvinay_yadhav: there havent been any major objections so far right?17:38
SumitNaiksatammaybe just a tap17:38
vinay_yadhavyes no major objections17:38
vinay_yadhavsumit: ok, but collapsing is not good17:38
SumitNaiksatami would prefer to avoid proliferation of resources where we can17:39
SumitNaiksatamvinay_yadhav: why?17:39
SumitNaiksatamvinay_yadhav: unless there is no 1:1 association between tap_flow and tap_service17:39
vinay_yadhavbecause the Tap_Service sets up the destination port for mirrored data17:39
SumitNaiksatamvinay_yadhav: yeah, but its a 1:1 association with a tap_flow, right?17:39
vinay_yadhavcan there is a n:1 association between flow and service17:40
vinay_yadhavmultiple flows can be associated to a single service17:40
SumitNaiksatamvinay_yadhav: ah ok17:40
vinay_yadhavflow: ports u want to mirror17:40
vinay_yadhavservice: destination port to sent the mirroed data where a servicer VM can collect it17:40
vinay_yadhavhence its N:117:41
mariosvinay_yadhav: like monitoring more than one source port u mean?17:41
s3wonghost of event asks us to take a group photo. brb17:41
mariosto one service17:41
*** pballand has quit IRC17:41
vinay_yadhavmarios: yes17:41
SumitNaiksatamvinay_yadhav: ok, wasnt clear to be from the table17:41
vinay_yadhavu can check the work flow text.... but i will see if i can calrify it better17:42
mariosSumitNaiksatam: is there a process whereby we can say 'ok we have worked this spec tbrough a few iterations can we now have some core attention'?17:42
vinay_yadhavmarios: yes that would be good17:42
anil_raoAlso, separating the tap-service from the tap-flow means that we can add/remove flows from the service17:42
SumitNaiksatammarios: no forma process, but thats why i wanted that as a team we support our specs by putting a +117:42
SumitNaiksatam*formal17:42
vinay_yadhavanil:true17:42
mariosSumitNaiksatam: 17th july isnt that far off especially if there will be any unexpected issues17:42
vinay_yadhavon the 5th patch set we had a 8-9 +1s17:43
*** chuckC has quit IRC17:43
*** badveli has joined #openstack-meeting-317:44
vinay_yadhavso if every one can review it once more and +1 it, that wold be greate17:44
SumitNaiksatamvinay_yadhav: currently one +1, so hopefully we can get those +1s back17:44
vinay_yadhavsumit: yeah17:44
SumitNaiksatamvinay_yadhav anil_rao: any blockers on this (apart from reviewer attention)?17:45
vinay_yadhavi hope people go over it again and +1 it again17:45
mariosvinay_yadhav: will do hopefully tomorrow17:45
vinay_yadhavnot at this point17:45
vinay_yadhavmarios: thanx17:45
banixvinay_yadhav: will do17:45
anil_raoNo blockers at the moment, Sumit17:45
SumitNaiksatamvinay_yadhav: ok thanks17:45
vinay_yadhavthanx17:45
*** cathy_ has joined #openstack-meeting-317:45
banix(By the way, Ryan apologizes for not being able to participate today)17:45
SumitNaiksatam#topic Traffic steering17:46
*** openstack changes topic to "Traffic steering (Meeting topic: Networking Advanced Services)"17:46
SumitNaiksatam#link https://review.openstack.org/#/c/9247717:46
SumitNaiksatamcgoncalves: hi17:46
*** pballand has joined #openstack-meeting-317:46
cgoncalvesSumitNaiksatam: hello17:46
SumitNaiksatamcgoncalves: thanks to you (and joao) for the follow up  on this17:46
cgoncalvesSumitNaiksatam: do you want first to summarize yesterday's F2F meeting?17:46
banixwhose face 2 whose face?17:47
SumitNaiksatamcgoncalves: sure, this was mostly to get Cathy and LouisF upto speed with what we are doing in the adv services’s team, and where the different blueprint specs17:47
SumitNaiksatambanix: ^^^17:47
banixgot it17:47
cgoncalvesSumitNaiksatam: sure, no problem. not sure you all got my view I stressed on -dev last week17:47
cgoncalvesbanix: oops, it was a secret f2f. you wasn't supposed to know it :)17:48
SumitNaiksatamcathy_ and LouisF: had questions on the use of classifiers in teh group policy spec versus in the TS spec17:48
cgoncalvesSumitNaiksatam: ok17:48
SumitNaiksatambut nothing that we have not discussed in this IRC before17:49
banixcgoncalves: I was there. I work for NSA ;)17:49
SumitNaiksatambanix: and i thought i could you out by not inviting you :-P17:49
cgoncalves:)17:49
LouisFcgoncalves: can you state the concerns you raised in your email17:50
SumitNaiksatamcgoncalves: go ahead ^^^17:50
LouisFcgoncalves: regarding steerings17:50
banixjust wanted to know if i missed a call i was supposed to be on. thanks for not including me when not necessary.17:50
cgoncalvesSumitNaiksatam: ok, my idea was that the f2f was to also get to some aggreement on the TS and SC blueprints and you would eventually give us some feedback17:50
s3wongback17:50
SumitNaiksatamcgoncalves: mandeep has a new planned on the chaining spec, which will hopefully help17:51
SumitNaiksatam*new rev17:51
cathy_cgoncalves: The conclusion is that  the GBP group classifier applies at the ingress point of the chain. The TS classifier can be applied for reclassification use. If there are inconsistency between the two classifiers, the TS classifier takes precedence17:51
SumitNaiksatamcathy_: thanks17:51
cgoncalvesLouisF: in short, TS may not be the best way to use as backend of SC, although it can be used but putting some constraints17:52
mandeepSumitNaiksatam: cgoncalves: Yes I will clarify in the spec as cathy_ explained.17:52
LouisFmandeep: when can we get the updated bp?17:52
mandeepcgoncalves: Yes, I am working on it today17:53
SumitNaiksatamin general we dont expect the reference implementation of Group Policy to directly use the Traffic Steering classifier17:53
*** armax has joined #openstack-meeting-317:53
banixwill wait for the spec as what cathy_ said just doesn’t make sense to me17:53
cgoncalvesLouisF: and AFAIK there is no way defined yet as to how traffic should be steered to a SC17:53
cgoncalves(sorry, intermitent connection)17:53
cgoncalvesmandeep: nice, thanks17:53
LouisFcgoncalves: agree i thinkthe ts bp needs work17:53
mandeepbanix: Essentially what service or TS does in opaque to the GBP - it just forwards the packets to the appropriate port17:54
cgoncalvescathy_: ok, thanks.17:54
*** otherwiseguy has joined #openstack-meeting-317:54
cgoncalvesI've been this week internally getting some code working (based on the ones submitted to review.o.o) and interacting with ODL17:55
cathy_cgoncalves: Actually I read the existing service chaining blueprint again after the f-f meeting. It seems that the only difference bwtween the service chain BP API and the TS API is that the TS include Classifier specification. Is that correct?17:55
banixmandeep: yes that was my understanding. i thought the staement above was contradicting that but dont want to distract. will look at the specs.17:55
mandeepbanix: ok17:55
cgoncalvesthat's for PoC internally and I believe could all code be open-sourced (on the ODL side too)17:55
SumitNaiksatamcathy_: as we discussed that is not the only difference, the difference is at the level of abstraction17:55
SumitNaiksatamcathy_: service chain bp deals with chain service instances17:56
cgoncalvescathy_: I believe so, yes.17:56
cgoncalvesSumitNaiksatam: sure17:56
SumitNaiksatamcathy_: whereas, TS bp deals with chaining ports17:56
cathy_From the API point of view, it seems that is the diff. Maybe internal design has difference.17:56
SumitNaiksatamcgoncalves: at this point we have -1 from cathy_ and akihiro17:57
SumitNaiksatamcathy_: are your concerns addressed?17:57
cgoncalveswhile SC could potentially spin new neutron services and create a chain, the TS doesn't17:57
*** Sukhdev has quit IRC17:58
SumitNaiksatamcgoncalves: i think SC operation will be clarified in mandeep’s new rev of the spec17:58
cathy_cgoncalves: Does the SC API covers the spin of new neutron services ? I did not see this in the API17:58
SumitNaiksatamcgoncalves: but should be independent of the TS bp, so we can make progress in paralled17:58
cathy_Maybe I missed that part.17:58
SumitNaiksatam*parallel17:58
cgoncalvesall: I know I've some comments from you to catch up. sorry about that. I've been reviewing them but not commenting on review.o.o due to some time constraints on my end. truly apologies17:58
mariossorry for the silly question, but for clarity... SC = service chaining and TS is traffic steering right?17:58
SumitNaiksatammarios: yes17:58
mandeepmarios: Correct17:58
cathy_SumitNaiksatam: My concern about classifers are addressed. Thanks for asking17:59
cgoncalvescathy_: I'm not sure. just said it could *eventually*. we will have to wayt for mandeep to upload a new rev17:59
SumitNaiksatamcgoncalves: no need to apologize, you have been very prompt and sincere on this, big thanks for leading this initiative!17:59
cathy_marios: yes17:59
cgoncalvesSumitNaiksatam: of course, we can work independently17:59
mandeepcgoncalves: I will do so today. I got occupied by the 'day job' for a couple of weeks, catching up now ;-)18:00
cathy_cgoncalves: OK, I will review the new version.18:00
SumitNaiksatamcgoncalves: we might need to indepedently reach out to akihiro to see if his concerns are addressed18:00
cgoncalvescathy_: thanks18:00
*** pballand has quit IRC18:00
LouisFmandeep: great18:00
SumitNaiksatammandeep: thanks, we fully understand :-)18:00
mandeepSumitNaiksatam: ;-)18:00
cgoncalvesSumitNaiksatam: yeah, as he is a core reviewer \o/ :)18:00
SumitNaiksatamany other questions or suggestions for cgoncalves?18:01
SumitNaiksatamcgoncalves: ;-P18:01
cgoncalvesbring them on! (but be gentle though)18:01
LouisFcgoncalves: when will you update the bp?18:01
cathy_cgoncalves: very good work and good points in your email.18:01
SumitNaiksatamcathy_: +118:01
*** gduan has joined #openstack-meeting-318:01
cgoncalvesLouisF: lets say this week18:02
*** mestery has quit IRC18:02
*** gduan has quit IRC18:02
SumitNaiksatamcgoncalves: great thanks!18:02
SumitNaiksatam#topic Service base definition and Insertion18:02
*** openstack changes topic to "Service base definition and Insertion (Meeting topic: Networking Advanced Services)"18:02
SumitNaiksatams3wong: ?18:02
s3wongyes18:02
SumitNaiksatami believe kanzhe is not back yet18:02
SumitNaiksatam#link https://review.openstack.org/#/c/9312818:03
*** otherwiseguy has quit IRC18:03
SumitNaiksatams3wong: you posted a new rev, thanks18:03
SumitNaiksatamnot sure how many got a chance to review18:03
s3wongSome of us had a f2f meeting on Monday - and the team-members suggested a set of feedback for update18:03
SumitNaiksatami had put some comments on monday18:03
s3wongso the spec has been updated to reflect those points18:03
SumitNaiksatamto narrow the scope of this18:03
s3wongwe also drop flavor framework as a dependency (because it really isn't)18:04
SumitNaiksatams3wong: i will read through again (see some white spaces in red though ;-) )18:04
mariosSumitNaiksatam: i only saw your comments in passing today,but, will it still make sense without e.g. register/unregister service?18:04
* marios will look more closely tomorrow18:05
SumitNaiksatami believe people will need some time to read through the new rev18:05
s3wongSumitNaiksatam: yes, I noticed that after I uploaded. And since I will do another patch update due to not addressing some comments at revision 13, I will fix them on the next patch :-)18:05
SumitNaiksatammarios: per discusison with kanzhe and s3wong the register/unregister is something we can add as an enhancement in a later rev18:05
*** nati_ueno has joined #openstack-meeting-318:05
s3wongmarios: yes, the register/unregister were intended to support services that aren't aware by Neutron (non Neutron network services)18:06
SumitNaiksatammarios: since it was targeted more specifically at services not recognized by neutron18:06
s3wongbut still can do service insertion with the proposed framework18:06
SumitNaiksatammarios: i fully agree with the goal here, however, we need to focus on what we want to achieve as a first iteration18:06
s3wongbut SumitNaiksatam suggested that we should simplify and NOT address this use case in phase 118:06
s3wongand we all agreed18:06
mariosSumitNaiksatam: i see... yes i recall now that the point was '(neutron) services are already assumed available... e.g. via flavor framework'18:06
SumitNaiksatammarios: and make this very easy for the core reviewers to review and approve in the short time we have left18:06
*** ivar-lazzaro has joined #openstack-meeting-318:07
SumitNaiksatammarios: yes what s3wong said her18:07
mariosSumitNaiksatam: ok thanks i will try and look more closely tomorrow.18:07
SumitNaiksatamfor the record (and to put timelines into context), the service insertion discussion has been going for well over two years now, and we still dont have anything which begins to address this18:08
*** songole has quit IRC18:08
marioss3wong: sorry, am on mobile and the screen is pretty small... i miss a lot of stuff here18:08
s3wongyes - for all the previous reviewers who gave +1s, please review again :-)18:08
*** songole has joined #openstack-meeting-318:08
SumitNaiksatamhence we need to make sure that we make progress18:08
banixs3wong: you said you will have a new patch soon?18:08
s3wongfor those who wanted to give +1s, please also review :-)18:08
s3wongbanix: yes, just minor comments - but I would encourage reviewers to look at current revision and give comment18:09
s3wongthat way I can address them also18:09
SumitNaiksatams3wong: i believe marios volunteered for teh vpnaas piece18:09
banixs3wong: ok thx18:09
marioss3wong: there is code already?18:10
SumitNaiksatams3wong: can you add him to the assignees? i think marios had requested it18:10
s3wongSumitNaiksatam: yes - that is one of the revision 13 comments that I missed - add marios as a team-member, I will make that change18:10
marioss3wong: i noticed that :)18:10
s3wongmarios: yes, Kanzhe will upload the preliminary DB model changes soon18:10
* marios hurt18:10
SumitNaiksatams3wong: thanks, ah it was the earlier rev comment, got it18:10
*** mestery has joined #openstack-meeting-318:10
marioss3wong: great thanks18:10
SumitNaiksatammarios: dont worry, i got your back :-P18:11
mariosSumitNaiksatam: hehe thanks :)18:11
SumitNaiksatamall please, review this spec, this has to be a prirority for us as a team18:11
SumitNaiksatamnow our favorite topic18:12
SumitNaiksatam#topic Flavors18:12
*** openstack changes topic to "Flavors (Meeting topic: Networking Advanced Services)"18:12
cgoncalvesSumitNaiksatam: ok18:12
enikanorov__hi18:12
enikanorov__markmcclain: hi18:12
LouisFs3wong: when will Kanzhe post the update?18:13
s3wongLouisF: before Friday for sure :-)18:13
SumitNaiksatam#link https://review.openstack.org/#/c/90070#link https://review.openstack.org/10272318:13
*** pballand has joined #openstack-meeting-318:13
enikanorov__so I've made two suggestions on Mark's proposal which I think will make it as simple as possible and implementable in juno18:13
SumitNaiksatamenikanorov__: thanks18:13
SumitNaiksatamso for those who missed the party, we had a dedicated IRC meeting on Friday18:14
enikanorov__basically, I'd like to merge 'profiles' approach with providers18:14
SumitNaiksatamto discuss the flavors topic18:14
*** mestery_ has joined #openstack-meeting-318:14
enikanorov__and also i seems that extension list on a flavor is not necessary for various reasons18:14
SumitNaiksatam#link http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-06-27-17.30.log.html18:14
*** mestery has quit IRC18:14
enikanorov__i have left inline comments there as well as generic comment18:14
*** shakamunyi has joined #openstack-meeting-318:14
SumitNaiksatamenikanorov__: okay18:14
enikanorov__basically we need markmcclain to respond...18:15
SumitNaiksatamenikanorov__: do you anticipate we will need another IRC meeting for this? :-P18:15
SumitNaiksatamon 4th of July, may be? ;-P18:15
s3wongSumitNaiksatam: your idea of (forced) quick resolution?18:15
s3wong:-)18:15
mariosenikanorov__: is the idea to start converging on one of the two open reviews and abandon the other?18:15
enikanorov__I would not mind, but if markmcclain agrees with my comments we'll have a consensus18:15
enikanorov__marios: something like that18:16
SumitNaiksatamjokes apart, i think we have limited time18:16
enikanorov__although i'd treat tag-based proposal as further development of the idea18:16
SumitNaiksatamenikanorov__: i believe we agreed on that during the IRC meeting discussion18:16
enikanorov__that's all from my side18:16
enikanorov__SumitNaiksatam: yes18:17
SumitNaiksatamenikanorov__: i guess we need to assess the progress on a day to day basis, since we are short on time18:17
SumitNaiksatamenikanorov__: will you be implementing the eventual spec?18:17
enikanorov__do you mean the spec itself?18:18
*** marun_afk is now known as marun18:18
SumitNaiksatamenikanorov__: i meant the code18:18
mariosftr.. here is the meeting log from friday (didn't know it existed till i saw the mailing list this afternoon) http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-06-27-17.30.log.html18:18
enikanorov__well, yes, I'd like to implement whatever is the consensus18:18
*** amitpp has joined #openstack-meeting-318:19
SumitNaiksatammarios: i did post that earlier in the thread (if you scroll up)18:19
mariosSumitNaiksatam: oh my apologies!18:19
marios(was a pita to find on mobile as well!!)18:19
SumitNaiksatammarios: no worries, i guessed as much18:20
SumitNaiksatamenikanorov__: ok, perhaps if you have cycles, may be you can start updating your earlier PoC patch with what has been agreed upon18:20
SumitNaiksatamenikanorov__: just thinking loud here18:20
enikanorov__SumitNaiksatam: oh, sure, in fact i've already started the coding, but halted it once we continued the discussion18:21
enikanorov__ok18:21
SumitNaiksatamenikanorov__: fully understand, and thanks!18:21
*** mestery_ has quit IRC18:21
SumitNaiksatamany other questions for enikanorov__ or markmcclain?18:21
*** mestery has joined #openstack-meeting-318:21
SumitNaiksatamok moving on18:22
SumitNaiksatam#topic Service Chaining18:23
*** openstack changes topic to "Service Chaining (Meeting topic: Networking Advanced Services)"18:23
SumitNaiksatam#link https://review.openstack.org/#/c/9352418:23
SumitNaiksatami know we already discussing this18:23
SumitNaiksatamin case if there are any lingering questions for mandeep18:23
mandeepI have responded to all questions on the review, and I will be posting a new BP today18:23
SumitNaiksatammandeep: or any blockers at your end (apart from your day job time constraints ;-P)18:23
*** badveli has quit IRC18:24
SumitNaiksatammandeep: great18:24
mandeepNo, I am good for now.18:24
SumitNaiksatammandeep: thanks!18:24
LouisFmandeep: is config going to be removed from serviceNode?18:24
*** badveli has joined #openstack-meeting-318:24
*** pballand has quit IRC18:24
cgoncalvesmandeep: will the new BP rev describe how one can use a chain? i.e., how traffic should be sent to a chain18:25
*** Kanzhe has joined #openstack-meeting-318:25
mandeepI was hoping to leave it in for use in future (say to define a service not yet specified in neutron), but I can add that when that use case shows up18:25
mandeepOs that can be in a a vendor extension as well18:25
cgoncalvesmandeep: ok18:25
mandeepcgoncalves: Yes, I am adding an example18:26
LouisFmandeep: a ServiceInstance can be associated with many chains - right?18:26
cathy_mandeep: If your BP can describe the service instances more clearly, that will be good, especially how they are used in the API18:26
mandeepLouisF: Correct18:26
mandeep(now called ServiceChainSpec or, ServiceChainFalvour)18:26
*** mestery has quit IRC18:26
mandeepcathy_: OK18:27
LouisFmandeep: why is there a single chain in ServiceInstance?18:27
LouisFmandeep: should be a list of chains?18:27
cgoncalvesLouisF, mandeep: I guess the tricky part with shared services is how to separate the waters18:27
cathy_mandeep: thx. Also how the service instance correlate to the ports speficied in the API table18:27
mandeepPointer to the ServiceChainSpec that it was created from.18:27
*** mestery has joined #openstack-meeting-318:28
mandeepLouisF: Pointer to the ServiceChainSpec that it was created from.18:28
mandeepLouisF: A specific Instance is only created from a single chain spec18:28
* SumitNaiksatam hoping that we are still on track to finish on time for once today18:29
s3wongSumitNaiksatam: one minute :-)18:29
LouisFmandeep: I'm confused18:29
SumitNaiksatams3wong: and counting down18:29
SumitNaiksatammandeep: perhaps a quick reponse and we can wrap it up here18:29
mandeepcgoncalves: service-chain conveniently hands that problem to the provider (say traffic steering) and just specifies the expected semantics18:29
SumitNaiksatamLouisF: we can follow up on the spec of offline18:30
LouisFSumitNaiksatam: will do18:30
SumitNaiksatamLouisF: thanks!18:30
SumitNaiksatammandeep: thanks for the update18:30
mandeepLouisF: Let me post the updated BP and we can review that18:30
LouisFmandeep: ok18:30
mandeepSumitNaiksatam: Sure18:30
SumitNaiksatamlets call it a wrap for today (still a minute over)18:30
banixbye everybody18:30
s3wongSumitNaiksatam: is progress :-)18:31
SumitNaiksatamthanks all, keep up the great work (both on writing the specs/code and the reviews)18:31
*** jamiehannaford has quit IRC18:31
s3wongbye18:31
cgoncalvesmandeep: I know :) hence my comment on that the TS bp is limited by not been able to attend that requirement18:31
SumitNaiksatambye18:31
cathy_bye everyone18:31
SumitNaiksatam#endmeeting18:31
cgoncalvescya!18:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:31
openstackMeeting ended Wed Jul  2 18:31:13 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-07-02-17.31.html18:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-07-02-17.31.txt18:31
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-07-02-17.31.log.html18:31
*** chuckC has joined #openstack-meeting-318:31
*** anil_rao has left #openstack-meeting-318:31
*** cathy_ has quit IRC18:31
SumitNaiksatamhappy 4th of july to those in the US!18:31
vinay_yadhavbye18:31
mariosgoodnight all18:31
s3wongSumitNaiksatam: well, I will still see you on the channel tomorrow :-)18:31
cgoncalveshappy birthday OpenStack!18:31
mandeepcgoncalves: I will follow up on that with you offline, OK?18:31
cgoncalvesmandeep: sure18:31
SumitNaiksatams3wong: but of course :-)18:31
mandeepHappy Birthday!18:32
pcm_bye18:32
banixgroup hug18:32
SumitNaiksatammandeep: :-)18:32
*** vinay_yadhav has quit IRC18:32
* mandeep group hug ;-)18:32
SumitNaiksatambanix: sure, and s3wong i believe will raise that with a group photo as well :-P18:32
mandeepbye18:32
* s3wong group hugging...18:32
banixhahaha18:32
*** jamiehannaford has joined #openstack-meeting-318:32
SumitNaiksatamhi Neutron FWaaS team!18:32
SridarKHi All18:33
badvelihello18:33
pcm_hi18:33
SumitNaiksatamSridarK garyduan yisun badveli: hi!18:33
SumitNaiksatampcm_: hi18:33
*** mandeep has left #openstack-meeting-318:33
*** songole has left #openstack-meeting-318:33
SumitNaiksatamis Karthik on today?18:33
SumitNaiksatamanyway, lets get started18:33
SumitNaiksatam #startmeeting Networking FWaaS18:34
SumitNaiksatam #info agenda https://wiki.openstack.org/wiki/Meetings/FWaaS18:34
SumitNaiksatam #topic Action Item follow up18:34
SumitNaiksatamSridarK was to start an email thread with FWaaS team and SridharGaddam regarding https://review.openstack.org/#/c/9057518:35
SumitNaiksatamSridarK:  i believe you already did that, thanks!18:35
*** mestery_ has joined #openstack-meeting-318:35
SridarKSumitNaiksatam: yes - actually we also have another patch out18:35
*** mestery has quit IRC18:35
SumitNaiksatami dont think SridharGaddam is on18:35
SridarKand i think this should address the concerns18:35
SumitNaiksatamSridarK: yes, i noticed that, however i have not had a chance to review18:35
SumitNaiksatamSridarK: nice18:35
SumitNaiksatambeyounn was to follow up with nati_ueno and amotoki, request them to review #link https://review.openstack.org/#/c/9413318:36
SumitNaiksatami think he did that18:36
SumitNaiksatamgaryduan: yi not around today?18:36
SumitNaiksatamor badveli: ^^^ ?18:36
SumitNaiksatamSumitNaiksatam was to respond to beyounn’s email thread on service objects review, however i did not do that18:36
badveliyes, beyounn had send a reminder18:36
SumitNaiksatambut i have brought this up with the PTL18:37
nati_uenohi18:37
SumitNaiksatambadveli: yes, i know18:37
SumitNaiksatamnati_ueno: hi18:37
nati_uenoSorry I didn't reviewd 94133 yet18:37
SridarKSumitNaiksatam: i will also go back and review the latest patch - will get that done today18:38
SumitNaiksatamnati_ueno: no problem, as long as its on your radar :-)18:38
SumitNaiksatamnati_ueno: in general, are you comfortable with the idea?18:38
*** overlayer has joined #openstack-meeting-318:39
nati_uenoSumitNaiksatam: sure!18:39
SumitNaiksatamnati_ueno: i think its pretty straightforward18:39
SumitNaiksatamnati_ueno: thanks18:39
SumitNaiksatambeyounn was to send DVR issues related to -dev mailer18:39
SumitNaiksatamwhich i think he already did18:39
*** s3wong has quit IRC18:40
SumitNaiksatambadveli: the reason i was asking for yi is i wanted to check if there was any resolution to this18:40
SumitNaiksatamwe will this discuss this as a separate agenda item18:40
SumitNaiksatamSumitNaiksatam SridarK were to check with owner of https://bugs.launchpad.net/neutron/+bug/132329918:40
SumitNaiksatamSridarK: we havent done this, but not a priority i guess?18:40
SridarKSumitNaiksatam: i think we can close this as u have put a comment on the bug18:41
SumitNaiksatamah, this is the one where i put a comment18:41
SumitNaiksatamSridarK: yeah, ok for now18:41
SridarKclearly indicating that this is working as designed18:41
*** amitpp has quit IRC18:41
SridarKSumitNaiksatam: yes agreed - we also want to look longer term18:41
SumitNaiksatamSridarK: agreed18:41
SumitNaiksatamSridarK SumitNaiksatam were to triage new/undecided bugs18:41
SridarKSumitNaiksatam: we are okay on this18:42
SumitNaiksatamSridarK: sorry i dropped the ball a little bit on this, but you were following up18:42
SridarK2 new bugs from last week18:42
SridarKSumitNaiksatam: no worries  - u have too many things going on18:42
SridarKEugene has picked up one of those18:43
SumitNaiksatamSridarK: so no high or critical priority, right?18:43
SumitNaiksatamSridarK:  ok18:43
SumitNaiksatamSridarK: link?18:43
SridarK#link https://bugs.launchpad.net/neutron/+bug/133498118:43
SumitNaiksatamSridarK: ah right on cue :-)18:43
SridarK:-)18:43
SridarKassigned to enikanorov__ by himself18:43
SridarKthis looks valid18:43
SridarKif enikanorov__ is busy, i can also take a look18:44
SumitNaiksatamSridarK: sure, lets follow up18:44
SridarKok18:44
SridarKthe next18:44
SridarK#link https://bugs.launchpad.net/neutron/+bug/133665218:44
*** nati_ueno has quit IRC18:44
SumitNaiksatami think in general, our shared semantics and implementation need a revisit18:44
SridarKSumitNaiksatam: yes we should discuss more on this18:45
SumitNaiksatam#action SridarK to follow up with enikanorov__ on https://bugs.launchpad.net/neutron/+bug/133498118:45
*** nati_ueno has joined #openstack-meeting-318:45
SridarKon, #link https://bugs.launchpad.net/neutron/+bug/133665218:45
SridarKhave put a comment18:45
SridarKthis is similar to #link https://bugs.launchpad.net/neutron/+bug/131085718:45
SridarKwhich is being addressed by SridharGaddam18:45
*** NikitaKo_ has joined #openstack-meeting-318:46
SumitNaiksatamSridarK: nice follow up on this!18:46
SridarKnp at all18:46
SumitNaiksatamSridarK: i completely agree with your assessment18:46
SridarKonce we get a response from the submitter - perhaps we can Dup this18:46
SumitNaiksatamSridarK: sure18:47
*** eghobo has joined #openstack-meeting-318:47
SumitNaiksatamSridarK was to revisit discussion on router delete18:47
SridarKSumitNaiksatam: the bug has been updated with comments18:47
*** LouisF has quit IRC18:47
SumitNaiksatamSridarK: i think this is on hold for now until service insertion spec is approved, right?18:47
SridarKSumitNaiksatam: yes18:47
SumitNaiksatamSridarK: ok thanks18:47
*** eghobo has quit IRC18:47
SridarKwe will address this in that context18:47
*** Youcef has quit IRC18:47
*** eghobo has joined #openstack-meeting-318:48
SumitNaiksatamprad was to put a fwaas bp for hit counts18:48
SumitNaiksatamprad: there?18:48
pradSumitNaiksatam, hi18:48
SumitNaiksatamprad: hi18:48
SumitNaiksatamprad: so SridarK might have already updated you on this18:49
*** ttrifonov is now known as ttrifonov_zZzz18:49
SumitNaiksatamprad: the FWaaS team is fully behind you on this18:49
*** yamamoto has quit IRC18:49
SumitNaiksatamprad: however it does not seem like anyone will have time before july 10th to put a spec in18:49
*** overlayer has quit IRC18:49
pradyes, he mentioned the conversation you guys had last week18:49
*** thomasem has joined #openstack-meeting-318:49
SumitNaiksatamprad: so in case you have the time, you can put the spec18:49
*** overlayer has joined #openstack-meeting-318:50
*** armax has quit IRC18:50
SumitNaiksatamprad: else we will have to punt this to a later time (in which case it will not make it for juno)18:50
*** thomasem has quit IRC18:50
pradSumitNaiksatam, so would the spec be for a specific backend or more toward how the api will look?18:50
*** thomasem has joined #openstack-meeting-318:50
SumitNaiksatamprad: the spec would have to cover the refernece impl backend18:51
*** ttrifonov_zZzz is now known as ttrifonov18:51
SumitNaiksatamprad: but perhaps not in extreme detail18:51
SumitNaiksatamprad: perhaps Rajesh can also help on writing the reference impl part18:51
SumitNaiksatamprad: but we dont mean to push you too hard18:52
pradSumitNaiksatam, hmm ok, so based on some recent updates, we're asked to look more closely into CSR vs iptables.. so the API would still be the same, but the focus is probably toward a vendor specific backed rather than iptables18:52
*** cjellick has quit IRC18:52
pradhow is that handled.. would that be a separate spec?18:52
SumitNaiksatamprad: right18:52
SumitNaiksatamprad: the spec which introduces the API, would also refernce the iptables implementation18:52
*** cjellick has joined #openstack-meeting-318:52
SumitNaiksatamprad: and we will need a separate spec which can address the CSR18:52
SumitNaiksatamprad: that said, if there is an existing CSR spec in review, we can perhpas bolt it on top of that18:53
*** mfer has quit IRC18:53
pradSumitNaiksatam, ok, I'll see if i can get more details on the car side of things before july 10th.. if so i'll put in a spec with that info.. might need help on iptables side18:53
*** cjellick has quit IRC18:53
SumitNaiksatamprad: but the vendor bp should not be so much of an issye18:53
SumitNaiksatam*issue18:53
pradok18:53
*** cjellick has joined #openstack-meeting-318:53
*** nati_uen_ has joined #openstack-meeting-318:53
SumitNaiksatamprad: the other option is to just propose this as a purely vendor extension18:54
*** chuckC has quit IRC18:54
pradSumitNaiksatam, hmm ok18:54
SumitNaiksatamprad: not the preferred option though18:54
*** NikitaKo_ has quit IRC18:54
badvelisumit sorry to interrupt as we have limited time, i am going to submit a patch with the service group bp, cli and the database as the initial one, as service group is an independent one it will not have any affect and we can move quickly on this18:55
SumitNaiksatamprad: only mentioned that, if you, as a vendor, want to make faster progress (and willing to redo this if the community moves in a different direction later)18:55
SumitNaiksatambadveli: yes sure18:55
SridarKSumitNaiksatam: i think this is the approach that may work18:55
badvelithanks sumit18:55
SumitNaiksatambadveli: we have service group as a separate agenda item18:55
pradSumitNaiksatam, ok i'll discuss with Rajesh and Sridar and get back to you18:56
SumitNaiksatamprad: thanks18:56
SumitNaiksatambadveli: just doing the action item follow up right now :-)18:56
badveliyes18:56
badvelithanks sumit18:56
SumitNaiksatambtw i forgot to mention at the outset -18:56
SridarKSumitNaiksatam: badveli wants get his first patch pushed :-)18:56
*** nati_ueno has quit IRC18:56
SumitNaiksatam#info announcement Juno specification submission deadline: July 10th, specification approval deadline: july 17th18:56
SumitNaiksatamSridarK: i do feel badveli’s excitement! :-)18:57
SumitNaiksatamok moving on18:57
SridarK:-)18:57
*** chuckC has joined #openstack-meeting-318:57
SumitNaiksatam#topic Bug18:57
badvelibeyounn is already following on the bp18:57
*** jackib has quit IRC18:58
SumitNaiksatamSridarK: so anything else that we need to cover, apart from that in the action item follow up?18:58
SridarKSumitNaiksatam: i think we are done with the bugs nothing else to add18:58
*** thomasem has quit IRC18:58
SumitNaiksatamSridarK: ok thanks18:58
SumitNaiksatam#topic Service Objects18:58
SumitNaiksatamso we are still in the spec review on this18:58
SumitNaiksatamwe have reached out to the cores, so hopefully we should get this approved before july 17th18:59
SumitNaiksatambadveli: you wanted to update on the implementation?18:59
badvelii am also hoping18:59
badveliyes i have the patch set18:59
badveliand unit tests are run18:59
badvelihopefully we should be able to get in juno19:00
badvelisecond set will be the referece implementation19:00
badvelithanks for your help19:00
*** thomasem has joined #openstack-meeting-319:01
SumitNaiksatambadveli: links?19:01
badvelii will be able to send it as soon as possible, not yet submitted the patch19:02
SumitNaiksatambadveli: ah ok, sorry i misunderstood19:02
badvelishould i send it to the team? will be adding the team as reviewere19:02
SumitNaiksatambadveli: nice to send a head up email to the team (if you find it convenient)19:03
SumitNaiksatam*heads up19:03
badveliok, thanks will do19:03
SumitNaiksatambadveli: anything blocking you right now (apart from the review progress on the spec)?19:03
badvelinothing much, just implemented as per the spec19:04
badveliif anything  on the spec we will add19:04
SumitNaiksatambadveli: ok good19:04
SumitNaiksatambadveli: thanks for the update19:04
badvelithanks all19:04
SumitNaiksatam#topic DVR/FWaaS update19:05
SumitNaiksatami was hoping to get an update from Yi on this19:05
SumitNaiksatambadveli or garyduan: are you guys in sync on this?19:05
SridarKSumitNaiksatam: i think there was response on the thread - now i am not able to find it19:06
*** kenhui has quit IRC19:06
badveliyi is joining19:06
SumitNaiksatamSridarK: yeah, but i think Yi has also been participating in the L3 IRC meetings, so i was hoping to get an update19:06
SumitNaiksatambadveli: great19:06
garyduanHi,19:07
SumitNaiksatamgaryduan: hi19:07
garyduansorry, I was in a meeting19:07
SumitNaiksatamgaryduan: np19:07
garyduanYi talked to DVR team today19:08
*** beyounn has joined #openstack-meeting-319:08
SumitNaiksatamgaryduan: yes19:08
beyounnHi, sorry, I was in a meeting19:08
SumitNaiksatambeyounn: np19:08
SumitNaiksatambeyounn: just wanted to understand where we stand with regards to DVR/FWaaS19:08
SumitNaiksatambeyounn: i know you participated in the L3/DVR meeting19:09
beyounnSumit: I had chat with Carl and Vivek in a really short time19:09
SumitNaiksatambeyounn: ok19:09
SumitNaiksatambeyounn: any conclusion?19:09
beyounnSumit: the conclusion is that I will call a meeting with DVR guys and FWaaS guys after Swami back from PTO19:09
SumitNaiksatambeyounn: ok, and whats the approximate time frame?19:10
beyounnSumit: I will send email next week on ML next week after Swami back19:10
beyounnSo that people can propose time19:10
SumitNaiksatambeyounn: ok, i am hoping that will not be too late to get a solution in, right?19:11
SumitNaiksatambeyounn: it should not happen that DVR implementaiton in Juno cannot support FWaaS19:11
beyounnSumit: that is mostly like what to happen19:11
SumitNaiksatambeyounn: oh19:11
beyounnBut FWaaS will be there anyway19:11
beyounnJust that FWaaS can not work with DVR19:12
SumitNaiksatambeyounn: hmmm…i was thinking that was not going to be the case19:12
SumitNaiksatami would imagine that going forward all deployments will mostly use DVR19:12
beyounnSumit: Well, no one really have any ideas on how it works. There was some thoughts, but it does not seem to work19:13
SumitNaiksatamand if FWaaS cannot be used with that, it undermines the acceptability of FWaaS19:13
SumitNaiksatambeyounn: ok19:13
SumitNaiksatambeyounn: you mean on how to get FWaaS to work with DVR?19:13
beyounnSumit: Yes, Vivek's idea does not seem to work with stateful FW at all19:14
beyounnSumit: so we get back to the starting point now19:14
SumitNaiksatambeyounn: thats a bummer19:14
beyounnSumit: Do you think that we can call it a show stopper for DVR?19:15
SumitNaiksatambeyounn: i was thinking all along that we had more than one option on how to deal with this, and we were trying to figure out which is the better option19:15
SumitNaiksatambeyounn: i dont think we can stop DVR because it does not support FWaaS19:15
SumitNaiksatambeyounn: DVR is required for nova-parity i believ19:15
SumitNaiksatam*believe19:15
SumitNaiksatamthis is defintiely a show stopper for us though19:16
beyounnSumit: no, we don't. as I said to you earlier that I don't really have solutions.19:16
SumitNaiksatami think its okay if we cannot support FWaaS on DVR in one release19:16
SumitNaiksatambut there needs to be a concrete path forward to do it19:17
SumitNaiksatambeyounn: do you know if vpnaas is supported on DVR?19:17
beyounnLet me start on the meetings and how we can sort out something19:17
SumitNaiksatamnati_uen_: there?19:17
beyounnSumit: I think it should work19:17
nati_uen_SumitNaiksatam: back19:17
SumitNaiksatamnati_uen_: hi19:17
nati_uen_SumitNaiksatam: What's up?19:17
SumitNaiksatamnati_uen_: quick question, will VPNaaS be supported on DVR?19:18
nati_uen_SumitNaiksatam: IMO, Swami is working on this19:18
SumitNaiksatamnati_uen_: ok19:18
nati_uen_SumitNaiksatam: DVR has some service node (sorry I'm not sure exact name), and he is going to run it in service node19:18
SumitNaiksatamnati_uen_: we have realized that as per the current implementation of DVR, it does not support FWaaS19:19
nati_uen_SumitNaiksatam: oh,19:19
nati_uen_SumitNaiksatam: For VPN, we can't have distributed ipsec19:19
SumitNaiksatamnati_uen_: since there is no one node on which the connections can be tracked19:19
beyounnSumit, is running FW on service node is a acceptable solution,19:19
SumitNaiksatamnati_uen_: i meant DVR does not have one node to track connections19:20
SumitNaiksatambeyounn: i think it would be for starters19:20
SumitNaiksatambeyounn:  are you familiar with the service node that nati_uen_ mentions here?19:20
beyounnbut for the IPsec, it will be the same19:20
nati_uen_SumitNaiksatam: ok so we can't do stateful firewall on DVR, right?19:20
SumitNaiksatamnati_uen_: exactly19:20
*** Sukhdev has joined #openstack-meeting-319:21
SumitNaiksatamnati_uen_: and FWaaS reference implementation is only stateful firewall :-)19:21
beyounnSumit, not in detail, but it is a dedicated node for the services like ipsec, NAT19:21
*** jamiehannaford has quit IRC19:21
nati_uen_SumitNaiksatam: iptables, right?19:21
SumitNaiksatamnati_uen_: yeah19:21
nati_uen_SumitNaiksatam: I don't get why we need centralized connection tracker19:21
SumitNaiksatambeyounn: ah, yeah NAT would have the same problem19:21
SumitNaiksatamnati_uen_: how else would we do it?19:21
SumitNaiksatambeyounn: nati_uen_’s question ^^^19:22
nati_uen_beyounn: ya. so FWaaS can run in service node19:22
nati_uen_SumitNaiksatam: so we can simply write iptables rule in each node19:22
beyounnNati_uen_: yes, it is for NS traffic19:22
nati_uen_beyounn: NS?19:22
SumitNaiksatamNS - norht-south19:22
nati_uen_kk19:22
SumitNaiksatam*north19:22
*** jackib has joined #openstack-meeting-319:22
beyounnnati_uen_: so we can go NSX model, the NS FW is on the service node and the EW are security-group19:23
SridarKbeyounn: but we could have East - West traffic (subnet to subnet) needing FW19:23
nati_uen_beyounn: ya. That's one option19:23
SumitNaiksatamSridarK: yes, but i guess if you choose to use DVR, you cannot deploy it for EW traffic then19:24
SumitNaiksatamit -> FWaaS19:24
SridarKSumitNaiksatam: yes seems like19:24
SumitNaiksatamand that would be a limitation of DVR, not FWaaS?!?19:24
nati_uen_I'm not sure why FWaaS can't do something sec group is doing yet..19:24
beyounnSridarK: you are correct, for the EW, you can still force the traffic to Service node, but just with the bad performance19:24
SridarKbeyounn: aah ok19:24
SridarKthat would be acceptable19:25
*** otherwiseguy has joined #openstack-meeting-319:25
beyounnnati_uen_: the sec group is on the NIC where you are seeing the traffic from both side19:25
beyounnnati_uen_: FWaaS is on router, but DVR sees only one leg of the traffic19:25
beyounnnati_uen_: That is why FWaaS on DVR will not work19:26
nati_uen_beyounn: oh, so how about one more leg?19:26
nati_uen_beyounn: it will be magically trasfered by openflow?19:26
SumitNaiksatamnati_uen_: i think the point is that the same node does not see both legs19:27
*** mfer has joined #openstack-meeting-319:27
SumitNaiksatambeyounn: correct me if i am wrong19:27
SumitNaiksatamnati_uen_: both legs do get processed, but not on the same node19:27
beyounnnati_uen_: each DVR node only sees outgoing traffic19:27
nati_uen_beyounn: how about incomming traffic?19:28
beyounnnat_uen_: nop19:28
SumitNaiksatambeyounn: you mean no-op?19:28
beyounnlet me explain, I just type slow :-(19:29
SumitNaiksatambeyounn: np  :-)19:29
beyounnyou have two VM on two hypervisors and each VM is in a different network (subnet)19:29
*** pballand has joined #openstack-meeting-319:29
beyounnLet's call VMs as A and B19:29
beyounnwhen A sends icmp request, the packet hits on local DVR node and get route to B's network from there19:30
beyounnSo when the traffic comes to B's hypervisor, the DVR on B's hypervisor does not see the traffic, since it has always be routed by A's DVR node19:30
*** yamamoto has joined #openstack-meeting-319:31
beyounnWhen B sends icmp reply, the B's DVR node sees the traffic and put it on to the A's network directly and then forward it out19:31
beyounnThe A's DVR will not see icmp reply at all, since it is already on the A's network19:31
beyounnSo, on each DVR nodes, you only see either icmp request or reply but not both19:32
beyounnOk, hope this is clear19:32
*** lblanchard has quit IRC19:32
*** MarkAtwood has quit IRC19:33
SridarKbeyounn: nice recap19:33
beyounn:-)19:33
nati_uen_beyounn: Thanks19:33
SumitNaiksatambeyounn: yes, thanks19:33
beyounnSo, the worse case solution is to somehow work out a forwarding rule on the DVR nodes and forward the traffic that needs to be fire walled to the service node and have service node to run FWaaS19:34
SumitNaiksatambeyounn: so different DVR nodes process the forward and return flows19:34
beyounnBut, even this, there are a lot of detail to source out19:34
beyounnSumit: Yes19:34
SumitNaiksatambeyounn: yeah that is tricky19:34
SumitNaiksatambeyounn: and perhaps results in the same performance bottleneck that DVR tries to get away from19:35
beyounnSumit: Yes19:35
beyounnSumit: right19:35
SumitNaiksatamnati_uen_: so this is not an issue with VPNaaS?19:35
beyounnSumit: One thing need to consider-- the L7 services19:35
*** yamamoto has quit IRC19:35
SumitNaiksatambeyounn: ok19:35
pcm_SumitNaiksatam: wouldn't VPNaaS be N-S?19:36
nati_uen_SumitNaiksatam: we can't support distributed ipsec19:36
SumitNaiksatampcm_: yeah, but for that it will have to go through this one node, right?19:36
beyounnSumit: All L7 services are CPU eaters, running L7 services on each hypervisor where all other VMs are running, may cause local CPU shortage19:36
SumitNaiksatambeyounn: good point19:36
beyounnSumit: It may be a good choice to run L7 service on a service node19:37
SumitNaiksatampcm_: you are saying current DVR targets E-W traffic19:37
beyounnSumit: and FWaaS is mainly targeted on the L4 and above19:37
pcm_SumitNaiksatam: the above was talking E-W.19:37
SumitNaiksatampcm_: yeah19:37
pcm_SumitNaiksatam: so if VPN used in N-S, it would use service node, right?19:38
SumitNaiksatamok so the conclusion we are drawing here is that when running DVR, and wanting to use FWaaS, we can propose deploying FWaaS on the service node19:38
*** mestery_ is now known as mestery19:38
SumitNaiksatamin that case however, FWaaS is only for N-S traffic19:38
SridarKSumitNaiksatam: yes that will be the problem19:38
SumitNaiksatamactually let me rephrase19:39
SumitNaiksatamin that case the refernece implementation of FWaaS can only be used for N-S traffic19:39
beyounnSumit: realistically, I don't think FWaaS on DVR will be able to be in Juno, let me kick off the meeting with DVR guys first and see how it goes. We may be able to create more than one service node19:39
SumitNaiksatambeyounn: as long as we have a path forward its pefectly fine if its addresed in the following release19:40
beyounnAnd have DVR to forward the traffic to localized service node, this is half baked idea,so take it as .....19:40
*** peristeri has quit IRC19:40
SumitNaiksatamhowever my concern is that at this point we dont seem to have a technical solution for E-W traffic19:40
SridarKif we force everything thru the Serv Node19:40
SumitNaiksatambeyounn: ok, hopefully that idea “distribute” service node can help19:40
beyounnSumit: you can still forward the E-W traffic to service node19:40
SridarKif FWaaS is configured19:41
beyounnSumit: My actual concerns are the FWaaS constructs that could be required to support DVR19:41
SridarKwe will degrade performance only with FWaaS but can have something that works19:41
SumitNaiksatamSridarK: ok19:41
SumitNaiksatambeyounn: yes that was my next question19:41
SumitNaiksatambtw, we are 12 minutes over already19:41
beyounnSumit: that is why I was really hesitate to send original email19:41
beyounnSumit: Let me pop some eamils internally first19:42
*** overlayer has quit IRC19:42
SumitNaiksatambeyounn: so to support deploying FWaaS on service node, we would need additional DVR configuration or is it on the FWaaS side?19:42
beyounnSumit; both19:42
*** overlayer has joined #openstack-meeting-319:43
SumitNaiksatambeyounn: ok19:43
SumitNaiksatambeyounn: also if we do end up supporting on N-S traffic (again, for the reference implementation), how do we not allow firewall policy configuration for E-W trafffic?19:43
beyounnSumit: on the DVR side we need a way to filter and forward traffic to service node, on the FWaaS side, we need construct like zone or address group to be the context of policy19:43
*** peristeri has joined #openstack-meeting-319:43
beyounnSumit: for NS it is easy, just put FWaaS with the NS router19:43
beyounnSumit: all the traffic needs to go to ext-br, so the FWaaS should be there19:44
*** lblanchard has joined #openstack-meeting-319:44
SumitNaiksatambeyounn: but we dont have service insertion yet to put it on a specific router :-)19:44
SumitNaiksatamthis is royal jam!19:45
beyounnSumit: and I'm swimming in the jam19:45
SridarKbeyounn: is Swami back next week ?19:45
SumitNaiksatami think we need to bring this up with the PTL at the earliest19:45
beyounnSridark: that is what Carl told me19:45
beyounnI saw Kely was around19:46
SumitNaiksatamnati_uen_ pcm_: so to check with you again, you guys are all set as far as VPNaaS is concerned, or will you like to participate in the FWaaS-related discussion as well if it applies to you?19:46
SumitNaiksatammestery: there?19:46
*** mrunge has quit IRC19:47
mesterySumitNaiksatam: o/19:47
SumitNaiksatammestery: hi :-)19:47
pcm_SumitNaiksatam: I'll certainly want to keep an ear in on the discussions so I can better understand all this.19:47
SumitNaiksatampcm_: ok19:47
SumitNaiksatammestery: so we seem to be running into bigger issues than imagined as far as DVR and FWaaS is concerned19:48
mesterySumitNaiksatam: #sadpanda :(19:48
* mestery looks at the backscroll.19:48
SumitNaiksatambeyounn (Yi Sun): here has been leading the discussions on that19:48
SumitNaiksatammestery: :-)19:48
*** safchain has quit IRC19:48
SumitNaiksatammestery: as a team we have had several discussions with Swami before19:48
SumitNaiksatammestery: but none of the solutions seem promising19:49
nati_uen_SumitNaiksatam: Sorry I'm in another meeting now. let's talk later19:49
mesterybeyounn SumitNaiksatam: So do we need to indicate FWaaS and DVR won't work together in Juno? Is that the only option?19:49
SumitNaiksatamnati_uen_: sure, thanks for the discussion earlier19:49
beyounnnati_uen_: could  you help to review my service object/group spec? Thanks19:49
SumitNaiksatammestery: the best that we can do is that FWaaS runs on the service node, and can only firewall N-S traffic19:49
*** thomasem has quit IRC19:50
beyounnnat_uen_: link:https://review.openstack.org/#/c/94133/19:50
beyounnnati_uen_:https://review.openstack.org/#/c/94133/19:50
SumitNaiksatammestery: however, even for that we would need the service insertion spec to be approved and implemented so that we can get FWaaS to insert on a specific router (which is the service router)19:50
nati_uen_beyounn: sure!19:50
SumitNaiksatambeyounn: we already talked with nati_uen_ regarding the service objects spec, he said he will review19:50
mesterySumitNaiksatam: Yikes, this isn't sounding good, as that has limitations of it's own.19:51
beyounnnati_uen_: Sumit: big thanks19:51
SumitNaiksatammestery: this still does not solve the problem for E-W traffic19:51
*** shakamunyi has quit IRC19:52
SumitNaiksatammestery: this of course, is all in the context of the iptables-based reference implementation for FWaaS19:52
SumitNaiksatammestery: we dont need to decide right away19:53
SumitNaiksatammestery: but we would need to soon19:53
mesterySumitNaiksatam: I'm thinking the best option may be to say the two don't work, given the timelines in Juno, but I realize that decision may not be popular.19:53
SumitNaiksatammestery: beyounn has already started a thread on the -dev mailer for this19:53
mesterySumitNaiksatam: Lets track this and clsoe soon though.19:53
*** thomasem has joined #openstack-meeting-319:53
mesterybeyounn SumitNaiksatam: Thanks, I will reply there.19:53
SridarKSumitNaiksatam: perhaps if we force all traffic thru a service router19:53
SridarKSumitNaiksatam: we will get degraded perf19:53
SridarKwe should explore that19:54
SumitNaiksatammestery: perhaps should we also have a more focussed discussion with a smaller set of people?19:54
SridarKso we are not completely shot19:54
beyounnI will send out an other email to arrange another meeting19:54
SumitNaiksatammestery: does that sound okay? a dedicated meeting between FWaaS and DVR team to discuss this?19:54
beyounns/will/can/19:54
SumitNaiksatammestery: only problem is that Swami is away until next week19:55
mesterySumitNaiksatam beyounn: +119:55
mesteryWe need Swami there though19:55
SumitNaiksatammestery: and well we are fast approaching the long weekend too19:55
SumitNaiksatammestery: so perhaps next week is indeed our best option19:55
mesteryI think next week is it.19:55
SumitNaiksatambeyounn: my suggestion is that you send a focused email to mestery and other relevant folks suggesting the meeting, and also poiting out the issues and options we discussed today19:56
*** peristeri has quit IRC19:56
beyounnSumit: OK19:56
SumitNaiksatambeyounn: that way everyone will have enough context before the meeting and we can respond to the thread even before taht19:57
SumitNaiksatambeyounn: please cc nati_uen_ as well since they have issues with support ipsec VPN19:57
SumitNaiksatammestery: thanks for stopping by19:57
beyounnSumit: How about I just continue with the old email I sent out since it has older context and then add something new on it19:57
SumitNaiksatambeyounn:  ok sure19:57
beyounnSumit: Sure19:57
SumitNaiksatambeyounn: that work19:57
SumitNaiksatamworks19:57
SumitNaiksatambeyounn: we need to keep the discussion focussed19:58
beyounnOK19:58
SumitNaiksatambeyounn: i noticed there were some responsed on that thread, which to me did not seem to be in sync19:58
SumitNaiksatam*responses19:58
SumitNaiksatambeyounn: thanks a ton for shepherding this19:59
SumitNaiksatamlets all support beyounn on this!19:59
beyounnSumit: the email I will follow is the one I sent to the smaller group19:59
SumitNaiksatambeyounn: ah ok19:59
*** yamamoto has joined #openstack-meeting-319:59
SumitNaiksatambeyounn: perhaps -dev is just as fine19:59
SumitNaiksatambeyounn: and you can cc specific people19:59
beyounnSure19:59
SumitNaiksatam#topic open discussion20:00
beyounnAll: my issue is that I have limit bandwidth, so please also help to follow up if possible20:00
SumitNaiksatamfor once the FWaaS meeting is longer than the adv services meeting20:00
SumitNaiksatambeyounn: yes fully understand20:00
SridarKSumitNaiksatam: on the service insertion i hope we don't need another BP to address FWaaS changes ?20:00
beyounnAll: I have moved all my service object works to Vishnu20:00
SumitNaiksatambeyounn: sure20:01
SumitNaiksatamSridarK: yeah, i thought the spec already captures that20:01
SridarKSumitNaiksatam:  just to be sure thanks20:01
SumitNaiksatamSridarK: yeah20:01
beyounnAll: I need to go, I will send email today. TTYL20:02
SumitNaiksatambeyounn: thanks20:02
SridarKbeyounn: thanks20:02
SumitNaiksatamSridarK: any chance that we can borrow some of Rajesh’s cycles for the DVR discussion?20:02
beyounn:-)20:02
SridarKSumitNaiksatam: not sure i will check20:02
SumitNaiksatamSridarK: not implemenation, but just to participate in the discussion20:02
SridarKSumitNaiksatam: also if needed we can do an internal discussion also b4 talking to DVR folks20:02
SumitNaiksatamSridarK: we need more people who are involved on the iptables side to help beyounn20:03
SridarKso we can propose some alternatives20:03
SumitNaiksatamSridarK: sure, that sounds like a good plan20:03
SridarKSumitNaiksatam: yes got it will check with Rajesh as well20:03
SumitNaiksatamSridarK: please feel free to suggest f2f meeting if required20:03
SridarKSumitNaiksatam: i think that will be good20:03
SumitNaiksatami can do it on july 4th as well :-)20:03
*** yamamoto has quit IRC20:04
SumitNaiksatamjust kidding20:04
SridarKSumitNaiksatam: i am out of town :-(20:04
SumitNaiksatamSridarK: no worries20:04
beyounnany one know pcm_'s email?20:04
SridarKu think tomorrow is too short notice20:04
SridarKbeyounn: i can send u an email20:04
SumitNaiksatambeyounn: pcm@cisco.com20:04
beyounnsure, thanks20:04
pcm_pcm@cisco.com20:04
beyounn:-)20:04
SridarKash there now pcm is going to get spammed20:05
SridarK:-)20:05
pcm_:)20:05
SumitNaiksatamSridarK: i can do tomorrow, if thats what everyone feels comfortable with20:05
SridarKSumitNaiksatam:ok will send an email to sort logistics20:05
SumitNaiksatamall right, thanks everyone for your time!20:06
SridarKif not tomorrow we should target Mon20:06
SumitNaiksatamSridarK: sure20:06
SumitNaiksatamhappy 4th of July if we dont meet this week20:06
SumitNaiksatambye20:06
SridarKok thanks bye all20:06
badvelibye20:06
pcm_FYI: I'll be at mid-cycle sprint next week - Tue to Fri20:06
SumitNaiksatam#endmeeting20:06
*** pballand has quit IRC20:06
*** pcm_ has left #openstack-meeting-320:07
*** shakamunyi has joined #openstack-meeting-320:07
*** thangp has quit IRC20:12
*** pballand has joined #openstack-meeting-320:13
*** Sukhdev has quit IRC20:13
*** cjellick has quit IRC20:23
*** cjellick has joined #openstack-meeting-320:23
*** cjellick has quit IRC20:28
*** cjellick has joined #openstack-meeting-320:29
*** cjellick has quit IRC20:30
*** mestery_ has joined #openstack-meeting-320:30
*** cjellick has joined #openstack-meeting-320:30
*** alexpilotti has quit IRC20:31
*** pgpus has quit IRC20:43
*** marun is now known as marun_afk20:43
*** Kanzhe has quit IRC20:45
*** Sukhdev has joined #openstack-meeting-320:50
*** marun_afk is now known as marun20:52
*** jackib1 has joined #openstack-meeting-320:57
*** Sukhdev_ has joined #openstack-meeting-320:57
*** jackib has quit IRC20:58
*** yamamoto has joined #openstack-meeting-320:59
*** Sukhdev has quit IRC21:00
*** Sukhdev_ has quit IRC21:02
*** yamamoto has quit IRC21:03
*** mestery_ has quit IRC21:04
*** mfer has quit IRC21:07
*** julim has quit IRC21:15
*** lblanchard has quit IRC21:18
*** markmcclain has quit IRC21:25
*** overlayer has quit IRC21:30
*** SumitNaiksatam has quit IRC21:32
*** ttrifonov is now known as ttrifonov_zZzz21:32
*** overlayer has joined #openstack-meeting-321:40
*** pgpus has joined #openstack-meeting-321:56
*** SridarK has quit IRC21:56
*** thomasem has quit IRC21:58
*** yamamoto has joined #openstack-meeting-321:59
*** MarkAtwood has joined #openstack-meeting-321:59
*** yamamoto has quit IRC22:04
*** MaxV has joined #openstack-meeting-322:07
*** nelsnelson has quit IRC22:15
*** shakamunyi has quit IRC22:17
*** jackib1 has quit IRC22:19
*** shakamunyi has joined #openstack-meeting-322:20
*** otherwiseguy has quit IRC22:21
*** banix has quit IRC22:26
*** briancurtin is now known as briancurtin_away22:31
*** otherwiseguy has joined #openstack-meeting-322:36
*** armax has joined #openstack-meeting-322:42
*** pballand has quit IRC22:44
*** briancurtin_away is now known as briancurtin22:49
*** david-lyle has quit IRC22:53
*** david-lyle has joined #openstack-meeting-322:54
*** david-lyle has quit IRC22:59
*** yamamoto has joined #openstack-meeting-322:59
*** yamamoto has quit IRC23:04
*** otherwiseguy has quit IRC23:05
*** lblanchard has joined #openstack-meeting-323:11
*** shakamunyi has quit IRC23:11
*** jackib has joined #openstack-meeting-323:12
*** Sukhdev has joined #openstack-meeting-323:22
*** carl_baldwin has quit IRC23:26
*** MaxV has quit IRC23:30
*** lblanchard has quit IRC23:41
*** jcoufal has quit IRC23:48
*** nati_uen_ has quit IRC23:49
*** lblanchard has joined #openstack-meeting-323:50
*** hurgleburgler has quit IRC23:58
*** prad has quit IRC23:59
*** yamamoto has joined #openstack-meeting-323:59

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