Thursday, 2015-01-29

*** Brian_Shang has quit IRC00:01
*** xuhanp has joined #openstack-meeting-300:09
*** yamamoto has joined #openstack-meeting-300:09
*** etoews has quit IRC00:11
*** VW_ has quit IRC00:12
*** seizadi has quit IRC00:13
*** ericpeterson has quit IRC00:18
*** Yi_ has joined #openstack-meeting-300:18
*** vishwanathj has joined #openstack-meeting-300:19
*** sarob has joined #openstack-meeting-300:20
*** ongk has left #openstack-meeting-300:23
*** david-lyle is now known as david-lyle_afk00:28
*** Sukhdev has quit IRC00:30
*** xuhanp has quit IRC00:36
*** Sukhdev has joined #openstack-meeting-300:44
*** eghobo has joined #openstack-meeting-300:47
*** markvoelker has quit IRC00:48
*** banix has joined #openstack-meeting-300:48
*** yamamoto has quit IRC00:48
*** isq has quit IRC00:51
*** markvoelker has joined #openstack-meeting-300:59
*** baoli has joined #openstack-meeting-301:00
*** johnthetubaguy is now known as zz_johnthetubagu01:04
*** sarob_ has joined #openstack-meeting-301:05
*** sarob_ has quit IRC01:06
*** salv-orlando has joined #openstack-meeting-301:07
*** sarob has quit IRC01:07
*** salv-orlando has quit IRC01:08
*** banix has quit IRC01:10
*** esp has left #openstack-meeting-301:12
*** tellesnobrega_ has quit IRC01:15
*** jaypipes has quit IRC01:15
*** seizadi has joined #openstack-meeting-301:25
*** armax has quit IRC01:34
*** yapeng has joined #openstack-meeting-301:35
*** banix has joined #openstack-meeting-301:36
*** yapeng has quit IRC01:39
*** Sukhdev has quit IRC01:40
*** banix has quit IRC01:40
*** stanzgy has joined #openstack-meeting-301:40
*** sigmavirus24 is now known as sigmavirus24_awa01:42
*** marun has quit IRC01:46
*** lblanchard has joined #openstack-meeting-301:50
*** seizadi has quit IRC01:52
*** lblanchard has quit IRC01:54
*** banix has joined #openstack-meeting-301:55
*** alexsyip has quit IRC01:56
*** markvoelker has quit IRC01:57
*** markvoelker has joined #openstack-meeting-301:58
*** markvoelker has quit IRC02:02
*** seizadi has joined #openstack-meeting-302:06
*** yapeng has joined #openstack-meeting-302:08
*** SridharRamaswamy has quit IRC02:10
*** lblanchard has joined #openstack-meeting-302:11
*** marg7175 has quit IRC02:11
*** lblanchard has quit IRC02:12
*** lblanchard has joined #openstack-meeting-302:13
*** killer_prince has quit IRC02:13
*** lblanchard has quit IRC02:14
*** s3wong has quit IRC02:16
*** killer_prince has joined #openstack-meeting-302:31
*** killer_prince is now known as lazy_prince02:32
*** banix has quit IRC02:35
*** sunny_ has quit IRC02:38
*** tellesnobrega_ has joined #openstack-meeting-302:43
*** baoli has quit IRC02:47
*** mrmartin has joined #openstack-meeting-302:51
*** eghobo has quit IRC02:53
*** lblanchard has joined #openstack-meeting-302:54
*** lblanchard has quit IRC02:55
*** lblanchard has joined #openstack-meeting-302:56
*** lblanchard has quit IRC02:57
*** VW_ has joined #openstack-meeting-302:57
*** bpokorny_ has quit IRC02:58
*** lhcheng has quit IRC02:59
*** clu_ has quit IRC03:00
*** seizadi has quit IRC03:07
*** lblanchard has joined #openstack-meeting-303:08
*** lblanchard has quit IRC03:12
*** jckasper has joined #openstack-meeting-303:14
*** jckasper has quit IRC03:14
*** jckasper has joined #openstack-meeting-303:14
*** ongk has joined #openstack-meeting-303:19
*** lazy_prince has quit IRC03:19
*** sbalukoff has quit IRC03:35
*** Yi_ has quit IRC03:37
*** mrmartin has quit IRC03:39
*** baoli has joined #openstack-meeting-303:39
*** ivar-laz_ has joined #openstack-meeting-303:44
*** ivar-lazzaro has quit IRC03:47
*** ivar-laz_ has quit IRC03:49
*** dkehn has quit IRC03:52
*** dkehn has joined #openstack-meeting-303:52
*** yamahata has joined #openstack-meeting-304:06
*** yamahata has quit IRC04:11
*** badveli has quit IRC04:17
*** VW_ has quit IRC04:17
*** VW_ has joined #openstack-meeting-304:18
*** markvoelker has joined #openstack-meeting-304:21
*** Yi has joined #openstack-meeting-304:21
*** yamahata has joined #openstack-meeting-304:25
*** SumitNaiksatam has quit IRC04:25
*** SumitNaiksatam has joined #openstack-meeting-304:26
*** wchrisj has quit IRC04:27
*** killer_prince has joined #openstack-meeting-304:29
*** killer_prince is now known as lazy_prince04:29
*** yamahata has quit IRC04:29
*** Yi has quit IRC04:38
*** marg7175 has joined #openstack-meeting-304:42
*** lazy_prince has quit IRC04:44
*** rhagarty has quit IRC04:45
*** rhagarty has joined #openstack-meeting-304:46
*** tellesnobrega_ has quit IRC04:46
*** killer_prince has joined #openstack-meeting-304:46
*** killer_prince is now known as lazy_prince04:46
*** yamahata has joined #openstack-meeting-304:47
*** Yi has joined #openstack-meeting-304:51
*** yamahata has quit IRC04:52
*** markvoelker has quit IRC04:53
*** markvoelker_ has joined #openstack-meeting-304:53
*** sandr8 has quit IRC05:02
*** stanzgy has quit IRC05:04
*** sbalukoff has joined #openstack-meeting-305:08
*** Sukhdev has joined #openstack-meeting-305:11
*** Yi has quit IRC05:14
*** seizadi has joined #openstack-meeting-305:14
*** mestery has quit IRC05:15
*** mestery has joined #openstack-meeting-305:16
*** markvoelker_ has quit IRC05:16
*** carl_baldwin has joined #openstack-meeting-305:16
*** markvoelker has joined #openstack-meeting-305:16
*** stanzgy has joined #openstack-meeting-305:17
*** julim_ has joined #openstack-meeting-305:19
*** ctlaugh has quit IRC05:21
*** markvoelker has quit IRC05:22
*** sandr8 has joined #openstack-meeting-305:22
*** julim has quit IRC05:22
*** ctlaugh has joined #openstack-meeting-305:22
*** vishwanathj has quit IRC05:23
*** yapeng has quit IRC05:24
*** baoli has quit IRC05:24
*** marg7175 has quit IRC05:25
*** yamamoto_ has joined #openstack-meeting-305:27
*** seizadi has quit IRC05:33
*** Longgeek has joined #openstack-meeting-305:43
*** markvoelker has joined #openstack-meeting-305:47
*** markvoelker has quit IRC05:52
*** salv-orlando has joined #openstack-meeting-305:59
*** carl_baldwin has quit IRC06:02
*** Longgeek has quit IRC06:03
*** VW_ has quit IRC06:08
*** VW_ has joined #openstack-meeting-306:08
*** seizadi has joined #openstack-meeting-306:14
*** Yi has joined #openstack-meeting-306:14
*** Longgeek has joined #openstack-meeting-306:18
*** VW_ has quit IRC06:19
*** VW_ has joined #openstack-meeting-306:19
*** Yi has quit IRC06:21
*** Longgeek has quit IRC06:22
*** eghobo has joined #openstack-meeting-306:24
*** reed has quit IRC06:26
*** yapeng has joined #openstack-meeting-306:27
*** seizadi has quit IRC06:28
*** yapeng has quit IRC06:28
*** lazy_prince has quit IRC06:28
*** Sukhdev has quit IRC06:30
*** killer_prince has joined #openstack-meeting-306:43
*** killer_prince is now known as lazy_prince06:43
*** eghobo has quit IRC06:44
*** markvoelker has joined #openstack-meeting-306:48
*** vineetmenon has joined #openstack-meeting-306:48
*** JoshNang has quit IRC06:52
*** markvoelker has quit IRC06:52
*** evgenyf has joined #openstack-meeting-306:55
*** mrunge has joined #openstack-meeting-306:59
*** JoshNang has joined #openstack-meeting-307:01
*** coolsvap|afk is now known as coolsvap07:10
*** salv-orlando has quit IRC07:11
*** Godfath3r has quit IRC07:15
*** markvoelker has joined #openstack-meeting-307:21
*** jaypipes has joined #openstack-meeting-307:22
*** markvoelker has quit IRC07:27
*** mrmartin has joined #openstack-meeting-307:28
*** sc68cal has quit IRC07:32
*** jaypipes has quit IRC07:33
*** nelsnels_ has joined #openstack-meeting-307:33
*** scheuran has joined #openstack-meeting-307:33
*** nelsnelson has quit IRC07:35
*** sc68cal has joined #openstack-meeting-307:36
*** sahid has joined #openstack-meeting-307:38
*** Godfath3r has joined #openstack-meeting-307:38
*** belmoreira has joined #openstack-meeting-307:40
*** aleksandr_null has quit IRC07:40
*** aleksandr_null has joined #openstack-meeting-307:42
*** yamahata has joined #openstack-meeting-307:44
*** sergef has joined #openstack-meeting-307:46
*** _crobertsrh has quit IRC07:46
*** crobertsrh has joined #openstack-meeting-307:47
*** Godfath3r has quit IRC07:47
*** yamahata has quit IRC07:49
*** VW_ has quit IRC07:50
*** jcoufal has joined #openstack-meeting-307:51
*** Yi has joined #openstack-meeting-307:51
*** matrohon has joined #openstack-meeting-307:53
*** Yi has quit IRC07:57
*** devvesa has joined #openstack-meeting-307:59
*** yamahata has joined #openstack-meeting-308:02
*** yamahata has quit IRC08:07
*** salv-orlando has joined #openstack-meeting-308:12
*** safchain has joined #openstack-meeting-308:13
*** salv-orlando has quit IRC08:16
*** yapeng has joined #openstack-meeting-308:16
*** yamamoto_ has quit IRC08:17
*** yamahata has joined #openstack-meeting-308:21
*** iovadia has joined #openstack-meeting-308:21
*** yapeng has quit IRC08:22
*** markvoelker has joined #openstack-meeting-308:25
*** yamahata has quit IRC08:25
*** iovadia has quit IRC08:26
*** mestery has quit IRC08:29
*** yamahata has joined #openstack-meeting-308:29
*** markvoelker has quit IRC08:31
*** mestery has joined #openstack-meeting-308:31
*** yamahata has quit IRC08:34
*** zz_ttrifonov is now known as ttrifonov08:35
*** MaxV has joined #openstack-meeting-308:35
*** jtomasek has joined #openstack-meeting-308:38
*** iovadia has joined #openstack-meeting-308:39
*** yamahata has joined #openstack-meeting-308:47
*** yamahata has quit IRC08:51
*** egallen has left #openstack-meeting-308:53
*** JeanBriceCombebi has joined #openstack-meeting-308:59
*** egallen has joined #openstack-meeting-309:00
*** salv-orlando has joined #openstack-meeting-309:12
*** watanabe_isao has quit IRC09:15
*** salv-orlando has quit IRC09:18
*** isviridov_away is now known as isviridov09:23
*** Longgeek has joined #openstack-meeting-309:23
*** Longgeek has quit IRC09:27
*** markvoelker has joined #openstack-meeting-309:28
*** VW_ has joined #openstack-meeting-309:33
*** scheuran has quit IRC09:34
*** markvoelker has quit IRC09:34
*** VW_ has quit IRC09:39
*** Yi has joined #openstack-meeting-309:42
*** Yi has quit IRC09:47
*** nelsnels_ has quit IRC09:48
*** JeanBriceCombebi has quit IRC09:49
*** scheuran has joined #openstack-meeting-309:49
*** nelsnelson has joined #openstack-meeting-309:49
*** JeanBriceCombebi has joined #openstack-meeting-309:49
*** salv-orlando has joined #openstack-meeting-310:00
*** igordcard has joined #openstack-meeting-310:02
*** matrohon has quit IRC10:04
*** JeanBriceCombebi has quit IRC10:04
*** yapeng has joined #openstack-meeting-310:06
*** JeanBriceCombebi has joined #openstack-meeting-310:06
*** yapeng has quit IRC10:10
*** tellesnobrega_ has joined #openstack-meeting-310:17
*** akamyshnikova has quit IRC10:20
*** akamyshnikova has joined #openstack-meeting-310:22
*** markvoelker has joined #openstack-meeting-310:30
*** markvoelker has quit IRC10:34
*** scheuran has quit IRC10:35
*** tellesnobrega_ has quit IRC10:43
*** scheuran has joined #openstack-meeting-310:49
*** stanzgy has quit IRC10:51
*** tellesnobrega_ has joined #openstack-meeting-311:00
*** sergef_ has joined #openstack-meeting-311:05
*** tellesnobrega_ has quit IRC11:06
*** sergef has quit IRC11:06
*** sergef_ is now known as sergef11:06
*** tellesnobrega_ has joined #openstack-meeting-311:07
*** tellesnobrega_ has quit IRC11:11
*** markvoelker has joined #openstack-meeting-311:31
*** Yi has joined #openstack-meeting-311:32
*** markvoelker has quit IRC11:35
*** igordcard has quit IRC11:37
*** Yi has quit IRC11:38
*** igordcard has joined #openstack-meeting-311:39
*** igordcard has quit IRC11:41
*** baoli has joined #openstack-meeting-311:48
*** amotoki has quit IRC11:51
*** yapeng has joined #openstack-meeting-311:55
*** yapeng has quit IRC11:59
*** jtomasek has quit IRC12:09
*** pkoniszewski has joined #openstack-meeting-312:13
*** lazy_prince has quit IRC12:14
*** killer_prince has joined #openstack-meeting-312:18
*** killer_prince is now known as lazy_prince12:18
*** baoli has quit IRC12:22
*** Yi has joined #openstack-meeting-312:30
*** markvoelker has joined #openstack-meeting-312:31
*** Brian_Shang has joined #openstack-meeting-312:33
*** markvoelker has quit IRC12:36
*** vineetmenon has quit IRC12:37
*** julim has joined #openstack-meeting-312:43
*** Yi has quit IRC12:44
*** baoli has joined #openstack-meeting-312:45
*** belmoreira has quit IRC12:46
*** julim_ has quit IRC12:46
*** baoli_ has joined #openstack-meeting-312:46
*** mwagner_lap has quit IRC12:47
*** baoli_ has quit IRC12:48
*** baoli has quit IRC12:50
*** baoli has joined #openstack-meeting-312:50
*** mrunge has quit IRC12:50
*** JeanBriceCombebi has quit IRC12:55
*** JeanBriceCombebi has joined #openstack-meeting-312:56
*** adam_g is now known as adam_g_out12:57
*** Networkn3rd has quit IRC13:00
*** jcoufal_ has joined #openstack-meeting-313:06
*** pkoniszewski has quit IRC13:07
*** jtomasek has joined #openstack-meeting-313:09
*** jcoufal has quit IRC13:09
*** edleafe has quit IRC13:16
*** edleafe has joined #openstack-meeting-313:18
*** Brian_Shang has quit IRC13:19
*** Brian_Shang has joined #openstack-meeting-313:20
*** Yi has joined #openstack-meeting-313:21
*** bknudson has quit IRC13:26
*** markvoelker has joined #openstack-meeting-313:33
*** markvoelker has quit IRC13:35
*** markvoelker_ has joined #openstack-meeting-313:35
*** amotoki has joined #openstack-meeting-313:41
*** yapeng has joined #openstack-meeting-313:44
*** bknudson has joined #openstack-meeting-313:48
*** yapeng has quit IRC13:48
*** weiting has joined #openstack-meeting-313:49
*** huichun has joined #openstack-meeting-313:50
*** elmiko has joined #openstack-meeting-313:51
*** marg7175 has joined #openstack-meeting-313:53
*** sigmavirus24_awa is now known as sigmavirus2413:55
*** VW_ has joined #openstack-meeting-313:58
*** sreshetnyak has joined #openstack-meeting-313:59
*** tosky has joined #openstack-meeting-314:00
*** egafford has joined #openstack-meeting-314:00
*** kchen has joined #openstack-meeting-314:01
elmikohello?14:03
kchenhi all14:04
alazarevo/14:04
aignatovo/14:04
weitingo/14:04
sreshetnyako/14:04
*** mattf has joined #openstack-meeting-314:04
toskyo/14:04
huichuno/14:04
elmikoSergeyLukjanov: =)14:04
SergeyLukjanovo/14:04
SergeyLukjanovhey folks14:04
SergeyLukjanov#startmeeting sahara14:04
openstackMeeting started Thu Jan 29 14:04:45 2015 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.14:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:04
*** openstack changes topic to " (Meeting topic: sahara)"14:04
openstackThe meeting name has been set to 'sahara'14:04
* mattf waves14:04
elmikoahh, there we go14:05
SergeyLukjanov#link https://wiki.openstack.org/wiki/Meetings/SaharaAgenda14:05
* mattf may have gone to -alt first, oops14:05
alazarevit's pain to wake up at 6am :)14:05
SergeyLukjanov#topic sahara@horizon status (crobertsrh, NikitaKonovalov)14:05
*** openstack changes topic to "sahara@horizon status (crobertsrh, NikitaKonovalov) (Meeting topic: sahara)"14:05
egaffordHello.14:05
NikitaKonovalovok14:05
mattfalazarev, not if you just got to PT from ET and you're 3hrs ahead14:05
SergeyLukjanov#link https://etherpad.openstack.org/p/sahara-reviews-in-horizon14:05
elmikolol14:05
NikitaKonovalovas you can see the changes now are getting some reviews14:06
mattffor later - let's drop "ex Savanna"14:06
SergeyLukjanovI've added an action item to the next cross-project meeting to discuss slow-merging patches issues14:06
NikitaKonovalovmostly -1 for code style or similar stuff14:06
NikitaKonovalovbut that's a progress anyway14:07
alazarevno progress on my horizon patchea14:07
NikitaKonovalovalazarev: you've got a +2 here https://review.openstack.org/#/c/140518/14:07
*** vgridnev_ has joined #openstack-meeting-314:08
NikitaKonovalovso I thinks we might get some of those merged soon14:08
alazarevNikitaKonovalov, and here https://review.openstack.org/#/c/140485/14:08
crobertsrhthanks for updating NikitaKonovalov....sorry I was late14:09
NikitaKonovalovso that's all the update from me14:09
SergeyLukjanovI hope we'll get faster reviews someday...14:10
SergeyLukjanov#topic News / updates14:10
*** openstack changes topic to "News / updates (Meeting topic: sahara)"14:10
SergeyLukjanovfolks, please14:10
elmikostill cranking away on the security docs, fixed some bugs, and a bunch o reviews14:10
SergeyLukjanovmattf, thanks for the oslo sync :) you're still the only how authorised to do it :)14:11
sreshetnyaki'm working on new integration tests and bux fixing14:11
toskyworking on tempest to remove the hardcoded dependencies on some plugins14:11
vgridnev_i'm working with hdp bug and event-log14:11
kchenplease help review the cdh version management patch https://review.openstack.org/#/c/147933/14:11
weitingworking on cdh plugin impala service testing14:11
kchento separate the codes for different cdh versions14:11
NikitaKonovalovas the new release of stable/jun approaches there is a list of backports that should be done. You can find a chain of changes here https://review.openstack.org/#/c/150825/14:12
egaffordWorking on the unified job interface map impl now that the spec is merged (thanks SergeyLukjanov.)14:12
huichunworking on cdh service testing14:12
*** mwagner_lap has joined #openstack-meeting-314:12
*** tmckay has joined #openstack-meeting-314:12
alazarevI created a few of specs: auto clean up, placeholders in data sources14:13
mattfSergeyLukjanov, it's muscle memory at this point. tho my plans are to obsolete myself. we can prune more and more these days.14:13
crobertsrhHere's a fairly early version of the guided cluster creation ("wizard") page.  Feel free to take a peek and comment.  https://review.openstack.org/#/c/147677/14:13
SergeyLukjanovmattf, heh14:13
SergeyLukjanovcrobertsrh, nice, /me need to to try14:14
*** marg7175 has quit IRC14:14
SergeyLukjanov#topic Kilo release schedule14:15
*** openstack changes topic to "Kilo release schedule (Meeting topic: sahara)"14:15
SergeyLukjanov314:15
SergeyLukjanov#link https://wiki.openstack.org/wiki/Kilo_Release_Schedule14:15
SergeyLukjanovkilo-2 is next week14:15
SergeyLukjanovand 2014.2.2 is next week two if I remember correctly14:15
*** banix has joined #openstack-meeting-314:16
SergeyLukjanovI'd like to enlarge stable-maint core team for sahara14:16
tmckayI should have spark-swift stuff in today, and I'm trying to verify cdh5 version for spark (from venza)14:16
SergeyLukjanovand so, I need volunteers to review and help with support of stabe/juno branch14:16
tmckayI volunteer14:16
tmckayare there docs somewhere on stable maint?14:16
SergeyLukjanovyup, I'll share it14:17
egaffordSergeyLukjanov: I'm pretty involved in stable maintenance downstream at Red Hat, so I'd like to volunteer too; fits in nicely with a lot of my work.14:17
SergeyLukjanov#link https://wiki.openstack.org/wiki/StableBranch14:17
SergeyLukjanovtmckay, egafford, ack14:18
SergeyLukjanov#topic some breaking change in saharaclient Python API to align with other clients (find vs findall, see first comment in https://review.openstack.org/#/c/150347/) (pas-ha, won't be there)14:18
*** openstack changes topic to "some breaking change in saharaclient Python API to align with other clients (find vs findall, see first comment in https://review.openstack.org/#/c/150347/) (pas-ha, won't be there) (Meeting topic: sahara)"14:18
*** aleksandr_null has quit IRC14:19
SergeyLukjanovcurrently I don't see any issues with it14:20
SergeyLukjanovit just adds the find_unique14:20
elmikoas we're talking about the client, it might be nice to watch this as well https://review.openstack.org/#/c/145579/14:20
elmikocould be something we can implement in the future14:20
SergeyLukjanovelmiko, ++14:21
elmikogranted, it's an api change, but the client could use this for sorting14:21
SergeyLukjanovalazarev, do you have any issues with https://review.openstack.org/#/c/150347/ ?14:21
*** aleksandr_null has joined #openstack-meeting-314:21
alazarevSergeyLukjanov, not issues14:21
*** peristeri has joined #openstack-meeting-314:22
alazarevA question: do we want to make our client in line woth other openstack clients? If yes this will change client API14:22
alazarev*with14:23
elmikoi think we should be in line with the other clients14:23
mattfalazarev, yes, apiclient is gone from oslo too14:23
crobertsrh+1 for being in-line14:23
mattfsome potential pruning...14:23
alazarev+1 for being inline14:23
SergeyLukjanov+1 for being inline14:23
SergeyLukjanovthis change doesn't break anything, it just adds one more func14:24
*** lblanchard has joined #openstack-meeting-314:24
SergeyLukjanovso, currently there is no compatibility issues14:24
mattfhttps://github.com/openstack/oslo-incubator/blob/master/openstack/common/apiclient/base.py#L2314:24
alazarevthis clould break old versions of client users14:24
mattfalazarev, how old?14:25
*** banix has quit IRC14:25
alazareve.g. juno sahara will not work with new client14:25
elmikomattf: makes me wonder, do we need to have some start porting stuff to the common openstack client?14:25
mattfknow that for sure, or speculating?14:25
alazarevif we change method names - it will definitly be broken14:26
alazarevI'm not about proposed change14:27
SergeyLukjanovoh14:27
SergeyLukjanovok :)14:27
mattfalazarev, sounds like direction is to get on the new client lib, but we'll have to be careful or plan breaks at appropriate times14:27
alazarevI'm about message in the patch14:27
*** banix has joined #openstack-meeting-314:27
alazarevwe now use "find" as "findall"14:28
mattfelmiko, dunno14:28
alazarevdo we want to rename?14:28
mattfthat's independent of the lib we use tho14:28
mattfwe could break that now and change lib later14:28
*** Brian_Shang has quit IRC14:28
* mattf resets14:28
SergeyLukjanovalazarev, we could start using findall by adding alias while keeping find available too14:29
mattfalazarev, gotcha. i'm all set.14:29
*** Brian_Shang has joined #openstack-meeting-314:29
alazarevSergeyLukjanov, but other clients use "find" as "find one"14:29
*** Yi_ has joined #openstack-meeting-314:29
mattfthere's a semantic change going in already that allows for finding just one element, get an exception if not found14:29
mattfalazarev, is find/findall the only break that'd happen to get us inline?14:30
*** huichun has quit IRC14:30
SergeyLukjanovIMO it should be investigated and a spec should be proposed for it14:30
mattf+214:30
elmiko+114:30
alazarevmattf, I don't know, this is what Pavlo pointed14:31
tmckay+114:31
SergeyLukjanovto make us able to discuss it and probably share with TC and some WGs14:31
mattf+1 don't design now14:31
alazarevwhat is the usual practice? should old versions work with any version of client?14:31
tmckayAnd I'm okay with multiple names mapping to the same functionality for compat, maybe with a deprecate message14:31
mattfalazarev, may be appropriate to go to findall for v214:32
SergeyLukjanovmattf, ++14:32
alazarevtmckay, it is not possible since current name is used for other purpose14:32
tmckayah, I see.  nevermind :)14:32
*** huichun has joined #openstack-meeting-314:32
* tmckay is watching child drive while attending meeting14:33
alazarevv2 could be a solution14:33
alazarevdo we have plans for v2?14:33
*** JeanBriceCombebi has quit IRC14:33
mattfhehe14:33
*** mattfarina has joined #openstack-meeting-314:33
*** Yi has quit IRC14:33
mattf-2 on changing semantics w/o bumping version14:33
elmikoi'm still interesting in v2....14:33
elmikoand i know pecan much better now ;)14:34
SergeyLukjanovalazarev, it will be the most huge spec ever for sahara14:34
alazarevelmiko, everyone is interested :)14:34
tmckaymaybe by now we should call it v3 <wink>14:34
elmikolol14:34
*** JeanBriceCombebi has joined #openstack-meeting-314:35
crobertsrhsahara "millenium edition"14:35
mattfnext topic?14:35
alazarevcrobertsrh, millenium was in 2000 :)14:35
SergeyLukjanov#topic Open discussion14:35
SergeyLukjanov :)14:35
*** openstack changes topic to "Open discussion (Meeting topic: sahara)"14:35
crobertsrhNo...I mean the NEXT millenium :)14:35
mattflet's drop "ex Savanna"14:36
elmikoi'd like to talk about DIB briefly14:36
egaffordcrobertsrh: Then we'd have to quickly replace it with Sahara XP, and no one wants that.14:36
tmckay+114:36
SergeyLukjanovmattf, already done for meeting page14:36
elmikomattf: +114:36
crobertsrhheh14:36
mattfopen season on "ex Savanna", if you see it, remove it14:36
mattfand no, not from old docs14:36
elmikois DIB supposed to work with openSuse? because we have clauses for it in the script but it doesn't work on the latest version of openSuse....14:36
SergeyLukjanovfixed for https://launchpad.net/sahara14:36
mattffyi, i added sahara to openhub yesterday - https://www.openhub.net/p/openstack-sahara14:37
elmikomattf: nice!14:37
mattfopenhub, ex ohloh14:38
elmikois anyone using openSuse to run diskimage-create?14:38
mattfelmiko, i'm not14:38
elmikois there a reason for keeping compatibility?14:38
mattftry git blame to find the author...14:39
*** plaurin_ has left #openstack-meeting-314:39
elmikothought i'd bring it up here first, just to see if anyone knew about it14:39
elmikobut yea14:39
mattfThomas Bechtold14:39
crobertsrhThere was a guy asking about OpenSuse about 6 months ago14:39
alazarevI want to talk about cm_api one more time sinse I don't see ways to support indirect access for it; we need really few things from it, don't we want to create our own lib?14:39
mattfcommit 7dfcbe3a62813001376ecd71864e1bc947c7a7e614:39
mattfAuthor: Thomas Bechtold <tbechtold@suse.com>14:39
mattfDate:   Tue Nov 18 07:06:38 2014 +010014:39
mattf    Add openSUSE support for diskimage-create.sh14:39
mattfkinda on purpose14:40
toskyelmiko: afaik SuSE ships with their OpenStack version, not sure about Sahara14:40
SergeyLukjanovalazarev, I'm ok with it14:40
toskydo you mean another lib which replaces cm_api?14:40
tmckayalazarev, more sahara-extra?14:40
elmikomaybe i should send him an email asking him to fix compat for suse lol14:40
elmikoor just file bugs i suppose14:40
SergeyLukjanovnope, just a very simple client embeded to plugin14:40
toskya different wrapper for the proprietary CDH console?14:41
mattfelmiko, very reasonable. contributed and should be maintained.14:41
SergeyLukjanovlike it was done in intel plugin14:41
tmckaySergeyLukjanov, +114:41
alazarevtosky, just class in sahara, like we did with HDP14:41
mattfSergeyLukjanov, alazarev, cm_api has many functions, we use a couple, and the couple we use are primarily to do the CDH Console REST calls? so the proposal is to drop cm_api and have our own impl of the REST calls?14:42
alazarevmattf, exactly14:42
crobertsrhIt is tempting to "make our own" rather than try to wedge in the cm_api.14:42
mattf+1 w/ regrets14:42
SergeyLukjanovmattf, yeah, mostly because cm_api isn't packaged on any platforms and it's difficult to use it for some features like indirect access14:42
*** sigmavirus24 is now known as sigmavirus24_awa14:43
alazarevCDH guys, what do you think?14:43
egaffordSergeyLukjanov: +1 on that as well; unless Cloudera starts packaging, it's an overall maintenance win. (Also +1 to mattf's regrets, but so it goes.)14:43
kchenI think maybe we can define a subset of current cm_api, and only use those APIs.14:43
tmckayif it's packaged in the future, of course, we can always use the "real thing"14:44
tmckayand back out the home-brew14:44
egaffordtmckay: Indeed; that would be the ideal.14:44
weitingActually it's about maintenance. I mean if we do it we need to do the maintain job if there is any update from Cloudera.14:45
weitingFor long term plan, it should be a good idea to have it without cm_api.14:45
alazarevweiting, is REST changed often?14:45
mattfweiting, any info on likelihood of cloudera making incompatible changes to cm_api that we'd have to mirror?14:45
mattfalazarev, good use of fewer words14:46
kchenif we only maintain a subset of cm_api, maybe we can decrease the job of maintenance?14:46
tmckayand does CDH use any kind of api versioning?  Maybe that would help, too14:46
alazarevwe need really few REST calls from it14:46
weitingCM usually support the older version cm_api14:46
*** Brian_Shang has quit IRC14:47
kchenYes. currently released cm_api is v814:47
SergeyLukjanovoh, and cm_api doesn't support py33 => no way to global requirements14:47
*** Brian_Shang has joined #openstack-meeting-314:47
weitingAnd v8 can support v7 and v614:47
SergeyLukjanovalazarev, ++14:47
mattfweiting, what's the release cadence?14:47
weitingWe don't know. There is no cadence currently.14:48
tmckaysounds to me like maintenance would be reasonable, with api versions and a subset of REST calls14:49
weitingIt depends on CM and CDH update.14:49
mattfok14:49
kchenmaybe we can stay on v8, until changes are required.14:49
*** pkarikh has quit IRC14:49
mattfwe can always decide later that this was a bad decision and back it out14:49
tmckay+114:49
mattfopenstack bot isn't holding any stone tablets14:50
*** Yi_ has quit IRC14:50
*** pkarikh has joined #openstack-meeting-314:50
elmikoyea, given the talk seems like we need to make our own version instead of using cm_api14:50
*** Yi has joined #openstack-meeting-314:50
elmikothe py33 support is a total deal breaker for gobal req., as SergeyLukjanov said14:50
alazarevdo we have volunteers to make our small version of cm_api?14:51
egaffordweiting: Our other options are to independently maintain cm_api itself in packages on n OSes, beg Cloudera to package it on n OSes themselves, and not support Cloudera, right? Failing Cloudera packaging, the subset seems like the smallest to me.14:51
weitingOk, let us propose a bp for a subnet of cm_api.14:53
*** isviridov is now known as isviridov_break14:53
*** tidwellr has joined #openstack-meeting-314:53
*** JeanBriceCombebi has quit IRC14:54
SergeyLukjanovack14:54
SergeyLukjanovanything else?14:54
SergeyLukjanov5 mins left14:54
crobertsrhnothing from me14:54
alazarevnothing from me14:54
kchenno from me.14:55
tmckayintel guys, I will try to address Oozie mail thread questions today or tomorrow.  Trying to validate cdh5 for spark14:55
mattfnothing here14:55
*** JeanBriceCombebi has joined #openstack-meeting-314:55
*** mrsmith_ has joined #openstack-meeting-314:55
kchenhope we can finish the subset of cm_api patch by kilo314:55
*** jpomero has joined #openstack-meeting-314:56
SergeyLukjanovkchen, it'll be great, but don't forget that spec is needed earlier14:56
kchentmckay: thanks14:56
egaffordkchen: +1. I'd like to volunteer to help with impl to get that done, once the spec is up; full Cloudera support by Kilo would be wonderful.14:56
*** johnbelamaric has joined #openstack-meeting-314:57
SergeyLukjanovFPF is March 514:57
kchenSergeyLukjanov: ok14:57
SergeyLukjanov(feature proposal freeze)14:57
kchenegafford: thanks14:58
kchenI will finish the specs asap14:58
SergeyLukjanovthanks folks14:58
SergeyLukjanov#endmeeting14:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:58
openstackMeeting ended Thu Jan 29 14:58:51 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-01-29-14.04.html14:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-01-29-14.04.txt14:58
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-01-29-14.04.log.html14:58
weitingOnce the subnet lib has been done, can we enable cdh in sahara.conf by default?14:59
huichuntmckay: ok14:59
*** mattf has left #openstack-meeting-314:59
*** mlavalle has joined #openstack-meeting-314:59
SergeyLukjanovweiting, yup14:59
*** ihrachyshka has joined #openstack-meeting-315:00
*** pc_m has joined #openstack-meeting-315:00
pc_mhi15:00
mlavallehi15:00
*** tmckay has quit IRC15:00
*** weiting has quit IRC15:01
*** kchen has quit IRC15:01
*** mrsmith__ has joined #openstack-meeting-315:01
*** mrunge has joined #openstack-meeting-315:01
*** weiting has joined #openstack-meeting-315:01
*** mrsmith_ has quit IRC15:02
*** Swami has joined #openstack-meeting-315:02
ihrachyshkao/15:02
Swamihi15:02
johnbelamarichello15:02
*** markvoelker_ has quit IRC15:03
tidwellrhi15:03
*** huichun has quit IRC15:03
*** Rajeev has joined #openstack-meeting-315:03
*** weiting has quit IRC15:04
*** Brian_Shang has quit IRC15:04
*** elmiko has left #openstack-meeting-315:05
*** seizadi has joined #openstack-meeting-315:05
*** Brian_Shang has joined #openstack-meeting-315:05
pc_mL3 meeting?15:05
mlavallepc_m: this is the right channel for the L3 meeting, right?15:05
pc_myes.15:05
johnbelamaricyes, this is it15:06
Swamipc_m: waiting for the chair15:06
pc_mDon't see Carl online15:06
mlavallemaking sure I am not waiting at the wrong place.... I've done it before :-)15:06
*** tosky has left #openstack-meeting-315:07
RajeevNo worries. There are quite a few of us to be at the wrong place :)15:07
pavel_bondarhi15:09
*** Piet has joined #openstack-meeting-315:09
johnbelamarichi pavel_bondar - we are waiting for carl15:09
pavel_bondarhi John, yeah, got it15:09
pc_mShould we start w/o him?15:10
ihrachyshkapc_m, wanna lead? :)15:10
pc_mI can try...15:10
*** BrianShang has joined #openstack-meeting-315:10
*** Brian_Shang has quit IRC15:10
pc_m#startmeeting neutron_l315:10
openstackMeeting started Thu Jan 29 15:10:38 2015 UTC and is due to finish in 60 minutes.  The chair is pc_m. Information about MeetBot at http://wiki.debian.org/MeetBot.15:10
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:10
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:10
openstackThe meeting name has been set to 'neutron_l3'15:10
pc_m#topic Announcements15:10
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:10
pc_mK2 is on Feb 5th.15:11
pc_mAnyone have announcements?15:11
pc_mok... onto bugs...15:12
pc_m#topic Bugs15:12
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:12
pc_mHere the list:  #link https://bugs.launchpad.net/neutron/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.importance%3Alist=UNKNOWN&field.importance%3Alist=UNDECIDED&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&assignee_option=any&field.assignee=&field.15:12
pc_mbug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=l3-ipam-dhcp+&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprint15:12
pc_ms=on15:12
* pc_m wow, that didn't paste well.15:12
*** ongk has left #openstack-meeting-315:13
ihrachyshkause link shortener Luke15:13
pc_m#link http://goo.gl/7O8AKS15:13
*** sigmavirus24_awa is now known as sigmavirus2415:13
pc_mAny updates on these?15:14
*** BrianShang has quit IRC15:14
*** Brian_Shang has joined #openstack-meeting-315:15
* pc_m patiently hoping someone will speak up :)15:15
* ihrachyshka notes that some of those just need core reviewers to merge15:15
pc_mihrachyshka: OK.... #action Cores to review high priority bugs so they can merge15:16
pc_m:)15:16
ihrachyshka:)15:16
pc_mCarl also has a list of L3 IPAM DHCP bugs... #link https://bugs.launchpad.net/neutron/+bugs?field.tag=l3-ipam-dhcp15:17
pc_mAny comments/concerns/questions on these?15:17
*** egafford has left #openstack-meeting-315:18
pc_mOK. Will move on...15:18
pc_m#topic L3 Agent Restructuring15:18
*** openstack changes topic to "L3 Agent Restructuring (Meeting topic: neutron_l3)"15:18
pc_mAnyone care to give an update?15:18
pc_mI don't see amuller online15:19
pc_m#topic BGP Dynamic Routing15:20
*** openstack changes topic to "BGP Dynamic Routing (Meeting topic: neutron_l3)"15:20
pc_mdevvesa: ping15:20
pc_mIs there anything on this?15:21
*** obondarev_ has joined #openstack-meeting-315:21
pc_mHmm...15:21
*** fischerw has joined #openstack-meeting-315:21
pc_mRather than going through the agenda... Let's try something different.15:22
pc_mAnyone have an item that they want to discuss?15:22
Swamipc_m: we are seeing more failures on the dvr tests lately.15:22
pc_mor want to provide an update on?15:22
pc_m#topic DVR15:23
SwamiYesterday we saw most of the test failing with "No host found".15:23
*** openstack changes topic to "DVR (Meeting topic: neutron_l3)"15:23
SwamiDo you know is there a way to figure out why do we get "No host found" errors only with DVR tests and not with the neutron full tests.15:23
*** obondarev has quit IRC15:24
SwamiError message seen: Details: {u'message': u'No valid host was found. There are not enough hosts available.', u'created': u'2015-01-28T23:11:29Z', u'code': 500}15:24
*** mattfarina has quit IRC15:25
pc_mSwami: Can you post a link to one of the failure test runs, so folks can look at it?15:25
SwamiThe DVR team is currently working on sorting out the differences between the neutron-full test and neutron-dvr test.15:25
Swamisure.15:26
Swami#link http://logs.openstack.org/68/143568/10/check/check-tempest-dsvm-neutron-dvr/e0f5bd8/logs/testr_results.html.gz15:27
pc_mSwami: thanks15:27
SwamiI was consistently seeing these errors last night in most of the builds.15:28
pc_m:(15:28
pc_mSo not creating the server for the test?15:28
SwamiAny help from the Infra team to sort of such issues will be great.15:28
*** thangp has joined #openstack-meeting-315:28
pc_manteaya: ping15:29
Swamipc_m: Yes it seems that what it says.15:29
SwamiThe dvr team will be working on making the dvr test voting. That would be our high priority as of now. Any help from the community and infra will be appreciated.15:30
*** sergef has quit IRC15:30
SwamiThat would be our high priority for this week.15:30
pc_mSwami: Thanks for the info.15:30
SwamiThat's all I had from the DVR side.15:30
pc_mSwami: Maybe we can reach out to Maru to see if he knows of people that can help from infra.15:31
ihrachyshkahave you tried #openstack-infra?15:31
Swamipc_m: ok thanks will do15:31
pc_mihrachyshka: +115:31
SwamiI will try that IRC channel as well.15:31
pc_mIt'll be a good start.15:32
*** yapeng has joined #openstack-meeting-315:32
pc_mAny other topic people want to discuss or have questions on?15:32
*** vgridnev_ has quit IRC15:33
ihrachyshkaI have smth. I want to kindly ask people to check my test_l3_agent refactoring series at: https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:split_ra_unit_tests,n,z It's a start to later add more coverage for ra.py.15:33
pc_m#topic L3 Refactoring15:33
*** openstack changes topic to "L3 Refactoring (Meeting topic: neutron_l3)"15:33
ihrachyshkait's currently in conflict with trunk reality :) but I'd like to hear if direction is ok before proceeding15:33
*** crobertsrh has left #openstack-meeting-315:35
pc_mihrachyshka: Thanks. Please help Ihar out with reviewing this.15:35
ihrachyshkafor now a brief review on direction is enough15:35
ihrachyshkathanks :)15:35
pc_mAnything more on L3 refactoring?15:36
pc_mAnything on IPAM?15:36
ihrachyshkapavel_bondar, ?15:36
*** kozhukalov has joined #openstack-meeting-315:37
*** mattfarina has joined #openstack-meeting-315:37
*** yapeng has quit IRC15:37
pavel_bondarYeah, it would be nice if somebody took a look on current version of #link https://review.openstack.org/#/c/147479/15:37
* pc_m Thanks for helping with calling out people ihrachyshka!15:37
pc_m#topic IPAM15:37
*** openstack changes topic to "IPAM (Meeting topic: neutron_l3)"15:37
pavel_bondarit is IPAM Driver Loader15:38
johnbelamaricok, i will take a look today15:38
pc_mjohnbelamaric: Thanks for helping!15:38
tidwellrI'll take a look as well15:38
pc_mtidwellr: ditto!15:39
tidwellrhttps://review.openstack.org/#/c/148698/15:39
ihrachyshkathe last time I checked the interface definition was not mature. have you heard from carl on whether he'll update it in near future?15:39
johnbelamarichave we seen a reference driver from salv-orlando ? I know he has done a lot on it so far15:39
pc_msalv-orlando: ping15:39
pavel_bondarAlso I got WIP code from Salvatore(Reference IPAM Driver)15:40
pavel_bondar#link https://review.openstack.org/#/c/150485/ It is in WIP status, investigating deeper with it15:40
tidwellrI saw this as well15:40
*** seizadi has quit IRC15:40
johnbelamaricok, good15:41
pavel_bondarI'll plan to provide next week some WIP version of re-factored db_base_plugin based on it15:42
pc_mpavel_bondar: great15:42
pc_m#action pavel_bondar to provide WIP version of re-factored db_base_plugin next week15:43
*** isviridov_break is now known as isviridov15:43
pc_mpavel_bondar: Anything else on IPAM you care to bring up?15:43
tidwellrbasic subnetpool CRUD is taking shape, still WIP but some more eyes on it would be great https://review.openstack.org/#/c/148698/15:43
pavel_bondarthat's it for now15:44
pc_mthanks for the update.15:44
*** jtomasek has quit IRC15:44
*** Swami has quit IRC15:44
pc_mAnything else from the agenda that people want to discuss, before we go to open discussion?15:44
*** markvoelker has joined #openstack-meeting-315:45
pc_m#topic Open Discussion15:45
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:45
*** amuller has joined #openstack-meeting-315:45
*** elmiko has joined #openstack-meeting-315:45
*** erikmwilson has joined #openstack-meeting-315:45
pc_mamuller: hi15:46
amullerpc_m: Good morning15:46
pc_mWe're almost done. Did you have anything you wanted to discuss for L3?15:46
amullerNope!15:46
*** banix has quit IRC15:46
* pc_m Carl's not around today, so I'm feebly trying to fill in15:46
pc_mAnyone have any other items to discuss? Otherwise we'll give back a few mins :)15:47
*** devvesa has quit IRC15:48
pc_mOK. thanks for joining in everyone. If you have any other items, please use the IRC or ML and let Carl know.15:48
pc_m#endmeeting15:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:49
openstackMeeting ended Thu Jan 29 15:49:08 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-01-29-15.10.html15:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-01-29-15.10.txt15:49
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-01-29-15.10.log.html15:49
pc_mbye all!15:49
mlavallepc_m: thanks15:49
pc_mmlavalle: np15:49
*** Networkn3rd has joined #openstack-meeting-315:49
*** pc_m has left #openstack-meeting-315:49
*** mlavalle has left #openstack-meeting-315:49
*** banix has joined #openstack-meeting-315:50
*** mrsmith__ has quit IRC15:50
*** tidwellr has left #openstack-meeting-315:52
*** johnbelamaric has quit IRC15:52
*** marun has joined #openstack-meeting-315:55
*** cdent has joined #openstack-meeting-315:56
*** Brian_Shang has quit IRC15:56
*** etoews has joined #openstack-meeting-315:56
*** salv-orlando has quit IRC15:57
*** salv-orlando has joined #openstack-meeting-315:57
*** yamahata has joined #openstack-meeting-315:57
*** obondarev_ has quit IRC15:58
*** kaufer has joined #openstack-meeting-315:58
*** obondarev has joined #openstack-meeting-315:59
*** iovadia has quit IRC15:59
etoews#startmeeting api wg16:00
openstackMeeting started Thu Jan 29 16:00:13 2015 UTC and is due to finish in 60 minutes.  The chair is etoews. 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
etoewshi all!16:00
elmikohello/16:00
salv-orlandoaloha16:00
cdenthola16:00
kauferhello!16:00
etoews1 sec16:01
*** pkoniszewski has joined #openstack-meeting-316:02
etoews#topic agenda16:02
*** openstack changes topic to "agenda (Meeting topic: api wg)"16:02
etoews#link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda16:02
edleafeo/16:02
etoewsso we have a few topics i'd like to focus on this meeting rather than our usual agenda16:03
*** mattgriffin has joined #openstack-meeting-316:03
etoewslet's tackle the specs question first16:03
etoews#topic openstack-specs16:03
*** openstack changes topic to "openstack-specs (Meeting topic: api wg)"16:03
*** dtroyer has joined #openstack-meeting-316:03
etoewsi attended the cross-project meeting on tues. sigmavirus24 was there too.16:03
etoewsthe api wg is basically looking for more visibility for reviewing our guidelines16:04
etoewsttx had an interesting suggestion for us16:04
*** ryansb has joined #openstack-meeting-316:04
*** VW_ has quit IRC16:05
etoewsto quote ttx from an email to openstack-dev "keep the api-wg repository for the16:05
etoewsvarious drafting stages, and move to openstack-specs when it's ready to16:05
etoewsbe "recommended" and request wider community comments. Think Draft and16:05
etoewsRFC stages in the IETF process :)"16:05
*** carl_baldwin has joined #openstack-meeting-316:05
etoewsthere's been some further conversation on the ml about this16:06
etoewshas everybody had a chance to read the ml thread?16:06
etoewstake a minute to do so and let me know what you think16:06
* elmiko rushes off to email16:06
*** VW_ has joined #openstack-meeting-316:07
sigmavirus24#link http://lists.openstack.org/pipermail/openstack-dev/2015-January/055443.html16:07
sigmavirus24elmiko: ^16:07
kauferI've read the ML replies, I share the same concerns as Sean about having multiple repos16:07
edleafesame here16:07
*** ihrachyshka has left #openstack-meeting-316:07
sigmavirus24Yeah, I noticed just this week that a bunch of cross-project drivers started reviewing and -1'ing some of our proposals16:08
elmikosigmavirus24: thanks!16:08
*** Yi has quit IRC16:08
cdentI think the visibility of new recommendations is a bigger deal than the repo aspect16:08
sigmavirus24Humorous to me that everyone agreed to a separate repository though in the beginning and now wants it unified in one place16:08
elmikoi'm +1 for single repo, but i like the idea of separating the drafts from the guidelines16:08
cdentIt's not clear that gerrit is really working as a place to discuss...16:08
cdent(discuss the drafts I mean)16:08
etoewscdent: how else would such discussion happen?16:09
elmikoi think we should create a template like is used for the project spec repos, and then have the discussions through the patches to the repo. very similiar to project specs now.16:09
ryansbalso the merged/unmerged distinction is a great approved/draft distinction16:09
sigmavirus24So I think there are also some serious misconceptions around the documents the API-WG is producing as well that seem to continue to pop up16:10
edleafecdent: that's pretty much how all other specs are discussed16:10
elmikoryansb: +116:10
*** amuller has left #openstack-meeting-316:10
sigmavirus24== ryansb16:10
etoewsfor reference16:10
etoews#link https://github.com/openstack/openstack-specs16:10
etoews#link https://github.com/openstack/openstack-specs/blob/master/template.rst16:10
cdentfor sake of visibility I think email would be better. But basically I'm -1 on any non-code review happening in gerrit, so I'm probably just a grape in the path of progress.16:10
*** zz_jgrimm is now known as jgrimm16:10
*** devvesa has joined #openstack-meeting-316:10
elmikoetoews: i think we will need to customize the template, but details...16:10
etoewsso i'm +1 for single repo too16:11
elmikocdent: ack, but doesn't that go against the grain of how we review specs now? (for non-api-wg projects)16:11
etoewswho is +1 for single repo?16:12
elmiko+116:12
kaufer+116:12
sigmavirus24+116:13
sigmavirus24etoews: #vote maybe?16:13
dtroyer+116:13
sigmavirus24(so it's in the meeting notes)16:13
edleafe+116:13
etoewssigmavirus24: i was thinking just use #agreed16:13
sigmavirus24ah, didn't realize that could be used outside a vote :)16:14
etoewscdent: ryansb: care to vote?16:14
cdent+116:14
*** mattfarina has quit IRC16:14
*** pkoniszewski has quit IRC16:14
cdentelmiko: I think underlying this is that I don't think the api-wg guidelines are the same as specs...16:15
*** obondarev has quit IRC16:15
etoewsi think we've got consensus on that.16:15
etoews#agreed the api wg should only use a single repo16:15
elmikocdent: ok, that makes a good deal of sense16:15
etoewsnow the question becomes which repo?16:15
*** obondarev has joined #openstack-meeting-316:15
cdentelmiko: we keep using both terms guidelines and spec but that's not really the same thing.16:16
sigmavirus24etoews: what options do we have outside openstack-specs?16:16
etoewsthe current api-wg repo16:16
elmikocdent: true, although i think the metaphor of specs can be applied to api-wg stuff, but you're correct it's not the same as a code spec.16:16
etoewsalso see #5 of http://specs.openstack.org/openstack/api-wg/process.html16:16
*** evgenyf has quit IRC16:17
sigmavirus24It's not the same definition of spec as is uses by projects but it is in a sense a spec. But I agree we should really avoid confusing language as much as possible16:17
etoewsif we were to continue on in the api-wg repo, at some point in the future we supposed release an official version.16:17
etoewsi'm not exactly sure what form that official version would take at this point.16:17
ryansbwhy not just a generated site from all the content in api-wg?16:18
*** jkraj has joined #openstack-meeting-316:18
sigmavirus24Regardless, having the discussions on the ML has been kind of worthless because people ignore the [api] tag who aren't already interested in the wg cdent16:18
elmikoetoews: maybe something like how some projects publish their apis to the spec repos? (eg keystone)16:18
etoewssigmavirus24: +1 i avoid the word spec simply because it's already taken in openstack land.16:18
ryansblike writing-apis.openstack.org16:18
etoewselmiko: link?16:18
elmikoetoews: https://github.com/openstack/keystone-specs/tree/master/api16:19
sigmavirus24etoews: http://specs.openstack.org/openstack/glance-specs/16:19
*** seizadi has joined #openstack-meeting-316:19
elmikoso, if we're talking about guidelines as our official output, maybe instead of specs we should talk about guideline proposals?16:19
etoewsdon't we already effectively have that? http://specs.openstack.org/openstack/api-wg/16:19
etoewslet's bring the discussion back to visibility16:21
elmikoetoews: hmm, maybe. i guess i was thinking more about how we contain the proposals and released guidelines in a single repo. perhaps i'm just missing a few details.16:21
etoewsin the api-wg repo it seems we have to work harder to get review by affected projects.16:21
etoewswould that be different in the openstack-specs repo?16:22
cdentThis is the first meeting I've attended, basically because it's bad for my schedule (I'm in a video conference right now too), but the impression I get from the reviews is that much of the interesting discussion happens during this meeting. That is very bad for visibility and diversity of input.16:22
etoewssimply by virture that it is a blessed repo16:22
etoewscdent: i know what you mean.16:22
sigmavirus24So I have email notifications for the api-wg repository set-up so I always review the guidelines as they're proposed etc.16:23
elmikosame16:23
etoewssame but i speculate the CPLs don't16:23
sigmavirus24I never set up notifications for anything with APIImpact though which was the other part of this group's mission16:23
*** Sukhdev has joined #openstack-meeting-316:23
etoewsAPIImpact seems to be well adopted but there's too much for us to review!16:24
sigmavirus24etoews: right, and the thing is, I don't need notifications for everything in openstack-specs, so if we were to work there, would a separate branch be outside the realm of possibility?16:24
elmikoetoews: probably true, but isn't that what the liasons are supposed to be for =)16:24
etoewsand not many merged guidelines to reveiw against16:24
sigmavirus24I also find it hard to believe that there would be more constructive review of our guidelines on openstack-specs rather than what we're seeing now which is a bunch of -1s because the proposed guideline is too radically different from the current state of affairs16:25
sigmavirus24Which stems from people thinking that they'll be expected to immediately implement these changes because they never followed the ML threads about proposing how to upgrade16:25
etoewssigmavirus24: i don't think number of email notifications should be a driver for this decision16:25
sigmavirus24etoews: but there is a difference between overall specs (logging, etc.) and the guidelines we're proposing16:26
etoewssigmavirus24: true16:26
sigmavirus24having them on the same branch will probably overload more than just us16:26
elmikoi think it's a good point about watching a repo and wanting to filter only some of the content there16:26
*** JeanBriceCombebi has quit IRC16:26
etoewswe would need a subsection or branch or something if we were in openstack-specs16:26
sigmavirus24We don't currently have a lot of proposals or other information generated from ours, but we could quickly add a lot more volume up on openstack-specs which will undoubtedly annoy people16:26
elmikoi'd like to think it would make it easier for participation if it's contained in a separate api-wg repo16:27
sigmavirus24etoews: yeah, that's more my point16:27
etoewsthere must be other text we could filter on to only see specs relevant to us16:27
*** armax has joined #openstack-meeting-316:27
cdentI think that its own repo is more likely to enable efficient discussion, but at the cost of visibility.16:27
*** mrmartin has quit IRC16:28
cdentI think we can probably figure out how to deal with visibility in some other way.16:28
etoewscdent: that's the tradeoff i see16:28
*** mrmartin has joined #openstack-meeting-316:28
*** fischerw_ has joined #openstack-meeting-316:28
*** armax has quit IRC16:28
*** fischerw has quit IRC16:28
*** fischerw_ has quit IRC16:28
cdent(such as making explicit invitations to certain reviews on the mailing list, more often)16:28
*** fischerw has joined #openstack-meeting-316:29
etoewsbasically do a better job of reaching out and pulling in relevant reviewers.16:29
sigmavirus24cdent: I think you overestimate the usefulness of asking for review on a high-traffic list like -dev because even then I've seen little participation from the people whose feedback we seek the most16:29
cdentyes16:29
elmikowould it be possible to have the api-wg as a submodule of openstack-specs?16:29
sigmavirus24It seems most efficient to find people on irc and ping them directly16:30
*** lazy_prince is now known as killer_prince16:30
sigmavirus24elmiko: I'm not sure it would track well and I don't think it would contribute to visibility. We'd also need a bot to update the submodule each time a guideline is merged16:30
etoewselmiko: i dunno16:30
cdentsigmavirus24: I agree that it is likely a fruitless task, but if we want to make the appearance of inclusivity then the mailing list is the only one that transcends membership in cliques and existing in certain time zones16:30
elmikosigmavirus24: ahh, yea. that seems like a lose16:30
sigmavirus24And that bot would quickly become more annoying than the OpenStack proposal bot16:30
etoewsi do know that i'm not crazy about submodules16:31
sigmavirus24cdent: the problem is, I don't want the appearance, I want the actuality16:31
cdentgood luck getting that in openstack sigmavirus24 :)16:31
edleafe:q16:31
edleafeugh16:31
*** Rajeev has quit IRC16:31
sigmavirus24edleafe: we are not vim. we are emacs ;)16:31
elmikouh-oh...16:31
edleafesigmavirus24: wash your mouth out!16:31
edleafe:)16:31
* sigmavirus24 uses both in reality =P16:32
sigmavirus24Okay we're half-way through, should we move on to other topics?16:32
*** gholler has joined #openstack-meeting-316:32
*** mrmartin has quit IRC16:32
etoewsmaybe...16:33
dtroyerlast thought: keep in mind that this group is still relatively young, it takes some time to build the awareness of what we're doing16:33
cdentdtroyer++16:33
cdentthere's definitely been an upswing in participation from "others" in the very recent past16:33
elmikodtroyer: good point16:33
etoewsdtroyer: good point. i'm highly conscious of that in many respects. what we're doing right now is making early design decisions.16:34
etoewswe'll likely be stuck with the consequences of these decisions for some time.16:34
etoewswhich makes me cautious. maybe overly cautious...16:34
etoewsthere needs to be action here.16:35
etoewscontinue the discussion on the ml?16:35
dtroyerwfm16:35
*** seizadi has quit IRC16:35
ryansb+116:35
cdent+116:35
elmiko+116:36
*** devvesa has quit IRC16:36
kaufer+116:36
etoews#action etoews to kickoff a discussion to continue the question of which repo on the ml16:36
etoews#topic swift16:36
*** openstack changes topic to "swift (Meeting topic: api wg)"16:36
etoews#link https://review.openstack.org/#/c/141229/16:36
miguelgrinbergjust in time, it looks16:36
miguelgrinberg:)16:37
etoewsso notmyname had some valid concerns in that review16:37
etoewsthoughts?16:38
miguelgrinbergI have been thinking about the last review form notmyname, it has valid points, but swift has so many differences that I don't see how to combine their needs with the rest16:38
etoewsthat's my feeling too16:38
etoews"...with the REST"16:38
miguelgrinbergI can think of ways to change swift to accomodate what we are proposing, but they are not going to like it16:38
etoewsnor would client devs16:38
*** armax has joined #openstack-meeting-316:38
miguelgrinbergit seems this metadata in the headers idea came from aws16:39
miguelgrinbergthey also do that16:39
ryansbyeah, it did16:39
elmikoi tend to agree with miguelgrinberg's point about the "metadata" object. on the second point, i think it would be helpful to have an example, i'm a little confused.16:39
miguelgrinbergI personally don't like it, but notmyname feels pretty strongly about not changing that16:39
ryansbbut it actually is a nice solution to the object metadata problems16:39
cdentI'm surprised that "we" feel it necessary to formalize metadata handling.16:40
ryansbI agree w/ notmyname about not having metadata attrs require another HTTP call16:40
cdentOr rather, it's surprising that's high on the list of priorities.16:40
cdentalso given that swift follows no other rules, why would we require them to follow these?16:41
elmikois John == notmyname?16:41
miguelgrinbergcdent: not sure it is high, I think it was me that found high discrepancies between APIs, so I proposed we look at it16:41
*** obondarev has quit IRC16:41
dtroyerelmiko: yes16:41
elmikodtroyer: ty16:41
etoewscdent: i believe it came up when a service (cinder?) decided they needed metadata16:41
* salv-orlando agrees with cdent's point on swift16:42
*** obondarev has joined #openstack-meeting-316:42
etoewswe were hoping to use that as an opportunity to get some consistency16:42
ryansbwho *doesn't* need metadata16:42
*** mattfarina has joined #openstack-meeting-316:43
elmikocdent: i'm curious, do you think we shouldn't be attempting to create a guideline for metadata? (or maybe it should be lower prio)16:43
sigmavirus24ryansb: the NSA doesn't16:43
elmikolol16:43
ryansbyeah, but they sure do want it.16:43
etoewscdent: i know what you mean. so one way to deal with this is put an asterix by swift saying they aren't subject to certain guidelines16:43
miguelgrinbergI think it is going to be an uphill battle to make APIs consistent, we all tend to resist change16:44
elmikoetoews: not sure we need an asterisk, isn't our position that these are guidelines not mandates?16:44
cdentelmiko: I think making guidelines for representations is a bit odd. I think it is more important to guide that representations be transported correctly.16:44
etoewstrue16:44
kauferSo, IMO, this discussion relates to the purpose of our guidelines.  Are they to force all to adopt (I don't believe so) do they exist to help mold future APIs into a consistent state?16:44
miguelgrinbergelmiko: find the discussion I had on the topic with notmyname two days ago on openstack-dev16:44
cdentTo put it another way we should guide the HTTP headers more than we should guide the bodies.16:44
edleafeI think we should try to create a best-practice on metadata, but of course, we can't force swift or anyone else to change to match it16:44
salv-orlandoedleafe: agreed16:45
cdentThings like collection handling is relevant, and things like sorting, sure, but resource design is hard to generalize.16:45
etoewskaufer: mold16:45
elmikocdent: thanks, that makes it much clearer and good food for thought.16:45
elmikomiguelgrinberg: ack, ty16:45
ryansbyeah, but this spec isn't (IMO) quite ready to be a best practice for metadata because it doesn't handle concurrent object+metadata creation16:45
cdentkaufer++ I think we should be setting aspirational guidelines16:46
sigmavirus24cdent: I'm not sure I agree but I'm also not sure that disagreement is especially relevant righ tnow16:46
sigmavirus24ryansb: if I remember correctly we couldn't even reach consensus on play object creation16:47
etoewsto me this is also tangled up with versioning. seems everytime we propose a guideline that doesn't match a particular service, someone will cry foul.16:47
miguelgrinbergryansb: I did not include it in the spec, but metadata should also be accessible as a field in the resource16:47
sigmavirus24I don't think we even came close to discussion concurrent creation of object+metadata16:47
miguelgrinbergryansb: does that satisfy your requirement of setting metdata along with the obj?16:47
edleafeetoews: of course - that's to be expected16:47
sigmavirus24etoews: that's my instinctual reaction to all of this as well16:47
dtroyeretoews: that's when we repeat the mantra and move on16:47
sigmavirus24perhaps I should just write a guideline for adoption16:47
etoewsif we could point them at a versioning strategy that everyone can agree on then we'd have an answer for that16:47
ryansbas long as I can use 1 request to create the object and its metadata I'm happy16:48
miguelgrinbergetoews: are we planning something to educate teams at the summit?16:48
dtroyergetting bogged down in this ever time is not productive16:48
edleafeetoews: but that shouldn't stop anyone from saying "this is the preferred way to do it"16:48
elmikomiguelgrinberg: that's a cool idea16:48
ryansbmiguelgrinberg: that would work, definitely include that bit16:48
sigmavirus24and try to get more people involved on the ML discussion about moving towards adoption of the guidelines through API versions16:48
*** jaypipes has joined #openstack-meeting-316:48
etoewsdtroyer: we should come to an agreement on the mantra16:48
sigmavirus24etoews + miguelgrinberg should do a co-presentation at the summit on the API-WG and it's goals16:48
etoewsmiguelgrinberg: i'll definitely be proposing to the design summit16:48
elmikoetoews: i'm on the bandwagon with regards to us keeping consistent about creating a set of useful guidelines16:48
dtroyer"these are guidelines, not prescriptions.  please, no wagering"16:49
dtroyerexcept maybe for that last part16:49
elmikodtroyer: +116:49
miguelgrinbergso I proposed a session to give my views on the openstack API design16:49
miguelgrinbergI was thinking more along the lines of describing what the API-WG does16:49
*** david-lyle_afk is now known as david-lyle16:49
miguelgrinberghappy to propose one on that with others.16:50
elmikomiguelgrinberg: +116:50
kaufermiguelgrinberg: +1 ... there seems to be confusion that the "guidelines" are rules that all must adpot instead of best practices that is used to help guide future API developent16:50
etoewsdo we need to come up with an official mantra/mission statement on the ML to make sure everybody gets it?16:50
elmikokaufer: we need to clean that messaging up16:50
elmikoetoews: i think so16:51
miguelgrinbergkaufer: yeah, and also people worry about not being in compliance with the guidelines16:51
sigmavirus24elmiko: the thing is we've been messaging that since the start (as far as I recall) and people misunderstand because they don't have time to read the docs on that16:51
elmikoetoews: and that mantra should be clear on the wiki as well16:51
etoewsyep16:51
dtroyermiguelgrinberg: that's a worry we should not remove, but set it at an appropriate level.  we want people to think about it16:51
miguelgrinbergI think the ideal would be to get people from all projects actively involved16:52
elmikosigmavirus24: fair, we will always have some that miss the message, i guess we just need to be dilligent16:52
miguelgrinbergso we need to sell ourselves to the teams16:52
elmikosigmavirus24: gotta have something catchy ;)16:52
etoews#action etoews to start api wg mission statement discussion on the ML16:53
sigmavirus24Yeah. I think we should also be tagging our messages as [all] when we want other people's feedback because some may think [api] is specific to the group and they can/should skip it16:53
miguelgrinbergI think to some, it seems we come up wtih some arbitrary rules in a vacuum and try to push them into all the projects16:53
etoewsit would have to be 2-3 sentences max16:53
elmikosigmavirus24: good idea16:53
*** SridharRamaswamy has joined #openstack-meeting-316:53
* sigmavirus24 is guilty of not using [all]16:53
dtroyeretoews: 140 chars would be awesome16:53
elmikomaybe we need some stickers for summit? help get the message out, WE ARE NOT THE API POLICE!16:53
etoewssigmavirus24: ya. i'm starting to get the sense that [api] is a bit cliquey.16:54
sigmavirus24etoews: I know I filter by tag and read the ones I care about most first and the rest later if I have time (which is rare)16:54
miguelgrinbergREST police sounds better =P16:54
elmikolol yes16:54
etoewssigmavirus24: same boat16:54
elmikosigmavirus24: same16:55
sigmavirus24miguelgrinberg: RESTful police ++16:55
etoews#topic open topics16:55
*** openstack changes topic to "open topics (Meeting topic: api wg)"16:55
sigmavirus24As long as we're not the HATEOASBI16:55
elmikolol16:55
etoewsanything else to highlight?16:55
etoewsi do think a version guideline will be one of the first things we need to come up with16:56
miguelgrinbergsigmavirus24: you say that to enrage me, I know it16:56
etoewsit will help teams know there is a path forward16:56
elmikoetoews: agreed16:56
miguelgrinbergclear steps for projects that have implementations not blessed by the API-WG would be helpful16:56
sigmavirus24so silly idea: what if we have a proposed and finalized subdirectory for stuff?16:57
etoewselmiko: btw, did you see the email from max lincoln about swagger for openstack projects?16:57
sigmavirus24As in stuff is finalized once we have the TC's approval, etc16:57
* notmyname just got online this morning and saw his name16:57
cdentmiguelgrinberg: is "blessing" the business this group is in? ;)16:57
etoewsnotmyname: 3 minutes to go!16:57
elmikoetoews: yes, i need to reply16:57
notmyname:-)16:57
etoews:)16:57
elmikosigmavirus24: i'm not a fan of that style16:57
miguelgrinbergcdent: there you go, it should be clear what we do16:58
notmynameetoews: I'd be happy to pick it up in a different channel16:58
kaufersigmavirus24: wouldn't 'proposed' be things under review in gerrit and 'finalizaed' be what is merged?16:58
sigmavirus24kaufer: elmiko "silly idea"16:58
elmikosigmavirus24: lol gotcha. we tried something similar in sahara and just refactored it out16:58
sigmavirus24A way to get people to not overreact to proposals under going review because we had already described the process as needing approval by the TC once we have some strong set of guidelines anyway16:58
elmikotoo much work to maintain16:59
etoewssigmavirus24: kaufer: under #5 of http://specs.openstack.org/openstack/api-wg/process.html we need to figure out what form "official version" takes16:59
etoewsbut i think that's a ways down the road16:59
etoews#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Thu Jan 29 17:00:10 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-01-29-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-01-29-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-01-29-16.00.log.html17:00
*** ryansb has left #openstack-meeting-317:00
etoewsthank you so much everybody.17:00
elmikoetoews: tnx!17:00
*** elmiko has left #openstack-meeting-317:01
kauferetoews: thx!17:01
*** scheuran has quit IRC17:01
*** markvoelker has quit IRC17:03
*** cdent has left #openstack-meeting-317:04
*** marg7175 has joined #openstack-meeting-317:05
*** dtroyer has left #openstack-meeting-317:07
*** jkraj has quit IRC17:08
*** coolsvap is now known as coolsvap|afk17:10
*** safchain has quit IRC17:10
*** isviridov is now known as isviridov_away17:17
*** amotoki has quit IRC17:18
*** yapeng has joined #openstack-meeting-317:21
*** sahid has quit IRC17:23
*** alexsyip has joined #openstack-meeting-317:26
*** yapeng has quit IRC17:27
*** markvoelker has joined #openstack-meeting-317:30
*** SumitNaiksatam has quit IRC17:32
*** MaxV has quit IRC17:32
*** MaxV has joined #openstack-meeting-317:33
*** matrohon has joined #openstack-meeting-317:34
*** jcoufal_ has quit IRC17:35
*** nelsnelson has quit IRC17:37
*** MaxV has quit IRC17:38
*** bradjones has quit IRC17:38
*** bradjones has joined #openstack-meeting-317:39
*** erikmwilson has left #openstack-meeting-317:40
*** nelsnelson has joined #openstack-meeting-317:43
*** matrohon has quit IRC17:46
*** carl_baldwin has quit IRC17:49
*** marg7175 has quit IRC17:50
*** mattgriffin has quit IRC17:53
*** eghobo has joined #openstack-meeting-317:53
*** SumitNaiksatam has joined #openstack-meeting-317:53
*** marg7175 has joined #openstack-meeting-317:53
*** salv-orlando has quit IRC17:54
*** carl_baldwin has joined #openstack-meeting-317:55
*** Yi has joined #openstack-meeting-317:56
*** mageshgv has joined #openstack-meeting-317:59
*** LouisF has joined #openstack-meeting-317:59
*** Youcef has joined #openstack-meeting-318:00
*** reed has joined #openstack-meeting-318:00
SumitNaiksatamLouisF: mageshgv Yi: hi there18:00
*** rkukura has joined #openstack-meeting-318:00
SumitNaiksatamrkukura: hi18:00
SumitNaiksatamlets get started18:00
rkukurahi18:00
mageshgvhi18:00
Yihello18:00
LouisFhi18:00
banixSumitNaiksatam: hi18:01
SumitNaiksatambanix: hi18:01
banixhi everybody18:01
SumitNaiksatam#startmeeting networking_policy18:01
openstackMeeting started Thu Jan 29 18:01:11 2015 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: networking_policy)"18:01
openstackThe meeting name has been set to 'networking_policy'18:01
SumitNaiksatamwe will discuss kilo plan and milestone as an agenda items, but prior to that I dont have any milestone related announcements18:01
SumitNaiksatamanything anyone wants to share in terms info/announcements to the team?18:02
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy#Jan_29th.2C_201518:02
SumitNaiksatam#topic Bugs18:02
*** openstack changes topic to "Bugs (Meeting topic: networking_policy)"18:02
SumitNaiksatamwe went through some of the major bugs last week18:03
*** yapeng has joined #openstack-meeting-318:03
SumitNaiksatama couple of more have been added to that, and mageshgv has fixed another18:03
SumitNaiksatamyapeng: hi18:03
yapenghi18:03
SumitNaiksatambut the meta-comment i had was that to request you to look at the assigned bugs18:04
SumitNaiksatammost bugs have a milestone date18:04
SumitNaiksatamif a bug is assigned to you and is targeted for k1, please confirm that you can fix it18:04
*** etoews has quit IRC18:04
SumitNaiksatamelse move it to a later milestone18:04
SumitNaiksatamfor bugs which are more open ended we have a “next” milestone18:05
SumitNaiksatamso use you judgements18:05
*** KrishnaK has joined #openstack-meeting-318:05
SumitNaiksatam*judgement18:05
SumitNaiksatamKrishnaK: hi18:05
KrishnaKSumitNaiksatam: hi18:05
SumitNaiksatamif we determine that the bug is high priority we cannot defer it to too long though18:06
SumitNaiksatamcurrently we dont have any critical bug18:06
SumitNaiksatam*bugs18:06
*** ivar-lazzaro has joined #openstack-meeting-318:07
SumitNaiksatamcurrently i think all of the k1 server side bugs are assigned to myself, rkukura, ivar-lazzaro, and mageshgv18:07
SumitNaiksatamivar-lazzaro: hi18:07
ivar-lazzarohi18:07
*** kaufer has left #openstack-meeting-318:08
SumitNaiksatamalso please make a call whether a particular fix needs to be backported18:08
SumitNaiksatamif so please assign the “juno-backport-potential” tag18:08
SumitNaiksatamonce the fix merges, please cherry-pick the fix to the stable/juno branch18:08
SumitNaiksatamquestions/comments?18:09
SumitNaiksatamokay moving on18:09
SumitNaiksatam#topic Packaging Update18:10
*** openstack changes topic to "Packaging Update (Meeting topic: networking_policy)"18:10
SumitNaiksatamrkukura: you have some good news to report, right? ;-)18:10
rkukurayes18:10
*** songole has joined #openstack-meeting-318:10
*** ff has joined #openstack-meeting-318:10
rkukuraAt least I think this is since last meeting18:10
SumitNaiksatamrkukura: yes18:11
rkukuraThe GBP packages are now in the official RDO yum repositories18:11
SumitNaiksatamyay!18:11
ivar-lazzaronice!18:11
rkukuraThis means running “yum install \*gbp\*” will install all of them on top of an existing RDO setup.18:11
SumitNaiksatamrkukura: sweet! thats much easier18:12
banixcool!18:12
rkukuraI plan to do some testing and then update the RDO wiki page as soon as I get a chance.18:12
Yivery cool18:12
KrishnaKrkukura: great! Also thanks for your help this AM. Iam continuing my setup testing (centos ) ...18:12
rkukuraThis should support Fedora 20 and 21, as well as RHEL 7 and CentOS 7.18:12
SumitNaiksatamKrishnaK: thanks for your perseverance on this, you are the only person at this time that i know off who has dared to start testing on CentOS, so the team needs to really thank you here! :-)18:13
SumitNaiksatamrkukura: cool18:14
rkukuraNext steps are to start supporting GBP in the puppet scripts and Red Hat’s packstack and foreman installers.18:14
SumitNaiksatamrkukura: so the issues which KrishnaK has ran into (gbpautomation), that is CentOS-specific, or its his setup specific?18:14
rkukuraKrishnaK: Correct me if I’m wrong, but I think the issue was that the default packstack configuration did not install heat, so restarting it with GBP failed because it wasn’t configured.18:15
KrishnaKrkukura: yes. thx.18:16
rkukuraI’ll add a note about this to the RDO GBP wiki as well.18:16
rkukuraThat it for RDO.18:16
SumitNaiksatamrkukura: good point about the installer18:16
SumitNaiksatam*installers18:16
SumitNaiksatamrkukura: is that a long process too, to get a patch in?18:17
rkukuraI’ve never directly worked on upstreaming puppet patches, but that may take some time18:17
SumitNaiksatamrkukura: okay, is it an ongoing thing, or they have milestones and freezes too?18:17
rkukuraWould be good to get someone with puppet experience involved, and I think SumitNaiksatam may have someone in mind.18:18
SumitNaiksatamrkukura: I am not volunteering myself :-)18:18
*** amotoki has joined #openstack-meeting-318:18
SumitNaiksatamrkukura: but yeah we need to discuss offline18:18
rkukuraI don’t think upstream puppet is tied to OpenStack release cadence.18:19
SumitNaiksatamrkukura: okay18:19
SumitNaiksatamrkukura: anyone else wanting to jump in on this and help out is welcome18:19
rkukuraIf anyone on the team wants to take this on, please speak up!18:19
SumitNaiksatamrkukura: +118:19
SumitNaiksatamrkukura: if someone wants to jump in on this, you will be able to connect them to the right set of folks and pointers in terms of the process to follow?18:20
rkukuraI’m happy to advice and help, but I’m focusing on upstream neutron work right now, plus some GBP bug fixing, etc.18:20
*** s3wong has joined #openstack-meeting-318:20
*** eghobo has quit IRC18:21
SumitNaiksatamrkukura: yeah, my question was more whether we know the process18:21
s3wongsorry, late18:21
SumitNaiksatamrkukura: seems like you know it18:21
SumitNaiksatams3wong: hi, np18:21
SumitNaiksatamnoticed songole joined earlier too, hi!18:21
rkukuraSumitNaiksatam: I’ve observed it through team meetings etc., back at Red Hat, but never involved directly with puppet or packstack.18:21
songoleHi SumitNaiksatam18:21
SumitNaiksatamrkukura: okay, i think that should be good to get us started18:22
SumitNaiksatamokay any other questions for rkukura on the fedora and RDO?18:22
*** coolsvap|afk is now known as coolsvap18:22
*** gugl has quit IRC18:22
SumitNaiksatamrkukura: BIG thanks on behalf of the entire team for working on this and getting this into RDO!18:23
*** gugl has joined #openstack-meeting-318:23
SumitNaiksatamon the ubuntu packaging18:23
SumitNaiksatammageshgv ran into an issue when installing the group-based-policy-automation package in his setup18:23
*** amotoki has quit IRC18:24
SumitNaiksatamhe investigated and found out why it happens18:24
SumitNaiksatammageshgv: thanks for that18:24
SumitNaiksatamwe are still working on what the right solution for this18:24
SumitNaiksatamdepending on which ubuntu packages you have installed, you may or may not run into that issue18:24
SumitNaiksatamplease ping mageshgv or me if you run into it and need a solution (while we are trying to fix this correctly)18:25
*** salv-orlando has joined #openstack-meeting-318:25
SumitNaiksatammageshgv: anything you wanted to add on that?18:25
SumitNaiksatamok next topic18:25
mageshgvBasically we will run into this problem if we have pbr version <0.10.718:25
SumitNaiksatammageshgv: ah okay18:26
SumitNaiksatam#topic Proposed Kilo Plan and Milestones18:26
*** openstack changes topic to "Proposed Kilo Plan and Milestones (Meeting topic: networking_policy)"18:26
SumitNaiksatam#link https://etherpad.openstack.org/p/kilo-gbp-plan18:26
SumitNaiksatamso we have been gathering feedback after the release, and to some extent discusssing in this meeting as well18:26
SumitNaiksatamthe plan above is based on pretty much everyone’s input (and the issues we have logged in launchpad)18:27
SumitNaiksatamthis is a kind of a guiding plan18:27
*** Sukhdev has quit IRC18:28
SumitNaiksatamwe will adapt as we go along18:28
SumitNaiksatamso please provide your feedback18:28
rkukuraI think we need to explicitly list tempest tests and CI18:29
SumitNaiksatamrkukura: okay18:29
rkukuraI see GBP Test Plan and CI now, so OK18:29
rkukurawas looking for the word “tempest”18:29
SumitNaiksatamyeah but we could add “tempest tests” as a separate item18:29
SumitNaiksatamyeah we could add that explicitly18:30
SumitNaiksatami agree18:30
*** LouisF has quit IRC18:30
SumitNaiksatami think that is one are where we would need to work collectively as a team18:30
SumitNaiksatamadd coverage in tempest for the entire project cannot be done by one or two people18:30
SumitNaiksatam*adding18:31
SumitNaiksatamso we will start by identifying one or two people, and they can guide the rest of the team here18:31
SumitNaiksatamif you are interested in participating in this, please ping me18:31
*** etoews has joined #openstack-meeting-318:32
*** LouisF has joined #openstack-meeting-318:32
SumitNaiksatamgiven that we planning to add more features, i think this is the most critical area of the project that needs attention so that we dont introduce regressions18:32
SumitNaiksatamwell even before we add features, we will be doing a bunch of refactoring18:32
SumitNaiksatamdo people have questions on the specific line items mentioned in the plan?18:33
*** pkoniszewski has joined #openstack-meeting-318:34
Yifor the l4-7 classifiers -- do you have more details?18:34
yapengI have question about DB change and REST API changes.18:34
SumitNaiksatami will take Yi’s question first18:35
SumitNaiksatamYi: yes, LouisF has posted a spec on that18:35
*** thomasem has quit IRC18:35
SumitNaiksatam#link https://review.openstack.org/#/q/status:open+project:stackforge/group-based-policy-specs+branch:master,n,z18:35
SumitNaiksatamYi: the above has all the specs currently in review18:36
Yiok18:36
LouisFSumitNaiksatam: i's like to have those specs reviewed18:36
SumitNaiksatamLouisF: :-)18:36
SumitNaiksatamLouisF: so Yi should look at the “GBP Classifier Extensions” spec?18:37
Yisure18:37
LouisFSumitNaiksatam, Yi : yes18:37
SumitNaiksatamis nicolas here?18:38
*** marg7175 has quit IRC18:38
SumitNaiksatamhe was planning to do some investigation on the ODL side to see how this could be implemented18:38
SumitNaiksatamthat is partly the reason that is holding this up18:38
*** marg7175 has joined #openstack-meeting-318:38
SumitNaiksatamwe need to have some level of validation that we are able to realize it18:39
s3wongSumitNaiksatam: don't think there is any DPI project on ODL as of yet18:39
SumitNaiksatams3wong: hmmm18:39
s3wongSumitNaiksatam: but that tons of projects are being proposed, so I probably have missed it18:40
*** Sukhdev has joined #openstack-meeting-318:40
SumitNaiksatams3wong: yeah, we had this discussion a few months back, seems like you are saying that not much has changed since18:40
SumitNaiksatamthat is part of the reason i put this in the second milestone so that we can some more time to investigate18:40
s3wongSumitNaiksatam: not that I am aware of, but then again, I have NOT being attending or catching up with the TSC meetings18:40
SumitNaiksatamLouisF: any chance that you can touch base with nicolas on this?18:40
SumitNaiksatams3wong: np18:41
yapengis the ODL the only option to implement this?18:41
LouisFSumitNaiksatam: i will contact him reagrds the odl support for dpi18:41
SumitNaiksatamyapeng: no, not saying that18:41
SumitNaiksatamyapeng: i brought it up because that was the option that nicolas mentioned he was going to explore18:41
s3wongyapeng: no, but we need a reference implementation18:41
SumitNaiksatamother than that no one has proposed anything18:41
SumitNaiksatamLouisF: thanks18:42
SumitNaiksatamyapeng: back to your question18:42
SumitNaiksatamyapeng: you were asking about DB and REST server?18:42
yapengmy question is that: DB change seems have big impact on many things, how to resolve the dependencies of all the other feature developed in parallel?18:43
*** MaxV has joined #openstack-meeting-318:43
SumitNaiksatamyapeng: yeah, good question18:43
SumitNaiksatamin fact this is true for the entire refactor18:43
*** eghobo has joined #openstack-meeting-318:44
*** mrunge has quit IRC18:44
SumitNaiksatamlets decide as as team as to whats the most non-disruptive path18:44
SumitNaiksatami have some ideas18:44
*** amotoki has joined #openstack-meeting-318:45
SumitNaiksatamso specifically regarding the DB18:45
SumitNaiksatamthe critical change that we need to make is to remove the foreign key constraints18:45
SumitNaiksatamforeing key constraints to the neutron tables that is18:46
s3wongSumitNaiksatam: is upgrade from GBP Juno to GBP Kilo an item to consider also on this?18:46
SumitNaiksatams3wong: good point :-)18:46
SumitNaiksatams3wong: we will have to make some hard decisions there18:47
SumitNaiksatams3wong: one of the stated goals of the Juno release was that we are making it available to users to get their feedback, so changes should be expected18:47
*** MaxV has quit IRC18:47
s3wongSumitNaiksatam: that18:47
rkukuraSumitNaiksatam: In place of the foriegn key constraints, is the idea to consume notifications from neutron and cleanup related GBP resources if something is deleted in neutron?18:47
s3wongthat's fair (sorry, accidentally hit "enter")18:48
SumitNaiksatamthat said, we will gauge who is using it, and how much impact it has, and based on that decide the most effective strategy18:48
SumitNaiksatamwe will definitely strive to minimize pain18:48
*** sunny_ has joined #openstack-meeting-318:48
SumitNaiksatamrkukura: good question, the point about concurrently using the Neutron API is tricky in itself (as we have discussed before)18:49
SumitNaiksatamrkukura: the approach that you mention is certainly worth considering18:50
s3wongSumitNaiksatam, rkukura: what approach?18:51
rkukuras3wong: replacing the FK constraints with cleanup based on notifications from neutron18:51
SumitNaiksatams3wong: so if someone cleans up a port on the neutron side, clean up the PT of the GBP side18:51
s3wongSumitNaiksatam, rkukura: OK18:52
SumitNaiksatamand do this by consuming the port delete notification from Neutron18:52
SumitNaiksatamthis happens today based on the FK constraints18:52
s3wongSumitNaiksatam, rkukura: does Neutron have all the notification on things we care about (port, subnet, router, SG, SG rules...)?18:52
SumitNaiksatamand all that wil have to be implemented in the code when we decouple18:52
SumitNaiksatams3wong: yes, for all CRUD operations for all resources18:53
s3wongSumitNaiksatam: good18:53
*** mwagner_lap has quit IRC18:53
SumitNaiksatamthe issue obviously is that if the PT deletion fails for some reason, then we are left in an inconsistent state18:53
SumitNaiksatamor if we lose the notification18:53
rkukuraHopefully we’ll be able to work through these kinds of details in reviewing specs for kilo.18:54
SumitNaiksatamrkukura: yeah18:54
rkukurawhich means getting the spec written ;)18:54
SumitNaiksatam:-)18:54
YiSumit, rkukura: the notification is coming from API, or from mechanism driver?18:55
s3wongSumitNaiksatam: so the notification comes as the API is invoked? Or as the operation is completed (i.e., the Neutron port is deleted)?18:55
rkukuraas I recall, there are start and end notifications18:55
SumitNaiksatamYi: s3wong the notification comes on an AMQP topic18:56
s3wongrkukura: oh, OK18:56
ivar-lazzaroDo they exist for any resource? Or just ports?18:56
*** coolsvap is now known as coolsvap|afk18:56
banixall resourcces18:56
SumitNaiksatamivar-lazzaro: my earlier point, it used to be for all resources, unless something has changed18:57
SumitNaiksatamthe API handling code had the notifications built it18:57
rkukuraivar-lazzaro: Ports have additional notifications for specific state changes to be consumed by nova18:57
SumitNaiksatamrkukura: good point18:58
SumitNaiksatamokay we have a couple of mins18:58
rkukuraand/or by firewall (SG) driver/agent18:58
SumitNaiksatamgood dicussion18:58
yapengneutron has these kinds of notification existing today?18:58
s3wongSumitNaiksatam, rkukura: with this, does it mean that our policy drivers no longer need to have the GBP ML2 driver?18:58
SumitNaiksatamwe need to have a lot more of that on these topics18:58
ivar-lazzaroSumitNaiksatam, rkukura: I see. thanks for the clarification18:58
banixyes, ceilometer for example uses them I believe (not to mention nova)18:59
SumitNaiksatamivar-lazzaro: i was trying to look up the code, but github is not responding18:59
SumitNaiksatams3wong: no, that is independent18:59
SumitNaiksatambanix: perfect, thats where it started18:59
ivar-lazzaros3wong: I guess it depends on what your ML2 driver' role is. For instance, if you use it to bind a special ML2 network type you may still need one18:59
*** thomasem has joined #openstack-meeting-319:00
rkukuras3wong: one potential risk is that the ml2 driver and policy driver will now be in separate processes, but may need some coordination, but that shouldn’t be too difficult, and is not that different from cases where neutron-server is replicated.19:00
s3wongivar-lazzaro, SumitNaiksatam: I see. The reason I asked is that one of the function of the GBP ML2 driver seems to be get notified for port state changes19:01
*** salv-orlando has quit IRC19:01
SumitNaiksatamivar-lazzaro: rkukura s3wong: good points19:01
SumitNaiksatamwe are min over time19:01
SumitNaiksatamwe can take this to #openstack-gbp19:01
SumitNaiksatamthanks all for attending19:01
SumitNaiksatambye19:01
s3wongSumitNaiksatam: obviously a great topic to discuss :-)19:01
banixbye19:01
rkukurathank19:01
mageshgvbye19:01
s3wongthanks!19:01
SumitNaiksatam#endmeeting19:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:01
yapengbye19:01
*** thomasem has quit IRC19:01
openstackMeeting ended Thu Jan 29 19:01:56 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-01-29-18.01.html19:02
Yil8r19:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-01-29-18.01.txt19:02
rkukurabye19:02
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-01-29-18.01.log.html19:02
ivar-lazzarobye19:02
*** rkukura has left #openstack-meeting-319:02
*** thomasem has joined #openstack-meeting-319:02
*** mageshgv has quit IRC19:02
*** egallen has quit IRC19:02
*** sunny_ has quit IRC19:03
*** Yi has quit IRC19:04
*** sunny_ has joined #openstack-meeting-319:04
*** eghobo has quit IRC19:04
*** amotoki has quit IRC19:05
*** kaufer has joined #openstack-meeting-319:05
*** kaufer has left #openstack-meeting-319:06
*** eghobo has joined #openstack-meeting-319:07
*** salv-orlando has joined #openstack-meeting-319:07
*** eghobo has quit IRC19:09
*** yapeng_ has joined #openstack-meeting-319:10
*** ivar-lazzaro has quit IRC19:10
*** mattgriffin has joined #openstack-meeting-319:11
*** yapeng_ has quit IRC19:15
*** Godfath3r has joined #openstack-meeting-319:26
*** smillward has joined #openstack-meeting-319:27
*** reed has quit IRC19:27
*** jaypipes has quit IRC19:31
*** dutsmoc has quit IRC19:38
*** sunny_ has quit IRC19:40
*** songole has quit IRC19:40
*** smillward has quit IRC19:40
*** sunny_ has joined #openstack-meeting-319:43
*** LouisF has quit IRC19:46
*** enikanorov has joined #openstack-meeting-319:47
*** sandr8_ has joined #openstack-meeting-319:48
*** ChuckC_ has joined #openstack-meeting-319:50
*** ivar-lazzaro has joined #openstack-meeting-319:50
*** s3wong_ has joined #openstack-meeting-319:51
*** tteggel_ has joined #openstack-meeting-319:52
*** lintan_ has joined #openstack-meeting-319:52
*** perister1 has joined #openstack-meeting-319:54
*** baoli has quit IRC19:54
*** mikal_ has joined #openstack-meeting-319:55
*** Yi has joined #openstack-meeting-319:56
*** ChuckC has quit IRC19:56
*** enikanorov_ has quit IRC19:56
*** sandr8 has quit IRC19:56
*** s3wong has quit IRC19:56
*** tteggel has quit IRC19:56
*** lintan__ has quit IRC19:56
*** peristeri has quit IRC19:56
*** mikal has quit IRC19:56
*** thangp has quit IRC19:57
*** Godfath3r has quit IRC19:58
*** amotoki has joined #openstack-meeting-320:05
*** amotoki has quit IRC20:10
*** carl_baldwin has quit IRC20:13
*** s3wong_ has quit IRC20:17
*** ChuckC has joined #openstack-meeting-320:20
*** Youcef has quit IRC20:20
*** mwagner_lap has joined #openstack-meeting-320:21
*** ChuckC_ has quit IRC20:23
*** s3wong has joined #openstack-meeting-320:24
*** VW_ has quit IRC20:24
*** salv-orlando has quit IRC20:27
*** ChuckC has quit IRC20:27
*** SridharRamaswamy has quit IRC20:30
*** sunny_ has quit IRC20:30
*** SridharRamaswamy has joined #openstack-meeting-320:31
*** etoews has quit IRC20:35
*** matrohon has joined #openstack-meeting-320:37
*** Sukhdev has quit IRC20:40
*** vishwanathj has joined #openstack-meeting-320:40
*** banix has quit IRC20:43
*** Sukhdev has joined #openstack-meeting-320:44
*** banix has joined #openstack-meeting-320:46
*** dboik has joined #openstack-meeting-320:46
*** pkoniszewski has quit IRC20:51
*** megm has joined #openstack-meeting-320:53
*** ChuckC_ has joined #openstack-meeting-320:54
*** clouddon has joined #openstack-meeting-320:54
mattgriffinHA Guide meeting starting in 5 minutes :) Agenda added to https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update#Next_Meeting and our etherpad. Please add any other items.20:55
*** armax has quit IRC20:56
*** yapeng_ has joined #openstack-meeting-320:59
*** SridharRamaswamy has quit IRC21:00
mattgriffinHello HA Guide update team21:00
*** nickchase has joined #openstack-meeting-321:00
mattgriffinhi nickchase21:00
nickchaseHi, mattgriffin21:01
nickchasehow goes?21:01
*** mrmartin has joined #openstack-meeting-321:01
mattgriffinnickchase, going well. almost friday21:01
clouddonhi all. logging in from mobile, responses might be bumpy21:02
nickchasethank goodness. :)21:02
mattgriffinclouddon, hello!21:02
mattgriffintoday's agenda - https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update#Next_Meeting21:02
nickchaseHey, clouddon!21:02
megmHello, HA Guide update team!21:02
mattgriffinclouddon, i'll type out...21:02
mattgriffinmegm, hello!21:02
clouddonhaha21:02
mattgriffinagenda21:02
mattgriffin1. Bug bash results21:02
*** lblanchard has quit IRC21:03
mattgriffin2. Next steps - triage the open bugs and possible assignment of bugs21:03
mattgriffin3. Update on getting added to the OpenStack Calendar. Thanks Sriram!21:03
*** igordcard has joined #openstack-meeting-321:03
mattgriffinshall we get started?21:03
*** killer_prince has quit IRC21:03
clouddonthe for typing. my place asure21:03
mattgriffinigordcard, hello and bye killer_prince21:03
mattgriffinclouddon, np :)21:03
*** s3wong has quit IRC21:04
*** yapeng_ has quit IRC21:04
mattgriffinok... #1 results from last week's Bug Bash21:04
*** eghobo has joined #openstack-meeting-321:04
igordcardoh, hello all21:04
*** killer_prince has joined #openstack-meeting-321:04
mattgriffinthanks to clouddon for organizing. we went from 8 to 25 bugs21:04
*** killer_prince is now known as lazy_prince21:04
clouddonyay!21:05
mattgriffinif you'd like to keep on bashing, tips from clouddon at https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update#Bug_Bash help21:05
clouddonthe for participating, matt n Shamail.21:06
*** SridharRamaswamy has joined #openstack-meeting-321:06
mattgriffinyeah... i need to do keep finding more bugs... just the tip of the iceberg21:06
*** sunny_ has joined #openstack-meeting-321:06
mattgriffinbut shouldn't stop anyone from triaging (the next item on the agenda)21:07
clouddonyes. ofcourse21:07
mattgriffinas well as fixing some of these21:07
clouddonI have some cycles tomorrow to triage21:07
clouddonunless someone already did it/ does it21:08
mattgriffinclouddon, cool. i should be reporting some tomorrow as well21:08
clouddonfor foxing, if its OK, I'd like to pick up bugs in chapter 121:08
clouddonIntro chapter21:09
clouddonOK with folks?21:09
mattgriffin+121:09
nickchase+121:09
nickchaseBefore we go deep into bugs, can I ask a quick question?21:09
mattgriffinnickchase, sure21:09
clouddongr8.21:09
clouddonsure21:09
nickchasethanks.  What I would like to know is...21:09
nickchasethe scale of what we're doing.  Are we just "fixing" the current doc, or is there a plan to change/enhance the structure?21:10
*** s3wong has joined #openstack-meeting-321:10
clouddonone of the bugs is on that21:10
clouddonDont have bug I'd now. but can fwd via email21:10
nickchasethis one? https://bugs.launchpad.net/openstack-manuals/+bug/121133221:11
clouddonwe can revisit the organization and structure21:11
nickchaseI'm not advocating either way21:11
nickchasejust asking what we're focusing on21:11
*** eghobo has quit IRC21:11
nickchasewe're going to pull in some Mirantis people to help21:11
nickchaseand I wanted to make sure that they were working on the right thing21:12
clouddonno, I filed another one21:12
clouddongr8. thats awesome. pl look st open ones21:12
mattgriffinnickchase, good question...21:12
mattgriffinnickchase, i would like to get to some larger scale structural changes like we've captured on the etherpad21:13
nickchaseGreat.  Remind me of the link?21:13
mattgriffinbut in the few bugs that i've filed, it's more about incorrect or outdated content21:13
nickchasesure, makes sense.21:13
nickchaseIt's likely that anything that's getting used enough that we notice it's wrong would go into any new structure anyway.21:14
mattgriffinyeah21:14
mattgriffinso i think a good focus for now is to fix a lot of the incorrect info and then we'll be ready to restructure.21:15
mattgriffinanyone else have a view?21:15
clouddon+121:15
nickchase+121:16
clouddonit if someone hasvpeoposal for new or betterr structure pl propose21:16
*** Godfath3r has joined #openstack-meeting-321:16
megmI have a question21:16
clouddonsorry for typos. I meant to say, pl propose while we fix current issues21:17
megmwhere should this doc begin?  Should it assume an already-deployed multil-node OpenStack environment or should it start with how to deploy an HA environment?21:17
nickchaseI think we need to start with deploying an HA environment21:18
nickchaseI mean, if you don't have the right foundation you can't MAKE it HA, can you?21:18
*** rcleere is now known as rcleere_away21:19
megmSo this would essentially replace the current Installation Guide?21:19
nickchaseNo, no, I would think it would supplement it21:19
nickchaseLike, "follow the instructions in the Install Guide, but here are the things you should do differently"21:20
nickchasebut that's just a thought on my part21:20
clouddonwe're providonig instructions to setup HA. this would need multi nodes.21:20
mattgriffinnickchase, how is HA addressed in the Install Guide?21:20
nickchaseit's not.21:20
mattgriffinha21:20
mattgriffinok21:20
nickchaseThe install guide...21:20
*** amotoki has joined #openstack-meeting-321:20
nickchaseits purely focused on getting the reasder to the piint where they can fire up Horizon launch an instance and log into it21:20
nickchasethat's it.21:20
nickchaseNot that the other services aren't covered21:21
nickchasebut that's the philiosophy21:21
nickchasebecause it's recognized that...21:21
nickchaseall cases are different.  For example, if you're doing HA, you have specific concerns.21:21
nickchaseSo I suppose if the instructions are significantly different, it makes sense to duplicate.21:21
nickchasewell, replace, not duplicate.21:22
clouddontheoretically install guise should have chapter on ha. in future may be21:22
nickchaseWell, it'd be good to cover it in the install guide, but could it really be covered in a chapter?21:23
nickchaseAnd if so, why do we need a whole manual? :)21:23
clouddonnote theoretically :)21:23
*** mwagner_lap has quit IRC21:24
clouddonfor now, we should treat install guide for default vaetups. more advanced, specific needs of HA are met with this21:24
*** amotoki has quit IRC21:25
nickchase+121:26
mattgriffinclouddon, ack ... then, as nickchase suggested, we probably need an HA deployment example at the beginning of the HA Guide21:26
megmSo does the HA setup say "Do this, this, and this following instructions in <link-to-specific-section-of-install-guide>?21:26
megmAnd then add a couple steps that are HA-specific, then more steps from install guide?21:26
nickchaseright now it's interesting because...21:27
nickchasethe HA guide basically says, "these are the pieces that you need to do an HA cluster, and here's you install/deal with each of those individually".21:27
*** armax has joined #openstack-meeting-321:27
nickchaseIt's educational in that...21:27
clouddonno. we only say ass these things to make service s HA. don't refer back to install gyide21:27
clouddoncorrect. +1 nick21:28
nickchaseit shows clearly that there's no such thing as "the OpenStack software".  It's really a bunch of different packages/programs/etc.  There's no specific database/queuing system/etc. that you need to use to underpin all of this.21:28
nickchaseUntil I started working on the guide I never realized that.21:28
nickchaseand it's important that that's clear.21:28
clouddonmegm, I think this is larger debate. plz file a bug to this effect. let's triage it based on priority and resources21:29
nickchaseI think that's really part of the document structure question.21:30
megmOkay -- I was just curious about what exactly we meant by supplementing the Install Guide21:30
nickchaseWould anybody mind if I took a look at the structure, potentially with megm?21:30
*** salv-orlando has joined #openstack-meeting-321:30
nickchaseit's probably the area where I can be of most assistance here.  I never did get Galera running properly. :)21:31
clouddonmegm ways ur email. I can follow up on structure21:31
megmmmcroberts@mirantis.com21:31
clouddonnick. sorry misread. plz go ahead21:31
nickchase:)  thank you. mine is nchase@mirantis.com, so please include me?  We'll take a look, me and megm.21:32
mattgriffinshould we dedicate the next meeting to that topic?21:32
nickchaseworks for me.21:32
mattgriffinand start an email thread - matt.griffin@percona.com21:32
mattgriffincool21:33
clouddonworks21:33
clouddonlet's do hangout:)21:33
megmWorks for me.21:33
mattgriffingreat... so agenda is set of the next meeting. any other important topics to discuss now?21:33
mattgriffinclouddon, hangout +121:33
megmThose of you who have been working on this -- does that seem like a good next step?21:34
clouddonyes. no more agenda from.me today21:34
mattgriffinmegm, i think we should still identify and fix poor content but never hurts to make progress on a structural change21:34
nickchase+121:35
nickchasewe definitely need to fix content problems21:35
megm+121:35
clouddonmatt, action items?21:35
clouddonwe're running out of time21:35
mattgriffinack... 1. start an discussion about content structure21:36
mattgriffin2. Add hangout URL to the agenda for next week on the wiki page21:36
mattgriffin3. continue to find and triage content bugs21:36
mattgriffinany others?21:36
clouddonno21:37
mattgriffinif not... thanks for your time all. have a great day!21:37
nickchaseThanks, all!21:37
megmThanks!21:37
clouddonthe, bye all. nice meeting u megm21:37
*** nickchase has quit IRC21:40
*** MaxV has joined #openstack-meeting-321:41
*** baoli has joined #openstack-meeting-321:42
*** carl_baldwin has joined #openstack-meeting-321:46
*** iovadia has joined #openstack-meeting-321:49
*** megm has quit IRC21:49
*** mrmartin has quit IRC21:51
*** kozhukalov has quit IRC21:53
*** Yi has quit IRC21:54
*** sunny_ has quit IRC21:55
*** baoli has quit IRC21:55
*** armax has quit IRC21:55
*** baoli has joined #openstack-meeting-321:56
*** sunny_ has joined #openstack-meeting-321:56
*** Godfath3r has quit IRC21:57
*** VW_ has joined #openstack-meeting-321:58
*** Piet has quit IRC21:59
*** salv-orlando has quit IRC22:00
*** MaxV has quit IRC22:00
*** eghobo has joined #openstack-meeting-322:03
*** VW_ has quit IRC22:03
*** sunny_ has quit IRC22:08
*** iovadia has quit IRC22:09
*** etoews has joined #openstack-meeting-322:09
*** rcleere_away is now known as rcleere22:11
*** Piet has joined #openstack-meeting-322:14
*** etoews has quit IRC22:15
*** ff has quit IRC22:15
*** sunny_ has joined #openstack-meeting-322:15
*** iovadia has joined #openstack-meeting-322:17
*** thomasem has quit IRC22:22
*** s3wong has quit IRC22:23
*** clouddon has quit IRC22:24
*** armax has joined #openstack-meeting-322:25
*** mattgriffin has quit IRC22:25
*** Yi has joined #openstack-meeting-322:31
*** mattfarina has quit IRC22:32
*** mattgriffin has joined #openstack-meeting-322:32
*** matrohon has quit IRC22:34
*** perister1 has quit IRC22:34
*** gholler has quit IRC22:34
*** banix has quit IRC22:37
*** iovadia has quit IRC22:41
*** eghobo has quit IRC22:42
*** Sukhdev has quit IRC22:44
*** markvoelker has quit IRC22:46
*** Networkn3rd has quit IRC22:46
*** markvoelker_ has joined #openstack-meeting-322:47
*** jpomero has quit IRC22:48
*** yapeng_ has joined #openstack-meeting-322:48
*** sunny_ has quit IRC22:48
*** tellesnobrega_ has joined #openstack-meeting-322:51
*** yapeng_ has quit IRC22:53
*** marg7175 has quit IRC22:53
*** jckasper has quit IRC22:54
*** sunny_ has joined #openstack-meeting-322:57
*** Sukhdev has joined #openstack-meeting-322:59
*** yamahata has quit IRC23:01
*** jckasper has joined #openstack-meeting-323:02
*** VW_ has joined #openstack-meeting-323:03
*** alexsyip has quit IRC23:09
*** amotoki has joined #openstack-meeting-323:09
*** marg7175 has joined #openstack-meeting-323:10
*** salv-orlando has joined #openstack-meeting-323:12
*** jckasper has quit IRC23:13
*** jckasper has joined #openstack-meeting-323:13
*** fischerw has quit IRC23:13
*** amotoki has quit IRC23:14
*** egallen has joined #openstack-meeting-323:15
*** Brian_Shang has joined #openstack-meeting-323:16
*** salv-orlando has quit IRC23:17
*** marg7175 has quit IRC23:26
*** sunny_ has quit IRC23:26
*** salv-orlando has joined #openstack-meeting-323:28
*** marg7175 has joined #openstack-meeting-323:35
*** dboik has quit IRC23:35
*** mattgriffin has quit IRC23:35
*** thomasem has joined #openstack-meeting-323:36
*** watanabe_isao has joined #openstack-meeting-323:36
*** egallen has quit IRC23:39
*** baoli has quit IRC23:41
*** dboik has joined #openstack-meeting-323:41
*** sunny_ has joined #openstack-meeting-323:44
*** marg7175 has quit IRC23:47
*** seizadi has joined #openstack-meeting-323:50
*** baoli has joined #openstack-meeting-323:51
*** seizadi1 has joined #openstack-meeting-323:53
*** seizadi has quit IRC23:54
*** salv-orlando has quit IRC23:56
*** baoli has quit IRC23:57
*** salv-orlando has joined #openstack-meeting-323:57
*** bknudson has quit IRC23:57

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