Thursday, 2015-06-04

*** alexpilotti has quit IRC00:03
*** yamamoto has quit IRC00:05
*** shwetaap has quit IRC00:06
*** Swami has quit IRC00:07
*** Swami has joined #openstack-meeting-300:08
*** fallenpegasus has quit IRC00:10
*** yamamoto has joined #openstack-meeting-300:11
*** banix has quit IRC00:14
*** banix has joined #openstack-meeting-300:19
*** yamamoto has quit IRC00:21
*** shwetaap has joined #openstack-meeting-300:24
*** yamamoto has joined #openstack-meeting-300:26
*** sankarshan_ has quit IRC00:27
*** jaypipes has quit IRC00:27
*** puranamr has quit IRC00:27
*** sarob has quit IRC00:35
*** Yi_ has quit IRC00:35
*** sankarshan_ has joined #openstack-meeting-300:36
*** yamamoto has quit IRC00:38
*** sankarshan_ is now known as sankarshan_away00:38
*** bknudson has joined #openstack-meeting-300:43
*** mattgriffin has joined #openstack-meeting-300:45
*** watanabe_isao has joined #openstack-meeting-300:49
*** mattgriffin has quit IRC00:50
*** Sukhdev has quit IRC00:59
*** mwagner_afk has joined #openstack-meeting-301:00
*** armax has quit IRC01:00
*** Yi_ has joined #openstack-meeting-301:03
*** Yi__ has joined #openstack-meeting-301:05
*** Yi__ has quit IRC01:05
*** Yi_ has quit IRC01:08
*** openstack has joined #openstack-meeting-301:21
*** hurgleburgler1 has joined #openstack-meeting-301:22
*** yamamoto has joined #openstack-meeting-301:22
*** alexsyip has quit IRC01:22
*** ChanServ sets mode: +o openstack01:22
*** Caleb-- has joined #openstack-meeting-301:25
*** openstack has joined #openstack-meeting-301:36
*** ChanServ sets mode: +o openstack01:36
*** s3wong has quit IRC01:40
*** yamahata has quit IRC01:46
*** mattgriffin has joined #openstack-meeting-301:47
*** openstack has quit IRC01:52
*** openstack has joined #openstack-meeting-301:53
*** ChanServ sets mode: +o openstack01:54
*** mattgriffin has quit IRC01:55
*** Aish has quit IRC01:59
*** clu_ has joined #openstack-meeting-302:01
*** mattgriffin has joined #openstack-meeting-302:02
*** clu_ has quit IRC02:04
*** eghobo_ has quit IRC02:04
*** vnod has joined #openstack-meeting-302:15
*** nelsnelson has quit IRC02:21
*** mattgriffin has quit IRC02:24
*** nelsnelson has joined #openstack-meeting-302:35
*** gcb has quit IRC02:35
*** vnod has quit IRC02:38
*** tqtran has quit IRC02:39
*** bknudson has quit IRC02:39
*** shwetaap has quit IRC02:42
*** ivar-lazzaro has quit IRC02:44
*** ivar-lazzaro has joined #openstack-meeting-302:44
*** julim has quit IRC02:47
*** nelsnelson has quit IRC02:48
*** stevemar has joined #openstack-meeting-302:58
*** ajmiller has joined #openstack-meeting-302:59
*** yamahata has joined #openstack-meeting-303:00
*** dims_ has quit IRC03:07
*** edleafe has quit IRC03:10
*** edleafe has joined #openstack-meeting-303:12
*** ivar-laz_ has joined #openstack-meeting-303:15
*** ivar-lazzaro has quit IRC03:15
*** badveli has quit IRC03:16
*** ivar-laz_ has quit IRC03:16
*** ivar-lazzaro has joined #openstack-meeting-303:17
*** sbalukoff has quit IRC03:19
*** markvoelker has quit IRC03:23
*** shwetaap has joined #openstack-meeting-303:24
*** Swami has quit IRC03:24
*** Swami_ has joined #openstack-meeting-303:25
*** Aish has joined #openstack-meeting-303:26
*** Aish has left #openstack-meeting-303:26
*** coolsvap|afk is now known as coolsvap03:39
*** hurgleburgler1 has quit IRC03:42
*** watanabe_isao has quit IRC03:46
*** gcb has joined #openstack-meeting-303:49
*** shwetaap1 has joined #openstack-meeting-303:51
*** tobe has joined #openstack-meeting-303:51
*** shwetaap has quit IRC03:52
*** watanabe_isao has joined #openstack-meeting-303:52
*** vnod has joined #openstack-meeting-303:55
*** dims_ has joined #openstack-meeting-304:07
*** eghobo has joined #openstack-meeting-304:11
*** dims_ has quit IRC04:13
*** Longgeek has joined #openstack-meeting-304:14
*** vnod has quit IRC04:16
*** ongk has joined #openstack-meeting-304:17
*** krotscheck has quit IRC04:19
*** mordred has quit IRC04:21
*** markvoelker has joined #openstack-meeting-304:23
*** mordred has joined #openstack-meeting-304:25
*** krotscheck has joined #openstack-meeting-304:25
*** shwetaap1 has quit IRC04:26
*** markvoelker has quit IRC04:28
*** irenab has quit IRC04:31
*** Swami_ has quit IRC04:34
*** sbalukoff has joined #openstack-meeting-304:34
*** Longgeek has quit IRC04:39
*** rushiagr_away is now known as rushiagr04:42
*** clu_ has joined #openstack-meeting-304:51
*** Longgeek has joined #openstack-meeting-304:53
*** clu_ has quit IRC04:53
*** Longgeek_ has joined #openstack-meeting-304:57
*** Longgeek has quit IRC05:00
*** stevemar has quit IRC05:04
*** banix has quit IRC05:10
*** tobe has quit IRC05:22
*** irenab has joined #openstack-meeting-305:35
*** armax has joined #openstack-meeting-305:36
*** tobe has joined #openstack-meeting-305:40
*** pkarikh has quit IRC05:41
*** fallenpegasus has joined #openstack-meeting-305:46
*** saneax has joined #openstack-meeting-305:51
*** belmoreira has joined #openstack-meeting-305:56
*** fallenpegasus has quit IRC06:10
*** saneax has quit IRC06:12
*** markvoelker has joined #openstack-meeting-306:13
*** mrunge has joined #openstack-meeting-306:17
*** mrunge has quit IRC06:17
*** markvoelker has quit IRC06:18
*** tobe has quit IRC06:18
*** ivar-lazzaro has quit IRC06:20
*** eghobo has quit IRC06:22
*** radek_ has joined #openstack-meeting-306:23
*** mrunge has joined #openstack-meeting-306:26
*** fallenpegasus has joined #openstack-meeting-306:26
*** flaper87 has quit IRC06:33
*** flaper87 has joined #openstack-meeting-306:33
*** clu_ has joined #openstack-meeting-306:40
*** jtomasek has quit IRC06:41
*** jtomasek has joined #openstack-meeting-306:42
*** clu_ has quit IRC06:42
*** jtomasek has quit IRC06:43
*** safchain has joined #openstack-meeting-306:43
*** jtomasek has joined #openstack-meeting-306:44
*** gsagie has left #openstack-meeting-306:46
*** saneax has joined #openstack-meeting-306:50
*** amotoki has joined #openstack-meeting-306:52
*** vikram has joined #openstack-meeting-306:54
*** sahid has joined #openstack-meeting-306:56
*** tobe has joined #openstack-meeting-306:57
*** woodster_ has quit IRC07:00
*** amotoki has quit IRC07:03
*** irenab has quit IRC07:06
*** devvesa has joined #openstack-meeting-307:08
*** wojdev has joined #openstack-meeting-307:10
*** irenab has joined #openstack-meeting-307:12
*** markvoelker has joined #openstack-meeting-307:13
*** natorious is now known as zz_natorious07:15
*** matrohon has joined #openstack-meeting-307:16
*** markvoelker has quit IRC07:18
*** mrunge has quit IRC07:23
*** mrunge has joined #openstack-meeting-307:23
*** mrunge_ has joined #openstack-meeting-307:25
*** mrunge_ has quit IRC07:26
*** amotoki has joined #openstack-meeting-307:27
*** mrunge has quit IRC07:29
*** mrunge has joined #openstack-meeting-307:30
*** zz_ttrifonov is now known as ttrifonov07:30
*** wojdev has quit IRC07:33
*** sqchen has quit IRC07:33
*** sqchen has joined #openstack-meeting-307:37
*** dims_ has joined #openstack-meeting-307:44
*** matrohon has quit IRC07:46
*** dims_ has quit IRC07:49
*** sqchen has quit IRC07:52
*** JeanBriceCombebi has joined #openstack-meeting-307:55
*** sahid has quit IRC07:57
*** sahid has joined #openstack-meeting-308:03
*** pkarikh has joined #openstack-meeting-308:05
*** sahid has quit IRC08:10
*** armax has quit IRC08:11
*** sahid has joined #openstack-meeting-308:13
*** yamahata has quit IRC08:14
*** matrohon has joined #openstack-meeting-308:20
*** amotoki has quit IRC08:20
*** amotoki has joined #openstack-meeting-308:20
*** fallenpegasus has quit IRC08:21
*** wojdev has joined #openstack-meeting-308:21
*** clu_ has joined #openstack-meeting-308:29
*** clu_ has quit IRC08:31
*** wojdev has quit IRC08:35
*** JeanBriceCombebi has quit IRC08:39
*** tobe has quit IRC08:39
*** tobe has joined #openstack-meeting-308:39
*** gcb has quit IRC08:41
*** sahid has quit IRC08:42
*** sahid has joined #openstack-meeting-308:43
*** JeanBriceCombebi has joined #openstack-meeting-308:48
*** wojdev has joined #openstack-meeting-308:52
*** matrohon has quit IRC08:55
*** sbalukoff has quit IRC08:57
*** matrohon has joined #openstack-meeting-309:00
*** markvoelker has joined #openstack-meeting-309:02
*** wojdev has quit IRC09:07
*** markvoelker has quit IRC09:07
*** salv-orlando has quit IRC09:08
*** amotoki has quit IRC09:08
*** watanabe_isao has quit IRC09:09
*** yamamoto has quit IRC09:11
*** yamamoto has joined #openstack-meeting-309:12
*** matrohon has quit IRC09:13
*** matrohon has joined #openstack-meeting-309:19
*** wojdev has joined #openstack-meeting-309:20
*** Yingxin has joined #openstack-meeting-309:22
*** Yingxin1 has quit IRC09:22
*** matrohon has quit IRC09:24
*** yamamoto has quit IRC09:32
*** tobe has quit IRC09:33
*** amotoki has joined #openstack-meeting-309:38
*** amotoki has quit IRC09:42
*** e0ne has joined #openstack-meeting-309:44
*** dims_ has joined #openstack-meeting-309:45
*** dims_ has quit IRC09:51
*** matrohon has joined #openstack-meeting-309:52
*** tobe has joined #openstack-meeting-309:53
*** dims_ has joined #openstack-meeting-310:03
*** JeanBriceCombebi has quit IRC10:08
*** salv-orlando has joined #openstack-meeting-310:09
*** salv-orlando has quit IRC10:17
*** clu_ has joined #openstack-meeting-310:17
*** markvoelker has joined #openstack-meeting-310:18
*** clu_ has quit IRC10:19
*** salv-orlando has joined #openstack-meeting-310:20
*** salv-orlando has quit IRC10:21
*** JeanBriceCombebi has joined #openstack-meeting-310:21
*** markvoelker has quit IRC10:22
*** salv-orlando has joined #openstack-meeting-310:23
*** yamamoto has joined #openstack-meeting-310:24
*** yamamoto has quit IRC10:30
*** coolsvap is now known as coolsvap|afk10:30
*** mwagner_afk has quit IRC10:45
*** yamamoto has joined #openstack-meeting-310:46
*** markvoelker has joined #openstack-meeting-310:46
*** Longgeek_ has quit IRC10:53
*** coolsvap|afk is now known as coolsvap10:54
*** Longgeek has joined #openstack-meeting-310:54
*** mwagner_afk has joined #openstack-meeting-310:58
*** JeanBriceCombebi has quit IRC10:59
*** woodster_ has joined #openstack-meeting-311:00
*** coolsvap is now known as coolsvap|afk11:16
*** mwagner_afk has quit IRC11:19
*** hichihara has joined #openstack-meeting-311:30
*** e0ne is now known as e0ne_11:39
*** baoli has joined #openstack-meeting-311:44
*** e0ne_ has quit IRC11:49
*** baoli has quit IRC11:50
*** baoli has joined #openstack-meeting-311:51
*** baoli has quit IRC11:53
*** tobe has quit IRC12:06
*** clu_ has joined #openstack-meeting-312:06
*** yamamoto has quit IRC12:08
*** clu_ has quit IRC12:08
*** yamamoto has joined #openstack-meeting-312:09
*** e0ne has joined #openstack-meeting-312:13
*** irenab has quit IRC12:17
*** irenab has joined #openstack-meeting-312:17
*** JeanBriceCombebi has joined #openstack-meeting-312:21
*** mwagner_afk has joined #openstack-meeting-312:22
*** ajmiller has quit IRC12:26
*** rushiagr is now known as rushiagr_away12:36
*** JeanBriceCombebi has quit IRC12:36
*** yamamoto has quit IRC12:38
*** JeanBriceCombebi has joined #openstack-meeting-312:38
*** yamamoto has joined #openstack-meeting-312:39
*** stevemar has joined #openstack-meeting-312:41
*** bknudson has joined #openstack-meeting-312:43
*** egafford has joined #openstack-meeting-312:49
*** JeanBriceCombebi has quit IRC12:53
*** JeanBriceCombebi has joined #openstack-meeting-312:53
*** peristeri has joined #openstack-meeting-312:54
*** mrunge has quit IRC12:55
*** baoli has joined #openstack-meeting-312:58
*** zhenguo has quit IRC12:58
*** shwetaap has joined #openstack-meeting-313:00
*** e0ne is now known as e0ne_13:01
*** yamamoto has quit IRC13:01
*** shwetaap1 has joined #openstack-meeting-313:01
*** yamamoto has joined #openstack-meeting-313:02
*** julim has joined #openstack-meeting-313:04
*** e0ne_ is now known as e0ne13:04
*** shwetaap has quit IRC13:05
*** egafford has quit IRC13:08
*** banix has joined #openstack-meeting-313:11
*** yamamoto has quit IRC13:12
*** nelsnelson has joined #openstack-meeting-313:15
*** irenab has quit IRC13:18
*** singlethink has joined #openstack-meeting-313:21
*** banix has quit IRC13:24
*** pkarikh has quit IRC13:24
*** rushiagr_away is now known as rushiagr13:28
*** lblanchard has joined #openstack-meeting-313:28
*** yamamoto has joined #openstack-meeting-313:30
*** puranamr has joined #openstack-meeting-313:33
*** VW has joined #openstack-meeting-313:33
*** marun_ has joined #openstack-meeting-313:34
*** vgridnev has joined #openstack-meeting-313:39
*** puranamr has quit IRC13:40
*** puranamr has joined #openstack-meeting-313:41
*** vgridnev has quit IRC13:42
*** stendulker has joined #openstack-meeting-313:42
*** saneax has quit IRC13:43
*** vgridnev has joined #openstack-meeting-313:44
*** TravT has quit IRC13:44
*** elmiko has joined #openstack-meeting-313:44
*** marun has joined #openstack-meeting-313:48
*** marun_ has quit IRC13:49
*** sahid has quit IRC13:50
*** puranamr has quit IRC13:50
*** puranamr has joined #openstack-meeting-313:50
*** clu_ has joined #openstack-meeting-313:55
*** sigmavirus24_awa is now known as sigmavirus2413:55
*** yamamoto has quit IRC13:56
*** clu_ has quit IRC13:57
*** pino|work has joined #openstack-meeting-313:57
*** stendulker_ has joined #openstack-meeting-313:59
*** e0ne is now known as e0ne_13:59
*** htruta has joined #openstack-meeting-313:59
*** weiting has joined #openstack-meeting-313:59
SergeyLukjanovhey sahara folks14:00
elmikohi14:00
weitinghi14:00
*** tellesnobrega has joined #openstack-meeting-314:00
alazarevhi14:00
vgridnevhi14:00
SergeyLukjanov#startmeeting sahara14:01
openstackMeeting started Thu Jun  4 14:01:00 2015 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: sahara)"14:01
openstackThe meeting name has been set to 'sahara'14:01
SergeyLukjanov#link https://wiki.openstack.org/wiki/Meetings/SaharaAgenda14:01
SergeyLukjanov#topic sahara@horizon status (crobertsrh, NikitaKonovalov)14:01
*** openstack changes topic to "sahara@horizon status (crobertsrh, NikitaKonovalov) (Meeting topic: sahara)"14:01
SergeyLukjanov#link https://etherpad.openstack.org/p/sahara-reviews-in-horizon14:01
SergeyLukjanovis it actual list?14:01
*** crobertsrh has joined #openstack-meeting-314:01
*** stendulker has quit IRC14:01
*** tmckay has joined #openstack-meeting-314:01
*** kchen has joined #openstack-meeting-314:02
NikitaKonovalovSergeyLukjanov: the changes on review a still there14:02
crobertsrhA few bug fixes and enhancements I've added, on review of course.14:02
crobertsrhI did talk with the horizon folks.....14:02
tmckayI mean, hi folks :) (wrong window)14:02
crobertsrhThey are thinking that for L, a single core +2 combined with enough +1s from us will get a patch merged.14:02
*** tosky has joined #openstack-meeting-314:03
*** huichun has joined #openstack-meeting-314:03
*** hdd has joined #openstack-meeting-314:03
*** huichun has quit IRC14:03
SergeyLukjanovcrobertsrh, it'll be great IMO14:03
elmikonice14:03
NikitaKonovalovcrobertsrh: that's gread14:03
NikitaKonovalovgreat*14:03
SergeyLukjanovcrobertsrh, and add you to the core team ;)14:03
crobertsrhheh14:03
elmiko+114:04
*** huichun_ has joined #openstack-meeting-314:04
*** huichun has joined #openstack-meeting-314:04
kchenhi all, these days I found the gate-sahara-neutron-direct-spark-aio test always failed, is it a bug? was it resolved now?14:04
*** e0ne_ has quit IRC14:04
elmikoalazarev linked to a bug patch for that issue, in one of the reviews14:04
alazarevhttps://review.openstack.org/#/c/187155/14:05
*** e0ne has joined #openstack-meeting-314:06
SergeyLukjanov#topic News / updates14:06
*** openstack changes topic to "News / updates (Meeting topic: sahara)"14:06
* SergeyLukjanov recovering from the vacation prev. week14:06
tmckaySergeyLukjanov, any update on Sahara-Ironic integration blog post / patches?14:07
crobertsrhThat is what work is for, right?  Recovering from vacation?14:07
SergeyLukjanovtmckay, blog post is on review for the blog :(14:07
elmikoi've been researching the improved secret spec more, and also working on a spec for keystone session objects. i have a few questions about the latter, for the group.14:07
tmckaySergeyLukjanov, well, review is good! :) Almost done then.14:08
SergeyLukjanovtmckay, we've not yet worked on the patches, we hope to attach volumes using cloud-init14:08
alazarevrewrote heat engine to use ResourceGroup, please review https://review.openstack.org/#/c/186543/14:08
vgridnevstill working with auto-tune hadoop configs, for vanilla ready for review14:08
vgridnev#link https://review.openstack.org/#/c/177280/14:08
SergeyLukjanovI'm now working on a few specs we were discussing on summit, hopefully will start to publish them soon14:08
*** vikram has quit IRC14:09
*** puranamr has quit IRC14:09
tmckayThere are some NetApp guys near me physically, we are going to meet face to face and brainstorm about Sahara/Manila integration.  There was a Manila talk at Summit that mentioned Sahara integration, so I followed up with them.  I'll let you know how it turns out.14:09
*** egafford has joined #openstack-meeting-314:09
tellesnobregai just started working on the multiple clusters change, we need to discuss some issues before i can start implementing14:09
SergeyLukjanovtmckay, cool, looking forward for info14:09
tmckayI am wondering if we can get some security benefits from it (multi-tenancy, file shares scoped to users maybe) and also some file transfer effiiciency (job binaries mounted in the cluster)14:10
tmckayand maybe, hdfs shares (intel wrote a Manila hdfs driver I think) can provide a simple way for users to set up shared libraries for Hadoop and host them in a long-running hdfs share14:10
tmckaythat could be linked into multiple clusters.  Things like that.14:11
*** vikram has joined #openstack-meeting-314:11
tellesnobregatmckay, cool14:11
*** vikram has quit IRC14:11
SergeyLukjanov#topic Open discussion14:11
*** openstack changes topic to "Open discussion (Meeting topic: sahara)"14:11
SergeyLukjanovtmckay, sounds interesting14:11
elmikocan we talk about keystone session objects for a few minutes?14:11
weitingYes, we did hdfs share in Manila.14:12
SergeyLukjanovelmiko, I don't see sreshetnyak and apavlov online now14:12
egaffordWorking on interface map; pretty much down to tests and review revisions @ this point (client and Horizon changes to follow).14:12
elmikoSergeyLukjanov: ok, i'll keep working on the spec. maybe we can talk next week about it14:12
tmckayegafford, I am trying to run against that but I hit a snag with my neutron based stack :(14:13
tmckaybut, I am looking at it.  Looks good so far14:13
weitingAnd we can discuss it how to use it in sahara.14:13
egaffordtmckay: Interesting; I'm also using Neutron. We should talk.14:13
egaffordtmckay: (Also, I'm sure there are bugs yet, as I posted a working happy path WIP without even vaguely adequate testing, and knew it.)14:14
tmckayweiting, certainly14:14
tmckayegafford, ack on WIP, I understand14:14
*** peristeri has quit IRC14:15
*** praveens has joined #openstack-meeting-314:15
*** peristeri has joined #openstack-meeting-314:15
tmckaySergeyLukjanov, are you working on a spec for moving plugins out-of-tree?14:17
SergeyLukjanovtmckay, yup14:17
SergeyLukjanovin my list now - resources ACL, extract plugins, extract scenario tests,14:18
*** marun has quit IRC14:18
tmckayokay. We talked about that a little more, and what impact multiple versions of plugins supported against multiple versions of Sahara might do to the CI matrix.  How do we test it all?  Who tests it?14:18
SergeyLukjanovI've got the most powerful jetlag this time after a few days at home :(14:18
tmckayheh14:18
*** marun has joined #openstack-meeting-314:18
tmckaybut we can ask such questions on review ^^14:19
SergeyLukjanovtmckay, it's one of the most important questions, I'd like to start spec with a basic ideas and grow it to the state it cover all questions14:19
elmikoyea, i would imagine those will be addressed in the spec14:19
SergeyLukjanovbecause it's very huge and important thing14:19
elmikoSergeyLukjanov: +114:20
SergeyLukjanovso far, I think it could be done be min set of tests vs not all plugins14:20
SergeyLukjanovfor the stable branches14:20
SergeyLukjanovwe don't need to test all plugins, we need to check that api isn't changed14:20
*** mrmartin has joined #openstack-meeting-314:21
SergeyLukjanovprobably it's a good time to chat about multiple cluster creation14:22
SergeyLukjanovtellesnobrega, ^^14:23
tellesnobregasure14:23
tmckayokay.  Looking forward to the spec :) thanks14:23
tellesnobregawe need to define a couple things14:23
tellesnobregafirst is to decide if we implement the change on the sahara side or horizon and client side14:23
tmckaytellensnobrega, sorry, what exactly does "multiple cluster creation" mean? I can already create multiple clusters :)14:24
crobertsrhI think I need more details14:24
tellesnobregaok14:24
crobertsrhAny feature that we have should eventually be mirrored in the client lib and horizon14:24
tellesnobregathe idea is to put a field to allow the user to select how many cluster with that configuration he wants to create14:25
*** matrohon has quit IRC14:25
tmckayah, ok.  So it's like pushing the launch button multiple times.  We need a naming convention14:25
crobertsrhIs there a real use case for such a feature?14:26
alazarevin nova this is implemented on server side, REST has a field "count", as I understand the proposal is to make the same in Sahara14:26
tellesnobregai can think on research labs (like the one i work)14:26
tellesnobregaalazarev, exactly14:26
tmckaycrobertsrh, the motivation would be fewer clicks and forms14:26
tellesnobregasometime we need to create more than one cluster to process different sets of data and so on14:26
SergeyLukjanovtellesnobrega, and clusters will be exactly the same>14:27
tmckaysame image, same ssh key, etc.  just a different name14:27
tellesnobregayes14:27
*** matrohon has joined #openstack-meeting-314:27
crobertsrhPossible to do this with just a horizon change, if desired.14:27
tmckayI wonder if one big cluster, with multi-tenancy (I know we don't have it) would work as well14:27
alazarevit is easy to implement, the only thing I concirned is use case, I can hardly imagine situation when multiple clusters with the same parameters are needed and this can't be automated via script14:28
elmikotmckay: i think we might need some sort of job queueing for that though?14:28
SergeyLukjanovif do on client side - there is an issue how to check quotas14:28
weitingtellesnobrega, how many cluster you would like to create at the same time in your case?14:28
*** julim has quit IRC14:29
tellesnobregathat depends, we have different labs that use our cloud, one of them is just analytics stuff, they have lots of students needing clusters there, so sometimes plenty, sometimes 2, most of the times just 1 for sure14:29
SergeyLukjanovso, the good news that it's already partially implemented - case when count==114:30
crobertsrhvery true14:31
tellesnobregayes14:31
tmckay:) yay, partly done14:31
tellesnobregalol14:31
*** armax has joined #openstack-meeting-314:31
alazarevcount==0 is implemented too14:31
tmckayalazarev, that was POC14:31
egaffordYou could make an argument for count==-1 too.14:31
*** JeanBriceCombebi has quit IRC14:32
SergeyLukjanovegafford, -inf as well, yay14:32
tellesnobregawill we implement for count > 1?14:32
SergeyLukjanovso, the last case is count==214:32
SergeyLukjanov:)14:32
SergeyLukjanovI'm ok with this feature, the only question I have - what's the correct place to do it14:33
SergeyLukjanovif we'd like to check quotas then we need to do it on server side somewhere after intelligent quotas check14:33
tmckayand do we just add "-N" to the name given to the cluster?14:33
*** JeanBriceCombebi has joined #openstack-meeting-314:33
*** hdd has quit IRC14:34
alazarevtmckay, I think so14:34
tellesnobregatmckay, i was thinkinh uuid, but was suggested the -N14:34
tellesnobregaso the name isn't too big14:34
*** praveens has quit IRC14:34
elmiko-N is nice so you know they're in a series14:34
tellesnobrega+114:34
elmikouuid could be confusing14:34
tmckaywhat about network settings?  do we want the clusters segregated? Do we need to change neutron settings for that?  (not sure)14:34
elmikogood question14:35
tmckayjust wondering if anything else on the cluster launch form has to be tweaked besides name14:35
tmckay(well, the cluster JSON really)14:35
alazarevtmckay, it looks like nothing, you can create clusters with the same parameters14:36
tellesnobreganot sure, btu i think the network can keep the same settings for now, if we detect problems we improve it14:36
SergeyLukjanov+1 for -N (in the best case impl exactly the same as it done in nova)14:37
*** praveens has joined #openstack-meeting-314:37
tellesnobrega+114:38
elmikosounds like we are assuming that when creating multiple clusters they will all belong to the same keystone project?14:38
*** hdd has joined #openstack-meeting-314:38
egaffordI might suggest that we pad with as many zeros as needed for the last number in the sequence.14:38
*** fallenpegasus has joined #openstack-meeting-314:39
tellesnobregaelmiko, yes14:39
tmckayelmiko, yeah.  All within the same tenant.  otherwise you're going to have to log out and log in again in the UI.14:39
egafford(So that an alphabetic sort by name will yield the expected order, in case anyone cares.)14:39
tellesnobregaegafford, like that14:39
elmikok, just wanted to confirm14:39
elmikoegafford: +114:39
elmikoalthough, i can't imagine needing to pad with more than 1 or *maybe* 2 0's lol14:39
elmikobut, who knows...14:40
tellesnobregai think 1 is enough, but 2 would be a safer choice14:40
tellesnobregayou never know14:40
tmckayyou can have up to 1000 clusters with one button push.  If you need more, you can push the button again14:40
elmikoyea, 2 for safety14:40
elmikotmckay: lol!14:40
tellesnobregatmckay, +114:40
egaffordWell, I just figure, okay, you're asking for 10 clusters? 1 x "0". 349? You're crazy, but okay, you get 2 zeros. 400,000? That's ambitious. 5 zeros.14:40
elmikooh, are you saying dynamically create the padding 0s?14:41
egaffordBut just padding 2 might be easier, and yeah, it's hard to imagine a case for 100,000 individual clusters.14:41
elmikosorry, this is serious bike-shedding at this point14:42
tellesnobregai'm ok with dynamic as well14:42
sreshetnyakwhat about API request and response? It's breaks backward compatible with older sahara versions?14:42
egaffordelmiko: That was my thought, but auto-padding with a rational number also meets the use case in huge numbers of cases.14:42
egaffordTrue.14:42
elmikosreshetnyak: not sure, sounds like it will just be an extra param in the json14:42
tmckayWe could use random words from a dictionary, with localization14:42
tellesnobregasreshetnyak, if we implement in the sahara side, that might be a point where we need to return a list of clusters14:43
elmikohey, now that sreshetnyak is here could we talk about keystone sessions for a minute? =)14:43
sreshetnyakelmiko, hi :)14:44
elmikohey!14:44
*** vikram___ has joined #openstack-meeting-314:44
tellesnobregawe need to decide where to implement it, but we can talk later about this14:44
elmikoso, i'm working through the spec for replacing keystone Client with Session based auth. i'm thinking the first step will be to replace our usage of keystone clients, but as a follow up we should replace all the service clients with Session usage. does that make sense?14:45
sreshetnyakelmiko, apavlov wants works on keystone sessions14:45
elmikocool!14:45
sreshetnyakelmilo, i think you need to talk to him14:45
sreshetnyakapavlov, here?14:45
elmikooh well, i'll try and send something to the ML14:47
elmikosreshetnyak: do you know if he's working on a poc or spec yet?14:47
elmikoalso, should i add both of you to the spec as co-assignees?14:47
sreshetnyakelmiko, no, but he wants to start14:48
elmikosreshetnyak: ok, i'll have to talk with him14:49
elmikois he in saratov timezone?14:49
*** praveens has quit IRC14:49
sreshetnyakyes14:49
elmikok14:49
elmikothanks =)14:49
SergeyLukjanov9 mins left14:51
SergeyLukjanovanything else to chat?14:51
crobertsrhNothing from me14:51
*** gsagie has joined #openstack-meeting-314:51
alazarevquotas is a separate topic to discuss, now we are retrieving the whole neutron DB for each cluster creation, horizon does the same thing14:51
*** john-davidge has joined #openstack-meeting-314:52
hddjust a quick question: what's the status of HDP 2.2 plugin?14:52
SergeyLukjanovhdd, the first parts are already on review14:53
*** haleyb has joined #openstack-meeting-314:53
SergeyLukjanovby sreshetnyak14:53
egaffordWe discussed the idea of using an agent and the possibility of Zaqar adoption at Summit. It was extremely brief, and I don't think anything was decided, but I'd like to get a notion of where we are on the question of trying to move away from straight SSH for communication.14:53
hddok, cool, I'll check it out. I'm eager to test14:53
tellesnobregathe multiple clusters questions that are still open we can discuss later14:53
*** nelsnels_ has joined #openstack-meeting-314:54
egafford(This could be a worth discussing next week as a larger topic.)14:54
* flaper87 drops something here: http://specs.openstack.org/openstack/zaqar-specs/specs/liberty/pre-signed-url.html14:54
egaffordflaper87: :D14:54
SergeyLukjanovflaper87, thx :)14:54
*** Ramanjaneya has joined #openstack-meeting-314:55
SergeyLukjanovegafford, so, it's the base for the potential guest agent impl14:55
*** nelsnelson has quit IRC14:56
egaffordSergeyLukjanov: Right; I just didn't come away with a firm picture of whether the guest agent impl is potential or planned.14:56
*** yamamoto has joined #openstack-meeting-314:56
*** dtroyer has joined #openstack-meeting-314:56
SergeyLukjanovegafford, it's a potential implementation option, but now it looks like the best option14:57
*** cdent has joined #openstack-meeting-314:57
SergeyLukjanovegafford, with zaqar queues per cluster and signed urls it'll be the full isolation for the control traffic14:57
SergeyLukjanovegafford, and no need for SSH :)14:57
*** fallenpegasus has quit IRC14:57
*** Ramanjaneya has quit IRC14:57
egaffordI see. So we are moving toward a guest agent, and Zaqar is a potential route toward it. Cool; that's what I needed to know. Thanks.14:58
*** Networkn3rd has joined #openstack-meeting-314:58
egafford(Potential and likely.)14:58
*** Ramanjaneya has joined #openstack-meeting-314:58
*** VW has quit IRC14:58
SergeyLukjanovegafford, yup, in real life - someday, hopefully sooner :)14:59
SergeyLukjanovwe're going out of time14:59
SergeyLukjanovthanks folks!14:59
SergeyLukjanov#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Thu Jun  4 14:59:26 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-06-04-14.01.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-06-04-14.01.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-06-04-14.01.log.html14:59
*** VW has joined #openstack-meeting-314:59
*** crobertsrh has left #openstack-meeting-314:59
elmikothanks SergeyLukjanov !14:59
*** VW has quit IRC14:59
*** carl_baldwin has joined #openstack-meeting-314:59
kchenbye14:59
*** Ramanjaneya has quit IRC14:59
*** fallenpegasus has joined #openstack-meeting-314:59
*** hdd has left #openstack-meeting-315:00
carl_baldwinhi all15:00
*** VW has joined #openstack-meeting-315:00
*** Ramanjaneya has joined #openstack-meeting-315:00
pavel_bondarcarl_baldwin, hi15:00
*** johnbelamaric has joined #openstack-meeting-315:00
john-davidgehi15:00
carl_baldwin#startmeeting neutron_l315:00
johnbelamarichi15:00
openstackMeeting started Thu Jun  4 15:00:29 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:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:00
openstackThe meeting name has been set to 'neutron_l3'15:00
carl_baldwinpavel_bondar: john-davidge: hi15:00
*** jxstanford has joined #openstack-meeting-315:00
carl_baldwin#topic Announcements15:00
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:00
*** weiting has quit IRC15:01
*** kchen has quit IRC15:01
carl_baldwinLiberty-1 is right around the corner.15:01
*** pc_m has joined #openstack-meeting-315:01
carl_baldwin#link https://wiki.openstack.org/wiki/Liberty_Release_Schedule15:01
*** tidwellr has joined #openstack-meeting-315:01
*** ryansb has joined #openstack-meeting-315:01
vikram___hi15:01
carl_baldwinThe Neutron mid-cycle is coming up.  In Fort Collins.  Anyone planning to attend?15:01
tidwellrI am planning on it15:01
pc_mcarl_baldwin: yes15:02
johnbelamariccarl_baldwin: I am still in the "maybe" category15:02
john-davidgetoo far away for me unfortunately15:02
haleybwill be there15:02
vikram___:(15:02
*** yamamoto has quit IRC15:02
Ramanjaneyahi15:02
carl_baldwin#link https://etherpad.openstack.org/p/neutron-liberty-mid-cycle15:03
*** eghobo has joined #openstack-meeting-315:03
carl_baldwinWe will miss those who are unable to attend.15:03
vikram___Me too ;)15:03
carl_baldwin#topic Bugs.15:03
*** openstack changes topic to "Bugs. (Meeting topic: neutron_l3)"15:03
*** tosky has left #openstack-meeting-315:03
carl_baldwinI did some triage but still need to do some more.15:04
carl_baldwinAny bugs to bring up specifically?15:04
carl_baldwinI don’t have any.15:05
*** belmoreira has quit IRC15:05
*** Ramanjaneya_ has joined #openstack-meeting-315:05
*** fallenpegasus has quit IRC15:05
carl_baldwingsagie: This is probably a good time to bring up your dvr patch15:05
gsagiehttps://review.openstack.org/#/c/185368/ , not a bug but its the decomposition task15:05
carl_baldwin#link https://review.openstack.org/#/c/185368/15:05
carl_baldwinRight, not a bug but I thought we’d squeeze it in due to your constraints.15:06
gsagiei aligned it with everyones comments, and would like to get it merged first before moving to the next step15:06
carl_baldwingsagie: I have not looked at it since my latest review.15:06
*** Ramanjaneya_ has quit IRC15:06
*** JeanBriceCombebi has quit IRC15:06
carl_baldwinI think the naming was the only open question for me.  What names did you settle on?15:06
*** egafford has left #openstack-meeting-315:07
gsagiecarl_baldwin: what you suggested, however thats still mainly in comment and the file name, i think we can replace that going forward if we think of something better15:07
*** hichihara has quit IRC15:07
carl_baldwinOkay.  I’ll have another look later today.15:07
gsagiethe next step/patch would be to remove the is_snat_host checks and align the unit tests and the creation in the agent15:07
gsagieafter that i will try to think about a composition model, but that will be more intrusive code wise15:08
*** julim has joined #openstack-meeting-315:08
*** cdent has left #openstack-meeting-315:08
*** Ramanjaneya has quit IRC15:08
*** Ramanjaneya has joined #openstack-meeting-315:08
*** JeanBriceCombebi has joined #openstack-meeting-315:08
carl_baldwingsagie: Let’s get to the second step and see what that looks like and go from there.15:09
gsagieokie, waiting your reviews then :)15:09
carl_baldwingsagie: Any other open issues on this?15:09
gsagienope, and thanks for letting me go first, have to run, bye!15:09
carl_baldwingsagie: bye15:10
*** Ramanajneya has joined #openstack-meeting-315:11
carl_baldwin#topic bgp-dynamic-routing15:11
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:11
*** alexpilotti has joined #openstack-meeting-315:11
carl_baldwintidwellr: vikram___: devvesa: hi15:11
tidwellrhi15:12
vikram___hi15:12
vikram___Rebasing for CLI and driver patch done!15:12
carl_baldwinvikram___: Excellent, do you have links handy?15:12
vikram___Good news we have a Horizon expert Vish willing to help us out for horizon15:12
vikram___I have over-written the same patch15:13
vishwanathjvikram___, Thanks for introducing me as an expert, don't think I am an expert but am glad to help out15:13
vikram___;)15:13
carl_baldwinvishwanathj: There will be many opportunities for doing Horizon work for Neutron features.  :)15:14
vikram___Driver: https://review.openstack.org/#/c/115938/15:14
vishwanathjthat will be awesome, appreciate the opportunity15:14
vikram___CLI: https://review.openstack.org/#/c/111318/15:14
carl_baldwinvikram___: Thanks.15:15
carl_baldwinAnything needing discussion now?15:15
*** Ramanajneya has quit IRC15:15
*** Ramanjaneya has quit IRC15:15
vikram___Carl: Ramanjenya is also willing to help us for CLI work15:15
tidwellrA couple issues to raise 1). I want to tread lightly with the scope of the spec https://review.openstack.org/#/c/125401/  2). The patches we have seem to be have been implemented as a service plugin. Is there a reason to continue down that path?15:15
*** bpokorny has joined #openstack-meeting-315:15
*** pino|work has left #openstack-meeting-315:16
tidwellrin terms of scope, I'm concerned that we may be biting off a little too much by support both routed floating IP and routed tenant networks15:17
*** singleth_ has joined #openstack-meeting-315:17
tidwellrwe can take the scope discussion to the spec, we don't need to go on about it here15:17
*** marun has quit IRC15:17
carl_baldwintidwellr: I think we should go for floating ips first and be sure that gets done.  The tenant networks piece will depend on address scopes which is not yet ready.15:17
carl_baldwinI think doing tenant networks will be a stretch goal.15:18
*** marun has joined #openstack-meeting-315:18
*** wojdev has quit IRC15:18
carl_baldwinLet’s take the service plugin discussion to the code review and possibly the ML.15:18
tidwellrcarl_baldwin: good plan15:18
carl_baldwinAnything else on this topic?15:19
vikram___Yes15:19
*** nelsnelson has joined #openstack-meeting-315:20
*** singlethink has quit IRC15:20
vikram___What is plan about BP approval and code delivery?15:20
carl_baldwinNice work on getting the patches up to date.  Has any had much luck running them in a test environment against quagga or anything?15:20
vikram___That's the next step;)15:20
carl_baldwinvikram___: It looks like the BP may need one more turn.15:20
carl_baldwinI’d like to see working code in someone’s test setup.  Hopefully one we can automate in the gate before merging the code.15:21
*** nelsnels_ has quit IRC15:22
tidwellrcarl_baldwin: no luck yet, the API / DB layer has been interesting to say the least15:22
*** vgridnev has quit IRC15:23
tidwellrgetting closer though, I'm hoping to have some code cleaned up and running next week15:23
*** vgridnev has joined #openstack-meeting-315:24
*** vgridnev has quit IRC15:24
carl_baldwinWe should make that the goal, connecting to floating ips through BGP routes rather than arp in an automated test.15:24
tidwellr+115:24
vikram___+115:24
carl_baldwintidwellr: vikram___:  Thanks for the update on progress.15:24
carl_baldwinWe have a lot to cover, so moving on...15:24
vikram___Carl: I will be on a vacation for 2 weeks...15:24
carl_baldwin#topic neutron-ipam15:24
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:24
*** mwagner_afk has quit IRC15:24
vishwanathjcarl_baldwin, vikram___ was mentioning that there was some specific horizon work related to subnet pool that needs to be done...is there a link that you can share that has the details15:24
vikram___Will ensure i sync up with ryan15:24
carl_baldwinvikram___: ack15:24
carl_baldwinvishwanathj: There is a blueprint, I will get you the link in a bit.15:25
vikram___Carl: thanks15:25
vishwanathjok, thanks15:25
carl_baldwinjohnbelamaric: pavel_bondar: ping15:25
johnbelamariccarl_baldwin: pong15:26
pavel_bondarcarl_baldwin: pong15:26
*** nelsnels_ has joined #openstack-meeting-315:26
johnbelamaricpavel_bondar broke the refactor/decompose patch up some more15:26
carl_baldwinWe’ve had some good progress.15:26
johnbelamaricfirst patch just moves code around15:26
johnbelamaric#link https://review.openstack.org/#/c/187961/15:26
johnbelamaricpretty simple15:26
carl_baldwinRef impl and driver loader down.15:26
johnbelamariccarl_baldwin: yes! I think the link above can merge soon too15:27
pavel_bondarand plan do some more siple slices from #link https://review.openstack.org/#/c/153236/15:27
*** nelsnelson has quit IRC15:27
pavel_bondars/siple/simple/15:27
johnbelamaricpavel_bondar: so you are going to break it up a bit more?15:27
carl_baldwinjohnbelamaric: It looks like it has seen some reviews and is a smaller bit to review.15:27
*** ajmiller has joined #openstack-meeting-315:28
*** stendulker_ has quit IRC15:28
carl_baldwinI think this patch is very manageable.  I will review it soon.15:28
johnbelamariccarl_baldwin: thanks15:28
johnbelamariccarl_baldwin: L1 is coming fast15:28
pavel_bondarjohnbelamaric: yes, there are still some copy with small modifications code in ipam_backend_mixin and ipam_non_pluggable_backend15:28
*** vgridnev has joined #openstack-meeting-315:29
johnbelamaricpavel_bondar: ok15:29
pavel_bondarso plan to create new review from that15:29
johnbelamaricmakes sense15:29
johnbelamaricpavel_bondar: so you were able to get rid of the "associate" step - you updated the ref driver too?15:29
*** zz_natorious is now known as natorious15:29
pavel_bondarjohnbelamaric, right, it works fine without it15:30
pavel_bondarI have updated dependent patches with this changes15:30
johnbelamaricok, good15:30
johnbelamaricpavel_bondar: so, once you split the patch again, we can push on with the reviews. ETA on that?15:31
pavel_bondarETA for split is tomorrow15:31
carl_baldwinThis sounds like it is really shaping up.  I will be sure to review 187961 today while I might have you guys available to discuss.  It looks simple enough to merge soon.15:31
*** tholtzen has joined #openstack-meeting-315:32
johnbelamariccarl_baldwin: great!15:32
carl_baldwinHopefully, that will open the door for the others to fall in line tomorrow and after.15:32
johnbelamaric:)15:32
pavel_bondarcarl_baldwin: sounds good!15:32
carl_baldwinFeel free to ping me on this to keep the review cycles tight.15:32
*** nelsnelson has joined #openstack-meeting-315:33
pavel_bondarcarl_baldwin, sure, thanks15:33
*** natorious is now known as zz_natorious15:33
carl_baldwinAnything else for the meeting?15:33
johnbelamaricaddress scopes?15:33
johnbelamaricor you mean for IPAM? I don't think so15:33
*** nelsnels_ has quit IRC15:33
carl_baldwin#topic Address Scopes15:34
*** openstack changes topic to "Address Scopes (Meeting topic: neutron_l3)"15:34
carl_baldwinThere.15:34
carl_baldwin:)15:34
*** marun has quit IRC15:34
*** marun has joined #openstack-meeting-315:34
carl_baldwinAre there still open questions?15:34
*** vnod has joined #openstack-meeting-315:34
*** nelsnels_ has joined #openstack-meeting-315:35
*** vgridnev has quit IRC15:35
vikram___BP looks really cool ;)15:35
vikram___Carl: Nice work15:35
*** nelsnels_ has quit IRC15:35
carl_baldwinvikram___: +1.  I think we found a sweet spot.  Something that can be implemented within the cycle and will provide a nice foundation.15:35
pc_m+115:36
johnbelamaricOne I think on whether we should allow route leaking between address scopes within Neutron. But maybe that is a follow on15:36
carl_baldwinjohnbelamaric: How do you feel about the spec?15:36
vikram___yes15:36
johnbelamariccarl_baldwin: i think it is looking good too. I think we can put route leaking (ie, routing between scopes without NAT) in a later cycle15:36
carl_baldwinjohnbelamaric: I was thinking not to allow leaking at first.  But, I’m open to discussion.15:36
*** eghobo has quit IRC15:37
johnbelamariccarl_baldwin: +1 let's keep the scope do-able!15:37
carl_baldwinjohnbelamaric: I think that VRF work in Linux may help us with that.  But, it is bleeding edge work that isn’t even merged.15:37
johnbelamariccarl_baldwin: yeah, who knows when that will happen…15:37
carl_baldwinjohnbelamaric: Right, I want to keep an eye on it.15:38
*** nelsnelson has quit IRC15:38
johnbelamariccarl_baldwin: Ok, +1 from me :)15:38
carl_baldwinOk, I’ll try to get this BP reviewed by the drivers team and approved.15:38
*** nelsnelson has joined #openstack-meeting-315:38
carl_baldwin#topic DNS15:39
*** openstack changes topic to "DNS (Meeting topic: neutron_l3)"15:39
carl_baldwinI’ll give a report on mlavalle ’s behalf.15:39
carl_baldwinThe BPs to get nova and neutron talking have been updated and are simpler and looking good.15:39
carl_baldwinKiall from designate is taking over the BP to get neutron and designate talking.15:40
carl_baldwinmlavalle is beginning to write code.  The momentum is looking good.15:40
carl_baldwinThat’s all.15:41
johnbelamaricsounds like good news15:41
carl_baldwin#topic IPv615:41
*** openstack changes topic to "IPv6 (Meeting topic: neutron_l3)"15:41
carl_baldwinHenryG: Are you around?15:41
carl_baldwinIt was mentioned yesterday that we might want to discuss bug 146072015:42
openstackbug 1460720 in neutron "Add API to set ipv6 gateway" [Undecided,New] https://launchpad.net/bugs/1460720 - Assigned to Abishek Subramanian (absubram)15:42
carl_baldwinThere is also the testing effort (bug 1401726)15:42
openstackbug 1401726 in tempest "Tempest IPv6 scenario tests use IPv4 and floating IPs to connect and test" [High,Confirmed] https://launchpad.net/bugs/1401726 - Assigned to Sean M. Collins (scollins)15:42
*** puranamr has joined #openstack-meeting-315:43
*** dims_ has quit IRC15:43
carl_baldwinAnyone around?15:43
*** clu_ has joined #openstack-meeting-315:44
*** nelsnelson has quit IRC15:44
*** peterstac has joined #openstack-meeting-315:44
* haleyb is lurking15:44
carl_baldwinOkay.  Will bump it to another week or discuss offline.15:44
carl_baldwin#topic ML315:45
*** openstack changes topic to "ML3 (Meeting topic: neutron_l3)"15:45
haleybi only know of the first bug - ipv6_gateway api support, which i talked to abishek at summit about, seems like a good step15:45
*** clu_ has quit IRC15:46
carl_baldwinI guess maybe we were looking to talk ML3 in a later meeting.15:46
carl_baldwin#topic Open Discussion15:46
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:46
carl_baldwinAny other topics?15:46
pcarverI'm planning to organize my thoughts on ML3 but haven't yet15:47
*** nelsnelson has joined #openstack-meeting-315:47
pcarverArmando has given me some good input to think about15:47
carl_baldwinpcarver: Ah, you did make it.  Good to see you.  I wasn’t sure what your nick was.15:47
*** singlethink has joined #openstack-meeting-315:47
pcarveryeah, sorry. Wasn't watching the whole meeting, just checking occasionally15:47
carl_baldwinpcarver: Thanks for the update.  I have seen your ML post and I plan to respond as soon as I get a minute.15:48
john-davidgecarl_baldwin: New prefix delegation patchset is up to address your review comments https://review.openstack.org/#/c/15869715:48
*** nelsnelson has quit IRC15:48
john-davidgeHopefully it captures everything. Currently evaluating what extra testing the new pd classes need15:48
pcarverSo I know I've got L3 routing problems, but I want to structure a writeup that's not specific to just me15:48
carl_baldwinjohn-davidge: ack.15:49
*** nelsnelson has joined #openstack-meeting-315:49
pcarverby L3 routing problems, I mean performance specifically, high bandwidth, high PPS, low latency15:49
carl_baldwinpcarver: understood15:49
*** singleth_ has quit IRC15:50
*** JeanBriceCombebi has quit IRC15:50
carl_baldwinI did forget to mention the “network segments” topic.  I removed “routing networks” and replaced it with this.15:52
carl_baldwinI don’t know what the chances are for making Liberty with it (if any) but it is something I’m thinking about.15:52
carl_baldwinAttempt to find common ground between https://bugs.launchpad.net/neutron/+bug/1458890 and https://review.openstack.org/#/c/172244/15:53
openstackLaunchpad bug 1458890 in neutron "Add segment support to Neutron" [Undecided,Confirmed]15:53
carl_baldwinAnyway, just FYI.15:54
carl_baldwinLast call for other topics before closing the meeting15:54
*** cdent has joined #openstack-meeting-315:54
carl_baldwinBye.  Thanks to everyone.15:56
carl_baldwin#endmeeting15:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:56
*** stevelle has joined #openstack-meeting-315:56
openstackMeeting ended Thu Jun  4 15:56:10 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-06-04-15.00.html15:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-06-04-15.00.txt15:56
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-06-04-15.00.log.html15:56
johnbelamaricthanks. bye15:56
*** s3wong has joined #openstack-meeting-315:56
*** pc_m has left #openstack-meeting-315:56
pavel_bondarbye15:56
*** johnbelamaric has left #openstack-meeting-315:56
*** JeanBriceCombebi has joined #openstack-meeting-315:56
*** baoli has quit IRC15:59
elmikohello folks15:59
cdento/15:59
miguelgrinberghi elmiko15:59
*** vikram___ has left #openstack-meeting-316:00
elmiko #startmeeting api wg16:00
elmikohmm16:00
elmiko#startmeeting api wg16:00
openstackMeeting started Thu Jun  4 16:00:15 2015 UTC and is due to finish in 60 minutes.  The chair is elmiko. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
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
elmikothere we go16:00
cdentslow bot16:00
*** baoli has joined #openstack-meeting-316:00
elmikoi think i had spaces in front that messed it up16:00
*** tidwellr has left #openstack-meeting-316:00
ryansbprobably16:00
elmiko#topic agenda16:00
*** openstack changes topic to "agenda (Meeting topic: api wg)"16:00
elmiko     #link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda16:00
*** tholtzen has left #openstack-meeting-316:00
elmiko#topic previous meeting action items16:01
*** openstack changes topic to "previous meeting action items (Meeting topic: api wg)"16:01
*** VW has quit IRC16:01
*** yapeng has joined #openstack-meeting-316:01
elmikoetoews is out, so we'll skip his action16:01
miguelgrinbergjust finished my review of  https://review.openstack.org/#/c/177397/ a few minutes ago16:02
elmikoawesome16:02
*** Sam-I-Am has joined #openstack-meeting-316:02
miguelgrinberglots of things I did not like16:02
*** Sam-I-Am has left #openstack-meeting-316:02
elmikoanything specific you'd like to bring up?16:02
sigmavirus24o/16:02
*** julim has quit IRC16:03
miguelgrinbergthey have optional components in the URL, in the middle16:03
ryansbo.O16:03
miguelgrinbergsomething like /artifacts/{type_version}/something_else16:04
miguelgrinbergand type_version can be omitted16:04
cdentthat's confusing16:04
elmikoagreed16:04
* sigmavirus24 sees if any of them are around16:04
miguelgrinbergI suggested a different structure, let's see how it goes16:04
cdentand not very URI16:04
sdagueo/16:04
*** mattfarina has joined #openstack-meeting-316:04
*** julim has joined #openstack-meeting-316:05
sigmavirus24o/ sdague16:05
cdentwhat is a "type version"16:05
miguelgrinbergit defines the version of the artifact structure16:05
miguelgrinbergor so I understand16:05
sigmavirus24cdent: so artifacts are a very generic abstraction of "things"16:06
sigmavirus24a type is a specialization of sorts, e.g., an image16:06
sigmavirus24or a heat template16:06
sdagueso... this version thing seems like it would be better done in a psuedo content negotiation model16:06
sigmavirus24I think the type_version is the artifact's version (since all artifacts are semantically versioned)16:06
stevelle^ that16:06
cdentsdague++16:06
miguelgrinbergI proposed to move the optional stuff to the end, but content negotiation would work too16:07
cdent(it's getting a bit boring agreeing with you so much sdague, can you say some stupid stuff every now and again just to keep me on my toes?)16:07
sdagueartifact_type seems to be completely mime types, so I don't understand why that's in the uri at all16:07
sigmavirus24cdent: having never met you, I'm not convinced you and sdague aren't the same person16:07
sdagueheh16:08
*** cknight has joined #openstack-meeting-316:08
miguelgrinbergsdague: they define it as a semver16:08
*** VW has joined #openstack-meeting-316:08
elmikosigmavirus24: lol16:08
sdaguemiguelgrinberg: no, that's type_version16:08
sigmavirus24Has anyone ever seen cdent and sdague in the same room together? I doubt it ;)16:08
sdagueThe `artifact_type` constant should unambiguously identify the16:08
sdagueartifact type, so the values of this constants should be unique among all the16:08
sdagueartifact types defined by the active plugins.16:08
miguelgrinbergsdague: ah, sorry, right16:08
cdentI think I saw sdague at summit, but I may have been imagining it, talking to myself16:08
sigmavirus24Oh I could be wrong16:08
*** jaypipes has joined #openstack-meeting-316:08
sigmavirus24They might allow versioning of artifact plugin types16:08
sdagueright, that seems to be what it is. But that really seems like it should just be mime types16:09
sigmavirus24jaypipes: might know more about artifacts since he's their bossman =P16:09
sdaguewith Accept headers16:09
sigmavirus24sdague: I don't disagree :D16:09
stevellethey allow versioning the types as well as the artifacts, yes16:09
sigmavirus24stevelle: right, I was confused for a few minutes there16:09
* edleafe arrives late and sits in the back row16:10
*** praveens has joined #openstack-meeting-316:10
elmikosounds like miguelgrinberg is on top of this, do we need another action item or does this seem on track?16:10
*** mfedosin has joined #openstack-meeting-316:10
elmikoor would other folks want to checkout #link https://review.openstack.org/#/c/177397/ as well?16:10
cdentis it worth getting more people on the review or will that just seem like piling on?16:11
peterstaco/16:11
elmikocdent: yea, that's my concern too16:11
sigmavirus24cdent: I think one or two other people to back up miguelgrinberg's concerns is fine16:11
sigmavirus24I think 10 people is piling on16:11
*** ativelkov has joined #openstack-meeting-316:11
miguelgrinbergI think a couple more is not going to hurt16:11
sigmavirus24ativelkov: has been working on artifacts16:11
elmikocdent, sdague, would either of you be able to take a look at that review as well?16:11
cdentyeah, I've just put in my think about this queue16:12
ativelkovhi folks16:12
elmikocool16:12
sdagueelmiko: yes, I can.16:12
elmikoativelkov: hi16:12
elmikoawesome, thanks16:12
sigmavirus24so if y'all have questions, ativelkov can answer them very well16:12
elmiko#action cdent and sdague to review https://review.openstack.org/#/c/177397/ and comment16:12
elmikook, next action item16:13
elmikostevelle, and ryansb, do you guys have anything to talk about for the filtering guideline?16:13
*** baoli has quit IRC16:13
stevelleNothing except to call for more reviews on the updates16:13
elmiko#link https://review.openstack.org/#/c/177468/16:13
ryansbelmiko: I don't think so16:14
ryansbyeah, what stevelle said16:14
*** hurgleburgler has joined #openstack-meeting-316:14
elmikook, cool. is that the correct link?16:14
ryansbyup16:14
elmiko#topic merge process status16:14
*** openstack changes topic to "merge process status (Meeting topic: api wg)"16:14
*** baoli has joined #openstack-meeting-316:14
elmiko#link https://review.openstack.org/#/c/186836/16:15
elmikoso, it looks like we are getting good acceptance of the process that etoews put together16:15
elmikoi wonder if we should post something to the ml about this, or can we merge maybe early next week?16:15
sigmavirus24send something to the ML16:16
sigmavirus24just to be safe16:16
sdagueposting to the ML never hurts16:16
sdagueand more communication the better on a lot of this, so there is less surprise to people16:16
sigmavirus24well, sometimes it does ;)16:16
elmikook, i won't freeze it though, since it's not really a guideline. does that make sense?16:17
sigmavirus24or if people are surprised, then we can say "you should have read the ML"16:17
ryansbsounds reasonable16:17
sigmavirus24elmiko: yep16:17
elmiko#action elmiko make post to ml about the merge process review16:17
elmiko#topic guideline freeze16:17
*** openstack changes topic to "guideline freeze (Meeting topic: api wg)"16:17
elmikothe review chain starting with #link https://review.openstack.org/#/c/179365/16:17
elmikoseems to have good reviews and i think it's mostly ready for merge16:18
elmikoshould we freeze the main 3 and make a post, following the new process, or are these small enough to skip that?16:18
cdentthey are small, but they make statements about response codes that seem to stir people up16:19
elmikoi'm kinda leaning towards freeze and post, but i wanted to get other's opinions16:19
cdentyeah16:19
sdagueyeh, freeze and post seems safe16:19
elmikok, sounds good16:19
elmiko#action elmiko freeze https://review.openstack.org/#/c/179365/ chain and post to ml16:20
elmiko#topic guidelines16:20
*** openstack changes topic to "guidelines (Meeting topic: api wg)"16:20
*** JeanBriceCombebi has quit IRC16:20
elmiko#link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z16:20
elmikoare there any other guidelines we should be looking at?16:20
cdentI think we should send the 501 stuff out for a global fight or it's going to linger and never actually be followed16:21
cdenteach time someone outside the group comes along they say "but wait, no!" and drop a -1 on it16:22
elmikothis one https://review.openstack.org/#/c/183456/ ?16:22
cdentyeah16:22
sigmavirus24I agree with cdent16:22
elmikohmm, what's the next step here. sdague is there room to update this?16:23
sigmavirus24I thought we were supposed to be telling people that they were doing it wrong though16:23
* sigmavirus24 kids16:23
miguelgrinbergwhat I think the problem is here is that we are not talking about specific examples16:23
cdentI'm starting to think that maybe sigmavirus24 is me too16:23
elmikolol16:23
sigmavirus24who's to say that I'm not?16:23
cdentexactly!16:23
*** puranamr has quit IRC16:23
sdagueelmiko: so beyond merge conflicts, I think there were a couple of minor wording corrections, right?16:23
cdentThe reason I bring this up now is because it is one of the main areas where there are a lot of implementations are using 501 to mean "that functionality is not currently configured"16:24
elmikosdague: yea, but it's picked up a few -1s that look like content issues16:24
sdagueI can make those changes for sure, I don't know where the balance of the 501 fight is right now though, as I'm still getting my hread around it16:24
sdagueelmiko: yeh, those are fixable16:24
sdagueI can do that later today16:24
cdentand making the guidline not to do that tests whether are guidelines are enforceable16:24
elmikosdague: awesome, thanks16:24
cdents/are/our/16:24
elmiko#action sdague review and repost #link https://review.openstack.org/#/c/183456/16:24
*** huichun has quit IRC16:25
miguelgrinbergsdague: if you could list examples it would be awesome. I can follow your reasoning all the way until you say 400, then it does not make sense to me, so looking at specific examples might help16:25
sdaguemiguelgrinberg: so, honestly, 400 is to me the default answer when nothing else fits16:25
*** sqchen has joined #openstack-meeting-316:25
jaypipessorry I'm late guys.16:26
sdaguebecause, you know, the http codes were designed around clients and servers before there were dynamic applications16:26
miguelgrinbergsdague: so I want to see why 404 does not fit better16:26
jaypipessigmavirus24: I still have to do the review on the API of the artifacts, sorry :(16:26
jaypipesand I'm not the boss man :)16:26
*** sqchen has quit IRC16:26
sigmavirus24you're sort of a boss, man ;)16:26
sdaguemiguelgrinberg: so, honestly, I don't have a hugely strong opinion on it, it's mostly the practical bit from the mailing list scuff between cdent and I16:26
miguelgrinbergsdague: but you understand the push back on 400 correct?16:27
sdagueI think if anything beyond 400 has multiple meanings, it gets weird on client side coding16:27
sdaguemiguelgrinberg: yes16:27
cdent404 should only be used when there's nothing responding on the URL16:27
*** sqchen has joined #openstack-meeting-316:27
sdaguemiguelgrinberg: http://lists.openstack.org/pipermail/openstack-dev/2015-May/063396.html is the crux of my practical argument around 400 fall back16:27
miguelgrinbergcdent: so I'd like to see an example where a service that is not configured still can have a valid URL16:28
*** puranamr has joined #openstack-meeting-316:28
sdaguemiguelgrinberg: oh, that's easy16:28
sdaguePOST volume-attach to /servers/ID/action16:29
sdaguefor a docker driver based cloud16:29
sdaguea lot of these are things where the more RPCish stuff is being done for features that not all backend drivers support16:30
sdaguehttp://docs.openstack.org/developer/nova/support-matrix.html16:30
sdaguePOST stop /severs/ID/action to an ironic based cloud16:30
miguelgrinbergsdague: okay, so side effect of using actions instead of resources. Good example.16:31
sdagueyeh, I can include that in the updated text16:31
elmikowould it help to have some of the example codified in the guideline?16:31
elmikok, thanks sdague16:31
cdentwhen do we write the guideline that says /servers/ID/action is a bad idea?16:32
miguelgrinbergsdague: I think it does help to justify the 400 with examples16:32
sdagueyeh, I'm totally happy adding more rationale to the docs, I think that's huge part of the value16:32
* elmiko backs away slowly16:32
sdaguecdent: lets see if we can get past this 501 thing first :)16:32
* cdent pokes elmiko 16:32
cdent:)16:32
elmikohehe16:32
sdagueand drink a lot of sake in tokyo and convince ourselves the action fight is worth fighting16:33
sdaguebecause I'm still mixed on that one16:33
elmikoi think at some point we should circle back around on the http guideline and format it more closely to the template,16:33
miguelgrinberg:)16:33
cdentyeah, "worth" is a good question16:33
*** matrohon has quit IRC16:33
elmikowe could add examples to each sub-section16:33
cdentworth putting off16:33
sdagueelmiko: yeh, examples would be great16:33
*** mattgriffin has joined #openstack-meeting-316:34
elmikook, any other guidelines we should be looking at, or might be ready for a freeze?16:34
sdagueI think every rule should end up with a why (rationale), what (here is the edict), and how (examples)16:34
elmikosdague: +116:34
elmikoi think part of the issue is that the http guideline started before we agreed on a format, so we'll need to clean it up at some point.16:34
sdagueyeh, no worries, I like that it's evolving that way16:35
elmikocool16:35
*** vgridnev has joined #openstack-meeting-316:35
elmikook, moving along16:35
elmiko#topic APIImpact16:35
*** openstack changes topic to "APIImpact (Meeting topic: api wg)"16:35
elmiko#link https://review.openstack.org/#/q/status:open+AND+(message:ApiImpact+OR+message:APIImpact),n,z16:36
elmikoanything there that folks would like to point out?16:36
*** peterstac-m has joined #openstack-meeting-316:36
*** yamahata has joined #openstack-meeting-316:37
elmikoi know this one, #link https://review.openstack.org/#/c/187443/16:37
*** vnod has quit IRC16:37
elmikogot discussed in channel a bit, not sure if it needs any eyeballs or not16:37
*** sarob has joined #openstack-meeting-316:37
*** eghobo has joined #openstack-meeting-316:37
elmikolooks like they dropped the PATCH ideas, so maybe not16:37
*** alexsyip has joined #openstack-meeting-316:39
elmikook then16:39
*** dims_ has joined #openstack-meeting-316:39
miguelgrinbergelmiko: seems pretty clean design16:39
elmiko#topic open discussion16:39
*** openstack changes topic to "open discussion (Meeting topic: api wg)"16:39
ryansbYeah, they seem like they're fine16:39
*** amotoki has joined #openstack-meeting-316:39
ryansb(the barbican review)16:39
elmikomiguelgrinberg: yea, i think they hashed out all the ideas with you in irc16:39
cdentI had dropped on the agenda earlier in the week but it went missing:16:40
cdentthere's a downstream request that all apis that list time oriented data support some form of changes-since, akin to what nova has on at least some stuff16:40
cdenta) is changes-since well and proper?16:40
cdentb) is it a portable concept?16:41
elmikoso, would this be a request that could be made for changes-since?16:41
elmiko(i'm not quite following the usage)16:41
cdentI'm not sure I quite follow it either because I'm not clear on what the existing implementation is doing16:42
elmikolol, ok16:42
sdagueit's a filter16:42
miguelgrinbergcdent: is the idea to get the entities that changed since a time, or the individual changes on them?16:42
elmikoah, that makes sense16:42
stevellewhy just "changes-since" instead of proper filtering on sortable property?16:42
*** devvesa has quit IRC16:43
sdaguebecause changes-since is a baked in contruct in some of the sqla apis in projects16:43
cdentwhat does the existing thing do?16:43
stevellethe construct is updated_at and also supports created_at iirc16:43
sdagueright, so it turns into an sql filter around updated_at16:44
sdagueand returns everything updated_at > changes-since16:44
stevelleso what I'm asking is why not allow < or <= as well16:44
sdaguefor various data slices16:44
miguelgrinbergthis can be integrated into ryansb guideline on filtering I think16:44
sdaguestevelle: could be, this is legacy stuff that's been there for a while16:44
*** amotoki has quit IRC16:45
nikhil_ko/16:45
*** praveens has quit IRC16:45
elmikomiguelgrinberg: +116:45
cdentmiguelgrinberg: yeah that probably gets to the core of my question: is changes-since is an implementation dependent use of generic sorting16:45
sdagueand I agree, the filtering guide probably is an appropriate place to talk about it16:45
cdentsounds like it is16:45
nikhil_kchanges-since is very non-scalable (my 2 cents)16:45
miguelgrinbergcdent: I see it as a query on a field of type timestamp16:45
sdaguenikhil_k: why is it non scalable?16:45
miguelgrinbergor datetime if you are Pythonic16:45
nikhil_kIf your database is N years old and your tenant has X thousand rows, this may result into a gigantic scan + join query16:46
sdaguenikhil_k: no, it's scanning updated_at, which you've got an index on16:46
sdagueso it's super scalable16:46
miguelgrinbergyou should index your datetime fields16:47
sdagueright, exactly, if you don't... well good luck16:47
nikhil_kright, but it won't return just the indexed rows16:47
edleafeIt actually helps scalability, as you don't pull data that hasn't changed16:47
sdaguenikhil_k: yes it will16:47
stevellenikhil_k: explain the join bit16:47
nikhil_khow about joins on other tables?16:47
nikhil_kOne example16:47
sdaguenikhil_k: well, don't crazy overnormalize your tables :)16:48
nikhil_kI can say without numbers on Rackspace public cloud that16:48
edleafenikhil_k: why is that worse than any other WHERE clause?16:48
woodster_elmiko: (thanks for the barbican mention above btw, just caught up)16:48
sdagueedleafe: right, exactly16:48
nikhil_kThe database is at least 5 years old and we have to purge the whole thing to keep only 90 days worth data to let the query run using chages-since16:48
elmikowoodster_: np, i know you had some questions about it16:48
nikhil_kThe worst case scenario is in image properties table16:49
nikhil_kwell, images have other tables that join over images one (like locations)16:49
sdaguenikhil_k: so I'd say that is a schema design problem16:49
*** bpokorny has quit IRC16:49
sdagueI don't think that changes-since is inherently non scalable, any more than any other criteria16:49
*** Swami has joined #openstack-meeting-316:50
*** nelsnelson has quit IRC16:50
nikhil_kSo, for example a tenant asks for changes-since 2 years. All images that are public, shared (And visible) and self creates would be retrieved16:50
*** bpokorny has joined #openstack-meeting-316:50
*** aduarte has joined #openstack-meeting-316:50
*** fitoduarte has joined #openstack-meeting-316:50
miguelgrinbergnikhil_k: using pagination, correct? you are not going to get all in one batch16:50
*** clu_ has joined #openstack-meeting-316:50
*** fitoduarte has quit IRC16:50
sdagueright, exactly16:50
nikhil_kBut it would be a mandatory thing for api that don't scale with it (unless I read the proposal wrond)16:50
*** aduarte has quit IRC16:50
nikhil_kwrong(16:50
sdaguethe fact that you aren't paging is a different problem16:51
nikhil_kmiguelgrinberg: pagination is another big issue.16:51
miguelgrinbergwhat's the problem?16:51
nikhil_kwe can set page sizes on clients, servers and apis that nova proxies16:51
elmikodoes the change-since topic need a post on ML, or can we debate it in the filtering review?16:51
elmikoalso, <10 min. left16:52
nikhil_kso, the latency of fetching can be inconsistent16:52
cdentI think on the review elmiko16:52
*** banix has joined #openstack-meeting-316:52
sdagueyeh, the filtering review should be fine16:52
cdentI hadn't realized raising the issue would be so interesting16:52
*** ajmiller has quit IRC16:52
elmikocdent: k, cool.16:52
cdentI was just trying to determine the extent to which it is worth considering for elsewhere16:52
*** fitoduarte has joined #openstack-meeting-316:52
elmiko#action cdent add changes-since language to filtering review16:53
sigmavirus24nikhil_k: so I'd argue that if we need to support changes-since that we should be able to change the response we provide16:53
elmikocdent: is that ok ^^?16:53
sigmavirus24so that we aren't joining tables if we dont' need to16:53
cdentmy takeaway is that the specifics of using that term are not germane, there are better more generic ways16:53
cdentyup elmiko16:53
sdagueso, I think we're exposing design issues in some of the projects in the process, which is good. In getting towards consistent APIs we're going to realize a lot of projects were just reflecting up very different db schema16:53
nikhil_kI see, also pagination can't be really trusted16:53
edleafecdent: it's pretty generic for data polling16:53
ryansbwell it's possible to do it as two queries, one with fewer/no joins and then a load of just the new records16:53
*** mrmartin has quit IRC16:54
*** vgridnev has quit IRC16:54
sdaguesigmavirus24: yeh, I think there is a lot of useful db optimization on a bunch of projects that makes all this work better as well, fortunately we can do db migrations to help on that as well :)16:54
*** vgridnev has joined #openstack-meeting-316:55
elmikoa little side-note, i had an action item from summit to contact the CPLs and do some outreach16:55
sigmavirus24sdague: glance hasn't had a good recent history with migrations =P16:55
elmikoi've shared the nova-inspired liaison responsibilities, and merge process review with most of the listed CPLs16:55
miguelgrinbergif there are no other topics, would you guys want to chat about HTTP caching?16:55
cdentmiguelgrinberg: in 5 minutes? ;)16:56
nikhil_ksdague: +1 on db optimization,  input would be appreciated. I would in general be hesitent on changes-since. we never had good experience with it16:56
miguelgrinbergcdent: I'm a dreamer :)16:56
elmikowe are still looking for CPLs from congress, designate, magnum, mistral, murano, rally, triple-o, and zaqar. if you know anyone, let me know =)16:56
elmikomiguelgrinberg: go for it, we'll carry over into openstack-api for those who are interested16:56
miguelgrinbergjust wanted to test the waters and see what you guys think. I really like to propose that we start adding caching headers to all APIs16:57
nikhil_kmiguelgrinberg: ++16:57
miguelgrinberga middleware that does the basic support would be nice16:57
elmikoi really like the middleware idea16:57
miguelgrinbergmaybe setting etags on all responses, and interpreting the conditional requests16:57
sdagueso, I was talking with krotscheck about that the other day16:58
krotscheckeh? wha?16:58
sdagueI'm not sure that etags middleware is going to do us a ton of good16:58
sdaguebecause you'll have to compute all the resources16:58
miguelgrinbergsdague: yes, it only saves bandwidth16:58
miguelgrinbergyou still have to run the server side handler16:58
sdagueright, and bw is rarely the concern here.16:58
sdagueIf we can get clients to not make calls they don't need to, that's a huge win16:59
miguelgrinbergso I'm thinking we have to add caching to our ersponses, so we might as well do the etags, since it does not hurt16:59
sdaguebut I don't think you can solve that with middleware, it has to be deeper in the project about what the cache-control really is for things16:59
elmikosorry, almost out of time, can we take this to openstack-api?16:59
*** hichihara has joined #openstack-meeting-316:59
sdagueyeh16:59
miguelgrinbergbut even adding a basiline cache-control header will be helpful16:59
elmikothanks everyone!16:59
elmiko#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
edleafethanks elmiko17:00
openstackMeeting ended Thu Jun  4 17:00:01 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
* cdent waves17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-06-04-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-06-04-16.00.txt17:00
*** VW has quit IRC17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-06-04-16.00.log.html17:00
*** ryansb has left #openstack-meeting-317:00
*** nikhil_k is now known as nikhil-afk17:01
*** SlickNik has joined #openstack-meeting-317:01
*** SlickNik has left #openstack-meeting-317:02
*** cdent has left #openstack-meeting-317:02
*** VW has joined #openstack-meeting-317:03
*** nbouthors has joined #openstack-meeting-317:03
*** ajmiller has joined #openstack-meeting-317:04
*** fitoduarte has quit IRC17:04
*** fitoduarte has joined #openstack-meeting-317:04
*** adduarte has joined #openstack-meeting-317:04
*** fitoduarte has quit IRC17:04
*** adduarte has quit IRC17:04
*** fitoduarte has joined #openstack-meeting-317:05
*** stevelle has left #openstack-meeting-317:05
*** fitoduarte has quit IRC17:05
*** fitoduarte has joined #openstack-meeting-317:06
*** fitoduarte is now known as duartea17:06
*** duartea is now known as adduarte17:07
*** adduarte is now known as fitoduarte17:08
*** Youcef has joined #openstack-meeting-317:12
*** marun has quit IRC17:12
*** salv-orlando has quit IRC17:12
*** s3wong has quit IRC17:13
*** marun has joined #openstack-meeting-317:13
*** hurgleburgler has quit IRC17:15
*** hurgleburgler has joined #openstack-meeting-317:16
*** nikhil-afk is now known as nikhil_k17:17
*** bradjones is now known as bradjones_away17:19
*** e0ne has quit IRC17:22
*** mwagner_afk has joined #openstack-meeting-317:24
*** Viswanath has joined #openstack-meeting-317:25
*** ajmiller_ has joined #openstack-meeting-317:28
*** mrmartin has joined #openstack-meeting-317:29
*** Viswanath has quit IRC17:30
*** ajmiller has quit IRC17:31
*** hichihara has quit IRC17:35
*** puranamr has quit IRC17:35
*** sqchen has quit IRC17:37
*** baoli has quit IRC17:38
*** marun has quit IRC17:39
*** fallenpegasus has joined #openstack-meeting-317:40
*** salv-orlando has joined #openstack-meeting-317:40
*** sqchen has joined #openstack-meeting-317:40
*** dims_ has quit IRC17:40
*** puranamr has joined #openstack-meeting-317:41
*** bpokorny_ has joined #openstack-meeting-317:42
*** john-davidge has quit IRC17:43
*** bpokorny has quit IRC17:43
*** VW_ has joined #openstack-meeting-317:46
*** SumitNaiksatam has joined #openstack-meeting-317:46
*** VW has quit IRC17:47
*** vnod has joined #openstack-meeting-317:48
*** s3wong has joined #openstack-meeting-317:48
*** SumitNaiksatam has quit IRC17:48
*** SumitNaiksatam has joined #openstack-meeting-317:49
*** singlethink has quit IRC17:51
*** mwang2 has joined #openstack-meeting-317:53
*** sbalukoff has joined #openstack-meeting-317:54
*** yamahata has quit IRC17:55
*** yamahata has joined #openstack-meeting-317:55
*** igordcard_ has joined #openstack-meeting-317:55
*** singlethink has joined #openstack-meeting-317:56
*** igordcard_ has quit IRC17:56
*** igordcard_ has joined #openstack-meeting-317:56
*** ajmiller_ has quit IRC17:57
*** ajmiller_ has joined #openstack-meeting-317:57
*** rushiagr is now known as rushiagr_away17:57
*** nbouthors has quit IRC17:59
*** rkukura has joined #openstack-meeting-317:59
*** singleth_ has joined #openstack-meeting-317:59
SumitNaiksatamrkukura: igordcard_ yamahata: hi18:01
rkukurahi18:01
*** elmiko has left #openstack-meeting-318:01
igordcard_SumitNaiksatam: hi18:01
igordcard_hi all18:01
s3wonghello18:01
*** Viswanath has joined #openstack-meeting-318:01
*** barra204 has joined #openstack-meeting-318:01
yamahatahello18:02
SumitNaiksatams3wong: hi18:02
s3wongapparently 1800 UTC means something else for service chaining meeting :-)18:02
SumitNaiksatamok lets get started18:02
SumitNaiksatams3wong: ;-)18:02
igordcard_s3wong: indeed...18:02
SumitNaiksatam#startmeeting networking_policy18:02
openstackMeeting started Thu Jun  4 18:02:57 2015 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: networking_policy)"18:03
openstackThe meeting name has been set to 'networking_policy'18:03
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#June_4th.2C_201518:03
*** dtroyer has left #openstack-meeting-318:03
SumitNaiksatamis ajay or amit here?18:03
*** singlethink has quit IRC18:03
*** yapeng has left #openstack-meeting-318:03
*** yapeng has joined #openstack-meeting-318:04
SumitNaiksatamyapeng: hi18:04
*** Viswanath has quit IRC18:04
yapenghello, everyone18:04
*** ransari has joined #openstack-meeting-318:05
SumitNaiksatamsorry for the delay, i was looking for amit, ajay, magesh and ivar18:05
SumitNaiksatambut none of them seem to be on18:05
SumitNaiksatamah ransari is here, thanks for joining rukhsana18:05
SumitNaiksatam#topic Bugs18:05
*** openstack changes topic to "Bugs (Meeting topic: networking_policy)"18:05
ransariyou're welcome sumit18:05
*** mrmartin has quit IRC18:06
SumitNaiksatamwe did not have any critical bugs in the last week18:06
*** tellesnobrega_ has joined #openstack-meeting-318:06
SumitNaiksatamhowever a bunch of new High priority ones got added18:06
*** barra204 has quit IRC18:07
SumitNaiksatam#link https://bugs.launchpad.net/group-based-policy/+bugs?search=Search&field.importance=High&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress&field.status=Fix+Committed18:07
*** amitbose has joined #openstack-meeting-318:08
*** Ajay_ has joined #openstack-meeting-318:08
SumitNaiksatammore specifically, we ajay (who was planning to join), is one of the first users actually writing to our API, found a bunch of stuff18:08
Ajay_joined now18:08
Ajay_sorry confused with UTC time18:08
SumitNaiksatamah, and there he is, right on cue - Ajay_: hi18:08
*** dims_ has joined #openstack-meeting-318:08
SumitNaiksatamamitbose: we see you too, thanks for joining18:08
*** ivar-lazzaro has joined #openstack-meeting-318:09
SumitNaiksatamwill get to the packaging in a minute18:09
ivar-lazzarohello, sorry I'm late18:09
SumitNaiksatamso as i was saying, Ajay_ is one of the first brave new users of the GBP API18:09
SumitNaiksatamivar-lazzaro: np, we are just getting warmed up ;-)18:09
Ajay_i am integrating GBP into Rally18:09
SumitNaiksatamAjay_: yes thanks18:10
Ajay_tests i mean18:10
SumitNaiksatamso he has been looking at various different aspects as he is working through writing the Rally tests18:10
SumitNaiksatamhe has also posted a bunch of bugs, which i think are very good feedback for the team here18:10
Ajay_so far 5 UI bugs and a 3 were non UI issues18:11
SumitNaiksatamAjay_: do you feel comfortable pointing out a few of the high priority bugs and/or generall issues that you are seeing?18:11
Ajay_ya mainly the UI issues with regards to presenting the view to users18:11
*** Aish has joined #openstack-meeting-318:11
SumitNaiksatamAjay_: but i think some of your observations on the service and API side are more pressing18:12
*** Aish has left #openstack-meeting-318:12
Ajay_ya for API side18:12
Ajay_these issues18:12
Ajay_https://bugs.launchpad.net/group-based-policy/+bug/146202418:12
openstackLaunchpad bug 1462024 in Group Based Policy "Concurrent create_policy_target_group call fails" [High,Confirmed] - Assigned to Robert Kukura (rkukura)18:12
Ajay_where concurrent usage of policy target group was causing issues18:12
Ajay_https://bugs.launchpad.net/group-based-policy/+bug/146083118:13
openstackLaunchpad bug 1460831 in Group Based Policy "API for group update is not clear" [High,Confirmed] - Assigned to Sumit Naiksatam (snaiksat)18:13
Ajay_for Group update API18:13
Ajay_and there is one more on treatment of orphaned openstack resources18:13
Ajay_those sumit where the ones from API18:14
SumitNaiksatamAjay_: yes18:14
Ajay_also i was faced with no documentation on python API18:14
SumitNaiksatamright18:14
Ajay_which makes the development cycle for app users writing applications on top of GBP longer18:14
SumitNaiksatamso as a user, Ajay_ expected that there be a python SDK that he could have used18:15
SumitNaiksatamand we dont have one18:15
ivar-lazzaroAjay_: that's great feedback!18:15
Ajay_also i noticed a few cases where i am deviating from intenant18:15
ivar-lazzaroSumitNaiksatam: do other OpenStack projects have a SDK?18:15
SumitNaiksatamthis is an area we have to address immediately, so if there’s anyone wanting to work on this, please let me know18:15
SumitNaiksatamivar-lazzaro: yes18:15
Ajay_example i still need to specify quoatas in neutron still need to know neutron port to attach A VM etc18:16
SumitNaiksatam#link https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0CC4QFjAA&url=https%3A%2F%2Fwiki.openstack.org%2Fwiki%2FSDK-Development%2FPythonOpenStackSDK&ei=35VwVZcIxfygBPeUgYgC&usg=AFQjCNEl4q5Yu_SQZLQFWQNQlOlp73kIDQ&sig2=KLHnZGp8bQzWCrWb77AN6Q&bvm=bv.95039771,d.cGU18:16
Ajay_as an App API user i want to perform all operations in intent and dont want to keep track of neutron18:16
*** Youcef has quit IRC18:16
SumitNaiksatamAjay_: i believe we should track that as a bug too18:16
*** sballe has joined #openstack-meeting-318:17
SumitNaiksatamivar-lazzaro: for the integrated projects, they were part of the SDK18:17
ransariSumit:Ajay: w.r.t  1460831 - does the bug translate to "Why is a key of provider/consumer required if it is already called out in the CLI via --provided-rule-set?"18:17
SumitNaiksatamivar-lazzaro: however we can use that SDK as a lib, and build our own18:17
ivar-lazzaroSumitNaiksatam: I found this #link https://github.com/stackforge/python-openstacksdk18:17
SumitNaiksatamransari: yes18:17
ransarisumit: ok18:17
SumitNaiksatamivar-lazzaro: yes, thats the one18:18
SumitNaiksatamransari: sorry, it relates to “what is the use of the scope, and its confusing the way its structured”18:18
Ajay_Sumit which one quota one or the neutron port knowledge to attach VM what needs a bug?18:18
SumitNaiksatamAjay_: the quota one18:18
ivar-lazzaroAjay_: we had a wrapper in the client for VM creation with --group option18:18
SumitNaiksatamAjay_: for the neutron port, we will address that as a part of the compute integration18:19
Ajay_also even if we dont have a SDK immediatly documentation on the current python API , Like REST body to use would be useful18:19
ivar-lazzaronot sure if it's part of the current release anymore18:19
SumitNaiksatamAjay_: agree, we will try to address this one way or the other at the earliest18:19
SumitNaiksatamivar-lazzaro: its probably not18:19
SumitNaiksatamivar-lazzaro: i mean its not, and it probably wont be18:20
*** songole has joined #openstack-meeting-318:20
Ajay_we cant expect application developers using GBP to capture output from CLI and than put those REST body in their python scripts ....18:20
Ajay_thats all i had on feedback18:20
Ajay_for this week18:20
SumitNaiksatamAjay_: yes, agreed, and apologies for making you do that18:20
yapengcurrently all APIs are in python language?18:21
SumitNaiksatamAjay_: great, thanks much (but dont go away)18:21
SumitNaiksatamyapeng: true18:21
Ajay_yes wont18:21
ransariAjay: in terms of documentation, is the expectation something along the lines of:  http://developer.openstack.org/api-ref-networking-v2.html18:22
SumitNaiksatamyapeng: but we still need an SDK that abstracts the client side usage18:22
SumitNaiksatamransari: did you just volunteer to do that? :-P18:22
Ajay_ransari: yes18:22
yapengSumitNaiksatam: makes sense18:22
*** Sukhdev has joined #openstack-meeting-318:22
ransariajay: ok18:22
ransarisumit: will discuss with hemanth if we can help out with that18:23
SumitNaiksatamthe WADL formatting is a bit time consuming to code18:23
SumitNaiksatamhence the delay in doing this18:23
SumitNaiksatamransari: sure18:23
SumitNaiksatamokay, i know we deviated a little bit from the usual meeting flow today (and perhaps we should called this topic - User Feedback), but i wanted to get Ajay_’s input while its fresh in his mind18:24
SumitNaiksatam#topic Test - Functional, Integration, Rally18:25
*** openstack changes topic to "Test - Functional, Integration, Rally (Meeting topic: networking_policy)"18:25
SumitNaiksatamnote that i added Rally here18:25
SumitNaiksatamso like Ajay_ mentioned he has been working on writing these tests18:25
*** eghobo_ has joined #openstack-meeting-318:25
SumitNaiksatamAjay_: can you give a quick summary of the scenarios that you are currently targeting?18:25
Ajay_I am testing all the Implicit Policy APIs for functional, concurrency and scale18:26
Ajay_to do this i am using the python client API to code these tests in Rally benchmark tool18:26
Ajay_so far policy actions/calissifiers/rule/ruleset/target group/target are codes18:26
Ajay_coded18:26
Ajay_these APIs i mean18:27
*** singlethink has joined #openstack-meeting-318:27
*** eghobo has quit IRC18:27
SumitNaiksatamAjay_: why do you say “implicity policy” APIs?18:27
Ajay_code is in my github under username: akalambu forked rally repo18:27
Ajay_as in i create a policy target group18:27
Ajay_and it creates a L2 and L3 policy18:27
SumitNaiksatamAjay_: ok18:27
SumitNaiksatamyou mean the implicity workflows18:27
SumitNaiksatamAjay_: great!18:28
Ajay_next would be explicit L2/L3 policy and external network18:28
SumitNaiksatamAjay_: as regards a home for the tests18:28
SumitNaiksatamAjay_: these should be in the GBP upstream repo18:28
*** singlet__ has joined #openstack-meeting-318:28
Ajay_i can speak to Boris and see if he is ready to accept this upstream?18:28
*** amotoki has joined #openstack-meeting-318:28
Ajay_Boris is Rally PTL18:28
SumitNaiksatamAjay_: ah, i was thinking this should be part of the GBP repo18:29
SumitNaiksatamother projects do it that way18:29
Ajay_ok18:29
*** bradjones_away is now known as bradjones18:29
*** tellesnobrega_ has quit IRC18:29
Ajay_ya we can do that too18:29
*** tellesnobrega_ has joined #openstack-meeting-318:29
*** tellesnobrega_ has quit IRC18:29
SumitNaiksatamAjay_: yeah, we can have a “rally” directory here #link https://github.com/stackforge/group-based-policy/tree/master/gbpservice/tests18:30
SumitNaiksatamor in any other location that makes sense18:30
SumitNaiksatamwhat does the rest of the team think about this?18:30
Ajay_sumit: issue is it needs rally infra to run18:30
Ajay_which is in a different rpo18:30
Ajay_repo18:30
*** singleth_ has quit IRC18:30
SumitNaiksatamAjay_: yes agreed18:30
SumitNaiksatamAjay_: but we have integration tests that need devstack too18:31
igordcard_seems okay to me, have no issue with it18:31
SumitNaiksatamAjay_: so we would have a separate job that would setup the rally infra to exercise these tests18:31
SumitNaiksatamigordcard_: ok good18:31
Ajay_sumit: sounds good will work on i18:31
*** tellesnobrega_ has joined #openstack-meeting-318:32
SumitNaiksatamAjay_: ok cool, we can connect offline to discuss the feasibility and mechanics of this18:32
*** singlethink has quit IRC18:32
Ajay_sumit: sounds good18:32
SumitNaiksatamany questions for Ajay_ on this?18:32
ivar-lazzaroI would go with as much in-tree as possible at least as far as the tests are concerned18:32
*** tellesnobrega_ has quit IRC18:32
SumitNaiksatamivar-lazzaro: +118:32
ivar-lazzaroso that any developer can write basic tests for their new features18:32
ivar-lazzarowho knows... Maybe even as a requirement :p18:33
SumitNaiksatamivar-lazzaro: integration tests should definitely be a requirement18:33
SumitNaiksatamunfortunately we are not there yet18:33
*** amotoki has quit IRC18:33
SumitNaiksatamexercise script is helping in some way18:33
SumitNaiksatamAjay_: thanks much for your work and update on this as well!18:34
Ajay_sumit: welcome18:34
SumitNaiksatami dont have any updates on the functional and integration tests18:34
SumitNaiksatam#topic Packaging18:34
*** openstack changes topic to "Packaging (Meeting topic: networking_policy)"18:34
SumitNaiksatamfolks, apart from Ajay_ we have a second new member to the team as well, please welcome amitbose18:35
amitboseHello!18:35
ivar-lazzaroamitbose: Welcome!18:35
igordcard_Hello amitbose!18:35
SumitNaiksatamamitbose is currently focussing on the ubuntu packagind and has made good progress18:35
yapengamtibose: Hi!18:35
SumitNaiksatamrkukura: last week you asked about this, i believe amitbose will be able to give an update18:35
SumitNaiksatamamitbose: over to you18:35
rkukuragreat!18:35
amitboseSo far I've been looking at build packages from stable/juno branch, but it should be pretty straight forward to port them for kilo18:36
SumitNaiksatamamitbose: ok18:36
SumitNaiksatamamitbose: and we will be posting them on the ppa?18:37
amitboseyeah, sure I can do that ... I will need the signing key though18:37
SumitNaiksatam#link https://launchpad.net/~group-based-policy-drivers/+archive/ubuntu/ppa18:37
SumitNaiksatamamitbose: ok lets discuss that offline18:37
SumitNaiksatamamitbose: thanks for the update, looking forward to more in the coming weeks18:38
SumitNaiksatamrkukura: anything at your end for the k-3 packages on fedora?18:38
rkukuraamitbose: Lets compare notes at some point regareing Red Hat vs. Ubuntu packaging18:38
*** yapeng has quit IRC18:39
ransariHello amitbose18:39
SumitNaiksatamrkukura: yes definitely, had meant to send you an email prior to this meeting on that topic18:39
rkukuraI have not yet put much effort into updating the Fedora packages to k-3, but expect to get this done in the next couple days18:39
SumitNaiksatamrkukura: ok thanks18:39
*** openstackstatus has joined #openstack-meeting-318:39
*** ChanServ sets mode: +v openstackstatus18:39
SumitNaiksatamransari: did you have a question for amitbose?18:40
rkukuraAnd I’d like to start looking into delorean and how that would impact us18:40
amitboseOne question: do we need packages only the latest milestone (2015.1.0.0b3) or earlier ones as well?18:40
Ajay_rkurkura: will the instructions you sent for RDO work on RHEL OSP618:40
SumitNaiksatamrkukura: okay, but that will not impact us for kilo, right?18:40
*** bradjones is now known as bradjones_away18:40
rkukuraprobably not immediately for kilo, but I think they are working to support stable branches for k foreward18:41
*** tellesnobrega_ has joined #openstack-meeting-318:41
rkukuraAjay_: OSP6 would be similar, except that the GBP packages are not yet in the OSP yum repo, so you’d need to add the RDO repo or some other repo, or install packages explicitly18:42
-openstackstatus- NOTICE: Gerrit has been restarted to clear an issue with its event stream. Any change events between 17:25 and 18:38 UTC should be rechecked or have their approvals reapplied to initiate testing.18:42
SumitNaiksatamrkukura: can we capture that detail on the wiki page?18:42
Ajay_rkukura: can we get the right repo to use...thats always the issue with RHEL18:43
rkukuraSumitNaiksatam: I’m not sure putting OSP details on the RDO wiki page is appropriate, but we can find somewhere18:43
*** tellesnobrega_ has quit IRC18:43
SumitNaiksatamrkukura: okay18:44
*** VW_ has quit IRC18:44
rkukuraThe standard RDO repos work with RHEL, CentOS, and Fedora, but not necessarily with RHEL OSP18:44
Ajay_rukukura/sumit: lets discuss the RHEL OSP part offline in email18:45
*** tellesnobrega_ has joined #openstack-meeting-318:45
rkukuraMost likely the RDO RHEL packages will work on the corresponding RHEL OSP release, but there could be dependency issues, and it would be important to make sure RDO packages don’t have priority over supported OSP packages.18:45
SumitNaiksatamAjay_: rkukura: ok lets take this offline, we are begind schedule18:47
SumitNaiksatamrkukura: thanks for the update on this!18:47
rkukuraok18:47
*** ajo has quit IRC18:47
SumitNaiksatam#topic Kilo features18:48
*** openstack changes topic to "Kilo features (Meeting topic: networking_policy)"18:48
SumitNaiksatamfloating ip support: #link https://review.openstack.org/#/c/16717418:48
SumitNaiksatamthe exercise script is validating that this is working per the current design18:48
SumitNaiksatamplease review and comment if you have objections with this patch going forward18:48
SumitNaiksatamelse we need to close on this soon18:48
*** VW has joined #openstack-meeting-318:49
SumitNaiksatamService chain driver refactoring: #link https://review.openstack.org/#/q/status:open+project:stackforge/group-based-policy+branch:master+topic:bp/node-centric-chain-plugin,n,z18:49
SumitNaiksatamivar-lazzaro has been deligently pluggin away on this and updating the patches18:49
SumitNaiksatamand it has shaped up really nicely18:49
SumitNaiksatamso lets provide the review support for this as well18:50
SumitNaiksatamand try to close on this at the earliest18:50
igordcard_I haven't yet had a chance to calmly review all the latest patches on that but will do it throughout today and this weekend18:50
ivar-lazzaroHopefully I'll be able to provide a driver for testing it soon18:50
SumitNaiksatamigordcard_: yes being calm is important, its a lot of stuff :-)18:50
ivar-lazzaroigordcard_: thanks!18:51
SumitNaiksatamivar-lazzaro: my assumption is that we will at least have a heat-based driver to test the basic integration with the neutron services like before?18:51
SumitNaiksatamivar-lazzaro: so that our exercise scripts can be used to validate that18:51
ivar-lazzaroSumitNaiksatam: I thought magesh is working in something heat based18:51
SumitNaiksatamivar-lazzaro: okay18:52
ivar-lazzaroSumitNaiksatam: so I thought I would do the Nova driver instead18:52
ivar-lazzaroSumitNaiksatam: which will also make proper use of the plumber and should nicely integrate with igordcard_ work18:52
SumitNaiksatamransari: songole: so magesh is working on porting the appliance driver for the neutron services?18:52
SumitNaiksatamivar-lazzaro: okay18:52
igordcard_yep18:52
igordcard_what is the current date for the final kilo-gbp? https://etherpad.openstack.org/p/kilo-gbp-plan seems to be outdated18:53
songoleSumitNaiksatam: not sure. will find out.18:53
SumitNaiksatamigordcard_: you need to rebase your patch?18:53
SumitNaiksatamigordcard_: we are looking at Kilo release for the end of this month latest18:53
songoleSumitNaiksatam: started reviewing the patches. Hope to complete over the weekend.18:53
igordcard_SumitNaiksatam: probably, I had already rebased it once, but it should be no problem in its current state18:53
SumitNaiksatamso we will try to get into the RC phase in about 10 days time frame18:53
SumitNaiksatamsongole: okay18:54
igordcard_SumitNaiksatam: okay, thanks, will write that down on calendar18:54
SumitNaiksatamwhich means that we need all this reviewed at the earliest18:54
SumitNaiksatamany thoughts/comments/objections on either of the above features being discussed?18:55
*** sqchen has quit IRC18:55
ransari<sumit> Magesh will start work on porting appliance to service-node model sometime next week18:56
SumitNaiksatamivar-lazzaro: thanks for the update and the fantastic work so far!18:56
SumitNaiksatamransari: next week???18:56
SumitNaiksatamransari: lets discuss offline18:56
ivar-lazzaroThere was one more feature I wanted to discuss, but I guess I'll send out an email instead18:56
SumitNaiksatamwe need to be able to validate that all this works end-to-end, and without a driver how do we do that?18:56
ransarisumit: once service refactor  review is cmpletd and merge to kilo is done18:57
SumitNaiksatamivar-lazzaro: ok, you can summarize here18:57
ransarisumit: we can discuss offline18:57
ivar-lazzaroGiven how many operations we issue in the backend (postcommit), I believe it's critical for usability to move our project towards a promise theory approach18:57
SumitNaiksatamransari: i would have preferred to see the driver in place in parallel, since the service refactor work does include the refactored reference driver18:57
*** sqchen has joined #openstack-meeting-318:58
SumitNaiksatamivar-lazzaro: okay18:58
ivar-lazzaroBut even before doing that, having an asynchronous backend is critical18:58
SumitNaiksatamivar-lazzaro: yes, okay so thats a longer discussion ;-)18:58
ivar-lazzaroSumitNaiksatam: it is :)18:58
rkukuraivar-lazzaro: Do you feel TaskFlow is up to the job for this?18:58
SumitNaiksatamivar-lazzaro: thanks for bringing it up18:58
ivar-lazzarorkukura: definetively, but I think we need a solution for Kilo18:59
SumitNaiksatamrkukura: i would assume we use it to realize the async18:59
SumitNaiksatamivar-lazzaro: hmmm, kilo might be challenging, but perhaps you have thought through this18:59
SumitNaiksatamlets discuss offline until next meeting18:59
ivar-lazzarorkukura: otherwise usability will not be great (or even fair)18:59
*** krtaylor has quit IRC18:59
ivar-lazzarook18:59
SumitNaiksatam#topic Liberty features19:00
*** openstack changes topic to "Liberty features (Meeting topic: networking_policy)"19:00
SumitNaiksatami trust the other folks - yapeng, yi are working in parallel on the kilo features19:00
SumitNaiksatamwe will get spending more time on those once the kilo backlog is cleared19:00
SumitNaiksatamokay so we are out of time for today19:01
SumitNaiksatamany parting thoughts?19:01
rkukuraivar-lazzaro: Lets discuss async/TaskFlow tomorrow if possible.19:01
igordcard_liberty features: probably that drag-and-drop SC UI, but for kilo most likely not19:01
ivar-lazzarorkukura: yes!19:01
ivar-lazzaroSumitNaiksatam: yes, the renaming!19:02
ivar-lazzaro#link https://etherpad.openstack.org/p/gbp-rename-proposals19:02
SumitNaiksatamigordcard_: yes that for kilo19:02
SumitNaiksatamivar-lazzaro: yes, thanks for the reminder19:02
ivar-lazzarohere are a bunch of proposals19:02
ivar-lazzaroI'm very sad about "Meta" and19:02
ivar-lazzaro"Regi'a19:02
ivar-lazzarobeing unusable19:02
igordcard_I still like intento19:03
ivar-lazzaroI'll start a poll today19:03
igordcard_ivar-lazzaro: cool19:03
SumitNaiksatamivar-lazzaro: lets hold on the poll19:03
ivar-lazzarohopefully we'll have a decision by next week (or before Kilo closes)19:03
ivar-lazzaroSumitNaiksatam: why is that?19:03
*** vishwana_ has joined #openstack-meeting-319:04
SumitNaiksatamivar-lazzaro: give people some time to thing19:04
SumitNaiksatamthink19:04
rkukuraWhy not rename in liberty at the time we become a standalone server?19:04
ivar-lazzaro(by the way I wonder who proposed "Membrane"... It reminds me of something :) )19:04
SumitNaiksatami would prefer to get people focussed on getting kilo done first19:04
ivar-lazzaroSumitNaiksatam: fair enough19:04
SumitNaiksatamivar-lazzaro: i proposed membrain19:04
SumitNaiksatamnote, its not membrane ;-)19:04
ivar-lazzaroSumitNaiksatam: lol :D! was the Embrane reference intended?19:05
SumitNaiksatamrkukura: yeah19:05
*** puranamr has quit IRC19:05
SumitNaiksatamivar-lazzaro: it might seem like, but no :-P19:05
SumitNaiksatamalright, lets wrap it up for today19:05
ivar-lazzaroSumitNaiksatam: the company name actually derives from membrane... But we digress19:05
SumitNaiksatamivar-lazzaro: i would image :-)19:05
SumitNaiksatamthanks all!19:05
SumitNaiksatambye19:05
songolebye19:06
ivar-lazzaroadieuuu19:06
igordcard_bye all19:06
SumitNaiksatam#endmeeting19:06
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:06
openstackMeeting ended Thu Jun  4 19:06:08 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:06
rkukurabye, and thanks SumitNaiksatam!19:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-06-04-18.02.html19:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-06-04-18.02.txt19:06
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-06-04-18.02.log.html19:06
*** clu_ has quit IRC19:06
*** rkukura has left #openstack-meeting-319:06
*** songole has quit IRC19:06
*** ransari has quit IRC19:06
*** vishwanathj has quit IRC19:06
*** Ajay_ has quit IRC19:07
*** amitbose has left #openstack-meeting-319:09
*** Longgeek has quit IRC19:12
*** puranamr has joined #openstack-meeting-319:14
*** salv-orlando has quit IRC19:15
*** Viswanath has joined #openstack-meeting-319:18
*** aa_ has joined #openstack-meeting-319:19
*** aa_ has quit IRC19:19
*** Viswanath has quit IRC19:21
*** krtaylor has joined #openstack-meeting-319:23
*** salv-orlando has joined #openstack-meeting-319:23
*** cknight has quit IRC19:27
*** puranamr has quit IRC19:28
*** cknight has joined #openstack-meeting-319:28
*** puranamr has joined #openstack-meeting-319:37
*** puranamr has quit IRC19:38
*** matrohon has joined #openstack-meeting-319:42
*** beagles is now known as beagles_brb19:43
*** clu_ has joined #openstack-meeting-319:48
*** VW has quit IRC19:49
*** VW has joined #openstack-meeting-319:49
*** sarob has quit IRC19:50
*** puranamr has joined #openstack-meeting-319:52
*** peterstac-m has quit IRC19:53
*** puranamr has quit IRC19:54
*** VW has quit IRC19:54
*** e0ne has joined #openstack-meeting-319:55
*** Viswanath has joined #openstack-meeting-319:55
*** puranamr has joined #openstack-meeting-319:56
*** baoli has joined #openstack-meeting-319:57
*** nelsnelson has joined #openstack-meeting-319:59
*** VW has joined #openstack-meeting-320:00
*** marun has joined #openstack-meeting-320:00
*** sarob has joined #openstack-meeting-320:00
megmHello, HA people!20:00
*** Viswanath has quit IRC20:00
mattgriffinmegm, howdy20:01
*** singlethink has joined #openstack-meeting-320:01
mattgriffin1 sec... gotta refresh on the meetingbot commands20:03
mattgriffin#startmeeting HA-Guide20:03
openstackMeeting started Thu Jun  4 20:03:42 2015 UTC and is due to finish in 60 minutes.  The chair is mattgriffin. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:03
*** openstack changes topic to " (Meeting topic: HA-Guide)"20:03
openstackThe meeting name has been set to 'ha_guide'20:03
mattgriffinok... and now the agenda20:04
mattgriffin#link https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update#Next_Meeting20:04
mattgriffinmegm, seen any others around lately?20:04
megmNoone I recognize but I'm hoping your email may bring in some new people20:05
*** singlet__ has quit IRC20:05
mattgriffinack20:06
*** Viswanath has joined #openstack-meeting-320:07
*** nelsnelson has quit IRC20:07
*** baoli has quit IRC20:08
megmWho is here for the ha-guide meeting?20:09
*** Viswanath has quit IRC20:10
* mattgriffin scans list of people in this channel20:10
megmI see that merged material now appears at http://docs.openstack.org/draft/ha-guide/20:11
mattgriffinyeah. that's really cool!20:11
megmIt will be cooler when we get some more stuff merged ;-)20:12
mattgriffinmegm, ok to hang here for a little while longer? if no one else shows up, i'll send our usual attendees a note about the plan we discussed (that I included in my docs email about an hour ago)20:13
megmI'm good with hanging and waiting a bit...20:13
mattgriffinok20:14
* mattgriffin takes a look at pending reviews :)20:15
*** SumitNaiksatam has quit IRC20:15
*** SumitNaiksatam has joined #openstack-meeting-320:16
*** Viswanath has joined #openstack-meeting-320:16
*** baoli has joined #openstack-meeting-320:16
mattgriffinmegm, are you still noting here (https://etherpad.openstack.org/p/openstack-haguide-update-next-steps) where you are in the docbook->rst conversion process?20:17
*** amotoki has joined #openstack-meeting-320:17
megmYes.20:17
*** stevemar has quit IRC20:18
*** baoli has quit IRC20:18
megmI didn't accomplish a lot yesterday, alas...20:18
*** baoli has joined #openstack-meeting-320:18
mattgriffin:)20:18
mattgriffinbut you need a few reviews here? https://review.openstack.org/#/q/status:open+ha-guide,n,z20:19
megmYes.20:19
megmI was hoping that Shilla would join us -- she did the merges that are there.20:20
*** Viswanath has quit IRC20:20
*** VW has quit IRC20:20
megmDo you have the names of the five people who showed up in Vancouver in the afternoon?20:20
mattgriffini do not. had already left the room ... maybe in email20:21
* mattgriffin checks20:21
megmYou can look at the Comment history on the merged CRs and get some names, too.20:22
*** amotoki has quit IRC20:22
*** Sukhdev has quit IRC20:22
megmRadoslaw (Radek) Smigielski, Mark Muehl, Shilla Saebi...20:22
*** sarob has quit IRC20:22
mattgriffinmegm, gotcha. found the email thread20:23
mattgriffini'll include them in the message I send out directly to the team20:24
megmRadek has recent contribs to the XML version.20:24
megmAlso Christian Berendt -- recently contributed info about how to install RabbitMQ on openSUSE20:25
*** stendulker has joined #openstack-meeting-320:25
*** bradjones_away has quit IRC20:26
mattgriffinmegm, ok. let's call it. i'll send out an email directly to the group to keep them in the loop.20:26
megmSigh.  Okay, and I'll get back to converting the docs.20:26
mattgriffinok. thanks. ttyl20:27
mattgriffin#endmeeting20:27
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:27
openstackMeeting ended Thu Jun  4 20:27:13 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:27
megmhave a great week!20:27
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ha_guide/2015/ha_guide.2015-06-04-20.03.html20:27
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ha_guide/2015/ha_guide.2015-06-04-20.03.txt20:27
mattgriffinyou too20:27
openstackLog:            http://eavesdrop.openstack.org/meetings/ha_guide/2015/ha_guide.2015-06-04-20.03.log.html20:27
*** mattgriffin has quit IRC20:30
*** bradjones has joined #openstack-meeting-320:32
*** julim has quit IRC20:32
*** stendulker has quit IRC20:32
*** sarob has joined #openstack-meeting-320:33
*** lblanchard has quit IRC20:37
*** markvoelker has quit IRC20:41
*** sarob has quit IRC20:41
*** sarob has joined #openstack-meeting-320:42
*** peristeri has quit IRC20:42
*** Viswanath has joined #openstack-meeting-320:44
*** igordcard_ has quit IRC20:45
*** Viswanath has quit IRC20:47
*** cknight has quit IRC20:57
*** beagles_brb is now known as beagles21:00
*** e0ne has quit IRC21:05
*** s3wong_ has joined #openstack-meeting-321:16
*** s3wong_ has quit IRC21:17
*** s3wong_ has joined #openstack-meeting-321:17
*** s3wong_ has quit IRC21:18
*** s3wong has quit IRC21:20
*** hurgleburgler has left #openstack-meeting-321:20
*** tellesnobrega_ has quit IRC21:21
*** s3wong has joined #openstack-meeting-321:21
*** tmckay has left #openstack-meeting-321:25
*** ajmiller_ has quit IRC21:31
*** ajmiller_ has joined #openstack-meeting-321:32
*** asahlin is now known as asahlin_away21:33
*** baoli has quit IRC21:34
*** ivar-laz_ has joined #openstack-meeting-321:35
*** baoli has joined #openstack-meeting-321:35
*** salv-orlando has quit IRC21:35
*** sarob has quit IRC21:35
*** ivar-laz_ has quit IRC21:35
*** ivar-laz_ has joined #openstack-meeting-321:36
*** mattfarina has quit IRC21:37
*** mattfarina has joined #openstack-meeting-321:38
*** ivar-lazzaro has quit IRC21:38
*** mwagner_afk has quit IRC21:40
*** salv-orlando has joined #openstack-meeting-321:41
*** markvoelker has joined #openstack-meeting-321:41
*** markvoelker has quit IRC21:46
*** ajmiller_ has quit IRC21:47
*** ajmiller has joined #openstack-meeting-321:47
*** matrohon has quit IRC21:49
*** ivar-laz_ has quit IRC21:51
*** ivar-lazzaro has joined #openstack-meeting-321:52
*** mattfarina has quit IRC21:54
*** krtaylor has quit IRC21:56
*** wojdev has joined #openstack-meeting-322:03
*** puranamr has quit IRC22:04
*** stevemar has joined #openstack-meeting-322:05
*** amotoki has joined #openstack-meeting-322:06
*** banix has quit IRC22:08
*** ivar-lazzaro has quit IRC22:09
*** amotoki has quit IRC22:11
*** puranamr has joined #openstack-meeting-322:13
*** sigmavirus24 is now known as sigmavirus24_awa22:13
*** clu_ has quit IRC22:16
*** SumitNaiksatam has quit IRC22:17
*** vgridnev has quit IRC22:19
*** aleksandr_null_ has quit IRC22:22
*** aleksandr_null has joined #openstack-meeting-322:22
*** eghobo_ has quit IRC22:22
*** sarob has joined #openstack-meeting-322:23
*** jrist has quit IRC22:26
*** krtaylor has joined #openstack-meeting-322:27
*** bknudson has quit IRC22:28
*** Sukhdev has joined #openstack-meeting-322:29
*** huichun_ has quit IRC22:30
*** jrist has joined #openstack-meeting-322:33
*** SotK has quit IRC22:34
*** csd has quit IRC22:34
*** SotK has joined #openstack-meeting-322:34
*** csd has joined #openstack-meeting-322:35
*** baoli has quit IRC22:36
*** wojdev has quit IRC22:37
*** markvoelker has joined #openstack-meeting-322:42
*** markvoelker has quit IRC22:47
*** wojdev has joined #openstack-meeting-322:48
*** singlethink has quit IRC22:50
*** clu_ has joined #openstack-meeting-322:54
*** fallenpegasus has quit IRC22:55
*** sarob has quit IRC22:59
*** clu_ has quit IRC22:59
*** saneax has joined #openstack-meeting-323:04
*** wojdev has quit IRC23:05
*** carl_baldwin has quit IRC23:05
*** wojdev has joined #openstack-meeting-323:06
*** radek_ has quit IRC23:09
*** sdake_ has joined #openstack-meeting-323:09
*** sarob has joined #openstack-meeting-323:09
*** ivar-lazzaro has joined #openstack-meeting-323:16
*** sarob has quit IRC23:21
*** puranamr has quit IRC23:25
*** puranamr has joined #openstack-meeting-323:28
*** yamamoto has joined #openstack-meeting-323:28
*** enikanorov_ has quit IRC23:29
*** enikanorov__ has joined #openstack-meeting-323:29
*** fitoduarte has quit IRC23:29
*** zhenguo has joined #openstack-meeting-323:30
*** shwetaap1 has quit IRC23:33
*** ivar-lazzaro has quit IRC23:36
*** bradjones has quit IRC23:36
*** ivar-lazzaro has joined #openstack-meeting-323:36
*** bradjones has joined #openstack-meeting-323:39
*** puranamr has quit IRC23:40
*** eghobo has joined #openstack-meeting-323:41
*** bpokorny has joined #openstack-meeting-323:41
*** bpokorny_ has quit IRC23:41
*** eghobo_ has joined #openstack-meeting-323:43
*** sdake_ is now known as sdake23:44
*** eghobo has quit IRC23:46
*** yamamoto has quit IRC23:51
*** VW has joined #openstack-meeting-323:51
*** puranamr has joined #openstack-meeting-323:51
*** yamamoto has joined #openstack-meeting-323:53
*** salv-orlando has quit IRC23:53
*** shwetaap has joined #openstack-meeting-323:58
*** ajmiller has quit IRC23:59

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