Thursday, 2014-11-13

*** ycombinator_ has joined #openstack-meeting-300:00
*** shakamunyi has quit IRC00:01
*** shakamunyi has joined #openstack-meeting-300:03
ycombinator_are we having the api-wg meeting here?00:03
miguelgrinbergI hope so00:03
sigmavirus24yes00:04
sigmavirus24We should be.00:04
sigmavirus24It's 2000UTC00:04
sigmavirus24actually 2004UTC =P00:04
*** dconde has quit IRC00:04
miguelgrinberg20? it is 00:00 of tomorrow UTC00:04
sigmavirus24sorry yeah00:05
sigmavirus24mixing up my meeting times00:05
sigmavirus24just added one to my calendar at 200000:05
ycombinator_@cyeoh, are we doing the meeting?00:05
* sigmavirus24 isn't braining well today00:05
sigmavirus24technically any one of us could run it00:05
sigmavirus24kashyap: you around?00:06
ycombinator_okay, why don't we start and then maybe @cyeoh, Jay Pipes or Everett Toews might join and take over00:07
ycombinator_#startmeeting api wg00:08
openstackMeeting started Thu Nov 13 00:08:11 2014 UTC and is due to finish in 60 minutes.  The chair is ycombinator_. Information about MeetBot at http://wiki.debian.org/MeetBot.00:08
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.00:08
*** openstack changes topic to " (Meeting topic: api wg)"00:08
openstackThe meeting name has been set to 'api_wg'00:08
ycombinator_#topic roll call00:08
*** openstack changes topic to "roll call (Meeting topic: api wg)"00:08
ycombinator_Shaunak Kashyap, Rackspace00:08
*** david-lyle_afk is now known as david-lyle00:10
sigmavirus24Ian Cordasco, Rackspace00:10
* sigmavirus24 looks at miguelgrinberg 00:10
miguelgrinbergMiguel Grinberg, Rackspace (heh)00:10
ycombinator_#topic agenda00:10
*** openstack changes topic to "agenda (Meeting topic: api wg)"00:10
ycombinator_https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda00:11
ycombinator_actually I think that should be #link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda00:11
sigmavirus24I think the first topic would be "Summit Review" anyway00:11
ycombinator_#topic summit review00:12
*** openstack changes topic to "summit review (Meeting topic: api wg)"00:12
ycombinator_@sigmavirus24, @miguelgrinberg were either of you at the summit?00:12
miguelgrinbergNo00:12
sigmavirus24I don't think either of us were, no00:12
ycombinator_okay, should we skip to the next topic then?00:12
miguelgrinbergwas there any related discussions in Paris?00:13
ycombinator_I wasn't at the summit either so I can't say00:13
sigmavirus24miguelgrinberg: judging by the etherpad, yes00:13
sigmavirus24https://etherpad.openstack.org/p/kilo-crossproject-api-wg00:13
ycombinator_thanks @sigmavirus2400:13
miguelgrinbergmaybe we push it for later when others that were there join?00:14
*** SumitNaiksatam has quit IRC00:14
ycombinator_sounds good to me00:14
ycombinator_#topic additional meeting time00:14
*** openstack changes topic to "additional meeting time (Meeting topic: api wg)"00:14
ycombinator_https://review.openstack.org/#/c/132668/00:14
sigmavirus24Looks like it was already accepted00:15
*** stevelle has joined #openstack-meeting-300:15
*** rrrobbb has joined #openstack-meeting-300:15
ycombinator_yeah, its on the agenda but I think its already done00:15
sigmavirus24So next week's meeting will be 4 hours earlier :)00:15
sigmavirus24e 8 hours00:15
* sigmavirus24 keeps thinking it's 2000 utc still00:15
miguelgrinbergyeah, it's 8 I think00:16
ycombinator_yeah 8 hours earlier00:16
miguelgrinberg8am for me :-(00:16
ycombinator_hold on, won't it be 16 hours later?00:16
sigmavirus24don't listen to me about timezones00:17
miguelgrinbergit's 8 hours earlier time of day, but it is the next day, so yes, 16 hours later00:17
ycombinator_haha, ok00:17
ycombinator_moving to next item in agenda :)00:17
*** Viswanath has joined #openstack-meeting-300:17
ycombinator_#topic wiki page updates00:18
*** openstack changes topic to "wiki page updates (Meeting topic: api wg)"00:18
ycombinator_#link https://wiki.openstack.org/wiki/API_Working_Group00:18
ycombinator_I'm not sure what there is to do on this one00:18
ycombinator_do either of you know?00:18
*** SumitNaiksatam has joined #openstack-meeting-300:18
miguelgrinbergmaybe review this? I don't know, looks pretty good to me00:19
sigmavirus24yeah it's much fuller than it used to be00:20
sigmavirus24Looks a lot better than it did pre-summit00:20
ycombinator_yeah, I don't have anything to add on this item00:20
*** Viswanath has quit IRC00:20
ycombinator_#topic APIImpact flag00:21
*** openstack changes topic to "APIImpact flag (Meeting topic: api wg)"00:21
ycombinator_#link https://review.openstack.org/#/q/status:open+AND+(message:ApiImpact+OR+message:APIImpact),n,z00:21
ycombinator_for these, maybe we can go through the -1 and -2 reviews?00:21
ycombinator_#link https://review.openstack.org/#/c/132342/00:22
sigmavirus24I think we can do that after the meeting00:22
*** banix has quit IRC00:22
sigmavirus24It looks like most of them are cyeoh and etoews adding requirements for APIImpact to projects00:22
*** SridharRamaswamy has quit IRC00:22
ycombinator_yeah, most of them appear to be just that00:23
miguelgrinbergI don't see much to comment on either00:24
ycombinator_okay... moving on then00:25
ycombinator_#topic review 201-header-and-body00:26
*** openstack changes topic to "review 201-header-and-body (Meeting topic: api wg)"00:26
sigmavirus24https://review.openstack.org/#/c/133087/00:26
ycombinator_#link https://review.openstack.org/#/c/133087/00:26
sigmavirus24So I agree with cyeoh's most recent feedback that async operations should be 202. 202 best fits that case00:27
miguelgrinbergI have provided as much justification I could find for not requiring a body (i.e making it a recommendation, but optional)00:27
sigmavirus24Otherwise, I agree with miguelgrinberg about representations being optional00:27
sigmavirus24If we can get etoews to address those concerns I think we'll have something that everyone but Sam will approve00:28
ycombinator_if the representation is optional, shouldn't the response code be 204, then?00:28
miguelgrinbergI'm also in agreement with cyeoh00:28
sigmavirus24ycombinator_: 204s shouldn't be used for creates semantically00:28
sigmavirus24There are APIs which also return a short representation of the resource instead of returning nothing00:28
ycombinator_right, I agree with 201 for synchronous create and 202 for asynch create00:28
sigmavirus24201s don't require a body, just a 0 Content-Length if there is no body00:29
ycombinator_but if we don't return any representation, are we required to use 204/00:29
sigmavirus24No00:29
miguelgrinbergI would say no to the 204, it's too odd00:29
sigmavirus24Just like right now when methods for a route aren't defined, we return a 404 instead of the proper 40500:29
miguelgrinbergI prefer a 201 with empty body00:29
sigmavirus24405 would be the canonical response to something like that (and something every framework gives us for free) but we don't do it00:29
ycombinator_ok, if 201 with empty body is acceptable by spec, that makes sense to me for synch creation00:30
sigmavirus24So I mean, we can define OS-REST but I'd really rather not have something that is our own standard *just because*00:30
sigmavirus24201 explicitly signals "created"00:30
sigmavirus24which is the information we want to know.00:30
miguelgrinbergright, 204 does not confirm creation00:30
sigmavirus24204 is typically tied to "no content" which is terribly ambiguous00:30
miguelgrinbergplus, I have never seen 204 tied to a location header00:31
*** reed has quit IRC00:31
sigmavirus24ditto00:31
miguelgrinbergI have seen 201 and 202 w/location header, that is pretty standard00:31
ycombinator_yeah, me too00:31
*** lhcheng has quit IRC00:31
ycombinator_but I've also never seen a 201/202 without a body00:31
ycombinator_all that said, I can't find anything in the HTTP spec that says a 201 must have a body00:32
*** lhcheng has joined #openstack-meeting-300:32
sigmavirus24You won't because it doesn't have to have a body00:32
sigmavirus24:)00:32
ycombinator_right, so I'm down with 201 for synch creation and 202 for asynch creation (with or without body)00:32
ycombinator_so what's the next step here? :)00:32
miguelgrinberglocation header mandatory or optional?00:33
miguelgrinbergif it is optional, then that means that it is somewhere in the body00:33
miguelgrinbergwhich can be confusing00:33
ycombinator_I'd say mandatory, even if the link is in the body00:33
ycombinator_rather, the link in the body is optional00:33
miguelgrinberg+100:33
sigmavirus24+100:33
ycombinator_but having the location header makes it uniform00:33
miguelgrinbergeven for the 20200:33
miguelgrinbergthough for a 202 it may not be a resource link00:34
miguelgrinbergit can be a get-status link for a resource that doesn't exist yet00:34
sigmavirus24mhm00:34
sigmavirus24+100:34
miguelgrinbergyou may not know the resource link00:34
ycombinator_+100:34
sigmavirus24so should someone take over this patchset and amend it with what's been discussed here?00:35
*** armax has joined #openstack-meeting-300:35
ycombinator_yes, I can do that00:35
ycombinator_to confirm, I captured two things:00:35
ycombinator_1. synchronous creation should respond with 201, asynchronous with 202; body is optional00:35
*** armax has quit IRC00:35
ycombinator_2. in either synchronous or asynchronous creation, there must be a location header00:35
ycombinator_correct?00:35
miguelgrinberglooks good to me00:36
sigmavirus24#action ycombinator_ will update https://review.openstack.org/#/c/133087/ with 1. synchronous creation should respond with 201, asynchronous with 202; body is optional and 2. in either synchronous or asynchronous creation, there must be a location header00:36
ycombinator_thanks @sigmavirus2400:36
sigmavirus24you're welcome I constructed it as you spoke :)00:36
ycombinator_moving to next item00:36
ycombinator_#topic reviews00:36
*** openstack changes topic to "reviews (Meeting topic: api wg)"00:36
ycombinator_#link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z00:36
*** lhcheng has quit IRC00:36
sigmavirus24So I'd like to discuss https://review.openstack.org/#/c/132248/ and https://review.openstack.org/#/c/131320/00:37
sigmavirus24The first we've just agreed against and we should probably point that out to Sam00:37
sigmavirus24The second is what my mini-rant was about above00:37
miguelgrinbergso cyeoh complains that it may be impractical to implement the 40500:38
miguelgrinbergI suggested he looks at my proposal for the heat API, which generates the 405s and the Allow header automatically00:38
sigmavirus24And since that seems like it might be desirable in other libraries, we should probably move it into oslo-incubator if we can get dhellmann's approval00:39
*** banix has joined #openstack-meeting-300:39
*** annegentle has joined #openstack-meeting-300:39
ycombinator_@sigmavirus24 do you want to take an action for commenting on the first one for Sam?00:39
sigmavirus24ycombinator_: certainly00:40
miguelgrinbergagreed00:40
ycombinator_#action sigmavirus24 will comment on https://review.openstack.org/#/c/132248/ re: no 204 for creation00:40
miguelgrinbergit should be part of the framework00:40
sigmavirus24If you're talking about Routes, I discussed this with Ben and he vehemently disagreees00:40
sigmavirus24Unless you want to bring it up again00:41
sigmavirus24It could also be a third party package that's maintained and not included in oslo at all00:41
sigmavirus24That may be harder to have added to global-requirements.txt though00:41
sigmavirus24Unless this review is approved00:41
miguelgrinbergI mean framework in a relaxed way, maybe something on top of the routes pkg00:41
*** etoews has joined #openstack-meeting-300:41
sigmavirus24Fair enough00:41
miguelgrinbergor we should just switch everything to Flask and be done with it ;-)00:42
sigmavirus24smh00:42
etoewshi00:43
ycombinator_hi :)00:43
sigmavirus24hey etoews00:43
sigmavirus24we started without you, hope you don't miind00:43
etoewsnot at all00:43
ycombinator_sigmavirus24, miguelgrinberg: so what's the next step on https://review.openstack.org/#/c/131320/?00:44
etoewsso sorry i'm late. i could've sworn it was 7 pm for me.00:44
annegentleyeah DST got a few of us :)00:44
miguelgrinbergI think we need to talk to cyeoh00:44
sigmavirus24ycombinator_: coming to a decision about whether we want to enforce the standard of every other API on OpenStack regardless of convenience00:44
ycombinator_after this one we can circle back to the first couple of items on the agenda00:44
*** SridharRamaswamy has joined #openstack-meeting-300:44
sigmavirus24ycombinator_: unless there are other reviews people would like to highlight/discuss00:45
etoewsyes00:45
ycombinator_right00:45
etoewshttps://review.openstack.org/#/c/133087/00:45
ycombinator_miguelgrinberg: do you want to take the action on initiating the conversation with cyeoh?00:45
miguelgrinbergyes, I can do that00:45
etoews#link https://review.openstack.org/#/c/133087/00:45
ycombinator_#action miguelgrinberg to start conversation with cyeoh re: https://review.openstack.org/#/c/131320/00:46
sigmavirus24etoews: thoughts?00:46
etoewsthat's the proposal i started at the summit with the entire group present.00:46
sigmavirus24Right00:46
etoewssadly i haven't even had a chance to really review the comments since i got back :(00:47
sigmavirus24etoews: it's okay :) we discussed it earlier00:47
*** yamahata has joined #openstack-meeting-300:47
sigmavirus24the arguments are as follows (for a tl;dr): 1. 201s body should be recommended but optional00:48
sigmavirus242. 201s should always have a Location header pointing to the created resource00:48
etoewsthat's reasonable.00:48
ycombinator_or a status resource, right sigmavirus24 ?00:48
sigmavirus243. 202s should be returned for asynchronous creation tasks and should include a Location header (which does not need to be the resource URL)00:48
ycombinator_nvm - 20100:49
ycombinator_continue00:49
sigmavirus24Even though a 201 may have no body, it's better (and more consistent) to return a 201 to signal successful creation than a 204 which has no intrinsic meaning of "yes we created that"00:49
sigmavirus24Basically cyeoh asked for the 202 specific information to be included. We all agree with them on that. Miguel is requesting that we not ever use 204 for POSTs whose representation is too large to reasonably returned in a 20100:50
etoewsone of the things we discussed at the summit was being opinionated and using strong language (like "must") in our proposals. if we get good counter arguments, we can adjust the language. makes for better history and stronger guidelines.00:51
miguelgrinbergI like the stronger language, but that may put some of the APIs at fault until the rev their specs to comply00:52
sigmavirus24I'm not sure I follow00:52
etoewsi'll read the eavesdrop and the review comments and update the proposal for 201-header-and-body00:52
ycombinator_thanks etoews00:53
etoewsmiguelgrinberg: so we don't want to use language that encompasses current practice. we want to use language that encompasses best/preferred/recommended practice, regardless of what the current apis do.00:53
miguelgrinbergfine with me00:54
miguelgrinbergjust pointing out that it may look confusing00:54
sigmavirus24etoews: that sounds excellent00:54
ycombinator_#action etoews to update proposal for 201 header and body in https://review.openstack.org/#/c/133087/00:55
ycombinator_any other reviews to go over?00:55
ycombinator_also, we have 5 minutes left technically00:55
etoewsthat's one of the things that came up in the design summit. what to do about "old" apis that don't follow the guidelines. i updated the deliverables and #5 reflects that. https://wiki.openstack.org/wiki/API_Working_Group00:56
etoews#topic additional meeting time00:57
etoewsso that review was accepted.00:57
sigmavirus24yep00:57
etoewspersonally (obviously?) that time works a bit better for me.00:58
etoewsi'll be switching to that one.00:58
etoews#topic wiki page updates00:59
etoewsi updated the wiki00:59
sigmavirus24the updates look awesome. thank you00:59
etoewsbased on feedback at the summit.00:59
etoewsplease to review :)00:59
etoewsi'll try to send out a summit summary sometime this week.00:59
etoewssummit summary sometime summit summary sometime summit summary sometime00:59
etoewsaaaaaaand time01:00
ycombinator_#endmeeting01:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"01:01
openstackMeeting ended Thu Nov 13 01:00:59 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)01:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2014/api_wg.2014-11-13-00.08.html01:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2014/api_wg.2014-11-13-00.08.txt01:01
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2014/api_wg.2014-11-13-00.08.log.html01:01
etoewsthanks everyone. sorry again. burned by daylight savings time i think.01:01
ycombinator_thanks everyone01:01
miguelgrinbergthank you, see you next time01:01
*** s3wong has quit IRC01:01
*** otherwiseguy has joined #openstack-meeting-301:03
*** gholler_ has joined #openstack-meeting-301:05
*** SumitNaiksatam has quit IRC01:05
*** gholler has quit IRC01:08
*** otherwiseguy has quit IRC01:14
*** shakamunyi has quit IRC01:14
*** gholler__ has joined #openstack-meeting-301:14
*** hinnant has quit IRC01:15
*** otherwiseguy has joined #openstack-meeting-301:16
*** gholler_ has quit IRC01:17
*** banix has quit IRC01:17
*** mwang2_ has quit IRC01:21
*** dboik_ has joined #openstack-meeting-301:26
*** armax has joined #openstack-meeting-301:29
*** armax has quit IRC01:31
*** armax has joined #openstack-meeting-301:31
*** bpokorny_ has joined #openstack-meeting-301:35
*** yamamoto_ has quit IRC01:35
*** carl_baldwin has quit IRC01:35
*** bpokorny has quit IRC01:38
*** rrrobbb has left #openstack-meeting-301:49
*** sigmavirus24 is now known as sigmavirus24_awa01:51
*** jacalcat has joined #openstack-meeting-301:51
*** ChuckC has quit IRC01:53
*** dconde has joined #openstack-meeting-301:54
*** bpokorny has joined #openstack-meeting-301:55
*** jacalcat has left #openstack-meeting-301:57
*** bpokorny_ has quit IRC01:58
*** ycombinator_ has quit IRC02:00
*** dconde has quit IRC02:02
*** yamamoto_ has joined #openstack-meeting-302:04
*** dconde has joined #openstack-meeting-302:04
*** ChuckC has joined #openstack-meeting-302:04
*** david-lyle is now known as david-lyle_afk02:08
*** gholler__ has quit IRC02:08
*** bpokorny has quit IRC02:08
*** wuhg has joined #openstack-meeting-302:09
*** alexsyip has quit IRC02:13
*** otherwiseguy has quit IRC02:15
*** jrist has quit IRC02:24
*** otherwiseguy has joined #openstack-meeting-302:28
*** etoews has quit IRC02:30
*** sankarshan is now known as sankarshan_away02:30
*** etoews has joined #openstack-meeting-302:37
*** jrist has joined #openstack-meeting-302:39
*** jrist has quit IRC02:41
*** etoews has quit IRC02:43
*** jrist has joined #openstack-meeting-302:47
*** yamahata has quit IRC02:47
*** yamahata has joined #openstack-meeting-302:48
*** jrist has quit IRC02:53
*** SridharRamaswamy has quit IRC02:53
*** salv-orlando has quit IRC02:56
*** vkmc has quit IRC03:04
*** jacalcat has joined #openstack-meeting-303:07
*** jacalcat has left #openstack-meeting-303:08
*** bpokorny has joined #openstack-meeting-303:16
*** Longgeek has joined #openstack-meeting-303:19
*** ivar-laz_ has joined #openstack-meeting-303:20
*** ivar-lazzaro has quit IRC03:23
*** ivar-laz_ has quit IRC03:24
*** Longgeek has quit IRC03:26
*** SumitNaiksatam has joined #openstack-meeting-303:26
*** carl_baldwin has joined #openstack-meeting-303:29
*** dboik_ has quit IRC03:34
*** SumitNaiksatam has quit IRC03:34
*** dboik has joined #openstack-meeting-303:34
*** etoews has joined #openstack-meeting-303:39
*** sankarshan_away is now known as sankarshan03:45
*** etoews has quit IRC03:49
*** carl_baldwin has quit IRC03:54
*** marun has joined #openstack-meeting-303:55
*** carl_baldwin has joined #openstack-meeting-304:00
*** ctracey has quit IRC04:05
*** ctracey has joined #openstack-meeting-304:06
*** Adri2000_ has joined #openstack-meeting-304:08
*** sweston_ has joined #openstack-meeting-304:08
*** s1rp_ has joined #openstack-meeting-304:10
*** mordred_ has joined #openstack-meeting-304:12
*** dboik has quit IRC04:12
*** Adri2000 has quit IRC04:12
*** vishy has quit IRC04:12
*** sweston has quit IRC04:12
*** cyeoh has quit IRC04:12
*** s1rp has quit IRC04:12
*** redrobot has quit IRC04:12
*** mordred has quit IRC04:12
*** mordred_ is now known as mordred04:12
*** sweston_ is now known as sweston04:13
*** redrobot has joined #openstack-meeting-304:14
*** redrobot is now known as Guest1762704:14
*** cyeoh has joined #openstack-meeting-304:14
*** vishy has joined #openstack-meeting-304:17
*** badveli has quit IRC04:27
*** jacalcat has joined #openstack-meeting-304:48
*** jacalcat has left #openstack-meeting-304:48
*** jrist has joined #openstack-meeting-304:54
*** jrist has quit IRC05:00
*** otherwiseguy has quit IRC05:03
*** terryw has joined #openstack-meeting-305:03
*** Longgeek has joined #openstack-meeting-305:10
*** jrist has joined #openstack-meeting-305:11
*** marun has quit IRC05:14
*** Longgeek has quit IRC05:15
*** bpokorny has quit IRC05:19
*** etoews has joined #openstack-meeting-305:46
*** Longgeek has joined #openstack-meeting-305:46
*** gcb has joined #openstack-meeting-305:47
*** etoews has quit IRC05:50
*** carl_baldwin has quit IRC06:08
*** k4n0 has joined #openstack-meeting-306:09
*** nelsnelson has quit IRC06:28
*** Longgeek has quit IRC06:31
*** Longgeek has joined #openstack-meeting-306:33
*** armax has quit IRC06:36
*** terryw has quit IRC06:44
*** ChuckC has quit IRC06:45
*** etoews has joined #openstack-meeting-306:47
*** reed has joined #openstack-meeting-306:51
*** etoews has quit IRC06:51
*** etoews has joined #openstack-meeting-307:13
*** etoews has quit IRC07:18
*** ChuckC has joined #openstack-meeting-307:18
*** mrunge has joined #openstack-meeting-307:19
*** evgenyf has joined #openstack-meeting-307:37
*** yamamoto_ has quit IRC07:42
*** salv-orlando has joined #openstack-meeting-307:51
*** safchain has joined #openstack-meeting-308:04
*** matrohon has joined #openstack-meeting-308:10
*** sergef has joined #openstack-meeting-308:12
*** etoews has joined #openstack-meeting-308:14
*** etoews has quit IRC08:18
*** iovadia has joined #openstack-meeting-308:20
*** yamahata has quit IRC08:22
*** sankarshan is now known as sankarshan_away08:36
*** MaxV has joined #openstack-meeting-308:41
*** jcoufal has joined #openstack-meeting-308:46
*** zz_ttrifonov is now known as ttrifonov08:46
*** ttrifonov is now known as zz_ttrifonov08:47
*** pkarikh has joined #openstack-meeting-308:47
*** zz_ttrifonov is now known as ttrifonov08:48
*** salv-orlando has quit IRC09:28
*** igordcard has joined #openstack-meeting-309:29
*** tteggel has quit IRC09:35
*** tteggel has joined #openstack-meeting-309:35
*** tteggel has quit IRC09:39
*** tteggel has joined #openstack-meeting-309:40
*** dmahony has quit IRC09:45
*** amotoki has quit IRC09:46
*** reed has quit IRC09:50
*** reed has joined #openstack-meeting-310:02
*** etoews has joined #openstack-meeting-310:15
*** Longgeek has quit IRC10:15
*** Longgeek has joined #openstack-meeting-310:16
*** Longgeek_ has joined #openstack-meeting-310:17
*** Longgeek has quit IRC10:20
*** etoews has quit IRC10:20
*** gcb has quit IRC10:35
*** zhipeng has quit IRC10:37
*** gcb has joined #openstack-meeting-310:46
*** mwagner_lap has quit IRC10:51
*** yamahata has joined #openstack-meeting-311:06
*** lhcheng has joined #openstack-meeting-311:41
*** lhcheng has quit IRC11:42
*** lhcheng has joined #openstack-meeting-311:42
*** salv-orlando has joined #openstack-meeting-311:58
*** gcb has quit IRC12:06
*** vkmc has joined #openstack-meeting-312:10
*** vkmc has quit IRC12:10
*** vkmc has joined #openstack-meeting-312:10
*** etoews has joined #openstack-meeting-312:17
*** etoews has quit IRC12:21
*** gcb has joined #openstack-meeting-312:22
*** mwagner_lap has joined #openstack-meeting-312:34
*** yamahata has quit IRC12:37
*** yamahata has joined #openstack-meeting-312:37
*** salv-orlando has quit IRC12:38
*** salv-orlando has joined #openstack-meeting-312:49
*** thomasem has joined #openstack-meeting-312:53
*** thomasem has quit IRC12:56
*** thomasem has joined #openstack-meeting-312:58
*** salv-orlando has quit IRC12:59
*** sankarshan_away is now known as sankarshan13:02
*** Longgeek_ has quit IRC13:03
*** matrohon has quit IRC13:05
*** dboik has joined #openstack-meeting-313:09
*** Longgeek has joined #openstack-meeting-313:10
*** dboik_ has joined #openstack-meeting-313:10
*** dboik has quit IRC13:14
*** jacalcat has joined #openstack-meeting-313:18
*** jacalcat has left #openstack-meeting-313:18
*** gaitan has quit IRC13:28
*** gaitan has joined #openstack-meeting-313:28
*** dboik_ has quit IRC13:30
*** alexpilotti has joined #openstack-meeting-313:34
*** mattfarina has joined #openstack-meeting-313:40
*** sigmavirus24_awa is now known as sigmavirus2413:43
*** lhcheng_ has joined #openstack-meeting-313:44
*** lhcheng has quit IRC13:47
*** dboik has joined #openstack-meeting-313:50
*** dboik has joined #openstack-meeting-313:51
*** gaitan has quit IRC14:00
*** gholler has joined #openstack-meeting-314:05
*** Eran has joined #openstack-meeting-314:08
*** Eran has quit IRC14:09
*** k4n0 has quit IRC14:10
*** gaitan has joined #openstack-meeting-314:15
*** yamamoto has joined #openstack-meeting-314:15
*** carl_baldwin has joined #openstack-meeting-314:19
*** carl_baldwin has quit IRC14:26
*** peristeri has joined #openstack-meeting-314:30
*** baoli has joined #openstack-meeting-314:46
*** otherwiseguy has joined #openstack-meeting-314:46
*** dboik_ has joined #openstack-meeting-314:52
*** dboik_ has quit IRC14:52
*** dboik has quit IRC14:52
*** dboik has joined #openstack-meeting-314:53
*** johnbelamaric has joined #openstack-meeting-314:54
*** rohit404 has joined #openstack-meeting-314:57
*** thangp has joined #openstack-meeting-314:59
*** etoews has joined #openstack-meeting-315:01
*** carl_baldwin has joined #openstack-meeting-315:02
carl_baldwinhi15:02
johnbelamarichi15:02
yamamotohi15:02
rohit404hi15:02
carl_baldwinSorry to be a little late.  Wifi was being a little picky about connecting this morning.15:02
carl_baldwin#startmeeting neutron_l315:02
openstackMeeting started Thu Nov 13 15:02:57 2014 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:03
openstackThe meeting name has been set to 'neutron_l3'15:03
carl_baldwin#topic Announcements15:03
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:03
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:03
carl_baldwinI did not take the time yesterday to update the agenda.  I think it is probably a little bit out of date.15:03
*** pc_m has joined #openstack-meeting-315:04
carl_baldwinThe mid-cycle has been announced but I think the date is still in question.15:04
carl_baldwin#link http://lists.openstack.org/pipermail/openstack-dev/2014-November/050128.html15:04
*** markmcclain has joined #openstack-meeting-315:05
carl_baldwinHere is the wiki:  https://wiki.openstack.org/wiki/Sprints/NeutronKiloSprint15:05
*** otherwiseguy has quit IRC15:05
*** devvesa has joined #openstack-meeting-315:05
carl_baldwinI plan to be there for either week.15:05
*** markmcclain has quit IRC15:05
*** zhipeng has joined #openstack-meeting-315:05
carl_baldwin#link https://wiki.openstack.org/wiki/Sprints/NeutronKiloSprint15:05
carl_baldwinSummit was great.15:06
carl_baldwinAny other announcements?15:06
yamamotonothing from me15:06
carl_baldwinOkay.15:07
*** markmcclain has joined #openstack-meeting-315:07
carl_baldwinI guess I’ll just wing it on the agenda.  I’ll take some time today to freshen up the agenda on the wiki.15:07
carl_baldwin#topic l3-high-availability15:07
*** openstack changes topic to "l3-high-availability (Meeting topic: neutron_l3)"15:07
carl_baldwinsafchain: amuller:  Anything new here?15:07
*** nelsnelson has joined #openstack-meeting-315:08
carl_baldwin#topic bgp-dynamic-routing15:09
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:09
carl_baldwindevvesa: ping15:09
devvesahi15:09
carl_baldwinI talked to a lot of people at the summit who are interested in this.15:09
devvesado they use case (or idea) fit with current spec?15:10
carl_baldwinMany of them, yes.  This is outside of the BGPVPN crowd.15:10
devvesayes, it seems so. Every time I'm more conviced that we can find very few points in common with them15:11
carl_baldwinThere is some interest for it with routing to IPv6 networks.15:11
*** thangp has quit IRC15:11
carl_baldwinThe use case is very specialized.15:11
*** armax has joined #openstack-meeting-315:11
carl_baldwinI see that the spec has a few minor comments.  Will you have a chance to take a look at it?15:12
devvesaMathieu Rohon found some nits in current spec. I will push a new patch15:12
devvesayes, currently I'm caught in Midonet's CI because of our open source stuff15:13
carl_baldwindevvesa: Great.  I’ll watch for it.  I think the idea is in pretty good shape.  I’ll reach out to the drivers team about merging it for Kilo.15:13
devvesaIf I find a free hour I'll review15:13
devvesathis week15:13
devvesauhm... maybe beginning of next :)15:13
*** Eran has joined #openstack-meeting-315:13
carl_baldwindevvesa: I hope you can find that hour.15:13
devvesa(just realised we live on Thursday)15:13
*** thangp has joined #openstack-meeting-315:13
carl_baldwinThese weeks do go by quickly.15:14
carl_baldwin#action devvesa to update the bgp spec15:14
devvesawhat we need after your approval15:14
*** sergef has quit IRC15:14
devvesa?15:14
carl_baldwindevvesa: We need the Neutron drivers team to approve.15:14
carl_baldwin#action carl_baldwin will reach out to Neutron drivers team.15:14
devvesacool15:15
carl_baldwindevvesa: anything else?15:15
devvesanothing else. thanks15:15
carl_baldwindevvesa: Thank you.  It was good to see you at the summit.15:15
carl_baldwin#topic L3 Agent Restructuring15:15
*** openstack changes topic to "L3 Agent Restructuring (Meeting topic: neutron_l3)"15:15
carl_baldwinI updated my spec and got a lot of feedback yesterday.  I’m partially through addressing that feedback.15:16
carl_baldwin#link https://review.openstack.org/#/c/131535/15:16
* pc_m lots of good stuff in there15:16
carl_baldwinI haven’t heard any major deal-breaking feedback.  But, there are some sections that need some fleshing out.  I will make it a priority today.15:17
carl_baldwinI wanted to ask if anyone read the comments around L132?15:17
carl_baldwin#link https://review.openstack.org/#/c/131535/2/specs/kilo/restructure-l3-agent.rst15:17
pc_myes15:18
carl_baldwinThe comments are around inheritence vs a driver approach.  I realized that my ideas there were not baked enough to have a clear plan.15:18
carl_baldwinThanks for all of your comments, btw.15:18
carl_baldwinI’m once again entertaining the idea of using inheritence  for types of routers like DVR, HA, Legacy.15:19
carl_baldwinAny more thoughts?15:20
pc_mGut feel is that services seem like capabilities added (composition) for a router.15:20
pc_mRouter has a VPN capability, router has a FW capability.15:21
carl_baldwinpc_m: Agreed.  I think my comment reflects that.  I was hesitent to use any kind of inheritence because I didn’t want to end up with a VPNRouter or a FWaaSRouter.15:21
pc_m:)15:21
carl_baldwinI’m entertaining the idea of using inheritence to create a DVRRouter, HARouter, etc.15:21
*** sergef has joined #openstack-meeting-315:21
ChuckCmaybe armando should also take a look?15:21
ChuckCoh, well, salvatore is there15:22
carl_baldwinYes, I would welcome armax’s input here.15:22
carl_baldwinIt is a bit early for him though since DST has ended for the year.  :)15:22
armax:)15:22
* armax catching up15:23
devvesaso a router that uses DVR and HA is going to be a DVRHARouter?15:23
carl_baldwinarmax: no worries.15:23
carl_baldwindevvesa: I think that would follow, yes.15:23
* carl_baldwin just realized that DVRRouter is redundant.15:24
devvesai have to read the spec. but what it does not fit in my head is the fact that a DVR router depends on l3_agent configuration15:24
carl_baldwinIf you have some thoughts, feel free to chime in on the review.  I’m not sure this needs to be completely spelled out before we can proceed but I’d like to have a good idea of the direction it will take.15:25
armaxcarl_baldwin: inheritance vs composition needs to be looked at especially when considering how much code can be reause15:25
devvesawhereas HA it depends on user call15:25
*** marun has joined #openstack-meeting-315:25
devvesa(just thinking loud)15:25
*** johnbelamaric has quit IRC15:27
carl_baldwindevvesa: That is true.  DVR does have the extra agent configuration piece.  We might need an extra SNAT class for the centralized part of the router.15:27
devvesai think it will be easy to handle, but keep in mind that opens the door to complex inheritance if there are more kinds of routers in a future15:28
carl_baldwinHowever, igoring the agent configuration part, a DVR can be created much like an HA router.15:28
*** johnbelamaric has joined #openstack-meeting-315:28
carl_baldwindevvesa: That is a point that I continue to consider.  Thanks.15:28
*** amuller has joined #openstack-meeting-315:28
carl_baldwinamuller: hi15:28
amullercarl_baldwin: Hey sorry I was interviewing someone15:29
carl_baldwinamuller: Looking for a new job?15:29
* carl_baldwin is joking15:29
amullerThe guy I was interviewing is =D15:29
amullerAre you? :)15:29
carl_baldwinamuller: We were just wrapping up the discussion on inheritence from the L3 agent spec.15:30
amullerI'll read the meeting notes later15:30
carl_baldwinI hope to hear your thoughts but I’ll give you a chance to catch up.15:30
amullerinheritence vs drivers for different router types? Let's decide that during implementation phase, imo15:31
carl_baldwinI think we’ll take the discussion to the review.15:31
carl_baldwinamuller: We may need the flexibility to do just that.15:31
carl_baldwin#topic neutron-ipam15:32
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:32
carl_baldwinWe had a good discussion about IPAM at the design summit.15:32
johnbelamarici replied to some of your review comments just before this meeting, not sure you would have had a chance to take a look15:32
carl_baldwinjohnbelamaric: I was just noticing your comments on the review.15:33
carl_baldwinhttps://review.openstack.org/#/c/97967/35/specs/kilo/neutron-ipam.rst15:33
*** otherwiseguy has joined #openstack-meeting-315:33
johnbelamaricagree that we need to cut the originally proposed interface way back15:33
carl_baldwin#link https://etherpad.openstack.org/p/neutron-ipam15:33
carl_baldwinjohnbelamaric: I think the nature of the interface needs to change too.  I think I get why the interface was done the way it was but I don’t think that is the right permanent solution.15:34
johnbelamaricagreed15:34
carl_baldwinjohnbelamaric: I’d like the interface to be intuitive to use and review.15:34
johnbelamaric"minimal surface area" is the way Soheil put it yesterday :)15:34
carl_baldwinjohnbelamaric: Have you had a chance to look at my straw man?  I had limited time to put it together yesterday so I’m sure it is missing some things.15:35
carl_baldwinBut, I think it should be enough to illustrate what I had in my mind.15:36
carl_baldwin#link http://paste.openstack.org/show/132513/15:36
johnbelamaricyes, i did. it looks good for the most part. i think there are a few things - 1) we should let the IPAM system know about the scopes15:36
johnbelamaric2) i think we may want to pass some things like "port object" into the IPAM calls. this enables the IPAM system to make allocation decisions based upon meta-data about the port, vm, tenant, etc.15:37
carl_baldwinjohnbelamaric: It does know.  L64.  My thought was that the driver would be instantiated once for each scope.15:37
johnbelamarici will do more of a thorough review today15:37
johnbelamaricyes15:37
carl_baldwinBy their definition, scopes are orthogonal.  So, creating an instance per scope makes sense to me.  That way, the rest of the method calls are not cluttered with this detail.15:38
johnbelamaricah, right. driver per scope. hmm. so, when the driver is instantiated it will need some configuration data that goes with it, potentially15:38
carl_baldwinaddress_type is similar.  They are orthogonal.  Hence, the address_type argument no the same line.15:38
johnbelamaricyes, that makes sense. so, different scopes managed by different drivers or instances thereof15:38
johnbelamaricnot sure why address type needs a separate driver instance15:39
*** armax has quit IRC15:39
johnbelamaricbut i don't see a problem with it15:39
carl_baldwinjohnbelamaric: Yes, I assumed that the driver can define its own configuration.15:39
*** mwang2 has joined #openstack-meeting-315:39
carl_baldwinjohnbelamaric: address_types are also orthogonal.  Cluttering the rest of the interface with address_type parameters would less clean.15:40
carl_baldwinjohnbelamaric: I’m writing a new blueprint to follow this blueprint that will add a REST API and new data model so that the reference implementation can take advantage of the scope idea.15:40
johnbelamaricso, get_driver is essentially a factory method, right? it doesn't currently allow input of any opaque (ie, possibly driver-specific) config data15:41
carl_baldwinI’ll add you folks as reviewers when I have posted the spec.15:41
johnbelamaricok, great. thanks15:41
johnbelamarici will review your proposal closer today15:41
carl_baldwinjohnbelamaric: Right.  I imagine configuration will be done through config files.  But, there may be some room to enhance this interface.15:41
johnbelamarici think config files is not sufficient, because scopes may be dynamically created and we wouldn't want to have to add config file changes at that time15:42
carl_baldwinjohnbelamaric: You may a point there.  Let’s continue the discussion about this.15:43
johnbelamaricok15:43
*** mwang2_ has joined #openstack-meeting-315:43
carl_baldwinMaybe I should post the base class as a review so that we can annotate it with discussion.15:43
*** hinnant has joined #openstack-meeting-315:44
johnbelamaricyes, i think that would be helpful15:44
carl_baldwinI was being a bit hasty yesterday when I threw it in pastebin.15:44
carl_baldwin#action carl_baldwin will post a review with http://paste.openstack.org/show/132513/15:44
johnbelamaricok - quick process question if you don't mind - is it possible for me to modify Soheil's change by uploading a patch that, say, incorporated the changes from this discussion? I am not sure he'll have time this week to update it himself15:44
johnbelamaricdon't need to know how in this meeting - but want to know it's possible before I make the effort - being new to Gerritt, etc.15:45
carl_baldwinjohnbelamaric: Yes, that is possible.  You will find that you can’t do a few things like mark it as a WIP but I could do that for you if you want.15:45
johnbelamaricgreat, thanks carl15:45
*** mwang2 has quit IRC15:46
carl_baldwinjohnbelamaric: Feel free to ping me for help on that if you need.  The process is simple though.  Just git review -d NNNNN the review.  Amend it and post it like normal.15:46
johnbelamaricok, good15:46
carl_baldwinjohnbelamaric: Thanks.15:46
carl_baldwinAnything else?15:46
johnbelamaricnot right now on IPAM for me - moving the discussion to a review makes sense15:47
carl_baldwinjohnbelamaric: Great.  Thanks for your work here.  I’m exciting to get this done.15:47
carl_baldwin#topic l3 plugin for routervm/modular l3 router plugin15:47
*** openstack changes topic to "l3 plugin for routervm/modular l3 router plugin (Meeting topic: neutron_l3)"15:47
carl_baldwinyamahata: ping15:47
yamahatacarl_baldwin: pong15:47
yamahataI'm planning to respin the spec this week. i.e. tomorrow15:48
yamahataAnd upload WIP patch15:48
carl_baldwinyamahata: great.15:48
yamahataWIP = no test yet15:48
carl_baldwinDo you have any discussion points to bring up?15:49
*** gaitan has quit IRC15:49
*** asahlin has joined #openstack-meeting-315:49
yamahatanothing at this point.15:49
pc_myamahata: Link to spec, please?15:49
yamahatahttps://review.openstack.org/#/c/105078/15:50
pc_mThanks!15:50
carl_baldwinyamahata: Could you “Set the URL for this specification” in launchpad so that the specs are a bit easier to find from the blueprints?15:50
*** armax has joined #openstack-meeting-315:51
yamahatacarl_baldwin: done15:51
carl_baldwinyamahata: Thank you.  I have subscribed to both specs and will watch them.15:52
carl_baldwin#topic Open Discussion15:52
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:52
*** gaitan has joined #openstack-meeting-315:53
carl_baldwinIf there is nothing else, we’ll close the meeting for today.  Thanks everyone for your work.15:54
carl_baldwinI hope that some of you can make it to the mid15:54
rossella_scarl_baldwin: regarding the l2 agent improvements...who's gonna coordinate that?15:54
carl_baldwin-cycle meetup.15:54
carl_baldwinrossella_s: That is a good question.  It was not on the top of my mind.15:55
rossella_sI imagine a design spec should be proposed, something similar to what you did for the l3 agent15:56
carl_baldwinrossella_s: I guess we should get with armax and discuss that.  I’m trying to find the etherpad which I had up in a tab.15:56
rossella_shttps://etherpad.openstack.org/p/kilo-neutron-agents-technical-debt15:57
rossella_sthis one?15:57
rossella_s#link https://etherpad.openstack.org/p/kilo-neutron-agents-technical-debt15:57
carl_baldwinrossella_s: You beat me, yes that one.15:57
carl_baldwinrossella_s: Your name is the first one I see on the etherpad.  ;)15:58
*** mrsmith has joined #openstack-meeting-315:58
rossella_s:D15:58
carl_baldwinmarios, Kevin, Manish, Terry, Eugene, Armando, Simeon are the others.15:59
rossella_syes, maybe we should discuss with those people and spit taks15:59
carl_baldwinrossella_s: This meeting is about out of time.  We could discuss more in the neutron room.  Do you have suggestions for how to proceed?15:59
rossella_ss/tasks/tasks15:59
*** gaitan has quit IRC15:59
rossella_sit's ok, let's move to the neutron room15:59
carl_baldwin#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu Nov 13 16:00:00 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-11-13-15.02.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-11-13-15.02.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-11-13-15.02.log.html16:00
yamamotobye16:00
*** pc_m has left #openstack-meeting-316:00
*** MaxV has quit IRC16:00
*** Eran has left #openstack-meeting-316:01
*** dboik has left #openstack-meeting-316:01
*** johnbelamaric has quit IRC16:02
*** seizadi has joined #openstack-meeting-316:02
*** MaxV has joined #openstack-meeting-316:03
*** etoews has quit IRC16:04
*** matrohon has joined #openstack-meeting-316:05
*** iovadia has quit IRC16:08
*** jschwarz has joined #openstack-meeting-316:08
*** etoews has joined #openstack-meeting-316:08
*** rohit404 has left #openstack-meeting-316:09
*** dboik has joined #openstack-meeting-316:10
*** gaitan has joined #openstack-meeting-316:12
*** jschwarz has quit IRC16:12
*** kashyap has quit IRC16:13
*** bpokorny has joined #openstack-meeting-316:14
*** kashyap_afk has joined #openstack-meeting-316:18
*** kashyap_afk is now known as kashyap16:19
*** amuller has quit IRC16:19
*** yamahata has quit IRC16:20
*** ycombinator_ has joined #openstack-meeting-316:25
*** Longgeek has quit IRC16:28
*** markmcclain has quit IRC16:30
*** thatsdone has joined #openstack-meeting-316:31
*** salv-orlando has joined #openstack-meeting-316:32
*** Guest17627 is now known as redrobot16:34
*** salv-orlando has quit IRC16:38
*** mwagner_lap has quit IRC16:42
*** bpokorny_ has joined #openstack-meeting-316:46
*** evgenyf has quit IRC16:46
*** armax has quit IRC16:46
*** otherwiseguy has quit IRC16:48
*** bpokorny has quit IRC16:49
*** MaxV has quit IRC16:50
*** otherwiseguy has joined #openstack-meeting-316:55
*** david-lyle_afk is now known as david-lyle16:58
*** thatsdone has quit IRC16:58
*** mrunge has quit IRC16:59
*** thatsdone has joined #openstack-meeting-316:59
*** salv-orlando has joined #openstack-meeting-317:00
*** amuller has joined #openstack-meeting-317:02
*** salv-orlando has quit IRC17:04
*** etoews has quit IRC17:13
*** dconde has joined #openstack-meeting-317:15
*** kashyap_afk has joined #openstack-meeting-317:17
*** safchain has quit IRC17:17
*** seizadi has quit IRC17:18
*** mtreinish has quit IRC17:19
*** dboik has quit IRC17:19
*** bpokorny has joined #openstack-meeting-317:20
*** kashyap has quit IRC17:20
*** bpokorny_ has quit IRC17:23
*** alexsyip has joined #openstack-meeting-317:26
*** baoli has quit IRC17:27
*** markmcclain has joined #openstack-meeting-317:28
*** markmcclain1 has joined #openstack-meeting-317:30
*** baoli has joined #openstack-meeting-317:32
*** markmcclain has quit IRC17:32
*** ycombinator_ has quit IRC17:37
*** kashyap_afk is now known as kashyap17:38
*** bpokorny has quit IRC17:40
*** bpokorny has joined #openstack-meeting-317:41
*** thatsdone has quit IRC17:41
*** ycombinator_ has joined #openstack-meeting-317:44
*** matrohon has quit IRC17:51
*** ivar-lazzaro has joined #openstack-meeting-317:51
*** ycombinator_ has quit IRC17:51
*** ivar-lazzaro has quit IRC17:52
*** stevelle has left #openstack-meeting-317:52
*** ivar-lazzaro has joined #openstack-meeting-317:53
*** SumitNaiksatam has joined #openstack-meeting-317:54
*** carl_baldwin has quit IRC17:54
SumitNaiksatamivar-lazzaro: hi18:00
*** s3wong has joined #openstack-meeting-318:00
SumitNaiksatams3wong: hi18:00
ivar-lazzaroSumitNaiksatam: hey there18:00
*** amuller has left #openstack-meeting-318:00
*** banix has joined #openstack-meeting-318:01
SumitNaiksatami think the time change might have been confusing for some18:01
s3wongSumitNaiksatam: hello --- almost forgot about standard time vs daylight saving18:01
SumitNaiksatambanix: hi, warm welcome back!18:01
banixhi SumitNaiksatam18:01
SumitNaiksatams3wong: yeah, i should have sent a note out earlier!18:01
*** RG has joined #openstack-meeting-318:01
s3wongbanix: welcome back!!! (and thanks for the +2 on my spec :-)  )18:01
banixhi s3wong all18:01
SumitNaiksatamok lets get started18:01
banixgood to be back thanks18:01
igordcardHello all18:02
SumitNaiksatamigordcard: welcome to the GBP IRC!18:02
SumitNaiksatam#startmeeting networking_policy18:02
openstackMeeting started Thu Nov 13 18:02: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:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: networking_policy)"18:02
*** rharwood has quit IRC18:02
*** nbouthors has joined #openstack-meeting-318:02
openstackThe meeting name has been set to 'networking_policy'18:02
SumitNaiksatam#info meeting agenda https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy#Nov_13th.2C_201418:03
SumitNaiksatam#topic Paris summit follow up18:03
*** openstack changes topic to "Paris summit follow up (Meeting topic: networking_policy)"18:03
*** wuhg has quit IRC18:03
SumitNaiksatamI think the summit was pretty exciting from a GBP perspective18:04
SumitNaiksatamthanks to everyone for contributing and participating18:04
*** Youcef has joined #openstack-meeting-318:04
SumitNaiksatam#info GBP presentation at conference: #link https://www.openstack.org/summit/openstack-paris-summit-2014/session-videos/presentation/group-based-policy-extension-for-networking18:04
SumitNaiksatam#info GBP design session etherpad: #link https://etherpad.openstack.org/p/kilo-gbp-design-summit-topics18:05
SumitNaiksatamYoucef: welcome! ;-)18:05
*** rkukura has joined #openstack-meeting-318:05
SumitNaiksatamrkukura: thanks for joining18:05
rkukurahi - sorry I’m late18:05
rkukuracalendar didn’t stick with UTC18:05
SumitNaiksatamany thoughts, feedback from the summit that we need to discuss up front?18:06
SumitNaiksatamrkukura: yeah, i think most people have the issue, i should have sent a note out earlier18:06
SumitNaiksatamso any feedback from the summit, that we want to discuss?18:06
SumitNaiksatam(we will get into specific technical items next, just checking for any general comments)18:07
SumitNaiksatamokay, seems like people are still catching up ;-)18:08
SumitNaiksatam#topic GBP Juno milestones18:08
*** openstack changes topic to "GBP Juno milestones (Meeting topic: networking_policy)"18:08
*** Kanzhe has joined #openstack-meeting-318:08
SumitNaiksatamduring the breakout session on thursday it was proposed that we have the following immediate milestones18:08
s3wongwell, even Kanzhe decides to join :-)18:08
Kanzhehi all.18:08
SumitNaiksatamoh yeah, we volunteered Kanzhe for a work item18:09
SumitNaiksatami bet he has an update! ;-P18:09
SumitNaiksatamKanzhe: good to see you back18:09
*** pballand has joined #openstack-meeting-318:09
SumitNaiksatamso on the milestones18:09
Kanzhethanks.18:09
SumitNaiksatamprior to the summit, we wrapped on juno-gbp-2 milestone18:10
SumitNaiksatamthe proposal is to do juno-gbp-3 on nov 28th, and release on dev 19th18:10
*** hemanthravi has joined #openstack-meeting-318:10
*** bpokorny_ has joined #openstack-meeting-318:11
SumitNaiksatamany issues with the above time lines (we will discuss next what we are targeting for those milestones)18:11
ivar-lazzaroSumitNaiksatam: depends on the items :)18:12
SumitNaiksatamivar-lazzaro: yes, okay so we will defer the questions18:12
SumitNaiksatam#topic Pending work items18:12
*** openstack changes topic to "Pending work items (Meeting topic: networking_policy)"18:12
*** KrishnaK_ has joined #openstack-meeting-318:13
*** armax has joined #openstack-meeting-318:13
SumitNaiksatamso based on the discussions and feedback during the summit, we will have to push some more essential features for juno18:13
SumitNaiksatamlet me quickly try and run through those18:13
SumitNaiksatamfeel free to interject at any time18:13
*** bpokorny has quit IRC18:14
SumitNaiksatamfirst thing we want to target is the resources’ renaming18:14
SumitNaiksatamso i posted a patch for that: #link https://review.openstack.org/#/c/13394918:14
SumitNaiksatamivar-lazzaro: will need your help on a few UTs that are failing18:14
ivar-lazzaroSumitNaiksatam: thanks for taking care of this!18:15
SumitNaiksatamivar-lazzaro: np18:15
SumitNaiksatamwe also need to refactor the client code for this18:15
SumitNaiksatami will post the patch later today (unless someone else wants to pick this up)18:15
ivar-lazzaroSumitNaiksatam: at a first glance, It seems a problem related to the fact that APIC driver uses an external library for getting the work done18:15
SumitNaiksatamivar-lazzaro: ok18:15
ivar-lazzaroSumitNaiksatam: and renaming also those calls is breaking things :)18:15
SumitNaiksatamivar-lazzaro: ah ok, i tried to do it in a way that the calls to the external libraries were not broken, but i might messed it up! :-(18:16
*** lpetrut has joined #openstack-meeting-318:16
*** sigmavirus24 is now known as sigmavirus24_awa18:16
ivar-lazzaroSumitNaiksatam: np, I'll try to fix it later today18:17
SumitNaiksatamivar-lazzaro has a spec for shared resources #link https://review.openstack.org/#/c/133603/18:17
*** sigmavirus24_awa is now known as sigmavirus2418:17
SumitNaiksatamthis helps to target the external network use case18:17
SumitNaiksatamkindly review that spec18:18
s3wongSumitNaiksatam: is that targeting Juno also?18:18
ivar-lazzaroyes please, especially let's try to understand together which resources we want to make "sharable" on the reference implementation18:18
SumitNaiksatams3wong: yes all this for Juno18:18
ivar-lazzarobased on what neutron allows us to do ofc :)18:18
SumitNaiksatamand by Juno we mean preferably Nov 28th, because that is feature18:19
SumitNaiksatam*feature freeze18:19
SumitNaiksatamrkukura is also working on the extensions loading mechanism for vendor drivers18:19
SumitNaiksatamthe spec is approved18:20
*** dboik has joined #openstack-meeting-318:20
SumitNaiksatamrkukura: is a patch posted for this?18:20
rkukuranot yet - next week18:20
SumitNaiksatamrkukura: ok cool18:20
*** mwagner_lap has joined #openstack-meeting-318:20
rkukuraDo we need extensions for all resources initially? Or just the ones with mappings?18:21
SumitNaiksatamanyone planning to write the vendor drivers please take note of the extension loading mechanism (similar to that proposed in ML2)18:21
SumitNaiksatamrkukura: ah, so you are planning to move the mapping to the driver as well?18:21
rkukuraSumitNaiksatam: That would be a 2nd phase, but maybe also next week18:21
SumitNaiksatamrkukura: ok18:22
SumitNaiksatami think ivar-lazzaro and banix have requirements for the extension loading from drivers18:22
rkukuraPlan is for initial patch to support extensions for L3P, L2P, PTG, and PT only18:22
*** Cathy_ has joined #openstack-meeting-318:22
SumitNaiksatamso they might be able to speak to this18:22
SumitNaiksatamCathy_: hi18:22
Cathy_SumitNaiksatam: hi, sorry to join late18:22
SumitNaiksatamCathy_: no worries, the time shift was confusing for everyone18:23
*** dboik has quit IRC18:23
*** dboik has joined #openstack-meeting-318:23
SumitNaiksatamivar-lazzaro banix can you sync with rkukura offline on which resources you need support for?18:23
ivar-lazzarorkukura: what does that imply? Will contracts still be bound to SGs for all the drivers?18:23
banixSumitNaiksatam: ok will do18:24
SumitNaiksatambanix: thanks18:24
rkukuraivar-lazzaro: We don’t expose the SG mapping, so shouldn’t be an issue for that18:24
rkukuraA followup patch would add support for extending whatever other resources we need18:24
ivar-lazzarorkukura: yeah just realized that, nevermind :)18:24
SumitNaiksatamrkukura: ah, that would be ideal!18:24
ivar-lazzarorkukura: that's great!18:25
SumitNaiksatamrkukura: thanks for that update18:25
SumitNaiksatamnext item ...18:25
SumitNaiksatams3wong is working on getting the updates to work for the policy rules and rule sets18:25
SumitNaiksatams3wong this would involve DB schema changes, right?18:26
s3wongSumitNaiksatam: indeed18:26
SumitNaiksatamjust asking if this warrants a spec18:26
SumitNaiksatambut dont want to introduce unnecessary process overhead18:26
SumitNaiksatamwe can have a separate design review session if required18:26
s3wongSumitNaiksatam: yes, I need to have several more tables to get which SG a policy-rule/classifier/action maps to18:27
SumitNaiksatams3wong: makes sense18:27
s3wongSumitNaiksatam: OK18:27
SumitNaiksatamnext item is incorporating the redirect action in the hierarchical contract composition18:27
*** ycombinator_ has joined #openstack-meeting-318:27
*** SridharRamaswamy has joined #openstack-meeting-318:27
SumitNaiksatammagesh is not here, but he might be interested in doing that, i will follow up offline with him18:27
s3wong(currently I am operating under the assumption that I don't need a separate spec for that... because TBH, it should have been done along with the last SG patch :-)  )18:28
rkukuras3wong: have you looked into a joined query?18:28
ivar-lazzarorkukura: +118:28
SumitNaiksatams3wong: fair enough :-)18:28
rkukuras3wong: I agree a spec should not be needed18:28
s3wongrkukura: no, but that does sound like a better thing to do...18:28
hemanthraviSumitNaiksatam, i18:29
SumitNaiksatamhemanthravi: hi, you made it :-)18:29
hemanthraviSumitNaiksatam, will follow up magesh on the redirect...18:29
*** salv-orlando has joined #openstack-meeting-318:29
hemanthraviSumitNaiksatam, forgot about the time change...call at 1118:29
SumitNaiksatamhemanthravi: great thanks!18:30
SumitNaiksatams3wong: thanks for the update, anything more on that work item?18:30
s3wongSumitNaiksatam: no, but will definitely get it done by Nov. 28th :-)18:30
SumitNaiksatams3wong: sweet, thanks! :-)18:30
SumitNaiksatamnext item - vendor drivers18:31
SumitNaiksatami believe ronak is not here18:31
SumitNaiksatami believe he is working on this18:31
SumitNaiksatambanix: any chance that you will posting one for this release?18:31
banixSumitNaiksatam: There is a colleague who is working on it and I will have to check and see how that is going. Have not been in close contact with that work.18:32
*** markmcclain1 has quit IRC18:32
SumitNaiksatambanix: no worries18:32
SumitNaiksatambanix: please let us know if you/he needs any help on that18:33
banixSumitNaiksatam: sure. thanks.18:33
SumitNaiksatambanix: we have a couple of vendor drivers in, so we have some basic experience on that18:33
SumitNaiksatamjust noticed s3wong posted the ODL driver, #link https://review.openstack.org/13428518:33
banixsounds good.18:33
s3wongSumitNaiksatam: the ODL policy driver probably won't make the 11/28 cutoff (though I posted the spec under juno)18:33
SumitNaiksatams3wong: great that you got this in18:33
SumitNaiksatams3wong: lets work on that18:34
banixthe spec for it18:34
SumitNaiksatams3wong: is yapeng planning to help out with the implementation?18:34
s3wongSumitNaiksatam: Yapeng is more focus on ODL side18:35
SumitNaiksatams3wong: ok got it18:35
SumitNaiksatams3wong: lets have a separate short session to review that spec, so that we can move ahead18:35
s3wonghe is looking into having another renderer and implement any gap between ODL and OpenStack GBP in ODL GBP18:35
SumitNaiksatams3wong: okay sounds good18:35
SumitNaiksatamnext major work item is testing18:36
SumitNaiksatamwe need to increase UT and FT coverage18:36
SumitNaiksatami will work on weeding out the problem areas18:37
nbouthorss3wong: where can we find the specs for the ODL GBP driver requirements18:37
SumitNaiksatamKanzhe is looking at the scenarios that we would need to test18:37
SumitNaiksatamnbouthors: #link https://review.openstack.org/13428518:37
s3wongnbouthors: SumitNaiksatam posted a link above.. but here it is #link https://review.openstack.org/#/c/134285/18:37
nbouthorsok thanks18:37
SumitNaiksatamKanzhe: probably you did not get a chance to look at this yet18:37
KanzheSumitNaiksatam: Not yet.18:38
SumitNaiksatamKanzhe: np, some kind of a summary test plan would be good18:38
KanzhePlan to start working on it later the week.18:38
SumitNaiksatamKanzhe: that way multiple people can work on it in parallel18:38
SumitNaiksatamKanzhe: thanks18:38
SumitNaiksatamjust the high level scenarios18:39
KanzheSumitNaiksatam: sure.18:39
SumitNaiksatamthanks18:39
SumitNaiksatamthat work items on client, ui and heat side18:39
SumitNaiksatamsome things are broken in the client (apart from the renaming)18:39
SumitNaiksatambugs are posted, so please feel free to pick them up18:40
SumitNaiksatamuday is not here, but he is working on several UI pieces18:40
SumitNaiksatamperhaps we can have a separate session to discuss what the team would like to see in the UI18:40
SumitNaiksatamis susaant here?18:41
SumitNaiksatamhemanthravi: i believe the heat patches are mostly merged now?18:41
hemanthraviSumitNaiksatam, yes, will check if susaant pushed the devstack changes18:42
SumitNaiksatamhemanthravi: ok thanks18:42
SumitNaiksatamso the above is mostly what we want to focus for the juno release18:42
SumitNaiksatam#topic Kilo work items18:43
*** openstack changes topic to "Kilo work items (Meeting topic: networking_policy)"18:43
SumitNaiksatamCathy_: Louis and nbouthors have been working on a number of specs18:43
SumitNaiksatamthey are all listed here: #link https://review.openstack.org/#/q/status:open+project:stackforge/group-based-policy-specs+branch:master,n,z18:43
SumitNaiksatamso in parallel we will try to make progress on these spec reviews as well18:44
*** s1rp_ is now known as s1rp_irssi18:44
SumitNaiksatamwe have other features like policy tags which will be immediate priorities in Kilo18:44
SumitNaiksatambut i dont want to get too far ahead of ourselves, we can revisit priorities and features when we are actually done with Juno18:45
s3wongSumitNaiksatam: +118:45
Cathy_SumitNaiksatam: sounds good.18:45
SumitNaiksatamwe will discuss and have the Kilo topics as a standing agenda item in the meetings though, until then18:45
SumitNaiksatamwe should all be making progress in parallel, ideally! ;-)18:46
igordcardSumitNaiksatam, +118:46
SumitNaiksatamigordcard: that would also include the traffic steering and classifiers :-)18:46
igordcardprobably it is already too late, but I would like to re-propose the traffic steering blueprint for Kilo18:46
Cathy_We will submit another BP for integrating with Service Funcitons instantiated outside of GBP or SC, which we think is higher priority than the other BPs we proposed earlier on18:46
igordcardSumitNaiksatam, exactly :)18:47
SumitNaiksatamCathy_: sounds good18:47
SumitNaiksatamigordcard: we will have to focus on getting the current model to work correctly (with the current set of classifiers)18:47
Cathy_SumitNaiksatam:ok18:48
SumitNaiksatamigordcard: but yes, i agree, lets discuss steering part in parallel, and figure out the scope and applicability18:48
SumitNaiksatam#action SumitNaiksatam to follow up with igordcard on steering spec18:48
Cathy_SumitNaiksatam: for integrating with Service Funcitons instantiated outside of GBP or SC, we would like to target it at Kilo18:48
igordcardSumitNaiksatam, alright :)18:48
SumitNaiksatamCathy_: yes, mandeep and tgraf (thomas) had some thoughts around this, so lets get everyone on the same page18:49
SumitNaiksatam#action SumitNaiksatam to follow up with Cathy_ on SFC18:49
Cathy_SumitNaiksatam: since in reality (based on my talk with other service function appliance companies) quite some SF will be instantiated outside GBP and SC18:49
*** armax has quit IRC18:50
SumitNaiksatamCathy_: agreed18:50
*** armax has joined #openstack-meeting-318:50
SumitNaiksatam#topic Open Discussion18:50
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:50
Cathy_SumitNaiksatam: I am looking forwward to talking with you. We will help develeping this.18:50
SumitNaiksatamCathy_: yes, hence added the AI for me :-)18:51
SumitNaiksatamokay we have 9 mins18:51
SumitNaiksatamwe circle back to discussion on the timelines etc18:51
SumitNaiksatamivar-lazzaro: so does it sound reasonable?18:51
*** gaitan has quit IRC18:51
ivar-lazzaroSumitNaiksatam: yes seems fair18:52
SumitNaiksatamivar-lazzaro: ok, doable? ;-)18:52
hemanthraviCathy_, we should also discuss if we can use SC to represent the SF instantiated outside18:52
ivar-lazzaroSumitNaiksatam: the work is well distributed, apart from major blockers that may arise it seems a reasonable timeline18:52
Cathy_hemanthravi: yes18:52
SumitNaiksatamivar-lazzaro: yeah18:52
SumitNaiksatamone dependency might be rkukura’s extension loading for the vendor drivers18:53
*** gaitan has joined #openstack-meeting-318:53
SumitNaiksatamoh i forgot to mention18:53
igordcardThe TS bp at its latest state is at https://review.openstack.org/#/c/92477, should its topic just be changed, or completely abandoned and recreated afterwards? Also, I'm not sure if gerrit allows changing the ownership...18:53
Cathy_hemanthravi: I have some thought on this. Let's have a meeting to discuss it18:53
SumitNaiksatamrkukura is working furiously on the packaging18:53
hemanthraviCathy_, ok18:53
rkukuraand my expense report ;)18:53
SumitNaiksatamrkukura: :-)18:53
SumitNaiksatamso rkukura would be working on the extension loading after that18:54
Cathy_hemanthravi: SumitNaiksatam : will Sumit call for a seperate face-to-face meeting for the discussion?18:54
SumitNaiksatamso we need to coordinate a bit so that we work in lock step here18:54
s3wongSumitNaiksatam: no problem for rkukura, he still has THREE whole weeks :-)18:54
SumitNaiksatamCathy_: hemanthravi sounds good18:54
SumitNaiksatams3wong: :-)18:54
SumitNaiksatamigordcard: to your question18:54
s3wongSumitNaiksatam: actually TWO18:54
SumitNaiksatamigordcard: note that your earlier spec was submitted in the neutron specs18:55
hemanthravirkukura, do the vendor drivers need to make any changes for the new mech18:55
SumitNaiksatamigordcard: however, the GBP specs are now separate from the neutron specs18:55
SumitNaiksatamigordcard: hence i was saying we need to understand which part is relevant where18:55
s3wongSumitNaiksatam, igordcard: traffic steering is interesting for GBP; on one hand, we already have classifier in GBP, on the other, we operate on an abstraction level such than TS may be a bit low level18:56
SumitNaiksatams3wong: agree18:56
SumitNaiksatambut we still need it18:56
s3wongigordcard: so --- looking forward to seeing your spec in context of GBP :-)18:57
SumitNaiksatamsince the service chain should ideally leverage this18:57
SumitNaiksatamigordcard: i can bring you up to speed if you are cofused between the projects and the processes ;-)18:57
SumitNaiksatamigordcard: lets take it offline18:58
SumitNaiksatamokay anything more to discuss to today?18:58
igordcardSumitNaiksatam, Okay then18:58
hemanthravineed to log off, bye18:58
*** hemanthravi has quit IRC18:58
SumitNaiksatamokay thanks everyone for joining18:58
Cathy_bye18:58
igordcardCya all18:58
SumitNaiksatamtill next week, bye!18:58
SumitNaiksatam#endmeeting18:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:58
KrishnaK_Quick question: Iam working on bug. what is best way to reach to the expert ? email or send group email18:58
openstackMeeting ended Thu Nov 13 18:58:43 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-11-13-18.02.html18:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-11-13-18.02.txt18:58
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-11-13-18.02.log.html18:58
*** Cathy_ has quit IRC18:58
banixbye18:59
SumitNaiksatamKrishnaK_: you can use the IRC channel #openstack-gbp18:59
igordcardSumitNaiksatam, where to?18:59
SumitNaiksatamand/or send to the -dev mailing list18:59
KrishnaK_SumitNaiksatam: Thanks.18:59
SumitNaiksatamand/or send to the team :-)18:59
ivar-lazzarociao!19:00
*** bobmel_ has joined #openstack-meeting-319:00
*** RG has quit IRC19:00
rkukurabye19:00
s3wongbye19:00
*** nbouthors has quit IRC19:01
*** jtomasek has quit IRC19:06
*** marun has quit IRC19:06
*** LouisF has joined #openstack-meeting-319:06
*** LouisF has quit IRC19:09
*** Kanzhe has quit IRC19:12
*** SridharRamaswamy has quit IRC19:12
*** igordcard has quit IRC19:13
*** carl_baldwin has joined #openstack-meeting-319:15
*** bobmel_ has quit IRC19:16
*** baoli has quit IRC19:19
*** dconde has quit IRC19:21
*** etoews has joined #openstack-meeting-319:23
*** dconde has joined #openstack-meeting-319:24
*** rkukura has left #openstack-meeting-319:24
*** otherwiseguy has quit IRC19:26
*** LouisF has joined #openstack-meeting-319:27
*** LouisF has quit IRC19:28
*** ivar-laz_ has joined #openstack-meeting-319:29
*** marun has joined #openstack-meeting-319:30
*** MaxV has joined #openstack-meeting-319:30
*** ivar-laz_ has quit IRC19:30
*** ivar-laz_ has joined #openstack-meeting-319:31
*** ivar-lazzaro has quit IRC19:31
*** ivar-laz_ has quit IRC19:31
*** salv-orlando has quit IRC19:31
*** ivar-lazzaro has joined #openstack-meeting-319:32
*** bobmel_ has joined #openstack-meeting-319:36
*** SridharRamaswamy has joined #openstack-meeting-319:41
*** bobmel_ has quit IRC19:45
*** lpetrut has quit IRC19:49
*** ycombinator_ has quit IRC19:53
*** salv-orlando has joined #openstack-meeting-319:55
*** bpokorny has joined #openstack-meeting-319:59
*** yamamoto has quit IRC20:01
*** marun has quit IRC20:02
*** Youcef has quit IRC20:02
*** bpokorny_ has quit IRC20:02
*** marun has joined #openstack-meeting-320:04
*** KrishnaK_ has quit IRC20:04
*** rharwood has joined #openstack-meeting-320:05
*** bpokorny_ has joined #openstack-meeting-320:06
*** igordcard has joined #openstack-meeting-320:07
*** bpokorny has quit IRC20:09
*** otherwiseguy has joined #openstack-meeting-320:18
*** kashyap is now known as ||20:18
*** || is now known as kashyap20:18
*** MaxV has quit IRC20:30
*** yamamoto has joined #openstack-meeting-320:32
*** yamamoto has quit IRC20:34
*** yamamoto has joined #openstack-meeting-320:34
*** MaxV has joined #openstack-meeting-320:37
*** MaxV has quit IRC20:38
*** MaxV has joined #openstack-meeting-320:38
*** yamamoto has quit IRC20:39
*** SridharRamaswamy has quit IRC20:39
*** iovadia has joined #openstack-meeting-320:42
*** carl_baldwin has quit IRC20:43
*** carl_baldwin has joined #openstack-meeting-320:50
*** SumitNaiksatam has quit IRC20:50
*** baoli has joined #openstack-meeting-320:57
*** baoli has quit IRC20:57
*** baoli has joined #openstack-meeting-320:58
*** bobmel_ has joined #openstack-meeting-321:00
*** bobmel_ has quit IRC21:00
*** bobmel_ has joined #openstack-meeting-321:00
*** matrohon has joined #openstack-meeting-321:06
*** otherwiseguy has quit IRC21:06
*** bobmel_ has quit IRC21:07
*** dboik has quit IRC21:10
*** otherwiseguy has joined #openstack-meeting-321:13
*** otherwiseguy has quit IRC21:18
*** SumitNaiksatam has joined #openstack-meeting-321:22
*** dboik has joined #openstack-meeting-321:22
*** baoli has quit IRC21:23
*** baoli has joined #openstack-meeting-321:25
*** peristeri has quit IRC21:30
*** yamamoto has joined #openstack-meeting-321:32
*** thomasem has quit IRC21:34
*** MarkAtwood has joined #openstack-meeting-321:35
*** yamamoto has quit IRC21:37
*** otherwiseguy has joined #openstack-meeting-321:38
*** Adri2000_ is now known as Adri200021:50
*** bpokorny has joined #openstack-meeting-321:54
*** bpokorny_ has quit IRC21:56
*** bpokorny_ has joined #openstack-meeting-322:00
*** bpokorn__ has joined #openstack-meeting-322:02
*** bpokorny has quit IRC22:02
*** bpokorny_ has quit IRC22:03
*** bobmel_ has joined #openstack-meeting-322:05
*** igordcard has quit IRC22:06
*** sergef has quit IRC22:11
*** bobmel_ has quit IRC22:16
*** igordcard has joined #openstack-meeting-322:21
*** banix has quit IRC22:26
*** thangp has quit IRC22:29
*** ivar-laz_ has joined #openstack-meeting-322:31
*** ivar-laz_ has quit IRC22:31
*** ivar-laz_ has joined #openstack-meeting-322:32
*** yamamoto has joined #openstack-meeting-322:32
*** dboik has quit IRC22:32
*** matrohon has quit IRC22:33
*** ivar-lazzaro has quit IRC22:34
*** yamamoto has quit IRC22:37
*** banix has joined #openstack-meeting-322:37
*** banix has quit IRC22:38
*** ycombinator_ has joined #openstack-meeting-322:41
*** gholler has quit IRC22:43
*** armax has quit IRC22:47
*** marun has quit IRC22:47
*** jcoufal has quit IRC22:51
*** MaxV has quit IRC22:51
*** MaxV has joined #openstack-meeting-322:52
*** alexsyip has quit IRC22:56
*** bpokorny has joined #openstack-meeting-323:00
*** pballand has quit IRC23:01
*** banix has joined #openstack-meeting-323:03
*** bpokorn__ has quit IRC23:03
*** gduan has joined #openstack-meeting-323:04
*** garyduan has quit IRC23:04
*** mattfarina has quit IRC23:04
*** pballand has joined #openstack-meeting-323:05
*** bobmel_ has joined #openstack-meeting-323:05
*** alexpilotti has quit IRC23:05
*** sigmavirus24 is now known as sigmavirus24_awa23:08
*** ivar-laz_ has quit IRC23:10
*** ivar-lazzaro has joined #openstack-meeting-323:10
*** igordcard has quit IRC23:11
*** bobmel_ has quit IRC23:12
*** banix has quit IRC23:18
*** armax has joined #openstack-meeting-323:20
*** baoli has quit IRC23:20
*** armax has quit IRC23:21
*** baoli has joined #openstack-meeting-323:21
*** armax has joined #openstack-meeting-323:23
*** MaxV has quit IRC23:24
*** Sukhdev has joined #openstack-meeting-323:26
*** banix has joined #openstack-meeting-323:30
*** yamamoto has joined #openstack-meeting-323:32
*** dtroyer has joined #openstack-meeting-323:32
*** yamamoto has quit IRC23:37
*** gduan has quit IRC23:37
*** baoli has quit IRC23:41
*** otherwiseguy has quit IRC23:41
*** dconde has quit IRC23:52
*** ChuckC has quit IRC23:52
*** Sukhdev has quit IRC23:53
*** iovadia has quit IRC23:53
*** gholler has joined #openstack-meeting-323:54
*** banix has quit IRC23:55
*** garyduan has joined #openstack-meeting-323:56
*** ameade has joined #openstack-meeting-323:56
*** adrian_otto has joined #openstack-meeting-323:57
*** banix has joined #openstack-meeting-323:57
*** rudrarugge has joined #openstack-meeting-323:58

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