Thursday, 2014-12-18

*** sunny_ has joined #openstack-meeting-300:00
*** bradjones has quit IRC00:01
*** bradjones has joined #openstack-meeting-300:03
*** pballand has joined #openstack-meeting-300:04
*** baoli has quit IRC00:09
*** sunny_ has quit IRC00:10
*** ChuckC has joined #openstack-meeting-300:11
*** sunny_ has joined #openstack-meeting-300:11
*** sarob has joined #openstack-meeting-300:11
*** xuhanp_ has joined #openstack-meeting-300:12
*** Rockyg has quit IRC00:14
*** SotK has quit IRC00:16
*** SotK has joined #openstack-meeting-300:16
*** sunny_ has quit IRC00:26
*** chuckC_ has quit IRC00:31
*** carl_baldwin has quit IRC00:33
*** xuhanp_ has quit IRC00:39
*** ChuckC has quit IRC00:44
*** yamamoto has joined #openstack-meeting-300:50
*** ongk has joined #openstack-meeting-300:52
*** ongk has quit IRC00:52
*** Amogh has quit IRC00:54
*** hinnant has quit IRC00:55
*** s3wong has quit IRC00:57
*** salv-orlando has quit IRC00:57
*** etoews has quit IRC00:57
*** lhcheng has quit IRC01:02
*** yapeng_ has joined #openstack-meeting-301:10
*** eliqiao has joined #openstack-meeting-301:10
*** MarkAtwood has quit IRC01:11
*** sarob has quit IRC01:12
*** ChuckC has joined #openstack-meeting-301:13
*** chuckC_ has joined #openstack-meeting-301:13
*** Sukhdev has quit IRC01:14
*** killer_prince is now known as lazy_prince01:14
*** yamamoto has quit IRC01:14
*** SridharRamaswamy has quit IRC01:25
*** mwang2_ has quit IRC01:26
*** SumitNaiksatam has quit IRC01:26
*** etoews has joined #openstack-meeting-301:31
*** obondarev has quit IRC01:32
*** bradjones has quit IRC01:32
*** obondarev has joined #openstack-meeting-301:33
*** glebo has joined #openstack-meeting-301:34
*** ivar-lazzaro has quit IRC01:37
*** dboik has joined #openstack-meeting-301:37
*** glebo1 has joined #openstack-meeting-301:46
*** wuhg has joined #openstack-meeting-301:47
*** glebo has quit IRC01:49
*** glebo1 has quit IRC01:50
*** glebo has joined #openstack-meeting-301:53
*** dboik_ has joined #openstack-meeting-301:53
*** stanzgy has joined #openstack-meeting-301:54
*** dboik has quit IRC01:56
*** salv-orlando has joined #openstack-meeting-301:58
*** salv-orlando has quit IRC02:03
*** markmcclain has joined #openstack-meeting-302:08
*** etoews has quit IRC02:09
*** david-lyle is now known as david-lyle_afk02:10
*** etoews has joined #openstack-meeting-302:10
*** Longgeek has quit IRC02:11
*** alexsyip has quit IRC02:19
*** baoli has joined #openstack-meeting-302:24
*** markmcclain1 has joined #openstack-meeting-302:24
*** markmcclain1 has quit IRC02:24
*** markmcclain1 has joined #openstack-meeting-302:24
*** markmcclain has quit IRC02:26
*** etoews has quit IRC02:30
*** armax has joined #openstack-meeting-302:34
*** amotoki has joined #openstack-meeting-302:38
*** SridharRamaswamy has joined #openstack-meeting-302:42
*** igordcard has joined #openstack-meeting-302:44
*** VW_ has joined #openstack-meeting-302:50
*** glebo has quit IRC02:53
*** igordcard has quit IRC02:53
*** VW_ has quit IRC02:55
*** lblanchard has joined #openstack-meeting-303:01
*** SumitNaiksatam has joined #openstack-meeting-303:02
*** lblanchard has quit IRC03:03
*** SridharRamaswamy has quit IRC03:03
*** lblanchard has joined #openstack-meeting-303:06
*** SumitNaiksatam has quit IRC03:10
*** lblanchard has quit IRC03:10
*** SumitNaiksatam has joined #openstack-meeting-303:10
*** dboik_ has quit IRC03:13
*** lblanchard has joined #openstack-meeting-303:13
*** dboik has joined #openstack-meeting-303:16
*** obondarev has quit IRC03:19
*** obondarev has joined #openstack-meeting-303:19
*** etoews has joined #openstack-meeting-303:22
*** reed has quit IRC03:23
*** julim has joined #openstack-meeting-303:29
*** yapeng_ has quit IRC03:41
*** yamamoto has joined #openstack-meeting-303:43
*** jaypipes has joined #openstack-meeting-303:44
*** lazy_prince is now known as killer_prince03:51
*** dboik has quit IRC03:56
*** emagana has quit IRC03:56
*** emagana has joined #openstack-meeting-303:58
*** banix has quit IRC04:01
*** emagana has quit IRC04:02
*** badveli has quit IRC04:05
*** sarob has joined #openstack-meeting-304:12
*** pballand has quit IRC04:14
*** sarob has quit IRC04:17
*** lblanchard has quit IRC04:19
*** killer_prince is now known as lazy_prince04:20
*** yamamoto has quit IRC04:21
*** lblanchard has joined #openstack-meeting-304:31
*** sweston has quit IRC04:35
*** carl_baldwin has joined #openstack-meeting-304:42
*** lblanchard has quit IRC04:45
*** yamamoto has joined #openstack-meeting-304:50
*** esp has left #openstack-meeting-304:52
*** ongk has joined #openstack-meeting-305:01
*** ongk has left #openstack-meeting-305:02
*** sarob has joined #openstack-meeting-305:05
*** SumitNaiksatam has quit IRC05:14
*** SumitNaiksatam has joined #openstack-meeting-305:17
*** etoews has quit IRC05:27
*** sarob has quit IRC05:30
*** salv-orlando has joined #openstack-meeting-305:33
*** markmcclain1 has quit IRC05:34
*** pballand has joined #openstack-meeting-305:37
*** salv-orlando has quit IRC05:37
*** carl_baldwin has quit IRC05:38
*** lazy_prince has quit IRC05:48
*** jemangs has quit IRC05:48
*** jemangs has joined #openstack-meeting-305:49
*** killer_prince has joined #openstack-meeting-305:49
*** killer_prince is now known as lazy_prince05:49
*** etoews has joined #openstack-meeting-305:53
*** etoews has quit IRC05:58
*** gcb has joined #openstack-meeting-306:06
*** k4n0 has joined #openstack-meeting-306:10
*** SridharRamaswamy has joined #openstack-meeting-306:28
*** tomoe_ has joined #openstack-meeting-306:29
*** MarkAtwood has joined #openstack-meeting-306:29
*** tomoe_ has quit IRC06:29
*** tomoe has joined #openstack-meeting-306:29
*** cgoncalves has quit IRC06:31
*** cgoncalves has joined #openstack-meeting-306:33
*** sergef has joined #openstack-meeting-306:34
*** mrmartin has joined #openstack-meeting-306:37
*** jtomasek has joined #openstack-meeting-306:38
*** pballand has quit IRC06:51
*** akamyshnikova_ has joined #openstack-meeting-306:52
*** akamyshnikova_ has quit IRC06:52
*** MarkAtwood has quit IRC06:53
*** mrunge has joined #openstack-meeting-306:58
*** kevinbenton has quit IRC07:06
*** kevinbenton has joined #openstack-meeting-307:08
*** vinay_yadhav has joined #openstack-meeting-307:14
*** jcoufal has joined #openstack-meeting-307:18
*** egallen has quit IRC07:20
*** armax has quit IRC07:21
*** sahid has joined #openstack-meeting-307:25
*** vinay_yadhav has quit IRC07:29
*** alexpilotti has joined #openstack-meeting-307:35
*** SridharRamaswamy has quit IRC07:38
*** gcb has quit IRC07:42
*** egallen has joined #openstack-meeting-307:45
*** egallen has quit IRC07:48
*** devvesa has joined #openstack-meeting-307:55
*** jtomasek has quit IRC07:57
*** egallen has joined #openstack-meeting-308:03
*** salv-orlando has joined #openstack-meeting-308:04
*** salv-orlando has quit IRC08:09
*** salv-orlando has joined #openstack-meeting-308:11
*** amotoki has quit IRC08:15
*** VW_ has joined #openstack-meeting-308:15
*** iovadia has joined #openstack-meeting-308:17
*** yamamoto has quit IRC08:18
*** VW_ has quit IRC08:20
*** matrohon has joined #openstack-meeting-308:21
*** zz_ttrifonov is now known as ttrifonov08:28
*** sarob has joined #openstack-meeting-308:31
*** sarob has quit IRC08:36
*** devvesa has quit IRC08:36
*** JeanBriceCombebi has joined #openstack-meeting-308:40
*** JeanBriceCombebi has quit IRC08:44
*** pino has joined #openstack-meeting-308:46
*** safchain has joined #openstack-meeting-308:55
*** safchain has quit IRC08:55
*** alexpilotti has quit IRC08:56
*** JeanBriceCombebi has joined #openstack-meeting-308:58
*** iovadia has quit IRC09:04
*** lazy_prince has quit IRC09:08
*** vinay_yadhav has joined #openstack-meeting-309:11
*** lazy_prince has joined #openstack-meeting-309:11
*** lazy_prince has quit IRC09:11
*** salv-orlando has quit IRC09:11
*** lazy_prince has joined #openstack-meeting-309:11
*** sergef has left #openstack-meeting-309:13
*** vinay_yadhav has quit IRC09:14
*** MaxV has joined #openstack-meeting-309:17
*** iovadia has joined #openstack-meeting-309:18
*** takadayuiko has joined #openstack-meeting-309:31
*** takadayuiko has quit IRC09:31
*** JeanBriceCombebi has quit IRC09:33
*** JeanBriceCombebi has joined #openstack-meeting-309:36
*** igordcard has joined #openstack-meeting-309:39
*** zz_johnthetubagu is now known as johnthetubaguy09:52
*** gilliard_afk is now known as gilliard09:57
*** mrmartin has quit IRC10:02
*** salv-orlando has joined #openstack-meeting-310:12
*** salv-orlando has quit IRC10:17
*** jtomasek has joined #openstack-meeting-310:24
*** alexpilotti has joined #openstack-meeting-310:35
*** sweston has joined #openstack-meeting-310:49
*** jemangs has quit IRC10:49
*** JeanBriceCombebi has quit IRC10:51
*** evgenyf has joined #openstack-meeting-310:52
*** jemangs has joined #openstack-meeting-310:55
*** stanzgy has quit IRC10:56
*** sweston has quit IRC10:59
*** devvesa has joined #openstack-meeting-311:00
*** ozamiatin has quit IRC11:03
*** egallen has quit IRC11:09
*** egallen has joined #openstack-meeting-311:10
*** salv-orlando has joined #openstack-meeting-311:12
*** eliqiao has quit IRC11:21
*** ilyashakhat has joined #openstack-meeting-311:26
*** evgenyf has quit IRC11:35
*** sergef has joined #openstack-meeting-311:36
*** pino has quit IRC11:40
*** VW_ has joined #openstack-meeting-311:52
*** pino has joined #openstack-meeting-311:55
*** VW_ has quit IRC11:56
*** salv-orlando has quit IRC11:59
*** pino has quit IRC12:03
*** Longgeek has joined #openstack-meeting-312:06
*** pino has joined #openstack-meeting-312:11
*** vkmc has joined #openstack-meeting-312:22
*** alexpilotti has quit IRC12:26
*** Longgeek has quit IRC12:33
*** Longgeek has joined #openstack-meeting-312:33
*** JeanBriceCombebi has joined #openstack-meeting-312:37
*** JeanBriceCombebi has quit IRC12:42
*** lazy_prince is now known as killer_prince12:47
*** VW_ has joined #openstack-meeting-312:47
*** lblanchard has joined #openstack-meeting-313:06
*** tomoe_ has joined #openstack-meeting-313:09
*** tomoe has quit IRC13:11
*** edleafe has quit IRC13:12
*** JeanBriceCombebi has joined #openstack-meeting-313:13
*** edleafe has joined #openstack-meeting-313:14
*** mwagner_lap has joined #openstack-meeting-313:19
*** pino has quit IRC13:19
*** pino has joined #openstack-meeting-313:19
*** yamamoto has joined #openstack-meeting-313:23
*** VW_ has quit IRC13:23
*** iovadia has quit IRC13:26
*** wznoinsk has quit IRC13:27
*** JeanBriceCombebi has quit IRC13:30
*** VW_ has joined #openstack-meeting-313:32
*** JeanBriceCombebi has joined #openstack-meeting-313:32
*** VW_ has quit IRC13:32
*** mrmartin has joined #openstack-meeting-313:40
*** jcoufal_ has joined #openstack-meeting-313:40
*** weiting has joined #openstack-meeting-313:40
*** JeanBriceCombebi has quit IRC13:41
*** jcoufal has quit IRC13:43
*** JeanBriceCombebi has joined #openstack-meeting-313:43
*** _crobertsrh is now known as crobertsrh13:44
*** Longgeek has quit IRC13:44
*** Longgeek has joined #openstack-meeting-313:45
*** xuhanp_ has joined #openstack-meeting-313:48
*** huichunlu has joined #openstack-meeting-313:48
*** kchen has joined #openstack-meeting-313:49
*** sigmavirus24_awa is now known as sigmavirus2413:50
*** yamamoto has quit IRC13:55
*** yamamoto has joined #openstack-meeting-313:56
SergeyLukjanovsahara folks, ping13:58
*** elmiko has joined #openstack-meeting-313:59
*** Bobby__ has joined #openstack-meeting-313:59
SergeyLukjanovelmiko, morning13:59
elmikoSergeyLukjanov: hey13:59
*** pino has quit IRC13:59
*** sigmavirus24 has left #openstack-meeting-313:59
SergeyLukjanov#startmeeting sahara14:00
openstackMeeting started Thu Dec 18 14:00:32 2014 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: sahara)"14:00
openstackThe meeting name has been set to 'sahara'14:00
*** zhipeng has joined #openstack-meeting-314:01
*** alazarev has joined #openstack-meeting-314:01
SergeyLukjanov#topic sahara@horizon status (croberts, NikitaKonovalov)14:02
*** openstack changes topic to "sahara@horizon status (croberts, NikitaKonovalov) (Meeting topic: sahara)"14:02
SergeyLukjanovcrobertsrh, NikitaKonovalov, please14:02
SergeyLukjanovany good things happening?14:02
crobertsrhStill a few patches waiting for review.14:02
NikitaKonovalovour changes are getting some attention14:02
NikitaKonovalovfrom Horizon team14:02
crobertsrhI'm still waiting for meaningful input from UX for UI rework ("wizards").  Will reping them again today.14:03
NikitaKonovalovso we'll probably get Job Executions table working properly soon14:03
SergeyLukjanovcrobertsrh, do you have some proposal for them?14:03
alazarevtwo of my horizon patched were merged14:03
*** Adri2000 has quit IRC14:03
alazarevtwo other are still on review14:04
*** thomasem has joined #openstack-meeting-314:04
crobertsrhI was hoping they would have proposals for me.  In the background, I'm starting a few thing though.  I will mock them up soon regardless of their input or lack thereof.14:04
SergeyLukjanovcrobertsrh, got it14:04
SergeyLukjanov#topic News / updates14:05
*** openstack changes topic to "News / updates (Meeting topic: sahara)"14:05
crobertsrhSpecs for template editing and default templates are up for comments.  Still some work needed there, but I wanted to get comments before vacation time.14:06
crobertsrhSkeleton blueprint for UI wizards is up as well14:07
elmikoi'm progressing further into creating the content for the data processing chapter of the security guide. i'm using as a place to collect ideas, so if anyone could take a look and post comments as the content grows that would be great. aside from that, reviews, and a few minor bug fixes.14:07
alazarevI was busy doing teampest tests for sahara, here is result:
SergeyLukjanovcrobertsrh, that's really cool14:07
alazarevplease review14:07
aignatovwell, I’ve uploaded my latest version of new pig example
aignatovwill add new job execution to integratin tests14:08
alazarev*teampest would be cool :)14:08
weitingAbout Pre-built CDH Plugin Image, cloudera is asking for a place to put their EULA and let the user accept the license.14:08
SergeyLukjanovelmiko, so, we'll have a chapter in openstack re sahara security?14:08
elmikoSergeyLukjanov: yes14:08
weitingIs there any suggestion for this?14:08
SergeyLukjanovweiting, heh, there is no way right now to do it14:09
SergeyLukjanovweiting, thanks for the update14:09
weitingHDP image don't need to do this?14:10
*** tellesnobrega has joined #openstack-meeting-314:10
weitingI mean is there any other similar experience for this?14:10
SergeyLukjanovweiting, hwx was ok with publishing their images14:11
*** Adri2000 has joined #openstack-meeting-314:11
*** Adri2000 has quit IRC14:11
*** Adri2000 has joined #openstack-meeting-314:11
elmikoweiting: hdp images don't do any sort of eula agreement14:11
weitingOk, got it. So maybe the CDH image cannot publish at this moment.14:11
*** mattf has joined #openstack-meeting-314:12
SergeyLukjanovwe should think about the mechanism to show license for plugins14:12
alazarevweiting, at which stage should user accept agreement?14:12
* mattf waves14:12
SergeyLukjanovmattf, morning :)14:12
weitingThey are asking to show the EULA when the user use it at first time.14:13
* mattf has to update his calendar14:13
mattfeula for what?14:13
* mattf finds chat log14:13
elmikoweiting: would that be the first time a user creates a cluster from those images?14:13
weitingEnd User License Agreement14:13
aignatovmattf: for cdh deployment14:13
*** tosky has joined #openstack-meeting-314:14
tosky(hi, the new time!)14:14
alazarevweiting, for cluster or for each instance?14:14
SergeyLukjanovtosky, yup, it's alt time each second week14:14
weitingYes, but I think it should be difficult to put a license when creating a cluster14:14
alazarevif we add new tab with agreement to UI... will this work?14:14
mattfweiting, who's requesting the eula?14:15
*** Nikolay_St has joined #openstack-meeting-314:15
mattflegal, prod, eng?14:15
weitingJust need one time to show and let the user accept it.14:15
mattfseems very wrong, but assuming it's necessary14:16
crobertsrhRight, just a one-time thing.  I think cluster create time is good.14:16
weitingCloudera ask to put the eula14:16
mattfcan they accept a eula before downloading / creating an image ?14:16
SergeyLukjanovmattf, it'll be the best option14:16
mattfa eula is very anti-automation14:16
SergeyLukjanovmattf, yeah...14:16
mattfand sahara is all about automation14:16
mattfstrikes me as a fundamental conflict14:17
SergeyLukjanovbut we still have dib14:17
weitingOk, I can ask them about to put the eula before downloading the image.14:17
crobertsrhWhat about launches from the CLI?14:17
mattfi'm curious who's asking for this because they might not have enough context14:17
aignatovalazarev’s approach would also work14:17
mattfweiting, do they have a eula before access their yum repositories?14:17
mattfalazarev, aignatov, it's weird tho. who should be accepting the eula? if an org buys openstack & cloudera, does each user accept or does IT?14:18
weitingI don't think they have, but I'm not sure.14:18
mattfis cloudera going to be producing the images?14:19
weitingNo, it's based on sahara-image-elements14:20
mattfimho the oracle jdk eula accept shouldn't be in the elements14:21
SergeyLukjanovso, looks like we need to iterate on it offline14:21
mattfi'm wary of adding another14:21
mattfSergeyLukjanov, wise14:21
SergeyLukjanovmattf, there is a switch to openjdk patch proposed14:21
mattfSergeyLukjanov, yeah, i +'d it, it's currently -workflow14:22
*** mattf has quit IRC14:22
*** mattf has joined #openstack-meeting-314:22
SergeyLukjanovdo we have any other topics to chat about?14:22
crobertsrhFor template editing, is it acceptable (or possible the *right*) thing to disallow editing of templates that are in use by a cluster.  This would be similar to how we don't allow in-use templates to be edited.  It would avoid quite a bit of work with keeping old versions of templates around.14:22
SergeyLukjanovmattf, sreshetniak is on vacation now and will finish it next week I think14:22
SergeyLukjanov#topic Open discussion14:22
mattfi'd like to discuss plugins w/ 3rd party deps14:22
*** openstack changes topic to "Open discussion (Meeting topic: sahara)"14:22
elmikoi'd like to discuss security14:23
mattfelmiko, you go first14:23
SergeyLukjanovcrobertsrh, I think so14:24
alazarevquick question, is any particular reason why we recommend using floating IPs for devstack with nova network? (this regarding
crobertsrhawesome.  I will rework the spec to reflect that, if nobody disagrees.14:24
*** thomasem has quit IRC14:24
weitingI will ask Cloudera if the eula can be put during downloading.14:24
weitingAnd we can discuss it offline.14:25
SergeyLukjanovcrobertsrh, but I think that it's ok to edit template that is in use only by other template14:25
*** Bobby__ has quit IRC14:25
SergeyLukjanovcrobertsrh, I mean node group tmpl and cluster tmpl14:25
crobertsrhYes, I agree with that.14:25
*** thomasem has joined #openstack-meeting-314:25
elmikook, i'm curious about our default position with regards to sahara security. namely do we have any positions surround stack operation?14:25
elmikoin specific things like, separation of users into projects, cluster sharing, data management, these types of topics.14:26
alazarevcrobertsrh, I don't understand why we disallow in-use template to be edited14:26
elmikoi'm asking because as i assemble the chapter for the sec guide, i'm left wondering if we have done any work to create a baseline expectation for our users with respect to how they should configure a sahara enabled stack?14:27
*** peristeri has joined #openstack-meeting-314:27
crobertsrhalazarev:  Editing an in-use template requires us to save the old template and update the reference in the that we can still accurately show the templates that formed that cluster.14:27
alazarevwe allow clusters and job to be deleted while there are job executions... what wrong with editing template while cluster is running14:27
SergeyLukjanovalazarev, because when we have cluster online from template - the template is in fact a spec for cluster and that means users expect that if they use the same template the same cluster wil be provisioned14:28
alazarevcrobertsrh, we copy all data to cluster, template is for reference only14:28
crobertsrhThe links in the UI go to the template itself14:28
SergeyLukjanovalazarev, job exec is just an event about starting job and job results are most probably aren't stored in the cluster14:28
SergeyLukjanovalazarev, templates are for creating the same cluster14:29
*** k4n0 has quit IRC14:29
crobertsrhI think it's essentially the same reason we don't let users delete templates that are in-use by a cluster.14:29
*** VW_ has joined #openstack-meeting-314:30
alazarevSergeyLukjanov, I could imagine scenario when users always create cluster using template X, and admins tune settings for it in the same time14:31
*** dboik has joined #openstack-meeting-314:31
SergeyLukjanovcrobertsrh, yup14:31
alazarevcrobertsrh, yeap, and I don't understand that either14:31
SergeyLukjanovalazarev, the question of dissallow in-use templates deletion and editing was discussed when we've been adding the templates14:31
SergeyLukjanovalazarev, and we even decided to not implement editing14:32
crobertsrhalazarev:  So you're thinking that when a template is edited, we would also push those changes (processes, configs, etc) to the cluster right away?14:33
alazarevSergeyLukjanov, may be it is time to discuss more :)14:33
SergeyLukjanovelmiko, honestly it's a very difficult question about security guidelines14:33
elmikoSergeyLukjanov: yea... ;)14:33
SergeyLukjanovalazarev, I'm still very sure that we shouldn't allow to edit and delete in-use templates, crobertsrh is for it too as I see14:33
crobertsrhI think it's consistent with everything else we do (to not allow it) and it avoids many possible complications.14:34
alazarevcrobertsrh, no, I mean that reference in cluster is for information only, I don't see much trouble if template was edited from time of cluster creation14:34
alazarevcrobertsrh, agree that it is consistent, I mean approach in general14:35
crobertsrhyou say consistent, but not great14:35
alazarevit makes things complicated, sometimes14:36
crobertsrhOk.  I will update the spec for now and we can continue the conversation there.  I don't want to eat-up the whole meeting with other topics waiting.14:37
alazarevbut I agree, this is a big topic for design sessions, not for IRC chat14:37
SergeyLukjanovmattf, what's about plugins with 3rd party deps?14:38
mattfi'm curious what the team's view is about supporting plugins that don't operate w/o a 3rd party (non openstack) dependency14:39
mattffor instance, the cdh plugin and cm_api14:40
mattfshould sahara only support plugins that are single sourced (
SergeyLukjanovmattf, IMO we just should document it, enable by default, but add a warning while starting sahara about missed dependency for plugin14:40
SergeyLukjanov(enable by default was about cdh)14:41
elmikoimo, i'm ok with plugins that have 3rd party deps, but i think the 3rd parties should help to ensure that the deps are available downstream14:41
elmikoSergeyLukjanov: enable by default creates issues for the downstream repackage though14:42
mattfSergeyLukjanov, i've been thinking about it as: user has to do a non-openstack install step to get the dep, it's reasonable to also have a config step14:42
SergeyLukjanovelmiko, if we'll add a warn and lack of the dependency will not break sahara than it's ok IMO14:42
mattfi'm curious if folks know what other projects are doing w/ this situation14:42
weitingActually, Cloudera is asking to put cm_api to CDH Plugin source code.14:43
elmikoSergeyLukjanov: ok, agreed with that14:43
SergeyLukjanovweiting, oh, interesting14:43
*** evgenyf has joined #openstack-meeting-314:43
mattfinteresting indeed14:43
weitingBut I think it's really hard for maintenance.14:43
SergeyLukjanovweiting, what's the argument for doing it?14:43
mattfi think we should have an opinion as a project, as well as discuss the cloudera case14:43
kchenwho will take the charge of maintaining that? I cannot image14:44
kchenmaintaining cm_api in cdh plugin14:44
weitingIt's open source and they accept to put it in Sahara.14:44
elmikokchen: good question14:44
mattfopenstack has a long history of copy-libs, but also has a well defined process for them14:44
toskywould it be a copy, while keeping the development of the library outside?14:45
mattfweiting, each new upstream cm_api release could be copied into the plugin?14:45
toskyI'm not sure this is the right approach (distributions will use the upstream one as much as possible)14:45
weitingYes. That's what they are asking for.14:46
mattftosky, alternatives seem to be not enabling the cdh plugin or trying to get cm_api into openstack14:46
weitingYes, I agree with tosky.14:46
mattfthose aren't good results imho14:46
weitingI think Cloudera don't have the resource to maintain cm_api, so tthey are asking for this.14:48
mattfweiting, is cm_api something cloudera uses elsewhere or has support for their customers to use?14:48
weitingYes, it's open to support for their customer.14:49
SergeyLukjanovprobably we should re-spin this question next meeting when sreshetnyak will be available too14:49
weitingBut they are focusing on java based cm_api.14:49
mattfit's almost another swift-fs situation14:50
SergeyLukjanovas I remember sreshetnyak was talking about having very simple cm api implemented in the plugin14:50
SergeyLukjanovlike it was done for intel plugin14:51
*** TravT has left #openstack-meeting-314:51
mattfthe next meeting i'll be at is 8 jan14:52
huichunluGood option, we currently use just few of cm_api call14:54
SergeyLukjanovhuichunlu, yeah, in fact we don't need it, only some basic funcs14:54
SergeyLukjanovmattf, ack14:54
SergeyLukjanovin RU NY holidays are Jan 1-1114:55
SergeyLukjanovbtw I'll be on meeting 8 jan, but not sure about other RU folks14:55
mattfok, let's table for the time being14:55
*** carl_baldwin has joined #openstack-meeting-314:56
SergeyLukjanova few mins left14:57
SergeyLukjanovanything else to discuss?14:57
elmikoi just want to bring this up again, i'd be happy to have any opinions, criticism, questions, etc...14:57
*** mrsmith has joined #openstack-meeting-314:58
alazarev"the next meeting i'll be at is 8 jan" - the same for me, and probably for the most of others14:58
elmikoi'm going to try and extrapolate our default sec. position from the available guides and my own common sense, so input is good =)14:58
SergeyLukjanovelmiko, last min promotions :)14:58
*** johnbelamaric has joined #openstack-meeting-314:58
*** huichunlu has quit IRC14:58
kchenwhat is the clock of next meeting?14:58
*** mlavalle has joined #openstack-meeting-314:58
elmikokchen: 1600UTC14:58
SergeyLukjanovokay, thanks folks14:59
SergeyLukjanovhave a good day/night/smth else14:59
aignatovelmiko: I’ll take a look on your spec14:59
*** openstack changes topic to "OpenStack Meetings ||"14:59
openstackMeeting ended Thu Dec 18 14:59:23 2014 UTC.  Information about MeetBot at . (v 0.1.4)14:59
elmikoaignatov: thanks!14:59
openstackMinutes (text):
mattfciao folks14:59
*** mattf has left #openstack-meeting-314:59
*** crobertsrh has left #openstack-meeting-314:59
toskyelmiko: 1600UTC?14:59
elmikotosky: yea, i thought that was alternating meeting schedule? (did i mess it up?)15:00
toskyif it's alternative, like today, then it's 1400UTC (it's 1500UTC now)15:00
toskyotherwise it's 1800UTC15:00
elmikoyes, my bad15:00
*** tholtzen has joined #openstack-meeting-315:01
toskyjust to be sure, another change and I would miss it :D15:01
carl_baldwinhi, L3 meeting time.15:01
elmikodefinitive source, 1800UTC15:01
toskyups, time to leave15:01
*** tosky has left #openstack-meeting-315:01
carl_baldwinno worries, thanks!15:01
weitingOk, thanks.15:01
*** kchen has left #openstack-meeting-315:01
*** elmiko has left #openstack-meeting-315:01
*** weiting has quit IRC15:01
*** huichunlu has joined #openstack-meeting-315:02
carl_baldwin#startmeeting neutron_l315:02
openstackMeeting started Thu Dec 18 15:02:02 2014 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:02
openstackThe meeting name has been set to 'neutron_l3'15:02
*** huichunlu has left #openstack-meeting-315:02
carl_baldwinhi all15:02
carl_baldwin#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:02
carl_baldwinLooks like I need to update the agenda a bit.15:02
carl_baldwinLooks like kilo-1 is today.15:03
*** mlavalle has quit IRC15:03
*** wuhg has quit IRC15:03
*** mlavalle has joined #openstack-meeting-315:04
carl_baldwinSpecs are winding down for kilo.15:04
carl_baldwinAre there any specs still lingering in the review queue that have not been finalized?15:04
carl_baldwin#topic L3 Agent Restructuring15:05
*** openstack changes topic to "L3 Agent Restructuring (Meeting topic: neutron_l3)"15:05
carl_baldwinpc_m: Are you around?15:06
carl_baldwinamuller: ?15:06
haleybbueller? :)15:06
*** tomoe_ has quit IRC15:06
*** etoews has joined #openstack-meeting-315:06
*** david-lyle_afk has quit IRC15:07
*** xuhanp_ has quit IRC15:07
carl_baldwinWell, Paul’s patch merged yesterday.  It had a few patches behind it that we should be able to merge soon.15:07
carl_baldwinmlavalle: hi15:08
mlavallecarl_baldwin: hi15:08
mlavalleI added the next episode to the process_router last nigh:
carl_baldwinmlavalle: I’ll have a look.  Could you edit the topic to “bp/restructure-l3-agent”?15:09
mlavalleit follows up on the comments that carl_baldwin and haleyb made to my previous patch about about defer_off and defer_on15:09
*** pc_m has joined #openstack-meeting-315:09
mlavallecarl_baldwin: yeah, I'll sure do that15:09
pc_msorry I'm late15:09
carl_baldwinpc_m: hi15:09
mlavalleafter that patchset I'll start moving methods to the router calss15:10
carl_baldwinpc_m: I see that your patch merged.15:10
carl_baldwinmlavalle: I started taking a crack at that yesterday.  It may take more than one person to tag team on that.15:10
mlavallecarl_baldwin: coll, let me know how can I help15:10
carl_baldwinpc_m: Will you be driving the adv svcs portion of that now?15:10
mrsmithI made good progress with dvr.py15:11
pc_mcarl_baldwin: sorry, late... portions of...?15:11
carl_baldwinmlavalle: I will post a WIP today with a start.  I thought I’d start with the floating ip methods.  The choice was a bit arbitrary but seemed as good as any.15:11
mrsmithmoving dvr metods, etc there15:11
mlavallecarl_baldwin: :-)15:11
haleybmlavalle: i will review your change today before i leave for holidays15:11
mlavallehaleyb: thanks!15:11
*** mrunge has quit IRC15:12
mrsmithcarl_baldwin: I can adjust once I see what your patch looks like15:12
carl_baldwinmrsmith: Great.15:12
carl_baldwinmrsmith: I will post what I have soon.  It will not pass tests but I’ll be working on that.15:13
mrsmithI also created a agents/common/ file to hold our constants15:13
*** JeanBriceCombebi has quit IRC15:13
carl_baldwinmrsmith: Is yours up as a WIP?15:13
mrsmithnot yet, probably today15:13
mrsmithUTs are passing, etc - just doing some cleanup15:14
carl_baldwinmrsmith: okay15:14
carl_baldwinSounds like we’ve got a lot of work going on.  Just be sure to use “bp/restructure-l3-agent” as the topic and I’ll track it and drive it as much as I can.15:15
mrsmithI am using mixins like the does15:15
*** amuller has joined #openstack-meeting-315:16
carl_baldwinmrsmith: I was just thinking yesterday about how to change from using a mixing to being a sub-class.15:16
carl_baldwinamuller: hi15:16
*** bradjones has joined #openstack-meeting-315:17
amullerSorry meeting ran late15:17
carl_baldwinamuller: thanks for making it.15:17
carl_baldwinamuller: Do you have time to address
mrsmithcarl_baldwin: sure... I was just going with small changes first15:17
amullercarl_baldwin: Not today :( We had a lot of L3 HA blocker bugs pop up lately15:18
carl_baldwinmrsmith: okay, sounds good.15:18
carl_baldwinamuller: Okay, I’ll take a look at it today.15:18
amullercarl_baldwin: Thank you15:19
*** Nikolay_St has quit IRC15:20
carl_baldwinamuller: You’re welcome.  I think we’ll be tag teaming much of this work to try to keep it going.15:20
carl_baldwinIs there anything else on refactoring that we need to discuss?15:20
*** JeanBriceCombebi has joined #openstack-meeting-315:20
carl_baldwin#topic bgp-dynamic-routing15:21
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:21
carl_baldwindevvesa: Hi15:21
carl_baldwinI think I’ll probably move this topic later in the agenda but I do not want to drop it.15:21
*** emagana has joined #openstack-meeting-315:21
devvesasure, no problem. I was about to ask you the same. Maybe even drop it for now if you want15:22
carl_baldwinFor now, I think our best bet is to continue the L3 agent refactoring so that it will be easier to eventually make the L3 changes needed to connect to L3 routed network.15:22
carl_baldwindevvesa: That is fine.  I’ll plan to add it back to the agenda around kilo-2.15:23
devvesaOk. I'll be in the available in the meetings anyway15:23
devvesaSo add it again anytime15:23
carl_baldwindevvesa: Thanks for all of your work.  It is good to have you here.15:23
devvesaThanks carl15:24
carl_baldwin#topic neutron-ipam15:24
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:24
carl_baldwinjohnbelamaric: hi15:24
carl_baldwinsalv-orlando: around?15:24
*** mageshgv has joined #openstack-meeting-315:25
*** chuckC_ has quit IRC15:25
carl_baldwinLooks like there is one more spec to merge.15:26
carl_baldwinWe kind of need this to continue with the other specs.15:26
*** nelsnelson has joined #openstack-meeting-315:27
johnbelamaricyes, have you heard anything from salv-orlando ?15:27
carl_baldwinjohnbelamaric: Looks like he’s been granted an extension until tomorrow to address the comments on the spec.  Probably because it is needed by our other specs that have been accepted.15:28
*** mattfarina has joined #openstack-meeting-315:28
johnbelamaricso - the plan now is to start work on refactor based on the WIP interface you have submitted?15:29
*** etoews has quit IRC15:29
carl_baldwinjohnbelamaric: Yes, I think so.  It would be nice to tie up any loose ends on the interface.  Would you have any time to see what is still needed?15:30
johnbelamariconce this spec has merged I think we can start on that - would be best to understand some of the plans here prior to refactoring15:30
johnbelamarici will take a look today15:30
carl_baldwinjohnbelamaric: Thanks.15:31
carl_baldwinThere is another related BP still in review.15:31
*** etoews has joined #openstack-meeting-315:31
carl_baldwinI don’t think it will fit in to kilo with the rest of the IPAM work.  But, it will be a very nice enhancement to IPv6 capabilities.15:32
johnbelamarici have not looked at that one, I will take a peek15:32
carl_baldwinjohnbelamaric: Thanks.15:35
carl_baldwinAnything else on IPAM?15:35
carl_baldwinI think we need to get the work on the reference implementation started soon.  I’ll talk to salv-orlando about that.15:36
*** belmoreira has joined #openstack-meeting-315:36
carl_baldwin#action carl_baldwin will sync with salv-orlando on reference implementation.15:36
johnbelamaricnothing more from me15:36
carl_baldwin#topic neutron-ovs-dvr15:36
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:36
carl_baldwinHad the dvr meeting yesterday.  Anything new since then?15:37
*** egallen has quit IRC15:37
*** egallen has joined #openstack-meeting-315:37
carl_baldwinmrsmith: My impression yesterday is that there are a lot of reviews in play for dvr.15:37
mrsmithI started the refactoring effort as we discussed above15:37
*** egallen has quit IRC15:38
carl_baldwinMore than I can wrap my head around.15:38
mrsmithyes - there are a few patches in review15:38
mrsmithmanual snat move, agent restart, ipv6, l3-ha15:38
mrsmithmultiple ext nets15:38
mrsmithwe are actively working on them all :)15:39
mrsmithfunctional tests also15:39
mrsmithalso trying to debug and isolate failures on the experimental tempest job15:39
*** VW_ has quit IRC15:39
carl_baldwinmrsmith: Speaking of which, it looks like the failures are spiking again today.15:40
mrsmithahh... spikes are different... usually a clear breakage15:40
carl_baldwinYes, it looks like we have another breakage.  :(15:41
carl_baldwinYesterday the failure rate was tracking much closer to that of check-tempest-dsvm-neutron-full15:41
*** mageshgv has quit IRC15:41
mrsmiththats the goal15:42
carl_baldwinWhat is it about Thursdays and this test job?15:42
mrsmithI'll spend some cycles looking at this new breakage15:42
carl_baldwinmrsmith: Thanks.15:42
carl_baldwinAnything more on dvr?15:43
carl_baldwin#topic l3-high-availability15:44
*** openstack changes topic to "l3-high-availability (Meeting topic: neutron_l3)"15:44
carl_baldwinamuller: You mentioned L3 HA bugs?  Is there anything you want to discuss or mention here?15:44
*** markmcclain has joined #openstack-meeting-315:44
amullerWe're doing some internal testing of L3 HA15:44
amullerand found a few issues. There's also been some bugs reported by the community in the last couple of weeks15:44
amullerI've been managing the l3-ha bugs list15:44
amullerCarl I'll ping you when I feel a fix is ready for any of these bugs15:45
*** gholler has joined #openstack-meeting-315:45
amullercurrently some fixes are missing, some are in review and not yet ready15:45
*** elmiko has joined #openstack-meeting-315:46
amullerThere's one which I would appreciate some thoughts on: Making L3 HA and l2pop work, is important both for L3 HA and to eventually integrate L3 HA and DVR. Mike Kolesnik has started a mailing list thread about this.15:46
carl_baldwinamuller: Do you have a link for that one handy15:46
amullerIt's called [openstack-dev] [Neutron][L2Pop][HA Routers] Request for comments for a possible solution15:47
carl_baldwinAh, ML thread.  I’m with you now.15:47
amullerThat's it for me15:47
carl_baldwinamuller: Thanks.15:48
*** stevelle has joined #openstack-meeting-315:50
carl_baldwin#topic Open Discussion15:50
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:50
carl_baldwinThanks everyone!15:52
amullercarl_baldwin: Thank you15:52
*** openstack changes topic to "OpenStack Meetings ||"15:52
openstackMeeting ended Thu Dec 18 15:52:30 2014 UTC.  Information about MeetBot at . (v 0.1.4)15:52
openstackMinutes (text):
mlavallecarl_baldwin: no meetings next 2 weeks?15:52
*** mrsmith has quit IRC15:52
carl_baldwinmlavalle: Ah, good question.  Not next week as it will land right on Christmas and I’ll be with my family.15:53
carl_baldwinI will communicate on the ML soon.15:53
mlavallecarl_baldwin: :-)\15:53
*** pc_m has left #openstack-meeting-315:54
*** johnbelamaric has left #openstack-meeting-315:54
*** VW_ has joined #openstack-meeting-315:54
*** mageshgv has joined #openstack-meeting-315:55
*** isviridov_away has joined #openstack-meeting-315:55
*** kozhukalov has joined #openstack-meeting-315:55
*** tholtzen has quit IRC15:56
*** dtroyer has joined #openstack-meeting-315:56
*** sigmavirus24 has joined #openstack-meeting-315:59
*** amuller has left #openstack-meeting-316:00
*** ttrifonov is now known as zz_ttrifonov16:00
etoews#startmeeting api wg16:00
openstackMeeting started Thu Dec 18 16:00:30 2014 UTC and is due to finish in 60 minutes.  The chair is etoews. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: api wg)"16:00
openstackThe meeting name has been set to 'api_wg'16:00
*** isviridov_away is now known as isviridov16:00
etoewsseasons greetings :)16:01
etoews#topic agenda16:01
*** openstack changes topic to "agenda (Meeting topic: api wg)"16:01
sigmavirus24I season my greetings lightly but that's personal taste16:01
etoews#topic api definition formats16:02
*** openstack changes topic to "api definition formats (Meeting topic: api wg)"16:02
elmikoswagger go-go16:02
etoewselmiko: was it you that brought this up at the end of the last meeting?16:02
*** david-lyle has joined #openstack-meeting-316:02
etoewsswagger a go-go16:02
elmikomainly in the guise of creating a swagger generator for sahara16:02
etoewsguises are good16:03
etoewscan you share that link again?16:03
elmikothe larger effort i was getting at was trying to generate something for the api-ref website16:03
etoewsthat is a larger effort16:03
etoewsbut worthwhile16:03
*** geography76 has joined #openstack-meeting-316:03
elmikoit's pretty basic so far, but generates the minimum required doc for swagger2.016:03
etoewsdo you have the generated doc somewhere?16:04
elmiko1sec, i can make one16:04
etoewssure then gist or paste or whatever16:04
etoewsso let's discuss the more general issue16:04
*** ryansb has joined #openstack-meeting-316:05
etoewsi'm totally in favour of having api definition formats a thing that the api wg advocates for. that is to say, i think it's in scope for us. thoughts?16:05
elmikototal agreement from me16:05
stevelleyes please16:06
sigmavirus24etoews: agreed16:06
etoewsalright. i need to update the scope section of the wiki page anyway.16:06
etoews#action etoews update the scope section of the wiki page and include api definition format16:07
etoewsat the moment i'm totally undecided on which one we should recommend or even if we should recommend one.16:07
elmikoif we are going to have them all on api-ref we need to at least provide a set of formats that are acceptable16:08
etoewsis it better to just say we recommend an api def format, here are some examples.16:08
elmikowadl is ok, if you like xml. but i'm finding swagger pretty easy to work with.16:08
etoewsso here's another thing16:08
elmikoalso it has some nice overlap with jsonschema stuff16:09
isviridovIs swagger integrated with sphinx somehow?16:09
isviridovOr any other tool>16:09
elmikoisviridov: that's a good question16:09
etoewsone of the reasons i think wadl wasn't as useful as it could have been was because it was used as a documentation format.16:09
etoewswe don't need documentation. we need definition.16:09
etoewswe need the projects to own these definition files.16:10
etoewsthe defs should be the contract between client and server16:10
isviridovbut it would be great to generate some documentation from definition in already adopted format. I mean sphinx16:10
elmikoisviridov: +116:10
etoewsso rather than having api-ref be the place where these defs live16:11
sigmavirus24I worked on a ruby project that used json schema to enforce a contract on a live server between client and server code16:11
etoewsthe defs live in the individual projects16:11
etoewsand api-ref makes use of them16:11
elmikoetoews: would the idea be that api-ref would pull from the projects?16:11
sigmavirus24I have a case-study up that we can look to as a reference for architecture if we're interested in something like that16:12
etoewselmiko: something like that16:12
elmikosigmavirus24: post a link!16:12
etoewssigmavirus24: yes. that's the direction we need to go.16:12
sigmavirus24I had thought of doing a case-study app with flask for simplicity but never got around to it16:12
etoewsotherwise it's just another doc format that lags behind what the def actually is16:12
*** evgenyf has quit IRC16:12
sigmavirus24I let my former employer publish it a few weeks ago for reasons like this :P16:12
stevelleisviridov: do you have much familiarity with swagger?16:12
isviridovstevelle not yet16:13
etoewsi talked to the barbican folks about adopting a model like this. api def first dev.16:13
etoewsthey were open to the idea16:13
isviridovelmiko thx16:13
stevelleisviridov: swagger has tools to publish good human-readable documentation16:13
etoewsbut didn't have dev time to commit to it16:13
isviridovstevelle I see16:14
*** markmcclain has quit IRC16:14
etoewsif we could help projects bootstrap their api def efforts, that might be one way to make it stick.16:14
etoewswe would also want to demonstrate the benefits the project gained from adopting an api def16:15
*** mageshgv has quit IRC16:15
sigmavirus24one thing i should mention is that this ruby project also used the API definition files to test/build clients and would probably be awesome to have something similar for openstack APIs16:15
*** marun has joined #openstack-meeting-316:16
etoewssigmavirus24: you're reading my mind16:16
*** carl_baldwin has quit IRC16:16
etoewsdoes anybody have the time to create a swagger def for barbican?16:16
etoewsi wouldn't have time for it until next year but am willing to do it16:17
elmikoetoews: i've been looking into barb, i could take a pass at it16:17
etoewselmiko: have you seen the barb api "docs"16:17
elmikoetoews: yes16:17
sigmavirus24etoews: "docs"16:17
elmikoetoews: i might go through their pecan impl to pull out the swagger spec though16:18
etoewssome wiki page somewhere.16:18
etoews_goes off to find link_16:18
elmikoi believe it's still under the cloudkeep stuff16:18
etoewsthe "docs" aren't sooooo bad :)16:19
etoewsthere are worse16:19
sigmavirus24oh etoews the other thing is that this format allowed for microversioning16:19
*** mlavalle has left #openstack-meeting-316:19
elmikotheir definitely workable, but non-ideal16:19
etoewssigmavirus24: "this format" == ??16:19
sigmavirus24*the ruby project I referenced earlier16:19
etoewssigmavirus24: which is the api def format file in that project?16:21
* sigmavirus24 goes to get a link16:21
elmikoetoews: if i generate something for barb, should i just toss it on github?16:21
sigmavirus24 etoews16:21
sigmavirus24given how sinatra/rack work, the params in the URL are also documented in teh format so it's not just request/response body16:22
etoewselmiko: yes. at that point we can take it to the ml and see what barbican thinks.16:22
elmikoetoews: cool16:22
etoews#action elmiko to generate swagger doc for barbican and commit to github somewhere16:23
etoewssigmavirus24: i that it that's a format defined by the framework?16:23
sigmavirus24etoews: interpol is the library there16:24
sigmavirus24we don't have to follow it to the T16:24
sigmavirus24but interpol is just using jsonschema under the covers16:24
etoews"Interpol is an open source toolkit for policing your HTTP JSON interface maintained by Moz. It uses YAML files with definitions of the expected request and the promised response. These are called endpoint definitions. Caravan uses Interpol to enforce a contract with the consumer of the JSON interface."16:24
etoewsi think we'd want to go with a more broadly known/accepted format moving forward though16:25
sigmavirus24but the behaviour is what I care about personally16:25
sigmavirus24it's just a concrete example16:25
etoewsi particularly like "policing your HTTP JSON interface"16:25
sigmavirus24It's a strategy used by and it works really reallly well for them16:25
etoewssuch things require much policing16:26
sigmavirus24I'm not sure how much of their architecture I can talk about though =P16:26
etoewsunderstood. thanks for the concrete example though.16:26
sigmavirus24you're quite welcome16:26
etoewswhat actually might be really helpful is if you could elaborate on the real benefits moz saw from adopting an api def.16:27
etoewswe should discuss this on the ml16:27
sigmavirus24I'll write up a document to that effect16:27
etoewsmore viz16:27
sigmavirus24Action item forme?16:27
elmikoi think another question about these generated formats is how much do we want to talk about generating the base reference, and then hand tailoring with custom info(e.g. descriptions)?16:27
sigmavirus24s/forme/for me/16:27
etoewssigmavirus24: as in starting the discussion on the ml or just documenting benefits.16:28
*** MaxV has quit IRC16:28
etoewshmmmm...the benefits could be a reply to the discussion16:28
*** bradjones has quit IRC16:28
etoewselmiko: that's a good point. i'm not sure.16:29
*** pballand has joined #openstack-meeting-316:29
elmikomy understanding is that the wadl present on api-ref is a mix of auto-generate and handhack16:29
etoewsif these formats are maintained by the projects themselves, it might be too much of a burden for them.16:29
sigmavirus24etoews: roger that16:29
etoewsat least initially.16:30
etoewssigmavirus24: okay. i'll kick off a discussion and if you could reply with the benefits that would be really helpful.16:30
elmikoetoews: would be awesome to see some sort of oslo package that could help with the generation16:30
sigmavirus24etoews: will do16:30
etoews#action etoews start discussion about api def formats on ml16:30
*** bradjones has joined #openstack-meeting-316:31
etoews#action sigmavirus24 reply to discussion with benefits moz saw from using an api def format16:31
*** mageshgv has joined #openstack-meeting-316:31
etoewselmiko: i hadn't considered that. that could work.16:31
elmikoi'm just thinking about how we could create something that would help the projects maintain their refs16:32
etoewselmiko: are you thinking generate the api def formats from the code using an oslo package?16:32
elmikoetoews: not completely, but something to help.16:32
stevellemany frameworks have decorators or the like to help with generating swagger docs.16:32
elmikowe have enough different wsgi impls that we probably can't have a single package to generate16:32
stevellepecan doesn't, though16:33
elmikostevelle: yea... =(16:33
elmikonice thing about swagger though, is that json is easy to generate from python16:33
etoewsthis is all good fodder for a discussion on the ml16:33
elmikoetoews: agreed16:34
etoewswe should move on16:34
etoews#topic previous meeting action items16:34
*** openstack changes topic to "previous meeting action items (Meeting topic: api wg)"16:34
etoewshmmmm...i don't think miguelgrinberg or ycombinator are around16:35
sigmavirus24miguelgrinberg: might show up late16:36
sigmavirus24but he may also just not show up16:36
*** annegent_ has joined #openstack-meeting-316:36
*** Networkn3rd has joined #openstack-meeting-316:37
etoewsgotcha. i do see he started a metadata guideline.16:37
*** Networkn3rd has quit IRC16:37
etoewsso something i think we need to start doing more of is this.16:37
etoews#1 under #link
etoewsanalyze current design16:38
etoewsi don't want the wg to act like we're creating guidelines in a vacuum.16:39
stevellethere was another review I looked at yesterday, on addressing collections, that also did that.16:39
elmikoetoews: +116:39
etoewsokay. i'm going to make a point about that on the ml.16:40
*** geography76 has quit IRC16:40
etoewsi have a feeling like it might uncover some gremlins16:40
etoewsare we striving for a good enough design that's consistent or are we striving for an ideal like hateoas?16:41
sigmavirus24etoews: why not both?16:42
sigmavirus24pragmatic with a hint of idealism is what I've been thinking of personally16:42
etoewsanyway, i just suspect that might fall out of such a discussion.16:42
etoewsi might be over thinking it though.16:42
*** debauer_ has joined #openstack-meeting-316:42
elmikosigmavirus24: +116:43
etoews#action etoews start discussion on ml about doing more analysis of current design and not creating guidelines in a vacuum16:43
annegent_a light scent of idealism should be detected :)16:43
annegent_+1 for more analysis of current state16:43
*** carl_baldwin has joined #openstack-meeting-316:43
etoewsannegent_ has joined the game16:44
*** pino has joined #openstack-meeting-316:44
annegent_put me in, coach!16:44
etoewsback on prev action items.16:44
etoewsi pinged jaypipes about merging some of the guidelines. he merged the infra ones and commented on others.16:45
etoewsnot much time left.16:45
etoews#topic APIImpact16:46
*** openstack changes topic to "APIImpact (Meeting topic: api wg)"16:46
etoewsblerg. anything we can discuss in 5 min?16:46
sigmavirus24 should be simple enough16:47
sigmavirus24also it's mine =P16:47
etoewsthat's fair. :)16:47
sigmavirus24glance supports downloading images in chunks (only when using the filesystem as a store) but doesn't return 206 when it responds properly. the problem is that every other storage device doesn't respect it16:47
sigmavirus24so it needs to change so that it returns the proper status code but can also simultaneously support the operation properly so there are some changes in the pipeline for that16:48
sigmavirus24It has APIImpact in the sense we're changing status codes midstream and I'm not convinced it's a good idea even if it's the right thing =P16:49
annegent_I think our guidance generally was the guidelines can be applied to current API definitions but are meant for future designs.16:49
*** yamamoto has quit IRC16:50
etoewsfrom the patches i can't tell what the status code was originally16:50
sigmavirus24Which is correct when downloading the entire image at once16:50
etoewsis that even remotely practical?16:51
etoews(download the entire image at once)16:51
*** banix has joined #openstack-meeting-316:51
ryansbon 10G sure16:51
*** debauer_ has left #openstack-meeting-316:52
sigmavirus24this is probably off-topic at this moment16:52
etoewsi don't think so16:52
etoewsa 206 seems perfectly reasonable16:52
ryansbI mean, an 8gb image would take around 8 seconds on a 10gigabit link16:52
etoewsor necessary really16:52
etoewsryansb: assuming the network is reliable. ;)16:53
sigmavirus24etoews: yeah.16:53
sigmavirus24I meant the practicality of downloading the entire image is probably out of scope for discussion16:53
etoewsah yes. my tangent.16:53
*** armax has joined #openstack-meeting-316:54
sigmavirus24but yeah, this makes me wonder if we should be defining all status codes (like usage of 206) in the WG too16:54
sigmavirus24we've had enough yaks shaved over 201/204 on creation and such16:54
etoewsi think so16:54
etoewsif there had been a guideline for something like this in the first place the proper status code might have even gotten used!16:55
sigmavirus24there is a guideline... it's RFC 723316:55
dtroyereven in the case of the 201/204 discussion, we should document that even if no clear reccommendation is made to attempt to at least short-circuit the next time that discussion arises16:55
etoews5 min left. i think we'll have to skip the guidelines topic.16:56
elmikodtroyer: +116:56
etoewsdtroyer: +116:56
etoewswe can also think of the guidelines as providing mental heuristics for others.16:56
elmikoit's tough work, especially getting a consensus, but very valuable to at least have a guide for response codes16:56
etoews#topic open topics16:56
*** openstack changes topic to "open topics (Meeting topic: api wg)"16:56
etoewsi'm assuming we're canceling next week's meeting. ;)16:57
*** sweston has joined #openstack-meeting-316:57
elmikomakes sense16:57
stevelle+1 that16:57
etoewsshould probably cancel the week after too.16:57
etoewsso cancel dec. 24 and jan. 1.16:58
etoewsanything else anybody wants to fire off in 2 min or less?16:58
elmikohappy holidays?16:58
etoewshappy holidays16:59
sigmavirus24enjoy the two week break?16:59
etoews(note the lack of question mark)16:59
elmikothat's why i plus oned ;)16:59
etoewsawesome. thanks everyone!16:59
*** ryansb has left #openstack-meeting-317:00
sigmavirus24thanks etoews17:00
elmikohave fun all!17:00
*** openstack changes topic to "OpenStack Meetings ||"17:00
openstackMeeting ended Thu Dec 18 17:00:17 2014 UTC.  Information about MeetBot at . (v 0.1.4)17:00
*** pballand has quit IRC17:00
openstackMinutes (text):
*** stevelle has left #openstack-meeting-317:00
*** sigmavirus24 has left #openstack-meeting-317:01
*** ivar-lazzaro has joined #openstack-meeting-317:01
*** mrmartin has quit IRC17:01
*** dtroyer has left #openstack-meeting-317:03
*** belmoreira has quit IRC17:07
*** sahid has quit IRC17:15
*** bpokorny has joined #openstack-meeting-317:15
*** mwang2 has joined #openstack-meeting-317:18
*** bpokorny has quit IRC17:19
*** elmiko has left #openstack-meeting-317:19
*** gholler has quit IRC17:21
*** pino has quit IRC17:23
*** dboik has quit IRC17:27
*** markmcclain has joined #openstack-meeting-317:32
*** sergef has quit IRC17:35
*** dboik has joined #openstack-meeting-317:37
*** etoews has quit IRC17:41
*** mrmartin has joined #openstack-meeting-317:42
*** reed has joined #openstack-meeting-317:44
*** KrishnaK has joined #openstack-meeting-317:47
*** devvesa has quit IRC17:48
*** alexsyip has joined #openstack-meeting-317:48
*** yamamoto has joined #openstack-meeting-317:50
*** sunny_ has joined #openstack-meeting-317:54
*** yamamoto has quit IRC17:56
*** sunny_ has quit IRC17:58
*** sunny_ has joined #openstack-meeting-317:59
*** rkukura has joined #openstack-meeting-318:00
*** s3wong has joined #openstack-meeting-318:01
SumitNaiksatamrkukura: banix KrishnaK mageshgv: hi18:01
SumitNaiksatam#startmeeting networking_policy18:01
openstackMeeting started Thu Dec 18 18:01:58 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: networking_policy)"18:02
openstackThe meeting name has been set to 'networking_policy'18:02
SumitNaiksatams3wong: hi18:02
SumitNaiksatam#info agenda
SumitNaiksatamwe are closing in on the release ;-)18:02
SumitNaiksatamso we are on track to wrap up the features and bugs by tomorrow18:03
SumitNaiksatamlets go over the details18:03
SumitNaiksatam#topic Bugs18:04
*** openstack changes topic to "Bugs (Meeting topic: networking_policy)"18:04
SumitNaiksatamthere is one open critical bug: #link
SumitNaiksatammageshgv: i believe this is addressed18:04
mageshgvSumitNaiksatam: Yes, Right now this is done in the same patch as hierarchial redirects, May be we want to separate them ?18:05
SumitNaiksatammageshgv: i believe those are related (as far as your implementation is concerned)18:06
SumitNaiksatammageshgv: so i think its fine18:06
SumitNaiksatammageshgv: thanks for working on this18:06
mageshgvSumitNaiksatam: yes, thats right. ok18:06
SumitNaiksatamwe have a bunch of high and medium priority bugs18:06
SumitNaiksatami have a few high on my plate18:07
SumitNaiksatamrkukura: you have some, right?18:07
SumitNaiksatamsome might be targeted for the next release though18:07
rkukuraSumitNaiksatam: Only one that I think is worth fixing now.18:07
rkukuraOr may be.18:07
SumitNaiksatamrkukura: ok, link?18:07
rkukuraLets make sure defering the other two is OK18:08
rkukuraThis is the nova bug where pre-created ports get deleted on VM delete18:08
*** nbouthors has joined #openstack-meeting-318:09
rkukuraivar-lazzaro had committed a workaround, and I don’t think we need to do anything more right now.18:09
SumitNaiksatamrkukura: yes, there is pending patch in Nova18:09
SumitNaiksatamrkukura: agree18:09
rkukuraWe need to pressure nova to rebase and review the fix18:09
SumitNaiksatamrkukura: yeah its pending for a long time18:09
rkukuraThe other I think we can defer is
SumitNaiksatamacross releases18:10
ivar-lazzarorkukura: maybe just the delete subnet when BadRequest occurs?18:10
*** tellesnobrega has left #openstack-meeting-318:10
rkukuraThis is the one were subnets get created for overlapping IPs18:11
ivar-lazzarorkukura: ops :)18:11
rkukuraivar-lazzaro did a workaround, and the real fix is to use the subnet pool feature planned for neutron in kilo18:11
SumitNaiksatamrkukura: got it18:11
rkukurathe one thing we might do now on this one is to delete the subnet when adding the interface to the router results in BadRequest18:12
rkukurawith the workaround, this could occur still occur with concurrent threads, but is not likely18:12
SumitNaiksatamrkukura: ah ok18:12
rkukuraso I think we could do that on the stable/juno branch at some point if needed18:12
SumitNaiksatamrkukura: can we have a separate bug to track this?18:13
SumitNaiksatamrkukura: just the delete subnet18:13
rkukuraSumitNaiksatam: I think we can use the current bug, since the subnet pools are addressed in the “does not scale” bug18:13
SumitNaiksatamrkukura: okay18:14
rkukuraSumitNaiksatam: Does that make sense? We’d target stable/juno I guess18:14
*** jaypipes is now known as jaypipes-afk18:14
rkukuraLast high priority bug is
SumitNaiksatamrkukura: yes, for critical bug fixes we plan to back port18:14
rkukuraThis is where updating the L2 policy fails18:14
SumitNaiksatamrkukura: yes, you are planning to fix that?18:15
rkukuraI could do this one today if needed, I think18:15
*** ivar-lazzaro has quit IRC18:15
SumitNaiksatamrkukura: okay great, we will have quick review turnaround on this18:15
rkukuraI’m not clear on whether we really want to allow updating a PTG’s L2P at all for the RMD18:16
SumitNaiksatamideally i would like to clear up the review queue for any non-vendor related patched by EoD (today)18:16
SumitNaiksatamtomorrow we can do vendor patches (ODL and Nuage)18:16
rkukuraWe cannot update it if any PTs exist in the PTG18:16
SumitNaiksatamrkukura: true since we cannot move the PTs18:16
rkukuraIs it OK to simpy reject any changes to the PTG’s L2P?18:16
*** GeoffArnold has joined #openstack-meeting-318:16
SumitNaiksatamyes, perhaps better to codify that in the driver thought?18:17
SumitNaiksatamin case some other backend is able to support this?18:17
rkukuraOr do we need to check whether any PTs have been created, and if not, we’d need to tear everything down and recreate the PTG18:17
rkukuraThis check would be the resource_mapping drive18:18
SumitNaiksatamrkukura: ok great, i think the former would suffice for now18:18
rkukuraOK, I’ll whip up a patch today18:18
SumitNaiksatamrkukura: perhaps a comment in the code to the effect of the latter (as a possibility)18:18
rkukuraSumitNaiksatam: agreed18:19
SumitNaiksatamrkukura: thanks18:19
rkukuraSumitNaiksatam: Are we concerned with the medium priority bugs at this point?18:19
SumitNaiksatamrkukura: depends, some were classified as medium but turned out to be high18:20
SumitNaiksatamrkukura: for the ones you have on your plate i will leave it to your judgement18:20
SumitNaiksatammageshgv: how does it look on your plate in terms of the high priority18:20
rkukuraSumitNaiksatam: OK, I’ll look them over18:20
KrishnaKHave a question related to What is the right way to check if the router id belongs to tenant during L3P creation ?18:20
SumitNaiksatamrkukura: great, thanks18:20
SumitNaiksatamKrishnaK: one sec, we will come to that18:20
SumitNaiksatammageshgv: any high priority ones for which patches are not posted yet?18:20
SumitNaiksatamKrishnaK: thanks for joining though, i know you are fighting another releae in paralle! ;-)18:21
SumitNaiksatam*release in parallel18:21
mageshgvSumitNaiksatam: No, patches are posted for them all, just need some modifications for hierarchial redirect18:21
rkukuraSumitNaiksatam: I think all the medium and low bugs assigned to me can be defered18:21
*** jtomasek has quit IRC18:21
SumitNaiksatamrkukura: ok thanks18:21
SumitNaiksatammageshgv: great18:21
SumitNaiksatammageshgv: i believe we have a plan on the hierarchical redirect based on the discussion today morning18:22
mageshgvSumitNaiksatam: yes, will have to factor in those changes18:22
SumitNaiksatammageshgv: ok thanks, looking forward to that patch, since it has the critical bug fix as well18:23
SumitNaiksatammageshgv: worst we might have to break those down (leave it to your judgement)18:23
SumitNaiksatammageshgv: but we need to merge the critical fix by EoD (PST)18:24
mageshgvSumitNaiksatam: ok, will see what can be done18:24
*** VW_ has quit IRC18:24
SumitNaiksatammageshgv: thanks for your effort fixing the numerous bugs in quick time18:24
SumitNaiksatamKrishnaK: your question now18:24
SumitNaiksatam“Have a question related to What is the right way to check if the router id belongs to tenant during L3P creation ?”18:25
KrishnaKSumitNaiksatam: thx.18:25
SumitNaiksatamKrishnaK: i was thinking that if you just checked for the router existence by doing a get and filtering on the tenant_id and the router_id18:26
SumitNaiksatamthat would not work?18:26
*** SridharRamaswamy has joined #openstack-meeting-318:26
SumitNaiksatamrkukura: this is the bug you created for validating the resources that are explicitly provided when creating PT/PTG/L2p?l3P18:26
SumitNaiksatamPT and PTG is done18:26
SumitNaiksatamKrishnaK is working on L2P and L3P18:27
KrishnaKfor the router id , tenant id is different for some case.18:27
SumitNaiksatamKrishnaK: really, i dont think that would be the case18:27
SumitNaiksatamKrishnaK: where did you see that happening?18:27
KrishnaK2014-12-18 10:28:35,249     INFO [neutron.api.v2.resource] create failed (client error): Error while creating L3 Policy : Router id a54b6371-c996-4ab7-8bae-e37fe1e797c6 does not belong to t\ he  tenant id test-tenant. ====================================================================== FAIL:
SumitNaiksatamrkukura: any chance that you can help KrishnaK with this one?18:29
*** egallen has joined #openstack-meeting-318:29
rkukuraSumitNaiksatam: I can try18:29
SumitNaiksatami think his changes are breaking the existing UTs18:29
SumitNaiksatamrkukura: thanks18:30
KrishnaKrkukura: thx18:30
SumitNaiksatamKrishnaK: can you do a quick follow after this meeting with rkukura?18:30
SumitNaiksatam*follow up18:30
rkukuraAre these UTs that break related to shared L3Ps?18:30
KrishnaKSumitNaiksatam: Thanks.18:30
KrishnaKrkukura: I didn't see shared for that router18:30
KrishnaKLet me gather more debug data and email you or post in the review.18:31
SumitNaiksatamrkukura: i believe the UTs are breaking on in krishnak’s patch where he trying to do a validation18:31
SumitNaiksatamon -> only18:31
SumitNaiksatam#topic Pending feature merges18:32
*** openstack changes topic to "Pending feature merges (Meeting topic: networking_policy)"18:32
SumitNaiksatamHierarchical PRS compostion for redirects: #link
SumitNaiksatamsome of us met this morning to review this18:32
SumitNaiksatammageshgv: rkukura ivar, thanks for your time18:32
SumitNaiksatamif you are not familiar with the above feature, essentially what we are trying to do is allow the admin to introduce redirect constraints for a user’s PRS18:33
*** yapeng_ has joined #openstack-meeting-318:34
SumitNaiksataman example being, the admin can introduce a firewall to inspect traffic18:34
SumitNaiksatamyapeng: hi, good to see you here18:34
SumitNaiksatamwe will come to the ODL part in just a bit18:34
SumitNaiksatammageshgv: thanks for working on the above feature, and to ivar for reviewing it18:34
*** yapeng_ is now known as yapeng__18:35
*** yapeng__ is now known as yapeng_18:35
SumitNaiksatam#topic ODL and Vendor drivers18:35
*** openstack changes topic to "ODL and Vendor drivers (Meeting topic: networking_policy)"18:35
*** yapeng_ is now known as yapneg18:35
*** yapneg is now known as yapeng_18:35
SumitNaiksatamyapeng and yi and the rest of the ODL team are working furiously to get the ODL integration done18:35
SumitNaiksatamyapeng: any update for the team here?18:36
SumitNaiksatami believe you are mostly done on the openstack policy driver side?18:36
yapeng_ok, single compute node is working now.18:36
SumitNaiksatamyapeng: wohoo!18:36
yapeng_i think Yi is working on test case part now.18:36
SumitNaiksatamyapeng: awesome18:36
yapeng_I am testing multi-compute node setup .18:36
SumitNaiksatamyapeng: sweet18:36
SumitNaiksatamyapeng: what about the part to raise not supported error for neutron operations?18:37
yapeng_I coded it up, will test this afternoon.18:37
SumitNaiksatamah ok18:37
yapeng_if works, I will submit my patch18:37
SumitNaiksatamis that a new patch, i dont see one posted yet18:37
yapeng_i have not posted yet.18:37
yapeng_should be today18:38
SumitNaiksatamyapeng: ah ok, you might want to post it anyway as WIP, so its on people’s review radar18:38
s3wongwe are still targeting to get ODL policy driver merged by tonight (PST)?18:38
SumitNaiksatamyapeng: thanks to you and yi for working on this18:38
SumitNaiksatams3wong: tomorrow is fine18:38
yapeng_sure Sumit.18:38
*** egallen has quit IRC18:38
SumitNaiksatamwe can have a session tomorrow morning18:39
SumitNaiksatamto review the workflow and the code18:39
s3wongthere is a weekly ODL GBP status meeting tomorrow morning18:39
SumitNaiksatams3wong: okay18:39
SumitNaiksatami think keith can relay the update there18:40
*** egallen has joined #openstack-meeting-318:40
SumitNaiksatami dont believe ronak is here, but i provided some high level comments on his Nuage driver18:40
banixs3wong: can you pls send me a link if there is one. if handy otherwise i will find it18:40
s3wongbanix: a link to the patch?18:41
SumitNaiksatambanix: there are two patches18:41
banixs3wong: no the the odl gbp call18:41
s3wongbanix: or to the webex for weekly ODL GBP meeting?18:41
*** jcoufal_ has quit IRC18:41
SumitNaiksatam#topic Packaging18:41
*** openstack changes topic to "Packaging (Meeting topic: networking_policy)"18:41
SumitNaiksatamrkukura: over to you18:41
rkukuraOk, the openstack-neutron-gbp, python-gbpclient, and python-django-horizon-gbp packages are all officially in fedora, and are based on recent commits18:42
SumitNaiksatamrkukura: awesome!!18:42
rkukuraThe openstack-heat-gbp package is still waiting for review, but that should be done tomorrow morning18:43
SumitNaiksatamrkukura: ok18:43
SumitNaiksatamrkukura: so are able to deploy and test from the UI?18:43
rkukuraSumitNaiksatam: I have not been able to test the UI yet18:43
SumitNaiksatamrkukura: okay18:43
rkukuraSo we need to do more testing, and there are a few small fixes to the packaging to include in the next round of updates18:44
SumitNaiksatamrkukura: some sym links have to be created to the gbp horion files, did oyu take that into consideration?18:44
*** igordcard has quit IRC18:44
rkukuraSumitNaiksatam: No, will need to add the symlinks to the packaging, if that is possible.18:44
s3wongbanix: I forwarded the ODL weekly meeting invite to your gmail account18:44
banixs3wong: thank you18:45
rkukuraSumitNaiksatam: Is the plan to do a juno-rc1 label?18:45
SumitNaiksatamrkukura: see this for what i do in devstack: #link
*** VW_ has joined #openstack-meeting-318:45
*** egallen has quit IRC18:45
SumitNaiksatamrkukura: there wasnt a plan, but we can discuss18:46
rkukuraSumitNaiksatam: Thanks18:46
SumitNaiksatamrkukura: ideally we should have been in RC1 now18:46
rkukuraSumitNaiksatam: OK, whether we do an RC1 or go right to the official release, do we have a process to create official tarballs on launchpad?18:46
SumitNaiksatamrkukura: i thought you were looking at the tarball part? ;-)18:47
SumitNaiksatamrkukura: i figured out adding the tags and creating the branch18:47
SumitNaiksatami have tested adding tags18:47
SumitNaiksatamhave created a branch18:47
rkukuraSumitNaiksatam: I’ll work with you on the tarball part18:47
SumitNaiksatamrkukura: okay18:47
SumitNaiksatamrkukura: i think uploading the tarball is straightforwar, but for creating i guess we have to follow the right process18:48
SumitNaiksatamrkukura: there are some release scripts available, but i havent tested those18:48
rkukuraWe really should test all of this with an RC1, because its possible we’ll need to make changes to setup.cfg or something18:48
SumitNaiksatamrkukura: ok18:48
SumitNaiksatamlets discuss that as a follow up to this meeting18:48
SumitNaiksatamplease ping me if anyone else has thoughts or suggestions on how we want to go about this (else i will follow up with rkukura)18:49
SumitNaiksatam#topic Open Discussion18:49
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:49
SumitNaiksatamsorry we havent been able to discuss Kilo specs for a while now18:49
*** bradjones has quit IRC18:49
rkukuraThe Fedora packages will then be the basis for RDO and RHEL-OSP packages18:49
SumitNaiksatamhopefully once we wrap up this release we can restart18:49
*** bradjones_ has joined #openstack-meeting-318:50
*** bradjones_ is now known as bradjones18:50
SumitNaiksatamrkukura: great, good to know the process there18:50
*** bradjones has quit IRC18:50
*** bradjones has joined #openstack-meeting-318:50
SumitNaiksatamrkukura: is this still the right page: #link
SumitNaiksatamor is there more?18:51
rkukuraSumitNaiksatam: Yes, but there are some newer package versions on my fedorapeople account18:51
SumitNaiksatamrkukura: okay, perhaps when you get some time, can we have a new openstack wiki page for all the pacakges information, and that can in turn point to the above and others pages?18:52
SumitNaiksatamanyone else have anything else to bring up for discussion?18:53
yapeng_SumitNaiksatam: how's the status of GBP heat part? I have not got chance to integrate heat with OS and ODL GBP yet. If possible, I would like to give it a try.18:53
rkukuraSumitNaiksatam: That probably makes sense, and should include common stuff like configuring vendor drivers and a usage tutorial18:53
SumitNaiksatamoh btw, needless to say, no meeting next week18:53
banixguys a quick and perhaps off question18:53
SumitNaiksatamrkukura: perfect, thanks!18:53
SumitNaiksatamyapeng_: yes its functional18:54
SumitNaiksatamyapeng_: the same devstack you are using has heat support18:54
SumitNaiksatambanix: sure, go for it18:54
banixare we still planning to have the gbp under the networking program or that is not going to be possible18:54
yapeng_SumitNaiksatam: do you have some instruction how to verify?18:54
SumitNaiksatambanix: we are currently a stackforge project18:55
SumitNaiksatambanix: we need to get input from the community on this point18:55
SumitNaiksatambanix: until then we continue to function as stackforge18:55
SumitNaiksatambanix: in general, the stackforge option is always ongoing since it allows us to experiment18:55
rkukuraSumitNaiksatam, banix: I think having something the community can acutally use will help us get useful input.18:55
banixSumitNaiksatam:  we cannot be in stackforge and under networking? just verifying18:56
SumitNaiksatambanix: in parallel, we will continually evaluate in concert with the coummunity as to what goes where18:56
SumitNaiksatambanix: we could18:56
banixrkukura: i agree and great effort to get here18:56
SumitNaiksatambanix: but again i think thats a community call18:57
banixSumitNaiksatam: ok thanks18:57
SumitNaiksatamcommunity includes us well :-)18:57
banixSumitNaiksatam: yes we can talk again; for a project to be under a openstack project, is there a process… going off topic so pls ignore if out of time18:58
*** annegent_ has quit IRC18:58
SumitNaiksatambanix: np18:58
*** kozhukalov has quit IRC18:58
SumitNaiksatambanix: actually there was only “integrated” criteria up until now18:58
SumitNaiksatambanix: so you were either integrated (like nova, neutron) etc or not18:58
SumitNaiksatambanix: and AFAIK, programs were integrated18:59
SumitNaiksatamhowever i believe those policies are being reworked18:59
SumitNaiksatamthere is also a notion of a “def core”18:59
SumitNaiksatamsome kind of a validated core18:59
*** LouisF has joined #openstack-meeting-318:59
banixyeah wondering for example where the lbass and service be and if we can be somewhere similar … we’ll talk more later thanks18:59
SumitNaiksatambanix: for lbaas, the code was in neutron and it was split into a new repo19:00
SumitNaiksatambanix: but stil neutron program19:00
SumitNaiksatamso did not required new incubation process19:00
SumitNaiksatamok we are at the hour19:00
banixSumitNaiksatam: ok thx19:01
SumitNaiksatamhappy holidays and happy new year to everyone in advance19:01
SumitNaiksatamsee you next year, if not before19:01
SumitNaiksatamthanks all19:01
banixSumitNaiksatam: same to you and the rest of the team19:01
*** openstack changes topic to "OpenStack Meetings ||"19:01
openstackMeeting ended Thu Dec 18 19:01:36 2014 UTC.  Information about MeetBot at . (v 0.1.4)19:01
openstackMinutes (text):
SumitNaiksatamyapeng_: sorry did not answer your question19:01
*** rkukura has left #openstack-meeting-319:01
SumitNaiksatamyapeng_: i will send you the instructions19:01
yapeng_SumitNaiksatam: np19:01
s3wongSumitNaiksatam: I saw that you talked about hierarchical redirect, is there a spec on this?19:02
yapeng_SumitNaiksatam: thanks!19:02
SumitNaiksatams3wong: its part of the main GBP spec19:02
s3wongSumitNaiksatam: OK19:02
SumitNaiksatams3wong:  the notion of parent and child PRS19:02
SumitNaiksatams3wong: do you think more clarifications were needed?19:03
SumitNaiksatams3wong:  if so we can update the spec19:03
SumitNaiksatams3wong: in general we are way behind on the user facing documentation19:03
s3wongSumitNaiksatam: we mandate 'redirect' action as the last action on contract19:03
SumitNaiksatams3wong: correct19:03
*** yamamoto has joined #openstack-meeting-319:03
SumitNaiksatams3wong: well, let me rephrase19:04
s3wongSumitNaiksatam: so I just wonder for hierarchical redirect, do we just take the higher priority one (which presumably would be the one from parent), or ability to do two 'redirect's?19:04
SumitNaiksatams3wong: we cannot gaurantee that anything after the redirect will be hit in the datapath19:04
SumitNaiksatams3wong: good question, mind if i answer this in #openstack-gbp?19:04
s3wongSumitNaiksatam: sure, let's move over there then19:05
*** SridharRamaswam1 has joined #openstack-meeting-319:08
*** yamamoto has quit IRC19:08
*** johnthetubaguy is now known as zz_johnthetubagu19:09
*** SridharRamaswamy has quit IRC19:10
*** SridharRamaswam1 has quit IRC19:16
*** SridharRamaswam1 has joined #openstack-meeting-319:16
*** egallen has joined #openstack-meeting-319:17
*** ivar-lazzaro has joined #openstack-meeting-319:19
*** ivar-lazzaro has quit IRC19:20
*** ivar-lazzaro has joined #openstack-meeting-319:21
*** Networkn3rd has joined #openstack-meeting-319:32
*** banix has quit IRC19:34
*** GeoffArnold has quit IRC19:35
*** bradjones has quit IRC19:36
*** sunny_ has quit IRC19:39
*** bradjones has joined #openstack-meeting-319:39
*** etoews has joined #openstack-meeting-319:39
*** jaypipes-afk is now known as jaypipes19:41
*** emagana has quit IRC19:41
*** LouisF has quit IRC19:44
*** emagana has joined #openstack-meeting-319:45
*** sahid has joined #openstack-meeting-319:55
*** baoli has quit IRC19:59
*** mageshgv has quit IRC20:00
*** JeanBriceCombebi has quit IRC20:09
*** Longgeek has quit IRC20:10
*** bradjones has quit IRC20:18
*** sunny_ has joined #openstack-meeting-320:40
*** sunny_ has quit IRC20:44
*** jtomasek has joined #openstack-meeting-320:46
*** sarob has joined #openstack-meeting-320:51
*** Networkn3rd has quit IRC20:51
*** nbouthors has quit IRC20:53
*** sunny_ has joined #openstack-meeting-320:54
*** zz_johnthetubagu is now known as johnthetubaguy20:58
*** sunny_ has quit IRC20:59
*** baoli has joined #openstack-meeting-321:07
*** baoli has quit IRC21:07
*** baoli has joined #openstack-meeting-321:07
*** carl_baldwin has quit IRC21:08
*** ivar-laz_ has joined #openstack-meeting-321:10
*** baoli has quit IRC21:10
*** baoli has joined #openstack-meeting-321:11
*** ivar-lazzaro has quit IRC21:12
*** baoli has quit IRC21:14
*** baoli_ has joined #openstack-meeting-321:16
*** baoli_ has quit IRC21:17
*** baoli_ has joined #openstack-meeting-321:18
*** dboik has quit IRC21:20
*** SridharRamaswamy has joined #openstack-meeting-321:23
*** SridharRamaswam1 has quit IRC21:24
*** sunny_ has joined #openstack-meeting-321:24
*** sahid has quit IRC21:24
*** VW_ has quit IRC21:25
*** sarob has quit IRC21:25
*** sweston_ has joined #openstack-meeting-321:27
*** sweston has quit IRC21:28
*** sweston_ is now known as sweston21:28
*** markmcclain has quit IRC21:34
*** jtomasek has quit IRC21:35
*** mrmartin has quit IRC21:40
*** sunny_ has quit IRC21:44
*** julim has quit IRC21:48
*** pballand has joined #openstack-meeting-321:51
*** dboik_ has joined #openstack-meeting-321:52
*** SridharRamaswamy has quit IRC21:54
*** ivar-laz_ has quit IRC21:54
*** ivar-lazzaro has joined #openstack-meeting-321:55
*** ivar-lazzaro has quit IRC21:55
*** ivar-lazzaro has joined #openstack-meeting-321:56
*** etoews has quit IRC21:58
*** etoews has joined #openstack-meeting-321:59
*** SridharRamaswamy has joined #openstack-meeting-322:00
*** salv-orlando has joined #openstack-meeting-322:01
*** johnthetubaguy is now known as zz_johnthetubagu22:03
*** yamamoto has joined #openstack-meeting-322:05
*** lblanchard has quit IRC22:07
*** gilliard is now known as gilliard_afk22:08
*** yamamoto has quit IRC22:10
*** thomasem has quit IRC22:12
*** pballand has quit IRC22:21
*** cbader has quit IRC22:21
*** peristeri has quit IRC22:23
*** sigmavirus24 has joined #openstack-meeting-322:24
*** pballand has joined #openstack-meeting-322:25
*** banix has joined #openstack-meeting-322:28
*** VW_ has joined #openstack-meeting-322:30
*** sweston_ has joined #openstack-meeting-322:33
*** sweston has quit IRC22:34
*** sweston_ is now known as sweston22:34
*** VW_ has quit IRC22:35
*** carl_baldwin has joined #openstack-meeting-322:35
*** mattfarina has quit IRC22:37
*** mohan has joined #openstack-meeting-322:39
*** mohan is now known as Guest8897122:40
*** SridharRamaswamy has quit IRC22:42
*** sunny_ has joined #openstack-meeting-322:45
*** sunny_ has quit IRC22:50
*** banix has quit IRC22:50
*** etoews has quit IRC22:55
*** etoews has joined #openstack-meeting-322:58
*** david-ly_ has joined #openstack-meeting-322:58
*** david-lyle has quit IRC23:03
*** SumitNaiksatam has quit IRC23:03
*** SridharRamaswamy has joined #openstack-meeting-323:03
*** SumitNaiksatam has joined #openstack-meeting-323:04
*** VW_ has joined #openstack-meeting-323:21
*** VW_ has quit IRC23:25
*** SumitNaiksatam has quit IRC23:29
*** SumitNaiksatam has joined #openstack-meeting-323:30
*** lblanchard has joined #openstack-meeting-323:30
*** peristeri has joined #openstack-meeting-323:31
*** banix has joined #openstack-meeting-323:37
*** sunny_ has joined #openstack-meeting-323:46
*** SumitNaiksatam has quit IRC23:50
*** sunny_ has quit IRC23:50
*** SumitNaiksatam has joined #openstack-meeting-323:51
*** lblanchard has quit IRC23:53
*** sunny_ has joined #openstack-meeting-323:55
*** sunny_ has quit IRC23:59
*** baoli_ has quit IRC23:59

Generated by 2.14.0 by Marius Gedminas - find it at!