Wednesday, 2014-06-25

*** lcheng has joined #openstack-meeting-300:02
*** lcheng has quit IRC00:04
*** shakamunyi has quit IRC00:05
*** prad_ has quit IRC00:09
*** xuhanp has joined #openstack-meeting-300:09
*** xuhanp has quit IRC00:28
*** Sukhdev has joined #openstack-meeting-300:31
*** jaypipes has quit IRC00:35
*** Sukhdev has quit IRC00:38
*** coolsvap is now known as coolsvap|afk00:44
*** carl_baldwin has quit IRC00:54
*** sarob has quit IRC00:58
*** sarob has joined #openstack-meeting-300:59
*** sarob has quit IRC01:03
*** jackib has quit IRC01:20
*** jackib has joined #openstack-meeting-301:23
*** seizadi has joined #openstack-meeting-301:26
*** gduan has quit IRC01:27
*** jackib has quit IRC01:30
*** garyduan has joined #openstack-meeting-301:31
*** yamamoto_ has joined #openstack-meeting-301:32
*** nati_ueno has quit IRC01:40
*** asahlin has joined #openstack-meeting-301:41
*** asahlin has quit IRC01:47
*** shakamunyi has joined #openstack-meeting-301:47
*** alexpilotti has quit IRC01:55
*** banix has joined #openstack-meeting-301:59
*** eghobo has quit IRC02:05
*** seizadi has quit IRC02:10
*** seizadi has joined #openstack-meeting-302:24
*** baojg has joined #openstack-meeting-302:33
*** jackib has joined #openstack-meeting-302:33
*** otherwiseguy has joined #openstack-meeting-302:33
*** carl_baldwin has joined #openstack-meeting-302:35
*** otherwiseguy has quit IRC02:40
*** otherwiseguy has joined #openstack-meeting-302:41
*** jackib has quit IRC02:53
*** otherwiseguy has quit IRC02:55
*** baojg has quit IRC02:56
*** otherwiseguy has joined #openstack-meeting-302:56
*** baojg has joined #openstack-meeting-302:56
*** pballand has joined #openstack-meeting-302:57
*** jackib has joined #openstack-meeting-303:05
*** sankarshan_away is now known as sankarshan03:07
*** armax has left #openstack-meeting-303:07
*** hurgleburgler has quit IRC03:16
*** jackib has quit IRC03:17
*** pballand has quit IRC03:22
*** seizadi has quit IRC03:22
*** nati_ueno has joined #openstack-meeting-303:25
*** eghobo has joined #openstack-meeting-303:36
*** beyounn has quit IRC03:55
*** baojg has quit IRC04:04
*** carl_baldwin has quit IRC04:06
*** carl_baldwin has joined #openstack-meeting-304:07
*** nati_ueno has quit IRC04:08
*** nati_ueno has joined #openstack-meeting-304:09
*** otherwiseguy has quit IRC04:13
*** otherwiseguy has joined #openstack-meeting-304:14
*** eghobo has quit IRC04:14
*** eghobo has joined #openstack-meeting-304:15
*** shakamunyi has quit IRC04:16
*** shakamunyi has joined #openstack-meeting-304:17
*** shakamunyi has quit IRC04:17
*** shakamunyi has joined #openstack-meeting-304:20
*** baojg has joined #openstack-meeting-304:22
*** banix has quit IRC04:25
*** carl_baldwin has quit IRC04:26
*** nati_ueno has quit IRC04:29
*** zehicle_at_dell has joined #openstack-meeting-304:31
*** otherwiseguy has quit IRC04:39
*** zehicle_at_dell has quit IRC04:42
*** zehicle_at_dell has joined #openstack-meeting-304:42
*** Sukhdev has joined #openstack-meeting-304:44
*** cjellick has quit IRC04:53
*** cjellick has joined #openstack-meeting-304:53
*** seizadi has joined #openstack-meeting-304:55
*** cjellick has quit IRC04:57
*** shakamunyi has quit IRC05:00
*** baojg has quit IRC05:02
*** baojg has joined #openstack-meeting-305:02
*** baojg has quit IRC05:04
*** baojg has joined #openstack-meeting-305:04
*** markmcclain has joined #openstack-meeting-305:17
*** nati_ueno has joined #openstack-meeting-305:17
*** markmcclain1 has joined #openstack-meeting-305:18
*** coolsvap|afk is now known as coolsvap05:19
*** markmcclain has quit IRC05:22
*** cjellick has joined #openstack-meeting-305:24
*** nati_ueno has quit IRC05:26
*** amitpp has joined #openstack-meeting-305:31
*** cjellick has quit IRC05:32
*** markmcclain1 has quit IRC05:39
*** amitpp has quit IRC05:42
*** jtomasek has joined #openstack-meeting-305:48
*** Sukhdev has quit IRC05:56
*** jtomasek has quit IRC06:07
*** seizadi has quit IRC06:09
*** MaxV has joined #openstack-meeting-306:23
*** seizadi has joined #openstack-meeting-306:28
*** seizadi has quit IRC06:39
*** nati_ueno has joined #openstack-meeting-306:42
*** kashyap has quit IRC06:45
*** kashyap has joined #openstack-meeting-306:48
*** MaxV has quit IRC06:50
*** kashyap` has joined #openstack-meeting-306:52
*** lsmola has joined #openstack-meeting-306:56
*** kashyap has quit IRC06:56
*** zehicle_at_dell has quit IRC07:00
*** mrunge has joined #openstack-meeting-307:00
*** kashyap` is now known as kashyap07:05
*** sankarshan is now known as sankarshan_away07:15
*** sankarshan_away is now known as sankarshan07:16
*** lsmola has quit IRC07:25
*** jcoufal has joined #openstack-meeting-307:30
*** ttrifonov is now known as ttrifonov_zZzz07:41
*** baojg has quit IRC07:48
*** baojg has joined #openstack-meeting-307:49
*** baojg has joined #openstack-meeting-307:49
*** enykeev has joined #openstack-meeting-307:50
*** baojg has quit IRC08:04
*** ttrifonov_zZzz is now known as ttrifonov08:07
*** kashyap is now known as kashyap_lunch08:07
*** zehicle_at_dell has joined #openstack-meeting-308:09
*** MaxV has joined #openstack-meeting-308:12
*** baojg has joined #openstack-meeting-308:14
*** cjellick has joined #openstack-meeting-308:29
*** MaxV has quit IRC08:32
*** MaxV has joined #openstack-meeting-308:33
*** cjellick has quit IRC08:33
*** yamamoto_ has quit IRC08:39
*** igordcard has joined #openstack-meeting-308:45
*** kashyap_lunch is now known as kashyap09:10
*** amotoki has quit IRC09:24
*** gcb_ has joined #openstack-meeting-309:27
*** MaxV has quit IRC09:28
*** nati_ueno has quit IRC09:31
*** safchain has joined #openstack-meeting-309:32
*** lcheng has joined #openstack-meeting-309:33
*** MaxV has joined #openstack-meeting-309:34
*** sankarshan is now known as sankarshan_away09:36
*** MaxV has quit IRC09:42
*** MaxV has joined #openstack-meeting-309:47
*** jtomasek has joined #openstack-meeting-310:00
*** MaxV has quit IRC10:00
*** MaxV has joined #openstack-meeting-310:01
*** yamahata has quit IRC10:08
*** MaxV has quit IRC10:11
*** gcb_ has quit IRC10:11
*** igordcard has quit IRC10:18
*** rm_work is now known as rm_work|away10:23
*** gcb_ has joined #openstack-meeting-310:28
*** amitpp has joined #openstack-meeting-310:28
*** lcheng has quit IRC10:31
*** jtomasek has quit IRC10:41
*** jtomasek has joined #openstack-meeting-310:55
*** sankarshan_away is now known as sankarshan10:59
*** baojg has quit IRC11:10
*** baojg has joined #openstack-meeting-311:11
*** coolsvap is now known as coolsvap|afk11:11
*** baojg has joined #openstack-meeting-311:12
*** yamahata has joined #openstack-meeting-311:15
*** baojg has quit IRC11:16
*** gcb_ has quit IRC11:16
*** MaxV has joined #openstack-meeting-311:20
*** thinrichs has quit IRC11:22
*** banix has joined #openstack-meeting-311:29
*** banix has quit IRC11:33
*** jackib has joined #openstack-meeting-311:37
*** jackib has quit IRC11:38
*** jackib has joined #openstack-meeting-311:38
*** erecio has joined #openstack-meeting-311:44
*** jtomasek has quit IRC11:46
*** jtomasek has joined #openstack-meeting-311:47
*** mwagner_lap has quit IRC11:53
*** jackib has quit IRC12:03
*** erecio has quit IRC12:11
*** erecio has joined #openstack-meeting-312:12
*** erecio has quit IRC12:13
*** erecio has joined #openstack-meeting-312:14
*** alexpilotti has joined #openstack-meeting-312:15
*** amitpp has quit IRC12:19
*** amitpp has joined #openstack-meeting-312:19
*** erecio has quit IRC12:20
*** erecio has joined #openstack-meeting-312:21
*** amitpp has quit IRC12:22
*** iovadia has joined #openstack-meeting-312:45
*** iovadia has left #openstack-meeting-312:47
*** prad_ has joined #openstack-meeting-312:56
*** amitpp has joined #openstack-meeting-312:58
*** julim has joined #openstack-meeting-313:03
*** safchain has quit IRC13:06
*** igordcard has joined #openstack-meeting-313:06
*** safchain has joined #openstack-meeting-313:06
*** shakamunyi has joined #openstack-meeting-313:08
*** thomasem has joined #openstack-meeting-313:10
*** yamamoto has joined #openstack-meeting-313:16
*** mwagner_lap has joined #openstack-meeting-313:16
*** amitpp has quit IRC13:30
*** akrivoka has joined #openstack-meeting-313:31
*** baojg has joined #openstack-meeting-313:31
*** peristeri has joined #openstack-meeting-313:35
*** markmcclain has joined #openstack-meeting-313:36
*** markmcclain1 has joined #openstack-meeting-313:37
*** markmcclain1 has quit IRC13:38
*** markmcclain has quit IRC13:40
*** coolsvap|afk is now known as coolsvap13:43
*** jmsoares has joined #openstack-meeting-313:53
*** nati_ueno has joined #openstack-meeting-313:55
*** akrivoka has left #openstack-meeting-314:00
*** armax has joined #openstack-meeting-314:00
*** lblanchard has joined #openstack-meeting-314:02
*** otherwiseguy has joined #openstack-meeting-314:12
*** nati_ueno has quit IRC14:16
*** enykeev has quit IRC14:19
*** xuhanp has joined #openstack-meeting-314:21
*** enykeev has joined #openstack-meeting-314:21
*** carl_baldwin has joined #openstack-meeting-314:22
*** nelsnelson has joined #openstack-meeting-314:29
*** MaxV_ has joined #openstack-meeting-314:33
*** MaxV has quit IRC14:34
*** eguz has joined #openstack-meeting-314:36
*** eguz has quit IRC14:36
*** eghobo has quit IRC14:41
*** scott-millward has joined #openstack-meeting-314:47
*** markmcclain has joined #openstack-meeting-314:48
*** shakamunyi has quit IRC14:54
*** shakamunyi has joined #openstack-meeting-314:56
*** shakamunyi is now known as shakamunyi_otp14:57
*** shakamunyi_otp is now known as shakamunyi14:57
*** david-lyle has joined #openstack-meeting-314:57
*** shakamunyi is now known as shakamunyi_otp14:57
*** mwagner_lap has quit IRC15:00
*** nelsnelson has quit IRC15:00
*** banix has joined #openstack-meeting-315:01
*** nelsnelson has joined #openstack-meeting-315:01
*** jackib has joined #openstack-meeting-315:06
*** jackib has quit IRC15:06
*** jackib has joined #openstack-meeting-315:07
*** samchoi has joined #openstack-meeting-315:16
*** mwagner_lap has joined #openstack-meeting-315:16
*** cjellick has joined #openstack-meeting-315:17
*** shakamunyi_otp has quit IRC15:20
*** shakamunyi has joined #openstack-meeting-315:20
*** shakamunyi has quit IRC15:20
*** mfer has joined #openstack-meeting-315:27
*** hurgleburgler has joined #openstack-meeting-315:27
mfer#startmeeting openstack-sdk-php15:30
openstackMeeting started Wed Jun 25 15:30:31 2014 UTC and is due to finish in 60 minutes.  The chair is mfer. Information about MeetBot at http://wiki.debian.org/MeetBot.15:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:30
*** openstack changes topic to " (Meeting topic: openstack-sdk-php)"15:30
openstackThe meeting name has been set to 'openstack_sdk_php'15:30
mferHello folks. Can you list your name along with any applicable associations.15:30
mferMatt Farina, HP15:31
samchoiSam Choi, HP15:31
*** jtomasek has quit IRC15:32
mferglenc is anyone from your org coming today?15:33
mfersamchoi if no one else is coming should we call it a day?15:34
samchoisamchoi: sure, that sounds fine to me15:34
samchoimfer:15:34
samchoiinteresting...irc wanted to auto complete my own username :)15:35
mferit's your client :)15:35
mfersamchoi then i'll call the meeting and we can pick up again next week.15:37
mfer#endmeeting15:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:37
openstackMeeting ended Wed Jun 25 15:37:14 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-06-25-15.30.html15:37
*** thinrichs has joined #openstack-meeting-315:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-06-25-15.30.txt15:37
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_sdk_php/2014/openstack_sdk_php.2014-06-25-15.30.log.html15:37
*** MaxV has joined #openstack-meeting-315:39
*** MaxV_ has quit IRC15:40
*** Sukhdev has joined #openstack-meeting-315:42
*** jcoufal is now known as jcoufal_bbl15:48
*** david-lyle has quit IRC15:51
*** jackib has quit IRC15:51
*** david-lyle has joined #openstack-meeting-315:51
*** xuhanp has quit IRC15:54
*** jackib has joined #openstack-meeting-315:56
*** eghobo has joined #openstack-meeting-315:56
*** david-lyle has quit IRC15:56
*** eghobo has quit IRC15:57
*** david-lyle has joined #openstack-meeting-315:57
*** eghobo has joined #openstack-meeting-315:57
*** yamahata has quit IRC15:58
*** david-lyle has quit IRC16:00
*** david-lyle has joined #openstack-meeting-316:00
*** pballand has joined #openstack-meeting-316:02
*** zehicle_at_dell has quit IRC16:12
*** david-lyle has quit IRC16:17
*** david-lyle has joined #openstack-meeting-316:17
*** david-lyle has quit IRC16:19
*** david-ly_ has joined #openstack-meeting-316:19
*** pballand has quit IRC16:20
*** johnthetubaguy has joined #openstack-meeting-316:20
*** david-ly_ has quit IRC16:22
*** david-lyle has joined #openstack-meeting-316:23
*** tjones has joined #openstack-meeting-316:25
*** amotoki has joined #openstack-meeting-316:26
*** david-lyle has quit IRC16:27
tjones#startmeeting NovaBugScrub16:30
openstackMeeting started Wed Jun 25 16:30:08 2014 UTC and is due to finish in 60 minutes.  The chair is tjones. Information about MeetBot at http://wiki.debian.org/MeetBot.16:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:30
*** openstack changes topic to " (Meeting topic: NovaBugScrub)"16:30
openstackThe meeting name has been set to 'novabugscrub'16:30
tjonesHi - anyone here today?16:30
tjoneshellooooooooo16:32
*** briancurtin has left #openstack-meeting-316:32
tjones*listens……*16:32
tjones#link https://etherpad.openstack.org/p/NovaBugTriage16:33
*** mrunge has quit IRC16:34
*** shakamunyi has joined #openstack-meeting-316:37
dansmithtjones: I would if I wasn't in another meeting :(16:39
*** ttrifonov is now known as ttrifonov_zZzz16:40
dansmithtjones: but I *do* feel sorry for you, if that's any consolation :)16:40
tjonesdansmith: i feel sorry for me too - thanks16:40
dansmithheh16:40
tjonesim just using this time to go through bugs16:40
*** ttrifonov_zZzz is now known as ttrifonov16:40
tjonesi have some ideas for making this better - so i am feeling less sorry for me16:41
*** MaxV has quit IRC16:43
*** beyounn has joined #openstack-meeting-316:44
*** pballand has joined #openstack-meeting-316:50
tjones#endmeeting16:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:51
openstackMeeting ended Wed Jun 25 16:51:36 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-06-25-16.30.html16:51
*** tjones has left #openstack-meeting-316:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-06-25-16.30.txt16:51
openstackLog:            http://eavesdrop.openstack.org/meetings/novabugscrub/2014/novabugscrub.2014-06-25-16.30.log.html16:51
*** mwagner_lap has quit IRC16:54
*** safchain has quit IRC16:56
*** jackib has quit IRC16:59
*** thinrichs has quit IRC17:01
*** david-lyle has joined #openstack-meeting-317:01
*** sarob has joined #openstack-meeting-317:04
*** otherwiseguy has quit IRC17:04
*** jackib has joined #openstack-meeting-317:06
*** jackib has quit IRC17:08
*** yamamoto has quit IRC17:08
*** anil_rao has joined #openstack-meeting-317:16
*** Kanzhe has joined #openstack-meeting-317:17
*** jaypipes has joined #openstack-meeting-317:17
*** banix_ has joined #openstack-meeting-317:20
*** jamiehannaford has joined #openstack-meeting-317:20
*** kj has joined #openstack-meeting-317:20
*** kj has quit IRC17:20
*** LouisF has joined #openstack-meeting-317:22
*** marios_ has joined #openstack-meeting-317:23
*** LouisF has quit IRC17:24
*** LouisF has joined #openstack-meeting-317:25
*** banix_ has quit IRC17:26
*** baojg has quit IRC17:26
*** SumitNaiksatam has joined #openstack-meeting-317:27
*** briancurtin has joined #openstack-meeting-317:28
*** yamamoto_ has joined #openstack-meeting-317:29
*** s3wong has joined #openstack-meeting-317:30
SumitNaiksatamenikanorov Kanzhe s3wong cgoncalves mandeep: there?17:30
marios_o/ hi all17:30
enikanorovyes, sir!17:30
KanzheHi17:30
s3wonghello17:30
cgoncalvesSumitNaiksatam: howdy!17:31
*** yamamoto_ is now known as yamamoto17:31
SumitNaiksatamhi all!17:31
*** yamamoto_ has joined #openstack-meeting-317:31
*** otherwiseguy has joined #openstack-meeting-317:31
*** vinay_yadhav has joined #openstack-meeting-317:31
*** SridarK has joined #openstack-meeting-317:31
banixhi17:31
SumitNaiksatamok lets get started17:31
SridarKhi17:31
vinay_yadhavHi17:31
LouisFSumitNaiksatam: hi17:31
*** pcm_ has joined #openstack-meeting-317:31
SumitNaiksatam#startmeeting Networking Advanced Services17:31
openstackMeeting started Wed Jun 25 17:31:58 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.17:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:32
*** openstack changes topic to " (Meeting topic: Networking Advanced Services)"17:32
openstackThe meeting name has been set to 'networking_advanced_services'17:32
SumitNaiksatam#info agenda: https://wiki.openstack.org/wiki/Meetings/AdvancedServices17:32
SumitNaiksatam#topic Action Item followup17:32
*** openstack changes topic to "Action Item followup (Meeting topic: Networking Advanced Services)"17:32
SumitNaiksatamcgoncalves: you had taken an AI to post a new patch, pending response to your email thread17:33
SumitNaiksatamcgoncalves: i guess we can discuss that in your section of the update17:33
cgoncalvesSumitNaiksatam: that's right17:33
cgoncalvesok17:33
*** mandeep has joined #openstack-meeting-317:33
s3wongcgoncalves: don't be too optimistic, flavor discussion will once again take up 70% of meeting time :-)17:34
*** cathy_ has joined #openstack-meeting-317:34
SumitNaiksatamthere was a suggestion last time that we increase the length of this meeting, or figure out how we can give more time to discuss the items which are not able to cover17:34
enikanorovi hope we'll manage to fit in 30 mins17:34
cgoncalvess3wong: neither you as steering will take 30% :)17:34
SumitNaiksatamwe have discussed an option to have a longer meeting before, but that was not favorable to some17:34
SumitNaiksatami dont think its feasible to have to meetings in a week, its just too much overhead17:35
SumitNaiksatamin terms of getting people together17:35
s3wongenikanorov: 50% is certainly an improvement :-)17:35
enikanorovs3wong: it's 1/3 i think :)17:35
SumitNaiksatamanyone have any thoughts on the meeting lenght logistics?17:35
mandeepSumitNaiksatam: It will only get shorter as spend time discussing how much time we have ;-)17:36
SumitNaiksatamor we can postpone this discussion to the end of the meeting (assuming we get time for it :-) )17:36
enikanorovSumitNaiksatam: could it be that once we're done with discussin glavors it would not require that much time?17:36
marios_SumitNaiksatam: i dont attend often as i should but an hour is hard enough to fit in already with everything else... imo17:36
SumitNaiksatammandeep: :-)17:36
SumitNaiksatamenikanorov: that is certainly an possibility :-)17:36
marios_enikanorov: +117:36
SumitNaiksatammarios_: very true17:36
marios_seems we have a specific issue here17:37
*** samchoi has quit IRC17:37
banixenikanorov: we will discuss flavors for eternity17:37
SumitNaiksatamin general we wanted this to be a status meeting, and not a full blown design discussion (which should be had out of band)17:37
enikanorovbanix: i hope not. markmcclain is here17:37
cgoncalvesSumitNaiksatam: chaining and steering (and GBP) are quite related and probably worth arranging an extra meeting with the folks involved17:37
*** natarajk has joined #openstack-meeting-317:37
enikanorovmarkmcclain: hi17:37
*** yamamoto has quit IRC17:37
SumitNaiksatambut we do try to accomodate some of the design discussion so that we can get a quick resolution while everyone is here17:37
cgoncalvesSumitNaiksatam: such meetings should be sporadic until we get to a consensus17:38
SumitNaiksatamokay, lets table the meeting logistics for now17:38
SumitNaiksatamcgoncalves: true17:38
*** yamamoto has joined #openstack-meeting-317:38
SumitNaiksatam#topic Flavors17:38
*** openstack changes topic to "Flavors (Meeting topic: Networking Advanced Services)"17:38
enikanorovok17:38
pcm_Has mark published his proposal for flavors?17:38
SumitNaiksatammestery: there?17:39
enikanorovso let me briefly tell you what concerns some folks had on the review17:39
* markmcclain is currently sitting in another meeting 17:39
marios_enikanorov: did you get any feedback on yr concerns with marks proposal?17:39
SumitNaiksatamenikanorov: sure17:39
mesteryI believe markmcclain is about to publish that now, I've spoken to him recently, hopefully in the next 30 minutes. :)17:39
enikanorovmarkmcclain: i'll try to do a ork for you explaining your proposal :)17:39
mesteryenikanorov: Please go ahead.17:39
s3wongpcm_: I have not seen it, though I was there in person when markmcclain presented his idea in San Antonio last week17:39
enikanorovyep, so Mark's proposal in short:17:39
*** yamamoto has quit IRC17:40
enikanorovwe introduce a notion of 'driver profile' which is a bunch of configuration of one driver for particular use case17:40
enikanorovfor instance, non-HA, HA. or l2 insertion, L3 insertion17:40
enikanorovthen, the flavor is associated with several such profiles17:40
banixenikanorov: one profile for each of those?17:40
enikanorovno tags, no capabilities17:40
enikanorovbanix: possibly multiple profiles for the same driver17:41
*** johnthetubaguy is now known as zz_johnthetubagu17:41
SumitNaiksatamenikanorov: this is kind of vague17:41
enikanorovso from user perspective user only sees flavor and it's description17:41
*** jamiehannaford has quit IRC17:41
marios_enikanorov: so admin creates profile that matches exactly some requirement?17:41
enikanorovon the background it is associated with the type of implementation17:41
banixoperator associates flavors with profiles17:41
banix?17:41
*** jamiehannaford has joined #openstack-meeting-317:41
enikanorovbanix: right17:41
enikanorovmarios_: yes, i guess so17:41
enikanorovso my point is17:41
marios_enikanorov: is there ANY comm9n ground or work towards it or does it come down to choosing an approach17:42
enikanorovthat exactly this usage is supported by the framework I was proposing17:42
*** Sukhdev has quit IRC17:42
SumitNaiksatamenikanorov: so on what basis does the user choose?17:42
marios_enikanorov: if the latter i suggest interested parties do their research and schedule an hour17:42
enikanorovSumitNaiksatam: i guess it is description then17:42
SumitNaiksatamenikanorov: the description seems like a very subjective metric17:42
enikanorovSumitNaiksatam: i agree17:42
SumitNaiksatamenikanorov: this is not how nova flavors are structured17:43
markmcclainenikanorov's description is not accurate17:43
enikanorovit doesn't solve the problem of feature discovery and doesn't give guarantees17:43
SumitNaiksatamenikanorov: just to take an existing example17:43
enikanorovmarkmcclain: ok, sorry17:43
enikanorovthat's how i understood it17:43
enikanorovmarkmcclain: please correct me17:43
*** jaypipes has quit IRC17:44
markmcclainso flavors are curated by operators17:44
*** jaypipes has joined #openstack-meeting-317:44
pcm_why now get the proposal published and we can read and then have a meeting to discuss all the proposals?17:44
markmcclainflavors contain the list of extensions to enable for a service (ie TLS, L7)17:44
enikanorovthat's not very clear17:45
markmcclainpcm_: trying to get it finalized… 10hrs of driving last 48hrs17:45
enikanorovare you talking about API extensions?17:45
pcm_markmcclain: understood. Just thinking of the best use of everyones time.17:46
SumitNaiksatamenikanorov: i agree, thats not very clear to me either17:46
markmcclainso wait for the spec to be published17:46
*** pgpus has joined #openstack-meeting-317:46
SumitNaiksatammarkmcclain: do you have a timeline for this?17:46
markmcclainI'd provide more detail but I'm sitting in another meeting right now17:46
SumitNaiksatammarkmcclain: in the neutron IRC meeting, you mentioned it was going to be last monday17:46
SumitNaiksatammarkmcclain: dont mean to sound pushy, but just trying to get an estimate17:47
enikanorovok, let's then postpone this, i'd really like to have more detailed markmcclain's input17:47
markmcclainI did not have connectivity while traveling the last 2 days (was expecting to have it)17:47
enikanorovcurrently i think that what i have proposed is a superset of Mark's proposal17:47
mandeepWe have had flavors discussion going on for a long time. The plan is to reset that even before we have a proposal to review?17:48
markmcclainenikanorov: I wouldn't classify it as a superset17:48
marios_+1 mandeep this has been under discussion since summit17:48
enikanorovmarkmcclain: sure, i don't know all the details of yours yet17:48
marios_though ftr i havent had chance to check markmcclain proposal17:48
garyduanvendor's implemention really rely on the flavor framework to move forward17:49
SumitNaiksatammestery: from a process perspective, is it advisable to have multiple proposals, or to collaborate on one proposal?17:49
mandeepgaryduan: +1, that is why I am worried about resets based on subjective claims17:50
mesterySumitNaiksatam markmcclain: I want to see collaboration here, so we need to converge as a team on one proposal.17:50
mesteryI was in San Antonio last week with s3wong and others and got to listen to Mark's proposal, which I know others havent' had a chance to digest yet.17:51
mesterySo perhaps once Mark publishes his we can quickly converge. Sound good?17:51
pcm_+117:51
SumitNaiksatammestery: my undestanding was that enikanorov’s proposal started from markmcclain’s input since, markmcclain had objections with the existing service type framework17:51
SumitNaiksatammestery: both fwaas and vpnaas had patches to support STF in havana17:52
SumitNaiksatammestery: and these were put on hold17:52
mandeepmestery: We also need to be careful that the months on discussion/debate that preceded it is not lost17:52
SumitNaiksatammestery: its been a few months since then17:52
mesteryI think there was some disconnect between enikanorov and markmcclain there, I'm hoping we can quickly converge on those for flavors this week.17:52
SumitNaiksatammestery: so what is your directive to this team on this topic going forward?17:53
mesteryI think the two approaches are close enough I'm hopeful this can be resolved ASAP.17:53
mesterymarkmcclain: Once you publish your spec, I'll set something up to close on this.17:53
markmcclainSumitNaiksatam: so problem is that the current direction does not solve the original problem we set out to solve17:53
enikanorovmy opinion is that it solves the original problem17:54
enikanorovand goes beyond that17:54
SumitNaiksatammarkmcclain: okay, but i have trouble understanding that17:54
enikanorovi can show it on different use cases17:54
SumitNaiksatammarkmcclain: the majority of the team here seems to think that the current flavors proposal is shaping up well17:54
mandeepmarkmcclain: enikanorov: I am having problem with subjective claims without details. Please provide content/context17:54
markmcclainSumitNaiksatam: the current prop fails on operator use cases17:54
SumitNaiksatammarkmcclain: perhaps we dont need to implement the proposal in its entirety in the first iteration17:55
enikanorovmarkmcclain: is it possible to list those use cases?17:55
*** yamamoto_ has quit IRC17:55
enikanorovi think some folks from lbaas team just din't read through deep enough to claim that17:55
markmcclainenikanorov: I think most folks have read it several times now17:56
enikanorovif that were so, their comments would be different, i guess...17:57
enikanorovanyway, let's talk when the alternative is published17:57
mandeepmarkmcclain: I just want to understand it with a specific use-case/scenario17:58
SumitNaiksatammarkmcclain: so once you publish your proposal, will it eventually be folded into enikanorov’s proposal?17:58
SumitNaiksatammarkmcclain: i am just trying to understand what process we are proposing here17:59
mandeepmarkmcclain: (that is the differences between the two approaches)17:59
*** badveli has joined #openstack-meeting-317:59
enikanorovi think right now it would require too much explanations from markmcclain, let's wait for the spec17:59
banix i think we can wait for markmcclain proposal and take it from there; I would think we could come up with an agreement quickly once both proposals are at hand.17:59
mandeepenikanorov: banix: OK18:00
mesterybanix: That's my hope as well, and we need flavors in Juno, so I expect a resolution to this that keeps everyone happy and moves Neutron forward.18:00
*** nati_ueno has joined #openstack-meeting-318:00
s3wongbanix: +118:00
LouisFmarkmcclain: can we get your proposal today?18:00
mandeepenikanorov: banix: I agree that with a proposal, my questions should be addressed18:01
pgpusAre we talking of this ? * Service Type - string identifier (LOADBALANCER, FWAAS, L3, VPN, etc)18:01
pgpus* Name - name of the flavor18:01
pgpus* Tags - string containing a list of (key, value) pairs (tags) that define capabilities.18:01
SumitNaiksatampgpus: that is the existing proposal18:01
*** dstanek has joined #openstack-meeting-318:01
enikanorovpgpus: it was a bit updated since then, but yes18:01
pgpusok18:01
banixSumitNaiksatam: when the proposal is out we may want to have a meeting on Friday perhaps?18:02
pcm_+118:02
*** Sukhdev has joined #openstack-meeting-318:02
*** rm_work|away is now known as rm_work18:02
SumitNaiksatambanix: sure18:02
pcm_SumitNaiksatam: Let's get an action item for delivery of the proposal, and an action item to have a meeting to discuss.18:02
s3wongbanix: are you suggesting that markmcclain should have the proposal written and ready by Thursday?18:02
pgpusyes we did discuss tags with key,value with some mandory fields per Service Type18:03
pcm_s3wong: Let's get a concrete estimate from markmcclain18:03
SumitNaiksatammestery markmcclain: does that sound like a good plan - have a meeting on friday to discuss the two proposals?18:03
banixs3wong: I think mestery said the proposal will be out some time soon today. If that is the case or we have it by tomorrow then we can meet on friday18:03
pgpusHow is this different from Mark's am I missing something?18:03
mesterySumitNaiksatam: +118:03
nati_ueno+118:03
enikanorovpgpus: let's wait for the detailed spec18:03
pgpusok18:04
nati_uenoI think we invested plenty time to discuss flavor stuff18:04
nati_ueno2 release cycles, right?18:04
SumitNaiksatamlast time i proposed that we have a discussion on this markmcclain -1’ed the idea since he was not available18:04
nati_uenoWe should choose some way18:04
SumitNaiksatamhence i am waiting for him to respond, if he is not available perhaps the meeting is pointless?18:04
enikanorovnati_ueno: true18:05
*** pballand has quit IRC18:05
garyduannati_ueno: +118:05
s3wongnati_ueno: +1... we definitely should18:05
SumitNaiksatamnati_ueno: yes, i think plenty of people share your frustration18:05
*** ttrifonov is now known as ttrifonov_zZzz18:05
banixhe is perhaps stuck in the other meeting and cannot read the current conversation; I think we will resolve this by this time next week ;)18:05
s3wongbanix: or resume this discussion next week :-)18:06
SridarKnati_ueno: +1 as a vendor, if flavors is going to arrive late J-2 or J-3 we are toast w.r.t getting vendor implementations out18:06
banixs3wong: i think we have all interested parties involved; we can get to an agreement in a week18:06
SumitNaiksatambanix: absolutely, i dont want to chalk up an action item for him without him even getting to see what it is18:06
mandeepmestery: as this is important for all services, can we put a deadline for this discussion/meeting?18:06
nati_uenoSridarK: yeah, not only vendor. FWaaS and VPNaaS is still experimental because of flavor18:07
mesteryI think per SumitNaiksatam we should plan for an IRC meeting on Friday.18:07
SridarKnati_ueno: yes absolutely18:07
nati_uenoHow about have a vote on the Friday meetings?18:07
nati_uenoLet's see multiple options18:07
LouisF+118:07
enikanorovhehe18:07
vinay_yadhav+118:07
natarajk+118:07
enikanorovokay18:07
garyduan+118:07
* mestery notes there is some upcoming dates around Spec Proposal and Spec Approval deadlines for Juno coming out soon ...18:07
pcm_+118:07
SridarK+118:07
mandeepbut the meeting is not much use unless markmcclain can join. Hence the request for a deadline18:07
s3wongnati_ueno: +1. Resolution by Friday, let's not have another 40 minutes discussion on flavor during next week's adv service meeting18:08
SumitNaiksatam#action SumitNaiksatam mestery markmcclain enikanorov to convene a meeting on friday june 27th to wrap up flavors blueprint spec18:08
nati_uenomestery: do you like voding idea?18:08
mesterynati_ueno: I hope we don't need to vote, and can instead incorporate ideas from the specs together. Consensus is the way forward. :)18:08
nati_uenos/voding/voting/18:08
pcm_mestery: +118:08
nati_uenomestery: yeah, it is best18:08
pgpusok put the meeting time on site and will follow up18:08
SumitNaiksatamdoes the same time as this meeting work for everyone?18:09
*** dstanek has left #openstack-meeting-318:09
banixmestery: agree and I think we can get there in short order… why am i so optimistic today :)18:09
SumitNaiksatamsame time same channel?18:09
mesterybanix: :)18:09
mandeepbanix: ;-)18:09
nati_uenomestery: however sometimes we need to go forward in time18:09
pgpusok18:09
banixSumitNaiksatam: yes18:09
pcm_SumitNaiksatam: time is OK for me.18:09
s3wongbanix: :-)18:09
mesterynati_ueno: Also very relevant. There are many balls in motion here, we all want the same thing, sometimes getting there requires a little sweat and tears. ;)18:09
nati_uenotime is ok for me too18:09
cathy_same time works for me. should we move on to the next topic and have everyone review the new Flavor proposal offline?18:09
vinay_yadhavok18:09
mestery+1 on time18:09
SridarKSumitNaiksatam: time works18:09
mandeepSumitNaiksatam: that time works for me as well18:10
nati_uenomestery: gotcha.18:10
s3wongso time would be 1730 UTC June 27 on #openstack-meeting-318:10
pgpusyou mean 11.30 AM PST istead of 10.30 AM PST Friday?18:10
SumitNaiksatam#agree meeting to wrap up flavors discussion on Jun 27th Friday 17.30 UTC (10.30 AM PDT) in -meeting-318:11
pgpusok18:11
*** coolsvap is now known as coolsvap|afk18:11
SumitNaiksatamok moving on :-)18:11
mandeep10:30 PDT (so it is 11:30 PST ;-)18:11
SumitNaiksatam#undo18:11
openstackRemoving item from minutes: <ircmeeting.items.Agreed object at 0x2ff5950>18:11
banixmandeep: “same time” is all i can follow18:12
SumitNaiksatam#agree meeting to wrap up flavors discussion on Jun 27th Friday 17.30 UTC (10.30 AM PST) in -meeting-318:12
SumitNaiksatammandeep pgpus: thanks :-)18:12
SumitNaiksatamenikanorov: we can move on right?18:12
enikanorovsure18:12
mandeepbanix: I agree - that is much easier18:12
SumitNaiksatamenikanorov markmcclain: thanks for the update18:12
s3wongcgoncalves: as I predicted, 70% ... actually it is closer to 80% :-)18:13
SumitNaiksatam#topic Service base definition and Insertion18:13
*** openstack changes topic to "Service base definition and Insertion (Meeting topic: Networking Advanced Services)"18:13
cgoncalvess3wong: :)18:13
SumitNaiksatams3wong: i hope you think we made progress though :-)18:13
SumitNaiksatam#link https://review.openstack.org/#/c/9312818:13
SumitNaiksatamso i dont see any -1s on this proposal18:14
mandeeps3wong: if you really want to talk numbers it was 73.46 %18:14
mandeeps3wong: ;-)18:14
SumitNaiksatamKanzhe s3wong: so are we all in agreement? :-)18:14
s3wongSumitNaiksatam: yep, enough +1s (there were more before Kanzhe posted the latest patch) to move forward18:14
KanzheSumitNaiksatam: So far, I haven't seen any outstanding issues.18:14
SumitNaiksatamKanzhe s3wong: so there are no blockers for you that you need to discuss here?18:15
KanzheSumitNaiksatam: not at this time.18:15
SumitNaiksatamideally more people from this team should be +1ing this in case they are in agreement, so that it sets up the stage for the cores to step in18:15
pgpusThis was good old L2, L3 insertion with contect or did it change missed on that?18:15
s3wongSumitNaiksatam: nope - and welcome SridarK to join us in making FWaaS work with service insertion framework18:15
LouisFKanzhe: what sort of Horizon work is needed to support service insertion?18:15
pgpuscontext I meant18:16
SridarKs3wong: yes absolutely glad to be of help18:16
marios_Kanzhe: am i still on for the vpn side?18:16
SumitNaiksatams3wong: yes sure, SridarK: thannks for jumping in18:16
SridarKno worries18:16
marios_Kanzhe: have started looking at the db models and service base18:16
Kanzhemarios_: yes, :-)18:16
SumitNaiksatammarios_: yes i was about to bring that up as well18:16
marios_Kanzhe: cool thx i will keep following18:16
banixSumitNaiksatam: are we aware of any cores outside this group with significant interest?18:16
SumitNaiksatammarios_: i noticed your comment as well, thanks much for jumping in18:16
banixSumitNaiksatam: i meant wrt service insertion18:17
*** mandeep has left #openstack-meeting-318:17
KanzheLouisF: We can discuss in detail once the db mode is up for review.18:17
SumitNaiksatambanix: i know that mestery nati_ueno markmcclain and rkukura have signed up18:17
marios_SumitNaiksatam: great to be of help have been following the various specs from summit18:17
banixSumitNaiksatam: what do you mean by  “signed up” sorry18:17
nati_uenoI'm OK with this spec. but I have one quick question. Why we don't support insertion type for network?18:18
SumitNaiksatambanix: see here #link https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan18:18
LouisFKanzhe: thx18:18
SumitNaiksatamKanzhe: nati_ueno’s question ^^^18:18
Kanzhenati_ueno: right now the thinking is subnet only. We can extend to network if use case comes up.18:19
s3wongnati_ueno: do you see such need?18:19
Kanzhenati_ueno: also to keep the first version simple.18:19
nati_uenoI think BGP based vpn network insersion18:19
nati_uenoKanzhe: OK. if so I can work this in another bp18:19
Kanzhenati_ueno: great! thanks.18:20
banixSumitNaiksatam: thanks. want to make sure we persuit them and get their views so we know if there are significant disagreements sooner rather that later. that’s all.18:20
s3wongnati_ueno: certainly, welcome to do so18:20
SumitNaiksatambanix: yes, its a chicken and egg kind of situation18:20
*** hurgleburgler has left #openstack-meeting-318:21
SumitNaiksatambanix: cores will probably not review if they dont see enough support from the sub team18:21
SumitNaiksatamok moving on18:21
KanzheAs s3wong pointed out, the spec lost a few +1's after I uploaded the latest version.18:21
SumitNaiksatam#topic Traffic steering18:21
*** openstack changes topic to "Traffic steering (Meeting topic: Networking Advanced Services)"18:21
SumitNaiksatamKanzhe: sure18:21
SumitNaiksatamKanzhe: hopefully we can get them back :-)18:22
SumitNaiksatamcgoncalves: your baby18:22
SumitNaiksatamcgoncalves: was the plan to post an updated spec based on input?18:22
cgoncalvesSumitNaiksatam: poor child18:22
KanzheSumitNaiksatam: yes. :-)18:22
cgoncalvesSumitNaiksatam: yes, but in the meantime we exchanged some emails18:22
cgoncalveslet me summarized my concerns to all18:23
cathy_cgoncalves: I have a suggestion on the API so that they do not have duplicate API functionality and is consistent among the two BP. Have you seen my comment?18:23
cgoncalvesservice chain (SC) BP is a high level BP18:23
cgoncalvescathy_: here? review.o.o?18:23
SumitNaiksatamcgoncalves: that is right18:23
cathy_I mean the GBP18:24
cgoncalvescathy_: yeah, I read it18:24
cgoncalvescathy_: let me just summarize my concerns first, please18:24
cathy_ok18:24
cgoncalvesso... I see some trending on SDN controllers like ODL and OpenContrail on supporting Service Function Chaining (SFC) / SC18:24
cgoncalvesthe way it's going, I'd say for the SC BP implementation it would be much better to interact directly with those controllers as drivers rather than the traffic steering (TS)18:25
cgoncalvesin that way, SC would not depend on TS18:26
SumitNaiksatamcgoncalves: that is one option18:26
nati_uenocgoncalves: +118:26
cgoncalvesalthough, I think there is no plan yet on how to steer traffic to chains18:26
*** yamamoto has joined #openstack-meeting-318:26
cgoncalvessame should be valid for the GBP work as they are considering the 'redirect' action to a SC18:26
SumitNaiksatamcgoncalves: that said, as i was mentioning on the email thread, i think have precendence of using the controller-less OVS-based reference implementation18:26
SumitNaiksatamneutron has, that is18:27
cgoncalvesSumitNaiksatam: for the SC BP?18:27
*** mwagner_lap has joined #openstack-meeting-318:27
banixcgoncalves: no in general18:27
SumitNaiksatamcgoncalves: for any backend supporting the API18:27
SumitNaiksatamcgoncalves: any feature that is18:27
cgoncalvesbanix, SumitNaiksatam: ah, right18:27
LouisFcgoncalves: GBP redirect action will steer traffic to SFC18:28
SumitNaiksatamLouisF: GBP will only signal that intent18:28
cgoncalvesLouisF: ok, that's the part I'd like to know better. how does GBP will steer traffic to SFC?18:28
* SumitNaiksatam thinks we need another dedicated meeting for TS bp spec as well!18:29
cgoncalvesTS could be used by GBP, and any other work, to steer traffic to a SC for instance18:29
cgoncalvesSumitNaiksatam: :)18:29
*** samchoi has joined #openstack-meeting-318:29
pgpusSC can define Policies but traffic steering can simply focus on different ways to control flows and so we here provide primitives for use cases may SC is one of the users18:29
* SumitNaiksatam thinks may be we should just have a weeklong Adv Services’ hackathon ;-)18:29
banixSumitNaiksatam: :)18:29
* SumitNaiksatam or “mini-summit"18:29
cathy_cgoncalves: agree, that TS could be used by GBP, that is why my API proposal18:30
s3wongSumitNaiksatam: you are too optimistic - we are far from hacking code yet18:30
cgoncalvesSumitNaiksatam: yeah! Paris next week? :)18:30
LouisFcgoncalves: a match in a GBP policy rule results in redirect action18:30
SumitNaiksatams3wong: i meant mini-summit actually :-)18:30
SumitNaiksatamanyway, seems like this is a longer discussion18:30
cgoncalvescathy_: exactly, but TS would still add support to traffic classification18:30
SumitNaiksatammainly, cgoncalves LouisF cathy_ you need to reconcile?18:30
SumitNaiksatamor is it more folks?18:30
s3wongcgoncalves: I actually would agree with that - so once TS is available, GBP's mapping driver can utilize it18:31
LouisFcgoncalves: GBP policy rule has a classifier18:31
*** morganfainberg_L has quit IRC18:31
cgoncalvesI'd like everyone's opinion on this as it would considereably change the TS BP18:31
*** yamamoto has quit IRC18:31
cathy_cgoncalves: GBP already has classifier specification in its "redirect to chain" API. How do we make sure these two classifiers are consistent.18:31
SumitNaiksatamcathy_ LouisF: the GBP classifier is application centric classifier18:32
cgoncalvesLouisF: I know but TS should not be specific to GBP as other works may rely on and need classification on TS18:32
banixcgoncalves: opinion on “this” you wrote; can you specify what “this” is18:32
SumitNaiksatamso its L418:32
jmsoarescgoncalves, SumitNaiksatam, cathy_: I also think the TS should be thought beyond the SC functionality. SC needs TS, but TS can possibly enable other things.18:32
SumitNaiksatamcgoncalves: i agree with you18:32
s3wongcathy_: in that case, the mapping driver would set the TS classifier - which may or may not have anything to do with GBP policy-rule classifier18:32
cathy_I am OK with TS having classifier if we can have a way to solve the consistency issue18:32
pgpusAgree with Summit traffic steering involves classification of packets or flows how it viwes may differ from SC18:32
SumitNaiksatamjmsoares: i agree hence we separated this out18:32
*** OSM has joined #openstack-meeting-318:32
cgoncalvesbanix: instead of TS be used for chaining, it should be the other way. TS steering traffic to chains18:33
* SumitNaiksatam makes a customary apology to the FWaaS folks for eating into their meeting time!18:33
s3wongOK guys, 3 minutes overtime already :-)18:33
cathy_SumitNaiksatam: the GBP classifier will be pulled into the intent of service chain through "redirect" action18:33
SumitNaiksatamcathy_: shall we discuss the GBP specifics in teh GBP meeting tomorrow?18:33
SumitNaiksatamcathy_: we will have more time there18:33
marios_goodnight all18:34
cgoncalvescathy_: we can indeed come up with a compatible/same classifier resource or even share them, but both BPs should have their own classification APIs18:34
LouisFSumitNaiksatam: +118:34
SumitNaiksatamcgoncalves jmsoares: unfortunately it does not seem like we can resolve this right now18:34
jmsoaresSumitNaiksatam: yes, this is only to highlight that TS is by itself a functionality, that by nature I believe it needs the "classifier" entity18:34
* s3wong feels sorry that vinay_yadhav never got a chance to update TapaaS over the last several weeks18:34
SumitNaiksatamcgoncalves: any chance you can fire up a -dev thread?18:34
vinay_yadhav:)18:34
cgoncalvesSumitNaiksatam: sure, will do18:34
banixcgoncalves: yes thanks18:34
cathy_SumitNaiksatam: ok18:35
anil_raoA suggestion: Can we proceed through the Specs in round-robin fashion from next week?18:35
vinay_yadhavCan we get some time for TaaS next week18:35
SumitNaiksatamanil_rao vinay_yadhav: yes sure, and our apologies18:35
cgoncalvesanil_rao: in order to give everyone a chance to present their work, I agree with you18:35
s3wonganil_rao: as in - let's start with TapaaS first next week :-)18:35
anil_raoThanks. :)18:36
vinay_yadhavthanx18:36
marios_ani18:36
SumitNaiksatamwe do have to prioritize based on what is higher prirority for Juno though18:36
SumitNaiksatambut we will take up TAPaaS next time first18:36
marios_s3wong: am always up for tapas ;)18:36
SumitNaiksatammarios_: :D18:36
SumitNaiksatam#topic open discussion18:36
*** openstack changes topic to "open discussion (Meeting topic: Networking Advanced Services)"18:36
anil_rao:D18:36
s3wongSumitNaiksatam: if we indeed can come to a resolution this Friday on flavor, I think next week's meeting will have plenty of time :-)18:36
SumitNaiksatamany parting thoughts?18:36
cgoncalvesmarios_: I was also having the exact same thought :D18:37
SumitNaiksatams3wong: absolutely :-)18:37
cathy_cgoncalves: agree with your suggestion on same classifier resource and share with them18:37
LouisFSumitNaiksatam: time of flavor meeting on Friday?18:37
SumitNaiksatamalright 7 minutes over18:37
SumitNaiksatamLouisF: 17.30 UTC (10.30 AM pST)18:37
LouisFthx18:37
cgoncalvescathy_: problem will be coordination as I believe the GBP work is quite advanced when compared to TS at the moment18:37
SumitNaiksatamalright thanks everyone!18:38
cathy_cgoncalves: agree. as long as no conflict on classfier specification in two APIs, I am fine.18:38
marios_o/ night then18:38
banixthank you18:38
anil_raoThanks.18:38
banixbye everybody18:38
cgoncalvesthanks18:38
cgoncalvescathy_: yes18:38
vinay_yadhavbye thanx18:38
SumitNaiksatamcgoncalves cathy_: lets continue in the GBP meeting tomorrow18:38
SumitNaiksatambye all!18:38
SumitNaiksatam#endmeeting18:38
*** anil_rao has left #openstack-meeting-318:38
cathy_ok18:38
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:38
openstackMeeting ended Wed Jun 25 18:38:25 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-06-25-17.31.html18:38
cathy_tahnsk18:38
s3wongthanks, guys!!!18:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-06-25-17.31.txt18:38
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_advanced_services/2014/networking_advanced_services.2014-06-25-17.31.log.html18:38
*** igordcard has quit IRC18:38
cathy_bye18:38
jmsoarescgoncalves, cathy_: maybe we are not able to converge in a short term to a single "classifier", but can point as a mid-term goal18:38
*** OSM has left #openstack-meeting-318:38
banixSumitNaiksatam: i am not sure where mark will post his spec; do you know?18:38
SumitNaiksatambanix: no idea18:38
SumitNaiksatambanix: i have been checking the spec repository (very often :-) )18:39
cathy_let's discuss in the email thread that cgoncalves will initiate18:39
SumitNaiksatambanix: in anticipation18:39
banixSumitNaiksatam: ok will have to keep our eyes open. wide open :)18:39
SumitNaiksatamFWaaS folks here - SridarK, garyduan, beyounn, badveli, prad_?18:39
beyounnyes18:39
SridarKHi All18:39
SumitNaiksatamok lets get started18:40
banixcathy_: sounds good18:40
SridarKprad_ cannot make it today18:40
*** cathy_ has quit IRC18:40
garyduanhi18:40
SumitNaiksatam#startmeeting Networking FWaaS18:40
openstackMeeting started Wed Jun 25 18:40:55 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:40
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:40
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:40
openstackThe meeting name has been set to 'networking_fwaas'18:40
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/FWaaS18:41
SumitNaiksatam#topic Action Item follow up18:41
*** openstack changes topic to "Action Item follow up (Meeting topic: Networking FWaaS)"18:41
SumitNaiksatam#link https://wiki.openstack.org/wiki/Meetings/FWaaS#Action_items_from_previous_meeting18:41
SumitNaiksatambeyounn: have we sent the DVR related email to the mailer?18:41
beyounnno, I did not18:41
* SumitNaiksatam thinks whether its past its relevance to send it now18:42
*** LouisF has quit IRC18:42
SumitNaiksatambeyounn: last week you mentioned you were going to, any blockers?18:42
beyounnOk, I will do18:42
SumitNaiksatambeyounn: we want this to be on record18:42
*** jmsoares has quit IRC18:42
beyounnThe issues is that I don't have a idea on the direction for this18:43
SumitNaiksatambeyounn: that we have identified the issues18:43
SumitNaiksatambeyounn: thats fine18:43
SumitNaiksatambeyounn: the expectation is not necessarily that you provide you a solution18:43
beyounnI throw it out, only makes open end problem, anyway, I will do it18:43
SumitNaiksatambeyounn: identifying and raising the issue is the first step18:43
beyounnOK18:43
SumitNaiksatamSridarK: were you able to check with the owner of  https://bugs.launchpad.net/neutron/+bug/1323299?18:44
SumitNaiksatamoh wait i put a comment here18:44
*** vinay_yadhav has quit IRC18:45
SridarKSumitNaiksatam: no since i saw that u have updated the bug that this is expected behaviour18:45
SridarKSumitNaiksatam: yes18:45
SumitNaiksatamSridarK: ok18:45
SridarKso this can be closed i think ?18:45
*** zehicle_at_dell has joined #openstack-meeting-318:45
SumitNaiksatamSridarK: lets wait for him to come back18:45
SridarKok18:46
SumitNaiksatamSridarK: i think we can certainly have a discussion on how we can extend to this functionality18:46
SumitNaiksatamSridarK: right?18:46
SridarKyes18:46
*** yamamoto has joined #openstack-meeting-318:46
SumitNaiksatamSridarK: i guess you are asking if the AI can be closed?18:46
SumitNaiksatamSridarK: if so yes, lets just keep an eye if the author comes back18:46
SridarKactually i was asking about the bug18:46
SridarKbut i see ur point18:46
SumitNaiksatamSridarK: ah18:47
SumitNaiksatamSridarK: what about following up with #link https://review.openstack.org/#/c/90575/18:47
*** jackib has joined #openstack-meeting-318:47
SumitNaiksatami am not able to locate his coordinates18:47
SridarKYes i have discussed with SridharGaddam18:47
SumitNaiksatamSridarK: ah cool18:47
SridarKHe has responed to Mark's comments and waiting response18:47
SridarKI requested him to ping him on IRC18:47
SumitNaiksatamSridarK: but the last response is June 5th18:48
SridarKHe will follow up -18:48
SumitNaiksatamSridarK: i did bring this up with markmcclain in the neutron IRC18:48
SumitNaiksatamSridarK: i think we should try and get them together18:48
SumitNaiksatamSridarK: but you have a -1 as well on this18:48
SridarKI also asked him to join the mtg today - is bit late for SridharG18:48
SumitNaiksatamSridarK: are your concerns addressed?18:49
SridarKSumitNaiksatam: yes - my issue which was earlier is on the same line of composing plugin on agent18:49
SridarKbut i am not sure on the right approach18:49
SridarKMark pretty much put the -2 for this i believe18:49
SumitNaiksatamSridarK: so do you plan to remove the -1 or keep it?18:49
SridarKI think if it is okay to take this approach - then i can add some more things that can be done18:50
SridarKbut if this approach is itself wrong then we need to abandon or take a diff approach18:51
SumitNaiksatamgaryduan beyounn: have you looked at this?18:51
*** yamamoto has quit IRC18:51
SridarKperhaps we can discuss this more as well18:51
SumitNaiksatami had looked at this earlier, but i have lost a bit of context on it since18:51
SridarKwill send u an email18:51
SridarKand we can discuss more amongst the team18:51
garyduanyes18:52
*** MaxV has joined #openstack-meeting-318:52
SridarKmy concern was loading composing the plugin in the agent side18:52
SridarK*composing18:53
SumitNaiksatamSridarK: you seemed to have asked for UTs as well18:53
SridarKyes minor issue on the UT18:53
SumitNaiksatam#action SridarK to start an email thread with FWaaS team and SridharGaddam regarding https://review.openstack.org/#/c/9057518:53
SridarKI think if we can conclude that this approach is fine - i am good - i will point him to a few more checks that can be added18:53
SumitNaiksatamSridarK: lets try to close on this18:53
SridarKok will do18:53
garyduanThe proposed fix is good to have, right?18:54
garyduanbut not that critical18:54
SumitNaiksatamgaryduan: please weigh in as well, i have added you as reviewer18:54
SumitNaiksatamSridarK: you can add markmcclain to the thread as well18:54
SridarKok18:54
garyduanOk18:54
*** jackib has quit IRC18:55
SumitNaiksatamSridarK: next AI for you again, how is the bug triage coming along?18:55
SridarKAll bugs triaged18:55
SumitNaiksatamSridarK: ah ok18:55
SridarKI don't have rights to mark it as Triaged18:55
SumitNaiksatamSridarK: oh18:55
SridarKSumitNaiksatam: perhaps only u can do it18:56
SumitNaiksatamSridarK: ok i can follow up on that18:56
SumitNaiksatamSridarK: whats the best way to sync up?18:56
SridarKok there were only 2 that needed action18:56
SumitNaiksatamSridarK: i want to minimize the effort on your end18:56
*** chuckC has quit IRC18:56
SridarKi have added comments to the bugs18:56
SumitNaiksatamSridarK: ok18:56
SridarKSumitNaiksatam: i can send u an email18:56
SumitNaiksatamSridarK: alright great, thanks much!18:57
SridarKand u can mark it Triaged or if i can be given rights i can do so18:57
SridarKnp18:57
SridarKSumitNaiksatam: we can sync up offline18:57
SumitNaiksatamSridarK: unfortunately i dont have the admin rights to any of this, i am just as much of a foot soldier :-)18:57
SridarKSumitNaiksatam: :-)18:58
SridarKIt says u need to be "Bug Supervisor"18:58
SridarKwhatever that means :-)18:58
SumitNaiksatamSridarK: perhaps part of the cavalry :-P18:58
SridarKnot a big deal - i will push u a list and u can mark it so18:58
SridarK:-)18:58
SumitNaiksatamSridarK: regarding the router delete18:59
SumitNaiksatami noticed that there was a similar bug for VPNaaS about deleting interfaces18:59
SridarKSumitNaiksatam: yes that has been updated on the associated bug18:59
SridarKSumitNaiksatam: as we discussed last week18:59
SumitNaiksatamand out there they are taking the approach that they are not allowing the interface delete18:59
SumitNaiksatamSridarK: yeah, should we follow that approach as well?19:00
SridarKSumitNaiksatam: i think we will do the same with service insertion patch19:00
SumitNaiksatamthis is question for all19:00
SumitNaiksatamnot allow interface or router delete if firewall is associated?19:00
*** Kanzhe_ has joined #openstack-meeting-319:00
*** Kanzhe has quit IRC19:00
*** Kanzhe_ is now known as Kanzhe19:00
SridarKSumitNaiksatam: as we will now track the router in the plugin db19:00
garyduanI agree19:00
SumitNaiksatambut perhaps its different for firewall, since it will temporarily open up a security hole19:00
SumitNaiksatamSridarK garyduan: see my last comment ^^^19:01
garyduanSumitNaiksatam: that makes sense too19:01
SridarKSumitNaiksatam: yes19:01
garyduanthen should we update firewall state?19:01
SumitNaiksatamgaryduan: but then it does not solve the problem19:02
SridarKgaryduan: that gets tricky on the "all routers in tenant" scenario19:02
*** mwagner_lap has quit IRC19:02
SumitNaiksatamSridarK: perhaps we have to wait fall back to the service insertion related fix19:02
garyduanWhy do we have PENDING state associated with if there is a router or not?19:03
SridarKSumitNaiksatam: my feeling too as it is a lot cleaner19:03
SumitNaiksatamSridarK: and let anyone who wants to fix it in the interim do it, if they want to19:03
SridarKSumitNaiksatam: yes so left the bug unassigned as we discussed19:03
*** pballand has joined #openstack-meeting-319:03
SumitNaiksatamgaryduan: PENDING is when an operation is in process19:03
garyduancan we see if firewall is pushed to agent, we mark it as active?19:03
garyduansee=say19:04
SumitNaiksatamgaryduan: i dont think its proper to move a firewall from ACTIVE to PENDING if the router is deleted, is it?19:04
garyduanSumitNaiksatam: I agree19:04
SridarKesp if there are other routers in the tenant19:04
SridarKwe need to do it for last router in the tenant19:04
garyduanSumitNaiksatam: but people might ask question about consistency19:04
garyduanso why don't we mark it as active when fw is created without router19:05
SumitNaiksatamgaryduan: definitely not that19:05
SridarKgaryduan: as there is no router it really cannot be active19:05
garyduanI am totally ok with that19:06
SumitNaiksatamgaryduan: you can make a case for moving it to PENDING when the router is deleted19:06
garyduanI am just thinking that people might ask questions19:06
*** jamiehannaford has quit IRC19:06
SumitNaiksatamgaryduan: can you elaborate on the question that people might ask?19:07
SumitNaiksatamgaryduan: sorry i must have missed it19:07
SridarKSumitNaiksatam: garyduan yes that case of router delete - is valid - but we almost would need to say that is PENDING_DELETE on that router but it is still active on other routers19:07
garyduanwhen fw is created without router, it's pending19:07
garyduanwhen the only router that fw uses is deleted, it's active19:07
garyduanthat's not consistent19:07
*** yjiang5 is now known as yjiang5_away19:08
garyduanSridarK also raised a question, which is if fw is applied on multiple router19:08
garyduanwe have to track them19:08
garyduanto maintain the firewall state19:08
SridarKgaryduan: yes that is a problem for sure - but we don't track them as we were always looking at insertion to get away from the model of all routers on tenant19:08
SumitNaiksatamgaryduan: that is the problem that we are trying to solve19:09
SumitNaiksatamgaryduan: we know that it is inconsistent, no argument on that :-)19:09
SridarKI think we can solve that problem but will require some cycles and this will get solved with insertion so why not just wait for that19:09
*** jamiehannaford has joined #openstack-meeting-319:09
garyduanI agree. If we do want to have PENDING state, then some cleanup need to be done19:09
SridarKand solve this issue in that context19:09
SumitNaiksatamgaryduan: just whether we should fix it now (and the fix is kind of intensive) or wait for the service insertion to come through so taht we can do it in an elegant way19:10
garyduanI'd say wait for service insertion19:10
SumitNaiksatamSridarK: yeah, basically repeating what SridarK said19:10
SumitNaiksatamgaryduan: exactly19:10
SumitNaiksatamgaryduan: so we are all on the same page :-)19:10
SridarKso it is documented to that effect on the bug19:10
garyduanalways19:10
SridarKso we will just leave this as is for now19:12
garyduanagree19:12
SumitNaiksatamok moving on19:12
SumitNaiksatamthe AI was beyounn badveli to decide if they can look at hit counts19:13
SumitNaiksatamhowever i think we discussed this19:13
SumitNaiksatamand we are not looking at this now19:13
SumitNaiksatamor rather immediately19:13
SridarKSumitNaiksatam: on that point prad_ was quite interested in this19:13
SridarKI did tell him that in terms of resources - both dev and review - it was decided that it is tight19:14
SumitNaiksatamSridarK: we can help him in any way he needs help19:14
*** sarob has quit IRC19:14
SridarKSumitNaiksatam: yes for sure - we will defn get the lifecycle metrics19:15
*** pgpus has quit IRC19:15
*** sarob has joined #openstack-meeting-319:15
SridarKand on hit counts lets see how it goes if beyounn and badveli have time constraints19:15
SridarKbut clearly he indicated that it is high on his priority list19:16
badveli ok19:16
SumitNaiksatamSridarK: please convey to prad_ that we are willing to help him if he is ready to take the lead on this19:16
SumitNaiksatamSridarK: by we, i mean the entire team here19:16
SridarKSumitNaiksatam: will do19:16
beyounnSridark, we will try to help as much as we can19:16
SumitNaiksatambeyounn: great, ye19:17
SridarKok got it thanks SumitNaiksatam beyounn19:17
SumitNaiksatami can also propose that, if it comes to that, we can all have a day long hackathon with prad_ at the other end19:17
SumitNaiksatamand just walk him through19:17
SridarKSumitNaiksatam: sure i think that will be great19:17
garyduanya19:17
SumitNaiksatamSridarK: so basically let prad_ propose this and we will be happy to participate (i take the liberty of speaking on behalf of the entire team)19:18
*** Sukhdev has quit IRC19:18
SumitNaiksatamSridarK: we can try and request Rajesh as well, perhaps buy him a lunch first ;-)19:18
SridarKI will also check with RajeshM on the feasibility and to see if we can get some guidance19:18
SridarKSumitNaiksatam: on the same page :-)19:19
SumitNaiksatamSridarK: :-)19:19
SumitNaiksatamok we are going slow today19:19
SumitNaiksatamwe still have one more AI19:19
SumitNaiksatamif we do decide to do the hit counts, i would like to see a spec in review at the earliest (on the neutron side)19:19
*** sarob has quit IRC19:19
SumitNaiksatamthis is an AI for prad_ possibly19:20
SridarKSumitNaiksatam: will convey19:20
SumitNaiksatamSridarK: thanks19:20
SumitNaiksatam#topic Bugs19:20
*** openstack changes topic to "Bugs (Meeting topic: Networking FWaaS)"19:20
SumitNaiksatamok i think we already covered most of this19:20
SumitNaiksatamSridarK: anything that we did not cover?19:20
SridarKSumitNaiksatam:  no we are good19:20
SumitNaiksatamok19:21
SumitNaiksatam#topic blueprint tracking19:21
*** openstack changes topic to "blueprint tracking (Meeting topic: Networking FWaaS)"19:21
SumitNaiksatamservice objects #link https://review.openstack.org/#/c/9413319:21
SumitNaiksatambeyounn: ?19:21
*** pballand has quit IRC19:21
beyounnyes19:21
beyounnI have sent email to Kyle nachi and others19:22
beyounnbut I did not get any activities from them19:22
beyounnVashnu helped me to update the db migration script, I'm about to wake up my code review19:22
beyounnThat is all for me19:23
*** chuckC has joined #openstack-meeting-319:23
beyounnBTW-- since I have updated spec based on our last discussion, I hope everyone can also do a recheck, just in case I missed anything19:24
SumitNaiksatambeyounn: yes19:24
SridarKbeyounn: will do19:24
SumitNaiksatambeyounn: thanks19:24
beyounnThanks all19:24
*** thinrichs has joined #openstack-meeting-319:24
garyduanwill do19:24
SumitNaiksatambeyounn: since we did not get a response from nati_ueno amotoki, perhaps better to follow up further19:24
beyounnYes, I will send email this friday (once a week)19:25
SumitNaiksatam#action beyounn to follow up with nati_ueno and amotoki, request them to review #link https://review.openstack.org/#/c/9413319:25
beyounnI hope they are not mad at me :-)19:25
SumitNaiksatambeyounn: perhaps trying to catch them on IRC will be more helpful19:25
SumitNaiksatambeyounn: i will respond to the email thread19:25
beyounnSumit: thanks19:26
SumitNaiksatam#action SumitNaiksatam to respond to beyounn’s email thread on service objects review19:26
SumitNaiksatam#topic vendor blueprints19:26
*** openstack changes topic to "vendor blueprints (Meeting topic: Networking FWaaS)"19:26
SumitNaiksatamSridarK: anything to discuss here?19:26
SridarKSumitNaiksatam: nothing - working with our group to get a review up19:27
SumitNaiksatamSridarK: ok thanks19:27
SumitNaiksatam#topic open discussion19:27
*** openstack changes topic to "open discussion (Meeting topic: Networking FWaaS)"19:27
*** jcoufal_bbl has quit IRC19:28
SridarKwe plan to have a single spec to address plugin and agent/driver19:28
SumitNaiksatambeyounn: i noticed you sent the email about DVR19:28
SumitNaiksatamSridarK: ok19:28
SridarKand have separate patches referring to the same BP19:28
SumitNaiksatamSridarK: single spec is fine, perhaps patches need to be separate19:28
SumitNaiksatamSridarK: yeah, you said it :-)19:28
SridarKSumitNaiksatam: ok perfect that is the plan19:28
SumitNaiksatambeyounn: thanks for doing that19:28
SridarK:-)19:28
SumitNaiksatambeyounn: but we want this to be sent to the openstack-dev alias19:29
SumitNaiksatambeyounn: sorry for being pushy on this19:29
beyounnSumit: it is still not mail list19:29
beyounnSumit: it is ok, I just really at least  get some progress before dump it to the ML19:29
SumitNaiksatambeyounn: we need to describe the issue and send to the -dev mailer19:29
SumitNaiksatambeyounn: so that it comes to the attention of the neutron cores19:29
SumitNaiksatambeyounn: we can have a discussion on the solution in parallel19:30
SumitNaiksatambeyounn: but others have to know that this issues exists, since the cores will be approving the DVR patches19:30
garyduanbeyonunn is on a meeting now.19:30
beyounnok19:30
*** Sukhdev has joined #openstack-meeting-319:31
SumitNaiksatambeyounn garyduan: thanks19:31
beyounnYes, I have to run to another meeting, talk to you guys later19:31
SumitNaiksatamalright, lets call it a wrap on that happy note then19:31
SridarKok cool19:31
SumitNaiksatamthanks all for joining!19:31
SumitNaiksatambye!19:32
SridarKthanks19:32
SridarKbye19:32
garyduanbye19:32
SumitNaiksatam#endmeeting19:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:32
openstackMeeting ended Wed Jun 25 19:32:08 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-06-25-18.40.html19:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-06-25-18.40.txt19:32
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2014/networking_fwaas.2014-06-25-18.40.log.html19:32
*** alexpilotti has quit IRC19:32
*** Kanzhe has quit IRC19:32
*** pcm_ has left #openstack-meeting-319:38
*** pballand has joined #openstack-meeting-319:38
*** yamamoto has joined #openstack-meeting-319:46
*** Kanzhe has joined #openstack-meeting-319:47
*** MaxV has quit IRC19:49
*** pballand has quit IRC19:49
*** yamamoto has quit IRC19:51
*** shakamunyi has quit IRC19:52
*** erecio has quit IRC19:52
*** shakamunyi has joined #openstack-meeting-319:53
*** zehicle_at_dell has quit IRC19:54
*** erecio has joined #openstack-meeting-319:57
*** pballand has joined #openstack-meeting-319:59
*** otherwiseguy has quit IRC19:59
*** jamiehannaford has quit IRC20:00
*** jtomasek has joined #openstack-meeting-320:03
*** pballand has quit IRC20:03
*** sarob has joined #openstack-meeting-320:05
*** jackib has joined #openstack-meeting-320:08
*** MaxV has joined #openstack-meeting-320:09
*** pballand has joined #openstack-meeting-320:10
*** mwagner_lap has joined #openstack-meeting-320:18
*** pballand has quit IRC20:31
*** lcheng has joined #openstack-meeting-320:32
*** jtomasek has quit IRC20:34
*** otherwiseguy has joined #openstack-meeting-320:34
*** peristeri has quit IRC20:36
*** peristeri has joined #openstack-meeting-320:37
*** jtomasek has joined #openstack-meeting-320:38
*** cuddyt has joined #openstack-meeting-320:38
*** yamamoto has joined #openstack-meeting-320:46
*** badveli has quit IRC20:48
*** peristeri has quit IRC20:50
*** peristeri has joined #openstack-meeting-320:50
*** yamamoto has quit IRC20:51
*** yjiang5_away is now known as yjiang520:52
*** jackib has quit IRC20:53
*** erecio has quit IRC20:56
*** natarajk has left #openstack-meeting-321:04
*** jtomasek has quit IRC21:07
*** mfer has quit IRC21:09
*** MaxV has quit IRC21:14
*** julim has quit IRC21:16
*** lblanchard has quit IRC21:20
*** julim has joined #openstack-meeting-321:20
*** HenryG has quit IRC21:23
*** julim has quit IRC21:24
*** pballand has joined #openstack-meeting-321:30
*** Sukhdev has quit IRC21:31
*** jaypipes has quit IRC21:34
*** yamamoto has joined #openstack-meeting-321:46
*** nelsnelson has quit IRC21:49
*** chuckC has quit IRC21:49
*** pballand has quit IRC21:50
*** yamamoto has quit IRC21:51
*** thomasem has quit IRC21:52
*** jamiehannaford has joined #openstack-meeting-321:54
*** peristeri has quit IRC21:57
*** pballand has joined #openstack-meeting-321:58
*** david-lyle has quit IRC21:59
*** david-lyle has joined #openstack-meeting-321:59
*** yjiang5 is now known as yjiang5_away22:02
*** yjiang5_away has quit IRC22:02
*** david-lyle has quit IRC22:03
*** carl_baldwin has quit IRC22:06
*** markmcclain has quit IRC22:08
*** cuddyt has quit IRC22:10
*** chuckC has joined #openstack-meeting-322:12
*** jackib has joined #openstack-meeting-322:20
*** shakamunyi has quit IRC22:31
*** sarob has quit IRC22:34
*** gduan has joined #openstack-meeting-322:35
*** lcheng has quit IRC22:37
*** garyduan has quit IRC22:38
*** lcheng has joined #openstack-meeting-322:44
*** markmcclain has joined #openstack-meeting-322:45
*** yamamoto has joined #openstack-meeting-322:46
*** shakamunyi has joined #openstack-meeting-322:46
*** shakamunyi has quit IRC22:47
*** beyounn has quit IRC22:47
*** yamamoto_ has joined #openstack-meeting-322:48
*** markmcclain has quit IRC22:49
*** yamamoto has quit IRC22:51
*** jpomero has quit IRC22:51
*** shakamunyi has joined #openstack-meeting-322:52
*** yamamoto_ has quit IRC22:52
*** beyounn has joined #openstack-meeting-322:54
*** garyduan has joined #openstack-meeting-322:55
*** gduan has quit IRC22:56
*** markmcclain has joined #openstack-meeting-323:01
*** jamiehannaford has quit IRC23:02
*** seizadi has joined #openstack-meeting-323:04
*** erw has quit IRC23:10
*** seizadi has quit IRC23:13
*** erw has joined #openstack-meeting-323:14
*** otherwiseguy has quit IRC23:14
*** Sukhdev has joined #openstack-meeting-323:14
*** seizadi has joined #openstack-meeting-323:15
*** jamiehannaford has joined #openstack-meeting-323:23
*** peristeri has joined #openstack-meeting-323:23
*** pballand has quit IRC23:25
*** shakamunyi has quit IRC23:27
*** shakamunyi has joined #openstack-meeting-323:28
*** banix has quit IRC23:30
*** s3wong has quit IRC23:31
*** pballand has joined #openstack-meeting-323:32
*** jackib has quit IRC23:36
*** peristeri has quit IRC23:37
*** SumitNaiksatam has quit IRC23:39
*** lcheng has quit IRC23:43
*** yamamoto has joined #openstack-meeting-323:46
*** yamamoto has quit IRC23:51

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