Tuesday, 2017-07-25

*** masaki has joined #openstack-doc00:02
*** thorst_afk has quit IRC00:03
*** charcol has joined #openstack-doc00:09
*** gmann has quit IRC00:14
*** gmann has joined #openstack-doc00:14
*** annegentle has quit IRC00:24
*** fragatina has quit IRC00:45
*** fragatina has joined #openstack-doc00:46
*** catintheroof has joined #openstack-doc00:47
*** fragatin_ has joined #openstack-doc00:49
*** fragatin_ has quit IRC00:50
*** fragatina has quit IRC00:50
*** fragatin_ has joined #openstack-doc00:50
*** fragatin_ has quit IRC00:52
*** fragatina has joined #openstack-doc00:52
*** fragatina has quit IRC00:56
*** phuongnh has joined #openstack-doc01:02
*** catintheroof has quit IRC01:18
*** fragatina has joined #openstack-doc01:25
*** fragatina has quit IRC01:29
*** dmacpher has joined #openstack-doc01:37
*** chlong_ has joined #openstack-doc01:45
*** chlong__ has quit IRC01:47
*** chlong__ has joined #openstack-doc02:07
*** chlong_ has quit IRC02:07
*** fragatina has joined #openstack-doc02:16
*** chlong_ has joined #openstack-doc02:25
*** chlong__ has quit IRC02:27
*** fragatina has quit IRC02:34
*** suyog_ has joined #openstack-doc02:42
*** suyog has quit IRC02:44
*** gouthamr has quit IRC02:46
*** fragatina has joined #openstack-doc02:55
*** lbragsta_ has joined #openstack-doc03:03
*** harsh_ has joined #openstack-doc03:06
*** harsh_ is now known as vharsh03:07
*** vharsh is now known as Guest1493603:07
*** fragatina has quit IRC03:12
*** fragatina has joined #openstack-doc03:23
*** chlong_ has quit IRC03:28
*** chlong__ has joined #openstack-doc03:28
*** yamamoto has quit IRC03:45
*** lbragsta_ has quit IRC03:48
*** charcol has quit IRC03:58
*** Guest14936 has quit IRC03:58
*** yamamoto has joined #openstack-doc04:00
*** chlong__ has quit IRC04:01
*** chlong_ has joined #openstack-doc04:01
*** nicolasbock has joined #openstack-doc04:13
*** chlong__ has joined #openstack-doc04:25
*** chlong_ has quit IRC04:27
*** thorst_afk has joined #openstack-doc04:38
*** thorst_afk has quit IRC04:43
*** Guest14936 has joined #openstack-doc04:50
*** charcol has joined #openstack-doc04:51
*** masaki has quit IRC04:53
*** masaki has joined #openstack-doc04:53
openstackgerritAndreas Jaeger proposed openstack/openstack-manuals master: add user landing pages for older releases  https://review.openstack.org/48667005:06
*** chlong_ has joined #openstack-doc05:33
*** chlong__ has quit IRC05:34
*** Guest14936 is now known as vharsh06:06
*** rcernin has joined #openstack-doc06:10
*** andreas_s has joined #openstack-doc06:22
*** thorst_afk has joined #openstack-doc06:39
*** belmoreira has joined #openstack-doc06:43
*** thorst_afk has quit IRC06:44
*** suyog_ has quit IRC06:56
*** alexchadin has joined #openstack-doc06:59
*** AJaeger has quit IRC07:20
*** dmacpher has quit IRC07:23
*** charcol has quit IRC07:46
*** AJaeger has joined #openstack-doc07:59
*** efoley has joined #openstack-doc08:00
*** AJaeger has quit IRC08:01
*** AJaeger has joined #openstack-doc08:03
*** yamamoto has quit IRC08:33
openstackgerritAlexandra Settle proposed openstack/openstack-manuals stable/newton: [install-guide] Adds memcached instructions to obs guide  https://review.openstack.org/48694208:38
openstackgerritAlexandra Settle proposed openstack/openstack-manuals stable/ocata: [install-guide] Adds memcached instructions to obs guide  https://review.openstack.org/48694308:39
*** thorst_afk has joined #openstack-doc08:40
asettleAJaeger: ^^ could you please grab those backports08:41
asettleSee: https://bugs.launchpad.net/keystone/+bug/1587777 for context if necessary08:41
openstackLaunchpad bug 1587777 in OpenStack Identity (keystone) "Mitaka: dashboard performance" [Undecided,New]08:41
AJaegerasettle: thanks, done08:45
asettleThank you :)08:45
*** thorst_afk has quit IRC08:45
AJaegerasettle: could you review dhellmann's series of changes to get rid of the 404s, please?08:45
asettleAJaeger: on it as we speak :)08:45
AJaegergreat!08:45
*** yamamoto has joined #openstack-doc08:46
AJaeger486210, 486294, 475227 are ready as well - but I might be biased on mine ;)08:47
openstackgerritMerged openstack/openstack-manuals stable/newton: [install-guide] Adds memcached instructions to obs guide  https://review.openstack.org/48694208:48
asettleAJaeger: you caught me looking at it :p08:49
asettleOkay, I think it should start falling now08:49
asettleI can't see anymore08:49
*** yamamoto has quit IRC08:50
vharshBroken link -> https://docs.openstack.org/api/ found on -> https://docs.openstack.org/ocata/08:51
AJaegerLet's merge and publish -  and then review later whether the index pages are fine again...08:51
asettlevharsh: currently working on08:51
AJaegervharsh: asettle just approved changes to correct this, please wait until publishing is done08:51
openstackgerritMerged openstack/openstack-manuals stable/ocata: [install-guide] Adds memcached instructions to obs guide  https://review.openstack.org/48694308:51
asettleAJaeger: okay08:51
AJaegervharsh: should be fixed in two hours08:51
vharshAJaeger, Thanks :)08:51
AJaegervharsh: thanks for reporting08:51
vharshAJaeger, I couldn't find the OpenStack book also Link -> https://docs.openstack.org/ops-guide/preface.html08:52
asettlevharsh: the operations guide was deleted - email was sent out a week or so ago?08:52
asettleYou can find it (if necessary) in the before-migration tag in the openstack-manuals github repo :)08:52
asettleWe are attempting to migrate that doc to the openstack wiki08:52
asettleAnd by 'we', I mean, the operators08:52
vharshThanks asettle :)08:52
asettlenp - sorry for all the disruption, we're working on it all :D08:53
asettleAJaeger: what's next?08:54
openstackgerritMerged openstack/openstack-manuals stable/ocata: Update and expand cells config doc warning  https://review.openstack.org/48672408:54
openstackgerritMerged openstack/openstack-manuals master: run the link checks in parallel  https://review.openstack.org/48672808:54
openstackgerritMerged openstack/openstack-manuals master: add SERIES_TITLE template variable  https://review.openstack.org/48620908:55
openstackgerritMerged openstack/openstack-manuals master: add options to template generator to make it easier to only test links  https://review.openstack.org/48672908:55
openstackgerritMerged openstack/openstack-manuals master: remove series pages for EOL series  https://review.openstack.org/48673008:55
asettleAh, here the yare08:55
asettlethey are*08:55
openstackgerritMerged openstack/openstack-manuals master: add admin landing pages for older series  https://review.openstack.org/48666708:55
openstackgerritMerged openstack/openstack-manuals master: remove link to ops-guide from series landing pages  https://review.openstack.org/48666808:55
openstackgerritMerged openstack/openstack-manuals master: add api landing pages for older releases  https://review.openstack.org/48666908:55
AJaegerasettle: release notes is one discussion to have - with dhellmann later.08:55
openstackgerritMerged openstack/openstack-manuals master: add user landing pages for older releases  https://review.openstack.org/48667008:55
AJaegerasettle: I just read your comment on my change08:55
openstackgerritMerged openstack/openstack-manuals master: [www] Add install-guide for ceilometer  https://review.openstack.org/48629408:55
asettleAJaeger: yes absolutely. I just wanted to put my thoughts down08:55
asettleI'm happy to iterate08:55
openstackgerritMerged openstack/openstack-manuals master: [install-guide] The guide is version independent  https://review.openstack.org/48621008:56
AJaegernot sure what else is urgently needed - most should be on the futures etherpad. Will check back this evening again.08:56
*** yamamoto has joined #openstack-doc08:57
openstackgerritMerged openstack/openstack-manuals stable/ocata: Update HyperVNovaCompute download  https://review.openstack.org/47522708:58
openstackgerritMerged openstack/openstack-manuals stable/ocata: Update the "neutron auto-allocated-topology-show" output  https://review.openstack.org/47569708:59
*** masaki has quit IRC09:02
asettleAJaeger: thanks :)09:03
*** yamamoto has quit IRC09:05
*** yamamoto has joined #openstack-doc09:11
openstackgerritRob Cresswell proposed openstack/openstackdocstheme master: Serve minified CSS  https://review.openstack.org/48695609:20
robcresswellAJaeger, dhellmann, asettle: ^^ Thats my suggestion for serving minified CSS. It's fairly thoroughly explained in the commit message, though I may have misunderstood the requirements for stricter packaging ecosystems, like Debian.09:27
robcresswellminified css / js09:27
asettleThanks robcresswell :) I'll get around to it shortly09:27
*** yamamoto has quit IRC09:28
*** chlong__ has joined #openstack-doc09:33
*** chlong_ has quit IRC09:35
*** yamamoto has joined #openstack-doc09:36
*** yamamoto has quit IRC09:40
*** yamamoto has joined #openstack-doc09:44
*** yamamoto has quit IRC09:48
*** reed has quit IRC09:55
*** reed has joined #openstack-doc09:56
*** sambetts|afk is now known as sambetts10:06
*** phuongnh has quit IRC10:08
*** yamamoto has joined #openstack-doc10:13
*** openstackgerrit has quit IRC10:17
*** alexchadin has quit IRC10:22
*** thorst_afk has joined #openstack-doc10:24
dhellmannasettle, AJaeger : o/10:29
asettledhellmann: up early!10:29
asettleMalcolm...10:29
dhellmannactually, hungry human today10:30
dhellmannasettle : do you have time to have the release notes conversation or archiving conversation?10:31
* dhellmann goes to check the kettle10:31
asettledhellmann: yeah man, you've got me for half an hour before I run off to lunch.10:31
asettleI'm fighting with the nova docs10:31
asettleI may just give up10:31
dhellmannthat's the spirit!10:32
asettleI thought so10:32
dhellmannlet's do release notes first10:32
* asettle sits up straighter10:32
asettleOkay10:32
dhellmannwe're using reno for those, right?10:32
asettleWe are indeed now, yes10:32
dhellmannok10:32
dhellmannwithout branches, we'll need to maintain the list of versions for each series ourselves10:33
dhellmannthat's not a big deal, but it's one more thing to do10:33
dhellmannso if we want series-specific pages, it's possible10:33
asettledhellmann: so, reno isn't exactly entirely necessary for docs now - I mean, we included it at the beginning of this release because originally we were fumbling around with a million guides.10:33
dhellmannI don't feel strongly one way or the other for now10:33
asettlePrior to that we just wrote them manually per-release10:33
dhellmannbut yeah, that's also true10:33
dhellmannwe could just switch to writing the notes on the pages10:33
dhellmannthat may actually be easier for folks to keep up with10:34
asettleI guess my point is, it would be easier to write something in a structured format (per cycle) than it would be for a reader to go 'oh wiat, what release was this?!'10:34
dhellmannyeah, reno will work, but it may be overkill10:34
asettleLittle bit. It made sense when we had *all the things*10:34
dhellmannright10:34
asettleI guess I don't also want the release notes to be the responsibility of the PTL at the end of each release either10:35
dhellmannok, so then maybe the plan is to migrate away from reno to just using regular rst pages10:35
dhellmannyou'd still ask people to add release notes with their regular content changes, they would just not be reno files10:35
asettleomfg I think the nova docs just built omfg *passes out*10:35
asettleWe have admittedly been very bad at that in the past.10:35
asettleBut we would just have to ensure otherwise.10:35
asettleWhich should be simple enough10:35
dhellmannyeah, deciding whether to use reno won't really have any bearing on that :-)10:36
dhellmannshall I put this down on the "future" page then?10:36
dhellmannasettle : what do you think about the idea of having release notes for each guide *in* that guide?10:37
asettleLet's.10:37
asettledhellmann: that's not a bad idea, I could float with that.10:37
dhellmanna "history" or whatever10:37
dhellmannok, noted10:38
dhellmannline 60 if you're reading along10:38
dhellmannso, talk to me about the requirements behind archiving10:38
asettledhellmann: So, this discussion was chiefly Lana's domain, but I'll hand you what I know...10:40
asettleWe wanted to come up with an archiving solution so we weren't storing *everything* on the web. I believe AJaeger said something about space requirements. My guess is that you don't want to overload the web server with so much content it will barely load10:40
asettleI could be wrong there.10:40
asettleAnyway, we were trying to come up with a solution that worked within our previous confines of having release specific documentation10:41
asettleOur solution at the time was creating tarball that the user would be able to download off the website, but was stored in github (I'd need to double check that)10:41
asettleNow, we have docs in a million different repos10:41
dhellmannprobably stored on tarballs.openstack.org10:41
asettleI believe setuid has been looking into it (if he is awake?)10:41
asettleThat'd be the one10:41
dhellmannI should skim the spec again10:42
dhellmannthe main justification there has to do with removing EOL content10:42
asettle*nods*10:42
dhellmannoh, though it does mention the space thing for cloudsites10:43
dhellmannnow that we're not hosted there, I don't know how much that's a factor10:43
dhellmannso that's something to check with fungi about10:43
asettleHere is the start of the thread that sparked it all: http://lists.openstack.org/pipermail/openstack-docs/2017-January/009493.html10:43
asettlehttp://lists.openstack.org/pipermail/openstack-docs/2017-January/subject.html10:43
asettleIt was a *big* chat10:43
dhellmannoh, good, history10:43
dhellmannI'll read that today, too10:44
dhellmannI should do that before we get too far into details, but *if* we change the retention policy, do we still need archived docs?10:44
asettleArchiving was preferential to leaving EOL docs up and available.10:47
asettleMostly because we want the user to be aware that this is not supported by dev.10:47
asettleThat was another key factor.10:47
dhellmannok10:48
asettleAlso, at the time, our branches were being deleted - so we wouldn't be able to perform backports etc10:48
asettleWe needed to have stamps on documentation etc10:49
asettleAlso, another thing I just realised - we'll be pulling in docs from other repos, which will still be branching10:49
dhellmannright10:49
asettleOkay that's it down with nova. Nova doesn't get docs.10:49
dhellmannso, I think we need to stop deleting what we publish. at least so quickly. users trail *way* behind upstream. I don't think that's a problem.10:50
dhellmannI'll work on turning that into a more detailed position.10:50
asettleAgreed :)10:50
AJaegerwe had release notes for each guide in the guide in the past - and can continue this way...10:50
dhellmannso if we stop deleting content, and it is just available on docs.o.o, and there are no space constraints, do we still need to come up with an archiving solution?10:50
dhellmannare there other use cases for archiving?10:50
dhellmannasettle : what error are you seeing with the nova docs?10:51
AJaegerdhellmann: space is not the factor - the problem is that we have EOLed guides that we do not maintain anymore. And still some people are interested in them. We often just removed them.10:52
*** chlong_ has joined #openstack-doc10:52
asettleOh nothing, I was just having an argument with it while attempting to rebase.10:52
dhellmannAJaeger : right, I'm trying to understand the motivation for that fully so I can convince everyone it's a mistake to keep doing it.10:52
asettleAJaeger: I thought space was a factor? Sorry about that.10:52
asettledhellmann: so, the mistake is - we get bugs when the out-of-date documentation requires an update. But dev isn't supporting $EOLRELEASE so we have no updates *for* the individual.10:53
AJaegerasettle: space was a concern on cloud sites- we were the largest site up there10:53
asettleThe main concern was that we couldn't, and wouldn't, maintain out of date docs. But happy to leave it up there.10:53
*** chlong__ has quit IRC10:53
dhellmannasettle : can you give me an idea of how often that happens?10:53
AJaegerdhellmann: I never wanted archiving - I agree, it's the wrong solution to the problem. But we didn't come up with anything better10:53
dhellmannyeah, to be clear, I'm not suggesting we maintain them. just that we don't delete them.10:54
AJaegerdhellmann: problem is also CSS  exploits - with our docbook toolchain, we had once to update old docs due to the integrated search ;(10:55
asettledhellmann: the thread that I linked you above is a fair indication. Tom felt very strongly about it. But I'd say every couple of months we'd get a bug about 'not having icehouse docs' or 'updating mitaka' when it's already EOL'd10:55
AJaegerhope that won't hit us again10:55
dhellmannAJaeger : yeah, I do remember that one10:55
dhellmannasettle : ok, I'll read that thread and then we can talk again10:56
dhellmannmaybe the solution is to extend the lifetime of the docs, but not indefinitely10:56
AJaegerdhellmann: space is still a concern - so, I don't think we should have for e.g. nova for each single release going back to version 1.0.0 and each branch documentation up on docs.o.o. WE need some kind of cleanup ...10:56
dhellmannor maybe we just say "if there is a security issue with a series of docs we can't rebuild we will delete them"10:56
AJaegeragreed, not indefinte.10:56
AJaegerAnd it's needs to be "scriptable" to deliete10:56
dhellmanngood point10:57
*** chlong__ has joined #openstack-doc10:57
dhellmannAJaeger: if we're going to delete by age, isn't that just a script with rm and find?10:57
asettleHow would we determine deletion? User survey?10:58
AJaegerdhellmann: yes. And with the root-marker fiels, we can easily do it now ;)10:58
dhellmannasettle : pick a number of years that seems reasonable?10:58
AJaegerhttps://docs.openstack.org/.root-marker10:58
asettledhellmann: 1, perfect10:58
AJaegerthe root-marker has no date but a revision. But timestamp on it we can check...10:59
dhellmannright, I was thinking timestamps10:59
*** chlong_ has quit IRC10:59
dhellmannat this point we can't easily resurrect old series content (though if we have someone who wants to it would be interesting to try)11:00
AJaegerbbl11:00
dhellmannso if we said from now on we won't delete content before it is 5 years old, what would that do?11:00
*** masaki has joined #openstack-doc11:03
asettledhellmann: I believe setuid did want to try11:11
* setuid perks11:11
asettleYo homie11:11
asettleWelcome to the EOL doc discussion11:11
asettledhellmann: that woulddddd probably create some arguments somewhere but hey! TO the ML!11:12
setuidI haven't caught up on the scrollback yet11:12
setuidAs long as you don't delete the _tags_ in github, we can still build out from those, with some patching, which we'll probably maintain in another publicly accessible repo in the short term11:12
setuidI'd rather not have those self-hosted elsewhere (RH owning their copy, Canonical owning their copy, etc.)11:13
setuidThere's a small risk factor with some of the Js, but that's easily patched out/mitigated11:13
setuidAny of you happen to be in the NY Metro area? I'm heading into the city this morning, might be good to catch up over lunch, or... to the ML! :)11:14
dhellmannsetuid : not in the area, I'm afraid11:15
asettlesetuid: I am most definitely hangin' in sunny London :( sorry man11:15
asettleOkay I always hang in London11:15
setuidhahahah, np to both. I'll be in Edinburgh in about a month, trying to make my way down to London on a sleeper for a day trip11:15
asettleHopefully it'll actually be a nice day :p11:15
asettlePlan wisely!11:16
asettle:p11:16
setuidSo I've got the liberty-eol and mitaka tags building cleanly, though liberty needs both tox + mvn to build clean11:16
asettlebrb lunch11:16
asettlesetuid: yeah we made that nice and difficult just to annoy you :P11:16
asettle*thumbs up*11:17
* asettle runs away11:17
setuidNot annoying, just another few lines to script it out and some deps to install11:17
setuidThe current challenge, is fixing all of the orphans that are deployed into the build copy by the XML refs that point to the upstream URLs which no longer exist11:18
setuidI haven't quite sorted how to make that a clean fix11:18
dhellmannasettle : cdent has a point on https://review.openstack.org/#/c/485249/, do you want to add a link in the commit message pointing to the ML discussion?11:19
setuiddhellmann: You going to the PTG in Sept?11:25
dhellmannsetuid : yes, I'll be there11:25
dhellmannI expect this will be a big discussion for the team there11:25
setuidI'll find asettle and draft in behind to add my input where it makes sense11:26
AJaegersetuid: Edinburgh is so nice, stay a day longer instead of going to London ;)11:32
AJaegersetuid: liberty was transition from one to the other, so need both11:32
setuidAJaeger: Yep, trying to pack in as much as I can in Edinburgh, but taking a sleeper down to London to see the city would be nice too, might hire a car and drive around Scotland though.11:34
setuidWith the patches I've built out, I may take a stab at pulling each tag and patching/building with the correct tool(s), up to current non-eol tags.11:34
setuidI support a big client and their ops team has nothing to refer to, so for now I've had to pull the tag and build an internal copy for them to refer to. They have a very complex set of mitm/ssl/proxy rules, which meant digging into the innards of Maven, MAVEN_OPTS, JAVA_FLAGS and all sorts of fun things to get all of that pushed down into maven's referenced plugins in the build tree.11:35
AJaegersetuid: what fun ;(11:36
setuidit's ok, I've sorted it. Turns out some plugins don't read the maven config, they read the environment flags, while others inherit what mvn parsed out of its own config. Similar with Java and the -Dhttp.foo flags11:37
* asettle returns11:43
asettleAJaeger: I gotta agree with you there, setuid you should definitely spend more time in Edinburgh11:44
asettleLondon is... ugly ;P11:44
asettledhellmann: he does indeed. I'll have to go back and find our email11:44
*** chlong__ has quit IRC11:45
*** chlong_ has joined #openstack-doc11:45
d0ugal+1 for Edinburgh11:47
* d0ugal is biased11:47
*** alexchadin has joined #openstack-doc11:48
*** lbragsta_ has joined #openstack-doc11:53
* AJaeger is biased as well11:56
*** alexchadin has quit IRC11:58
*** chlong_ has quit IRC11:58
d0ugalI guess we all are :)12:05
*** alexchadin has joined #openstack-doc12:10
*** lbragsta_ has quit IRC12:12
setuidI'm biased, but I'm on the wrong side of the wrong pond :)12:13
*** openstackgerrit has joined #openstack-doc12:13
openstackgerritDoug Hellmann proposed openstack/openstack-manuals master: link to keystone admin and config guides  https://review.openstack.org/48702612:13
*** yamamoto has quit IRC12:18
*** tylerderosagrund has joined #openstack-doc12:18
*** tylerderosagrund has quit IRC12:19
*** tylerderosagrund has joined #openstack-doc12:19
*** tylerderosagrund has quit IRC12:19
*** tylerderosagrund has joined #openstack-doc12:19
*** tylerderosagrund has quit IRC12:26
*** gouthamr has joined #openstack-doc12:26
*** dmacpher has joined #openstack-doc12:29
fungii rather enjoyed edinburgh, though couldn't quite get accustomed to the taste of irn-bru12:31
*** dustins has joined #openstack-doc12:33
asettleI love that we've now got a group of people voting on setuid 's holiday12:34
asettleNice work, team12:34
asettlefungi: irn-bru is rank - never liked it either12:34
fungiseemed like that's all anyone was drinking (mixed with vodka)12:35
fungimaybe the bar scene there has changed since my last visit12:35
asettlefungi: Ugh that sounds horrible :p12:35
asettlePotentially?12:35
*** edmondsw has joined #openstack-doc12:36
*** yamamoto has joined #openstack-doc12:36
fungiit's been almost a couple decades at this point, i should revisit sometime12:36
asettleYou should :) it's very pretty12:36
*** catintheroof has joined #openstack-doc12:39
*** catintheroof has quit IRC12:39
*** catintheroof has joined #openstack-doc12:39
openstackgerritAlexandra Settle proposed openstack/security-doc master: [WIP] Add Key Management Chapter  https://review.openstack.org/45196512:41
*** matjazp has joined #openstack-doc12:45
*** lucasxu has joined #openstack-doc13:05
AJaegerfungi, they have good beer as well ;) But irn-bru is an acquired taste ;(13:09
*** yamamoto has quit IRC13:12
*** thorst_afk is now known as thorst13:13
*** vharsh has quit IRC13:18
fungiyeah, i remember i was getting the local tavern ales when i could... though the "popular" beers with locals seemed to be terrible mass-market imports from the usa13:28
fungiobviously i wasn't going to sit in a bar in scotland and order american beer so terrible i wouldn't even drink it at home13:29
AJaegeryeah ;(13:31
d0ugalhah, I kind of like irn bru - but I have had years of practice13:32
setuidWell this escalated quickly :)13:32
asettlesetuid: we're a merry band of travellers13:32
setuidGreat, now I have that Robin Hood comedy stuck in my head13:33
d0ugalfungi: you need to pick your bars carefully - but there is lots of good local beers now.13:33
asettlesetuid: Good movie13:33
d0ugalasettle: I'm not a traveller, I live in Scotland :)13:33
setuidEveryone pile into d0ugal's flat!13:33
asettled0ugal: oh okay yes except for d0ugal he's the only one legitimate here13:33
d0ugallol13:34
setuidSerious question, and "To the ML, Robin!" is a valid response.. if I tighten up these patches to build from the EOL tags, where's the logical place to hold those?13:35
fungid0ugal: i will admit, i was almost 20 years younger and not nearly so good at sorting decent bars from miserable ones. i stand a much better chance of making reasonable choices when i go back13:35
asettlesetuid: yeahhhh I think that's definitely a ML discussion. Although $10 on the table that discussion will end up being me, dhellmann AJaeger and Anne ...13:36
*** chlong has joined #openstack-doc13:37
setuidOk, I can hold off until Sept. It'll give us a date to land some discussion on, which should sedate $CLIENT somewhat.13:37
asettlesetuid: perfecto. We'll hold another discussion on the topic. Which reminds me, it's probably about time we started compiling that etherpad...13:37
setuidWhen's the need meeting in -meeting?13:38
fungisetuid: is the plan still to tar up the results so they're not web-browsable? i could see arguments for either serving them from tarballs.o.o or docs.o.o13:38
setuids/need/next/13:38
asettlesetuid: next Thursday :)13:38
asettlealso, setuid add your topic hurrr: https://etherpad.openstack.org/p/denver-PTG13:38
setuidfungi: Right now, I'm building and hosting under nginx in a private space, just to make sure all of the orphans are working13:38
fungii mean in the long run, but i guess that's part of what can get discussed in the ml thread13:39
*** alexchadin has quit IRC13:39
setuidIn the long run, it would be ideal for them to be hosted on something like openstack-doc-archive.openstack.org, or docs.openstack.org/old/liberty, or similar.13:39
setuidThere should be a clean rolloff/eol schedule for operators who need access beyond the eol dates, but we can talk through the specifics at the PTG, no need to beat that horse here13:40
asettleI kind of agree with the docs.o.o/$RELEASE13:40
AJaegerif we move them, than links will break...13:40
asettle*shudders*13:40
setuidRight, but the links are broken now anyway13:40
AJaegerWE might just have a BIG FAT warning on docs.o.o/EOL_release13:40
asettleI am very anti-link breaking rn13:40
fungii thought at one point we had said that the newer work to start generating pdfs would also factor into the long-term archiving story going forward (so we could retain pdfs marked as being for eol releases, no longer supported upstream) and just not delete those13:40
asettleWe did indeed13:41
asettleThat would be going forward13:41
AJaegersetuid: I'm concerned about future updates - you're talking about old ones ;)13:41
asettleBut we need to revive13:41
setuidProblem with PDFs, is they're not easily web-indexed, searchable, cut-and-paste'able (think operators here_)13:41
setuidAJaeger: That's why this needs to be strategic, not tactical13:41
AJaegerfungi: we're reopening that discussion now - since nobody signed up to archive...13:41
setuidarchving can't be a one-and-done solution13:41
fungisetuid: well, one of the main reasons for not keeping old release docs online was that search engines had a tendency to return results for old documentation when users were looking for newer, and then they'd get confused... but that's probably also solvable with some sitemap and optimization voodoo13:42
setuidSomething to correct xref in the XML when a branch goes eol, so the references dont' break, or when they get momved, they're not orphaned off13:42
AJaegerfungi, yes, our sitemap tool can omit releases...13:42
setuidfungi: You can control that with your ETag and Cache-Control directives13:43
setuid^^ also sitemap.xml13:43
setuidThere may be a way to be more explicit in your keywords directive too, which could help13:43
fungiwell, point being even if we did keep old html online, the argument against pdfs of "not easily web-indexed" is fairly moot13:43
fungisince we wouldn't want the old html to be web-indexed either, right?13:43
setuidRight now, you're not leveraging keywords at all, so that's going to sting you later13:44
setuidYou definitely want the old html to be indexed, but you don't want it showing up in incorrect SERPs13:44
setuidI wrote a free, web-based SEO tool years ago to help people get through this kind of hump13:44
setuidBut... I like the BIG BOLD WARNING BOILERPLATE at the top of eol docs, web-indexed, so those seeking Ocata docs that land on a Liberty-eol SERP, know they're not the latest13:45
* fungi just discovered that vera doesn't have an entry for "serp"13:45
setuidSEarch Results PageS13:46
fungithis is what i get for involving myself in web design discussions when i hardly use a web browser ;)13:46
setuidIt's less about the design and more about the content but point taken13:46
setuidRight now, d.o.o doesn't use keywords at all, so any search for 'nova' will return whatever Google deterimines is relevant. You can influence that with the correct keywords.13:47
fungii'll leave the optimization planning to those of you versed in it. the last time i did any serious webmastering was in the '90s13:48
fungibut once you figure out what you want, i should be able to help you make it happen on the backend13:48
*** annegentle has joined #openstack-doc13:53
*** annegentle has quit IRC13:59
*** emagana has joined #openstack-doc13:59
*** chlong has quit IRC14:03
*** efoley has quit IRC14:15
*** efoley has joined #openstack-doc14:16
*** yamamoto has joined #openstack-doc14:17
*** masaki has quit IRC14:18
* asettle signs fungi up for all helping things14:18
fungiyou know where to find me!14:20
AJaegerasettle: fungi, is great but we might need to clone him first ;)14:20
AJaegerRemove the "," above, please14:20
asettleAJaeger: never! that comma will haunt you14:21
asettlefungi: every channel? :P14:21
fungimost of them anyway14:21
openstackgerritDoug Hellmann proposed openstack/openstackdocstheme master: move the localtoc for the page into the sidebar  https://review.openstack.org/48710314:23
fungidhellmann: thanks!14:23
fungithat was fast14:23
dhellmannfungi : it has been bothering me, but the gov site is a great example of why14:24
fungiwell, the infra team page was a fairly extreme example14:24
fungiit didn't make most pages quite so problematic14:24
dhellmannthe goals pages had similar issues14:24
dhellmannbut yeah14:25
*** yamamoto has quit IRC14:25
*** donghao has joined #openstack-doc14:26
*** lucasxu has quit IRC14:38
setuidAnyone here happen to be going to the Mexico City Meetup? Was just told the specific issue around eol docs is going to be a session there for the operators; apparently several reps of large deployments are in back-rev openstack all the way to icehouse!14:46
setuidIs there a 'clean' target to tox? Or should I just use 'git reset --hard'?14:57
*** tylerderosagrund has joined #openstack-doc14:58
AJaegergit clean -f14:58
asettlesetuid: no to the Mexico City14:58
AJaegergit clean -f -x -d14:58
AJaegersetuid: ^14:58
setuidOkee, I'll add some macros14:59
dhellmannsetuid : it would be good to have someone collect feedback from that session and share it, can you do that?15:03
setuid$CLIENT is going to M.C., I asked if that feedback could come back up and be brought to the PTG, so I'll likely be part of that conduit15:05
dhellmannsounds good15:05
dhellmannthere's usually an etherpad, but the notes there aren't always easy to interpret by someone who wasn't in the room15:06
setuiddhellmann: We'll try to put someone in every room, and make sure we're all talking/sharing, we definitely don't want any of this dropped or missed.15:11
dhellmannsounds like a good plan15:11
setuidNot every room at every conf, of course, but someone who can roll up the important bits and hot-potato that to the next person at the next conf ($CLIENT at M.C meetup, myself at PTG, etc.)15:12
*** mihalis68 has joined #openstack-doc15:14
dhellmannit would be great to have those summaries sent to the appropriate mailing lists as a way of passing the potato15:14
mihalis68hello15:14
setuidYep, I'll do my best to capture the bits... "Off to the ML" is always the default op.15:15
*** chlong has joined #openstack-doc15:16
*** rcernin has quit IRC15:17
setuidasettle: Is there a deployment target that pushes the build trees into a single repo that can be hosted? Or do I have to cherry-pick them all and stitch them back together under nginx?15:21
setuidI'm trying to test out how to get the orphan xrefs to point to the local copies vs. the upstream/404 URIs15:22
mihalis68setuid invited me to join this channel since I'm the one asking for older doc sets15:24
asettlesetuid: uno momento :) on a meeting15:24
dhellmannhi, mihalis6815:25
mihalis68hi15:25
setuidAlso, mihalis68 is goign to the Mexico City meetup, so there's some synergy with our efforts15:26
dhellmannsetuid : the build does an rsync of the output of each build into a path derived from the project name and tag/version/series15:26
setuiddhellmann: Right, saw that, some are in ./target/ some are in ./build-$component/15:26
mihalis68is there any context I could provide which helps explain the request?15:26
setuidJust wondering if there's another chained target that extracts those to a tree15:26
dhellmannmihalis68 : oh, great! we're especially interested in the outcome of the discussion of moving the ops-guide to be owned by an operator group15:26
mihalis68yes I agreed to participate in that discussion earlier today in the ops meet up team meeting on IRC15:27
dhellmannsetuid : oh, I don't actually know how the older stuff works. waiting for asettle or AJaeger may be better15:27
mihalis68I hear it is proposed to move to a wiki15:27
mihalis68I should probably be upfront and mention my experience is wiki documentation asymptotically approaches garbage15:28
mihalis68at least here at Bloomberg15:28
openstackgerritDoug Hellmann proposed openstack/openstackdocstheme master: move the localtoc for the page into the sidebar  https://review.openstack.org/48710315:28
dhellmannmihalis68 : we are not prescribing the solution; the wiki was suggested by some operators15:29
mihalis68ok15:29
mihalis68noted15:29
dhellmannthe key thing is that the docs team is not going to maintain the content, and has already removed it from our build15:29
dhellmannwe can help recover it to move it somewhere else15:29
dhellmannthat can be another git repo owned by a new team, or it can be the wiki15:29
mihalis68I am involved in documentation efforts private to bloomberg. docs are hard15:29
dhellmannor something else, i guess, if there's a third option15:29
setuidmihalis68 is $CLIENT :D15:30
dhellmannyes, indeed, and we've lost several members of our team recently15:30
setuidThere, the barn doors are open15:30
mihalis68cover blown15:30
dhellmannwe would love to have your help upstream :-)15:30
mihalis68I seem to add value in proof-reading in more contexts than I do authoring new content. Glad to start with a bit of that15:31
setuidRight now, we're cobbling along with a local build of the tags, based on my patches (new patch forthcoming to fix orphans, testing that now), but that's a stopgap to a proper, strategic archival solution, whether that's moving docs to ./archive/$RELEASE/, docs.o.o/EOL_$RELEASE, a wiki or otherwise. All TBD.15:31
dhellmannmihalis68 : that would be good. doing that upstream on a recent version of the docs will mean working in project team repositories now that the content has moved.15:31
setuidfungi may end up catching some backend work to process keywords to help the search engines properly differentiate the release and eol branches, so the SERPs produce the desired pages, also TBD it sounds like15:32
mihalis68if someone wants to point me at a specific review task I'll take one and see how I do. I'm not an openstack contributor yet15:32
*** andreas_s has quit IRC15:32
dhellmannsetuid: I caught part of that conversation, but not all of it. How much does the sitemap impact page ranking? I have some ideas for generating that differently.15:33
*** tylerderosagrund has quit IRC15:33
asettleThis is what happens when I got on meetings15:33
asettleBarn doors are blown open15:33
dhellmannmihalis68 : I'm not sure if we have specific tasks, though asettle may be able to help there15:33
asettleand mihalis68 appears15:33
asettledhellmann: I'll need to read scroll back when I'm done trying to get reno to dance to my merry tune15:34
asettle(downstream, not upstream)15:34
dhellmannasettle : let me know if I can help tame reno15:34
mihalis68I'll just follow-along here and try to get my bearings15:34
asettleI don't think any of us have any bearings either15:35
*** dustins has quit IRC15:35
*** tylerderosagrund has joined #openstack-doc15:35
mihalis68btw the operators meet up is $20 for two days lunch included. Obviously mexico city may be a challenge but the eventbrite is still open15:35
setuiddhellmann: It's all magical google ranking, some hand-waving algos that they don't publish, but I think you can 'weight' your sitemap15:36
asettlemihalis68: sadly London -> Mexican City is not the easiest stop over15:36
mihalis68agreed15:36
asettleMexican city?15:36
asettleJeez Alex15:36
asettleMexico*15:36
setuidI thought we were all piling into d0ugal's house for beers and scotch?15:36
asettleOh we were, yes15:36
dhellmannmihalis68 : I'll be heading out for PTO around that time15:36
mihalis68I don't know where any of you are, 'cept setuid15:36
asettlemihalis68: London is moi15:36
mihalis68NYC here15:37
asettleI admittedly never remember where dhellmann is15:37
asettleSorry dhellmann15:37
asettleAJaeger is Germany15:37
dhellmannsetuid : my idea is to build a mini-sitemap for each individual doc build, then have one big sitemap index that links them all together. The sitemap index would only include a subset the the others, though (say, the ones for actively supported series).15:37
dhellmannasettle : Athens, Georgia, USA15:38
fungisetuid: i was talking more about backend work to handle ci publication of archived paths or tarballs of archived builds for upcoming eol activities, not anything specific around keywords (that's probably more fit for embedding in the content or theme repos)15:38
asettledhellmann: oh man I never actually knew that15:38
asettleI had something different in my head15:38
setuiddhellmann: Ok, that's an option, and as long as 'something' provides an href to the older html rendered copies, Google will find them, index them.15:39
setuidSo they won't need to be resident in the sitemap, but still indexed15:39
setuidfungi: *nod*, I think that's where I've got my foot stuck now, trying to figure out the best way to 'fix' the xrefs that get rendered and lead to public-facing 404 URIs, vs. the locally-staged build I've completed.15:40
setuidIn a local build, everything should be self-referrant, imho, right now it's a hybrid15:40
dhellmannsetuid : right. I mean, we could potentially list every single version in the sitemap index, but if we don't want the search engine to emphasize those results I'm not sure why we would15:41
dhellmannsetuid : if you have a list of some of those links, we could look at whether it makes sense to set up redirects15:41
setuiddhellmann: Unfortunately, whether they show up on the top of a first page of results or not, isn't usually based on whether you call it out in sitemap or not, it's based on 'relevance' to Google's own algo.15:41
dhellmannah, I thought the sitemap weight had more influence than that15:42
setuidSo if you sitemap ocata, and get 10,000 operators all searching for liberty docs, finding them because Google indexed them after your sitemap, it may put the liberty results higher in the SERPs15:42
dhellmannat least within a given domain15:42
setuidI'll have to look at it again, I do know the spec had something about weighting15:42
fungiyeah, which is why in the past we resorted to taking those unsupported versions offline. it was an easy, if somewhat forcible, means of making sure they didn't turn up in search results15:43
setuidhttps://www.sitemaps.org/faq.html#faq_priority_and_page_rank15:44
setuidWait, I was told the eol versions went away because the branches were deleted, is that not the case?15:44
fungiit was deemed much harder to find more elegant solutions to making sure people don't get outdated docs unless that's what they actually want, and won't report errata or assume the upstream community can help them with those old docs15:44
dhellmannasettle : it took some years of practice, but I've almost eliminated the southern accent from my typing15:44
dhellmannsetuid : there are many reasons15:45
tylerderosagrunddhellmann you never loose the accent trust me15:45
*** annegentle has joined #openstack-doc15:45
asettledhellmann: very impressive15:45
dhellmanntylerderosagrund :-)15:45
asettleThis is probably the most action this channel has had in ages15:45
setuidThis may lend itself to having a separate tld for eol docs, so the sitemap domain ref is not the same (modulo the BIG RED BOILERPLATE at the top of eol docs, of course)15:45
asettleA wild tylerderosagrund appears15:45
mihalis68I've lived in the US for 20 years. I still get identified as something something british within 20 minutes15:45
*** belmoreira has quit IRC15:45
* tylerderosagrund waves15:45
asettleo/15:46
tylerderosagrundI'm here in San Antonio15:46
asettlemihalis68: hola yo. Although I guess I'm never going to get rid of my Australia accent15:46
dhellmannsetuid : that's an intriguing idea15:46
asettleUnless drunk. Then you either get really bogan Alex, or really posh Alex15:46
asettleDepending on her mood15:46
dhellmannooh, fun, I wonder which I'll see in Denver?15:46
setuidYou're right, I really did kick up the channel density this am, didn't I :)15:47
asettledhellmann: place your bets now :p15:47
* setuid feigns guity15:47
asettlesetuid: you're good :P15:47
fungisetuid: the branches went away to prevent people from trying to update them and so we wouldn't have to maintain working build environments for them indefinitely. the rendered copies were removed because we had no easy means of rebuilding them and were hesitant to publish content we couldn't replace from source should the need arise15:47
setuidThis is all good discussion, I'll try to summarize back to the ML this afternoon, see what others have to say about these various ideas15:47
asettleThat would be very helpful, setuid :)15:47
asettleAlso, I'll answer any questions once I'm off this meeting15:48
tylerderosagrundsounds like an intense meeting15:48
asettletylerderosagrund: trying ot get shit built that doesn't want to fucking build15:48
asettleto*15:48
asettleA Downstream Story: By Alexandra Settle15:49
setuiddhellmann: This looks interesting, search for 'priority' in the table about 1/4 way down the page: https://www.sitemaps.org/protocol.html15:49
tylerderosagrundoh yea then I'll leave you too it then asettle :-D15:49
dhellmannsetuid : ++15:49
mihalis68"trying ot get shit built that doesn't want to fucking build" a concise definition of this job, mostly15:49
asettlemihalis68: amen15:49
dhellmannsetuid : we know the release names in order, so we could build a sitemap index that had higher priority for newer items15:50
dhellmannoh, although that's for a location in a sitemap, not for an index15:50
dhellmannhttps://www.sitemaps.org/protocol.html#index15:50
mihalis68so nobody asked me anything15:51
mihalis68such disappoint15:51
setuidIt would be nice if the protocol allowed us to express negative weighting, but I guess anything below 0.5 does that by default15:51
asettlemihalis68: what should we be asking you?15:51
mihalis68"hey mihalis68 why not upgrade, y u not CI CD"15:52
mihalis68I already had that elsewhere, I don't mind15:52
dhellmannsetuid : one issue with moving archives to a different domains is that there will be a lot of full URLs embedded in the docs15:52
setuiddhellmann: Some of those can be RST'd out, I think... some may not though.15:52
setuidThat's now a second-order problem, you can't commit changes to tags and the branches are gone, chicken and egg problem15:52
mihalis68the tl;dr is we got to Liberty and then got seriously busy and also had a lot of staff turnover, so today I still really need my nova-network docs to run our 9 production openstack clusters15:53
mihalis68the end15:53
dhellmannany time someone embeds a full link instead of using a :doc: or :ref: directive :-/15:53
dhellmannmihalis68 : I feel for you, really.15:53
dhellmannsetuid : sure, let's try to figure out how to solve the problem for currently active releases and the future, then we can decide what to do with anything older15:54
setuidmihalis68 represents the operators/cloud team, I'm just a hired mercenary to fix all the pieces that fall apart15:55
setuidback in a lunch15:55
mihalis68setuid has made strong contribs to our stack15:55
mihalis68mostly rooting out my "programming" e.g. bash15:55
dhellmannsetuid, asettle : at what cycle did we switch from docbook to rst?15:57
asettledhellmann: Liberty, fairly sure. Liberty -> Mitaka15:57
asettleAfter Paris15:57
dhellmannk15:58
asettleI dunno it was a horrible time in my life I never want to see an RST converted table again15:58
*** imacdonn_ has joined #openstack-doc15:59
*** edmondsw has quit IRC15:59
*** edmondsw has joined #openstack-doc16:00
*** imacdonn has quit IRC16:01
asettleOKAY I AM OFF THE MEETING NOBODY PANIC16:02
*** edmondsw_ has joined #openstack-doc16:03
asettledhellmann: you had many questions16:03
* tylerderosagrund doesnt panic16:03
*** edmondsw has quit IRC16:05
*** edmondsw_ has quit IRC16:07
asettletylerderosagrund: ah jeez man16:08
*** cburgess has quit IRC16:08
tylerderosagrundasettle I'm cool as ice16:09
tylerderosagrundbut I may have paniced just a little16:09
*** cburgess has joined #openstack-doc16:09
asettleDoes that mean you melted?16:14
asettleheh16:14
*** rcernin has joined #openstack-doc16:14
tylerderosagrundI guess I have16:16
tylerderosagrundTime to mop up my own mess16:16
* tylerderosagrund goes back to work16:16
*** edmondsw has joined #openstack-doc16:18
asettletylerderosagrund: wait... you a Racker?16:19
asettleI just cottoned on that you said SA16:19
tylerderosagrundI am and just came back to the Rack16:20
tylerderosagrundWhy am I in trouble now?16:20
*** edmondsw has quit IRC16:22
asettletylerderosagrund: nah bro, just checking who else is also a Racker or not :p16:23
tylerderosagrundOoooh nice :D Are you here in San Antonio too?16:23
asettleNope, I hide out in the London office like a good Australian :p16:24
*** edmondsw has joined #openstack-doc16:24
tylerderosagrundHaha sounds like Cam B :-)16:24
*** lucasxu has joined #openstack-doc16:26
*** lucasxu has quit IRC16:28
*** edmondsw has quit IRC16:28
*** donghao has quit IRC16:32
*** annegentle has quit IRC16:32
*** emagana has quit IRC16:34
*** matjazp has quit IRC16:35
setuiddhellmann: Looks like liberty is both mvn+tox, mitaka is tox-only. mvn builds 522 docs, tox adds an additional 433 to the liberty-eol tree, but there are some orphans (yes, I owe you a list)(16:48
openstackgerritMatt Riedemann proposed openstack/openstack-manuals stable/ocata: Fix cells doc link in cells v1 config reference  https://review.openstack.org/48714116:48
dhellmannsetuid : which specific guides are you looking for again?16:49
setuiddhellmann: mihalis68 needs the networking guide at the moment, that appears after the tox pass, so I think we're good there. It wasn't part of the mvn rendering.16:51
dhellmannsetuid : which series16:51
setuidHe's got some challenges with his internal Xenial instance, unrelated to doc structure, so I'm building on my laptop16:51
setuidliberty-eol at the moment16:51
setuidThat's where we're focused, mitaka after that, priority is liberty16:51
dhellmannhttps://docs.openstack.org/liberty/networking-guide/16:51
dhellmannthat exists16:51
dhellmannit may not be linked from anywhere16:51
*** edmondsw has joined #openstack-doc16:52
dhellmannsame for https://docs.openstack.org/mitaka/networking-guide/16:52
setuid*nod*16:52
dhellmann I'm finding all sorts of stuff on this web server that I didn't know existed16:52
setuidI don't think they're linked on the front/landing page, so not easy to find unless you know the URI16:53
dhellmannyeah, I'm going to see if I can address that after I find a sandwich16:53
*** lucasxu has joined #openstack-doc16:54
setuidThis is interesting, what's the difference between:16:55
setuid./publish-docs/liberty/networking-guide/index.html16:55
setuid./doc/networking-guide/build/html/index.html16:55
setuidtop one is from tox, bottom from mvn16:56
setuidI thought the build tools were additive, looks like they duplicate16:56
*** edmondsw has quit IRC16:56
setuidFollowing this structure: https://docs.openstack.org/contributor-guide/docs-builds.html#building-docs-from-end-of-life-releases16:56
*** annegentle has joined #openstack-doc17:04
*** sambetts is now known as sambetts|afk17:10
AJaegerdhellmann: we have priority already in our sitemap - set depending on location. See openstack-doc-tools repo17:32
* AJaeger reads backscroll17:32
AJaegersetuid: we rsync as tell of our build scripts to publish-docs, so there is no difference between those17:35
setuidAJaeger: That hasn't been my experience, but that may be a change post-mitaka17:36
setuidI'm rerunning builds now to check (scripted my own patching + CI/CD for these builds for the moment)17:36
AJaegersetuid: it depends on what job you call. If you call "mvn" directly, it does not copy. If you use tox for building, it copies for jobs like "checkbuild"17:40
setuidAJaeger: My read of the build process, the liberty tag requires building with mvn+tox to get a full copy of the docs, but mitaka-eol and later are all tox only17:40
setuidThe docs I build with mvn (522 rendered files) all end up in ./doc/<component>/target/docbkx/*17:41
AJaegersetuid: yes, they end there - if you build with mvn directly. If you use the scripts as they have been invoked from our CI system, they copy everything to publishdocs and that's the big collecting place we use for pushing to the web server17:44
setuidThe docs I build with tox (433 rendered files) all end up in a different top-level dir17:44
setuidah, that's what I was looking for earlier, if there was a tox target to aggregate all the built docs into one tree for publishing17:44
AJaegertox -e checkbuild17:45
setuidYep, adding all the checks to my CI now17:45
setuidGoing to loop through each of the tags and build, hopefully tox won't wipe out ./publish-docs/$rel/ at eaach pass17:45
openstackgerritAndreas Jaeger proposed openstack/openstack-doc-tools master: sitemap: Add ocata  https://review.openstack.org/48715117:46
AJaegerno, we never cleanup up publishdocs17:46
AJaegerbbl17:46
openstackgerritMerged openstack/openstack-manuals stable/ocata: Fix cells doc link in cells v1 config reference  https://review.openstack.org/48714117:54
dhellmannsetuid, mihalis68 : do you need a guide that is not listed at http://paste.openstack.org/show/616467/ ?17:55
*** annegentle has quit IRC17:59
setuidNope, that looks good for me/us..17:59
setuidCan't speak for those at the Mexico City operator's meetup though, they may go back to icehouse17:59
setuids/to/prior to/18:00
*** annegentle has joined #openstack-doc18:01
mihalis68there is at least one on icehouse18:01
mihalis68emagana (@meganap on twitter)18:01
mihalis68also some of the NTT team appear to have some stake in older docs18:01
setuidLet's take this up to the ML also, I'll start off a topic later this afternoon, once I've pulled all the bits together, it's been a busy day here and $here.18:02
openstackgerritAndreas Jaeger proposed openstack/openstack-doc-tools master: sitemap: Add ocata  https://review.openstack.org/48715118:03
dhellmannwell, there's a config-reference for icehouse  in there. did we have an admin guide then?18:03
dhellmannI'm trying to work out what might be missing.18:03
dhellmannI see config, install, and training guides on the old server18:04
setuidiirc, the networking-guide was missing18:04
setuidI'll know in a sec, I botched my mitaka-eol patch18:04
AJaegerdhellmann: admin guide is unversioned, so we never had one published from any stable/* branch18:05
dhellmannAJaeger : ok, that makes sense18:05
AJaegersetuid: I think networking-guide at liberty was in a very bad shape, so might not have been published.18:06
AJaegerchecking tools/build-all-rst.sh in liberty-eol, it's not published18:06
setuidI'll see if I can get mihalis68 to proof that, maybe fix up the bits. We may end up with a number of updates that need to get captured somewhere (maybe this is where the 'wiki' discussion began?)18:06
setuidI'll dot out some of these on the etherpad (https://etherpad.openstack.org/p/denver-PTG)18:07
*** KeithMnemonic has joined #openstack-doc18:09
setuiddhellmann: If I fork openstack-manuals and patch the eol tags so they build, what's the process to PR those back? (is that another TBD/open loop?)18:21
dhellmannthere is no process for contributing to eol branches, that's sort of the point of deleting the branches18:21
dhellmannso yeah, we'd need a longer conversation18:21
dhellmannbut please do not take that as a pre-commitment that patches would be accepted -- we should have that conversation before you invest too much time in the content18:22
setuidSo here's a thought we had over lunch: What if the eol branches were broken off and put into their own repo, specifically for eol docs _only_, and patches to those were accepted?18:22
setuidOh absolutely, at this point I'm just trying to satisfy the open request to have a working set of eol manuals18:22
dhellmannthat would make publishing them more complicated than just resurrecting the branches in their current location18:22
AJaegersetuid: if somebody commits to maintain a branch, we can keep it longer open.18:22
setuidWhile we're kicking around how to manage this strategically18:22
AJaegersetuid: (for future branches)18:22
dhellmannok, sure, I just wanted avoid setting your expectations too high18:22
AJaegersetuid: but so far the existing team with its resources had no bandwidth...18:22
setuidAJaeger: I'd rather pin that down before more branches go eol, so we don't multiply the effort18:23
setuidTotally understand, we're all under thin resources18:23
AJaegersetuid: just for the record, this is the first time it comes up  -and we EOL branches for ages...18:23
setuidmihalis68's team was recently thinned, unexpectedly as well as our own recent haircuts18:23
setuidOn the one hand, I'm surprised this is the first time, but on the other, solving it closes a number of issues out in the community18:24
mihalis68it's true that I didn't complain about it before, but I definitely struggled to find the documents of the openstack I am deploying for years now18:24
setuidThere's a gap between upstream project supported status and what we (Canonical) layer in on  top of that with our LTS support of openstack on Ubuntu.18:25
setuidmihalis68 currently fell in that gap18:25
mihalis68there is also the issue that sometimes when you select a supported release on the launch page, after a few link-follows you find yourself on latest, but perhaps don't even notice18:25
setuidI think the recent watermarking of release docs may make that a bit more obvious, but there could still be edge conditions18:26
mihalis68I often find cool new features in what I think is the right documentation level and then find I was mistaken18:26
mihalis68that sounds good. Not aware of it but if it makes a page self-represent its openstack version, that is awesome18:26
setuidmihalis68: Compare these:18:27
setuidhttps://docs.openstack.org/mitaka/networking-guide/intro-basic-networking.html18:27
setuidhttps://docs.openstack.org/liberty/networking-guide/intro-basic-networking.html18:27
setuidYou should see two different watermarks, it probably could be more obvious, but that's just some styling18:28
*** fragatina has quit IRC18:28
mihalis68Well would you look at that!18:28
mihalis68<oblivious>18:28
mihalis68thanks guys that's a big help right there18:28
setuidI'd love to see one of the watermarks right at the top of the page, so it's obvious before you scroll down, but that may be an easy fix18:29
*** matjazp has joined #openstack-doc18:33
setuidkilo patched, icehouse build working now... easier than I thought, once I worked out what needed tweaking18:40
*** dhellmann has quit IRC18:45
*** reed has quit IRC18:46
*** dhellmann has joined #openstack-doc18:47
*** fragatina has joined #openstack-doc18:51
setuidJust found something interesting18:52
setuidIf you check out juno-eol, all of the refs were correctly updated before that was tagged, later tags didn't have that step done, so I have to patch it back in18:53
setuidBut icehouse-eol _does_ need that patching18:54
AJaegersetuid: yes, we pushed for juno-eol - before closing it - a patch for each guide to mark it eol18:54
*** reed has joined #openstack-doc18:55
AJaegerAnd to build that patch, I needed to change content.18:55
AJaegersee change I1115dc8009d31d56e62290ca4019c910993b043318:55
*** phealy has quit IRC18:55
setuid*nod*, just noticing the discrepancy. If the same care was done to icehouse -> kilo -> liberty -> mitaka, these patches wouldn't be needed, leaving only the issue of eol doc residence the outstanding ask.18:56
AJaegersetuid: we marked those eol earlier and thus never run into the "problem"18:56
AJaegersetuid: it is a timing question. We retired with juno *later* then other repos and therefore hit that problem18:57
AJaegerLater we retired at the same time and thus did not run into the problem. Our liberty-eol tag was created at same time as nova-eol18:57
setuidYep, makes sense. Maybe some rigor right before tagging as -eol, to add that final pass to fix the refs so they're not broken?18:57
AJaegersetuid: not possible if we retire at the same time ;)18:58
*** dhellmann has quit IRC18:58
AJaegerit only works if we retire later...18:58
*** dhellmann has joined #openstack-doc18:58
setuidWhat if there's a staged PR, never merged in, which contains that last 'fix', so when you do retire, whenever that is, you merge that 'eol PR' and it fixed itself! :)18:59
AJaegerwhich makes it more difficult, retiring is a global step for all repos...18:59
AJaegersetuid: doesn't work in practice18:59
*** dhellman_ has joined #openstack-doc18:59
AJaegersetuid: yeah, we could make this work - but it was never needed in the past, so never on our check list19:00
* dhellman_ thinks his hosting provider is having some trouble, as his bouncer keeps disconnecting him19:00
setuidRight now, this is my hacky build script: https://paste.debian.net/hidden/f994b300/19:01
setuidTrying to be a bit pedantic19:01
AJaegersetuid: tox -e checkbuild would be better...19:05
*** KeithMnemonic1 has joined #openstack-doc19:06
setuidyep, rebuilding now19:06
*** KeithMnemonic has quit IRC19:06
*** phealy has joined #openstack-doc19:37
*** dhellman_ has quit IRC19:37
*** fragatin_ has joined #openstack-doc19:38
*** fragatina has quit IRC19:41
*** phealy has quit IRC19:43
*** annegentle has quit IRC19:48
*** annegentle has joined #openstack-doc19:50
*** nicolasbock has quit IRC19:52
*** mtreinish has quit IRC19:55
*** phealy has joined #openstack-doc20:00
*** phealy has quit IRC20:09
*** fragatin_ has quit IRC20:10
*** mtreinish has joined #openstack-doc20:10
*** fragatina has joined #openstack-doc20:11
*** fragatina has quit IRC20:11
*** fragatina has joined #openstack-doc20:12
openstackgerritDoug Hellmann proposed openstack/openstack-manuals master: add landing pages for historical versions  https://review.openstack.org/48719720:33
openstackgerritDoug Hellmann proposed openstack/openstack-manuals master: update release dates and status on all landing pages  https://review.openstack.org/48719820:33
openstackgerritDoug Hellmann proposed openstack/openstack-manuals master: move series dates into generator  https://review.openstack.org/48719920:33
openstackgerritDoug Hellmann proposed openstack/openstack-manuals master: use SERIES_INFO to pick up the message to describe the series status  https://review.openstack.org/48720020:33
openstackgerritDoug Hellmann proposed openstack/openstack-manuals master: move repetitive content from the index pages to the indexbase template  https://review.openstack.org/48720120:33
*** phealy has joined #openstack-doc20:37
openstackgerritDoug Hellmann proposed openstack/openstack-manuals master: move series dates into generator  https://review.openstack.org/48719920:37
openstackgerritDoug Hellmann proposed openstack/openstack-manuals master: move repetitive content from the index pages to the indexbase template  https://review.openstack.org/48720120:37
openstackgerritDoug Hellmann proposed openstack/openstack-manuals master: use SERIES_INFO to pick up the message to describe the series status  https://review.openstack.org/48720020:37
*** edmondsw has joined #openstack-doc20:40
openstackgerritDoug Hellmann proposed openstack/docs-specs master: switch to openstackdocstheme  https://review.openstack.org/48720420:41
openstackgerritDoug Hellmann proposed openstack/openstack-manuals master: update release dates and status on all landing pages  https://review.openstack.org/48719820:49
openstackgerritDoug Hellmann proposed openstack/openstack-manuals master: move series dates into generator  https://review.openstack.org/48719920:49
openstackgerritDoug Hellmann proposed openstack/openstack-manuals master: add landing pages for historical versions  https://review.openstack.org/48719720:49
openstackgerritDoug Hellmann proposed openstack/openstack-manuals master: move repetitive content from the index pages to the indexbase template  https://review.openstack.org/48720120:49
openstackgerritDoug Hellmann proposed openstack/openstack-manuals master: use SERIES_INFO to pick up the message to describe the series status  https://review.openstack.org/48720020:49
openstackgerritDoug Hellmann proposed openstack/openstack-manuals master: the mistral team deleted their admin guide landing page  https://review.openstack.org/48720920:49
*** tylerderosagrund has quit IRC20:57
*** gouthamr has quit IRC21:01
*** yamamoto_ has joined #openstack-doc21:07
*** lucasxu has quit IRC21:09
*** catintheroof has quit IRC21:11
*** arbaindur has joined #openstack-doc21:12
arbaindurIs there any documentation on the openstack designate CLIs?21:12
arbaindurIt is missing from: https://docs.openstack.org/python-openstackclient/latest/cli/command-list.html21:12
*** efoley has quit IRC21:14
annegentlearbaindur can offer https://github.com/openstack/python-designateclient/blob/master/doc/source/cli/index.rst for now21:22
*** gouthamr has joined #openstack-doc21:23
arbaindurAren't those individual clients deprecated? and designate CLI only supports v1 API apparently. we have v1 api turned off in designate, only v221:24
*** annegentle has quit IRC21:27
*** mtreinish has quit IRC21:42
*** mihalis68 has quit IRC21:43
*** mtreinish has joined #openstack-doc21:46
*** annegentle has joined #openstack-doc21:52
*** matjazp has quit IRC21:56
*** gouthamr has quit IRC21:58
*** yamamoto_ has quit IRC22:05
*** yamamoto has joined #openstack-doc22:09
*** annegentle has quit IRC22:49
*** suyog has joined #openstack-doc22:58
*** rcernin has quit IRC22:58
*** thorst has quit IRC23:06
*** edmondsw has quit IRC23:10
*** edmondsw has joined #openstack-doc23:11
*** dmacpher has quit IRC23:12
*** edmondsw has quit IRC23:15
*** chlong has quit IRC23:32
*** deep-book-gk_ has joined #openstack-doc23:41
*** deep-book-gk_ has left #openstack-doc23:42
*** arbaindur has quit IRC23:43
*** charcol has joined #openstack-doc23:54

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