Thursday, 2014-12-11

etoews#startmeeting api wg00:00
openstackMeeting started Thu Dec 11 00:00:21 2014 UTC and is due to finish in 60 minutes.  The chair is etoews. Information about MeetBot at http://wiki.debian.org/MeetBot.00:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.00:00
*** openstack changes topic to " (Meeting topic: api wg)"00:00
openstackThe meeting name has been set to 'api_wg'00:00
etoewsanyone else here for the api wg meeting?00:00
rosmaitao/00:00
etoewshello sir00:00
ryansbo/00:01
eliqiaoo/00:01
etoewsgood day/evening to all!00:01
elmikoo/00:01
etoews#topic agenda00:01
*** openstack changes topic to "agenda (Meeting topic: api wg)"00:01
etoews#link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda00:01
*** banix has quit IRC00:02
*** vinay_yadhav has joined #openstack-meeting-300:02
etoewsas you can probably tell i structured the wiki meeting page to be easy to copy/paste meetbot commands from00:02
rosmaitagood idea00:02
etoewsi'm thinking i'll put a "placeholder" in for *new* specific topics at the start00:03
etoewsif there's something beyond our regular review and such, we should tackle it first.00:03
etoewsso anyone is always welcome to update the agenda to put a specific topic00:03
elmikonice00:04
etoews#topic previous meeting action items00:04
*** openstack changes topic to "previous meeting action items (Meeting topic: api wg)"00:04
etoews#link http://eavesdrop.openstack.org/meetings/api_wg/2014/api_wg.2014-12-04-16.01.html00:04
*** mwang2_ has quit IRC00:04
etoewscyeoh merged the Process for merging guideline changesets https://review.openstack.org/#/c/131358/ !00:05
*** baoli has quit IRC00:05
elmikoyea, that was nice. seemed like we had a good consensus.00:05
etoewsthat really means we're off and running now00:05
stevelleo/00:05
etoewsmy guideline met that criteria and was merged today by jaypipes https://review.openstack.org/#/c/133087/00:06
elmikovery cool00:06
etoewswhen i say "my" i mean ours. that one started at the summit during a design session and a bunch of us worked on it.00:06
etoewsi emailed the magnetodb team and gave them an intro to the api wg on the ml00:07
etoewsit was pretty well received.00:07
*** salv-orlando has quit IRC00:08
elmikogood to hear00:08
ryansbyeah, saw that on the ML00:08
etoewsisviridov is now our liaison https://wiki.openstack.org/wiki/CrossProjectLiaisons#API_Working_Group00:08
*** s3wong has quit IRC00:08
etoewsycombinator had an action item00:09
*** bpokorny_ has joined #openstack-meeting-300:09
etoewslooks like he's not online atm.00:09
*** clu_ has quit IRC00:10
*** dboik has quit IRC00:10
etoewsthere's another action item for all of us but it belongs under apiimpact anyway00:10
*** ycombinator_ has joined #openstack-meeting-300:10
elmikolol, nice00:11
etoews#topic APIImpact00:11
*** openstack changes topic to "APIImpact (Meeting topic: api wg)"00:11
etoews#link https://review.openstack.org/#/q/status:open+AND+(message:ApiImpact+OR+message:APIImpact),n,z00:11
etoewsthe one we were requested to review was https://review.openstack.org/#/c/136760/00:11
etoews#link https://review.openstack.org/#/c/136760/00:11
etoewsi confess i didn't get to it amongst everything else... :(00:12
miguelgrinberghello, late again :-)00:12
*** bpokorny has quit IRC00:12
etoewsdid anyone have a look at it?00:12
elmikonot me, but looks like that review has generated a large amount of comments.00:13
rosmaitasorry, no, i am way behind00:13
etoewsno worries.00:14
*** eliqiao has quit IRC00:14
etoewselmiko: good point. it's got a fair amount of eyes on it already.00:14
*** emagana has quit IRC00:14
*** emagana has joined #openstack-meeting-300:15
etoewsanything else from https://review.openstack.org/#/q/status:open+AND+(message:ApiImpact+OR+message:APIImpact),n,z that someone would like to call out?00:15
miguelgrinbergI reviewed https://review.openstack.org/#/c/136253/00:15
*** vinay_yadhav has quit IRC00:15
miguelgrinbergit's an interesting one, it has a definition on how to add/remove from a list of things00:15
miguelgrinbergI suggested an approach that they did not like, because it is different to what they are doing now in other parts of the API00:16
miguelgrinbergthey use a PUT with a partial resource representation00:16
*** banix has joined #openstack-meeting-300:16
*** Sukhdev has quit IRC00:17
miguelgrinbergI think we should decide what is the approach to recommend going forward for dealing with lists of things00:17
*** emagana_ has joined #openstack-meeting-300:17
*** Rockyg has quit IRC00:17
etoewsis it a membership type of relationship or just a plain list of things?00:17
miguelgrinbergit's not a list of resources, these are metadata items00:18
*** emagana has quit IRC00:18
etoewsokay00:18
miguelgrinbergassociated with a volume in this case00:18
*** shakamunyi has quit IRC00:18
miguelgrinbergthey want to send PUT with key:value for new items, and key with empty value to delete00:18
etoewsoh00:19
elmikowouldn't that be normal for updating a resource?00:19
miguelgrinberga more correct approach IMHO would be to send the complete list in the PUT request00:19
*** SumitNaiksatam has joined #openstack-meeting-300:19
miguelgrinbergif you want to delete just not send what you want out00:19
elmikomiguelgrinberg: that seems like a more complete solution00:19
*** banix has quit IRC00:19
etoewsthat's puts a bigger burden on the client00:20
elmikodoes it burden the client to carry too much info though?00:20
miguelgrinbergit ensure you know what the collection is, if not it is kind of unpredictable00:20
miguelgrinbergI guess, you need to issue a GET to have the list00:20
miguelgrinbergbut it is likely the client already has that00:20
*** ChuckC has joined #openstack-meeting-300:20
etoewsi wouldn't make that assumption00:21
etoewstake a cli for example00:21
etoewsit's not storing any info anywhere00:21
ryansbalso there's the "what if it changed"00:21
*** banix has joined #openstack-meeting-300:21
etoewsstarting from 0 every time00:21
elmikogood points00:21
miguelgrinbergyeah, but adding to a list of things without knowing what's there in the first place it is not safe00:21
etoewsryansb: yep. a kind of race condition scenario00:21
ryansbif the list changed between your GET and PUT that would be bad00:22
miguelgrinbergit forces the server to deal with duplicates00:22
*** emagana_ has quit IRC00:22
miguelgrinbergrace conditions can happen in many other circumstances too00:22
*** emagana has joined #openstack-meeting-300:23
ycombinator_is adding/setting idempotent in this case (as its metadata)?00:23
elmikowhat about using some of the info, a partial record, to update with? ie just the essential plus your update00:23
etoewsi think sending the whole list to delete 1 thing would be particularly susceptible to that00:23
miguelgrinbergso going by the book, you would do that with a PATCH request, PUT should get the whole thing00:24
elmikoycombinator_: seems like it _should_ be... not sure how it's actually used in their code.00:25
*** bpokorny has joined #openstack-meeting-300:25
etoewswhat about treating metadata as its own resource and just issuing a DELETE?00:26
etoewswhether or not it is its own resource on the backend.00:26
miguelgrinbergetoews: that works, but you need to treat each metadata item as an individual resource, it can be overkill00:26
elmikointeresting idea though00:26
stevellea PATCH is just so much cleaner and easier to reason about00:27
miguelgrinberghow it is stored in the server does not matter, but the API will have to expose each item as an individual resource with its own URI00:27
etoewsoverkill in that there could be a lot?00:27
miguelgrinbergyeah, a lot of resources, and not much content in each00:27
*** ycombinator_ has quit IRC00:27
miguelgrinbergjust a value00:27
*** emagana has quit IRC00:27
dtroyeretoews: yes…a lot of round-trips00:27
elmikois there a compelling reason not to recommend the PATCH operation?00:28
*** bpokorny_ has quit IRC00:28
*** ycombinator_ has joined #openstack-meeting-300:29
miguelgrinbergso I'm not completely happy with how they delete stuff, even with PATCH that would have to stay the same00:29
miguelgrinbergthey set a key with an empty value00:29
ycombinator_(sorry, I'm having network issues)00:30
miguelgrinbergeven for a PATCH, that does not seem RESTful to me00:30
dtroyerI'm on the fence about that one…doing the key-only for delete simplified a bunch in OSC00:31
elmikomiguelgrinberg: are you saying the even with a PATCH the whole list should be sent?00:31
elmiko*that even00:31
miguelgrinbergelmiko: I'm not sure what I'm saying, just that deleting something with a PATCH request seems odd00:31
elmikogotcha00:32
miguelgrinbergwhat would be the possible responses to that? 200 if it worked, and what if the item does not exist?00:32
miguelgrinberg400?00:32
*** jaypipes has quit IRC00:32
*** vitorc has quit IRC00:32
elmikogood questions00:32
miguelgrinbergyou can't send a 404, since it's not a resource you are deleting00:32
ycombinator_is deleting an item that does not exist an error?00:33
miguelgrinbergycombinator_: another good question, it depends on that case I guess00:33
etoewsfor reference, nova treats metadata as a resource http://developer.openstack.org/api-ref-compute-v2.html#compute_server_metadata00:33
ycombinator_I like the PATCH approach because its not chatty but my only concern is the representation of the key's value for deletion - what if null/0 are valid values for a key?00:34
dtroyeralso, in this case at least, the metadata is a single field (a dict) at the volume record level.00:34
miguelgrinbergwell, we have a precedent, this looks much nicer than what they intend to do00:34
*** banix has quit IRC00:34
elmikohaving the metadata endpoint seems really nice00:35
miguelgrinbergthey even implemented PUT for the whole metadata set00:35
*** sunnyr has quit IRC00:35
etoewscinder snapshots treat it as a resource http://developer.openstack.org/api-ref-blockstorage-v2.html#snapshots-v200:35
miguelgrinbergnice00:35
*** vishwanathj has quit IRC00:35
etoewsheh. i forgot that this is a cinder spec!00:36
etoewsthey didn't look at their own api to ensure they were at least consistent with that?00:36
miguelgrinbergdo we need a spec on working with metadata items?00:36
miguelgrinbergsomething we can refer to?00:37
etoewsmiguelgrinberg: do you mean a guideline?00:37
miguelgrinbergsorry, yes, that's what I meant00:37
etoewsyes. i think you're right. we do.00:37
elmiko+100:37
etoewsdesparately00:37
*** banix has joined #openstack-meeting-300:37
ycombinator_is metadata a special case or do we need a guideline for updating some items in lists?00:37
*** clu_ has joined #openstack-meeting-300:38
etoewsi think metadata is something of a special case00:38
*** haleyb has quit IRC00:38
etoewsjust because it's used in so many places.00:38
miguelgrinbergyeah, metadata is special, it's key-value lists00:38
miguelgrinbergfor other resources you can use regular REST stuff00:38
ycombinator_I guess that's what I'm getting at - what is the downside of applying regular REST to metadata as well?00:39
etoewsmiguelgrinberg: did you want to take an action item to comment about it on that review?00:39
ycombinator_so the sub-resource for each metadata key idea that everett proposed earlier00:39
miguelgrinbergyes, I will do that00:39
miguelgrinbergycombinator_: I think we are saying that we need to apply REST to metadata items, but we also need ways to get or replace this data in one chunk, for practical purposes00:40
*** yamamoto has joined #openstack-meeting-300:40
miguelgrinbergthe nova example llinked above is a good one in my opinion00:40
etoews#action miguelgrinberg to comment on https://review.openstack.org/#/c/136253/ to point out that metadata works better as its own resource, just like for cinder snapshots http://developer.openstack.org/api-ref-blockstorage-v2.html#snapshots-v200:40
ycombinator_okay, so metadata is special because unlike other lists of resources, it needs to be updated en-masse more frequently - got it!00:40
ycombinator_we should probably clarify that in the guideline00:41
etoewsis there an action item here to create a guideline for metadata?00:41
*** SumitNaiksatam has quit IRC00:41
elmikosounds like it00:41
etoewsif so, who's got it?00:41
miguelgrinbergI think it would be useful00:41
ycombinator_I'm happy to take a crack at it00:42
ycombinator_unless it makes sense to keep both actions with miguelgrinberg since they are related00:42
miguelgrinbergI'm fine either way, I can write an initial doc to review next week if you want00:42
ycombinator_+100:43
*** vitorc has joined #openstack-meeting-300:43
*** salv-orlando has joined #openstack-meeting-300:43
*** carl_baldwin has quit IRC00:43
etoews#action miguelgrinberg to write up an initial guideline to review for metadata to be consistent across openstack00:43
etoewslet's move on00:43
etoews#topic guidelines00:43
*** openstack changes topic to "guidelines (Meeting topic: api wg)"00:43
etoews#link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z00:44
etoewsi think we had an action item from before to review ycombinator_ guideline https://review.openstack.org/#/c/133660/00:44
*** Piet has joined #openstack-meeting-300:45
ycombinator_yes, I was supposed to put some stats in a comment00:45
ycombinator_I have not had a chance to get to it :(00:45
etoewsmy initial thought is that trying to cover both singular and collection resources in the same proposal was biting off too much00:45
ycombinator_I'm also wondering if its better to split this guideline into two00:45
ycombinator_ha00:45
etoewsheh00:45
ycombinator_there's consensus on collections, I think00:45
ycombinator_so I'd rather just start with that00:46
etoewssounds good00:46
*** RuiZang has joined #openstack-meeting-300:46
miguelgrinberg+1, let's get collections done first00:46
ycombinator_#action ycombinator to restrict scope of https://review.openstack.org/#/c/133660/ to collections only00:46
etoewsor close that one completely and start fresh?00:46
etoewsbut then you lose easy access to the historical discussion on collections.00:47
ycombinator_sure00:47
etoewsyour call00:47
ycombinator_yeah00:47
etoewshmmm...considering you'd have to change the commit message a new one might be advisable. then link to the old one in the comments.00:48
ycombinator_true - okay, I'll do that00:48
etoewsanyone else have advice on how to proceed here?00:48
elmikoi dunno, seems a shame to lose the history00:48
ryansbI'd go ahead and change the review00:48
dtroyerwhat is the concern about changing the commit message?00:48
ryansb(not make a new CR)00:49
ycombinator_I can put in a comment saying I'm going to rework the patch, including changing the commit message00:49
ycombinator_that way if someone read the comments, they'll know what happened00:49
ryansbthe change to the commit message will be part of the patch00:49
ycombinator_right00:49
ryansbso folks could see anyways00:49
etoewssgtm00:49
*** ijw_ has quit IRC00:50
*** MaxV has quit IRC00:50
etoews5 min to discuss anything else in https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z00:50
*** RuiZang has quit IRC00:50
elmikohttps://review.openstack.org/#/c/137490/ might need a few more eyes00:50
ryansbor if folks don00:51
*** RuiZang has joined #openstack-meeting-300:51
ryansb*don't have other topics, we can probably adjourn early00:51
miguelgrinbergwhen are we going to start merging these guidelines?00:51
etoewsthat's what i was just looking at...00:51
etoewshttps://review.openstack.org/#/c/130825/ looks mergable.00:51
rosmaitaryansb: i have a topic for open discussion00:51
elmikoi have an item for open disc. too00:52
*** armax has joined #openstack-meeting-300:52
etoewsto look up the merge permissions on any project, use a URL like this:00:52
etoewshttps://review.openstack.org/#/admin/projects/openstack/api-wg,access00:52
etoewsyou can click to see who belongs in the group with access control:00:52
etoewshttps://review.openstack.org/#/admin/groups/468,members00:52
etoewscyeoh and jaypipes can merge.00:52
*** Sukhdev has joined #openstack-meeting-300:53
etoewsi know cyeoh is still recovering. i'll ping jay to review the queue and merge what meets the criteria.00:53
etoews#action etoews ping jay to review the queue https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z and merge what meets the criteria.00:54
etoews#topic open topics00:54
*** openstack changes topic to "open topics (Meeting topic: api wg)"00:54
etoewsshoot rosmaita00:54
rosmaitaanyone have a reaction to nova dropping xml in v2 ?00:54
rosmaitadidn't bother me when i thought there would be v300:55
rosmaitabut it seems a bit weird00:55
etoewsi had a reaction to it a long time ago but then i got over it.00:55
rosmaitai am late to the party00:55
miguelgrinbergsomebody somewhere is probably using it00:55
etoewsdefinitely00:55
rosmaitaguess that train has left the station00:55
etoewsi think so. i fought it for a bit but then folded like a house of cards. :(00:56
miguelgrinbergit would be awesome if some day content types are abstracted in a framework that all APIs use00:56
elmikomiguelgrinberg: +100:56
miguelgrinbergthen it does not matter, all we see are Python dicts00:56
rosmaitathat would indeed be awesome00:56
rosmaitaok, that's all i had00:56
elmikomine is mainly informational00:57
elmikoat summit we talked briefly about swagger00:57
etoewsyes00:57
elmikoi have a poc prototype up for sahara to generate the base required doc for swagger 2.000:57
elmikohttps://github.com/elmiko/sahara-doc00:57
elmikovery proto still, but i'm going to add more to it and create a WADL->Swagger generator as well00:57
elmikoright now it just dumps the json output, but i want to build a server in too00:58
etoewssaid wadl > swagger generator may already exist.00:58
etoewslet's make this a top level topic for next meeting!00:58
elmikoyea, i think Max Lincoln had something going, i still need to get in touch with him.00:58
ycombinator_https://pypi.python.org/pypi/wadl2swagger/0.0.200:58
elmikooh awesome!00:58
elmikoycombinator_: thanks00:59
miguelgrinbergit would be awesome to omit the syntax of reousrces in API docs, just saying00:59
miguelgrinbergso that people are not encouraged to build URLs on the client side00:59
*** alexpilotti has quit IRC00:59
ycombinator_+100:59
elmikomiguelgrinberg: not sure i follow, could you elaborate a little?00:59
miguelgrinbergyou do not need to show how URLs are formed01:00
miguelgrinbergbecause we want clients to get URLs from links in other resources01:00
elmikoahh ok01:00
ycombinator_miguelgrinberg: do you have an example?01:00
miguelgrinbergthe only URLs that should be public are the top-level ones01:00
elmikomakes good sense01:00
*** banix has quit IRC01:00
etoewsgonna have to end the meeting now...01:00
miguelgrinbergI need to dig for one, I promise to bring one next week01:00
*** salv-orlando has quit IRC01:00
ycombinator_cool01:00
rosmaitabye01:00
*** alexpilotti has joined #openstack-meeting-301:00
miguelgrinbergbye guys01:00
ycombinator_bye01:00
etoews#endmeeting01:01
elmikolater01:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"01:01
openstackMeeting ended Thu Dec 11 01:01:01 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-12-11-00.00.html01:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2014/api_wg.2014-12-11-00.00.txt01:01
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2014/api_wg.2014-12-11-00.00.log.html01:01
etoewsthanks all!01:01
*** stevelle has left #openstack-meeting-301:01
*** rosmaita has left #openstack-meeting-301:01
*** RuiZang has quit IRC01:01
*** ryansb has left #openstack-meeting-301:02
*** alexpilotti has quit IRC01:03
*** Piet has quit IRC01:03
*** armax has quit IRC01:04
*** elmiko has left #openstack-meeting-301:05
*** yamamoto has quit IRC01:06
*** armax has joined #openstack-meeting-301:06
*** ycombinator_ has quit IRC01:11
*** Longgeek has joined #openstack-meeting-301:13
*** Longgeek has quit IRC01:14
*** Longgeek has joined #openstack-meeting-301:14
*** stanzgy has joined #openstack-meeting-301:15
*** Longgeek has quit IRC01:18
*** reed has quit IRC01:21
*** RuiZang has joined #openstack-meeting-301:23
*** Sukhdev has quit IRC01:29
*** armax has quit IRC01:38
*** ChuckC has quit IRC01:38
*** dtroyer has left #openstack-meeting-301:38
*** markmcclain has quit IRC01:39
*** etoews has quit IRC01:41
*** yamamoto has joined #openstack-meeting-301:43
*** shakamunyi has joined #openstack-meeting-301:43
*** sandr8 has joined #openstack-meeting-301:44
*** ChuckC has joined #openstack-meeting-301:44
*** killer_prince has quit IRC01:45
*** killer_prince has joined #openstack-meeting-301:46
*** killer_prince is now known as lazy_prince01:46
*** banix has joined #openstack-meeting-301:46
*** ChuckC has quit IRC01:48
*** ChuckC has joined #openstack-meeting-301:49
*** MaxV has joined #openstack-meeting-301:51
*** lazy_prince has quit IRC01:52
*** RuiZang has quit IRC01:53
*** killer_prince has joined #openstack-meeting-301:54
*** killer_prince is now known as lazy_prince01:54
*** amotoki has joined #openstack-meeting-301:55
*** MaxV has quit IRC01:55
*** RuiZang has joined #openstack-meeting-301:58
*** RuiZang has quit IRC02:07
*** banix has quit IRC02:07
*** banix has joined #openstack-meeting-302:09
*** bpokorny has quit IRC02:13
*** jacalcat has joined #openstack-meeting-302:18
*** jacalcat has left #openstack-meeting-302:19
*** david-lyle is now known as david-lyle_afk02:30
*** baoli has joined #openstack-meeting-302:32
*** shakamunyi_ has joined #openstack-meeting-302:37
*** alexsyip has quit IRC02:40
*** banix has quit IRC02:46
*** shakamunyi_ has quit IRC02:48
*** clu_ has quit IRC02:50
*** banix has joined #openstack-meeting-302:50
*** vkmc has quit IRC02:52
*** ivar-lazzaro has quit IRC02:57
*** bpokorny has joined #openstack-meeting-302:58
*** shwetaap has joined #openstack-meeting-302:59
*** shakamunyi_ has joined #openstack-meeting-303:02
*** shakamunyi has quit IRC03:12
*** shakamunyi_ has quit IRC03:12
*** bpokorny has quit IRC03:13
*** bpokorny has joined #openstack-meeting-303:13
*** baoli has quit IRC03:19
*** VW has joined #openstack-meeting-303:19
*** baoli has joined #openstack-meeting-303:23
*** Piet has joined #openstack-meeting-303:24
*** amotoki has quit IRC03:42
*** amotoki has joined #openstack-meeting-303:42
*** lazy_prince has quit IRC03:45
*** killer_prince has joined #openstack-meeting-303:47
*** killer_prince is now known as lazy_prince03:47
*** amotoki has quit IRC03:47
*** yamamoto has quit IRC03:59
*** yamamoto has joined #openstack-meeting-304:02
*** yamamoto has quit IRC04:02
*** yamamoto has joined #openstack-meeting-304:02
*** yamamot__ has joined #openstack-meeting-304:02
*** yamamoto has quit IRC04:06
*** banix has quit IRC04:07
*** mwagner_lap has joined #openstack-meeting-304:14
*** jaypipes has joined #openstack-meeting-304:19
*** banix has joined #openstack-meeting-304:23
*** sarob has joined #openstack-meeting-304:25
*** yapeng has quit IRC04:37
*** amotoki has joined #openstack-meeting-304:38
*** MaxV has joined #openstack-meeting-304:40
*** baoli has quit IRC04:42
*** amotoki_ has joined #openstack-meeting-304:43
*** banix has quit IRC04:44
*** MaxV has quit IRC04:44
*** amotoki_ has quit IRC04:48
*** VW has quit IRC04:49
*** MaxV has joined #openstack-meeting-304:50
*** MaxV has quit IRC04:55
*** salv-orlando has joined #openstack-meeting-305:04
*** sarob has quit IRC05:05
*** Sukhdev has joined #openstack-meeting-305:14
*** mrda is now known as mrda-away05:34
*** etoews has joined #openstack-meeting-305:41
*** etoews has quit IRC05:46
*** etoews has joined #openstack-meeting-305:59
*** etoews has quit IRC06:04
*** salv-orlando has quit IRC06:04
*** armax has joined #openstack-meeting-306:14
*** jkraj has joined #openstack-meeting-306:19
*** jkraj has quit IRC06:25
*** Sukhdev has quit IRC06:25
*** amotoki_ has joined #openstack-meeting-306:33
*** amotoki_ has quit IRC06:37
*** salv-orlando has joined #openstack-meeting-307:05
*** salv-orlando has quit IRC07:10
*** evgenyf has joined #openstack-meeting-307:13
*** yamamot__ has quit IRC07:14
*** tnovacik has joined #openstack-meeting-307:27
*** jtomasek has joined #openstack-meeting-307:28
*** k4n0 has joined #openstack-meeting-307:44
*** jcoufal has joined #openstack-meeting-307:46
*** vinay_yadhav has joined #openstack-meeting-307:46
*** devvesa has joined #openstack-meeting-307:48
*** mrunge has joined #openstack-meeting-307:48
*** sergef has joined #openstack-meeting-307:55
*** etoews has joined #openstack-meeting-308:01
*** shwetaap has quit IRC08:02
*** etoews has quit IRC08:05
*** zz_ttrifonov is now known as ttrifonov08:11
*** [1]evgenyf has joined #openstack-meeting-308:11
*** nelsnelson has joined #openstack-meeting-308:12
*** Longgeek has joined #openstack-meeting-308:12
*** evgenyf has quit IRC08:14
*** [1]evgenyf is now known as evgenyf08:14
*** vinay_yadhav has quit IRC08:18
*** Longgeek has quit IRC08:21
*** amotoki_ has joined #openstack-meeting-308:21
*** Longgeek has joined #openstack-meeting-308:23
*** amotoki_ has quit IRC08:26
*** mrmartin has joined #openstack-meeting-308:31
*** dconde has joined #openstack-meeting-308:35
*** zhipeng has quit IRC08:35
*** dconde has quit IRC08:35
*** igordcard has joined #openstack-meeting-308:40
*** etoews has joined #openstack-meeting-308:41
*** jcoufal has quit IRC08:42
*** jcoufal has joined #openstack-meeting-308:43
*** etoews has quit IRC08:46
*** MaxV has joined #openstack-meeting-308:52
*** salv-orlando has joined #openstack-meeting-308:52
*** armax has quit IRC08:56
*** salv-orlando has quit IRC08:57
*** safchain has joined #openstack-meeting-308:57
*** jcoufal has quit IRC09:01
*** jcoufal has joined #openstack-meeting-309:01
*** bradjones has quit IRC09:08
*** bradjones has joined #openstack-meeting-309:10
*** [1]evgenyf has joined #openstack-meeting-309:20
*** evgenyf has quit IRC09:22
*** [1]evgenyf is now known as evgenyf09:22
*** bradjones has quit IRC09:24
*** mrmartin has quit IRC09:30
*** Longgeek has quit IRC09:33
*** mrunge has quit IRC09:34
*** Longgeek has joined #openstack-meeting-309:42
*** bradjones has joined #openstack-meeting-309:44
*** sergef has quit IRC09:51
*** sergef has joined #openstack-meeting-309:52
*** mrunge has joined #openstack-meeting-310:00
*** amotoki_ has joined #openstack-meeting-310:09
*** amotoki_ has quit IRC10:14
*** vinay_yadhav has joined #openstack-meeting-310:30
*** igordcard has quit IRC10:30
*** mateuszb has joined #openstack-meeting-310:32
*** tnovacik is now known as tnovacik|afk10:35
*** amotoki_ has joined #openstack-meeting-310:35
*** evgenyf has quit IRC10:42
*** etoews has joined #openstack-meeting-310:42
*** igordcard has joined #openstack-meeting-310:46
*** sankarshan_away has quit IRC10:47
*** etoews has quit IRC10:47
*** vinay_yadhav has quit IRC10:47
*** stanzgy has quit IRC10:54
*** vinay_yadhav has joined #openstack-meeting-311:06
*** tnovacik|afk has quit IRC11:08
*** vinay_yadhav has quit IRC11:20
*** evgenyf has joined #openstack-meeting-311:29
*** tnovacik|afk has joined #openstack-meeting-311:37
*** salv-orlando has joined #openstack-meeting-311:43
*** salv-orlando has quit IRC11:47
*** tnovacik|afk is now known as tnovacik11:48
*** vinay_yadhav has joined #openstack-meeting-311:51
*** amotoki has quit IRC12:03
*** amotoki_ is now known as amotoki12:03
*** yamamoto has joined #openstack-meeting-312:05
*** reed has joined #openstack-meeting-312:09
*** baoli has joined #openstack-meeting-312:12
*** enikanorov_ has joined #openstack-meeting-312:13
*** baoli has quit IRC12:14
*** baoli has joined #openstack-meeting-312:15
*** enikanorov has quit IRC12:15
*** reed has quit IRC12:16
*** etoews has joined #openstack-meeting-312:21
*** andymaier has joined #openstack-meeting-312:22
*** etoews has quit IRC12:25
*** julim has joined #openstack-meeting-312:28
*** andymaier has quit IRC12:37
*** andymaier has joined #openstack-meeting-312:38
*** etoews has joined #openstack-meeting-312:39
*** shwetaap has joined #openstack-meeting-312:42
*** etoews has quit IRC12:44
*** vinay_yadhav has quit IRC12:52
*** shwetaap1 has joined #openstack-meeting-312:53
*** jgrimm is now known as zz_jgrimm12:53
*** vinay_yadhav has joined #openstack-meeting-312:54
*** shwetaap has quit IRC12:56
*** zhipeng has joined #openstack-meeting-312:59
*** zhipeng has quit IRC12:59
*** zz_jgrimm is now known as jgrimm13:01
*** belmoreira has joined #openstack-meeting-313:01
*** Adri2000 has quit IRC13:03
*** Adri2000 has joined #openstack-meeting-313:08
*** jcoufal_ has joined #openstack-meeting-313:09
*** etoews has joined #openstack-meeting-313:10
*** jcoufal has quit IRC13:12
*** vkmc has joined #openstack-meeting-313:13
*** jaypipes has quit IRC13:14
*** etoews has quit IRC13:16
*** jaypipes has joined #openstack-meeting-313:17
*** vinay_yadhav has quit IRC13:19
*** vinay_yadhav has joined #openstack-meeting-313:20
*** thomasem has joined #openstack-meeting-313:24
*** matrohon has joined #openstack-meeting-313:24
*** Sukhdev has joined #openstack-meeting-313:37
*** VW has joined #openstack-meeting-313:41
*** xuhanp has joined #openstack-meeting-313:42
*** VW has quit IRC13:43
*** tnovacik has quit IRC13:54
*** mateuszb has quit IRC14:01
*** vinay_yadhav has quit IRC14:02
*** thomasem has quit IRC14:05
*** xuhanp has quit IRC14:05
*** mrmartin has joined #openstack-meeting-314:08
*** Piet has quit IRC14:08
*** vinay_yadhav has joined #openstack-meeting-314:09
*** vinay_yadhav has quit IRC14:09
*** crobertsrh has joined #openstack-meeting-314:15
*** thomasem has joined #openstack-meeting-314:17
*** peristeri has joined #openstack-meeting-314:21
*** vitorc has quit IRC14:21
*** salv-orlando has joined #openstack-meeting-314:22
*** crobertsrh has left #openstack-meeting-314:22
*** vitorc has joined #openstack-meeting-314:24
*** Sukhdev has quit IRC14:26
*** belmoreira has quit IRC14:29
*** sergef has quit IRC14:30
*** tnovacik has joined #openstack-meeting-314:36
*** mattfarina has joined #openstack-meeting-314:38
*** mrmartin has quit IRC14:40
*** mrunge has quit IRC14:41
*** mrmartin has joined #openstack-meeting-314:44
*** mateuszb has joined #openstack-meeting-314:48
*** VW has joined #openstack-meeting-314:51
*** carl_baldwin has joined #openstack-meeting-314:53
*** etoews has joined #openstack-meeting-314:54
*** tidwellr1 has joined #openstack-meeting-314:54
*** Swami has joined #openstack-meeting-314:56
*** dboik has joined #openstack-meeting-314:57
carl_baldwinGood morning, all.14:59
*** tnovacik has quit IRC14:59
devvesaMorning Carl14:59
tidwellr1Good morning14:59
*** johnbelamaric has joined #openstack-meeting-314:59
Swamihi carl14:59
carl_baldwindevvesa: hi14:59
carl_baldwintidwellr1: Swami: hi14:59
johnbelamarichi14:59
carl_baldwinjohnbelamaric: hi15:00
yamamotohi15:00
*** pc_m has joined #openstack-meeting-315:00
carl_baldwin#startmeeting neutron_l315:00
openstackMeeting started Thu Dec 11 15:00:07 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:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:00
openstackThe meeting name has been set to 'neutron_l3'15:00
carl_baldwinpc_m: hi15:00
pc_mcarl_baldwin: hi!15:00
*** salv-orlando has quit IRC15:00
carl_baldwin#topic Announcements15:00
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:00
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:00
carl_baldwinWe just wrapped up a very good mid-cycle.15:00
pc_m+10015:01
carl_baldwinThe spec proposal deadline has passed.15:01
carl_baldwinThe spec approval deadline is this coming Monday.15:01
carl_baldwinAny other announcements?15:01
*** etoews_ has joined #openstack-meeting-315:02
*** mateuszb_ has joined #openstack-meeting-315:02
*** Jean-Brice has joined #openstack-meeting-315:02
carl_baldwin#topic Bugs15:02
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:02
*** tnovacik has joined #openstack-meeting-315:02
carl_baldwinAny bugs to bring up?  I don’t see any new general L3 bugs since last week15:03
carl_baldwinThough I think I’m do for another pass through the bug backlog.15:03
carl_baldwin#action carl_baldwin will go through the existing bug list.15:04
*** thangp has joined #openstack-meeting-315:04
carl_baldwin#topic L3 Agent Restructuring15:05
*** openstack changes topic to "L3 Agent Restructuring (Meeting topic: neutron_l3)"15:05
SwamiI don't see any new bugs or critical on the dvr side.15:05
carl_baldwinSwami: thanks15:05
*** etoews has quit IRC15:05
*** mateuszb has quit IRC15:05
carl_baldwinWe made a lot of progress on the L3 agent this week and gathered good momentum.15:05
carl_baldwinRealistically, we’ve got a few more weeks to go on this.15:06
carl_baldwin#link https://review.openstack.org/#/q/topic:bp/restructure-l3-agent+status:open,n,z15:06
*** mrsmith has joined #openstack-meeting-315:07
carl_baldwinThe effort got a bit more complicated after the advanced services split.15:07
pc_mYes, need to get #link https://review.openstack.org/#/c/136549/ in, as FW and VPN services need the base class that's in that commit.15:08
carl_baldwinpc_m: Yes, the dependency merged late yesterday.  I’ll review that next.15:08
Swamicarl_baldwin:with all these movemoments on L3 and services split, what will be the status of the current patches that are out for reveiw. Should it all wait for the transitions to happen first.15:09
pc_mcarl_baldwin: Great. That'll help getting that dependency out of the way.15:09
carl_baldwinYou should know that there are three new repositories (at least) neutron-vpnaas, neutron-fwaas, and neutron-lbass.15:09
carl_baldwinSwami: If it isn’t critical then it should wait for the refactoring to go it.15:10
Swamicarl_baldwin: got it.15:10
carl_baldwinThe extra *aas repos means that our work is a ilttle more difficult until the refactoring is done which should decouple this quite a lot.15:10
pc_mcarl_baldwin: plus the tests in VPN/FW repos are still being skipped.15:10
carl_baldwinpc_m: Good point.  What is your plan for the VPN tests?15:11
pc_mcarl_baldwin: Not sure :) Need to hook up with Doug, as he is going to work on getting the tests working.15:12
pc_mplan to help on that as soon as I get back home.15:12
carl_baldwinIt is also worth noting that the core reviewer list for the new *aas repos is not the same as that of the neutron repo.15:12
carl_baldwinpc_m: Keep me updated, I will follow up with fwaas about theirs.  Anyone from fwaas on today?15:13
carl_baldwin#action carl_baldwin will follow up with fwaas about skipped tests.15:13
pc_mcarl_baldwin: sure. I'll probably help out on the FWaaS too.15:13
* carl_baldwin reminds all to add action items for themselves when they come up.15:14
carl_baldwinpc_m: That will help.15:14
pc_m#action pc_m to work with Doug W on getting VPN and FW repo tests working.15:14
*** yamamoto_ has joined #openstack-meeting-315:15
carl_baldwinLet’s try to drive the current patches quickly.  We have a few more patches coming.  For example, creating the router class and moving router functionality out.  Creating that inheritence hierarchy to encapsulate DVR and HA, more *aas decoupling, etc.15:15
*** yamamoto has quit IRC15:16
carl_baldwinTry to give these patches priority in the review queue both on the reviewer and contributor side of things.15:16
carl_baldwinAnything else we should bring up about the refactoring?15:16
pc_mlooks like you got it all.15:17
carl_baldwinHere is another one that I think is ready:  https://review.openstack.org/#/c/140193/15:17
*** mrsmith_ has joined #openstack-meeting-315:18
*** mrsmith has quit IRC15:18
*** mrsmith_ has quit IRC15:19
carl_baldwin#topic bgp-dynamic-routing15:19
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:19
carl_baldwindevvesa: ping15:19
carl_baldwinAnything new this week?15:19
*** mrsmith has joined #openstack-meeting-315:19
devvesawell, it seems like the BGP proposal has been rejected15:20
carl_baldwinLooks like the spec has been dropped from kilo.15:20
devvesayes15:20
carl_baldwinI can’t say that I’m not really dissappointed.15:20
*** sunnyr has joined #openstack-meeting-315:20
carl_baldwinThis just means that everything else will be pushed out further.15:20
carl_baldwinI will propose it for reactivation later in Kilo.15:21
devvesawhat's 'everything else'?15:21
carl_baldwinBy “everything else” I meant anything that would leverage a bgp speaker in Neutron.15:22
devvesaOh. Sure. Anyway, I think the BGP-VPN guys are taking another path with the advanced services split15:23
carl_baldwinThere is the backing network work that I was going to do which requires bgp.15:23
*** bpokorny has quit IRC15:23
carl_baldwinipv6 subnet routing requires bgp or something to complete routing.15:24
devvesaDecision from Midokura will be to develop it as vendor extension, and then, keep trying to push it into neutron15:24
devvesaYou might consider to install midonet in HP datacenters :P15:24
carl_baldwin:)15:24
devvesaWell, meanwhile. If any of you need any kind of help, don't hesitate in let me know15:25
carl_baldwinIt may just mean that we’ll have to run some code outside of upstream.15:25
carl_baldwindevvesa: Thanks.  I’d still like to collaborate on this.  If the implementation were still completed, it would be easier to argue to get it in if there is room in Kilo.15:26
*** etoews_ has quit IRC15:26
carl_baldwinI will certainly still continue to review the code and will start with what you have up now.15:26
carl_baldwindevvesa: Anything else?15:26
devvesaI'm afraid that's all15:26
carl_baldwindevvesa: Thanks15:26
devvesathanks carl_baldwin15:27
carl_baldwinKeep doing good work.15:27
carl_baldwin#topic neutron-ipam15:27
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:27
*** mestery has joined #openstack-meeting-315:27
carl_baldwinjohnbelamaric: I’ll make another pass on https://review.openstack.org/#/c/97967/ today.  I think it has to be close.15:27
johnbelamariccarl_baldwin: ok, good. so far no comments on the last PS15:28
*** etoews has joined #openstack-meeting-315:28
carl_baldwin#action carl_baldwin will review https://review.openstack.org/#/c/97967/ today15:28
carl_baldwintidwellr1: I see you’ve been hard at work on https://review.openstack.org/#/c/135771/15:28
*** sunnyr has quit IRC15:28
tidwellr1carl_baldwin: yes15:29
carl_baldwinThank you for taking that on.  I will review that today too.15:29
carl_baldwin#action carl_baldwin will review https://review.openstack.org/#/c/135771/15:29
*** yapeng has joined #openstack-meeting-315:29
tidwellr1still some loose ends on that, I hope to tie them up today15:30
carl_baldwinsc68cal: Would you mind taking another look at it?15:30
*** jrist has quit IRC15:30
*** jrist has joined #openstack-meeting-315:30
carl_baldwinjohnbelamaric: Anything more to bring up?15:31
johnbelamaricone thing - on your comment on subnet-allocations, it sounded like you were thinking a global default prefix length - i think the default is per pool15:31
carl_baldwintidwellr1: How about you?15:31
johnbelamaricjust wanted to make sure we were all on the same page there15:32
carl_baldwinjohnbelamaric: per pool is what I was thinking.  Maybe it was unclear.15:32
tidwellr1I was thinking a per-pool default15:32
johnbelamaricok15:32
johnbelamaricgood15:32
johnbelamaricthat's it for me15:32
tidwellr1that's all for me15:33
carl_baldwinjohnbelamaric: tidwellr1:  Thanks.  This has come a long way.15:33
carl_baldwinI think that both specs are manageable for Kilo.15:33
carl_baldwin#topic neutron-ovs-dvr15:34
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:34
johnbelamaricgreat, i think it will be a good addition15:34
mrsmithSwami might have dropped off15:34
Swamicarl_baldwin: hi15:34
carl_baldwinSwami: mrsmith: hi15:34
SwamiI am still here mike.15:34
mrsmithguess not :)15:34
*** Rajeev has joined #openstack-meeting-315:35
Swamidvr team is still in the process of fixing bugs and filling in the technical debts.15:35
carl_baldwinRajeev: hi, you’re right on time.15:35
Rajeevcarl_baldwin: Hi.15:35
SwamiWe have a bunch of patches in review and in progress.15:35
SwamiRight now we are also looking at the "instability" issues reported from the gate.15:35
SwamiAdolfo is looking into those tests to understand and what test is mainly causing the instability.15:36
carl_baldwinSwami: I took a look through the backlog yesterday.  I plan to discuss with armax this week about diverting some core reviewer attention to it now that the specs review process is winding down.15:36
SwamiThe issue that we might have now is with all the refactor happening, it would be a double fix and refactor for us.15:36
Swamicarl_baldwin: I would appreciate it.15:37
mrsmithRajeev and I have made good progress with l3-ha and DVR15:37
mrsmithI pushed a patch for the agent last week15:37
carl_baldwinSwami: That is great.  I linked the graph of the stability gap between non-dvr and dvr to the L3 subteam page.15:37
SwamiRegarding the dvr documentation we do have a good handle now and working with the documentation folks.15:37
carl_baldwin… under the neutron-ovs-dvr section.15:37
Swamicarl_baldwin: thanks15:37
Swamimrsmith: Rajeev : do you have anything else to discuss15:38
mrsmithcovered most of my points - backlog progress, l3-ha, gate15:39
mrsmithI want to help out more with refactor patches - carl_baldwin: are there any for dvr I can take on?15:39
Swamicarl_baldwin: One other information is if our patches get delayed and more focus is given to the l3-refactoring work, may be we can help to speed up the process of l3-refactoring. mrsmith would be a valid candidate to fill in the l3-refactoring work.15:39
SwamiAlso I can help on the services split vpnaas with pcm.15:40
Swamidvr vlan patch is also progressing. I think vivek is posting patches upstream.15:40
SwamiThat's all I have from the dvr side.15:40
pc_mSwami: super. Can use help with reviews that are out right now.15:41
carl_baldwinmrsmith: mlavalle and I will start moving router functionality out to router.py today.  We also need to create a dvr_router.py with a class that sub-classes the router class.15:41
Swamipc_m: sure I will start reviewing the patches that are out there.15:41
carl_baldwinSwami: I agree.15:41
carl_baldwinmrsmith: Do you want to create the dvr_router.py?15:41
mrsmithcarl_baldwin: is there a patch for the router.py work?15:41
carl_baldwinmrsmith: Coming very soon.15:42
mrsmithsure - I can create dvr_router.py15:42
mrsmithok15:42
Swamisorry folks I need to drop off. I will catch up with the logs.15:42
carl_baldwinFor now, we can start by creating a very small class that sub-classes the router15:42
carl_baldwinSwami: Thanks.15:42
carl_baldwinAs the router class is fleshed out with more methods, there will be dvr only functionality which can be moved to the sub-class.15:43
mrsmithsounds good15:43
carl_baldwinmrsmith: I imagine the same could be done with HA.15:43
carl_baldwinamuller may be able to work with you on that.15:43
Rajeevgreat, I am focussing on plugin side HA for now, but help out where I can15:44
carl_baldwinRajeev: thanks.15:44
*** markmcclain has joined #openstack-meeting-315:45
*** shakamunyi has joined #openstack-meeting-315:45
*** gholler has joined #openstack-meeting-315:45
carl_baldwinAnything else?15:45
carl_baldwinKeep on eye on the dvr tempest job stability.  Looks like it may be starting to diverge further today.15:46
carl_baldwinThe link to the graph is too large for me to want to paste it here.  But, it is link from the L3 subteam page.15:46
*** Swami has quit IRC15:47
mrsmithwe need more tests15:47
carl_baldwinmrsmith: Yes, we do.  We also need to review the current tests proposed.15:48
*** MaxV has quit IRC15:48
carl_baldwin#action carl_baldwin will review https://review.openstack.org/#/c/138632/15:49
carl_baldwin#topic Open Discussion15:49
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:49
carl_baldwinAnything I’ve missed?15:49
*** tidwellr1 has left #openstack-meeting-315:50
Rajeevcarl_baldwin: you may have touched this earlier, for the l3_agent refactor new non-refactor checkins are on hold for now15:51
carl_baldwinRajeev: Yes, I sent a message to the mailing. list.15:51
Rajeevcarl_baldwin: thanks, fair to expect a similar message when done ?15:52
carl_baldwinRajeev: I hope the heavy lifting can be done in a couple of weeks.  I will send a similar message when it is at a more stable point.15:52
RajeevYes, that will be very helpful15:53
carl_baldwinThanks, everyone.  I’ve got a flight to go board.15:53
Rajeevhave a safe trip!15:54
carl_baldwin#endmeeting15:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:54
openstackMeeting ended Thu Dec 11 15:54:14 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-12-11-15.00.html15:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-12-11-15.00.txt15:54
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-12-11-15.00.log.html15:54
carl_baldwinRajeev: Thanks.15:54
johnbelamarichave a safe flight15:54
*** johnbelamaric has left #openstack-meeting-315:54
yamamoto_bye15:54
pc_mbye. I'm flying out too, in a few hours.15:55
ChuckCbye15:55
*** pc_m has left #openstack-meeting-315:55
*** mrsmith has quit IRC15:55
*** etoews has quit IRC15:55
carl_baldwinyamamoto_: ChuckC: see you soon.15:55
*** carl_baldwin has quit IRC15:55
*** emagana has joined #openstack-meeting-315:57
*** kaufer has joined #openstack-meeting-315:59
*** Rajeev has quit IRC16:00
*** MaxV has joined #openstack-meeting-316:00
*** marun has joined #openstack-meeting-316:06
*** shakamunyi has quit IRC16:12
*** Jean-Brice has quit IRC16:12
*** jcoufal_ has quit IRC16:14
*** flwang has quit IRC16:20
*** sergef has joined #openstack-meeting-316:20
*** pballand has joined #openstack-meeting-316:21
*** banix has joined #openstack-meeting-316:22
*** armax has joined #openstack-meeting-316:23
*** etoews has joined #openstack-meeting-316:28
*** banix has quit IRC16:28
*** matrohon has quit IRC16:31
*** banix has joined #openstack-meeting-316:34
*** salv-orlando has joined #openstack-meeting-316:35
*** mateuszb_ has quit IRC16:36
*** iovadia has joined #openstack-meeting-316:37
*** iovadia has quit IRC16:37
*** lazy_prince is now known as killer_prince16:39
*** etoews has quit IRC16:40
*** salv-orlando has quit IRC16:41
*** sunnyr has joined #openstack-meeting-316:41
*** sunnyr has quit IRC16:42
*** salv-orlando has joined #openstack-meeting-316:43
*** banix has quit IRC16:45
*** dboik has quit IRC16:45
*** banix has joined #openstack-meeting-316:46
*** amotoki has quit IRC16:46
*** david-lyle_afk is now known as david-lyle16:46
*** andymaier has quit IRC16:48
*** tnovacik has quit IRC16:50
*** dboik has joined #openstack-meeting-316:53
*** markmcclain has quit IRC16:55
*** shakamunyi has joined #openstack-meeting-316:59
*** mageshgv has joined #openstack-meeting-316:59
*** SumitNaiksatam has joined #openstack-meeting-317:02
*** kashyap has left #openstack-meeting-317:03
*** sunnyr has joined #openstack-meeting-317:03
*** evgenyf has quit IRC17:05
*** bpokorny has joined #openstack-meeting-317:08
*** reed has joined #openstack-meeting-317:10
*** dtroyer has joined #openstack-meeting-317:13
*** wdutch has quit IRC17:13
*** banix has quit IRC17:14
*** salv-orlando has quit IRC17:18
*** salv-orlando has joined #openstack-meeting-317:19
*** Piet has joined #openstack-meeting-317:20
*** salv-orlando has quit IRC17:24
*** safchain has quit IRC17:25
*** thatsdone has joined #openstack-meeting-317:26
*** dboik has quit IRC17:26
*** etoews has joined #openstack-meeting-317:29
*** alexpilotti has joined #openstack-meeting-317:33
*** alexpilotti has quit IRC17:34
*** VW__ has joined #openstack-meeting-317:34
*** alexpilotti has joined #openstack-meeting-317:34
*** yamamoto_ has quit IRC17:36
*** baoli has quit IRC17:37
*** VW__ has quit IRC17:37
*** VW has quit IRC17:38
*** VW__ has joined #openstack-meeting-317:38
*** etoews has quit IRC17:38
*** cbader has joined #openstack-meeting-317:40
*** tnovacik has joined #openstack-meeting-317:43
*** baoli has joined #openstack-meeting-317:44
*** thatsdone has quit IRC17:49
*** crobertsrh has joined #openstack-meeting-317:51
*** crobertsrh has left #openstack-meeting-317:51
*** emagana has quit IRC17:54
*** LouisF has joined #openstack-meeting-317:54
*** clu_ has joined #openstack-meeting-317:54
*** banix has joined #openstack-meeting-317:55
*** ivar-lazzaro has joined #openstack-meeting-317:56
*** sunnyr has quit IRC17:58
*** dboik has joined #openstack-meeting-317:59
SumitNaiksatamivar-lazzaro: igordcard banix: hi18:00
ivar-lazzaroyo18:01
banixSumitNaiksatam: hi18:01
SumitNaiksatamperhaps lower attendance today18:01
SumitNaiksatamlets keep it short in that case18:01
SumitNaiksatam#startmeeting networking_policy18:01
openstackMeeting started Thu Dec 11 18:01:47 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: networking_policy)"18:01
openstackThe meeting name has been set to 'networking_policy'18:01
SumitNaiksatam#info agneda https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy#Dec_11th.2C_201418:02
SumitNaiksatam#topic Bugs18:02
*** openstack changes topic to "Bugs (Meeting topic: networking_policy)"18:02
SumitNaiksatamwe have one critical18:02
SumitNaiksatam#link https://bugs.launchpad.net/group-based-policy/+bug/139772118:02
*** hemanthravi has joined #openstack-meeting-318:02
*** hinnant_ has joined #openstack-meeting-318:02
SumitNaiksatamivar-lazzaro: thats on your plate18:02
SumitNaiksatamhemanthravi: hi18:03
*** Youcef has joined #openstack-meeting-318:03
SumitNaiksatamivar-lazzaro: i know you are swamped with other stuff18:03
hemanthravihi18:03
SumitNaiksatamYoucef: hi!18:03
LouisFhi18:03
SumitNaiksatamLouisF: hi!18:03
SumitNaiksatamis mageshgv here?18:03
ivar-lazzaroSumitNaiksatam: this is actually solved by https://review.openstack.org/#/c/140201/18:03
mageshgvSumitNaiksatam:hi18:04
*** sandr8 has quit IRC18:04
ivar-lazzaroSumitNaiksatam: not sure why the lp isn't updated18:04
SumitNaiksatamivar-lazzaro: awesome18:04
SumitNaiksatammageshgv: great thanks for joining18:04
SumitNaiksatamivar-lazzaro: i think you it might just a need some teaking in the commit message18:04
SumitNaiksatammageshgv: you seem to be making good progress with the ton of “high” priority bugs on your plate18:05
SumitNaiksatammageshgv: any blockers for you at this point?18:05
mageshgvSumitNaiksatam: yes, making good progress, no blockers :)18:06
SumitNaiksatammageshgv: great!18:06
*** MaxV has quit IRC18:06
SumitNaiksatamivar-lazzaro: i did not notice, you add a second critical yesterday: #link https://bugs.launchpad.net/group-based-policy/+bug/140134718:06
SumitNaiksatamits a critical if there is not workaround18:07
ivar-lazzaroyes, that one also fixed18:07
SumitNaiksatambut anyway you have the fix18:07
ivar-lazzarothere is not18:07
ivar-lazzaroonce the port is deleted the PT leaks forever18:07
SumitNaiksatamminor pep8 issue18:07
SumitNaiksatamivar-lazzaro: okay got it18:07
SumitNaiksatamivar-lazzaro: i will track this as soon as you fix the pep818:08
SumitNaiksatam#topic Features merged in the last week18:08
*** openstack changes topic to "Features merged in the last week (Meeting topic: networking_policy)"18:08
SumitNaiksatamResources sharing (with shared attributed) : #link https://review.openstack.org/#/c/134692/18:08
SumitNaiksatamthis helps us to enable a bunch of use cases, most importantly, external connectivity (which is in review right now)18:09
SumitNaiksatamExtensions loading from drivers: #link https://review.openstack.org/#/c/138249/18:09
SumitNaiksatambanix: this ^^^ should make you happy :-)18:10
banixSumitNaiksatam: that’s right. thanks.18:10
SumitNaiksatamwith the above change the GBP model becomes extensible for individual drivers if they decide to do so18:10
SumitNaiksatamdecide -> choose18:11
SumitNaiksatamLouisF: perhaps you were also looking for the above change18:11
SumitNaiksatamunfortunately it has landed a little late in the cycle18:11
SumitNaiksatambut it is there, so we can start planning on how we can use it18:11
SumitNaiksatamthanks rkukura for that18:11
LouisFSumitNaiksatam: yes18:11
igordcardSumitNaiksatam, hi18:12
SumitNaiksatamPolicy Rule Updates: #link https://review.openstack.org/13833818:12
SumitNaiksatamthanks to s3wong for that18:12
SumitNaiksatamigordcard: hi, go ahead18:12
*** s3wong has joined #openstack-meeting-318:12
SumitNaiksatams3wong: i just finished thanking you!18:13
s3wongsorry, late18:13
SumitNaiksatamnp18:13
s3wongbad weather to get to office18:13
SumitNaiksatamyeah, its pretty out there18:13
SumitNaiksatamapparently parts of SF dont have power anymore18:13
*** sergef has quit IRC18:13
SumitNaiksatamjuice up your laptops!! :-P18:14
s3wongwould have been a good excuse to leave office if it happens here too :-)18:14
banixdid the temp drop below 50 for you guys? ;)18:14
SumitNaiksatams3wong: :-)18:14
s3wongbanix: actually, I don't think so, I think we are still @ around 60 :-)18:14
SumitNaiksatambanix: okay okay…not as bad as guys18:14
SumitNaiksatambanix: but we at least have something to whine about now :-P18:14
s3wongbanix: it is freezing out here :-)18:14
SumitNaiksatams3wong: lol18:15
SumitNaiksatamokay so those were the three main features in the last week18:15
SumitNaiksatamany questions on those?18:15
SumitNaiksatam#topic Pending reviews (features)18:16
*** openstack changes topic to "Pending reviews (features) (Meeting topic: networking_policy)"18:16
SumitNaiksatamExternal connectivity #link https://review.openstack.org/#/q/status:open+project:stackforge/group-based-policy+branch:master+topic:bp/external-connectivity,n,z18:16
SumitNaiksatamoops18:16
SumitNaiksatamwell may be it was the right link18:16
SumitNaiksatamivar-lazzaro is at it again! ;-)18:16
SumitNaiksatamon a more serious note, this is great work in a short period of time18:17
mageshgvSumitNaiksatam: the link doesnt show any open patch18:17
SumitNaiksatammageshgv: ooops18:17
ivar-lazzaroI've given some manual testing to the patches yesterday, using implicit shared default ES18:17
SumitNaiksatamivar-lazzaro: okay18:18
SumitNaiksatamperhaps ivar-lazzaro changed the topic on those patches18:18
ivar-lazzaroeverything went fine for very simple cases, I invite you all to give a try to find any bug asap :)18:18
*** alexsyip has joined #openstack-meeting-318:18
SumitNaiksatamso starting with this patch: #link https://review.openstack.org/#/c/137267/18:18
ivar-lazzaroyeah now something different is in the topic field, sorry about that18:18
SumitNaiksatamivar-lazzaro: it will be instructive for the team if you can create a short wiki page, and outline how you have tested this for the neutron mapping18:19
SumitNaiksatamivar-lazzaro: i can create a landing page for you and you can fill it up per your convenience18:19
ivar-lazzaroSumitNaiksatam: sure, I'll try to get some time to do so18:19
SumitNaiksatamivar-lazzaro: thanks18:19
SumitNaiksatamthis is critical functionality for this release, so please please review if you get a chance (and also to try it out)18:20
SumitNaiksatamany questions for ivar-lazzaro on this?18:20
SumitNaiksatamdoes everyone understand what ivar-lazzaro is trying to do here?18:20
SumitNaiksatamivar-lazzaro: perhaps a quick one line summary to level set?18:21
SumitNaiksatamsorry to put you on the spot18:21
ivar-lazzaronp18:21
LouisFquick summary?18:21
ivar-lazzaro3 new objects have been added to the API: External Segment (ES), External Policy (EP), Nat Pool (NP)18:21
ivar-lazzarotogether, they describe how a given L3_Policy can connect to the external world18:22
ivar-lazzaroThe ES physically represents the external network/subnet18:22
ivar-lazzarothe EP is basically an External EPG, that can provide and consume contracts on behalf of a given portion of the external world18:22
SumitNaiksatamivar-lazzaro: okay18:22
ivar-lazzaroand the Nat Pool (not used in this iteration) represents the floating IPs pool18:23
SumitNaiksatamivar-lazzaro: so EP is a “special” EPG, right?18:23
ivar-lazzaroyes18:23
SumitNaiksatamivar-lazzaro: how does it differ from EPG?18:23
ivar-lazzaroIt exists on a given External Segment18:23
SumitNaiksatamerrr…PTG18:23
ivar-lazzaroand can provide and consume contracts18:23
ivar-lazzaro(PRS)18:23
ivar-lazzarothe difference is that it doesn't have endpoints18:24
SumitNaiksatamivar-lazzaro: ah there you go18:24
SumitNaiksatamivar-lazzaro: also ES and EP can be CUD only by admin?18:24
ivar-lazzaroIt defines the policy for the external segment, in particular for its routes18:24
SumitNaiksatamivar-lazzaro: i guess also NAT pool18:24
ivar-lazzarothat's correct. Everything of course depends on the policy.json18:25
ivar-lazzaroso the role access can vary dynamically18:25
ivar-lazzarobut yeah, that's the typical use case18:25
ivar-lazzaroany questions?18:26
SumitNaiksatamivar-lazzaro: and in the context of the neutron mapping, what we should be looking for is whether the external network gets created properly18:26
LouisFivar-lazzaro: how is the ES defined? what attributes does it have?18:26
SumitNaiksatamivar-lazzaro: and the router’s external gateway is set properly?18:26
ivar-lazzaroyes, and also shared properly18:27
mageshgvivar-lazzaro: one quick question. Does the external segment and external policy help in modelling only the external network segment the openstack uses or does it also have a way to represent anything outside the cloud18:27
ivar-lazzaroLouisF: #link https://github.com/stackforge/group-based-policy-specs/blob/master/specs/juno/external-connectivity.rst :)18:27
LouisFivar-lazzaro: thx18:27
ivar-lazzaromageshgv: in this first iteration, especially for the RMD, it's tied on what Neutron can represent18:28
mageshgvivar-lazzaro: alright18:28
ivar-lazzaromageshgv: however, the idea is to make the ES very very simple, so that each driver can extend it18:29
ivar-lazzaromageshgv: in order to represent the outside of the cloud however they need to18:29
ivar-lazzaromageshgv: in a way the ES is meant to be extended in order to be used properly. The plan is to add more core attributes once we realize what can be defined as "common" requirement for the external world18:30
*** markmcclain has joined #openstack-meeting-318:30
SumitNaiksatamivar-lazzaro: can you provide a little more context on what “more” core attributes you anticipate18:31
mageshgvivar-lazzaro: thanks. that helps. wanted to make sure we have that in mind :)18:31
SumitNaiksatamtrying to get a feel for which direction we are going18:31
ivar-lazzaroso far the core attributes are *cidr* and *port_address_translation*18:31
ivar-lazzaroI feel that each driver will have to describe every L2 related attribute18:32
*** jcoufal has joined #openstack-meeting-318:32
ivar-lazzarolike encap, physnet (in Neutron's terminology) or encap_value18:32
ivar-lazzarohowever it's not clear now what is the common denominator18:32
SumitNaiksatamivar-lazzaro: okay makes sense18:33
SumitNaiksatamivar-lazzaro: i was just going to say that as long as you (as a vendor) were already mapping to the physical network in Neutron, you should be able to do it here as well18:33
SumitNaiksatamany more questions on this?18:34
SumitNaiksatammageshgv: you are working on (1) hierarchical PRS (2) Policy Action updates18:35
SumitNaiksatamSupport Hierarchial Policy Rule Set for Redirects: #link https://review.openstack.org/14028618:36
mageshgvSumitNaiksatam: yes, (1) is ready for initial review, (2) is completed18:36
SumitNaiksatamHandle Policy Action value update(Service Chain Spec update) #link https://review.openstack.org/13833818:36
*** yamamoto has joined #openstack-meeting-318:37
SumitNaiksatammageshgv: thats awesome, having a tough time keeping pace with the flurry of patches!18:37
SumitNaiksatamany questions for mageshgv on those two?18:37
SumitNaiksatam#topic New Policy drivers18:38
*** openstack changes topic to "New Policy drivers (Meeting topic: networking_policy)"18:38
*** Piet has quit IRC18:38
SumitNaiksatamODL: #link https://review.openstack.org/#/c/138556/18:38
SumitNaiksatamthis is coming along nicely18:38
SumitNaiksatami think this one is the first patch in the series: #link https://review.openstack.org/#/c/138235/318:39
SumitNaiksatamwe have yi and yapeng working on the OpenStack side, and keith and thomas bachman working on the ODL side18:39
s3wongSumitNaiksatam: finally out of WIP mode?18:39
SumitNaiksatams3wong: first one is, second patch is not18:39
SumitNaiksatams3wong: but the testing is going well18:40
*** markmcclain has quit IRC18:40
s3wongSumitNaiksatam: OK18:40
SumitNaiksatami mean there is end-to-end intergration tested18:40
SumitNaiksatamwith respect to EPs being registered on the ODL side18:40
SumitNaiksatamwe have not tested the datapath yet18:40
SumitNaiksatamLouisF: you probably work with yapeng?18:41
SumitNaiksatamis ronak here?18:41
s3wongSumitNaiksatam: I think yapeng and LouisF are in different BUs and different countries :-)18:41
*** yamamoto has quit IRC18:42
SumitNaiksatams3wong: yeah i know yapeng is in Canada18:42
SumitNaiksatam#topic Packaging18:42
*** openstack changes topic to "Packaging (Meeting topic: networking_policy)"18:42
SumitNaiksatamrkukura does not seem to be here (he is probably on his flight back from the neutron mid-summit)18:43
SumitNaiksatamthe update there is that this is proceeding well18:43
SumitNaiksatamrkukura’s patch to fedora was approved for the GBP server side package18:43
SumitNaiksatamso its a matter of now keeping it updated with the release version18:43
LouisFSumitNaiksatam: yes18:43
SumitNaiksatami belive he has this done for the client as well18:44
SumitNaiksatamand the heat and horizon packages are in the works18:44
SumitNaiksatam#topic Open Discussion18:44
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:44
SumitNaiksatamsorry we have been skipping the discussion on the kilo specs18:44
SumitNaiksatambut we have too many things on our plate to finish by dec 19th, hence the delay on that discussion18:45
SumitNaiksatamwe should be able to focus our discussion on those once we reach the release point18:45
*** sarob has joined #openstack-meeting-318:45
SumitNaiksatamLouisF: thanks for being patient on that, and apologies for not reviewing your specs18:45
SumitNaiksatamanything else we want to discuss today?18:46
SumitNaiksatambtw, the update on the Horizon front is that its shaping up well18:46
SumitNaiksatamthere is one critical issue with creating service chain specs18:46
SumitNaiksatam(and another regression on creating the policy classifier)18:47
SumitNaiksatambut other than that its mostly functional18:47
LouisFSumitNaiksatam: np18:47
SumitNaiksatamanything else?18:47
*** etoews has joined #openstack-meeting-318:48
SumitNaiksatamivar-lazzaro and mageshgv thanks for the herculean effort!18:48
SumitNaiksatamalrighty, !until next week18:48
SumitNaiksatamthanks for attending18:48
SumitNaiksatambye18:48
s3wongbye18:48
mageshgvbye18:48
banixbye18:48
ivar-lazzarothanks, bye!18:48
SumitNaiksatam#endmeeting18:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:49
openstackMeeting ended Thu Dec 11 18:49:00 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-12-11-18.01.html18:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-12-11-18.01.txt18:49
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-12-11-18.01.log.html18:49
banixwill try to pick up reviewing next week.18:49
*** kaufer has left #openstack-meeting-318:49
*** etoews_ has joined #openstack-meeting-318:54
*** etoews has quit IRC18:57
*** flwang has joined #openstack-meeting-318:59
*** markmcclain has joined #openstack-meeting-319:02
*** hemanthravi has quit IRC19:04
*** mageshgv has quit IRC19:04
*** SotK has quit IRC19:16
*** ivar-laz_ has joined #openstack-meeting-319:22
*** ivar-laz_ has quit IRC19:23
*** ivar-laz_ has joined #openstack-meeting-319:23
*** ivar-lazzaro has quit IRC19:26
*** ttrifonov is now known as zz_ttrifonov19:29
*** sunnyr has joined #openstack-meeting-319:29
*** banix has quit IRC19:44
*** LouisF has quit IRC19:50
*** carl_baldwin has joined #openstack-meeting-319:51
*** thangp has quit IRC19:51
*** baoli has quit IRC19:53
*** shwetaap1 has quit IRC20:02
*** matrohon has joined #openstack-meeting-320:04
*** sunnyr has quit IRC20:15
*** sunnyr has joined #openstack-meeting-320:17
*** cbader has quit IRC20:19
*** Sukhdev has joined #openstack-meeting-320:23
*** markmcclain has quit IRC20:25
*** mrda-away is now known as mrda20:28
*** SridharRamaswamy has joined #openstack-meeting-320:28
*** dtroyer has left #openstack-meeting-320:28
*** SridharRamaswamy has left #openstack-meeting-320:29
*** SridharRamaswamy has joined #openstack-meeting-320:30
*** thangp has joined #openstack-meeting-320:40
*** Piet has joined #openstack-meeting-320:41
*** jacalcat has joined #openstack-meeting-320:48
*** jacalcat has left #openstack-meeting-320:48
*** alexpilotti has quit IRC20:49
*** sunnyr has quit IRC20:49
*** reed has quit IRC20:52
*** SridharRamaswamy has quit IRC20:55
*** tnovacik has quit IRC21:01
*** carl_baldwin has quit IRC21:01
*** ChuckC has quit IRC21:02
*** carl_baldwin has joined #openstack-meeting-321:02
*** mrmartin has quit IRC21:03
*** s3wong has quit IRC21:06
*** vishwanathj has joined #openstack-meeting-321:06
*** baoli has joined #openstack-meeting-321:07
*** sunnyr has joined #openstack-meeting-321:07
*** s3wong has joined #openstack-meeting-321:08
*** carl_baldwin has quit IRC21:12
*** Longgeek has quit IRC21:17
*** baoli has quit IRC21:18
*** baoli has joined #openstack-meeting-321:19
*** sergef has joined #openstack-meeting-321:23
*** matrohon has quit IRC21:24
*** ChuckC has joined #openstack-meeting-321:25
*** MarkAtwood has joined #openstack-meeting-321:31
*** baoli has quit IRC21:38
*** baoli has joined #openstack-meeting-321:39
*** matrohon has joined #openstack-meeting-321:44
*** SridharRamaswamy has joined #openstack-meeting-321:44
*** Rockyg has joined #openstack-meeting-321:52
*** sergef has quit IRC21:52
*** vishwanathj has quit IRC21:55
*** vishwanathj has joined #openstack-meeting-321:56
*** vishwanathj has quit IRC21:56
*** vishwanathj has joined #openstack-meeting-321:56
*** matrohon has quit IRC21:56
*** MaxV has joined #openstack-meeting-321:59
*** markmcclain has joined #openstack-meeting-322:02
*** sunnyr has quit IRC22:03
*** sunnyr has joined #openstack-meeting-322:11
*** reed has joined #openstack-meeting-322:14
*** s3wong_ has joined #openstack-meeting-322:16
*** s3wong has quit IRC22:16
*** mattfarina has quit IRC22:17
*** ivar-laz_ has quit IRC22:18
*** gholler has quit IRC22:21
*** ivar-lazzaro has joined #openstack-meeting-322:22
*** Sukhdev has quit IRC22:23
*** Piet has quit IRC22:29
*** jrist has quit IRC22:29
*** jrist has joined #openstack-meeting-322:30
*** ChuckC has quit IRC22:32
*** sunnyr has quit IRC22:33
*** sunnyr has joined #openstack-meeting-322:35
*** SridharRamaswamy has quit IRC22:35
*** yamamoto has joined #openstack-meeting-322:40
*** s3wong has joined #openstack-meeting-322:40
*** s3wong_ has quit IRC22:41
*** yamamoto has quit IRC22:45
*** peristeri has quit IRC22:47
*** MarkAtwood has quit IRC22:48
*** markmcclain has quit IRC22:50
*** MarkAtwood has joined #openstack-meeting-322:52
*** thomasem has quit IRC22:53
*** baoli has quit IRC22:53
*** baoli has joined #openstack-meeting-322:54
*** etoews_ has quit IRC23:01
*** jcoufal has quit IRC23:02
*** MarkAtwood has quit IRC23:03
*** MarkAtwood has joined #openstack-meeting-323:05
*** thangp has quit IRC23:06
*** vishwanathj has quit IRC23:13
*** VW__ has quit IRC23:14
*** ChuckC has joined #openstack-meeting-323:15
*** Rockyg has quit IRC23:16
*** sunnyr has quit IRC23:26
*** sunnyr has joined #openstack-meeting-323:36
*** sarob has quit IRC23:41
*** MaxV has quit IRC23:45
*** MaxV has joined #openstack-meeting-323:45
*** shakamunyi has quit IRC23:49
*** MaxV has quit IRC23:50
*** igordcard has quit IRC23:57
*** sarob has joined #openstack-meeting-323:58

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