Thursday, 2015-05-07

*** s3wong has quit IRC00:06
*** s3wong has joined #openstack-meeting-300:08
*** yalie has joined #openstack-meeting-300:15
*** mwang2_ has quit IRC00:24
*** VW_ has quit IRC00:25
*** igordcard has quit IRC00:28
*** clu_ has quit IRC00:28
*** zhenguo has joined #openstack-meeting-300:28
*** eghobo_ has quit IRC00:30
*** s3wong has quit IRC00:33
*** eghobo has joined #openstack-meeting-300:33
*** pavel_bondar has quit IRC00:34
*** pavel_bondar has joined #openstack-meeting-300:34
*** s3wong has joined #openstack-meeting-300:35
*** VW_ has joined #openstack-meeting-300:44
*** sarob has quit IRC00:47
*** sarob has joined #openstack-meeting-300:49
*** smccully has quit IRC00:54
*** sigmavirus24 is now known as sigmavirus24_awa00:56
*** shakamunyi has quit IRC01:02
*** VW_ has quit IRC01:16
*** asahlin_afk has quit IRC01:20
*** asahlin has joined #openstack-meeting-301:24
*** stanzgy has joined #openstack-meeting-301:35
*** bpokorny has quit IRC01:36
*** Aish has quit IRC01:36
*** s3wong has quit IRC01:46
*** sarob has quit IRC01:51
*** eghobo has quit IRC01:55
*** banix has joined #openstack-meeting-302:00
*** salv-orlando has quit IRC02:03
*** banix has quit IRC02:03
*** stevemar has joined #openstack-meeting-302:04
*** Piet has quit IRC02:09
*** shakamunyi has joined #openstack-meeting-302:09
*** yalie has quit IRC02:11
*** sarob has joined #openstack-meeting-302:15
*** yamahata has joined #openstack-meeting-302:17
*** vishwanathj_ has quit IRC02:20
*** yamahata has quit IRC02:20
*** yamahata has joined #openstack-meeting-302:20
*** Piet has joined #openstack-meeting-302:27
*** baoli has joined #openstack-meeting-302:27
*** lhcheng has quit IRC02:29
*** baoli_ has joined #openstack-meeting-302:30
*** baoli has quit IRC02:33
*** VW_ has joined #openstack-meeting-302:35
*** sarob has quit IRC02:42
*** yalie has joined #openstack-meeting-302:51
*** Aish has joined #openstack-meeting-302:54
*** Aish has left #openstack-meeting-302:54
*** markvoelker has quit IRC03:04
*** banix has joined #openstack-meeting-303:05
*** ivar-laz_ has joined #openstack-meeting-303:06
*** vishwanathj_ has joined #openstack-meeting-303:07
*** ivar-lazzaro has quit IRC03:09
*** ivar-laz_ has quit IRC03:10
*** SumitNaiksatam has joined #openstack-meeting-303:23
*** baoli_ has quit IRC03:30
*** fallenpegasus has joined #openstack-meeting-303:31
*** ivar-lazzaro has joined #openstack-meeting-303:34
*** watanabe_isao has quit IRC03:36
*** jrist has quit IRC03:43
*** marun has quit IRC03:44
*** btully has joined #openstack-meeting-303:53
*** jrist has joined #openstack-meeting-303:55
*** mrmartin has joined #openstack-meeting-304:00
*** watanabe_isao has joined #openstack-meeting-304:01
*** emagana has quit IRC04:03
*** markvoelker has joined #openstack-meeting-304:04
*** armax has joined #openstack-meeting-304:07
*** markvoelker has quit IRC04:09
*** armax has quit IRC04:16
*** mattgriffin has joined #openstack-meeting-304:20
*** banix has quit IRC04:32
*** banix has joined #openstack-meeting-304:33
*** btully has quit IRC04:35
*** amotoki has joined #openstack-meeting-304:38
*** banix has quit IRC04:38
*** emagana has joined #openstack-meeting-304:41
*** emagana has quit IRC04:46
*** gsagie has left #openstack-meeting-304:47
*** doug-fish has left #openstack-meeting-304:48
*** mattgriffin has quit IRC05:01
*** stevemar has quit IRC05:03
*** coolsvap|afk is now known as coolsvap05:03
*** nkrinner has joined #openstack-meeting-305:04
*** markvoelker has joined #openstack-meeting-305:05
*** mattgriffin has joined #openstack-meeting-305:07
*** markvoelker has quit IRC05:10
*** btully has joined #openstack-meeting-305:13
*** fallenpegasus has quit IRC05:14
*** vishwanathj_ has quit IRC05:20
*** ivar-laz_ has joined #openstack-meeting-305:24
*** ivar-laz_ has quit IRC05:24
*** ivar-laz_ has joined #openstack-meeting-305:24
*** ivar-laz_ has quit IRC05:25
*** ivar-laz_ has joined #openstack-meeting-305:25
*** fallenpegasus has joined #openstack-meeting-305:26
*** ivar-lazzaro has quit IRC05:27
*** Longgeek has joined #openstack-meeting-305:33
*** watanabe_isao has quit IRC05:35
*** emagana has joined #openstack-meeting-305:35
*** evgenyf has joined #openstack-meeting-305:37
*** eghobo has joined #openstack-meeting-305:40
*** emagana has quit IRC05:40
*** jtomasek has joined #openstack-meeting-305:43
*** btully has quit IRC05:48
*** salv-orlando has joined #openstack-meeting-305:50
*** markvoelker has joined #openstack-meeting-305:51
*** VW_ has quit IRC05:53
*** markvoelker has quit IRC05:56
*** baoli has joined #openstack-meeting-305:57
*** mrunge has joined #openstack-meeting-305:59
*** baoli has quit IRC06:02
*** Longgeek has quit IRC06:06
*** pkoniszewski has joined #openstack-meeting-306:07
*** mwang2_ has joined #openstack-meeting-306:21
*** mwang2_ has quit IRC06:25
*** scheuran has joined #openstack-meeting-306:25
*** jcoufal has joined #openstack-meeting-306:28
*** Rui_Zang has joined #openstack-meeting-306:32
*** Rui_Zang has quit IRC06:33
*** emagana has joined #openstack-meeting-306:37
*** Swami has quit IRC06:41
*** emagana has quit IRC06:42
*** safchain has joined #openstack-meeting-306:42
*** markvoelker has joined #openstack-meeting-306:52
*** markvoelker has quit IRC06:56
*** wojdev has joined #openstack-meeting-306:57
*** mattgriffin has quit IRC06:58
*** sahid has joined #openstack-meeting-307:00
*** matrohon has joined #openstack-meeting-307:03
*** Longgeek has joined #openstack-meeting-307:07
*** Longgeek has quit IRC07:21
*** Longgeek has joined #openstack-meeting-307:21
*** emagana has joined #openstack-meeting-307:32
*** emagana has quit IRC07:36
*** VW_ has joined #openstack-meeting-307:42
*** VW_ has quit IRC07:46
*** wojdev has quit IRC07:48
*** wojdev has joined #openstack-meeting-307:58
*** eghobo has quit IRC08:00
*** ajo has joined #openstack-meeting-308:01
*** scheuran has quit IRC08:02
*** jcoufal_ has joined #openstack-meeting-308:03
*** stanzgy has quit IRC08:04
*** ivar-laz_ has quit IRC08:05
*** JeanBriceCombebi has joined #openstack-meeting-308:06
*** stanzgy has joined #openstack-meeting-308:06
*** jcoufal has quit IRC08:07
*** scheuran has joined #openstack-meeting-308:17
*** JeanBriceCombebi has quit IRC08:20
*** JeanBriceCombebi has joined #openstack-meeting-308:20
*** mrunge has quit IRC08:22
*** mrunge has joined #openstack-meeting-308:22
*** e0ne has joined #openstack-meeting-308:23
*** emagana has joined #openstack-meeting-308:26
*** emagana has quit IRC08:31
*** JeanBriceCombebi has quit IRC08:36
*** JeanBriceCombebi has joined #openstack-meeting-308:38
*** wojdev has quit IRC08:46
*** yalie has quit IRC08:51
*** JeanBriceCombebi has quit IRC08:51
*** pkg_ has joined #openstack-meeting-308:53
*** markvoelker has joined #openstack-meeting-308:53
*** jcoufal_ has quit IRC08:55
*** jcoufal has joined #openstack-meeting-308:56
*** pkg_ has quit IRC08:57
*** markvoelker has quit IRC08:58
*** yamahata has quit IRC09:01
*** e0ne is now known as e0ne_09:03
*** fallenpegasus has quit IRC09:06
*** zz_ttrifonov is now known as ttrifonov09:10
*** emagana has joined #openstack-meeting-309:20
*** scheuran has quit IRC09:24
*** emagana has quit IRC09:25
*** evgenyf has quit IRC09:30
*** e0ne_ is now known as e0ne09:33
*** scheuran has joined #openstack-meeting-309:46
*** markvoelker has joined #openstack-meeting-309:54
*** wojdev has joined #openstack-meeting-309:55
*** evgenyf has joined #openstack-meeting-309:57
*** markvoelker has quit IRC09:58
*** wojdev has quit IRC10:13
*** emagana has joined #openstack-meeting-310:14
*** emagana has quit IRC10:18
*** Jean-Brice has joined #openstack-meeting-310:25
*** Jean-Brice has quit IRC10:25
*** ttrifonov is now known as zz_ttrifonov10:32
*** zz_ttrifonov is now known as ttrifonov10:34
*** coolsvap is now known as coolsvap|afk10:43
*** baoli has joined #openstack-meeting-310:43
*** baoli has quit IRC10:48
*** alexpilotti has joined #openstack-meeting-310:49
*** ttrifonov is now known as zz_ttrifonov10:53
*** markvoelker has joined #openstack-meeting-310:55
*** zz_ttrifonov is now known as ttrifonov10:56
*** sahid has quit IRC10:57
*** sahid has joined #openstack-meeting-310:58
*** Longgeek has quit IRC10:58
*** stanzgy has quit IRC10:58
*** Longgeek has joined #openstack-meeting-310:58
*** markvoelker has quit IRC11:00
*** banix has joined #openstack-meeting-311:05
*** emagana has joined #openstack-meeting-311:08
*** emagana has quit IRC11:13
*** VW_ has joined #openstack-meeting-311:18
*** banix has quit IRC11:21
*** VW_ has quit IRC11:22
*** e0ne is now known as e0ne_11:27
*** wojdev has joined #openstack-meeting-311:43
*** e0ne_ is now known as e0ne11:51
*** VW_ has joined #openstack-meeting-311:53
*** jckasper has joined #openstack-meeting-311:55
*** markvoelker has joined #openstack-meeting-311:56
*** VW_ has quit IRC11:57
*** jckasper has quit IRC12:00
*** markvoelker has quit IRC12:00
*** emagana has joined #openstack-meeting-312:02
*** emagana has quit IRC12:07
*** markvoelker has joined #openstack-meeting-312:15
*** JeanBriceCombebi has joined #openstack-meeting-312:24
*** btully has joined #openstack-meeting-312:35
*** VW_ has joined #openstack-meeting-312:38
*** btully has quit IRC12:48
*** emagana has joined #openstack-meeting-312:57
*** emagana has quit IRC13:01
*** sarob has joined #openstack-meeting-313:05
*** JeanBriceCombebi has quit IRC13:06
*** JeanBriceCombebi has joined #openstack-meeting-313:07
*** amotoki has quit IRC13:08
*** baoli_ has joined #openstack-meeting-313:11
*** baoli_ has quit IRC13:13
*** baoli has joined #openstack-meeting-313:14
*** jckasper has joined #openstack-meeting-313:17
*** david-lyle has quit IRC13:19
*** Piet has quit IRC13:22
*** peristeri has joined #openstack-meeting-313:24
*** openstackstatus has quit IRC13:25
*** openstackstatus has joined #openstack-meeting-313:26
*** ChanServ sets mode: +v openstackstatus13:26
*** lblanchard has joined #openstack-meeting-313:27
*** egafford has joined #openstack-meeting-313:34
*** e0ne is now known as e0ne_13:34
*** JeanBriceCombebi has quit IRC13:35
*** mrunge has quit IRC13:36
*** e0ne_ is now known as e0ne13:37
*** yamahata has joined #openstack-meeting-313:37
*** sigmavirus24_awa is now known as sigmavirus2413:38
*** evgenyf has quit IRC13:39
*** evgenyf has joined #openstack-meeting-313:40
*** JeanBriceCombebi has joined #openstack-meeting-313:42
*** egafford has left #openstack-meeting-313:42
*** elmiko has joined #openstack-meeting-313:44
*** Piet has joined #openstack-meeting-313:48
*** esikachev has joined #openstack-meeting-313:53
*** weiting has joined #openstack-meeting-313:54
*** pino|work has joined #openstack-meeting-313:56
*** jschwarz_ has joined #openstack-meeting-313:56
*** Gridnev has joined #openstack-meeting-313:58
*** Nikolay_St has joined #openstack-meeting-313:58
*** crobertsrh has joined #openstack-meeting-313:59
SergeyLukjanovhey sahara folks!14:00
SergeyLukjanov#startmeeting sahara14:00
openstackMeeting started Thu May  7 14:00:09 2015 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
sreshetnyak  hi14:00
*** openstack changes topic to " (Meeting topic: sahara)"14:00
openstackThe meeting name has been set to 'sahara'14:00
crobertsrhhello/14:00
elmikoheyo/14:00
alazarevo/14:00
Gridnevhi14:00
SergeyLukjanov#link https://wiki.openstack.org/wiki/Meetings/SaharaAgenda14:00
weitingo/14:00
SergeyLukjanov#link https://libertydesignsummit.sched.org/?s=sahara14:00
*** kchen has joined #openstack-meeting-314:00
SergeyLukjanov#topic sahara@horizon status (crobertsrh, NikitaKonovalov)14:01
*** openstack changes topic to "sahara@horizon status (crobertsrh, NikitaKonovalov) (Meeting topic: sahara)"14:01
SergeyLukjanov#link https://etherpad.openstack.org/p/sahara-reviews-in-horizon14:01
SergeyLukjanovfolks, please14:01
*** wojdev has quit IRC14:01
crobertsrhNot much to report from me.  I've been mostly looking at a few other things.  I should update the review sheet though.14:01
*** huichun has joined #openstack-meeting-314:01
*** jschwarz_ has left #openstack-meeting-314:01
NikitaKonovalovcrobertsrh: I've already moved some merged patches to the merged section14:01
*** yapeng has joined #openstack-meeting-314:02
crobertsrhthanks14:02
SergeyLukjanovokay, thx folks14:02
NikitaKonovalovstill not much attention to event-log change still14:02
SergeyLukjanovso, let's move on14:02
*** sarob has quit IRC14:02
kchenI am working on cdh plugin 5.4 version, trying to add unit test case.14:02
SergeyLukjanov#topic News / updates14:02
*** openstack changes topic to "News / updates (Meeting topic: sahara)"14:02
SergeyLukjanovNikitaKonovalov, that's sad14:02
crobertsrhI'll see if I can get attention to it during the next horizon meeting14:02
huichunI am working on scheduled edp jobs14:03
SergeyLukjanovNikitaKonovalov, it should be pushed till l1 hopefully14:03
NikitaKonovalovSergeyLukjanov: I'll ping horizon team again14:03
elmikoi've been working on a prototype for the castellan integration. also doing some internal work on hadoop secure mode, and more prep work on the summit session pads.14:03
*** nkrinner has quit IRC14:04
*** amuller has joined #openstack-meeting-314:04
kchenToday I met some bugs on horizon on my devstack. I am not sure whether some recent changes caused them.14:04
sreshetnyakNo updates from me14:05
NikitaKonovalovkchen: are those bugs in Sahara panels?14:05
crobertsrhkchen: someone was in the horizon room late yesterday with some devstack issues.  Hopefully, they are being fixed.  You might want to check to see if a bug was opened or not.14:05
kchenyes14:05
elmikokchen: is that the same issue li,chen brought up on the mailing list?14:05
huichunsreshetnyak: hi , are you working on the HA on CDH and HDP?14:05
crobertsrhI was also having trouble uploading an image via the UI yesterday.  Possibly related.14:06
kchenyes14:06
alazarevI tried to get managed and floating IP from heat outputs, but it looks that it is impossible in heat now. The only option is to put entire "addresses" attribute as output, but it is not better than neutron call.14:06
Nikolay_StI update the healthcheck spec and write some UT to improve coverage14:06
sreshetnyakhuichun, hi, i started working on HA in HDP plugin14:06
*** fallenpegasus has joined #openstack-meeting-314:07
huichunsreshetnyak: do you have any spec about HA?14:08
sreshetnyakhuichun, no, i don't have specs14:09
*** egafford has joined #openstack-meeting-314:10
alazarevsreshetnyak, shouldn't HDP be upgraded first?14:10
*** tellesnobrega has joined #openstack-meeting-314:11
*** devvesa has joined #openstack-meeting-314:11
*** tmckay has joined #openstack-meeting-314:12
sreshetnyakalazarev, yes, i created blueprint for it14:12
sreshetnyak#link https://blueprints.launchpad.net/sahara/+spec/hdp-22-support14:12
tmckay\o/14:12
*** btully has joined #openstack-meeting-314:12
Nikolay_Sttmckay: o/14:12
tmckayare we on updates?14:13
elmikoyea14:13
* tmckay should look at eavesdrop14:13
sreshetnyakalazarev, also i created etherpad with plans on HDP and HA14:13
sreshetnyak#link https://etherpad.openstack.org/p/sahara-hdp-ha14:14
*** jcoufal has quit IRC14:14
alazarevsreshetnyak, ok, thanks14:14
tmckayokay, for me, I am looking into JSON null validation in our schemas, so that for instance you can update a node group template with a "null" for an optional field that has previously been set.  Only way to "unset" a field (currently there is none).  This came up as part of default templates.14:14
*** jrist has quit IRC14:14
tmckaysimple for simple stuff -- ["null", "integer"] for a nullable int14:15
*** wojdev has joined #openstack-meeting-314:15
tmckaybut, hard for complicated stuff (like arrays of things).  I haven't quite figured out how to change that yet, docs are only a little helpful14:15
tmckayplus, if folks have done work with Sahara+Ironic I would love to hear about it.14:16
SergeyLukjanovtmckay, oh, after reading your message 3 times I understand the issue - how to unset values :(14:16
*** absubram has joined #openstack-meeting-314:16
tmckaySergeyLukjanov, yes! :)14:17
crobertsrhI just added a blueprint to add template editing to the CLI (was missed for kilo).  I'll start work on that soon.14:17
tmckaySergeyLukjanov, current unset is "delete and recreate" :)14:17
SergeyLukjanovtmckay, we have it's working - Ironic exposed as a hypervisor in nova with dedicated flavors + dib could build special images and it's working ok14:17
SergeyLukjanovtmckay, yup :)14:18
tmckayor hook into sqlalchemy directly :-D without validation by Sahara14:18
SergeyLukjanovtmckay, NikitaKonovalov will write up a blog post on Ironic integration stuff in a next few weeks14:18
tmckaySergeyLukjanov, awesome, any Sahara commits necessary to make it work?14:18
tmckayok, sounds good14:18
SergeyLukjanovtmckay, as I remember there is only one issue - Ironic doesn't mount attached HDDs, so, we'll need to handle it somehow14:19
NikitaKonovalovtmckay: looks like not much, sahara works as is, the special images are required however14:19
tmckayso maybe commits to sahara-image-elements?14:20
SergeyLukjanovtmckay, it's not clear right now - probably yes or on the sahara side14:20
huichunSergeyLukjanov:  you are working on the ironic integration with Sahara? provision cluster on bare metal?14:20
tmckayokay, thanks14:20
SergeyLukjanov#topic Open discussion14:20
*** openstack changes topic to "Open discussion (Meeting topic: sahara)"14:20
SergeyLukjanovhuichun, yup14:21
crobertsrhIs there an etherpad for the summit sessions yet?14:21
tmckayI think interest in this is growing ^^14:21
tmckay(ironic I mean, not etherpads :) )14:21
SergeyLukjanovhuichun, our plan is to make it fully working in the next mirantis openstack release (Kilo based)14:21
*** baoli has quit IRC14:22
SergeyLukjanovcrobertsrh, the proposals etherpad could be used so far14:22
crobertsrhOk14:22
SergeyLukjanovcrobertsrh, I'm planning to create per-session etherpads early next week14:22
crobertsrhSounds good, thanks14:22
huichunSergeyLukjanov:  will not merged into the upstream?14:23
SergeyLukjanovBTW I'll be in California next, anyone there to have some beer?14:23
elmikoi see a bunch of work going on with keystone session objects, any plans for us to switch from using keystone clients to sessions for all of sahara?14:23
*** tosky has joined #openstack-meeting-314:23
SergeyLukjanovhuichun, I mean the timeframe, we definitely contribute all the stuff to upstream14:23
*** baoli_ has joined #openstack-meeting-314:23
tmckaySergeyLukjanov, come to the East Coast and we can go to a local brewery ;-)14:24
elmikohehe14:24
SergeyLukjanov(I'll be in California next == next week)14:24
SergeyLukjanovheh14:24
tmckaySergeyLukjanov, I can even get you a visitor badge and a spare cubicle.  Snacks are good.14:24
SergeyLukjanovso, Vancouver breweries discovery will begin in 10 days :)14:25
tmckayI hear Canadians are good at beer14:25
SergeyLukjanovtmckay, yay! (re visitor badge)14:25
tmckaybut maybe that is just in the movies14:25
SergeyLukjanovand yay re good bear ;)14:25
sreshetnyakelmiko, i have patch with keystone session in integration tests #link https://review.openstack.org/#/c/169295/14:25
SergeyLukjanovI hope it's not only in movies14:25
elmikosreshetnyak: yea, i saw that. i'm kinda wondering about sahara itself switching to use sessions, they seem the way of the future.14:26
SergeyLukjanovelmiko, ++14:26
*** jrist has joined #openstack-meeting-314:26
elmikodoes this need a spec or will a bug be sufficient?14:26
tmckayspeaking of way of the future, I need to check in to the glance work on artifacts for openstack services14:26
tmckayI haven't looked at it since Paris, they were working hard on it at that time14:27
tmckayWe could potentially migrate all kinds of stuff out of Sahara db14:27
*** jcoufal has joined #openstack-meeting-314:27
sreshetnyakelmiko, only swift doesn't supports keystone sessions :(14:27
elmikosreshetnyak: yea, but we can get an auth token from a session, so we should be able to satisfy swift.14:28
SergeyLukjanovtmckay, I'm unsure but it's probably not yet fully merged ;(14:28
elmikoso, if i want to explore making sahara use sessions would we want a spec to go along with that?14:29
tmckayoh, egafford, anything to report on hdp 2 image problems?14:29
tmckayor not sure yet?14:29
SergeyLukjanovelmiko, sreshetnyak I think we need a spec to make a migration to sessions clear14:29
elmikoSergeyLukjanov: ok, thanks.14:29
elmikosreshetnyak: is this something you are interested in as well?14:30
*** shwetaap has joined #openstack-meeting-314:30
egaffordtmckay: Nothing yet, I fear. Context: I'm working on some internal work around HDP image generation, and I'm seeing a reasonably persistent error in the install process across several different Kilo-based installations. I'll keep folks posted as I learn anything more definite.14:30
sreshetnyakelmiko, yes14:31
elmikosreshetnyak: ok, if i draft up a spec i can add you as a co-assignee?14:31
tmckaymaybe possible something is wrong in DIB for hdp images on sahara trunk, if anyone else sees problems installing services please shout14:32
* tmckay hasn't tried yet14:32
crobertsrhI haven't tried in awhile, I can give it a go14:32
sreshetnyakelmiko, yes, i have ideas about sessions14:33
*** wojdev has quit IRC14:33
elmikosreshetnyak: should i wait on creating a spec, maybe we can talk more after the meeting?14:34
*** esp has left #openstack-meeting-314:35
SergeyLukjanovany other topics to chat about today?14:36
*** Gridnev has quit IRC14:37
sreshetnyakelmiko, i think i will add ideas on spec review :)14:37
elmikosreshetnyak: excellent!14:37
*** Gridnev has joined #openstack-meeting-314:37
SergeyLukjanovclosing meeting in 2 mins14:38
*** mattfarina has joined #openstack-meeting-314:39
SergeyLukjanov thanks folks!14:41
SergeyLukjanov#endmeeting14:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:41
openstackMeeting ended Thu May  7 14:41:06 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:41
kchenbye14:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-05-07-14.00.html14:41
elmikothanks SergeyLukjanov14:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-05-07-14.00.txt14:41
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-05-07-14.00.log.html14:41
*** emagana has joined #openstack-meeting-314:41
*** crobertsrh has left #openstack-meeting-314:43
*** tosky has left #openstack-meeting-314:43
*** kchen has quit IRC14:44
*** pino|work has left #openstack-meeting-314:45
*** vikram__ has joined #openstack-meeting-314:47
*** david-lyle has joined #openstack-meeting-314:49
*** Rui_Zang has joined #openstack-meeting-314:50
*** carl_baldwin has joined #openstack-meeting-314:51
*** tidwellr has joined #openstack-meeting-314:55
*** egafford has left #openstack-meeting-314:55
*** johnbelamaric has joined #openstack-meeting-314:57
*** saggi1 has joined #openstack-meeting-314:58
*** yamahata has quit IRC14:59
*** baoli_ has quit IRC14:59
*** mattgriffin has joined #openstack-meeting-314:59
*** yamahata has joined #openstack-meeting-314:59
*** mlavalle has joined #openstack-meeting-315:00
carl_baldwinhi15:00
mlavallehi15:00
pavel_bondarhi15:00
Rui_Zanghi15:00
HenryGhi15:00
*** baoli has joined #openstack-meeting-315:00
*** yalie has joined #openstack-meeting-315:00
haleybhi15:00
vikram__hi15:00
saggi1ho15:00
carl_baldwin#startmeeting neutron_l315:00
tidwellrhi15:00
openstackMeeting started Thu May  7 15:00:40 2015 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:00
openstackThe meeting name has been set to 'neutron_l3'15:00
johnbelamarichi15:00
carl_baldwin#topic Announcements15:00
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:00
yamahatahello15:00
yaliehi15:01
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:01
devvesaHi15:01
*** pc_m has joined #openstack-meeting-315:01
carl_baldwinI don’t think I have any announcements.  Anyone?15:01
carl_baldwinI think we all know about summit coming up.15:01
HenryGI have one15:02
*** jcoufal has quit IRC15:02
carl_baldwinHenryG: go15:02
HenryGAn updated wiki for IPv6 has been created15:02
HenryGhttps://wiki.openstack.org/wiki/NEUTRON-IPV6-MANUAL15:02
*** wojdev has joined #openstack-meeting-315:03
HenryGPlease read and review. Anyone can edit and improve it.15:03
HenryGIt can be used as seed information for real docs.15:03
carl_baldwinHenryG: Great.  We’ll link it from the subteam page.15:03
*** wojdev has quit IRC15:03
carl_baldwinmlavalle: ^15:03
devvesa615:04
mlavallecarl_baldwin: ok, will take care of it15:04
carl_baldwinHenryG: Looks like it covers a lot.15:04
mlavalleHenryG: I just glanced over it and looks very good. Thanks for sharing15:04
HenryGYes, it has input from a lot of people who worked on the features15:05
sc68calo/15:05
carl_baldwinI’m sure it represents a lot of good work from a lot of contributors.15:05
HenryGsc68cal: Hi, see the wiki mentioned ^^15:05
* mlavalle kenw sc68cal was involved15:05
carl_baldwinAny other announcements?15:06
sc68calHenryG: ok, we should probably convert that wiki page into an RST doc and push a patch into openstack-manuals in the networking guide space15:06
carl_baldwinsc68cal: +115:07
HenryGsc68cal: yes, it was just a place to collect information as a start15:07
* carl_baldwin was just going to say the wiki can be a good place to start collecting information.15:07
*** salv-orlando has quit IRC15:08
carl_baldwinBTW, welcome to the IPv6 contributors.  A lot of good stuff was done in Kilo and I’m excited for what’s coming in Liberty.15:08
sc68calHenryG: is there a more specific URL than just cisco.com that this came from?15:08
*** dboik_ has joined #openstack-meeting-315:09
*** mwagner_lap has quit IRC15:10
carl_baldwin#topic bgp-dynamic-routing15:10
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:10
carl_baldwin#undo15:10
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x9198490>15:10
carl_baldwin#topic Summit15:10
*** openstack changes topic to "Summit (Meeting topic: neutron_l3)"15:10
carl_baldwinI wanted to use some time to start planning for summit.15:11
carl_baldwin#link https://www.google.com/url?q=https%3A%2F%2Fwiki.openstack.org%2Fwiki%2FSummit%2FLiberty%2FEtherpads%23Neutron&sa=D&sntz=1&usg=AFQjCNHhzpV5savYHInbQ92GaSfMMT100w15:11
* carl_baldwin gets a more direct link.15:12
*** tmckay has quit IRC15:12
carl_baldwin# link https://wiki.openstack.org/wiki/Summit/Liberty/Etherpads#Neutron15:12
carl_baldwinThat’s better.15:12
carl_baldwinOn Thursday at 9:50 is a Neutron L3 session.  I’d like to poll the team for ideas about how to best use this time.15:13
carl_baldwinThere is also the Friday “Contributor meetup”  which we can make use of.15:14
carl_baldwinSo, thoughts?15:14
*** esikachev has quit IRC15:15
devvesaI'm agree on discussing on what's already in the Etherpad15:15
devvesaI haven't read yet Vikram's proposal, but if there is a way to define a generic dynamic routing, maybe it is the best moment15:15
vikram__I want to include the general routing framework "https://review.openstack.org/#/c/180987/"15:15
*** bpokorny has joined #openstack-meeting-315:16
*** alex_xu has joined #openstack-meeting-315:16
carl_baldwinOkay, it is noted on the etherpad.  I’ll probably include it somewhere near the end of the session.  I fear that it could dominate the entire session otherwise.15:17
*** pcarver_ has joined #openstack-meeting-315:17
*** Swami has joined #openstack-meeting-315:17
devvesaWise15:18
carl_baldwinI also think that a smaller group could get together during the contributor meetups on Friday might be a good place to discuss it.15:18
*** asadoughi has joined #openstack-meeting-315:18
vikram__thanks carl15:18
carl_baldwinI would like to talk about the address scope blueprint:  https://review.openstack.org/#/c/180267/15:18
tidwellr+115:18
johnbelamaric+115:19
vikram__+115:19
Swami+115:19
yamahataI want to include ML315:19
Rui_Zang+115:20
carl_baldwinyamahata: Could you add a note and some links to the etherpad?15:20
yamahatahttps://review.openstack.org/#/c/105078/15:21
yamahataIt was proposed for Kilo15:21
*** weiting has quit IRC15:21
yalie+115:21
yamahataI'll restore and update it soon15:21
carl_baldwinyamahata: thanks.15:21
carl_baldwinIn the context of address scopes, talk about how this fits in with dynamic routing, l3 vpn, and IPAM.15:22
carl_baldwinAny other thoughts?15:23
carl_baldwin#link https://etherpad.openstack.org/p/YVR-neutron-l315:23
johnbelamaricmaybe also external dhcp/relay and recursive DNS?15:24
*** Nikolay_St has quit IRC15:24
johnbelamaricNot sure that is of interest to the whole group :)15:24
yamahataWhat about distributed dhcp?15:24
vikram__i feel this is important for taking the idea of L3VPN inside.15:25
Swamialso service-chaining15:26
carl_baldwinjohnbelamaric: The designate team has just reached out to me.  The would like to discuss some things in this area in their working session on Thursday at 1:30.15:27
johnbelamariccarl_baldwin: great, sounds good. I saw the email from Kiall15:27
carl_baldwinThanks for the ideas.  Be sure to add them to the etherpad with your irc nick and I’ll be working on the agenda.15:27
carl_baldwinjohnbelamaric: Good, I wasn’t sure how broadly he sent it.15:28
carl_baldwin#topic bgp-dynamic-routing15:28
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:28
carl_baldwindevvesa: tidwellr:  How are things going here?  Last I knew, there was a nasty rebase coming and we had some quagga running.15:29
johnbelamariccarl_baldwin: I meant the comment on the code review, I didn't have the time. I'll put it on my plan. Thanks!15:29
devvesaStill like this. I haven't had time to rebase it15:29
devvesaBut I am concerned how are we going to handle all of this15:30
devvesaI mean, if there is a 'generic dynamic routing' coming15:30
devvesaand I think ML3 using dynamic routing as l3 plugin is also something to consider15:30
carl_baldwindevvesa: I think the generic dynamic routing will be a good thing but I’m also concerned about it hindering development that is already going on.15:31
*** scheuran has quit IRC15:31
devvesaSo we go on with we had before15:31
vikram__devessa: my idea of generic routing won't require much changes to your current propopsal15:32
devvesaWhat about the spec? There is a new Feature Request proposal workflow15:32
devvesa#link https://review.openstack.org/#/c/177342/15:33
tidwellrdevvesa: are you going to take on a rebase of your earlier work?15:33
devvesaIf you think that's the way to follow, yes15:33
carl_baldwindevvesa: Keep the spec for now.  When the spec review process officially changes (i.e. the policy document merges) we’ll create a feature request following the policy.15:34
carl_baldwinThen, I guess the spec will need to be morphed in to devref document.15:34
devvesaOk15:35
devvesaSo, I'll rebase the patch15:35
*** marun has joined #openstack-meeting-315:35
carl_baldwindevvesa: I think that will be good progress.15:36
devvesaOk15:36
tidwellrI'd like to deploy it and play with that patch15:36
devvesaActually it were three patches. One with the entities/api15:37
devvesaAnother one with agent scheduling15:37
tidwellrdevessa: right, I'd like to try out all 3 :)15:37
carl_baldwinCool, so I think we have a plan.15:38
carl_baldwinAnything else for bgp?15:38
devvesaJust announce that Vikram may take care of rebase/implement the other 215:38
devvesaAs he kindly offered himself15:39
*** kozhukalov has joined #openstack-meeting-315:39
carl_baldwinThank you vikram__ .  Please feel free to ask tidwellr or /me for assistance.15:39
vikram__devvesa: +115:40
carl_baldwin#topic neutron-ipam15:40
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:40
vikram__sure. i will15:40
*** nelsnelson has joined #openstack-meeting-315:40
pavel_bondarwe have clean test pass for all 3 patches15:40
pavel_bondar#link https://review.openstack.org/#/c/153236/15:41
carl_baldwinpavel_bondar: That is great!15:41
amullercarl_baldwin: it looks like specs will remain15:41
amullercarl_baldwin: in their current form, maybe a thinner template15:41
pavel_bondarafter I have changed default to non-IPAM15:41
amullerwe'll see...15:41
pavel_bondarand created new dependent review to run IPAM implementation15:41
carl_baldwinamuller: I saw a note going that direction but I wanted to wait to see what merges.15:41
carl_baldwinpavel_bondar: I saw that15:42
carl_baldwin#link https://review.openstack.org/#/c/181023/15:42
pavel_bondarI expect only check-grenade-dsvm-neutron should fail in #181023, due to absence of migration to IPAM15:44
carl_baldwinpavel_bondar: The grenade test was the only thing remaining.  I think that is great progress and we — as reviewers — owe you some reviews.15:44
*** zhenguo has quit IRC15:44
carl_baldwinpavel_bondar: I will review again today.15:44
pavel_bondarcarl_baldwin: Thanks!15:45
*** cdent has joined #openstack-meeting-315:45
pavel_bondara few things left to do in reference driver #15048515:46
*** Aish has joined #openstack-meeting-315:46
carl_baldwinI encourage others to review too.15:46
pavel_bondarlike unit tests and auto_addressed subnet question15:46
pavel_bondarI am working on that in #15048515:46
johnbelamaricpavel_bondar, carl_baldwin: I will go through it again as well15:47
carl_baldwinpavel_bondar: I haven’t visited that review in a few days.  What is left?15:47
*** JeanBriceCombebi has quit IRC15:47
carl_baldwinI will take another look today.15:48
pavel_bondarfor reference driver it is mostly several UT that left to do and auto_addressing15:49
pavel_bondar#link https://review.openstack.org/#/c/150485/19/neutron/ipam/drivers/neutrondb_ipam/driver.py15:49
carl_baldwinpavel_bondar: Right, auto_addressing.  Thanks for taking care of those items.15:50
*** mattfarina has quit IRC15:51
*** Aish has quit IRC15:51
pavel_bondarSo solution for auto_addressing will be detecting auto_addressed subnet by ip(is_eui64), or it is still on-going discussion?15:51
carl_baldwinAnything else?15:51
*** Aish has joined #openstack-meeting-315:52
johnbelamaricpavel_bondar: the ongoing discussion is around whether we inform IPAM of auto-assigned addresses (that are not link-local)15:52
*** Aish has quit IRC15:52
* carl_baldwin is having deja vu15:53
*** matrohon has quit IRC15:53
pavel_bondarjohnbelamaric: ok, so I'll wait discussion results on this topic15:53
*** btully has quit IRC15:54
carl_baldwinI tend to think that Neutron should still call IPAM and IPAM can choose what to do.15:54
*** Aish has joined #openstack-meeting-315:55
*** Aish has quit IRC15:55
johnbelamariccarl_baldwin: agreed, then we need to decide whether IPAM can reject the auto-assigned addressing or not. If not, we may want a separate "inform" vs. "allocate" call.15:55
*** dtroyer has joined #openstack-meeting-315:56
johnbelamariccarl_baldwin: I see a need for visibility in IPAM (for external IPAM) to auto-assigned addresses but not rejection15:56
carl_baldwinjohnbelamaric: Interesting.15:57
johnbelamariccarl_baldwin: but either way is fine by me - I just want to be sure we have the visibility into those addresses when they are assigned (particularly ULA) - though frankly for auto-assigned that is a nice-to-have and not critical15:58
*** stevelle has joined #openstack-meeting-315:59
*** saggi1 has quit IRC16:00
carl_baldwinLooking at it from an API perspective, I think it is good to give the IPAM system an opportunity to see the allocation even if it is automatic.  From the reference implementation perspective, I think it is fine to just ignore it.  That is just my opion though.  I’ll add a comment to the review.16:00
*** mwagner_lap has joined #openstack-meeting-316:00
etoewsis the neutron meeting done?16:00
carl_baldwinWe should find a way to converge on a decision for this soon.16:00
carl_baldwinetoews: thanks.  We’ll end now.16:00
carl_baldwin#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu May  7 16:00:49 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-05-07-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-05-07-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-05-07-15.00.log.html16:00
etoewssorry to barge in and all that16:01
etoews#startmeeting api wg16:01
*** pc_m has left #openstack-meeting-316:01
openstackMeeting started Thu May  7 16:01:08 2015 UTC and is due to finish in 60 minutes.  The chair is etoews. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: api wg)"16:01
openstackThe meeting name has been set to 'api_wg'16:01
elmikoyo/16:01
vikram__bye16:01
etoewssound off if you're here for api wg16:01
cdento/16:01
alex_xuo/16:01
*** johnbelamaric has left #openstack-meeting-316:01
stevelleo/16:01
etoewswelcome alex_xu!16:01
*** devvesa has quit IRC16:01
*** amuller has left #openstack-meeting-316:01
alex_xuetoews: thanks :)16:02
*** vikram__ has left #openstack-meeting-316:02
*** tidwellr has left #openstack-meeting-316:02
miguelgrinberghi16:02
dtroyero/16:02
etoewsexcellent16:03
*** annegentle has joined #openstack-meeting-316:03
etoews#topic agenda16:03
*** openstack changes topic to "agenda (Meeting topic: api wg)"16:03
etoews#link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda16:03
etoews#topic previous meeting action items16:03
*** openstack changes topic to "previous meeting action items (Meeting topic: api wg)"16:03
etoewshmmm...not the right link in the wiki. 1 sec.16:04
*** dboik_ has quit IRC16:04
jaypipeshi guys, sorry for being late.16:04
etoews#link http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-04-30-00.01.html16:04
etoewsnp16:04
sigmavirus24jaypipes: I'm later =P16:04
jaypipes:)16:05
etoewsi missed last week so i'm the latest there is16:05
elmikoso, i put the evaluating api changes up as a guideline for review, #link https://review.openstack.org/#/c/180612/16:05
elmikogetting good comments so far16:05
elmikothat was my action item from 2 weeks ago16:05
etoewsah16:05
elmikoand jaypipes i responded to your comments =)16:06
etoewsi haven't had a chance to look at that one yet. thx for getting to it.16:06
elmikonp, i hope it ends up working out16:06
*** Rui_Zang has quit IRC16:06
krotschecko/16:06
annegentleI like the move towards microversion rather than extension16:07
etoewsyep. the knives are out for extensions.16:07
elmikoi will change the language to mention microversions instead of extensions in the next version, i wanted to leave it open for more comments before revising though.16:08
etoewsmakes sense16:08
annegentleso, I am also commenting inline, but in order to point out inadequate documentation, we need to define adequate.16:08
*** e0ne is now known as e0ne_16:08
annegentleI can take a stab at it if you like I have some ideas/background in this.16:09
*** sarob has joined #openstack-meeting-316:09
elmikosure! any help would be appreciated =)16:09
annegentlewhere would that "adequacy" go?16:09
annegentlein a new guideline?16:09
etoews"some ideas/background in this" ...snort...that's putting it mildly.16:09
*** salv-orlando has joined #openstack-meeting-316:09
*** vhoward has left #openstack-meeting-316:10
annegentleetoews: snort16:10
elmikohmm, would a guideline about creating documentation be appropriate? i'm not sure16:10
*** vhoward has joined #openstack-meeting-316:10
jaypipeselmiko: ty sir! will respond again soon. sorry, meeting day today.16:10
elmikojaypipes: np, you made some great suggestions16:10
*** sahid has quit IRC16:10
annegentleelmiko: I should probably write "these are the current expectations for docs" in an API WG guideline16:10
elmikoannegentle: yea, that makes sense16:11
annegentleelmiko: ok, I'll take that on16:11
etoewsso just to be clear about it. we're saying that api docs are in scope for the api wg.16:12
*** safchain has quit IRC16:12
*** salv-orlando has quit IRC16:12
elmikosounds like it16:12
etoewsor maybe it's recommendations about api docs are in scope?16:12
elmikoi'm more comfortable with that statement16:12
cdentI'd think yeah recommendations16:12
annegentleetoews: guidelines are in scope16:13
etoewsya. and i do think it's something we should have an opinion on.16:13
annegentleetoews: I think. Yeah, recommendations16:13
annegentleetoews: at least to let the WG do reviews16:13
etoewsin the current state of the art, apis and api docs are highly coupled.16:13
annegentleetoews: and I plan to be general, not to the tool level16:13
etoewsannegentle: sgtm16:14
annegentleetoews: cool16:14
elmikothis could have wider impact with the whole autogen doc thingie that going on currently16:14
annegentleelmiko: yeah it really is "while I'm workign with teams on that, might as well write guidelines"16:14
elmikoannegentle: +116:15
etoewsright. we'll have to feel our way through this one.16:15
annegentletrue dat16:15
annegentleI've reached out to the Image team to see if they'd be interested in proof-of-concept. their API is still smallish16:15
annegentlethough it took 7 months to get metadata definitions documented :) https://review.openstack.org/#/c/121248/16:16
etoewsthat's like overnight in openstack time16:16
annegentleetoews: LOL16:16
elmikolol16:16
*** e0ne_ is now known as e0ne16:17
etoewsso we kind of veered into the next topic with these action items.16:17
etoews#topic API Reference information16:17
*** openstack changes topic to "API Reference information (Meeting topic: api wg)"16:17
annegentleya!16:17
annegentle#link http://libertydesignsummit.sched.org/event/29e7d4effc10832b4d6aa50339e0c973#.VUuJ6dNViko16:17
etoews#link https://review.openstack.org/#/c/177934/16:17
annegentlethat's the session also, didn't get that added to the agenda16:17
annegentle(in time)16:17
*** fallenpegasus has quit IRC16:18
annegentleSo I'm making progress and drafted again, also had a question from Celiometer dev ildiko about openstack versions v microversions16:18
annegentle#link http://lists.openstack.org/pipermail/openstack-docs/2015-May/006560.html16:18
annegentleSo I wanted to ask here: does it make sense to "lag" the OpenStack release with Dev Guides targeted for a particular release?16:19
annegentleAs in, now we'd work on a Dev Guide for Kilo16:19
etoewswhat's in scope for "dev guides"16:19
annegentleSo, the idea is to scrape code ONLY for params, errors, headers, and put that info into a Swagger 2.0 spec. Then build Dev Guides around that API ref info -- so that the experience feels like crafted docs, not roboted docs.16:20
annegentleThe vision is a nicer information experience for developer.openstack.org rather than "just" an API reference.16:21
elmikothat sounds cool16:21
annegentleis that amenable? I share etoews concerns about utter crappiness.16:21
annegentleas in, any time you automate it sucks for the user.16:21
elmikoand yeah, i think doing it for kilo makes some amount of sense16:22
annegentlemoving the reviews to the teams and hand-in-hand with WG guidelines for docs feels like it's the right direction.16:22
etoewsalso relevant #link http://lists.openstack.org/pipermail/openstack-docs/2015-April/006502.html16:22
annegentlethe only part that gives me pause is that we'd be backporting strings to stable/kilo potentially... across multiple repos.16:22
elmikoalthough, i also like the idea of the projects being able to autogen some part of the doc for themselves16:22
annegentleIt's scary right.16:22
annegentleAlso, check out this automation starting point16:23
annegentle#link https://review.openstack.org/#/c/179051/16:23
annegentleI really need eyes on that ^^ as a potential solution16:23
annegentlefor the scrape16:23
annegentleand generate16:23
etoewsannegentle: so that patch uses some python to generate swagger from the python api source code?16:25
annegentleheh I gave you all too much to read16:25
annegentleetoews: yes16:25
elmikoannegentle: i looked at that the other day, would the idea be that each project provides a function that will get called by external tools?16:25
*** woodster_ has joined #openstack-meeting-316:26
annegentleelmiko: possibly in oslo like we do for the configuration reference currently16:26
elmikoannegentle: cool, that's nice16:26
cdentThere was some discussion a while ago about being able to pecan -> swagger and it faltered becasue pecan makes it rather hard16:26
annegentlecdent: yeah16:26
annegentlecdent: I want to say ceilometer does pecan > WADL now16:26
elmikocdent: i did some work on a markup package to generate swagger from pecan16:26
cdentI think it's generally a good idea and if it drives us to use more readable frameworks then  all the better16:26
annegentleelmiko: how'd that go? say more. :)16:27
etoewsand if this works reasonably well in nailgun (whatever that is) it could potentially be rolled out to other projects via oslo?16:27
elmiko#link https://github.com/elmiko/pecan-swagger16:27
cdentelmiko: yeah, I think that's what I'm remembering. You were unable to do it by inspection though, right?16:27
annegentleetoews: maybe? Stackforge licensing doesn't exactly make it straightforward but I'm investigating16:27
elmikoit's a poc currently, but you need to add a little markup to the controller classes to help inform the hierarchy for swagger16:27
annegentleetoews: I need to talk to a few people16:27
annegentleelmiko: how many projects use pecan now?16:27
elmikocdent: correct, pecan doesn't carry any information about the ordering of it's controllers16:27
elmikoannegentle: not sure on exact numbers, but i know of 216:28
annegentleelmiko: ok, ceilometer and which?16:28
elmikobarbican16:28
annegentle(I have a hard stop in 2 mins)16:28
annegentleok16:28
annegentleI'm really wanting to get it right for "core compute" first tbh16:28
annegentlehave to prioritize16:28
etoewsannegentle: so what are the action items here before you go?16:29
elmikoi did a test for barbican swagger and sahara swagger in #link https://github.com/elmiko/os-swagger-docs16:29
cdentmonty posted a list of all the pecan using projects to os-dev recently16:29
annegentlecdent: yeah16:29
etoewssame as last week. ;)16:29
annegentleaug, sorry I have to get going :)16:29
etoewsnp16:29
annegentlethanks everyone16:29
* cdent wave16:29
cdents16:29
annegentlesee you in Vancouver :)16:29
elmikoannegentle: later16:29
*** shakamunyi has quit IRC16:29
etoewssee you16:29
etoews#action all: comment on https://review.openstack.org/#/c/177934/16:30
etoews#action all: comment on https://review.openstack.org/#/c/179051/16:30
etoewsi'm less sure about that one ^16:30
elmikoi like the idea of each project having a standard entry point that some external tool can use to harvest the swagger16:31
*** alexsyip has joined #openstack-meeting-316:31
etoewsyes. machine readable api doc would be nice.16:32
etoewslots of good use cases for that.16:32
etoews#topic summit sessions galore16:32
*** openstack changes topic to "summit sessions galore (Meeting topic: api wg)"16:32
etoews#link https://libertydesignsummit.sched.org/event/e14d84514003140fe30e984027299a4416:32
etoews#link https://openstacksummitmay2015vancouver.sched.org/event/c61ab30c4547a6c70612017e43cd607616:32
etoews#link https://openstacksummitmay2015vancouver.sched.org/event/0b86e7b3b74c44705d46dc1694272d6316:32
etoewsso we hit the jackpot on summit sessions. we'll be a busy bunch. i suppose that's a good problem to have.16:33
elmikolol, so many sched conflicts16:34
cdentthis must be a huge convention center, lots of people have surplus sessions16:34
etoewsi'd ask that everybody make a real effort to at least get to https://libertydesignsummit.sched.org/event/e14d84514003140fe30e984027299a4416:34
etoewsthat will be the most high profile session16:34
etoewsi'll do my best to do a good "where we were, where we are, and where we're going" but naturally i'll need help16:35
*** emagana has quit IRC16:35
elmikonice16:35
etoewsthen the other 2 sessions i see as being working sessions for us16:36
etoewsif we can actually get some work done, great. if not, that's okay too.16:36
etoewsdoes anybody want to highlight any other api wg related sessions at the summit?16:37
elmikomaybe we can arg^H^H^Hdiscuss some of the open reviews ;)16:37
etoewselmiko: exactly16:37
cdentdefine: API16:37
cdentand fight16:37
elmikolol16:37
etoews:troll:16:37
cdent:)16:38
etoewsdefine: pragmatic16:38
elmikoouch...16:38
cdentsnap!16:38
etoewscdent: oh great. now you've got me doing it.16:38
cdentactually you and dkranz's comments on that thread yesterday helped clarify or explain some cognitive dissonance I've been experiencing in some of my api-wg interactions16:39
etoewsmiguelgrinberg and i are doing a api wg related session #link http://libertydesignsummit.sched.org/event/602a2acdca6f546cef89dc0c4356e3d8#.VUuVL9pViko16:39
*** annegentle has quit IRC16:39
etoewscdent: say more16:39
elmikoetoews: that one looks cool16:39
cdentjaypipes and I have this: https://libertydesignsummit.sched.org/event/bf6f86afe58148a96ab9d1dd0d30a55416:40
elmikocdent: that looked nice too16:40
cdentI'll be demo-ing gabbi which makes life easier16:40
jaypipeswhich I still owe cdent slides on... coming soon! damn $work16:40
*** rushiagr_away is now known as rushiagr16:40
etoewsha! i owe miguelgrinberg slides16:40
cdentetoews: on the cognitive dissonance? I had thought that a notional API already exists sort of in the ether and we were intentionally trying to create resource oriented http apis (and guidelines for such things)16:41
miguelgrinbergetoews: we can wing it :)16:41
cdentthe comments made it clear that at least some people have a different approach (which is expected and fine, I just hadn't crystallized the difference)16:41
etoewscdent: ah16:42
etoewscdent: i also really liked your response to "Changing 403 Forbidden to 400" on os-dev16:42
*** emagana has joined #openstack-meeting-316:42
etoews(╯°□°)╯︵ ┻━┻16:42
elmikoyea, that post definitely made me more confused about which was more correct lol16:42
elmikoetoews: yes!16:42
cdentwe looked around and it seems that 403 is common out there in web land for such things16:43
cdentbut that doesn't really address the underlying issue about dealing with ambiguity16:43
cdentwhich is a _hard_ problem16:43
etoewscdent: i know what elmiko means. the email could have used a "and i recommend X in particular"16:43
cdentYou didn't take away that I still think 403 is right?16:43
*** yalie has quit IRC16:44
elmikocdent: i did. but i was starting to think 400 sounded proper, then you blew me out of the water. now i'm not sure16:44
etoewsthat was my impression but it wasn't stated explicitly...or was it?16:44
*** mwang2_ has joined #openstack-meeting-316:44
etoewslet's move on in a minute16:45
elmikoi do like the idea of being able to have better categorization using the 4XX codes16:45
elmikoetoews: cool, i have a guideline related topic too16:45
etoews#topic guidelines16:45
*** openstack changes topic to "guidelines (Meeting topic: api wg)"16:45
elmiko\o/16:45
elmikoso, woodster_ from the barbican team had brought up some questions about proper usage of POST/PUT for doing creation and updating16:46
elmikohave we started a guideline for this yet?16:46
elmikoalso, woodster_ ^^16:46
woodster_elmiko: ha, thanks for bring that up16:46
elmiko;)16:46
woodster_I hadn't seen guidance on the proper usage of POST vs PUT16:46
cdentthis is another one of those topics with years of discussion and rules of thumb that seem to move around a lot16:47
elmikoi thought the prevailing guidance was use POST for creation PUT for update, but apparently keystone has a situation where PUT is used for creation. (did i get that correct woodster_ ?)16:47
woodster_I'd always thought POST was creational, and PUT was replacement. PATCH was a delta change to an existing resource16:47
etoewsright. so let's set the rule of thumb for openstack.16:47
woodster_elmiko: that's correct16:47
elmikoetoews: please =)16:47
cdentthe rule of thumb I use is: if you are creating and you don't know already what the resulting URI is, they you POST16:48
cdentotherwise you PUT16:48
miguelgrinberg+1 that's how I do it16:48
cdentso for the vast majority of situations in openstack I would think POST for create because id's are generated on the backend16:48
elmikocdent: that was my thinking as well16:48
dstanekcdent: yes16:48
etoews++16:48
stevellemy rule is a little different from what cdent stated16:49
dstaneki think the case if Keystone you are talking about we knows the uri and don't care if something is there or not16:49
cdentwow, that was easier than expected :)16:49
stevellemostly the same result but different point of inflection16:49
miguelgrinbergdstanek: that was the one that changes the password for an existing user, correct?16:49
krotscheckWell, can I ask a followup question?16:49
etoewsof course16:50
woodster_miguelgrinberg: I believe so16:50
dstanekmiguelgrinberg: i was thinking about some of the assignment stuff - i'd have to look at password16:50
krotscheckSo let's say you POST to create a thing, is the appropriate response either a 201, or a 300 Here's-where-the-thing-with-the-new-id is?16:50
cdent201 with a location header16:50
etoewsthat we have a guideline for!16:50
krotscheckOh good!16:50
* krotscheck goes away now :)16:50
elmikosounds like we need an action item for a POST/PUT guideline?16:50
*** eghobo has joined #openstack-meeting-316:51
etoewskrotscheck: #link http://specs.openstack.org/openstack/api-wg/guidelines/http.html#xx-success-codes16:51
cdentI'll take that action if nobody else wants it16:51
miguelgrinbergdstanek: this http://docs.openstack.org/developer/keystone/api_curl_examples.html#post-v3-users-user-id-password16:51
* krotscheck thinks redirect is more "REST pure", but vastly prefers not adding additional HTTP noise.16:51
miguelgrinbergdstanek: it's a pretty odd one, as it requires the old password, even though you must authenticate to have access16:51
elmikocdent: sounds good to me =)16:51
etoewskrotscheck: pragmatic :)16:51
*** bpokorny_ has joined #openstack-meeting-316:51
elmikolol16:52
woodster_so if the URI is known, then a PUT is a better approach?16:52
krotschecketoews: I've written one too many browser clients to be a purist :)16:52
*** Aish has joined #openstack-meeting-316:52
stevelleif your representation is complete and accurate, including the URI then PUT is correct16:52
etoews#action cdent: create a POST/PUT guideline16:52
cdentkrotscheck: the problem with a redirect is that browers (inc js in browsers) will follow the redirect and the vast amount of time you dont' want to16:52
cdentthanks etoews16:52
stevelleany generated properties would recommend POST, not just ID16:53
dstanekmiguelgrinberg: ah yes, that's a post because we are not actually replacing a resource, but rather doing some processing16:53
etoewscdent: i'm not sure if it's a totally new guideline and should use elmiko's template #link http://specs.openstack.org/openstack/api-wg/template.html or if it's an update to an existing page.16:53
woodster_We have added access control lists to our entities, so we would expose a resource like this to modify the ACL (for example): /secrets/{UUID}/acl   Then it sounds like we can just PUT to that URI16:54
etoewsmaybe it depends in part on how complicated/hairy it gets16:54
elmikowoodster_: +116:54
cdentI'll adapt and be pragmatic etoews ;)16:54
miguelgrinbergwoodster_: you just said it, you are modifying, not creating, so PUT is right16:54
etoews:)16:54
*** pkoniszewski has quit IRC16:54
woodster_nice! Thanks for the guidance then folks16:55
*** bpokorny has quit IRC16:55
etoewswoodster_: thanks for reaching out to us!16:55
etoews5 min left16:55
alex_xujust question, if we have sub-error-code in the future, whether the client still depend on the status code?16:56
etoewsin that case i expect the status code becomes a "top level filter" for clients16:56
miguelgrinbergalex_xu: you would then group the sub-error codes and return them under the parent status code that makes more sense16:57
etoewsthen perhaps some real action can be taken based on the sub-error-code16:57
miguelgrinbergfor example, under 400 you can have an error code for missing arg, another for invalid arg, etc.16:57
etoewsya16:57
etoewsthat's how i see it too16:57
alex_xuah, I see, that sounds make sense, group some process for kind of errors16:58
miguelgrinbergright16:58
etoewsi won't be able to make it to the meeting next week16:58
*** huichun has quit IRC16:58
alex_xumiguelgrinberg etoews, thanks16:59
elmikoetoews: ack, i should be around16:59
etoewsthx elmiko!16:59
elmikoi love the api-wg after hours meetings ;)16:59
etoewsthey seem very relaxed ;)17:00
elmikoheh17:00
etoewssee some/all? of you at the summit!17:00
* cdent looks at the clock17:00
etoews#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Thu May  7 17:00:21 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-05-07-16.01.html17:00
elmikothanks etoews !17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-05-07-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-05-07-16.01.log.html17:00
*** emagana has quit IRC17:00
*** cdent has left #openstack-meeting-317:00
etoewsthanks all17:00
*** emagana has joined #openstack-meeting-317:01
*** elmiko has left #openstack-meeting-317:03
sigmavirus24we're over time, no?17:06
sigmavirus24d'oh17:06
*** iovadia has joined #openstack-meeting-317:07
*** iovadia has quit IRC17:07
*** mwang2_ has left #openstack-meeting-317:08
*** Youcef has joined #openstack-meeting-317:11
*** e0ne has quit IRC17:11
*** yamahata has quit IRC17:14
*** eghobo_ has joined #openstack-meeting-317:15
*** eghobo has quit IRC17:16
*** evgenyf has quit IRC17:16
*** VW_ has quit IRC17:19
*** mattfarina has joined #openstack-meeting-317:20
*** btully has joined #openstack-meeting-317:21
*** VW_ has joined #openstack-meeting-317:21
*** armax has joined #openstack-meeting-317:25
*** yamahata has joined #openstack-meeting-317:40
*** emagana has quit IRC17:40
*** emagana has joined #openstack-meeting-317:43
*** s3wong has joined #openstack-meeting-317:44
*** hemanthravi has joined #openstack-meeting-317:44
*** dtroyer has left #openstack-meeting-317:44
*** Nikolay_St has joined #openstack-meeting-317:45
*** anteaya has quit IRC17:45
*** singlethink has joined #openstack-meeting-317:46
*** emagana has quit IRC17:48
*** Nikolay_St has quit IRC17:50
*** ivar-lazzaro has joined #openstack-meeting-317:53
*** SumitNaiksatam has left #openstack-meeting-317:56
*** rkukura has joined #openstack-meeting-317:59
*** rushiagr is now known as rushiagr_away18:00
*** SumitNaiksatam has joined #openstack-meeting-318:01
SumitNaiksatamrkukura: ivar-lazzaro igordcard_ hemanthravi yapeng: hi18:01
rkukurahi18:01
ivar-lazzarohi18:01
SumitNaiksatams3wong: yamahata: hi18:01
yapenghi18:01
SumitNaiksatam#startmeeting networking_policy18:02
openstackMeeting started Thu May  7 18:02:00 2015 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: networking_policy)"18:02
openstackThe meeting name has been set to 'networking_policy'18:02
s3wonghi18:02
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#May_7th.2C_201518:02
*** bpokorny has joined #openstack-meeting-318:02
SumitNaiksatamanyone have announcemnts to share with the team?18:02
hemanthravihi18:03
SumitNaiksatam#topic Bugs18:03
*** openstack changes topic to "Bugs (Meeting topic: networking_policy)"18:03
SumitNaiksatamivar-lazzaro: is the backport for this done: #link https://bugs.launchpad.net/group-based-policy/+bug/1432779 ?18:03
openstackLaunchpad bug 1432779 in Group Based Policy "redirect actions don't work with external policies" [Critical,In progress] - Assigned to Ivar Lazzaro (mmaleckk)18:03
ivar-lazzaroSumitNaiksatam: checking18:04
SumitNaiksatamivar-lazzaro: i think it is18:04
*** mattfarina has quit IRC18:04
SumitNaiksatam#link https://review.openstack.org/17097218:04
SumitNaiksatamso we can close the bug18:04
*** stevelle has left #openstack-meeting-318:04
ivar-lazzaroSumitNaiksatam: yup18:04
SumitNaiksatami sent unicast emails to a few folks to check the status of the pending critcial and high priority bugs18:05
SumitNaiksatamkindly take note and update the state on launchpad18:05
SumitNaiksatamivar-lazzaro: thanks for your quick reponse to the email18:05
*** emagana has joined #openstack-meeting-318:05
*** Yi has joined #openstack-meeting-318:05
*** tellesnobrega has quit IRC18:05
SumitNaiksatamapart from the afore mentioned, we dont have any critical (show stoppers) identified18:06
*** bpokorny_ has quit IRC18:06
SumitNaiksatamany other bugs/fixes we need to discuss today?18:06
*** Yi_ has joined #openstack-meeting-318:06
SumitNaiksatamYi_: hi18:06
*** e0ne has joined #openstack-meeting-318:07
Yi_SumitNaiksatam: Hi18:07
SumitNaiksatamperhaps not, moving on18:07
SumitNaiksatam#topic Functional/Integration tests in gate job18:07
*** openstack changes topic to "Functional/Integration tests in gate job (Meeting topic: networking_policy)"18:07
SumitNaiksatamnot much of an update here18:07
SumitNaiksatamone thing to note here is that the testsuite “gbpfunc” which is being run in the functional gate job is residing out of the tree18:08
SumitNaiksatamso if you make a change that affects the current behavior of the API or how things are mapped to Neutron, the tests will break18:08
ivar-lazzaroSumitNaiksatam: what's the workflow for gate breaking changes in this case?18:08
SumitNaiksatamand will have to be fixed18:08
SumitNaiksatamthis happened in the case of ivar-lazzaro’s patch18:09
SumitNaiksatamthis is obviously not the desired way to go about things18:09
SumitNaiksatamivar-lazzaro: yeah18:09
SumitNaiksatamideally that test suite should be integrated in tree18:09
*** smccully has joined #openstack-meeting-318:09
SumitNaiksatambut for expediency reasons (and to avoid further regressions) we are linking it in the gate job18:09
SumitNaiksatamin the case of ivar-lazzaro’s patch we contacted jishnu who wrote the test suite and requested him to update the tests in consultation with ivar-lazzaro who was introducing the changes to the behavior18:10
*** Yi has quit IRC18:10
SumitNaiksatamivar-lazzaro: to answer your question, so until at least the summit, the workflow will be to contact me in case of such breaking changes, and i will coodinate to get a quick fix18:11
SumitNaiksatamivar-lazzaro: in your case you have access to jishnu, so you can directly reach him as well18:12
SumitNaiksatamlets discuss this aspect of the gate job and the test suite in general during the design summit session18:12
rkukuraHopefully we aren’t breaking existing APIs too often.18:12
SumitNaiksatamplease feel free to chime in here if you have thoughts18:12
SumitNaiksatamrkukura: :-)18:12
SumitNaiksatambut i could have gone like :-( too!18:13
*** VW_ has quit IRC18:13
SumitNaiksatamivar-lazzaro: sorry, i dont have immediately have a better solution to that18:13
ivar-lazzarorkukura: the tests also check the southbound APIs, that is that all the Neutron objects are created as expected18:14
SumitNaiksatamivar-lazzaro: good point18:14
ivar-lazzarorkukura: and it breaks when those expectation change :)18:14
*** anteaya has joined #openstack-meeting-318:14
rkukuraivar-lazzaro, SumitNaiksatam: Even those sorts of changes will be really problematic during upgrades of existing deployments.18:15
SumitNaiksatamrkukura: agreed18:15
SumitNaiksatamrkukura: but there are things we learn over time (based on usage feedback) that we need to fix18:16
SumitNaiksatamso most of what is being done now, is along those lines18:16
*** VW_ has joined #openstack-meeting-318:16
SumitNaiksatamas adoption increases, we need to be increasingly more careful18:17
SumitNaiksatam#topic Packaging Update18:17
*** openstack changes topic to "Packaging Update (Meeting topic: networking_policy)"18:17
SumitNaiksatami had an action item to follow up with rkukura on the k-3 release18:17
rkukuraI’m OK with breaking things for trunk-chasers on master, but we need some discipline on the stable/juno branch18:17
*** nikhil_k_ is now known as nikhil_k-afk18:17
SumitNaiksatamrkukura: agreed18:17
*** baoli has quit IRC18:17
SumitNaiksatamunfortunately there quite a few things in flux for k-3 so we did not tag k-318:18
*** baoli has joined #openstack-meeting-318:18
rkukuraWhat really needs to merge for k-3?18:18
SumitNaiksatami am hoping that we can wrap up on those changes a few days before the summit (say a week from now)18:18
SumitNaiksatamrkukura: #link https://review.openstack.org/#/q/status:open+project:stackforge/group-based-policy+branch:master,n,z18:19
*** VW__ has joined #openstack-meeting-318:19
*** annegentle has joined #openstack-meeting-318:19
SumitNaiksatamso there i guess there is no packaging update for today18:20
rkukuraAccording to https://launchpad.net/group-based-policy/+milestone/kilo-gbp-3, a lot needs to merge.18:20
rkukuraWhat about stable branch - will we have updates for those soon?18:20
SumitNaiksatamrkukura: a lot of the bugs are already fixed for k-318:21
*** VW_ has quit IRC18:21
SumitNaiksatamrkukura: yes, stable branch backports was in fact an agenda items18:21
SumitNaiksatam*item18:21
SumitNaiksatambut since you brought it up18:21
SumitNaiksatamthere have been quite a few patches recently merged, and will need to be backported18:21
SumitNaiksatamper our earlier plan to keep stable/juno relatively in sync with respect to features (per user requirements)18:22
rkukuraAre these really critical fixes for existing juno users? Can we start focusing on kilo-based deployments for new features?18:22
*** VW_ has joined #openstack-meeting-318:22
*** ttrifonov is now known as zz_ttrifonov18:22
SumitNaiksatamrkukura: there are critical requirements for users18:22
*** VW__ has quit IRC18:23
*** salv-orlando has joined #openstack-meeting-318:23
rkukuraBut we really cannot package stable branch updates if doing a “yum update” is going to completely break an exisiting deployment.18:23
SumitNaiksatamrkukura: this is predicated on the user feedback that they intend to use juno for the foreseeable future (since kilo packages are not going to be available for a while)18:23
*** david-lyle_ has joined #openstack-meeting-318:25
SumitNaiksatamrkukura: i believe in a earlier meeting we arrived at a consensus that it would be okay to do so18:25
SumitNaiksatamif there are bigger concerns (or the approach is not feasible) we can revisit, but might need some offline discussion18:25
*** david-lyle has quit IRC18:25
hemanthraviSumitNaiksatam:+1, we are working with a customer who will be deploying juno and might need some of these fixes backported18:25
*** david_lyle__ has joined #openstack-meeting-318:25
rkukuraSumitNaiksatam: None of this is a problem for new juno-based deployments. But what does someone do if they have a deployment and it breaks after an update? Do we just tell them to remove and reinstall?18:26
*** salv-orlando has quit IRC18:27
SumitNaiksatamrkukura: agreed that is a problem, and I believe we assessed the risk of that happening and concluded that we are willing to take it (or at least that was what I took away from the discussion)18:27
*** david-lyle has joined #openstack-meeting-318:28
rkukuraIs it a risk or a certainty?18:29
*** david-lyle_ has quit IRC18:29
SumitNaiksatamrkukura: in my understanding its a risk18:29
SumitNaiksatami have heard feedback that an existing user of GBP is in a situation where he would prefer to not reinstall18:30
SumitNaiksatamsorry i meant, i have *not*18:30
rkukuraSumitNaiksatam: That sounds to me like we are trying to ensure that upgrades will work. I’m not so sure we really have been doing that. I know we’ve added some DB migrations, but do these actually fix existing DB records?18:30
SumitNaiksatamrkukura: we have not attempted to migrate data18:31
rkukuraIf we don’t migrate data, we break the deployment.18:31
*** david_lyle__ has quit IRC18:31
SumitNaiksatambut i believe this not always the practice in existing projects either18:31
SumitNaiksatamat least in the early stage18:31
SumitNaiksatamnot saying that it not shoud be18:32
ivar-lazzaroI thought we were in experimental mode until the server split happens18:32
ivar-lazzaro(which will likely break things anyway... won't it?)18:32
SumitNaiksatamat this point the effort to instrument the data migration, would far out weight its benefits18:32
rkukuraI think its reasonable to break master trunk-chasers, and for a new major release to require re-deployment. I don’t think breaking stable branch deployments is reasonable.18:32
SumitNaiksatami am not advocating that we should adopt this as a philosophy, and we should definitely have a process in place going forward18:33
ivar-lazzarorkukura: just to clarify, do you mean breaking Juno to Kilo is OK but Juno to Juno is not?18:33
rkukuraMaybe we can add a pre-install script in the package that refuses to install if the DB has data in it?18:33
rkukurajuno-to-juno18:33
SumitNaiksatamrkukura: that is a very good happy medium18:34
*** david-lyle has quit IRC18:34
SumitNaiksatamrkukura: rather than refusing to install it can prompt user for confirmation before proceeding?18:34
rkukuraNot sure if that is possible18:35
SumitNaiksatamrkukura: okay18:35
SumitNaiksatamso lets have a follow up conversation on this, post this meeting18:35
SumitNaiksatamrkukura: ivar-lazzaro thanks for the feedback on this18:36
SumitNaiksatamhemanthravi: as well18:36
SumitNaiksatam#topic Liberty/Vancouver Summit18:36
*** openstack changes topic to "Liberty/Vancouver Summit (Meeting topic: networking_policy)"18:36
SumitNaiksatamas aderstized earlier: #link https://etherpad.openstack.org/p/gbp-liberty-design-summit18:36
SumitNaiksatami have put some strawman proposals18:36
SumitNaiksatamplease feel free to post your suggestions18:37
SumitNaiksatamwe have a couple of weeks to firm up18:37
SumitNaiksatamthe design sessions are on tuesday (later in the day) and on wednesday (morning)18:37
rkukuraSumitNaiksatam: Looks good so far18:37
SumitNaiksatamrkukura: okay great18:37
SumitNaiksatami was trying to find the link to the sessions, but not handy18:38
SumitNaiksatam#link https://libertydesignsummit.sched.org/type/design+summit/group+based+policy#.VUuxK9pVikp18:38
SumitNaiksatamfound it ^^^18:38
megm_Hi, Matt!  We missed you but ended up chatting for the full time.18:38
megm_Someone new was there and I am drawing a total blank.18:39
s3wong?18:39
SumitNaiksatamwe dont have a Matt here, but megm_ you are welcome to join the team18:39
megm_Apolgies -- wrong room18:39
ivar-lazzaro:)18:40
SumitNaiksatamHands-on lab -18:40
SumitNaiksatamivar-lazzaro: and rkukura over to you18:40
*** s3wong has quit IRC18:40
SumitNaiksatamivar-lazzaro: thanks for sending the write up yesterday, sorry, i havent had a chance to respond18:40
ivar-lazzaroSumitNaiksatam: thanks18:41
ivar-lazzaroWe are trying to come up with a script at the moment18:41
ivar-lazzarobeing this the first GBP hands on, we want to keep is simple, without showing too advanced workflows18:42
ivar-lazzarounless we have time of course18:42
SumitNaiksatamivar-lazzaro: +118:42
ivar-lazzaroThe idea is to focus especially on Groups (you won't say!)18:42
ivar-lazzaroand PRS18:42
ivar-lazzaro(so also simple serve chain examples)18:43
ivar-lazzaroleaving aside L3/L2 and external configurations18:43
ivar-lazzaroThis will also be a nice showcase for the implicit driver18:43
SumitNaiksatamivar-lazzaro: that sounds like a good plan18:43
Yi_ivar-lazzaro: +1 on simplicity18:43
hemanthravishould add a scenario with service chain18:44
ivar-lazzarothat will take care of all those things so that the user doesn't worry18:44
SumitNaiksatamhemanthravi: there will be one18:44
ivar-lazzarohemanthravi: there is one18:44
ivar-lazzaroI'm trying to draft roughly 2 different scripts18:44
SumitNaiksatamteam here, please plan on making yourself available to organize this session18:44
Yi_ivar-lazzaro: I assume it will be focusing on single-node?18:44
ivar-lazzarothe difference will be on the fact that we merge the patches about sharing or not18:44
ivar-lazzaroYi_: one single node and one full chain18:45
SumitNaiksatamlets have a final sync up session on wednesday (after the design summit) in person to firm up on how we are going to conduct the session18:45
SumitNaiksatamivar-lazzaro: rkukura thanks for the update18:45
ivar-lazzaroSumitNaiksatam: just a sec18:45
ivar-lazzaroSumitNaiksatam: there are a couple of patches we need to check18:46
SumitNaiksatami believe we will be sending out more targeted updates on this topic during the coming days18:46
ivar-lazzaroSumitNaiksatam: in order to make this happen with sharing capabilities18:46
ivar-lazzaro#link https://review.openstack.org/#/c/179327/18:46
ivar-lazzaro#link https://review.openstack.org/#/c/164907/18:46
SumitNaiksatamivar-lazzaro: is the latter ready to be reviewed?18:47
ivar-lazzaroI'll try to make the first one less painful if I can (with a pluggable sg_manager)18:47
rkukuraivar-lazzaro: I’ve started reviewing the 1st of these.18:47
SumitNaiksatamivar-lazzaro: i believe we had decided that we would be targeting : #link https://review.openstack.org/#/c/164907/ after the other service chain refactoring patches were merged18:47
*** david-lyle has joined #openstack-meeting-318:47
SumitNaiksatamrkukura: great18:47
ivar-lazzaroSumitNaiksatam: it's ready, I've refactored it so that it's easier to merge with the NCP18:48
SumitNaiksatamivar-lazzaro: okay18:48
rkukuraquestion - are these intented for kilo only, or for backport to juno?18:48
ivar-lazzaroSumitNaiksatam: so feel free to go for it18:48
SumitNaiksatamivar-lazzaro: okay18:48
ivar-lazzarorkukura: sharing service chain constructs is18:48
*** markmcclain has quit IRC18:48
SumitNaiksatamrkukura: at least the latter is intended to be backported to juno as well18:48
ivar-lazzarorkukura: but that's backward compatible18:48
hemanthravineed these for the backport too18:48
ivar-lazzarorkukura: as for the first one, we probably want it to stay in Kilo18:49
*** reed has quit IRC18:49
rkukuraivar-lazzaro: If we add new primary key fields, the DB migration scripts need to populate these.18:49
ivar-lazzarorkukura: "shared" is the only column I add. And it's not a primary key18:49
ivar-lazzarorkukura: as long as its value is preset to False (which is coherent) we should be fine18:50
ivar-lazzarorkukura: this is true for the second patch of course!18:50
ivar-lazzarorkukura: the first one as a whole bunch of non backward-compatible changes18:50
rkukuraivar-lazzaro: What about adding tenant_id as a primary key?18:50
ivar-lazzarorkukura: unless we have time to go with the pluggable approach... In which case everything will be fine18:50
ivar-lazzarorkukura: is that on the second patch?18:50
rkukurano, the 1st18:51
ivar-lazzarorkukura: yeah the first is not backward compatible today, I agree18:51
ivar-lazzarorkukura: I was advocating the 2nd18:51
SumitNaiksatamwe have 9 mins, so lets take the discussion on the 1st patch offline18:51
ivar-lazzarorkukura: we should we fine if we have pluggable managers though, right?18:51
rkukuraivar-lazzaro: probably18:52
SumitNaiksatamivar-lazzaro: pluggable managers will be very helpful and we should have had those from the beginning, so +118:52
rkukuraChanging all existing SGs during an upgrade would be difficult. Lets move on.18:52
ivar-lazzaroSumitNaiksatam: hopefully I have the time to do it :)18:52
SumitNaiksatamivar-lazzaro: :-)18:52
SumitNaiksatam#topic Kilo features18:53
*** openstack changes topic to "Kilo features (Meeting topic: networking_policy)"18:53
SumitNaiksatamplease note that sync with OpenStack kilo is complete18:53
*** emagana has quit IRC18:53
*** david-lyle_ has joined #openstack-meeting-318:53
SumitNaiksatamplease also note that the GBP heat resources are in their own namespace now18:53
SumitNaiksatam#link https://review.openstack.org/#/c/15517218:53
SumitNaiksatamwas merged yesterday18:53
SumitNaiksatamwhat it means is that if you have existing heat templates that reference the GBP heat resources with the earlier Neutron namespace, those will break18:54
SumitNaiksatamthis is applicable only for GBP kilo18:54
SumitNaiksatamso please adjust accordingly18:54
*** emagana has joined #openstack-meeting-318:55
*** emagana has quit IRC18:55
SumitNaiksatamFloating IP support (spec #link https://review.openstack.org/#/c/167174, impl: #link https://review.openstack.org/#/c/167174/) i believe is ready to move ahead18:55
SumitNaiksatamwe have gone through several iterations and i believe the outstanding comments have been addressed at leat for this iteration of support18:56
SumitNaiksatamunless there are any objections, lets move forward on this18:56
*** david-lyle has quit IRC18:56
SumitNaiksatamService chain driver refactor:18:57
*** david-lyle_ is now known as david-lyle18:57
SumitNaiksatamspec was reviewed and merged: #link https://review.openstack.org/#/c/17411818:57
*** reed has joined #openstack-meeting-318:57
SumitNaiksatamif there is further feedback, we can always update it18:57
SumitNaiksatambut we had to draw a line somewhere to proceed with the implementation18:57
SumitNaiksatamivar-lazzaro has a host of impl patches: #link https://review.openstack.org/#/q/status:open+project:stackforge/group-based-policy+branch:master+topic:bp/node-centric-chain-plugin,n,z18:57
*** Sukhdev has joined #openstack-meeting-318:58
SumitNaiksatamnot enough time to go into the details right now, but we can go to #openstack-gbp for follow up discussion if needed18:58
igordcard_okay, anything new that you may have discussed regarding the plumbing plugins?18:58
igordcard_SumitNaiksatam: okay18:58
SumitNaiksatamigordcard_: currently this will be very simple18:59
*** emagana has joined #openstack-meeting-318:59
SumitNaiksatamigordcard_: i dont anticipate that we will have the time to implement any of the sophisticated insertion cases18:59
ivar-lazzaroigordcard_: I'm looking at your traffic streering patch to see how it could fit18:59
SumitNaiksatamigordcard_: think of this as a place holder framework18:59
ivar-lazzaroigordcard_: I may have questions for you in the upcoming days18:59
SumitNaiksatamigordcard_: that you should be able to extend18:59
SumitNaiksatamigordcard_: thanks for the reviews18:59
SumitNaiksatam#topic Open Discussion19:00
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"19:00
SumitNaiksatamwe are almost out of time19:00
SumitNaiksatami was going to propse that we skip the IRC meeting for the next three weeks19:00
SumitNaiksatamsince next week we wil be busy with the summit preparations (or travelling)19:00
SumitNaiksatamthen we will be at the summit19:00
SumitNaiksatamand then we would need a week to recover ;-)19:01
SumitNaiksatamany objections?19:01
SumitNaiksatamof course, if required we can change meet in #openstack-gbp19:01
rkukuraFine with me, but don’t hestitate to re-instate next week if we need it to prepare for the summit.19:01
igordcard_SumitNaiksatam: about the openstackclient, I didn't go too deep in it but yes, it calls existing functionality on the other clients19:01
SumitNaiksatamrkukura: absolutely19:01
SumitNaiksatamigordcard_: awesome good to know19:01
SumitNaiksatamigordcard_: perhaps we can enable remote participation with you on this topic during the design summit19:02
igordcard_SumitNaiksatam: it's just a matter of adding a new module for gbp and creating the wrapper calls accordingly19:02
yapengODL GBP driver change will be submitted to reflect ODL GBP Lithium API changes.19:02
SumitNaiksatamigordcard_: and for the other topics as well based on your availability and interest19:02
igordcard_SumitNaiksatam: yes19:02
SumitNaiksatamigordcard_: good19:02
yapengI will submit for review after I test against with kilo stable branch.19:02
SumitNaiksatamyapeng: thanks for following on that, keep me in the loop on what you are planning19:02
SumitNaiksatamyapeng: so that we can ensure that it makes the kilo cut19:03
SumitNaiksatamalright, thanks all!19:03
yapengSumitNaiksatam, sure. when will cut happen?19:03
SumitNaiksatamyapeng: you have at least a week for kilo-319:03
*** stevemar has joined #openstack-meeting-319:03
SumitNaiksatambye!19:04
yapengSumitNaiksatam, sure. I think i can make it.19:04
yapengbye19:04
SumitNaiksatamyapeng: thanks19:04
igordcard_cya all19:04
SumitNaiksatam#endmeeting19:04
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:04
Yi_bye19:04
openstackMeeting ended Thu May  7 19:04:26 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:04
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-05-07-18.02.html19:04
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-05-07-18.02.txt19:04
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-05-07-18.02.log.html19:04
rkukurabye19:04
*** VW_ has quit IRC19:04
ivar-lazzarobye19:04
*** VW_ has joined #openstack-meeting-319:07
*** VW_ has quit IRC19:07
*** rkukura has left #openstack-meeting-319:08
*** VW_ has joined #openstack-meeting-319:08
*** markmcclain1 has joined #openstack-meeting-319:09
*** hemanthravi has quit IRC19:16
*** markmcclain1 is now known as markmcclain19:16
*** Youcef has quit IRC19:18
*** Yi_ has quit IRC19:19
*** ryansb has left #openstack-meeting-319:20
*** kozhukalov has quit IRC19:20
*** singlethink has quit IRC19:22
*** bpokorny has quit IRC19:22
*** bpokorny has joined #openstack-meeting-319:23
*** singlethink has joined #openstack-meeting-319:34
*** david-lyle has quit IRC19:43
*** mrmartin has quit IRC19:46
*** yamahata has quit IRC19:50
*** Piet has quit IRC19:53
*** marun has quit IRC19:56
*** csd has quit IRC19:56
*** lblanchard has quit IRC19:56
*** csd has joined #openstack-meeting-319:57
*** VW_ has quit IRC20:00
mattgriffinHA-Guide: i need a few more minutes. please take a look at today's agenda - https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update#Next_Meeting20:00
mattgriffinmegm_ and others ^20:00
*** singleth_ has joined #openstack-meeting-320:00
megm_Hello!20:01
*** matrohon has joined #openstack-meeting-320:01
*** salv-orlando has joined #openstack-meeting-320:01
*** annegentle has quit IRC20:02
*** bpokorny_ has joined #openstack-meeting-320:02
*** singlethink has quit IRC20:03
*** bpokorny_ has quit IRC20:03
*** bpokorny_ has joined #openstack-meeting-320:04
*** SumitNaiksatam has quit IRC20:06
*** bpokorny has quit IRC20:06
*** VW_ has joined #openstack-meeting-320:06
*** SumitNaiksatam has joined #openstack-meeting-320:06
*** baoli has joined #openstack-meeting-320:07
*** alexpilotti has quit IRC20:08
*** beagles has joined #openstack-meeting-320:08
*** baoli has quit IRC20:08
*** bknudson has joined #openstack-meeting-320:09
*** alexpilotti has joined #openstack-meeting-320:09
*** baoli has joined #openstack-meeting-320:09
megm_Hi, all!  I see some new names -- I hope everyone is here to discuss the HA Guide!20:11
mattgriffinmegm_, almost done with my meeting :)20:11
megm_matt, terrific -- we'll wait20:12
*** blogan has joined #openstack-meeting-320:12
megm_Does anyone have questions while we wait for mattgriffin to officially begin the meeting?20:12
megm_Or want to introduce yourselves?20:12
*** baoli has quit IRC20:13
mattgriffinmegm_, you can go ahead and get started... i'll start the official logging20:13
mattgriffin#startmeeting ha-guide20:13
openstackMeeting started Thu May  7 20:13:20 2015 UTC and is due to finish in 60 minutes.  The chair is mattgriffin. Information about MeetBot at http://wiki.debian.org/MeetBot.20:13
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:13
*** openstack changes topic to " (Meeting topic: ha-guide)"20:13
openstackThe meeting name has been set to 'ha_guide'20:13
*** baoli has joined #openstack-meeting-320:13
*** alexpilotti has quit IRC20:16
*** salv-orlando has quit IRC20:16
megm_Hello?20:17
*** Longgeek has quit IRC20:18
mattgriffinmegm_, hi. ok. ready20:19
mattgriffinmegm_, ok. first review the TOC and most recent changes?20:19
mattgriffin#link https://wiki.openstack.org/wiki/HAGuideImprovements/TOC20:20
megm_I'm concerned about including all the controller details in the intro.20:20
megm_Also, the info about stateless/stateful, etc is now an xref to the old ha-guide that this document is replacing20:21
megm_And a link to Mirantis Fuel doc for the HA Controller role description20:21
*** VW_ has quit IRC20:21
mattgriffinmegm_, gotcha. i think the TOC seems to be turning somewhat into the actual HA Guide document20:23
megm_Yes, and some great additions.  But we need an agreed-on structure to set up the files20:24
*** alexpilotti has joined #openstack-meeting-320:24
mattgriffinmegm_, is your concern about the controller details found in this section? https://wiki.openstack.org/wiki/HAGuideImprovements/TOC#Redundancy_and_failover20:25
megm_I'm thinking that we should move everything from "Controller node" to the "Stateless/stateful..." section to a separate "HA Controller Node Intro"20:25
megm_Yes.  And, do we have the intro to the HA controller before the "Basic Environment" and "Basic HA facilites" sections?20:26
mattgriffinno. i think the HA Controller content should be after the Basic Environment and Basic HA Facilities sections20:28
megm_I've been concerned about the details of Basic HA facilities.  Perhaps that section should be "Making the Controller Highly Available"?20:28
mattgriffinseems better to cover the basics first and then drill into the components20:28
*** alexpilotti has quit IRC20:29
megm_Is  Evkonst here?20:29
*** nikhil_k-afk is now known as nikhil_k20:29
*** baoli has quit IRC20:29
megm_matt, yes, basics first, but are the basics to install the O/S on each node, etc, or to understand what the HA Controller is, etc?20:30
*** emagana has quit IRC20:31
megm_And we are constrained by our agreement to follow the structure of the Install Guide as much as possible...20:31
*** emagana has joined #openstack-meeting-320:32
mattgriffinmegm_, they start with Basic Environment20:33
*** Swami has quit IRC20:33
mattgriffinunless that's changing20:33
mattgriffinmegm_, if anything, the controller node info should be part of the Basic Environment section (like they do in the Install Guide)20:35
megm_I'm just looking at what now shows as "HA Intro and Concepts" -- we have "Redundancy and failover" and then we go through all the Controller services, Hardware, Routing,  etc before we get to the active/active vs active passive and quorum info20:35
*** baoli has joined #openstack-meeting-320:35
megm_Yes, it may be that what we currently call "Basic Environment" should be "HA Controller"20:36
mattgriffinmegm_, i think the information listed at https://wiki.openstack.org/wiki/HAGuideImprovements/TOC#HA_Intro_and_Concepts is more of definitions rather than specifics on setting, yes?20:36
megm_Rather, "Basic HA facilities" -- or maybe the two "Basic" sections are combined20:36
megm_Do those definitions belong in the intro, before the intro to HA concepts?  That is my question.  The material is great but I think it does not belong in the Intro20:37
mattgriffinwe could combine them20:37
megm_I was hoping that Evkonst would be here to explain his/her vision20:38
mattgriffinmegm_, gotcha.... how about we leave an "HA Intro" section and have a uber-Basic section that includes the Basic content of today (in the 2 sections) as well as the definitions to pair with any, for example, diagrams that might be in the Basic section?20:39
megm_Soounds reasonable.20:39
megm_What really matters right now is that we know what the main chapters are so we can set up the files -- a main file and a subdirectory of files for subsections for each20:40
mattgriffinmegm_, ok. i'll reorg the TOC and keep the great content that's already there20:40
mattgriffinmegm_, ack20:40
megm_Cool if you want to do it.20:40
megm_Is anyone here other than Matt and me?20:41
megm_I'm happy to do the work -- just wanted the discussion.20:41
mattgriffin#action mattgriffin reorg the TOC with an "HA Intro" section and a "Basic" section which includes the Basic content of today (in the 2 sections) as well as the definitions20:41
mattgriffinmegm_, np20:41
*** stevemar has quit IRC20:42
megm_Do you want me to rework the TOC or do you want to?  I'm willing but you are welcome to it20:42
*** Nikolay_St has joined #openstack-meeting-320:42
mattgriffinmegm_, can i take a first pass and then ping you?20:42
megm_Absolutely!20:43
mattgriffincool20:43
mattgriffini've got another meeting in 15 min so move on to other agenda topics?20:43
mattgriffinmegm_, ^20:43
megm_Yes, move on.20:43
megm_How much can we do without the others?20:43
mattgriffinmegm_, let's jump to the last 2 items on the agenda20:44
*** marun has joined #openstack-meeting-320:44
mattgriffinxrefs to Install Guide ... you brought this concern up20:44
mattgriffinis this something that we should prototype an approach and confirm how we're thinking this will work?20:45
megm_I was hoping that Nick knew what to do ;-)20:45
mattgriffinmegm_, ok. making that an action item20:45
megm_I don't think we have a choice -- the right way is to use the intersphinx facilities but those are not set up so we're going to have to use html links between the two guides20:46
mattgriffin#action nickchase: are there potential pitfalls with using xrefs to link to the Install Guide? should we build a prototype?20:46
mattgriffinok20:46
mattgriffinhmm... maybe someone will have a bright idea on that topic in Vancouver b/c it sounds like a big need20:47
megm_Just FYI, if you are writing something today, what is the URL for a new chapter in the Install Guide?20:47
megm_That is the initial problem...20:47
megm_For the last item, "Next steps" are to convert docbook->rst, set up new chapter files/subdirectories, and put existing content in the right place.  Nick had said he would do that.20:48
megm_Only question is do we commit to a merge of the old info into the new structure with NO fixes?20:48
*** Shamail has joined #openstack-meeting-320:48
mattgriffin#action convert docbook->rst, set up new chapter files/subdirectories, and put existing content in the right place. ... nick?20:48
*** absubram has quit IRC20:49
Shamailhi.20:49
megm_Hi, Shamail!20:49
mattgriffinmegm_, not sure. maybe better to start from scratch?20:49
*** SumitNaiksatam has quit IRC20:49
mattgriffinhi Shamail20:49
*** banix has joined #openstack-meeting-320:50
megm_Matt, I have no objections to starting from scratch, but all along, everyone has been adamant about the primacy of preserving the old material.  Is this a change in strategy?20:50
*** VW_ has joined #openstack-meeting-320:51
*** e0ne has quit IRC20:51
mattgriffinmegm_, well we'd keep as much of the old material as was relevant. were there objections to copy/paste text to do that?20:52
mattgriffinwell copy/paste/edit20:52
megm_I'm pretty open as to which strategy we take, but I think we need to agree on one20:52
mattgriffinmegm_, i'll check with the PTL and core reviewers for direction20:53
*** VW_ has quit IRC20:53
*** VW__ has joined #openstack-meeting-320:53
megm_See Step 2 in https://etherpad.openstack.org/p/openstack-haguide-update-next-steps -- that should be modified if we're changing strategy20:53
* mattgriffin clicks20:54
*** baoli has quit IRC20:55
megm_I hate six-way merges ;-)20:56
mattgriffinmegm_, sounds like copy/paste/edit to me20:56
mattgriffinhaha20:56
*** baoli has joined #openstack-meeting-320:56
*** nickchase has joined #openstack-meeting-320:56
mattgriffinmegm_, but i'll check to confirm20:56
megm_Nick, are you here?  Hooray!20:56
nickchasewow, what a reception. :)20:56
nickchasehey there.20:56
nickchaseam I late?20:57
mattgriffinwelcome nickchase20:57
nickchaseI thought it was starting in 5 minutes?20:57
mattgriffinyes. started 55 min ago :)20:57
nickchase(facepalm)20:57
mattgriffindid the time change again?20:57
megm_We've been playing What Would Nick Do?  Please tell us!  ;-)20:57
nickchasehahahahaha20:57
nickchaseOK, so I can tell you:20:57
nickchaseSo here's my update:20:57
nickchase1)  The spec's in and approved, finally, thank you very much Meg for helping there!20:57
*** VW__ has quit IRC20:58
nickchase2)  We have a bunch of content that's been added to the wiki, as you may have seen20:58
*** Sukhdev has quit IRC20:58
nickchaseit needs to be edited, smoothed out, etc. and co-credited to its original authors, but at least we have something to start with.20:58
ShamailLol megm_20:58
nickchaseSo that's my update.20:58
megm_And what happens next?20:59
nickchasethere's more content coming but that was what we could get done by today.20:59
megm_I really think we need to get content under git/gerrit and out of the etherpad -- it's starting to get ugly there!  ;-)20:59
mattgriffinnickchase: megm_ and i had some concerns about where the new content was slotting into the TOC...20:59
mattgriffinwe need to talk about that... but i need to run to a meeting now21:00
mattgriffinmegm_, +121:00
nickchasehey, you guys go for it; my job was to rally people. :)21:00
nickchasehave run21:00
nickchasefun*21:00
nickchasesorry I was late21:00
mattgriffin:)21:00
mattgriffinnickchase, np21:00
megm_Matt, should Nick, Shamail, and I continue the meeting?21:00
mattgriffinmegm_, you can... i'll leave the window open and end it when you're done for the log... just ping me21:01
ShamailI have to leave soon too21:01
megm_Nick and Shamail, does that work for you?21:01
Shamail+1 on moving to git21:01
nickchase+1 also21:01
*** VW_ has joined #openstack-meeting-321:01
nickchaseI do not have time to do it, though21:01
nickchasenot the next 3 weeks, anyway21:02
megm_Nick, are you going to set up files?  I'm willing to do some work but I need a little guidance21:02
*** bpokorny has joined #openstack-meeting-321:02
nickchasethe setup is done21:03
nickchaseAndreas did it21:03
megm_We don't have chapter files and subdirectories21:03
nickchasethere are no subdirectories.21:03
ShamailAwesome, can you please link?21:03
nickchaseI'm happy to give guidance21:03
nickchaseit's in the ha-guide repo, probably under "source"21:03
megm_Are we converting the RST files and locating them in the new files?  I thought that was the plan but Matt now seems to think otherwise21:04
nickchaseI haven't seen it myself; I'm taking Andreas' word for it :)21:04
ShamailOkay.  I'll look in the existing area.21:04
nickchaseNo, what we're doing is...21:04
nickchaseputting in the new content, then filling in the TOC where there's old content that fits.21:04
nickchaseThat was how we "sold" that we needed to do this in RST rather than Docbook.21:04
*** bpokorny_ has quit IRC21:05
megm_So do we know what the main  chapters are?   I made a list a long time ago but it may need to be revised...21:06
nickchasethey're in the TOC.21:06
*** Piet has joined #openstack-meeting-321:06
* nickchase just updated his calendar. (facepalm)21:07
megm_High Availability Concepts21:07
megm_Hardware Setup21:07
megm_Install O/S on Nodes21:07
megm_Basic Infrastructure21:07
megm_Configure Networking on Each Node21:07
megm_Install and Configure MySQL21:07
nickchasethe RST files are not hierarchical like the docbook ones are21:07
megm_RabitMQ Message Broker21:07
nickchasethey're topic-based.21:07
megm_Keystone Identity Services21:07
megm_Glance image service21:07
megm_Cinder Block Storage Service21:07
nickchaseloosk right21:07
megm_Swift Object Storage21:07
megm_Storage Backend Options21:07
megm_Nova Compute Service21:07
megm_Heat Orchestration21:07
megm_Ceilometer Telemetry and MongoDB21:07
megm_Database Service (Trove)21:08
megm_Sahara21:08
megm_Other21:08
megm_~21:08
ShamailLooks good21:08
nickchase+121:08
megm_Should the sections for Controller node services be combined into a single "HA Controller" section with subsections?21:08
nickchaseif you look in the wiki, there's a bunch of content in there21:08
*** Swami has joined #openstack-meeting-321:08
nickchaseI don't understand the question21:09
megm_The list of "chapters" I submitted...  Do we want to group the Controller stuff or leave each individual?21:10
ShamailThat might make sense... Effectively can we make a "HA controller" section, document common items for general controller HA, and then have sub-sections for service specific requirements (keystone, cinder, etc.)21:10
ShamailI'm sure there will be common things that apply to controller nodes in general.  This might prevent repeating or extensive referencing.21:11
megm_Yes, Shamail.  So maybe we have "HA Controller," "HA Storage", "HA Compute"21:11
nickchaseI think taht you should leave it where it is21:11
nickchasebecause we hashed out this TOC pretty thoroughly, didn't we?  Or did I miss something?21:12
nickchaseI mean, it's designed to track the install guide.21:12
megm_I thought we had but Evknost made massive changes -- added a whole bunch of stuff to Intro that I think may belong in an "Introl toController"'  section21:12
nickchaseSo I'm assuming that the TOC follows that.21:12
ShamailWe did.  I thought we validated the topics not necessarily the organization of it.  If that was a part of the review too then I agree that we should leave it.21:12
nickchaseahhhhhh.21:12
nickchaseOK, now THAT makes sense;21:13
nickchaseIntro to controller seems a perfectly reasonable thing21:13
Shamail:-)21:13
nickchaseI thought you were talking about within the body21:13
megm_I'm not sure of anything!  Maybe we just need to grab SOME structure and create files!  We can always move stuff later21:13
nickchase:)21:13
nickchaseOK, so here's what I think:21:13
ShamailWe have consensus! (Can we have consensus on the fact that we actually have it?)21:13
nickchaseIf we're saying take what's there and chuck it in, and combine the intro to controller stuff into one section, then yes.21:14
megm_Do we add "Intro to Controller", "Intro to Storage", etc as part of (or right after) the Intro to HA concepts and before they start installation?21:14
nickchase+121:14
Shamailmegm_: +121:14
nickchaseafter21:14
nickchaseno, part of21:15
nickchasesorry21:15
nickchasepart of21:15
megm_Or do we do basic installation, then "Intro to Controller" then "How to HA the Controller services" sections....?21:15
megm_nick, part of intro?21:15
nickchaseI mean the following:21:15
nickchase1)  Intro to controller, intro to storage, etc. should be part of Intro to HA.21:16
megm_nickchase, I can +1 that21:16
nickchase2)  After the intro, we track the normal install, pointing out the places where things are different for an HA install.21:16
*** baoli has quit IRC21:16
nickchasethat's what I mean.21:16
megm_Nick, what do you mean that RST files are not hierarchical?  Do you mean just one big file for each chapter without subdirectories?21:17
*** baoli has joined #openstack-meeting-321:17
ShamailThat's perfect.  +121:17
nickchaseI mean that we're not doing subdirectories21:18
nickchaseall the chapters and sections and subsections are in one big source directory21:18
nickchaseand they're not named like the docbook.  for example...21:18
megm_Really?  Aren't we going to trip over each other a lot with so many people contributing?21:18
nickchasein docbook, we'd have section_intro_ha.xml and section_intro_ha_compute.xml.  In RST we have only intro_ha.rst and intro_compute.rst21:19
nickchaseI prefer hierarchical too, but I'm overruled on this.21:19
nickchasewe have to let git do its thing here.21:19
*** jckasper has quit IRC21:19
megm_Ah, it is written from a higher source, you're saying?21:20
nickchaseindeed.21:20
megm_Cool, then we're set.  It does make set-up easier ;-)21:21
ShamailI have to drop off.  Sorry.  Have a great weekend!  Are we meeting next week or Vancouver is the next one?21:21
nickchaseI can't meet in vancouver21:21
nickchasenext week, I assume21:21
megm_Would you have an hour or so early next week to give me some guidance and then I could set up files?  Unless Shamail can do it without guidance, of course21:21
nickchaseif you need me that's fine; check my calendar.21:22
ShamailI can't either... So the 1st option is best.21:22
megm_It would be good to have the files set up before Vancouver --and before we get more content in ehterpad!21:22
ShamailAlright, see you next week then.  Take care Nick chase and megm_21:22
megm_Bye21:23
*** Shamail has quit IRC21:23
megm_Nick, is the Network Guide set up correctly?  Can I study that for some clues?21:23
megm_Like for file names and such?21:23
nickchaseyes21:26
nickchasedo that21:26
megm_I added list of chapters to https://etherpad.openstack.org/p/openstack-haguide-update-next-steps21:29
*** Sukhdev has joined #openstack-meeting-321:32
nickchaseok, great.21:33
nickchaseis there anything els eyou need from me?21:33
*** banix has quit IRC21:34
megm_No, let's call it done for today.  I'll do some studying and ping you for some guidance...21:36
megm_I'll ping matt to close the minutes.21:36
mattgriffin#endmeeting21:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:36
openstackMeeting ended Thu May  7 21:36:57 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ha_guide/2015/ha_guide.2015-05-07-20.13.html21:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ha_guide/2015/ha_guide.2015-05-07-20.13.txt21:37
openstackLog:            http://eavesdrop.openstack.org/meetings/ha_guide/2015/ha_guide.2015-05-07-20.13.log.html21:37
*** baoli has quit IRC21:38
*** baoli has joined #openstack-meeting-321:39
*** peristeri has quit IRC21:39
*** mwagner_lap has quit IRC21:45
*** sarob has quit IRC21:46
*** matrohon has quit IRC21:47
*** baoli has quit IRC21:49
*** baoli has joined #openstack-meeting-321:50
*** david-lyle has joined #openstack-meeting-321:56
*** banix has joined #openstack-meeting-322:02
*** banix has quit IRC22:04
*** btully has quit IRC22:05
*** emagana has quit IRC22:07
*** baoli has quit IRC22:10
*** baoli has joined #openstack-meeting-322:11
*** nelsnelson has quit IRC22:11
*** baoli has quit IRC22:21
*** baoli has joined #openstack-meeting-322:22
*** salv-orlando has joined #openstack-meeting-322:25
*** eghobo_ has quit IRC22:27
*** btully has joined #openstack-meeting-322:29
*** salv-orlando has quit IRC22:31
*** mlavalle has quit IRC22:34
*** shwetaap has quit IRC22:35
*** david-lyle has quit IRC22:38
*** baoli has quit IRC22:53
*** baoli has joined #openstack-meeting-322:54
*** fallenpegasus has joined #openstack-meeting-322:55
*** singleth_ has quit IRC22:56
*** Gridnev has quit IRC23:02
*** baoli has quit IRC23:04
*** Piet has quit IRC23:05
*** VW_ has quit IRC23:17
*** markvoelker has quit IRC23:26
*** mattgriffin has quit IRC23:28
*** fallenpegasus has quit IRC23:28
*** Sukhdev has quit IRC23:32
*** carl_baldwin has quit IRC23:34
*** btully has quit IRC23:38
*** mattgriffin has joined #openstack-meeting-323:41
*** Aish has quit IRC23:49
*** eghobo has joined #openstack-meeting-323:50
*** markvoelker has joined #openstack-meeting-323:56
*** markvoelker has quit IRC23:57
*** markvoelker has joined #openstack-meeting-323:57

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