[openstack-dev] [docs][upgrades] time to add official docs for upgrading services?
mkassawara at gmail.com
Mon Nov 21 02:35:48 UTC 2016
How about top-level organization by project/service, each with consistent
topics that pertain to installation, configuration, upgrades, development,
API, etc? Projects can determine whether some or all of those topics reside
in the openstack-manuals or project repository.
On Fri, Nov 18, 2016 at 12:27 PM, Doug Hellmann <doug at doughellmann.com>
> Excerpts from Steve Martinelli's message of 2016-11-17 20:36:46 -0500:
> > In the keystone docs we have notes about how to upgrade between releases
> > , so does the nova team .
> > Is it time we create an official guides to  for this subject?
> >  http://docs.openstack.org/developer/keystone/upgrading.html
> >  http://docs.openstack.org/developer/nova/upgrade.html
> >  http://docs.openstack.org/
> Maybe, instead of creating a separate project-specific guide for
> every topic (install, upgrade, config, API, etc.), it would make
> sense to have developer, deployer, and user facing guides and create
> separate chapters in each for topics relevant to the audiences?
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev