Re: [Openstack-operators] old Juno documentation

2016-11-08 Thread Cristina Aiftimiei
Hi Mohammed, thank you very much, I'm looking into that right now! A small corretion - in my initial e-mail the link that I had and now gives a 404 is http://docs.openstack.org/juno/networking-guide/ scenario_provider_ovs.html , the "kilo" one is still working. Thanks again, Cristina On Mon, No

Re: [Openstack-operators] old Juno documentation

2016-11-07 Thread Tom Fifield
On 08/11/16 06:16, Cristina Aiftimiei wrote: Dear all, in the last days I'm looking around for an old link that I had on how to configure "Provider networks with Open vSwitch"in Juno release. I had the link http://docs.openstack.org/kilo/networking-guide/scenario_provider_ovs.html that now give

Re: [Openstack-operators] old Juno documentation

2016-11-07 Thread Anne Gentle
On Mon, Nov 7, 2016 at 4:38 PM, Kris G. Lindgren wrote: > I don’t have an answer for you, however I have noticed this EXACT same > thing happening with API documentation. The documentation gets replaced > with latest version and it’s impossible to point people to the > documentation for the olde

Re: [Openstack-operators] old Juno documentation

2016-11-07 Thread Mohammed Naser
As a small workaround, I'd suggest the following: https://github.com/openstack/openstack-manuals There are branches for the maintained codebases and tags for the EOL'd ones, for example, you can find all EOL'd Juno docs here: https://github.com/openstack/openstack-manuals/tree/juno-eol Not grea

Re: [Openstack-operators] old Juno documentation

2016-11-07 Thread Mathieu Gagné
I find it to be an inconvenient. (for the one times I read the docs) To compare, I found that some projets (like the ones on readthedocs) often keep the previous versions so one can refer to it. You can easily see all the available versions and switch to the one you need. That's very convenient an

Re: [Openstack-operators] old Juno documentation

2016-11-07 Thread Kris G. Lindgren
I don’t have an answer for you, however I have noticed this EXACT same thing happening with API documentation. The documentation gets replaced with latest version and it’s impossible to point people to the documentation for the older version of the api’s that we are actually running. IE: http: