Wednesday, 2017-05-03

*** thorst_afk has joined #openstack-doc00:00
*** catintheroof has joined #openstack-doc00:00
*** catintheroof has quit IRC00:01
*** masaki has joined #openstack-doc00:02
*** suyog has joined #openstack-doc00:02
*** catintheroof has joined #openstack-doc00:04
*** tonytan4ever has joined #openstack-doc00:22
*** darrenc has quit IRC00:27
*** catintheroof has quit IRC00:33
*** thorst_afk has quit IRC00:37
*** catintheroof has joined #openstack-doc00:39
*** thorst_afk has joined #openstack-doc00:44
*** thorst_afk has quit IRC00:46
*** masaki has quit IRC00:52
*** yamamoto has joined #openstack-doc00:57
*** phuongnh has joined #openstack-doc01:02
*** yamamoto has quit IRC01:05
*** catintheroof has quit IRC01:09
*** cathrichardson has joined #openstack-doc01:13
*** cathrich_ has quit IRC01:13
openstackgerritHuan Xie proposed openstack/openstack-manuals master: XenAPI: modify manual to use neutron network and os-xenapi  https://review.openstack.org/46046701:28
*** gouthamr has quit IRC01:37
*** dmacpher has joined #openstack-doc01:40
*** nicolasbock has quit IRC01:41
*** thorst_afk has joined #openstack-doc01:47
*** thorst_afk has quit IRC01:52
*** nicolasbock has joined #openstack-doc01:55
openstackgerritHuan Xie proposed openstack/openstack-manuals master: XenAPI: modify manual to use neutron network and os-xenapi  https://review.openstack.org/46046702:00
openstackgerritJay Bryant proposed openstack/training-guides master: [upstream] fix missing line and describe voting/non-voting  https://review.openstack.org/46192902:14
*** nicolasbock has quit IRC02:17
*** tonytan4ever has quit IRC02:22
*** nicolasbock has joined #openstack-doc02:33
*** charcol-v2 has joined #openstack-doc02:37
*** charcol has quit IRC02:40
*** thorst_afk has joined #openstack-doc02:48
*** fragatin_ has joined #openstack-doc03:03
*** fragatina has quit IRC03:06
*** fragatin_ has quit IRC03:08
*** thorst_afk has quit IRC03:08
*** nicolasbock has quit IRC03:10
*** gianpiet_ has joined #openstack-doc03:11
*** gianpietro has quit IRC03:11
*** gianpiet_ has quit IRC03:16
*** gianpietro has joined #openstack-doc03:16
*** gianpietro has quit IRC03:19
*** charcol-v2 has quit IRC03:53
*** charcol has joined #openstack-doc03:56
*** thorst_afk has joined #openstack-doc04:04
*** thorst_afk has quit IRC04:09
*** salv-orlando has joined #openstack-doc04:18
*** salv-orlando has quit IRC04:23
*** chlong has joined #openstack-doc04:23
*** fragatina has joined #openstack-doc04:24
*** fragatina has quit IRC04:25
*** fragatina has joined #openstack-doc04:25
*** dmacpher is now known as dmacpher-afk04:31
*** salv-orlando has joined #openstack-doc04:49
*** adisky has joined #openstack-doc04:53
adiskyhi04:58
adiskycan anybody tell me how to publish install guide of other services on openstack-manuals??04:58
*** huanxie has quit IRC05:02
*** huanxie has joined #openstack-doc05:03
*** huanxie has quit IRC05:04
*** huanxie has joined #openstack-doc05:05
*** erikmwil_ has joined #openstack-doc05:20
*** erikmwilson has quit IRC05:23
ianychoiadisky, which service? For example, heat install tutorials are in openstack/heat repository, not in openstack-manuals: http://git.openstack.org/cgit/openstack/heat/tree/install-guide/source05:25
adiskyianychoi: yes05:26
adiskyianychoi: how to link them??05:26
adisky<https://docs.openstack.org/project-install-guide/orchestration/draft/>05:28
*** charcol-v2 has joined #openstack-doc05:28
ianychoiadisky, it is already linked to https://docs.openstack.org/project-install-guide/ocata/ubuntu-services.html for ocatabranch05:29
adiskyianychoi: i know it is linked05:30
adiskyianychoi: i need to link for watcher05:30
*** charcol has quit IRC05:31
ianychoiadisky, aha.. imo you can propose a patch like: https://review.openstack.org/#/c/452042/05:31
ianychoiadisky, draft (currently in master) documents are being managed in: https://docs.openstack.org/draft/draft-index.html05:32
ianychoiSo it might be the patch for https://docs.openstack.org/project-install-guide/draft/ page05:32
adiskyianychoi: thank you thats what i was asking for :)05:32
adiskyianychoi: thanks for your help05:33
ianychoiadisky, it's my pleasure :)05:33
AJaegeradisky: all documented here: https://docs.openstack.org/contributor-guide/project-install-guide.html05:44
*** salv-orl_ has joined #openstack-doc05:46
adiskyAJaeger: Thanks  :)05:47
*** salv-orlando has quit IRC05:49
*** salv-orl_ has quit IRC05:50
*** pkovar has joined #openstack-doc05:50
*** thorst_afk has joined #openstack-doc06:06
*** thorst_afk has quit IRC06:11
*** andreas_s has joined #openstack-doc06:13
*** suyog has quit IRC06:16
*** rejy has joined #openstack-doc06:20
openstackgerritGergely Csatari proposed openstack/training-guides master: [upstream] Some corrections to the Governance slides  https://review.openstack.org/46183106:26
*** pcaruana has joined #openstack-doc06:27
openstackgerritGauvain Pocentek proposed openstack/openstack-manuals stable/ocata: [config-ref] Update keystone config tables  https://review.openstack.org/46200506:32
openstackgerritChason Chan proposed openstack/openstack-manuals master: [install] add Cells and Placement API verification step  https://review.openstack.org/46200906:51
*** thorst_afk has joined #openstack-doc07:06
mpranjicmorning07:09
*** charcol-v2 has quit IRC07:10
*** thorst_afk has quit IRC07:11
*** jpena|off is now known as jpena07:33
*** Qiming has quit IRC07:36
*** salv-orlando has joined #openstack-doc07:38
*** Qiming has joined #openstack-doc07:42
*** salv-orlando has quit IRC07:46
*** bmoss has joined #openstack-doc07:50
*** gouthamr has joined #openstack-doc07:51
*** oanson has quit IRC07:52
*** oanson has joined #openstack-doc07:53
*** gouthamr has quit IRC07:56
openstackgerritIan Y. Choi proposed openstack/training-guides master: [upstream] Refines Documentation section  https://review.openstack.org/46190808:01
openstackgerritIan Y. Choi proposed openstack/training-guides master: [upstream] Refines Documentation section  https://review.openstack.org/46190808:02
*** salv-orlando has joined #openstack-doc08:05
*** thorst_afk has joined #openstack-doc08:07
*** fragatina has quit IRC08:20
openstackgerritIan Y. Choi proposed openstack/training-guides master: [upstream] Governance - AUC and election activies  https://review.openstack.org/46190208:22
*** thorst_afk has quit IRC08:26
*** mikal has quit IRC08:39
*** mikal has joined #openstack-doc08:41
AJaegerianychoi: you can have multiple documents in one repo - your repo is i18n so that should be the project name.08:43
AJaegerianychoi: Do I get it right that the glossary is not synced via our scripts?08:44
mpranjicAJaeger: o/08:44
AJaegerhi mpranjic08:44
ianychoiAJaeger, currently PTL manually syncs glossary :)08:44
AJaegerianychoi: and that's the problem ;(08:44
AJaegerianychoi: why not sync glossary *And* your docs with the scripts - using one repo (As is) and one zanata project?08:45
ianychoiAJaeger, yep then I will consider to change glossary file name from i18n.pot to like i18n-glossary.pot08:45
AJaegerianychoi: that would work08:45
ianychoiAJaeger, I need to more investigate on  the mechanism of syncing glossary - really? Sorry I really need to take more time to sync it08:46
ianychoiAJaeger, Thanks a lot for such idea - yep if Zanata 3.9.6 supports glossary sync well, then infra sync job also can cover glossary sync - which will be so nice!08:47
AJaegerianychoi: Wait, you talk the glossary that is used in Zanata itself?08:47
AJaegerianychoi: where is that *translated* ?08:48
AJaegerbtw. why do we have https://translate.openstack.org/project/view/i18n-guide?dswid=-467 ? We create those repos *automatically*. No need to create one.08:48
ianychoiAJaeger, with previous Zanata 3.7.3, I manually synced with http://git.openstack.org/cgit/openstack/i18n/tree/i18n/locale/i18n.pot and po files with https://translate.openstack.org/glossary/ page08:49
AJaegerianychoi: Ah, I see. No idea how that works.08:49
AJaegerI expected you translated i18n.pot in Zanata itself.08:49
ianychoiAha.. yep I admit that I have not seen how Zanata 3.9.6 supports glossary sync well08:50
AJaegerBut that means there is no *i18n* repo used in translate.openstack.org, so you can just use it.08:50
ianychoi"question: what is the reason of the name? Can't we have a more meaningful name like i18n-guide or something? We already use 'i18n.po(t)' for glossary and I am not sure it is a good idea to use the same name."08:51
ianychoiThat was amotoki's comment and the reason why I changed to i18n-guide08:51
ianychoiMaybe changing glossary file naming would be a better idea?08:51
AJaegeryes, I would change glossary file name and keep the 1:1 relation between repo and zanata project08:52
ianychoiOkay I see! I will more see on glossary part and make the changes on the review later :)_08:54
ianychoiAJaeger, hope to see soon at Boston!08:54
openstackgerritChason Chan proposed openstack/openstack-manuals master: [install] add Cells and Placement API verification step  https://review.openstack.org/46200908:54
*** salv-orlando has quit IRC08:56
AJaegerianychoi: won't be coming to Boston. Have family event on weekend and other obligations so I decided not go ;(08:59
ianychoiAJaeger, oh I thought that you would come to Boston because you were listed in speakers in Documentation project updates. Family is also important in our lives :)09:00
AJaegerianychoi: that should have been changed, didn't check whether it happened09:04
*** yamamoto has joined #openstack-doc09:07
*** yamamoto has quit IRC09:11
*** bsilverman_13 has joined #openstack-doc09:23
*** bsilverman_ has quit IRC09:24
*** thorst_afk has joined #openstack-doc09:24
*** pots has quit IRC09:25
*** thorst_afk has quit IRC09:28
*** steveg_afk has joined #openstack-doc09:29
*** adreznec has quit IRC09:30
*** adreznec has joined #openstack-doc09:31
asettleMorning :)09:43
openstackgerritAlexandra Settle proposed openstack/openstack-manuals master: [install] add Cells and Placement API verification step  https://review.openstack.org/46200909:47
bmossheh. better you than me asettle. ;)09:51
asettlebmoss: ugh hhahaha. This one is a small fix, so it's okay. You can probably merge that one if you have a sec, bmoss :)09:52
asettleActually, bmoss while I got you here, did you see my email to Petra?09:52
bmossI did, I've been slack though and haven't replied yet.09:52
bmossIf Petra has the bandwidth to help out there though, that would be awesome.09:53
asettleYeah, she messaged me after the OSIC stuff about wanting to help out. Wanted a project. I gave her that one.09:53
asettleShe appears to be ready and willing.09:53
bmosssweet!09:53
bmossI'll be able to start picking up with OpenStack stuff again tomorrow I think. This past week has been all about job hunting.09:54
bmossbut the more help we can get, the better it is. Especially since we don't know where we're all going to land09:54
asettleNo problem :) thanks for staying onboard while you can. I really appreciate it.09:54
asettleYeah, that's my sentiments too.09:55
asettleHow's the job hunt?09:55
bmossI've had some good leads and some interviews. I'm feeling cautiously optimistic.09:55
bmossand the RCBAU team has been awesome. Everyone is really helping one another09:55
openstackgerritMerged openstack/openstack-manuals stable/ocata: [config-ref] Update keystone config tables  https://review.openstack.org/46200509:55
asettleThat's really great bmoss :D I'm really happy for you. I hope you land somewhere that really uses your skills09:56
asettle!09:56
asettleYeah man, that team is full of some seriously good eggs.09:56
asettleI miss you guys a lot :(09:56
*** tesseract has joined #openstack-doc09:56
bmoss+@09:56
bmoss+209:56
bmosslol. oops;09:56
bmossack. type much09:56
bmossbtw, that patch looks good. I'll just wait to check the built doc then I'm happy merge it.09:57
bmossthen, I'm going in search of dinner. :)09:57
asettlebmoss: sounds good :) thank you.10:02
asettleYeah typing is hard.10:02
*** bmoss has quit IRC10:05
*** salv-orlando has joined #openstack-doc10:06
openstackgerritMerged openstack/training-guides master: [upstream] Refines Documentation section  https://review.openstack.org/46190810:07
openstackgerritBrian Moss proposed openstack/openstack-manuals master: [install] add Cells and Placement API verification step  https://review.openstack.org/46200910:08
*** oanson has quit IRC10:19
*** oanson has joined #openstack-doc10:21
*** nicolasbock has joined #openstack-doc10:28
*** salv-orlando has quit IRC10:30
openstackgerritMerged openstack/openstack-manuals master: [install] add Cells and Placement API verification step  https://review.openstack.org/46200910:30
asettleaspiers: you around? :010:35
asettle:) *10:35
*** pkovar has quit IRC10:51
asettleAJaeger: I have a project idea I'd like to run by you :D10:54
*** rbowen has joined #openstack-doc10:54
*** rbowen has quit IRC11:00
openstackgerritMerged openstack/training-guides master: [upstream] fix missing line and describe voting/non-voting  https://review.openstack.org/46192911:17
*** phuongnh has quit IRC11:22
*** thorst_afk has joined #openstack-doc11:25
*** rbowen has joined #openstack-doc11:30
*** thorst_afk has quit IRC11:31
*** steveg_afk has quit IRC11:32
mpranjicasettle: morn :)11:34
asettlelo/11:36
*** rbowen has quit IRC11:42
*** pcaruana has quit IRC11:53
*** thorst_afk has joined #openstack-doc11:55
AJaegerasettle: you triggered my curiousity ;)11:56
mpranjicoh boy :)11:57
mpranjicAJaeger: you so gonna takeover some things now :D11:57
*** pcaruana has joined #openstack-doc11:57
* AJaeger runs away11:58
openstackgerritIldiko Vancsa proposed openstack/training-guides master: [upstream] Update agenda to add UC session  https://review.openstack.org/46209112:04
*** Qiming has quit IRC12:06
*** huanxie has quit IRC12:07
asettleAJaeger: hahahah okay. So. Thinking ahead a lot here - but do you think it would be possible to make the config ref a bit more autonomous? Currently we need someone to maintain it running all the auto-config scripts.12:16
asettleMy thoughts - and I dunno if it's possible or not - if we could collect those scripts in one BIG script, and run it at the end of each release.12:16
asettleIt would mean that we only update the config ref once per release cycle, but it would take away a lot of the maintenance.12:17
asettleActually, gpocentek and berendt - if either of you are around, and know if I could make this happen... ^^12:19
*** Qiming has joined #openstack-doc12:20
berendtasettle: i think it makes no difference if you call a wrapper script that calls required parameter combinations or if you manually call the script several times with different parameters12:23
asettleberendt: you know, I read that 3 times and I think I know what you said but I'm going to assume you just said "Yes, Alex. Perfect idea."12:23
asettle"Easy to implement"12:23
berendtbut i was not really involved with the config ref part in the past, i think the problem is that all flag mapping files have to be checked manually12:23
asettleYes ^ that is one of my questions/concerns.12:24
asettleIf there a way we can get around that?12:24
berendtasettle: of course ;)12:24
asettleberendt: TELL ME MORE12:24
berendthm, i do not know..12:24
asettleOkay that was anti-climatic.12:24
berendtrofl12:24
berendtlet me read the script and what we are doing at the moment.. it is a long time ago that i used it12:25
asettleberendt: what's the chances you could find out? :D12:25
asettleberendt: ah you're amazing, thanks :D12:25
*** rbowen has joined #openstack-doc12:29
*** catintheroof has joined #openstack-doc12:30
AJaegerasettle: I would love to have it fully automatic - the problem indeed are the new options, where to add them.12:32
AJaegerasettle: if we go down sfinucan's oslo.config work, we might not need to add new options since we sort it the same way as projects.12:32
berendtAJaeger: the problem is that we re-group and/or disable the configuration parameters using the flagmapping files, right?12:33
AJaegerasettle: Alternative: Thanks to oslo.config, we could push this to the projects. They could push out files after every merge as part of their publishing process.12:33
AJaegerberendt: yes, the groups - if they exist at all - are often not good enough12:33
*** nicolasbock has quit IRC12:34
berendti think it is a great idea to introduce a doc:has-config-reference tag and to move the flag mappings into the project repositories12:34
berendtit looks like we do not need the files for all projects12:34
berendthm ok nova is the only one with a disable file12:34
sfinucanberendt: More could probably use that, but nova was the one I was more familiar with12:36
openstackgerritMerged openstack/training-guides master: [upstream] Update agenda to add UC session  https://review.openstack.org/46209112:37
sfinucanberendt, AJaeger: I think I said this last week, but I thought about adding a 'category' option to the various Opt types in oslo.config12:37
berendtmaybe we should cleanup and try to disable flag mappings for as many projects as possible and afterwards we could move the remaining files into the project repositories?12:37
sfinucan...where category was a list of arbitrary categories that the opt belonged to12:38
berendtsfinucan: what is the difference between the new category and the existing group?12:38
sfinucana group is 1:N12:38
sfinucanso an opt can only belong to one group. Categories/tags would be N:M12:38
AJaegerberendt: we have options that are used by several drivers, so should show up for HW1, HW2, HW312:38
berendtah for cinder,12:38
sfinucanYup, that ^12:38
berendtbut this is the only use case for it, isn't it?12:39
sfinucanAye, but that would only make sense if more projects than cinder needed this12:39
sfinucanberendt: That is ze question :)12:39
AJaegerberendt: manila as well. and it could be in other places as well12:39
asettleAh I'm on a meeting I'll read all this backscroll real soon12:39
berendti only know this from cinder configurations.. but i do not use all new projects12:39
sfinucannova could make use of it if it was there12:39
sfinucanWe'd just have to be _very_ clear about the difference between group and category/tag though12:40
*** jpena is now known as jpena|lunch12:40
berendti think it should be easy to remove all disable flag mappings from the file by introducing some generic blacklisting/filter mechanism12:40
berendtat the moment we have > 4000 disable entries in the files12:41
sfinucanberendt: I noted the vast majority of those are oslo.* opts12:42
berendtasettle: i think it is worth to write a cross project spec for this task because we will touch other projects12:42
berendtsfinucan: i think so12:42
berendtsfinucan: at least more than 2000 contain the word oslo12:43
sfinucanberendt: I need to check, but I'm pretty sure they won't appear if we went the direction of oslo-config-generator, they wouldn't be included12:44
*** dmacpher-afk has quit IRC12:44
sfinucan...seeing as we could state which namespace to show options from (and therefore ignore all oslo namespaces)12:45
sfinucanberendt, asettle: There was a good bit of discussion on that on Friday [1]. All it needs is someone to sit down and do it [1] http://eavesdrop.openstack.org/irclogs/%23openstack-doc/%23openstack-doc.2017-04-28.log.html#t2017-04-28T14:59:1212:46
*** nicolasbock has joined #openstack-doc12:47
berendti have to move on for the moment, will read the backlog later12:47
asettleOkay lemme just read backlog here, then read backlog there, then maybe throw myself over a bridge for opening up a can of worms12:51
asettleYep12:54
* asettle goes to find a bridge12:54
asettleOkay, but seriously, this sounds pretty doable.12:54
AJaegerasettle: STOP!12:54
asettle:p12:54
asettleI joke, I joke12:54
asettleWhat repo does one write a cross-repo spec in? Governance? Or just docs and add the PTLs?12:54
AJaegerasettle: wait until you're at a place where it's wormer and you enjoy the jump and swim ;)12:54
asettleAJaeger: You mean when I go home?! :D12:55
asettleBritain has returned to its usual shitty weather.12:55
AJaegerasettle, openstack/openstack-specs12:55
asettleOh generic specs, nice.12:55
asettleThe more you know!12:55
*** nicolasbock has quit IRC13:05
*** gouthamr has joined #openstack-doc13:05
*** steveg_afk has joined #openstack-doc13:10
asettlesfinucan and berendt and AJaeger - I don't have the time to write up a cross-project spec right now. But I can work on drafting something from here: https://etherpad.openstack.org/p/config-ref-spec13:15
asettleYou all seem to know more about the technical stuff more htan I do.13:15
sfinucanasettle: I can take that so13:16
asettleYou can!?13:16
sfinucanasettle: If you want to fill that in etherpad in with your thoughts, I can flesh it out and turn it into a spec13:16
sfinucan...assuming that's what you mean13:16
sfinucan...and adding my own ideas in the process, of course :)13:17
asettleI can do the problem description and the other bits and bobs. But I"ll be a little lost when it comes to the "proposed change"13:17
asettleHow much time do you have?! You're amazing. Remind me to buy you a beer.13:17
sfinucanYup, that's fine by me13:18
sfinucanIt's all good :)13:18
asettleSWEET.13:18
asettleYou going ot the summit, btw?13:18
*** KeithMnemonic has joined #openstack-doc13:19
sfinucanYessir. There Sunday through Saturday :)13:19
asettlesfinucan: a beer it is. Find me. I'll be blonde, short, and looking probably very confused.13:20
asettleOr you know, a coke, if that's what's up.13:20
sfinucan:D beer it is13:20
asettleExcellent. You've been amazing help lately :D really, really appreciate it.13:20
*** nicolasbock has joined #openstack-doc13:22
*** rbowen has quit IRC13:23
*** salv-orlando has joined #openstack-doc13:25
*** rbowen has joined #openstack-doc13:25
*** rbowen has joined #openstack-doc13:25
asettlesfinucan AJaeger - do you think if we automate the changes for the config ref, we could potentially do the same for the cli ref?13:27
asettleHave a script that grabs all the man pages?13:27
sfinucanasettle: cli ref?13:28
asettleThe *other* guide13:28
asettlehttps://docs.openstack.org/cli-reference/13:28
*** chlong has quit IRC13:28
asettleIt also uses scripts.13:28
asettlehttps://docs.openstack.org/contributor-guide/doc-tools/cli-reference.html13:28
asettleSee hurr ^13:28
asettle\13:28
asettleThese are two guides I'm hoping to get to be a bit more autonomous. They're pretty high maintenance for a bunch of auto-scripted stuff.13:29
sfinucanasettle: I think my 'cliff.sphinxext' extension could be modified to do that for us -> https://docs.openstack.org/developer/cliff/sphinxext.html13:30
dhellmann++13:31
asettlesfinucan: *gasp*13:31
asettleTWO BEERS FOR YOU13:31
* asettle claps13:31
asettledhellmann: hey pal. Welcome!13:31
sfinucanI'm already using the directive for python-openstackclient, but nobody says the extension has to be used as a directive https://review.openstack.org/#/c/452861/13:32
sfinucanlemme draft something real quick13:32
dhellmannasettle : you have to get in line to buy sfinucan beer; I owe him one for taking that task off of my todo list13:32
asettledhellmann: hahahaha meet at the lobby on Thursday and I'll fight you for it :p13:32
asettle(okay not seriously, I'm very weak)13:32
asettlesfinucan: *gasp*13:32
asettleAmazing13:32
asettleThank you :D13:32
dhellmannsfinucan : write a new directive that generates rst with the existing directive? recursion all the way down13:32
*** rejy has quit IRC13:33
dhellmannasettle : thumb wrestle?13:33
asettlePerfect. Got really strong thumbs from all this 'space bar' pressing I've done over the years :p13:33
dhellmannaw, I should have seen that coming13:33
asettleHahahhahaa13:33
* dhellmann will be outmatched13:33
asettleAlthough it's weirdly with my left thumb. You very well might best me!13:33
asettledhellmann: we are drafting: https://etherpad.openstack.org/p/config-ref-spec13:34
dhellmannwe can rematch with pinkies (emacs user)13:34
asettleI've taken your idea of using etherpads to write up specs.13:34
asettledhellmann: oh no! Ookay. Then you'll win13:34
asettleAlso. Who USES emacs?!13:34
dhellmannI would like to be included in the discussion on that. I has ideas.13:34
asettledhellmann: please, please, type away.13:34
asettleYou can see my amazing 4 line description of not much.13:34
dhellmannwhatever you need, we'll build into oslo.config13:35
asettle:O13:35
asettleYou should see my face right now, it's like you just gave me lots and lots of wine13:35
asettle:D13:35
dhellmannin fact, you should probably review what's already possible13:35
*** KeithMnemonic has quit IRC13:35
asettledhellmann: where ?!13:35
dhellmannhttps://docs.openstack.org/developer/oslo.config/sphinxext.html13:35
dhellmannwe're using it in some of the in-tree guides now13:35
dhellmannwe probably have >50% of what you'd need13:36
dhellmannalso https://docs.openstack.org/developer/oslo.config/sphinxconfiggen.html13:36
dhellmannthe simplest solution may be to not have 1 guide, but to have a guide per project13:36
asettleOkay, so, like... I don't know anything about oslo.config so this is wonderful that it's documented.13:36
dhellmannthough I don't know your current philosophy on that, or user needs13:36
asettleHmmm 1 guide per project might work. Then we could have a 'config reference' section (like the install guides)13:37
asettleI'm happy to do that.13:37
asettleBut we just need to make it manageable. I don't want to add anything that can't be managed without simplicity. That's my entire goal at the moment.13:37
dhellmannif set create a template for the guide, then it's mostly a matter of making sure the build steps for each project read in the right set of values13:38
dhellmannlet me see if I can find someone using this already13:38
asettle*gasp*13:38
asettlePlease do.13:38
dhellmannoh, a bunch of projects have started: http://codesearch.openstack.org/?q=show-options&i=nope&files=&repos=13:38
asettleI could apply this to the cli-ref and config ref? Or just cli ref?13:38
dhellmannasettle : here are the old notes from the rollout: https://etherpad.openstack.org/p/automating-oslo-config-documentation13:39
asettleInteresting! So. I mean, I am pretty naive here - I don't really understand how .. show-options works?13:39
dhellmannprobably not that up to date13:39
asettleIt's an include?13:39
asettle*gasp* so, this was already started.13:39
dhellmannasettle : because all of these automation solutions tend to depend on having the software installed, I recommend that you have a separate guide per project, in-tree13:40
dhellmannthe show-options sphinx directive is another interface to the sample config generator, it just produces different output format13:40
dhellmannso you install the software you want, then it uses code introspection and plugin discovery mechanisms to find the options, and then it renders nice output13:41
*** jpena|lunch is now known as jpena13:41
dhellmannI believe sfinucan's thing works a similar way13:41
asettleInteresting! Okay. So we could do it similarly to the install and deploy guides. Separate guides, in tree, published using new gates on the docs.o.o site13:41
dhellmannright13:41
sfinucandhellmann: Yup, having the software installed is the issue13:41
asettleOkay, so, catch me up here - how do we get that software installed?13:42
sfinucanthat's why we couldn't have a recursive directive13:42
dhellmannso then the question is, do we want a separate sphinx build for each of these little things, or do we want one "not developer" doc build that includes sections13:42
dhellmannasettle : oh, just "tox"13:42
sfinucanasettle: tox -e venv [commands here]13:42
asettleOh right! Easy.13:42
sfinucanin pretty much any project13:42
dhellmannyeah, so you don't have to think about that13:42
asettledhellmann: I'd rather avoid separate sphinx builds, to be hoenst.13:42
asettleOh phew.13:42
dhellmannme, too13:42
asettleOkay. "not developer" doc build it is.13:43
dhellmannI like the idea of docs.openstack.org/not-developer/nova13:43
dhellmannfun name13:43
asettleVery catchy.13:43
asettle:p13:43
sfinucandhellmann, asettle: as would most users, I guess. Having a central config guide is super important for them, I'm told13:43
asettleNo confusion what-so-ever.13:43
asettleOkay, well, that's good user info.13:44
dhellmannsfinucan : we could still have a central page to reach all of the config guides from one place13:44
*** lucasxu has joined #openstack-doc13:44
dhellmannasettle : will you be in boston next week?13:44
asettlesfinucan: similar to how you reach the deploy guides: https://docs.openstack.org/project-deploy-guide/ocata/13:44
asettledhellmann: you bet.13:44
asettleYou?13:44
dhellmanncool, let's find some time to sit down and talk about this13:44
sfinucandhellmann: This is true. I was thinking more about configurations that are kind of cross-project13:45
asettleOkay, that sounds good :) I am crazy on Monday, and then I appear to only have one session Tues/WEd. So, Around that :)13:45
dhellmannsfinucan : that's a good point, if we have a bunch of those we'd have to decide how to address them13:45
asettlesfinucan: well, that opens up a whole new kettle of fish.13:45
sfinucani.e. if you want to use SR-IOV networking, that require config changes to both nova and neutron13:45
asettlesfinucan: option Z: Don't use SR-IOV networking :)13:45
asettleThat's not going to happen, is it?13:46
sfinucanasettle: Shh - I'd be out of a job if so13:46
sfinucan;)13:46
asettleHhahaha okay sorry13:46
asettleEVERYONE USE IT13:46
asettleSR-IOV13:46
asettleWOO13:46
sfinucanbetter13:46
dhellmannasettle : tue works for me, I have a bunch of logging stuff on wed13:46
dhellmannsfinucan : those instructions would go into the sr-iov guide, right?13:46
asettleOkay, let's doooo Tues morning?13:46
* sfinucan raises hand to join13:46
sfinucanTuesday is also fine with me, afaik13:46
asettleExcellent, please do. Maybe we should find a pub then :P I can do two birds, one stone.13:47
dhellmannasettle, sfinucan : were you planning to watch the keynotes, or would you like to meet then?13:47
asettledhellmann: I admit I usually don't go unless there's something that takes my interest.13:47
dhellmannworks for me13:47
sfinucandhellmann: RE: "would they go in the SR-IOV guide", good point13:47
sfinucanAlso, the config guide is already broken down by project, I see13:48
asettleProbs skip on the pub at 9am then13:48
sfinucanYup, works for me too13:48
asettlesfinucan: yes it is, so is the CLI guide.13:48
asettleSo, its' all sectioned. We just kinda need to make it... happen.13:48
dhellmannasettle : it's always 5:00 somewhere13:48
asettledhellmann: that's such a beautiful attitude.13:48
dhellmannI don't suppose there's any chance either of you is staying at the marriott? breakfast?13:49
dhellmannif not we can meet at registration and figure out where to go from there13:49
asettledhellmann: uhhhh13:50
asettleGood quesiton13:50
asettleLemme check13:50
asettleBoston Park Plaza Hotel - sorry13:50
asettleThat's the conf hotel though I think13:50
dhellmannok, np13:50
* dhellmann looks at his conference map13:51
sfinucanWestin, for me13:52
asettleYou are so organised. I didn't even know there was a conf map13:52
dhellmannlet's just plan to meet near registration. I don't know if the lounges will be open, but we'll know by Tuesday and can go there if they are. If not, we'll go off site and find a donut or something.13:52
dhellmann9:00?13:53
asettle9.00, Tuesday13:53
asettlePerfect.13:53
* asettle writes it on a post-it13:54
asettleYou guys are probably going to have to walk me through more than I'd like to admit right now.13:54
asettleBut learning!13:54
dhellmannno problem, we can talk about how the tools work and then sketch out a plan to get things implemented13:55
AJaegerasettle: the cli-ref could life as well in project repos - like the openstack client already does13:55
dhellmannAJaeger: will you be in boston next week? it'd be good to have you join this discussion if you're free13:56
asettleAJaeger: that's my thoughts right now too. But I still think we should publish on docs.o.o13:56
asettledhellmann: that's a good idea :) thank you. I really appreciate your support.13:56
dhellmannasettle : don't tell anyone, but the docs team is my favorite ;-)13:56
asettle\o/13:56
asettleIt's cause we're really nice, obvs.13:57
*** steveg_afk has quit IRC13:57
sfinucandhellmann: If you'd be so kind, a gcal invite would be super helpful13:57
dhellmannfer sur13:57
spotzdhellmann: I'm telling13:57
asettlespotz: shushhhhh pleaseeeeeee13:58
asettle:p13:58
spotzhehe13:58
* sfinucan has an awful tendency to forget things that aren't his own name13:58
dhellmannsfinucan : good idea13:58
dhellmannI have to run, but I'll send the invitation when I get back in a bit13:58
asettleSounds good :) thanks dhellmann !13:58
sfinucan(y) ta13:58
asettleJeez that's a long time since I've see a (y)13:58
*** dustins has joined #openstack-doc13:58
sfinucanasettle: A habit from my days using Lync (:shudder:)14:00
sfinucanFortunately, it also works on Messenger and WhatsApp, so all is not lost14:00
AJaegerdhellmann: can't make it ;(14:01
AJaegerdhellmann: seeing the discussion above, I'm confident you don't need me ;)14:01
asettlesfinucan: wow I remember it from MSN14:02
* asettle is now old14:02
*** lucasxu has quit IRC14:02
asettleI've never felt old until now14:02
spotzPoor asettle14:02
*** lucasxu has joined #openstack-doc14:02
asettleThanks spotz14:03
asettleI'm on the other side of 25 now.14:03
asettleWell, soon.14:03
asettleOkay not soon. But SOON ENOUGH14:03
spotzyeah lets not go there...14:03
asettleHhahahahah <314:04
*** rbowen has quit IRC14:13
*** lucasxu has quit IRC14:15
*** lucasxu has joined #openstack-doc14:17
*** openstackgerrit has quit IRC14:18
*** lucasxu has quit IRC14:24
*** lucasxu has joined #openstack-doc14:24
*** amotoki has joined #openstack-doc14:26
*** lucasxu has quit IRC14:26
*** yangyape_ has joined #openstack-doc14:27
*** rbowen has joined #openstack-doc14:30
*** yangyapepeng has quit IRC14:30
*** openstackgerrit has joined #openstack-doc14:33
openstackgerritGergely Csatari proposed openstack/training-guides master: [upstream] Some corrections to the Governance slides  https://review.openstack.org/46183114:33
asettleLol dhellmann I love that you actually documented "not-developer"14:35
dhellmann:-)14:36
dhellmannI did say we'd give it a better name14:36
asettleHhahahaha14:36
dhellmannshould I put you down for the "choosing a good name" task?14:37
asettleOh gosh please no14:37
asettleI'm shocking at naming things14:37
dhellmanndocy mcdocface?14:38
asettleStunning.14:39
asettleMaybe we could just do a naming pole. Get mordred to run another one for us14:39
asettlepole?!14:39
asettlePOLE!?14:39
asettleWho HIRED ME14:39
asettlePoll*14:39
* dhellmann wasn't going to point that out14:39
asettle*head desk*14:40
asettleHow embarrassment.14:40
openstackgerritMerged openstack/training-labs master: Fix description for st.py -e option  https://review.openstack.org/46164414:46
asettleOkay, dhellmann I have some thoughts. Maybe we should consider moving this proposed guide to the dev.o.o site?14:48
dhellmannasettle : ok, I think I've done my brain dump in there14:48
dhellmanndev.o.o? or docs.o.o?14:48
asettlehttps://developer.openstack.org/ dev14:48
asettleIt sounds like it almost fits better in there.14:48
dhellmannhmm. where is the existing configuration guide?14:49
asettledocs14:49
dhellmannthese things would replace that, right?14:49
asettleI suppose we don't want to uproot it and cause confusion.14:49
asettleYep.14:49
dhellmannwhat do you have now for per-project installation guides?14:49
*** fragatina has joined #openstack-doc14:49
dhellmannhow does that work? a separate sphinx build?14:49
dhellmannthat's the sort of thing I would expect to fold into this new guide at some point14:50
asettledhellmann: cookie cutter and separate gating. See: https://docs.openstack.org/contributor-guide/project-guides.html14:50
asettleYep, okay, maybe we should just use the existing infrastructure.14:50
dhellmannah, so it's in an install-guide subdir14:50
asettleYep - would that work with what you're thinking?14:50
asettleAlso, who's the orange? is that you sfinucan ?14:50
dhellmannI wonder if we want to just use that? add a new section to those things?14:50
dhellmannI'm grey14:51
asettleThat's what I was thinking when talking to sfinucan earlier.14:51
dhellmannthe little chart at the top shows sfinucan as orange14:51
asettleAH, it was blank before :)14:51
sfinucanasettle: Yup, set my name now14:51
asettlethanks sfinucan14:51
asettleNow, who's the green guy14:51
asettleIs that you AJaeger ?14:51
dhellmannprobably, based on the context of the comment14:52
AJaegerasettle: might have been ;)14:53
*** salv-orl_ has joined #openstack-doc14:53
* AJaeger reopens etherpad and adds a name14:53
asettleThanks AJaeger :P14:53
asettleOh! I didn't see the conext of the comment14:54
asettlegpocentek: when you get a chance, have a wee looksie at: https://etherpad.openstack.org/p/config-ref-spec14:54
*** salv-orlando has quit IRC14:56
sfinucandhellmann: I was going to wait to discuss this next week, but thoughts on the last alternative? Solves the issues with the third alternative by not needing installation at doc compile time - only when you want to update the configuration guides14:56
*** annegentle has joined #openstack-doc14:59
aspiersasettle: here now15:05
asettleaspiers: hey, so, we'll need to find some chat to talk about all the newly created ha-guide-draft bugs.15:06
asettleAnd what we're going to do now.15:06
asettledhellmann: "Introduction paragraph -- why are we doing anything?" - deliberately vague?!15:08
*** chlong has joined #openstack-doc15:16
aspiersasettle: for sure! Can it wait until you are here? I'm desperately trying to get my presentations ready :-/15:17
asettleaspiers: yep! That's what I mean :) sync up some time at the summit.15:17
aspiersand I can't remember what deadline I promised you for the reno stuff but I just remembered I've probably blown it already :-(15:17
*** salv-orl_ has quit IRC15:18
aspiersI'm currently having to do all the heavy lifting for both presentations15:18
*** salv-orlando has joined #openstack-doc15:18
asettleaspiers: no problem :) concentrate on what you gotta do. We'll work it out later :) don't sweat it.15:19
aspiersmy co-presenters both have annoyingly cast-iron excuses, like "just had a new baby" and "critical production outages"15:19
aspierscool, thanks :)15:19
asettleHow dare they have babies and production outages ;P15:19
aspiersexactly, so considerate15:19
asettleNo problem dude - sorry to add extra pressure to your workload.15:19
aspierserr, inconsiderate15:19
asettle*shakes head*15:20
aspiersasettle: I absolutely promise you will get my attention next week :)15:20
gpocentekoh my, so much to read!15:20
asettlegpocentek: yep! It's very exciting in here today15:20
annegentlegpocentek :)15:20
asettleaspiers: we'll sync up at some time :) no sweat.15:20
asettleannegentle: wanna get involved?! :p15:20
gpocentekasettle: an idea cam to ming while reading the backlog15:21
asettle... what/15:21
asettle?*15:21
asettlean idea came to you!15:21
gpocentekcame to mind15:21
asettleHhahaha yep, got that in the end :p15:21
gpocentekoh my... let me get my good hands15:21
asettleWhat's your idea?15:21
dhellmannsfinucan : I replied in the etherpad15:21
*** rbowen has quit IRC15:21
asettleFEel free to offer ideas up in our etherpad :) I linked you to it15:21
gpocentekI'll use the etherpad, yes15:22
sfinucandhellmann: Can't argue with that :)15:22
dhellmannasettle : I'm not sure what you mean about the introduction paragraph?15:22
sfinucan#automateALLthethings15:22
asettledhellmann: oh, that was just what was in the template from openstack-specs15:22
asettleI was confused too.15:22
asettleBut I ended up deleting it, it just seemed redundant.15:22
dhellmannaspiers : no worries on deadlines, I know we all have lots going on. And I don't remember any dates, either. It'll get done when it's done.15:23
dhellmannasettle : ah15:23
aspiersdhellmann: thanks for the calming words ;-)15:25
*** rbowen has joined #openstack-doc15:25
asettleaspiers: he's the chill one in here15:25
aspiershaha, at least someone is :)15:25
gpocentekaspiers: I see my idea in the spec actually, I think (very very long day so I will need to read again)15:27
gpocenteksfinucan dhellmann could the sphinx extension allow to create custom list of options?15:28
gpocentekthis could help solving the cinder ref problem (single option in multiple tables)15:29
gpocentekaspiers: sorry the message was for asettle15:29
aspiersgpocentek: np :)15:29
sfinucangpocentek: Not at the moment, no15:29
sfinucanI don't know if we'd want that either - it would necessitate manual wrangling again15:30
sfinucanIf we _did_ want it though, it could be easily added15:30
*** KeithMnemonic has joined #openstack-doc15:31
asettleThanks gpocentek :)15:32
dhellmanngpocentek : the sphinx extension uses the same mechanism as the sample config generator, right now.15:34
*** rbowen has quit IRC15:35
sfinucandhellmann, asettle: Do we want another spec for the CLI guide, or will we roll it into that15:35
sfinucanSame mechanism for both, I'd assume?15:35
dhellmannsfinucan : I was thinking about that. Do we need more than one guide? Isn't that just "the cli guide for python-openstackcclient"?15:36
dhellmannor do you mean for the project-specific clients?15:36
sfinucandhellmann: the latter. The former is already handled by the python-openstackclient docs15:36
dhellmanndoes your sphinx extension work for those clients, though?15:37
dhellmannor would we need something new?15:37
sfinucanIt should, assuming they're all using cliff15:37
dhellmannalmost none of them do15:37
sfinucan...which they should be15:37
sfinucanOh?15:37
dhellmannonly neutron does, afaik15:37
asettlesfinucan: I would have said same mechanism for both.15:37
dhellmannthe others were all written before cliff existed15:37
dhellmannthey use argparse directly, iirc15:37
asettlehave the same mechanism*15:38
asettleGosh I can't type.15:38
sfinucanOh, damn15:38
sfinucanYup, nova client is using the same hackery that nova-manage and it's ilk do15:39
* sfinucan would like to fix them but it would take forever and these clients are supposed to be going away15:39
asettleOkay. So. What do?15:40
dhellmannwe should be able to use some of the work sfinucan has already done to build an extension that works by getting the argument parser15:43
dhellmannthen we can modify the clients to have an API to return that, and set up the builds to call that new API15:43
sfinucanpython-fuelclient, python-rackclient, python-neutronclient, python-barbicanclient, python-vitrageclient, python-aodhclient, python-freezerclient, python-congressclient, python-heatclient, python-watcherclient, python-designateclient, python-mistralclient15:44
dhellmannit's more work, but we can at least reuse some of the formatting code15:44
asettleWell, that's pretty good :)15:44
sfinucanpython-kingbirdclient, python-group-based-policy-client, python-cueclient python-appcatalogclient python-octaviaclient python-glareclient python-saharaclient python-tricircleclient python-tripleoclient python-troveclient15:45
sfinucanI think that's it :)15:45
dhellmannlet's discuss this next week; I've got a reno bug blocking a project so I need to debug that15:45
asettleAlso, with relation to your 'not developer' guide in each project, I think we should just keep it as $PROJECT Configuration Reference15:45
sfinucantbf, that does cover a lot of the what's in the config guide15:45
sfinucanyup, next week it is15:45
*** KeithMnemonic has quit IRC15:56
openstackgerritGergely Csatari proposed openstack/training-guides master: [upstream] Some corrections to the Governance slides  https://review.openstack.org/46183116:08
*** KeithMnemonic has joined #openstack-doc16:12
*** KeithMnemonic has quit IRC16:13
*** rbowen has joined #openstack-doc16:16
*** pcaruana has quit IRC16:24
*** andreas_s has quit IRC16:25
*** erikmwil_ has quit IRC16:31
*** tesseract has quit IRC16:38
*** jpena is now known as jpena|off17:06
*** lucasxu has joined #openstack-doc17:12
*** annegentle has quit IRC17:24
*** zul has quit IRC17:26
*** zul has joined #openstack-doc17:29
*** thorst_afk is now known as thorst17:34
*** mtreinish has quit IRC17:46
*** fragatina has quit IRC17:49
*** annegentle has joined #openstack-doc17:55
*** rbowen has quit IRC17:57
*** annegent_ has joined #openstack-doc17:59
*** annegentle has quit IRC18:02
*** mtreinish has joined #openstack-doc18:05
*** donghao has joined #openstack-doc18:09
*** cbsterrett has joined #openstack-doc18:09
*** Syed__ has joined #openstack-doc18:10
*** lucasxu has quit IRC18:11
*** lucasxu has joined #openstack-doc18:11
*** salv-orlando has quit IRC18:12
*** rbowen has joined #openstack-doc18:13
*** steveg_afk has joined #openstack-doc18:14
*** donghao has quit IRC18:15
*** fragatina has joined #openstack-doc18:21
*** rbowen has quit IRC18:24
*** annegent_ has quit IRC18:40
*** annegentle has joined #openstack-doc18:41
*** annegentle has quit IRC18:51
-openstackstatus- NOTICE: Gerrit on review.openstack.org is being restarted to accomodate a memory leak in Gerrit. Service should return shortly.18:52
*** annegentle has joined #openstack-doc18:54
*** steveg_afk has quit IRC18:55
*** salv-orlando has joined #openstack-doc19:41
*** steveg_afk has joined #openstack-doc19:50
*** rbowen has joined #openstack-doc20:05
*** donghao has joined #openstack-doc20:12
*** rbowen has quit IRC20:15
*** donghao has quit IRC20:18
*** catinthe_ has joined #openstack-doc20:21
*** catintheroof has quit IRC20:24
*** lucasxu has quit IRC20:28
*** catinthe_ has quit IRC20:45
*** salv-orl_ has joined #openstack-doc20:56
*** salv-orlando has quit IRC20:59
*** csterret_ has joined #openstack-doc21:00
*** csterret_ has quit IRC21:00
*** dustins has quit IRC21:05
*** thorst has quit IRC21:13
*** Syed__ has quit IRC21:15
*** chlong has quit IRC21:17
openstackgerritIan Y. Choi proposed openstack/training-guides master: [upstream] Governance - AUC and election activies  https://review.openstack.org/46190221:19
*** thorst has joined #openstack-doc21:38
*** thorst has quit IRC21:43
*** csterret_ has joined #openstack-doc21:59
*** cbsterrett has quit IRC22:02
*** gouthamr has quit IRC22:07
*** fragatin_ has joined #openstack-doc22:21
*** ediardo_ has joined #openstack-doc22:23
*** cmurphy_ has joined #openstack-doc22:23
*** mikal_ has joined #openstack-doc22:26
*** igordcar1 has joined #openstack-doc22:26
*** dmacpher has joined #openstack-doc22:26
*** cmurphy has quit IRC22:26
*** cmurphy_ is now known as cmurphy22:26
*** alex_xu_ has joined #openstack-doc22:27
*** tdasilva- has joined #openstack-doc22:28
*** alex_xu has quit IRC22:28
*** ediardo has quit IRC22:28
*** fragatina has quit IRC22:28
*** mikal has quit IRC22:28
*** igordcard has quit IRC22:28
*** tdasilva has quit IRC22:28
*** d0ugal has quit IRC22:28
*** ediardo_ is now known as ediardo22:29
*** gouthamr has joined #openstack-doc22:31
*** salv-orl_ has quit IRC22:32
openstackgerritPranav Salunke proposed openstack/training-labs master: Update tarballs to include python scripts.  https://review.openstack.org/46231122:41
*** annegentle has quit IRC22:51
*** d0ugal has joined #openstack-doc22:52
*** charcol has joined #openstack-doc23:00
*** csterret__ has joined #openstack-doc23:10
openstackgerritIan Y. Choi proposed openstack/training-guides master: [upstream] Add a note for screen in DevStack  https://review.openstack.org/46231523:10
*** csterret_ has quit IRC23:13
*** csterret__ has quit IRC23:13
*** adisky has quit IRC23:19
*** suyog has joined #openstack-doc23:31
*** bmoss has joined #openstack-doc23:36
*** thorst has joined #openstack-doc23:58
*** thorst has quit IRC23:58

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