Added a set of schema and data migration policy rules to the `upgrades`
devref document to facilitate live upgrades.
Change-Id: I4e38a228b38927115bb13652966d45f250cc2af6
We log a warning when using cells that it's experimental, and we have
several locations in the docs that say it's experimental, but we have
never documented that rolling upgrades are not supported and that cells
deployments must be upgraded in lockstep. This adds that information to
the warning that's logged on startup and to the devref doc on upgrades
so people know that cells is still a special kitten that must be treated
differently.
Related-Bug: #1479181
Change-Id: Idd57f8daa308543a1733092f427e41b1a205b1d1
Listed the current process for upgrading the Nova database to allow for
better understanding of what will be changing.
Change-Id: Ib1c6abd8b08fe0987e2535d0ed6729f5384cebf3
Signed-off-by: Philip Schwartz <philip.schwartz@rackspace.com>
* Explain these docs are for trunk (copied from ironic)
* All the docs in this repo are meant to be developer docs, so having a
devref inside of the docs is redundant and just makes the docs more
complicated to navigate. Move everything out of the devref folder and
link to everything from main index.
* Move man pages into separate section. The man pages are pretty sparse
* right now, we should either make them useful or just delete them
* Remove dead docs from unused_docs list in doc/source/conf.py
* Shuffle docs landing page, move common referees to the top (API,
hypervisor support matrix), Add a introduction section and more. The
hope is the updated layout makes this document easier to navigate.
* Use maxdepth of 1
* Rename a few sections with what are hopefully better names
The next step is to prune out outdated documents and further cleanup
this page.
Change-Id: Iff453e47ccc902a0e72b1a5f6ce1ee939ff3a1a0
Brian Elliott