openstack/nova
Code Issues Proposed changes

doc: add cells v2 FAQ on mapping instances

Browse Source 
This came up in IRC where someone upgraded from newton to
ocata and didn't use the simple_cell_setup command, but they
didn't run the map_instances command. Our cells v2 deploy/upgrade
guide mentions using simple_cell_setup for the minimal scenario
so it wasn't clear that they needed to run map_instances.

The install guide doesn't mention any of this either since this
is about upgrades, and the install guide is focused on fresh installs
where there are no existing instances to map.

Change-Id: Iedf3aabf1508abf59a54071b20a7f1c58b63e32c
This commit is contained in:
Matt Riedemann 2017-05-23 12:55:17 -04:00
parent 7c1018a118
commit e8d8558531
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/source/cells.rst
View File

@ -588,3 +588,15 @@ FAQs
if you are having the same issue in those services. As of the 16.0.0 Pike
release there is no timer on the cache or hook to refresh the cache using a
SIGHUP to the service.
#. I have upgraded from Newton to Ocata and I can list instances but I get a
404 NotFound error when I try to get details on a specific instance.
Instances need to be mapped to cells so the API knows which cell an instance
lives in. When upgrading, the ``nova-manage cell_v2 simple_cell_setup``
command will automatically map the instances to the single cell which is
backed by the existing nova database. If you have already upgraded
and did not use the ``simple_cell_setup`` command, you can run the
``nova-manage cell_v2 map_instances --cell_uuid <cell_uuid>`` command to
map all instances in the given cell. See the :ref:`man-page-cells-v2` man
page for details on command usage.