Thursday, 2015-04-30

elmikoanyone here for api-wg?00:00
miguelgrinbergelmiko: I'm here00:00
elmikomiguelgrinberg: should we wait to see if a few more show up before starting?00:01
stevelleo/00:01
elmikook, cool00:01
elmiko#startmeeting api-wg00:01
openstackMeeting started Thu Apr 30 00:01:30 2015 UTC and is due to finish in 60 minutes.  The chair is elmiko. Information about MeetBot at http://wiki.debian.org/MeetBot.00:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.00:01
*** openstack changes topic to " (Meeting topic: api-wg)"00:01
openstackThe meeting name has been set to 'api_wg'00:01
elmiko#link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda00:02
elmiko#topic previous meeting action items00:02
*** openstack changes topic to "previous meeting action items (Meeting topic: api-wg)"00:02
elmiko#link http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-04-23-16.00.html00:03
miguelgrinbergelmiko: looks like you are the only one with an action item00:03
elmikoyea00:03
miguelgrinbergthe only one present00:03
elmikoetoews, handled his00:03
elmikoi'm still working on the guidelines change, trying to figure out what would be best for inclusion00:03
sigmavirus24o/00:04
sigmavirus24(sorry I'm late)00:04
elmikoi started trying to make the "Change Guidelines" fit the guidelines template, but i'm not totally sure if that's correct00:04
elmikosigmavirus24: no worries =)00:04
elmikoi'll put it up for review and we'll see what folks think00:04
sigmavirus24cool00:05
elmiko#topic guidelines00:05
*** openstack changes topic to "guidelines (Meeting topic: api-wg)"00:05
elmiko#link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z00:05
elmikoi think everything is pretty much under review at this point,00:05
elmikodoes anyone want to mention something specific?00:06
stevellenothing here00:06
miguelgrinbergWhen are we lifting the freeze on proposals?00:06
elmikooh, plus we're frozen on miguelgrinberg's proposals00:06
elmikomiguelgrinberg: i thought once the kilo release had ended00:07
sigmavirus24yeah we didn't discuss when we would unfreeze them00:07
miguelgrinbergKilo releases tomorrow right?00:07
sigmavirus24we just discussed the idea that PTLs are kind of super busy now and CPLs are probably busy too00:07
elmikoand i think etoews is out until next week00:07
elmikoyea00:07
elmiko#link https://wiki.openstack.org/wiki/Kilo_Release_Schedule00:08
elmikotomorrow is the release, maybe we should ping etoews through email00:08
sigmavirus24Perhaps we'll never unfreeze them. *laughs maniacally*00:08
miguelgrinbergGlad to see a spec on filtering is in the works00:08
elmikolol00:08
elmikoyea, very cool about filtering. i had questions about the best ways to implement this00:09
miguelgrinbergHeat has a couple of specs for Liberty where there is filtering, so it's good that we put something together00:10
elmikosahara is discussing a v2 api and the guidelines have been very helpful in finding problem areas in the current impl00:10
stevelletestimonails!00:11
elmikohehe =)00:11
stevelleand hopefully fewer typos than me00:11
sigmavirus24elmiko: we're going to do a google hangouts podcast series now00:11
miguelgrinbergyes, also the nova people reached out for help with tagging00:11
sigmavirus24And you'll be the guest00:11
sigmavirus24jaypipes: miguelgrinberg and I will grill you on how the API-WG has changed your life =P00:12
elmikoawesome... ;)00:12
elmikoeven though it's not merged yet, the tagging guideline has helped.00:12
miguelgrinbergyes, heat already implemented it, and now nova will00:13
elmikonice00:13
elmikoanything else for guidelines?00:13
jaypipeslol00:14
elmiko#topic APIImpact00:14
*** openstack changes topic to "APIImpact (Meeting topic: api-wg)"00:14
* sigmavirus24 half-heartedly apologizes for being so punchy tonight00:14
elmiko#link https://review.openstack.org/#/q/status:open+AND+(message:ApiImpact+OR+message:APIImpact),n,z00:14
stevelleapology half-heartedly accepted?00:14
elmikoany reviews we should look at?00:14
elmikolol00:14
jaypipessigmavirus24: did you see my callout to you, miguelgrinberg and etoews in a podcast recently?00:15
miguelgrinbergjaypipes: I did! total surprise to hear my name!00:15
sigmavirus24jaypipes: my coworker caught it and alerted us00:15
jaypipesheh00:15
elmikojaypipes: is that the bootstrapping hour?00:15
jaypipeselmiko: no, it was a podcast with Jeff DIckey from redapt and Niki Acosta from Cisco00:16
*** Shamail has quit IRC00:16
elmikooh, nice00:16
jaypipeselmiko: I need to get with sean about the bootstrapping hour continuing..00:16
jaypipesthx for the reminder :)00:16
elmikojaypipes: +1, i've really enjoyed it so far =)00:16
jaypipescool!00:16
jaypipesso, guys, I have a bit of API WG news...00:16
elmiko#topic News00:17
jaypipessorry for being late to this meeting, first of all00:17
*** banix has quit IRC00:17
*** openstack changes topic to "News (Meeting topic: api-wg)"00:17
jaypipesso, I've been chatting with johnthetubaguy, kenichi, mgilliard and alex_xu about a Nova contributor being a liaison to the API WG00:17
elmikonice00:17
jaypipesLooks like alex_xu and mgilliard will be our liaisons.00:18
jaypipesI suggested, however, that instead of just showing up to meetings, that they have specific tasks.00:18
jaypipesnamely, the following. one sec, grabbing copy.00:18
*** sarob_ has quit IRC00:18
jaypipessorry for the paste, but here it is:00:19
jaypipes1) Assign someone (or some two) people to monitor the active patch queue in00:19
jaypipesnova (and nova-specs) and look out for any patch that adds or changes the00:19
jaypipesREST API00:19
jaypipes2) For each patch collected in #1, determine if the constructs used in the00:19
jaypipespatch (or proposed spec) match the guidance currently laid out in the API00:19
jaypipesworking group repo's guidance documents.00:19
jaypipes3) If the patch does NOT match the guidance from the API working group, do a00:19
jaypipescode review on the patch pointing to the guidance from the API working00:19
jaypipesgroup, and ask the author to align with that guidance. Include in your00:19
jaypipesresearch patches to the API working group that may actually be in review and00:19
jaypipesnot merged. (An example of this recently occurred with Sergey Nikitin's00:19
jaypipesre-proposed instance tagging spec: https://review.openstack.org/#/c/177112/.00:19
jaypipesSee Ryan Brown's reference to an in-progress API working group guidance on00:19
jaypipestagging)00:19
jaypipes4) If there is NO guidance in the API working group repo for a particular00:19
jaypipesproposed API change or addition, create a proposed patch to the API working00:19
jaypipesgroup with guidance that clarifies the missing functionality that is00:19
jaypipesintroduced in the new Nova patch or spec patch, and bring the proposed00:19
jaypipesguidance to the attention of the API working group.00:19
elmikovery nice, i especially like #400:20
jaypipesif you guys feel the above is OK, perhaps it's worth codifying it after a test run in Nova and recmomending these steps for other teams to take with their liaisons to the API WG?00:20
elmiko+100:20
stevelleseems like a good place to work from00:21
miguelgrinbergvery good00:21
elmikoat the least it provides a solid guide for how other projects can get involved with the wg00:21
jaypipesOK, well, we'll give it a shot over in Nova-land and see if it works out well.00:21
elmikothanks for bringing it up00:21
*** baoli has joined #openstack-meeting-300:21
jaypipeslemme know if you have any suggestions on improving the steps for liaisons to take. happy to get feedback on it.00:22
jaypipesand sorry for dumping paste into IRC...00:22
elmikono worries00:23
elmiko#topic open discussion00:23
*** openstack changes topic to "open discussion (Meeting topic: api-wg)"00:23
elmikoanything else folks wanna talk about?00:23
miguelgrinbergjaypipes: my only suggestion for #4 is that alternatively the liason can alert an active member of the api-wg to write a guideline00:23
miguelgrinbergAt least in heat-land I find that some people are not interested in proposing something to api-wg00:24
miguelgrinbergat least they should get one of us to do it for them00:24
elmikodo they have any reason for why that might be?00:24
miguelgrinbergnothing special, lack of time I guess?00:24
elmikoyea, i can feel that00:25
miguelgrinbergI was going to write something on filtering due to heat having a couple of specs in that area, but ryanb beat me to it00:26
jaypipesmiguelgrinberg: cool, good suggestion, thank you!00:26
jaypipesHey, so are we ready to merge the 3 guidelines that Everett had put on hold?00:28
miguelgrinbergwe were wondering when is the freeze is going to end00:28
elmikoit seemed like they had good acceptance00:28
*** banix has joined #openstack-meeting-300:29
jaypipesYes, I was wondering when the freeze would end as well.00:29
elmikomaybe we should wait till next week to give the PTLs a chance to review after the kilo release?00:29
jaypipesI must have missed an email where etoews mentioned that.00:29
elmikoit has been a topic of some mystery00:29
jaypipessure, that's cool by me. no rush.00:29
elmikoi think the idea was that as we reach the milestone releases we should impose a freeze on guidelines to give the PTLs a chance to breathe without having to worry about reviewing new guidelines00:30
elmiko*i think*00:30
miguelgrinbergyes, that was the idea00:31
elmikomaybe next meeting we'll revisit?00:31
*** annegent_ has joined #openstack-meeting-300:31
elmikoi'm not sure who has +2 aside from etoews00:32
sigmavirus24jaypipes00:32
sigmavirus24cyeoh did00:32
sigmavirus24=(00:32
elmiko=(00:32
annegent_aww sad time to join :(00:32
annegent_sorry I'm late00:33
elmikono prob00:33
elmikoannegent_: did you have any topics to discuss?00:33
* annegent_ reads the log to catch up00:33
annegent_oo I like the nova liaison ideas jaypipes00:34
elmikocool00:34
annegent_yes I had API Reference information: specification for reinvention underway00:35
sigmavirus24=D00:35
annegent_you following https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda?00:35
elmikosorta, we ran through those topics so i just kinda freestyled00:35
elmiko;)00:35
annegent_Hee00:36
annegent_ok if I can go I'll go!00:36
elmikoplease00:36
annegent_Okay, so I really want to be rid of WADL00:36
elmiko\o/00:36
annegent_and want to figure out how to do the work00:36
jaypipes++00:36
annegent_so I've written a spec00:36
annegent_but it's still even wishy washy about where the work should live -- in the docs team or in the API WG? Discuss.00:37
annegent_#link https://review.openstack.org/#/c/177934/00:37
elmikoi had question when reading that,00:37
annegent_Tom Fifield has a summary post on openstack-docs about automation as well that I'll link to00:37
elmikowhat happens to things like the keystone api reference they have in their specs repo?00:37
elmikoi always found that to be a nice place for the upstream api refs00:38
annegent_elmiko: this is for API Reference, that is their "narrative" form documents00:38
elmikoahh, ok00:38
annegent_elmiko: yeah there's a difference, but it may also just need to live in specs, that's up for discussion00:38
annegent_there's 915 calls just in the first 8 or so services that became OpenStack00:39
elmikowould be interesting if each project owned their api-ref in the specs repo, then the "official" api-ref site did some sort of aggregation00:39
annegent_that doesn't even count the additional 10? 12? services00:39
annegent_#link http://lists.openstack.org/pipermail/openstack-docs/2015-April/006502.html00:39
annegent_so that's what I want to hear from you all00:39
annegent_automation okay?00:39
annegent_specs repos? <project> repos and scrape from their code?00:39
elmikosomething like that00:40
elmikoand i really liked the swagger based ideas, fwiw00:40
annegent_is automation awful when you need to provide real user info though?00:40
annegent_and do we de-scope to only infrastructure APIs in order to bring the quality level up?00:40
annegent_or will each team bring the quality level up?00:40
elmikoi think you had a good point about the errors that can creep in from automated docs00:40
*** s3wong has quit IRC00:40
sigmavirus24So... I'll say this: JSON Schema can be a nightmare. I'm not an expert but I'm not a novice either. If you're going to go with JSON Schema you'll need a validator with good ways of testing things00:41
annegent_elmiko: I always think it's a crappier user experience, but Tom does have good points00:41
annegent_sigmavirus24: yeah I worry about finding expertise in community sourcing, it's really really hard already00:41
elmikosigmavirus24: are you talking about the validation on a swagger schema?00:41
sigmavirus24elmiko: I'm talking about the RST + JSON Schema proposal at the end00:41
annegent_Diane Fleming has single handedly done the maintenance and she's unbelieveably fast and it's still not enough00:42
annegent_honestly you need JSON Schema for swagger too00:42
sigmavirus24So I'm comfortable with JSON Schema, but I'm no expert00:42
annegent_if you want to validate you need json schema from what I can see00:42
elmikoyea, that's why i asked. and yes Diane is excellent!00:42
annegent_she closed something like 80 doc bugs this release and we're still just barely under 170 API doc bugs00:42
elmikowow00:43
annegent_so the situation needs fixing00:43
annegent_but how?00:43
sigmavirus24yeah that's tough00:43
elmikoi kinda like the idea of automating the generation of a skeleton json(swagger) output, then each team working to fill in the missing parts00:44
annegent_I'm fine with trying automation. 1. Do you think all teams will comply? 2. will it be a worse experience for consumers of the info?00:44
elmikoone issue with automation is that projects using pecan will need to add extra markup to their code00:45
annegent_(the ops/admin docs are over 550 doc bugs so there's that comparison which is a bit unfair, ha ha)00:45
annegent_so, for pecan we already have WADL automation00:45
annegent_I don't know if you know that00:45
elmikoi did not, although i started down the path of swagger automation for pecan00:45
annegent_but yeah there's only ceilometer using pecan?00:45
elmikobarbican uses pecan as well00:46
annegent_we don't enable flask, correct?00:46
annegent_Looking at this list00:46
annegent_#link https://github.com/swagger-api/swagger-spec#python00:46
*** mwagner_lap has quit IRC00:46
annegent_also what do yuo think about descoping to infra-only? non-starter?00:47
miguelgrinbergannegent_: that is not just flask, it is a REST extension for flask, but no project uses Flask that I know of00:47
elmikoi didn't test the flask based solutions, but it's much easier to generate the swagger from flask00:47
stevelleceilometer wanted to use flask but was directed to pecan as I understand00:47
annegent_miguelgrinberg: right, it's not "blessed" centrally00:47
annegent_right00:47
annegent_stevelle: right00:47
elmikomiguelgrinberg: sahara is using flask00:47
*** ivar-lazzaro has quit IRC00:47
annegent_Okay so what about only documenting Compute, Block Storage, Object Storage, Identity, Images APIs?00:48
annegent_no-go on de-scope?00:48
miguelgrinbergelmiko: oh, nice!00:48
elmikoi like the idea of every project documenting, but not sure how practical it will be00:48
annegent_elmiko: ah I hadn't realized that00:48
miguelgrinbergdo you think it'll be able to stay on flask or will it go the ceilo way?00:49
jaypipesyeah, I feel the same as elmiko.00:49
jaypipesI'm torn on this autogeneration stuff, frankly.00:49
annegent_miguelgrinberg: it's a free-for-all at this point00:49
annegent_jaypipes: go on :)00:49
elmikomiguelgrinberg: i think there is pressure for us to move to pecan, but i'm not sure how far we'll get00:49
jaypipesannegent_: If it can be shown that we can accurately autogenerate API docs from the code, then I'll play along. I havent' yet seen anything that can do it well though. :)00:50
annegent_jaypipes: right, to me, all automation is worser00:50
annegent_worser!00:50
elmikoi don't think we can fully rely on autogeneration, especially not if we want the level of detail that api-ref currently has00:50
annegent_I'm fascinated with autogenerating Swagger 2.000:50
stevelle+1 that00:50
elmikoyea, it's got some really cool features00:50
annegent_we do a nice job with the Config Ref already, as Tom points out00:50
stevelleas a start point it would save a ton of time to get a transition started00:51
jaypipesannegent_: well, no, automation in general is betterer. But I'm just wary. The opposite direction -- i.e. code generated from docs -- almost NEVER works, so I'm skeptical about it.00:51
elmikoi think it would be nice if we could provide advice on how to autogenerate then markup00:51
annegent_two things I haven't investigated to satisfaction with Swagger:00:51
stevellebut only if it worked00:51
annegent_1. how to display headers. Object Storage API has like 80 headers00:51
annegent_2. how to indicate array requirements in requests00:51
*** zhenguo has joined #openstack-meeting-300:51
jaypipesannegent_: #2 is certainly possible. #1, I don't know.00:51
elmikoyea, i don't remember how #1 work, but i *think* it's in there00:52
annegent_#link https://github.com/rackerlabs/wadl2swagger/issues/800:52
annegent_long read, but two teammates couldn't figure it out jaypipes00:52
annegent_this is all useful. Would you like to have a session on this at the Summit? I think I can find time00:52
annegent_I know docs has a slot for API docs specifically to discuss this spec.00:53
annegent_now, do we make it a docs spec, or an API WG guideline? Discuss.00:53
annegent_as in, "review all code patches to comply with this API WG doc guideline"00:53
annegent_would that work?00:53
*** alexsyip has quit IRC00:53
elmikoi see several references to headers in https://github.com/swagger-api/swagger-spec00:53
jaypipesannegent_: a docs spec.00:53
elmikoannegent_: i'd make time for a discussion at summit00:54
annegent_jaypipes: ok00:54
elmikoagreed with jaypipes, especially if it continues to be a doc site production for the html side of the api-ref00:54
annegent_#link http://rackerlabs.github.io/wadl2swagger/openstack.html00:55
jaypipesannegent_: verified in the 2.0 swagger spec, it has full support for HTTP headers in both request and response.00:55
annegent_but for whatever reason we don't have an Object Storage API swagger there00:55
annegent_so I need to figure out "whatever reason"00:55
annegent_Okay, I think that was all my questions.00:56
elmikowadl2swagger is a nice start, but imo we should ultimately help projects to autogen the base swagger00:56
annegent_#action please comment on the docs spec at https://review.openstack.org/#/c/177934/00:56
*** eghobo has quit IRC00:56
annegent_#action please reply on the openstack-docs mailing list thread here: http://lists.openstack.org/pipermail/openstack-docs/2015-April/006502.html about automation00:56
annegent_elmiko: agreed00:56
elmikothanks for bringing this up annegent_00:56
annegent_elmiko: thanks for letting me crash in late!00:57
annegent_:)00:57
elmikoalways =)00:57
elmikook, any other last minute notes?00:57
* sigmavirus24 has none00:58
miguelgrinbergnope00:58
elmikothanks for coming out everyone!00:58
elmiko#endmeeting00:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"00:58
openstackMeeting ended Thu Apr 30 00:58:41 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)00:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-04-30-00.01.html00:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-04-30-00.01.txt00:58
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-04-30-00.01.log.html00:58
annegent_Kilo release tomorrow! Yay! :)00:58
elmiko\o/00:58
sigmavirus24o/00:58
*** Rockyg has quit IRC00:58
*** banix has quit IRC00:59
sigmavirus24I'm nervously anticipating Kilo Glance00:59
elmikowhy nervous?01:00
*** annegent_ has quit IRC01:00
*** ivar-lazzaro has joined #openstack-meeting-301:02
*** ivar-lazzaro has quit IRC01:03
*** mwagner_lap has joined #openstack-meeting-301:03
*** Swami has quit IRC01:04
*** ivar-lazzaro has joined #openstack-meeting-301:05
*** ivar-lazzaro has quit IRC01:05
*** sigmavirus24 is now known as sigmavirus24_awa01:05
*** ivar-lazzaro has joined #openstack-meeting-301:06
*** bknudson has joined #openstack-meeting-301:09
*** stevemar has joined #openstack-meeting-301:11
*** markvoelker has joined #openstack-meeting-301:11
*** elmiko is now known as _elmiko01:12
*** baoli has quit IRC01:15
*** baoli has joined #openstack-meeting-301:16
*** sarob has quit IRC01:17
*** stanzgy has joined #openstack-meeting-301:32
*** alex_xu has quit IRC01:43
*** Networkn3rd has joined #openstack-meeting-301:45
*** SumitNaiksatam has joined #openstack-meeting-301:52
*** stevemar has quit IRC01:52
*** SumitNaiksatam has quit IRC02:03
*** baoli has quit IRC02:07
*** baoli has joined #openstack-meeting-302:07
*** bpokorny has quit IRC02:08
*** yamahata has quit IRC02:12
*** stevemar has joined #openstack-meeting-302:25
*** VW_ has joined #openstack-meeting-302:30
*** VW_ has quit IRC02:32
*** VW_ has joined #openstack-meeting-302:32
*** Networkn3rd has quit IRC02:36
*** stevemar has quit IRC02:38
*** yamahata has joined #openstack-meeting-302:43
*** ir2ivps7 has quit IRC02:48
*** stevemar has joined #openstack-meeting-302:48
*** ir2ivps7 has joined #openstack-meeting-302:48
*** btully has quit IRC02:49
*** baoli has quit IRC02:51
*** baoli has joined #openstack-meeting-302:52
*** baoli_ has joined #openstack-meeting-302:53
*** baoli has quit IRC02:53
*** stanzgy__ has joined #openstack-meeting-303:31
*** stanzgy has quit IRC03:34
*** fallenpegasus has joined #openstack-meeting-303:36
*** baoli_ has quit IRC03:36
*** SumitNaiksatam has joined #openstack-meeting-303:39
*** fallenpegasus has quit IRC03:43
*** fallenpegasus has joined #openstack-meeting-303:43
*** jckasper has joined #openstack-meeting-303:46
*** fallenpegasus has quit IRC03:48
*** bpokorny has joined #openstack-meeting-303:50
*** bpokorny has quit IRC03:52
*** bpokorny has joined #openstack-meeting-303:52
*** _elmiko has left #openstack-meeting-304:07
*** eghobo has joined #openstack-meeting-304:17
*** VW_ has quit IRC04:22
*** jckasper has quit IRC04:29
*** ajo has joined #openstack-meeting-304:49
*** fallenpegasus has joined #openstack-meeting-305:14
*** wojdev has joined #openstack-meeting-305:16
*** ivar-laz_ has joined #openstack-meeting-305:17
*** Nikolay_St has quit IRC05:17
*** ivar-laz_ has quit IRC05:17
*** emagana has joined #openstack-meeting-305:19
*** ivar-lazzaro has quit IRC05:21
*** btully has joined #openstack-meeting-305:29
*** wojdev has quit IRC05:30
*** wojdev has joined #openstack-meeting-305:40
*** wojdev has quit IRC05:40
*** garyk has joined #openstack-meeting-305:50
*** mrunge has joined #openstack-meeting-306:03
*** mrunge has quit IRC06:03
*** mrunge has joined #openstack-meeting-306:03
*** armax has quit IRC06:08
*** egallen has joined #openstack-meeting-306:21
*** mrmartin has joined #openstack-meeting-306:28
*** [1]evgenyf has joined #openstack-meeting-306:33
*** eghobo_ has joined #openstack-meeting-306:36
*** eghobo has quit IRC06:39
*** eghobo has joined #openstack-meeting-306:44
*** e0ne has joined #openstack-meeting-306:45
*** eghobo_ has quit IRC06:45
*** egallen has quit IRC06:46
*** stevemar has quit IRC06:46
*** kevinbenton has quit IRC06:49
*** egallen has joined #openstack-meeting-306:50
*** eghobo has quit IRC06:50
*** kevinbenton has joined #openstack-meeting-306:50
*** Longgeek has joined #openstack-meeting-306:52
*** iovadia has joined #openstack-meeting-306:54
*** jtomasek has joined #openstack-meeting-306:55
*** rushiagr_away is now known as rushiagr06:57
*** scheuran has joined #openstack-meeting-306:58
*** iovadia has quit IRC06:59
*** jcoufal has joined #openstack-meeting-307:03
*** wojdev has joined #openstack-meeting-307:03
*** MaxV has joined #openstack-meeting-307:06
*** Longgeek has quit IRC07:07
*** sahid has joined #openstack-meeting-307:08
*** e0ne has quit IRC07:09
*** safchain has joined #openstack-meeting-307:10
*** Piet has quit IRC07:12
*** iovadia has joined #openstack-meeting-307:13
*** zz_ttrifonov is now known as ttrifonov07:13
*** vhoward has quit IRC07:13
*** mrmartin has quit IRC07:14
*** vhoward has joined #openstack-meeting-307:15
*** fallenpegasus has quit IRC07:17
*** fallenpegasus has joined #openstack-meeting-307:18
*** Longgeek has joined #openstack-meeting-307:22
*** alexpilotti has joined #openstack-meeting-307:23
*** nkrinner has joined #openstack-meeting-307:27
*** mrmartin has joined #openstack-meeting-307:29
*** mrmartin has quit IRC07:30
*** mrmartin has joined #openstack-meeting-307:39
*** mrmartin has quit IRC07:42
*** irenab_ has joined #openstack-meeting-307:48
*** irenab has quit IRC07:49
*** irenab_ is now known as irenab07:49
*** mrmartin has joined #openstack-meeting-307:59
*** JeanBriceCombebi has joined #openstack-meeting-308:00
*** wojdev has quit IRC08:07
*** btully has quit IRC08:07
*** Nikolay_St has joined #openstack-meeting-308:18
*** roeyc has joined #openstack-meeting-308:18
*** jcoufal_ has joined #openstack-meeting-308:21
*** nkrinner has quit IRC08:25
*** jcoufal has quit IRC08:25
*** nkrinner has joined #openstack-meeting-308:27
*** garyk has quit IRC08:31
*** roeyc has quit IRC08:31
*** dobson` has quit IRC08:31
*** roeyc has joined #openstack-meeting-308:31
*** garyk has joined #openstack-meeting-308:32
*** ajo has quit IRC08:34
*** ajo_ has joined #openstack-meeting-308:34
*** JeanBriceCombebi has quit IRC08:36
*** e0ne has joined #openstack-meeting-308:37
*** matrohon has joined #openstack-meeting-308:43
*** salv-orl_ has joined #openstack-meeting-308:45
*** salv-orlando has quit IRC08:46
*** belmoreira has joined #openstack-meeting-308:46
*** dobson has joined #openstack-meeting-308:49
*** JeanBriceCombebi has joined #openstack-meeting-308:50
*** wojdev has joined #openstack-meeting-308:52
*** pkoniszewski has joined #openstack-meeting-308:53
*** mrmartin has quit IRC09:22
*** sankarshan_away is now known as sankarshan_09:40
*** emagana has quit IRC09:40
*** e0ne is now known as e0ne_09:48
*** MaxV has quit IRC09:57
*** e0ne_ is now known as e0ne09:58
*** roeyc has quit IRC10:09
*** mwagner_lap has quit IRC10:13
*** e0ne is now known as e0ne_10:13
*** e0ne_ is now known as e0ne10:16
*** mwagner_lap has joined #openstack-meeting-310:30
*** yamahata has quit IRC10:36
*** stanzgy__ has quit IRC10:51
*** alexpilotti has quit IRC10:52
*** salv-orlando has joined #openstack-meeting-310:53
*** salv-orl_ has quit IRC10:56
*** banix has joined #openstack-meeting-311:00
*** e0ne has quit IRC11:05
*** rushiagr is now known as rushiagr_away11:08
*** roeyc has joined #openstack-meeting-311:09
*** e0ne has joined #openstack-meeting-311:10
*** banix has quit IRC11:13
*** markvoelker has quit IRC11:18
*** e0ne is now known as e0ne_11:20
*** e0ne_ is now known as e0ne11:21
*** mwagner_lap has quit IRC11:24
*** Longgeek_ has joined #openstack-meeting-311:31
*** Longgeek has quit IRC11:32
*** alexpilotti has joined #openstack-meeting-311:36
*** alexpilotti has quit IRC11:48
*** jcoufal_ is now known as jcoufal11:51
*** baoli has joined #openstack-meeting-311:56
*** VW_ has joined #openstack-meeting-311:58
*** VW_ has quit IRC12:01
*** VW__ has joined #openstack-meeting-312:01
*** mwagner_lap has joined #openstack-meeting-312:09
*** markvoelker has joined #openstack-meeting-312:11
*** sankarshan_ is now known as sankarshan_away12:18
*** VW__ has quit IRC12:19
*** sankarshan_away is now known as sankarshan_12:29
*** egallen has quit IRC12:30
*** Networkn3rd has joined #openstack-meeting-312:30
*** Longgeek has joined #openstack-meeting-312:32
*** Longgeek_ has quit IRC12:33
*** egallen has joined #openstack-meeting-312:34
*** sankarshan_ is now known as sankarshan_away12:42
*** alexpilotti has joined #openstack-meeting-312:43
*** Longgeek has quit IRC12:44
*** Longgeek_ has joined #openstack-meeting-312:48
*** doug-fish has left #openstack-meeting-312:51
*** jckasper has joined #openstack-meeting-312:58
*** wojdev has quit IRC13:03
*** Longgeek_ has quit IRC13:04
*** Longgeek has joined #openstack-meeting-313:05
*** peristeri has joined #openstack-meeting-313:09
*** bknudson has quit IRC13:09
*** MaxV has joined #openstack-meeting-313:10
*** mrunge has quit IRC13:11
*** fallenpegasus has quit IRC13:12
*** fallenpegasus has joined #openstack-meeting-313:13
*** JeanBriceCombebi has quit IRC13:14
*** MaxV has quit IRC13:15
*** fallenpegasus has quit IRC13:17
*** stevemar has joined #openstack-meeting-313:18
*** JeanBriceCombebi has joined #openstack-meeting-313:21
*** VW_ has joined #openstack-meeting-313:22
*** zhenguo has quit IRC13:27
*** lsmola_ is now known as lsmola13:29
*** wojdev has joined #openstack-meeting-313:39
*** ajo_ is now known as ajo13:40
*** bknudson has joined #openstack-meeting-313:43
*** sigmavirus24_awa is now known as sigmavirus2413:44
*** Piet has joined #openstack-meeting-313:50
*** JeanBriceCombebi has quit IRC13:52
*** JeanBriceCombebi has joined #openstack-meeting-313:52
*** Networkn3rd has quit IRC13:55
*** garyk has quit IRC13:56
*** absubram has joined #openstack-meeting-313:59
*** irenab has quit IRC13:59
*** armax has joined #openstack-meeting-313:59
*** irenab has joined #openstack-meeting-314:00
*** JeanBriceCombebi has quit IRC14:00
*** JeanBriceCombebi has joined #openstack-meeting-314:00
*** nkrinner has quit IRC14:04
*** irenab has quit IRC14:04
*** julim has joined #openstack-meeting-314:06
*** roeyc has quit IRC14:09
*** btully has joined #openstack-meeting-314:11
*** lsmola has quit IRC14:12
*** wojdev has quit IRC14:19
*** weiting has joined #openstack-meeting-314:21
*** jgrimm is now known as zz_jgrimm14:22
*** e0ne is now known as e0ne_14:25
*** [1]evgenyf has quit IRC14:25
*** mattfarina has joined #openstack-meeting-314:28
*** VW_ has quit IRC14:29
*** e0ne_ is now known as e0ne14:30
*** irenab has joined #openstack-meeting-314:31
*** VW_ has joined #openstack-meeting-314:32
*** roeyc has joined #openstack-meeting-314:33
*** irenab has quit IRC14:35
*** evgenyf has joined #openstack-meeting-314:36
*** MarkAtwood has joined #openstack-meeting-314:42
*** carl_baldwin has joined #openstack-meeting-314:43
*** emagana has joined #openstack-meeting-314:45
*** gsagie_ has joined #openstack-meeting-314:47
*** yalie has joined #openstack-meeting-314:49
*** saggi1 has joined #openstack-meeting-314:50
*** mlavalle has joined #openstack-meeting-314:54
*** vikram__ has joined #openstack-meeting-314:55
*** nelsnelson has joined #openstack-meeting-314:56
*** amuller has joined #openstack-meeting-314:57
mlavallecarl_baldwin: aren't the dragon flows guys attending the meeting?14:57
*** tidwellr1 has joined #openstack-meeting-314:58
gsagie_I am here14:59
gsagie_and i think saggi as well14:59
*** johnbelamaric has joined #openstack-meeting-314:59
*** lblanchard has joined #openstack-meeting-315:00
saggi1I'm here too15:00
mlavallegsagie_: great. should dragon flows be a point in the agenda?15:00
saggi1mlavalle: yea15:00
yaliehi, where could I find the agenda?15:00
mlavalleyalie: https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:01
carl_baldwinhi all.  Sorry to be a bit late.15:01
vikram__Carl: hi15:01
pavel_bondarhi <carl_baldwin>15:01
carl_baldwin#startmeeting neutron_l315:01
openstackMeeting started Thu Apr 30 15:01:37 2015 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
johnbelamarichi15:01
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:01
openstackThe meeting name has been set to 'neutron_l3'15:01
carl_baldwin#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
yaliemlavalle: thanks15:01
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:01
*** pc_m has joined #openstack-meeting-315:01
saggi1mlavalle: We just want to talk a bit about it. And try and get our head around how we fit into liberty15:02
carl_baldwinKilo released today!15:02
*** emagana has quit IRC15:02
* pc_m yay!15:02
carl_baldwinAlso, if you have not yet heard, there are changes coming to the feature proposal process.  Not merged yet but appears to be gaining momentum.15:03
carl_baldwin#link https://review.openstack.org/#/c/177342/15:03
*** wojdev has joined #openstack-meeting-315:04
carl_baldwinFrom my perspective, what this means is that there may be less work involved in proposing features for a cycle.  The more detailed design discussions can happen more independently when there is more confidence that a feature can be included in the scope of a release.15:04
*** bpokorny has quit IRC15:04
carl_baldwinIf this is the first you’ve heard, I encourage you to go take a look at the review I linked.15:05
gsagie_ok, thanks carl15:05
*** baoli has quit IRC15:05
carl_baldwinAny other announcements?15:05
yaliethanks15:05
vikram__thanks15:05
carl_baldwin#topic Bugs15:06
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:06
carl_baldwinI bumped up the priority of bug 143881915:06
openstackbug 1438819 in neutron "Router gets address allocation from all new gw subnets" [High,In progress] https://launchpad.net/bugs/1438819 - Assigned to Andrew Boik (drewboik)15:06
*** baoli has joined #openstack-meeting-315:07
carl_baldwinUnfortunately, we didn’t understand the full effect of the bug until it was too late for Kilo.  So, it is release noted.15:07
carl_baldwinI didn’t mark it critical because it is not a common use case to add a subnet to an external network.15:08
carl_baldwinAny other bugs we should be aware of?15:08
*** stevelle has left #openstack-meeting-315:09
carl_baldwin#topic Dragonflow15:09
*** openstack changes topic to "Dragonflow (Meeting topic: neutron_l3)"15:09
* carl_baldwin hopes he got that right.15:10
*** MarkAtwood has quit IRC15:10
*** iovadia has quit IRC15:10
gsagie_You got it right15:11
carl_baldwinsaggi1: Do you have links to introduce this to the team?15:11
carl_baldwingsagie_: ^15:11
saggi1Sure, https://launchpad.net/dragonflow15:11
saggi1carl_baldwin: Already pointed it out in a previous meeting15:11
gsagie_And you can also read the great blog posts from Eran Gampel here: http://blog.gampel.net15:11
*** krtaylor has quit IRC15:12
mlavallesaggi1: this is the repo, right: https://github.com/stackforge/dragonflow15:12
saggi1mlavalle: yes15:12
saggi1Basically we don't try and be a new full driver15:12
saggi1We base ourselves on the LegcayRouter and try and optimize where we can using ovs flows on the compute node15:12
saggi1For instance, if you have two VMs from different subnets on the same host. We detect that and install a flow that bypasses the normal routing15:13
gsagie_The idea in a nutshell is to achieve DVR on top of "legacy" L3 implementation using an SDN controller (based on Ryu framework) so we achieve DVR without the need of compute node L3 agents and without namespaces15:13
carl_baldwinsaggi1: gsagie_:  Are there db side changes too?15:13
saggi1carl_baldwin: no15:13
saggi1carl_baldwin: We use the topology information for our optimizations15:14
saggi1tenants, routers, subnets15:14
gsagie_and i believe in the future we will be able to eliminate the L2 agent as we can also leverage security groups driver that configure flows remotely15:14
carl_baldwinThis is all contained within the L3 agent process?15:14
mlavallesaggi1: so, the router namespaces in the network node still exist?15:14
gsagie_mlavalle : no15:14
gsagie_we use open flow flows to achieve the DVR functionallity15:14
gsagie_mlavalle : sorry, for SNAT we use them still15:15
tidwellr1so it's completely flow-based otherwise?15:15
gsagie_mlavalle : but we have future plans to distribute that just as well, design wise its possible15:15
mlavallegsagie_: also with flows, right?15:15
*** wojdev has quit IRC15:15
vikram__gsagie: did this support vpn as well?15:15
saggi1We want to offload as much as we can to openflow flows15:16
yaliegsagie_: is there dependency on the verison of ovs?15:16
saggi11.3 currently15:16
saggi1yalie: ^15:16
gsagie_mlavalle : in the current design SNAT/FIP is still using legacy L315:16
gsagie_yalie: 2.1.315:16
gsagie_but we have plans to also implement that using flows, so its mostly a matter of work resources15:17
*** bpokorny has joined #openstack-meeting-315:17
*** zz_jgrimm is now known as jgrimm15:17
mlavallegsagie_: got it15:17
*** krtaylor has joined #openstack-meeting-315:18
saggi1The design allows us to add more features as we go falling back to other, non-flow, packet delivery for anything we don't implement.15:18
*** roeyc has quit IRC15:19
gsagie_I think that getting rid of the agents in the compute node might prove to be a big complexity reducer, and i think the design is simple enough in the controller side so this might be a good reference design for SDN15:19
carl_baldwinSo, to be clear, you have E/W routing working and N/S routing is still done with the LegacyRouter implementation?15:19
gsagie_carl_baldwin: currently yes15:19
carl_baldwingsagie_: It is a good start.15:19
mlavallegsagie_: what are the benefits performance / throughput wise?15:20
gsagie_mlavalle: we are working on benchmarking this versus current DVR, no results yet, but management complexity wise, i think you can see that we don't need the namespaces is an improvment15:20
saggi1mlavalle: We don't have a lot of data on it. We are still trying to asses how to properly test "real world" use cases. So any suggestions about what to benchmark will be most appriciated.15:21
vikram__gsagie: how it's different from other open controllers like open-contrail?15:22
saggi1Hammering E\W communication saw a 20% increase in throughput IIRC but it was a very simple benchmark.15:22
*** evgenyf has quit IRC15:22
carl_baldwinI’m very happy to see this work being done.  I’d like to continue to support this effort.  How has been your experience integrating with the current L3 implementation?  I’m hoping your perspective might help to improve the modularity of the code.15:22
mlavallesaggi1: I work for a big deployer. We have a tendency to do thins based on flows. I am going to bring this up to my cowworkers and we may get back to you15:22
saggi1carl_baldwin: It's been problematic. But it's getting better.15:23
saggi1carl_baldwin: A lot of dvr specific code is causing odd bus for us.15:24
*** belmoreira has quit IRC15:24
saggi1That being said in the last couple of months there was a lot of work in decoupling l2 from l3 and it's been very helpful.15:24
gsagie_vikram_ : we are trying to build this in a very simple way, we leverage Ryu for the simplicity but any other SDN controller can be used, but we don't want to introduce more complexity if we don't need too15:24
carl_baldwinsaggi1: gsagie_:  I wonder if we could get together with a little more time to discuss it.  Either at summit — which may or may not be possible for me — or at another time.15:24
carl_baldwinsaggi1: I’m glad to hear that we’re moving in a good direction.15:25
vikram__Carl: +115:25
mlavallesaggi1: by the way, we are doing things with Ryu, so there's affinity already15:25
vikram__gsagie: thanks got it15:25
*** e0ne is now known as e0ne_15:25
gsagie_carl_baldwin: We would love to meet in the summit and further discuss it, hopefully we will also have some numbers to show you15:25
mlavallegsagie_, carl_baldwin: I am available, willing to meet at summit15:26
pc_mwould be interesting to learn more15:26
gsagie_I think we would love to make this a joint effort, because i think that idea wise this design can be a good reference15:26
tidwellr1I would love to learn a little more too15:26
vikram__idea sounds really interesting. I am in.15:27
carl_baldwinWe’ll find some time at the summit for it.  I’m not sure about my complete schedule but I’d like to fit this in.  My focus will be on what steps we can take to allow your efforts to continue successfully in parallel with the existing L3 implementation.15:27
yalieso, this is a new implement of DVR, will re-use the API now?15:28
saggi1carl_baldwin: That is exactly what we want to nail down. Since, as you can see, we depend on a lot of core l3 code15:28
*** MarkAtwood has joined #openstack-meeting-315:28
gsagie_carl_baldwin: is the L3 reference implementation going out of tree?15:28
*** scheuran has quit IRC15:29
carl_baldwinI’m thinking about the Friday as a “contributor meetup”15:29
mlavallecarl_baldwin: +115:29
vikram__timing?15:29
*** marun has joined #openstack-meeting-315:29
carl_baldwingsagie_: I’m not 100% sure yet.  So far, there are no immediate plans.15:30
carl_baldwingsagie_: saggi1:  Will you be staying until Friday?15:30
*** garyk has joined #openstack-meeting-315:31
gsagie_carld_baldwin: yes15:31
gsagie_carl_baldwin15:31
*** irenab has joined #openstack-meeting-315:31
carl_baldwin#action carl_baldwin to setup a time and place on Friday for a contributor meetup on L3 modularity and supporting development of dragonflow.15:32
gsagie_thanks carl !15:33
saggi1thanks15:33
*** kozhukalov has joined #openstack-meeting-315:33
carl_baldwingsagie_: saggi1:  Thank you for coming to the meeting.  I look forward to hearing more about your work.  I will read the blog posts and look through the code repository that you have linked.15:34
carl_baldwinAnything else on this topic for now?15:34
*** sergef has joined #openstack-meeting-315:34
gsagie_not from me, thanks15:34
yalieI have a question15:34
gsagie_feel free to approach any of us online if you have any question15:34
gsagie_yalie: yes?15:35
*** e0ne_ is now known as e0ne15:35
yalieabout the gateway of subnet, when a VM act as a router15:35
mlavallegsagie_: you hang out in #openstack-neutron?15:35
gsagie_yes15:35
saggi1mlavalle: yes15:35
yaliewe can't assign the gateway with a VM' port IP15:35
mlavalle:-)15:35
yaliebut when the VM as a service like router, we need it15:35
yaliecould we remove this limitation?15:36
*** irenab has quit IRC15:36
saggi1yalie: We would need to get that information from the DB. To know that this VM is a router. Since this is where we get the topology informationfrom15:36
carl_baldwinyalie: Could we postpone this for Open Discussion.  Or, we could discuss in the neutron channel just after the meeting.15:36
saggi1carl_baldwin: sure15:36
yaliecarl_baldwin: yes, thanks15:36
carl_baldwin#topic bgp-dynamic-routing15:37
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:37
carl_baldwindevessa cannot make it today.15:37
carl_baldwintidwellr1: Do you want to give an update quickly?15:37
tidwellr1sure15:37
tidwellr1I'm working through the tutorial here https://wiki.openstack.org/wiki/Neutron/DynamicRouting/TestingDynamicRouting15:38
tidwellr1I'm deviating from it slightly as I'm interested in how to go about automated testing og BGP advertisements15:39
*** emagana has joined #openstack-meeting-315:39
tidwellr1I'm mixing extra quagga instances, but following instructions otherwise15:40
*** Swami has joined #openstack-meeting-315:41
*** pkoniszewski has quit IRC15:41
*** sergef has quit IRC15:41
carl_baldwintidwellr1: Sounds like good progress but we’ve caught you in the middle of getting it on its feet.15:41
tidwellr1that's OK15:41
tidwellr1I'm really coming at this from the testing perspective15:42
carl_baldwintidwellr1: understood.  Keep up the good work.15:42
tidwellr1I'll have more to share next week15:43
carl_baldwintidwellr1: Do you think it would be difficult to run quagga on the same VM instance with devstack, adding routes to br-ex instead of eth0?  It may be very difficult still to get automated testing in the gate needing more than one instance.15:43
carl_baldwinSomething to think about… We should probably move on and get to ipam before the meeting time is over.15:45
carl_baldwin#topic neutron-ipam15:45
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:45
tidwellr1yeah, that's a concern. I have a couple ideas I'm going to play with, I'll report back next week15:45
carl_baldwinjohnbelamaric: tidwellr1: pavel_bondar:  ping15:45
*** jcoufal has quit IRC15:45
pavel_bondarpong15:45
johnbelamariccarl_baldwin: hello15:45
carl_baldwinI’ve been watching the progress with getting the tests to pass.15:46
carl_baldwinNice work so far.15:46
pavel_bondarit's close:)15:46
carl_baldwinI also started reviewing the patch but I did not finish.  It is a pretty large patch.15:46
pavel_bondarI switched back to pass subnet_id in interface instead of subnet_dict and has a workaround for issue with OpenContrail tests15:47
johnbelamariccarl_baldwin, pavel_bondar, tidwellr1: I think there is one comment left to address from Ryan regarding duplicate code15:48
pavel_bondarAlso I sent to ML my finding about original issue I had with OpenContrail tests and fetching subnet using plugin. #link http://lists.openstack.org/pipermail/openstack-dev/2015-April/063004.html15:49
*** yamahata has joined #openstack-meeting-315:49
pavel_bondarjohn, could you please point which comment?15:49
johnbelamaric*looking*15:50
carl_baldwinpavel_bondar: Thanks for pointing out the ML post.  I have not visited the ML yet today.  :)15:50
tidwellr1I struggled with the OpenContrail tests as well, they extend the db_plugin tests in some interesting ways15:51
pavel_bondartidwellr1: yeah, they do not call super methods directly, but instead create new http request, so they are quite different from others15:53
tidwellr1I ended up writing new test cases that the OpenContrail tests wouldn't extend as my hack, but that's not really an option here is it :)15:54
*** lblanchard has quit IRC15:54
*** egallen has quit IRC15:55
johnbelamaricpavel_bondar: nevermind, you fixed it in PS 5115:55
*** emagana has quit IRC15:57
pavel_bondarjohnbelamaric: yeah, right, workaround was used to bypass plugin level and call _get_subnet directly from db_base15:57
johnbelamaricpavel_bondar: I was referring to the open comment I thought there was, it was done in 5115:57
pavel_bondarah:)15:57
pavel_bondargot it15:57
pavel_bondarbut yeah, OpenContrail issue is not high priority for now since I have workaround, but it is still interesting why it deletes port on fetching subnet15:59
*** ryansb has joined #openstack-meeting-315:59
*** wojdev has joined #openstack-meeting-315:59
carl_baldwinWe can take this to the neutron room.  We’re out of time.  :)15:59
carl_baldwinThanks for all your work.15:59
carl_baldwin#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Thu Apr 30 15:59:55 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
*** emagana has joined #openstack-meeting-315:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-04-30-15.01.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-04-30-15.01.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-04-30-15.01.log.html16:00
pavel_bondarthanks16:00
*** pc_m has left #openstack-meeting-316:00
*** saggi1 has quit IRC16:00
yalieHi carl_baldwin? could we talk about that subnet gateway problem?16:01
carl_baldwinyalie: Yes, could you jump over to the neutron room?16:01
*** alexsyip has joined #openstack-meeting-316:01
*** johnbelamaric has left #openstack-meeting-316:01
*** baoli has quit IRC16:02
carl_baldwinopenstack-neutron16:02
carl_baldwinoops.16:02
carl_baldwin#openstack-neutron16:02
*** weiting has quit IRC16:02
yaliecarl_baldwin: OK, thanks!16:02
*** baoli_ has joined #openstack-meeting-316:03
*** vikram__ has quit IRC16:06
*** fallenpegasus has joined #openstack-meeting-316:08
*** JeanBriceCombebi has quit IRC16:10
ryansbanybody about for api-wg?16:11
krotscheckryansb: I am16:11
krotscheckryansb: But I'm guessing nobody else is.16:11
ryansbseems so ¯\_ツ_/¯16:12
ryansbanyways, unless anyone else shows up we'll just call it cancelled16:12
*** Swami has quit IRC16:13
*** egallen has joined #openstack-meeting-316:13
*** salv-orlando has quit IRC16:17
*** salv-orlando has joined #openstack-meeting-316:19
*** Nikolay_St has quit IRC16:21
*** julim has quit IRC16:22
*** krtaylor has quit IRC16:25
*** matrohon has quit IRC16:25
*** ryansb has left #openstack-meeting-316:26
*** gsagie_ has left #openstack-meeting-316:26
*** Networkn3rd has joined #openstack-meeting-316:28
*** Networkn3rd has quit IRC16:31
*** Networkn3rd has joined #openstack-meeting-316:31
*** safchain has quit IRC16:38
*** krtaylor has joined #openstack-meeting-316:38
*** eghobo has joined #openstack-meeting-316:39
*** tidwellr1 has left #openstack-meeting-316:42
*** alexpilotti has quit IRC16:46
*** igordcard_ has quit IRC16:46
*** e0ne is now known as e0ne_16:49
*** e0ne_ is now known as e0ne16:50
*** e0ne has quit IRC16:51
*** cawil1 has quit IRC16:52
*** melwitt has joined #openstack-meeting-316:55
*** igordcard_ has joined #openstack-meeting-316:56
*** igordcard_ has quit IRC16:56
*** igordcard_ has joined #openstack-meeting-316:58
*** bpokorny_ has joined #openstack-meeting-316:58
*** igordcard_ has quit IRC16:58
*** emagana has quit IRC17:00
*** bpokorny has quit IRC17:01
*** irenab has joined #openstack-meeting-317:01
*** Sukhdev has joined #openstack-meeting-317:02
*** Youcef has joined #openstack-meeting-317:04
*** amuller has left #openstack-meeting-317:05
*** irenab has quit IRC17:06
*** emagana has joined #openstack-meeting-317:06
*** yamahata has quit IRC17:07
*** eghobo_ has joined #openstack-meeting-317:09
*** beagles is now known as beagles_brb17:11
*** eghobo has quit IRC17:12
*** sahid has quit IRC17:12
*** salv-orlando has quit IRC17:16
*** wojdev has quit IRC17:16
*** salv-orlando has joined #openstack-meeting-317:16
*** yalie has quit IRC17:17
*** beagles_brb is now known as beagles17:18
*** salv-orlando has quit IRC17:21
*** sarob has joined #openstack-meeting-317:21
*** salv-orlando has joined #openstack-meeting-317:21
*** sbalukoff has quit IRC17:23
*** wojdev has joined #openstack-meeting-317:27
*** yamahata has joined #openstack-meeting-317:29
*** ivar-lazzaro has joined #openstack-meeting-317:29
*** mrmartin has joined #openstack-meeting-317:30
*** SumitNaiksatam has quit IRC17:34
*** emagana has quit IRC17:35
*** bpokorny_ has quit IRC17:39
*** VW_ has quit IRC17:40
*** ketem-shemen__ has joined #openstack-meeting-317:40
*** megm_ has joined #openstack-meeting-317:40
*** lintan_ has joined #openstack-meeting-317:41
*** Nikolay_St has joined #openstack-meeting-317:41
*** VW_ has joined #openstack-meeting-317:41
*** GheRiver1 has joined #openstack-meeting-317:41
*** VW__ has joined #openstack-meeting-317:42
*** VW__ has quit IRC17:42
*** VW__ has joined #openstack-meeting-317:43
*** coolsvapl has joined #openstack-meeting-317:45
*** sdague_ has joined #openstack-meeting-317:45
*** VW_ has quit IRC17:46
*** carl_baldwin_ has joined #openstack-meeting-317:46
*** carl_baldwin has quit IRC17:46
*** ketem-shemen_ has quit IRC17:47
*** kbyrne has quit IRC17:47
*** megm has quit IRC17:47
*** GheRivero has quit IRC17:47
*** lintan has quit IRC17:47
*** sdague has quit IRC17:47
*** coolsvap|afk has quit IRC17:47
*** salv-orlando has quit IRC17:47
*** jkoelker has quit IRC17:47
*** devananda has quit IRC17:47
*** VW_ has joined #openstack-meeting-317:47
*** carl_baldwin_ is now known as carl_baldwin17:47
*** sdague_ is now known as sdague17:47
*** salv-orlando has joined #openstack-meeting-317:49
*** jkoelker has joined #openstack-meeting-317:49
*** devananda has joined #openstack-meeting-317:49
*** VW__ has quit IRC17:51
*** rkukura has joined #openstack-meeting-317:51
*** kbyrne has joined #openstack-meeting-317:54
*** SumitNaiksatam has joined #openstack-meeting-317:56
*** igordcard has joined #openstack-meeting-317:56
*** vgridnev_ has joined #openstack-meeting-317:58
SumitNaiksatamrkukura: igordcard ivar-lazzaro hi18:01
rkukurahi18:01
ivar-lazzarohi18:01
SumitNaiksatam#startmeeting networking_policy18:01
openstackMeeting started Thu Apr 30 18:01:36 2015 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
igordcardhello all18:01
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#April_30th.2C_23rd.2C_201518:01
*** e0ne has joined #openstack-meeting-318:02
SumitNaiksatam#topic Bugs18:02
*** openstack changes topic to "Bugs (Meeting topic: networking_policy)"18:02
*** irenab has joined #openstack-meeting-318:02
SumitNaiksatami think only the back port for this is not merged: #link https://bugs.launchpad.net/group-based-policy/+bug/143277918:03
openstackLaunchpad bug 1432779 in Group Based Policy "redirect actions don't work with external policies" [Critical,In progress] - Assigned to Ivar Lazzaro (mmaleckk)18:03
SumitNaiksatamother than that, i dont think we have any reported outstanding critical bugs18:03
SumitNaiksatamany other bugs to discuss today?18:04
SumitNaiksatamokay perhaps not18:04
SumitNaiksatam#topic Functional/Integration Tests18:04
*** openstack changes topic to "Functional/Integration Tests (Meeting topic: networking_policy)"18:04
*** yapeng has joined #openstack-meeting-318:05
SumitNaiksatam#link https://review.openstack.org/#/c/17426718:05
SumitNaiksatamthe above patch starts running jishnu’s test suite which performs integration testing by exercising GBP REST and client interfaces18:05
ivar-lazzaronice!18:06
SumitNaiksatamat this point all tests are passing in that test suite18:06
*** huichun has joined #openstack-meeting-318:06
ivar-lazzarodo we know what is covered by the tests?18:06
SumitNaiksatamwe have to fix some bugs which this test suite caught18:06
SumitNaiksatamit covers all the resources we had in juno18:06
SumitNaiksatamand some  scenarios18:07
rkukuraare tests disabled due to bugs?18:07
SumitNaiksatamrkukura: no tests are currently disabled18:07
SumitNaiksatami mean no tests in that test suite are disabled18:07
rkukuraif they all pass, why do we have to fix some bugs?18:07
SumitNaiksatamrkukura: they were not passing before18:07
rkukuraOK, so they have already been fixed?18:08
SumitNaiksatamyeah, as of yesterday18:08
SumitNaiksatamso you see the job passing today18:08
rkukuragreat, I was confused by “we have to fix” implying they weren’t already fixed18:08
ivar-lazzarorkukura: +1 :)18:08
*** bpokorny has joined #openstack-meeting-318:09
*** irenab has quit IRC18:09
SumitNaiksatamoh, sorry, i meant to say “had” not “have”…my bad18:09
rkukurano problem18:09
*** songole has joined #openstack-meeting-318:09
SumitNaiksatamin some cases the bugs were fixed but the tests were not updated18:09
SumitNaiksatamin the sense that the tests were not checking for the right result18:09
SumitNaiksatamso a combination of things18:09
SumitNaiksatambut anyway, right now its clean18:10
SumitNaiksatamit would have been good to have jishnu in this meeting to answer specific questions on the extent of coverage18:10
SumitNaiksatambut he is in travel right now18:10
SumitNaiksatamthe patch itself is just shell script enabling the tests18:11
ivar-lazzaroSumitNaiksatam: is the test suite published anywhere?18:12
SumitNaiksatamyapeng: songole: hi thanks for joining18:12
songolehello18:12
ivar-lazzaroSumitNaiksatam: It would be good to have a feeling of which datapath scenario are covered18:12
ivar-lazzarosongole: hi18:12
*** emagana has joined #openstack-meeting-318:12
rkukurado the same tests run for both master and stable/juno?18:12
songoleivar-lazzaro: hi18:12
SumitNaiksatamivar-lazzaro: firstly the test suite is not doing data path testing18:13
SumitNaiksatamivar-lazzaro: the tests are published in pypi package18:14
SumitNaiksatamrkukura: the same tests run for both master and stable/juno18:14
rkukuraSumitNaiksatam: What will we do when master diverges from stable/juno so that we need different tests? Can we branch the test repo too?18:15
SumitNaiksatamrkukura: yes18:15
SumitNaiksatamrkukura: right now the test suite mostly covers the juno features18:15
*** Swami has joined #openstack-meeting-318:16
SumitNaiksatamany other questions on this test case?18:17
*** ivar-laz_ has joined #openstack-meeting-318:17
*** mlavalle has quit IRC18:18
*** VW_ has quit IRC18:18
SumitNaiksatamhopefully we can get the patch merged soon18:18
*** egallen has quit IRC18:18
SumitNaiksatam#topic Packaging Update18:18
*** openstack changes topic to "Packaging Update (Meeting topic: networking_policy)"18:18
*** mwang2 has joined #openstack-meeting-318:19
SumitNaiksatamrkukura: anything to update here?18:19
rkukuraI have not made any progress on fedora/RDO packages (was on PTO last week).18:20
*** Sukhdev has quit IRC18:20
rkukura I checked today and it looks like all the tarballs on launchpad are at least a month old. Are we waiting for new ones?18:20
*** ivar-laz_ has quit IRC18:20
*** baoli_ has quit IRC18:20
*** Sukhdev has joined #openstack-meeting-318:20
SumitNaiksatamrkukura: we havent cut kilo-3 yet18:20
rkukurathat’s what I thought18:20
SumitNaiksatamif thats what you are looking for18:20
rkukurathat, and a new stable/juno release I think18:20
SumitNaiksatamor were you looking for another stable/juno?18:21
*** ivar-lazzaro has quit IRC18:21
SumitNaiksatamah just asking that18:21
*** baoli_ has joined #openstack-meeting-318:21
rkukuraI can certainly update to the stable/juno tarballs we have, but thought we had lots of fixes since then18:21
SumitNaiksatamrkukura: okay lets sync up after this meeting on this18:21
rkukurasure18:21
*** Yi has joined #openstack-meeting-318:21
SumitNaiksatam#topic Kilo Sync18:22
*** openstack changes topic to "Kilo Sync (Meeting topic: networking_policy)"18:22
rkukuraI’d like to get the fedora packages update soon enough that the RDO packags will be updated by the summit.18:22
SumitNaiksatamrkukura: okay, lets work towards getting you need for that18:22
SumitNaiksatam*what you18:22
rkukuraSumitNaiksatam: thanks18:22
SumitNaiksatamrkukura: i will ping you after this meeting18:22
SumitNaiksatamregarding kilo sync18:23
SumitNaiksatamthe last vestiges of kilo sync are complete meaning - GBP-UI and GBP-Automation projects are is sync with kilo18:23
SumitNaiksatamalso the kilo-gbp devstack branch is functional with kilo18:24
igordcardSumitNaiksatam, nice18:24
SumitNaiksatamby functional with kilo I mean, it uses stable/kilo branches for openstack projects18:24
igordcardSumitNaiksatam, was the kilo-gbp devstack branch broken last saturday?18:24
*** ivar-lazzaro has joined #openstack-meeting-318:24
SumitNaiksatamigordcard: yes it was broken at different times :-)18:25
igordcardSumitNaiksatam, okay18:25
SumitNaiksatami have tested this, but please let me know if you see any issues18:25
ivar-lazzaromac died, sorry about that18:25
SumitNaiksatamivar-lazzaro: np18:25
*** baoli_ has quit IRC18:25
ivar-lazzarodid I miss anything exciting?18:25
*** songole has quit IRC18:25
SumitNaiksatamthe kilo-gbp branch itself is based on upstream devstack stable/juno18:25
SumitNaiksatamivar-lazzaro: no, same old boring stuff! ;-)18:26
igordcardlast night (your afternoon) kilo-gbp ran without any issues here18:26
SumitNaiksatamat this point i consider the kilo-sync acitivity to be complete18:26
SumitNaiksatamivar-lazzaro: ah okay, good to know18:26
*** ajo has quit IRC18:26
SumitNaiksatamone thing to note, especially rkukura - the gbp client also has progressed to sync with kilo18:27
SumitNaiksatamit means that for using GBP stable/juno we have to use 0.9.1 version of the client18:27
rkukuraSumitNaiksatam: For fedora and RDO, we’ll need to be compatible with the client versions included in those releases18:28
SumitNaiksatamby version, i mean its a 0.9.1 tag in the repo18:28
*** sbalukoff has joined #openstack-meeting-318:28
igordcardwill python-openstackclient be extended to support gbp?18:28
SumitNaiksatamrkukura: so 0.9.1 should work with openstack stable/juno18:28
*** egallen has joined #openstack-meeting-318:29
SumitNaiksatamigordcard: my understanding is that  python-openstackclient has a modular architecture such that we could extend it without us having to push anything into python-openstackclient, is that correct?18:29
igordcardSumitNaiksatam, I haven't seen the internals of python-openstackclient but the individual clients seem to be getting deprecated, so I asked18:30
*** mrmartin has quit IRC18:30
SumitNaiksatamigordcard: i believe this discussion came up in the context of neutron as well, and the last i heard they were not planning to move immediately (or at least were not being forced to)18:31
SumitNaiksatambut i have not been uptodate with that18:31
SumitNaiksatamthat said i dont think we are targeting any of this acitivity for kilo18:31
SumitNaiksatamunless we are forced to18:31
SumitNaiksatamof course, definitely something we do plan to do18:31
*** mattfarina has quit IRC18:31
SumitNaiksatamigordcard: in case you want to scope out what it involves, that would be great18:31
igordcardSumitNaiksatam, I can do that18:32
SumitNaiksatamjust to assess the amount of work both from a technical and resource perspective18:32
SumitNaiksatamigordcard: great, thanks18:32
SumitNaiksatam#topic Floating IP18:32
*** openstack changes topic to "Floating IP (Meeting topic: networking_policy)"18:32
SumitNaiksatami think magesh is on PTO18:33
SumitNaiksatambut i did notice that he addresses the review comments and has posted a new version of the spec18:33
SumitNaiksatamSpec #link https://review.openstack.org/#/c/16717418:33
SumitNaiksatamImplementation #link https://review.openstack.org/#/c/167174/18:33
*** Youcef has quit IRC18:33
SumitNaiksatamat this point i believe whatever was discussed in the numerous discussions has been captured and mostly implemented18:34
SumitNaiksatamsince magesh is not here, comments will have to go to the review18:34
SumitNaiksatam#topic Service Chain provider refactor18:35
*** openstack changes topic to "Service Chain provider refactor (Meeting topic: networking_policy)"18:35
SumitNaiksatamSpec #link https://review.openstack.org/#/c/17411818:36
SumitNaiksatamImpl #link https://review.openstack.org/#/q/status:open+project:stackforge/group-based-policy+branch:master+topic:bp/sc-refactor,n,z18:36
SumitNaiksatamso there were few revs on the spec, and ivar-lazzaro has posted WIP patches as well per the current state of the spec18:36
ivar-lazzaro#link https://review.openstack.org/#/q/status:open+project:stackforge/group-based-policy+branch:master+topic:bp/node-centric-chain-plugin,n,z18:36
ivar-lazzaroThe topic is different, just to be more specific18:37
ivar-lazzarothere was no blueprint yet in launchpad18:37
SumitNaiksatamivar-lazzaro: okay i will add it18:38
ivar-lazzaroSumitNaiksatam: it's there now, just with a different topic #link https://blueprints.launchpad.net/openstack/?searchtext=node-centric-chain-plugin18:38
ivar-lazzaroSumitNaiksatam: I arbitrarily chose it, but we can change it at any time if we want to18:39
SumitNaiksatamivar-lazzaro: nit comment - i prefer calling this a “nodes composition plugin” NCP18:40
ivar-lazzaroSumitNaiksatam: I like node composition better too18:41
ivar-lazzaroSumitNaiksatam: however I would use "Chain" instead of "Plugin"18:41
SumitNaiksatamivar-lazzaro: i would intentionally avoid “chain"18:41
ivar-lazzaroSumitNaiksatam: plugin would be implicit in this case, but it's at least clear that it's a servicechain implementation18:41
SumitNaiksatamother than that, the ability to pass service-specific key-value pairs also needs to be there18:41
ivar-lazzaroSumitNaiksatam: about that, I was wondering if we need to introduce the concept of "tag"18:42
ivar-lazzaroIt would be a different URI, something like /tags18:42
ivar-lazzaroin which you could define metadata for all the GBP objects (and SC) without changing them directly18:42
ivar-lazzaroThe main point of Tags is that they will be for consumption of entities outside of GBP itself18:43
ivar-lazzaro(eg. UI, Automation, etc...)18:43
SumitNaiksatamthats definitely an option as we discussed18:43
SumitNaiksatami would prefer to not call it tags, since we also have the notion of policy “labels” and can be confusing18:44
ivar-lazzaroSo that every "internal" API (eg. service_profile, that needs to be consumed by the Node Drivers) can be defined by APIs and Extensions18:44
SumitNaiksatambut names aside, it would be good to hear from the rest of the team on this18:44
ivar-lazzaroSumitNaiksatam: Difference between labels and tags is that the latter won't be understood by internal GBP components18:45
ivar-lazzaroSumitNaiksatam: but we can choose a different name for that nonetheless18:45
SumitNaiksatamivar-lazzaro: i dont think it will never be the case that a node driver does not use a service-specific meta-data attribute - that is an implementation detail for the node driver18:45
ivar-lazzaroSumitNaiksatam: right, but since the node understands it, then it could as well just be an extension of service_profile18:46
ivar-lazzaroSumitNaiksatam: instead of a generic key-value pair18:46
SumitNaiksatamthe benefit of having this common metadata resource approach is that it allows us to associate aribitrary meta-data with any GBP resources18:47
ivar-lazzaroSumitNaiksatam: while for externally consumed metadata, we can use tags (of course the driver could tag a node)18:47
rkukuraThis is not sounding very intent-oriented :(18:47
SumitNaiksatamthe downside is that it requires the user to correlate information18:47
ivar-lazzarorkukura: tags are not intended to change the resource behavior, they are useful for external automation more than anythig18:48
ivar-lazzarorkukura: for example: which UI should I use to manage this Node?18:48
rkukuraI don’t see how “nodes” have much to do with “intent”18:49
SumitNaiksatamrkukura: i agree that the level of the node driver its not an intent abstraction any more18:49
ivar-lazzarorkukura: on that I agree. However keep in mind that we are talking about an operator API18:49
rkukuraI admit I have not been following previous discussions on this, or the BP, so I’m not even sure what a “node driver” is.18:49
igordcardbut the user does not need to deal with a Node directly18:50
SumitNaiksatamrkukura: however its not the “nodes”, its the “nodes driver”18:50
rkukuraivar-lazzaro: If its purely operation API, I’m not as concerned.18:50
rkukuraoperator18:50
ivar-lazzaroigordcard: +118:50
*** Nikolay_St has quit IRC18:50
SumitNaiksatamrkukura: yes, per igordcard, the node driver is not visible to the user18:50
rkukurathanks18:50
ivar-lazzaroigordcard: that's for operator consumption18:50
SumitNaiksatamrkukura: and yes this configuration is for opertaional reasons18:51
SumitNaiksatamthe confusion is happening because so far we have been dealing only with tenant facing resources18:51
ivar-lazzarorkukura: Service chain Specs/Nodes/Instances are purely Operator oriented, mostly like L2/L3 policies18:51
rkukuraJust to clarify, we mean “cloud operator” here, not the application deployment role, right?18:51
igordcardthe user simply chooses a service to be put into the service chain, eventually assigning some meaningful tags that the system supports, which could then be used internally for, e.g. as ivar-lazzaro said, show a different UI18:51
ivar-lazzarorkukura: yes18:52
SumitNaiksatamhowever a new resource is being proposed here called “service profile”18:52
SumitNaiksatamthis resource is managed by the operator (cloud operator)18:52
ivar-lazzaroigordcard: the user would simply chose the policy rule (REDIRECT to some chain)18:52
SumitNaiksatambut is visible to the user18:52
igordcardivar-lazzaro, and the tags are predefined for the nodes that compose the chain right?18:53
ivar-lazzaroigordcard: how the chain is implemented and which metadata are associated with it is a Cloud Operator's concern18:53
SumitNaiksatami would have preferred to not immediately model these as a resource, but hide them as operational details (driven via configuration)18:53
ivar-lazzaroigordcard: this may be one use, yes. But the tag resource I have in mind actually covers *all* the GBP resources for API consistency18:54
ivar-lazzaroSumitNaiksatam: but this would mean adding key-value attributes to certain resources, so an API change is still required right?18:54
igordcardany thought been given on allowing users to influence the behaviour of resources by applying tags  themselves?18:55
*** dtroyer has joined #openstack-meeting-318:55
SumitNaiksatamivar-lazzaro: in that case the service profile is completely internal, you only expose its description to the user18:55
ivar-lazzaroigordcard: I think those are "labels", and no we haven't discussed them yet18:55
igordcardin this case the tag resource would probably be something else18:56
igordcardivar-lazzaro, yeah18:56
SumitNaiksatamlets not call them tags, since it casuses confusion, i think meta-date is more appropriate here :-)18:56
SumitNaiksatamotherwise we will go around in circles even in this small group18:56
ivar-lazzaroSumitNaiksatam: I say we call them Endpoints!18:57
SumitNaiksatamivar-lazzaro: amen18:57
ivar-lazzaroSumitNaiksatam: eheh :)18:58
igordcardso, just to clarify, you intend to have service profiles defined by operators and used by tenants18:58
SumitNaiksatamigordcard: yes18:58
SumitNaiksatamperhaps we might not expose all attributes to users18:58
*** matrohon has joined #openstack-meeting-318:58
igordcardand "config" is the field where the user can input additional constraints/metadata/configs for the service?18:59
igordcardper https://review.openstack.org/#/c/174118/7/specs/kilo/gbp-service-chain-driver-refactor.rst : "Node Driver": "This configures the service based on the “config” provided in the Service Node definition."18:59
ivar-lazzaroigordcard: I actually think that the user should never interact with the services18:59
SumitNaiksatamigordcard: we already have a config in the “node” definition18:59
SumitNaiksatamigordcard: the meta-data i am referring to goes beyond that “config"19:00
ivar-lazzaroThe final user should only think "intent19:01
SumitNaiksatamivar-lazzaro: true, user will never directly interact with the service, that doesnt happen today either19:01
SumitNaiksatam*will never -> should never19:01
SumitNaiksatamokay we are a minute over19:01
SumitNaiksatam#topic Vancouver Summit prep19:02
*** openstack changes topic to "Vancouver Summit prep (Meeting topic: networking_policy)"19:02
SumitNaiksatamivar-lazzaro: rkukura: anything quick to discuss?19:02
igordcardivar-lazzaro, yes, yes, but if the intent can be expressed in a richer way, it may be beneficial19:02
SumitNaiksatamigordcard: you are coming to the summit?19:02
SumitNaiksatamyapeng: you are coming to the summit?19:02
igordcardSumitNaiksatam, unfortunately not :(19:02
SumitNaiksatamigordcard: oh bummer!19:02
ivar-lazzaroSumitNaiksatam: I'm trying to figure out a way to implement shared PRS for the RMD19:02
yapengyes i will come19:02
SumitNaiksatamivar-lazzaro: ah correct19:02
ivar-lazzaroSumitNaiksatam: I have a couple of ideas but I'm still trying to validate them19:02
SumitNaiksatamivar-lazzaro: that part was challenging as you mentioned19:03
ivar-lazzaroShould we discuss them in the gbp channel?19:03
SumitNaiksatamivar-lazzaro: thanks for taking that up19:03
SumitNaiksatamivar-lazzaro: sure19:03
*** wojdev has quit IRC19:03
SumitNaiksatamyapeng: good19:03
ivar-lazzaroI'd like to hear from the rest of the team, especially those with a richer Neutron background19:03
YiSumitNaiksatam: unfortunately, I cannot19:03
YiI won't be able to go to summit19:04
SumitNaiksatamYi: sorry, i did not notice that you had joinied, earlier i checked you were not19:04
SumitNaiksatamYi: damn thats a bummer19:04
Yiwas stuck in another meeting19:04
rkukuraivar-lazzaro: Is there something for us to look at to understand your ideas?19:04
SumitNaiksatamYi: lets sync up offline on that19:04
Yisure19:04
ivar-lazzarorkukura: I have nothing besides some code, but it's not published yet... Maybe we can discuss it on IRC and then I can publish a WIP?19:04
rkukuraivar-lazzaro: sure19:05
*** irenab has joined #openstack-meeting-319:05
ivar-lazzarorkukura: I wanted to write a spec but I don't know yet what will work! So it's not easy19:05
SumitNaiksatamone last thing19:05
rkukuraivar-lazzaro: IRC, email, hangout, whatever works best19:05
SumitNaiksatam#topic Refactor feature branch19:05
*** openstack changes topic to "Refactor feature branch (Meeting topic: networking_policy)"19:05
SumitNaiksatamyi and yapeng’s patches are finally all in19:06
yapengcool :)19:06
ivar-lazzarorkukura: anything is good for me, the sooner we discuss the best. Do you have time after the meeting?19:06
SumitNaiksatamYi: thanks so much for pursuing the last patch19:06
SumitNaiksatamwe will work towards merging them from the feature branch once we are done with the summit19:06
Yimy pleasure19:06
ivar-lazzaroyapeng: Yi: Thanks guys!19:06
SumitNaiksatamokay lets move to -gbp19:06
SumitNaiksatamthanks all, and apologies for going over19:07
SumitNaiksatambye!19:07
igordcardcya19:07
Yibye19:07
ivar-lazzarociaooo19:07
SumitNaiksatam#endmeeting19:07
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:07
openstackMeeting ended Thu Apr 30 19:07:09 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:07
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-04-30-18.01.html19:07
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-04-30-18.01.txt19:07
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-04-30-18.01.log.html19:07
rkukuraivar-lazzaro: give me a couple minutes, then ping me19:07
*** Yi has left #openstack-meeting-319:07
yapengbye19:07
rkukurabye19:07
*** kozhukalov has quit IRC19:10
*** irenab has quit IRC19:11
*** eghobo_ has quit IRC19:16
*** marun has quit IRC19:17
*** ttrifonov is now known as zz_ttrifonov19:18
*** VW_ has joined #openstack-meeting-319:18
*** B_Smith_ has quit IRC19:20
*** marun has joined #openstack-meeting-319:22
*** egallen has quit IRC19:30
*** egallen has joined #openstack-meeting-319:32
*** ajo has joined #openstack-meeting-319:33
*** kevinbenton has quit IRC19:33
*** d0ugal has quit IRC19:33
*** d0ugal has joined #openstack-meeting-319:34
*** kevinbenton has joined #openstack-meeting-319:35
*** mattgriffin has joined #openstack-meeting-319:40
*** mwang2 has quit IRC19:43
*** dtroyer has left #openstack-meeting-319:45
*** mwang2 has joined #openstack-meeting-319:48
*** marun has quit IRC19:54
*** marun has joined #openstack-meeting-319:56
*** jpena has joined #openstack-meeting-319:57
*** Shamail has joined #openstack-meeting-320:00
*** clouddon has joined #openstack-meeting-320:00
*** wojdev has joined #openstack-meeting-320:01
*** e0ne has quit IRC20:01
ShamailHi megm_, clouddon, mattgriffin20:02
mattgriffinhi Shamail: got a conflict today. so can't make it... on a call now :(20:02
ShamailGot it.  Do we want to cancel for today?  Did you finish the spec draft?20:02
ShamailI don't see Nick or Sam on either.20:03
megm_I'm here -- wasn't sure if we were canceled or not.20:03
megm_I think the main item is to review the spec20:03
ShamailI'm fine with canceling today, I could use any extra time I can get this week.20:03
mattgriffinack. spec is in progress/review20:04
ShamailAgreed megm_, I haven't checked it to see if mattgriffin was able to complete.20:04
megm_We have a draft spec20:04
*** baoli has joined #openstack-meeting-320:04
ShamailOkay, perfect.20:04
megm_https://review.openstack.org/#/c/178427/2/specs/liberty/ha-guide.rst20:04
Shamailopening now20:04
*** antares_ has joined #openstack-meeting-320:05
megm_I've made updates but they aren't getting to gerrit -- but you can see the comments and my responses FWIW20:05
clouddonsorry guys. system issues. connecting from mobile is painful20:05
ShamailI know clouddon, it is always hard on mobile.20:05
ShamailHow about we all take the AI to review the draft and make additional comments (I do see your comments megm_)20:06
clouddonthx. will check logs for action items. thx20:06
*** mattgriffin has quit IRC20:06
ShamailWe can regroup next week and have a quick sync before moving it forward.20:06
clouddon+1 on review AR20:06
ShamailDoes that work for you megm_?20:06
megm_Sounds like a plan.20:07
ShamailAlright, see you next week!20:07
*** baoli has quit IRC20:07
Shamailbye megm_, clouddon20:07
megm_Note that we need to implement intersphinx to accomodate xrefs with Install Guide20:07
clouddontataa20:07
*** jpena has quit IRC20:07
megm_http://sphinx-doc.org/latest/ext/intersphinx.html20:07
Shamailgood point.  We should capture that requirement in the TOC wiki?20:07
*** baoli has joined #openstack-meeting-320:07
megm_Good point -- I'll update the TOC20:08
Shamailalrighty20:08
Shamaillater!20:08
antares_hi folks. I'm new here :) I'm a RabbitMQ team member. We'd like to help with the docs.20:08
ShamailHi antares_, nice to meet you.20:08
megm_Welcome, antares!  We welcome your help and expertise!20:08
antares_we are not familiar with the OpenStack process, so learning along the way20:09
antares_currently we are collecting notes on what can be improved. Patches will follow hopefully next week.20:09
Shamailantares_: This is the HA guide update team.... Please review the meeting notes from our last meeting, they contain some useful links starting at 20:16:22 to ramp up on our objective and progress.20:10
Shamailhttp://eavesdrop.openstack.org/meetings/ha_guide/2015/ha_guide.2015-04-23-20.03.log.html20:10
antares_Shamail: thanks, will take a look20:10
ShamailWe are canceling our meeting for today due to conflicts but this is our regular time.  We will also be holding a face to face meeting at the OpenStack Summit in Vancouver (Meeting Room #16, Thursday (5/21) 10:45A to 12:30P PT)20:11
megm_Our current status is that we have a draft spec under review for the project.  After that is approved, we can set up source files, convert existing source from docbook to RST and move things around to match the proposed structure.20:11
ShamailI have to run, take care megm_ and look forward to working with you antares_20:12
Shamailttfn20:12
*** Shamail has quit IRC20:12
antares_so the structure is being changed? will this affect Kilo docs?20:12
megm_antares, it would be great if you could look at the TOC.  Top priority is explaining how the HA controller is config'ed, etc.20:13
megm_I think we have the right items identified; I'm less confident that we have them in the right order.20:13
antares_megm_: my goal is to improve the RabbitMQ sections. I'm not an expert on other things the HA guide covers.20:14
megm_The spec is now targeting Liberty.  But I did see your mail that you have info to add.20:14
antares_megm_: OpenStack doc changes will be pretty light. Most of the content we have in mind will go to rabbitmq.com.20:15
megm_antares: I understand.  But RabbitMQ is pretty central -- be sure that it is appearing at the right place, with all prerequisites done before that section20:15
antares_sure20:15
megm_I saw that you are creating a separate RabbitMQ guide, which is terrific!20:15
megm_Is it being coded in RST with intersphinx so we can readily xref between that guide and this one?20:16
antares_do you meet once a week same day same time or does it vary?20:16
antares_we don't use RST and our website is not yet open source (pushing that through legal)20:16
antares_we were thinking OpenStack docs could use plain old HTML anchors20:17
antares_would that work for you?20:17
megm_antares: Okay, so we need to figure out how we handle RabbitMQ.  Perhaps you guys can contribute some basic info to this guide then we just hand off to your guide as a whole for additional info?20:17
*** mattgriffin has joined #openstack-meeting-320:18
megm_antares, I'm not sure about the html anchors.  RST can xref them but, if the URLs include version info, you will need to manually maintain them20:18
antares_megm_: that's the plan20:18
antares_megm_: our URLs are not version-specific and probably won't be20:19
*** eghobo has joined #openstack-meeting-320:19
antares_we will keep the URLs working, even if we change them (doesn't happen often) via redirects20:19
megm_antares, that will solve some issues -- and create others if different software versions have different capabilities.  But that's all manageable, I'm sure20:19
*** Sukhdev has quit IRC20:20
antares_that's a fair point20:20
megm_Meanwhile, I think you have new information that needs to be added to the HA Guide for Kilo, right?20:20
antares_we'd like to update the Kilo version, yes20:21
megm_antares: we are missing key people today, alas.  But I think you can go ahead and patch the docbook source for Kilo this week.20:21
antares_sounds good20:21
megm_Nick Chase will be converting that to RST and setting up the new files as soon as the spec is approved, but I think you have a little window20:21
*** pballand has joined #openstack-meeting-320:22
antares_sorry, will the Kilo guides be ported to RST as well? or just Liberty?20:22
megm_Perhaps when you submit such patches, you could send email tagged [ha-guide] to alert us all to the patch20:22
antares_if it's only Liberty we can target that from the start20:23
antares_to openstack-docs, correct?20:23
megm_Then we can be sure it is merged before Nick converts those sections.  I'm not real sure how this all works but that seems reasonable20:23
megm_antares: you might want to check with Andreas, Anne, etc.20:24
*** Sukhdev has joined #openstack-meeting-320:24
megm_But I THINK that the docbook HA Guide that is out there is being used for Kilo.20:24
antares_we can wait for a bit, put more effort into the new rabbitmq.com guide. Then discuss what to do at the summit.20:24
megm_Then all that content will be converted to RST and incorporated into the appropriate place in the new structure for Liberty20:24
antares_I'll ask Anne20:24
megm_Is the new rabbitmq guide -- or what you have -- published?20:25
antares_thanks, this is very useful to know that you're about to migrate to RST20:25
antares_not yet, no. It will be once it is maybe 75% complete.20:25
antares_I'll announce it on the list20:25
megm_antares, my email is meg.mcroberts@yahoo.com if you want to chat offline before the next meeting.  Caveats that I only partially know whereof I speak ;-)20:26
megm_Shamail, are you still there?20:26
*** asahlin is now known as asahlin_afk20:27
megm_antares_afk,  sounds good.  I was hoping that we could at least link to your guide as soon as it is published.20:28
*** ajo has quit IRC20:28
megm_But I'm not sure about policies for augmenting docs after the release20:28
antares_megm_: if we have to target Liberty, it's OK20:28
antares_our goal is to continue contributing as things change20:29
megm_Whatever, I'm awfully glad you guys are doing this -- I know that people have a lot of questions about exactly how RabbitMQ works, etc20:29
antares_:)20:29
antares_we are always happy to answer questions on our mailing list (rabbitmq-users)20:29
megm_Excellent!  I think we have an unusual amount of turmoil right now as docs are being converted from docbook to RST, procedures are being established to accomodate the growth in contributors, etc.20:30
ekarlsowhat meeting is this btw ? ^^20:30
antares_megm_: I think we've hijacked a meeting room20:30
megm_Yes, the rabbit people have an excellent reputation.  Still, a guide that puts it all together is valuable20:30
*** emagana has quit IRC20:30
antares_ekarlso: sorry20:30
megm_ekarlso, this is the time slot for the HA guide but it's kind of a non-meeting today20:31
ekarlsoi was just wondering ;p20:31
*** egallen has quit IRC20:31
megm_Did you mean to be here for the HA Guide meeting?20:31
ekarlsomegm_: nope .)20:32
antares_megm_: thank you for your help. I'll keep joining HA guide meetings and hope to meet the doc team at the summit.20:32
megm_Excellent, antares!  Have a great week and we'll chat next week.20:32
antares_you too20:32
*** marun has quit IRC20:32
*** alexsyip has quit IRC20:33
*** antares_ has quit IRC20:33
*** ajo has joined #openstack-meeting-320:34
*** alexsyip has joined #openstack-meeting-320:37
*** Networkn3rd has quit IRC20:42
*** mwang2_ has joined #openstack-meeting-320:44
*** mwang2 has quit IRC20:47
*** mattgriffin has quit IRC20:48
*** marun has joined #openstack-meeting-320:59
*** melwitt has quit IRC21:04
*** melwitt has joined #openstack-meeting-321:04
*** melwitt has quit IRC21:05
*** melwitt has joined #openstack-meeting-321:05
*** VW_ has quit IRC21:10
*** bpokorny_ has joined #openstack-meeting-321:10
*** bpokorny has quit IRC21:14
*** huichun has quit IRC21:18
*** matrohon has quit IRC21:18
*** wojdev has quit IRC21:22
*** mwagner_lap has quit IRC21:22
*** Longgeek has quit IRC21:24
*** ryansb_ has joined #openstack-meeting-321:28
*** ryansb_ has joined #openstack-meeting-321:28
*** ryansb_ is now known as ryansb21:28
*** Longgeek has joined #openstack-meeting-321:28
*** nelsnelson has quit IRC21:29
*** VW_ has joined #openstack-meeting-321:30
*** carl_baldwin has quit IRC21:30
*** ajo has quit IRC21:32
*** alexsyip has quit IRC21:38
*** emagana has joined #openstack-meeting-321:39
*** stevemar has quit IRC21:39
*** bpokorny has joined #openstack-meeting-321:41
*** shwetaap has joined #openstack-meeting-321:42
*** bpokorny_ has quit IRC21:44
*** wojdev has joined #openstack-meeting-321:44
*** clouddon has quit IRC21:48
*** ryansb has left #openstack-meeting-321:48
*** alexsyip has joined #openstack-meeting-321:50
*** igordcard_ has joined #openstack-meeting-321:53
*** jgrimm is now known as zz_jgrimm21:53
*** igordcard has quit IRC21:55
*** irenab has joined #openstack-meeting-321:56
*** Rockyg has joined #openstack-meeting-321:58
*** peristeri has quit IRC21:58
*** emagana has quit IRC21:59
*** bknudson has quit IRC22:01
*** irenab has quit IRC22:01
*** Swami has quit IRC22:02
*** jckasper has quit IRC22:05
*** egallen has joined #openstack-meeting-322:08
*** melwitt_ has joined #openstack-meeting-322:11
*** melwitt_ has quit IRC22:11
*** melwitt has quit IRC22:12
*** sbalukoff has quit IRC22:15
*** armax has quit IRC22:15
*** wojdev has quit IRC22:15
*** Sukhdev has quit IRC22:19
*** Sukhdev has joined #openstack-meeting-322:20
*** jtomasek has quit IRC22:20
*** melwitt has joined #openstack-meeting-322:20
*** wojdev has joined #openstack-meeting-322:21
*** Piet has quit IRC22:26
*** sigmavirus24 is now known as sigmavirus24_awa22:27
*** VW_ has quit IRC22:33
*** wojdev has quit IRC22:34
*** sarob has quit IRC22:34
*** julim has joined #openstack-meeting-322:35
*** emagana has joined #openstack-meeting-322:36
*** igordcard has joined #openstack-meeting-322:39
*** emagana has quit IRC22:42
*** wojdev has joined #openstack-meeting-322:44
*** Piet has joined #openstack-meeting-322:44
*** emagana has joined #openstack-meeting-322:46
*** shwetaap has quit IRC22:48
*** yalie has joined #openstack-meeting-322:53
*** Swami has joined #openstack-meeting-322:55
*** bpokorny has quit IRC23:02
*** bpokorny_ has joined #openstack-meeting-323:02
*** marun has quit IRC23:05
*** baoli has quit IRC23:06
*** marun has joined #openstack-meeting-323:06
*** melwitt has quit IRC23:07
*** Sukhdev_ has joined #openstack-meeting-323:10
*** banix has joined #openstack-meeting-323:10
*** Sukhdev has quit IRC23:11
*** marun has quit IRC23:11
*** wojdev has quit IRC23:11
*** vgridnev_ has quit IRC23:13
*** egallen has quit IRC23:14
*** salv-orl_ has joined #openstack-meeting-323:14
*** fallenpegasus has quit IRC23:15
*** MarkAtwood has quit IRC23:15
*** salv-orlando has quit IRC23:17
*** wojdev has joined #openstack-meeting-323:19
*** wojdev has quit IRC23:24
*** absubram has quit IRC23:34
*** melwitt has joined #openstack-meeting-323:36
*** emagana has quit IRC23:38
*** marun has joined #openstack-meeting-323:40
*** emagana has joined #openstack-meeting-323:41
*** krtaylor has quit IRC23:44
*** irenab has joined #openstack-meeting-323:45
*** salv-orl_ has quit IRC23:46
*** mrmartin has joined #openstack-meeting-323:48
*** irenab has quit IRC23:50
*** banix has quit IRC23:51
*** Swami_ has joined #openstack-meeting-323:51
*** SumitNaiksatam has quit IRC23:54
*** Swami has quit IRC23:55
*** krtaylor has joined #openstack-meeting-323:56

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