Fix and add some notes to the cells v2 first time setup doc

There was a typo in here about the map_cell0 command creating
a db connection with a _nova suffix when it's actually a _cell0
suffix like in the example, nova_cell0.

This also adds a reminder to sync the API database schema before
running the commands and also gives a warning about being
specific when using map_cell0 and having the databases on different
hosts.

Depends-On: I541b072638b5d50985145391e76f610417fdcaa6

Change-Id: Ibf3355217bbd0139a020de352bb62ff7d973d27b
This commit is contained in:
Matt Riedemann 2017-01-17 13:15:54 -05:00 committed by Stephen Finucane
parent ad78158deb
commit 5ba69008b6
1 changed files with 11 additions and 1 deletions

View File

@ -259,6 +259,9 @@ use those values. If need be, you can create separate config files and
pass them as `nova-manage --config-file foo.conf` to control the
behavior without specifying things on the command lines.
The commands below use the API database so remember to run
`nova-manage api_db sync` first.
First we will create the necessary records for the cell0 database. To
do that we use `nova-manage` like this::
@ -268,7 +271,14 @@ do that we use `nova-manage` like this::
.. note:: If you don't specify `--database_connection` then
`nova-manage` will use the `[database]/connection` value
from your config file, and mangle the database name to have
an `_nova` suffix.
a `_cell0` suffix.
.. warning:: If your databases are on separate hosts then you should specify
`--database_connection` or make certain that the nova.conf
being used has the `[database]/connection` value pointing to the
same user/password/host that will work for the cell0 database.
If the cell0 mapping was created incorrectly, it can be deleted
using the `nova-manage cell_v2 delete_cell` command and then run
`map_cell0` again with the proper database connection value.
Since no hosts are ever in cell0, nothing further is required for its
setup. Note that all deployments only ever have one cell0, as it is