Browse code
Add instructions for discovering hosts in the multinode guide
When doing a multi-node devstack deployment starting in Ocata
the child compute nodes must be discovered and mapped to the
single nova cell (cell1). In the upstream CI we do this discovery
in devstack-gate after the subnodes are stacked, but for anyone
doing this manually we need to provide some notes on what needs
to happen after child compute nodes are stacked for a multinode
environment.
Change-Id: I68418bcf28d86c60fe42537186d89458fa778bda
Closes-Bug: #1688397
Matt Riedemann authored on 2017/07/26 06:08:50Showing 1 changed files
| ... | ... |
@@ -197,6 +197,22 @@ A stream of activity ensues. When complete you will see a summary of |
| 197 | 197 |
to poke at your shiny new OpenStack. The most recent log file is |
| 198 | 198 |
available in ``stack.sh.log``. |
| 199 | 199 |
|
| 200 |
+Starting in the Ocata release, Nova requires a `Cells v2`_ deployment. Compute |
|
| 201 |
+node services must be mapped to a cell before they can be used. |
|
| 202 |
+ |
|
| 203 |
+After each compute node is stacked, verify it shows up in the |
|
| 204 |
+``nova service-list --binary nova-compute`` output. The compute service is |
|
| 205 |
+registered in the cell database asynchronously so this may require polling. |
|
| 206 |
+ |
|
| 207 |
+Once the compute node services shows up, run the ``./tools/discover_hosts.sh`` |
|
| 208 |
+script from the control node to map compute hosts to the single cell. |
|
| 209 |
+ |
|
| 210 |
+The compute service running on the primary control node will be |
|
| 211 |
+discovered automatically when the control node is stacked so this really |
|
| 212 |
+only needs to be performed for subnodes. |
|
| 213 |
+ |
|
| 214 |
+.. _Cells v2: https://docs.openstack.org/nova/latest/user/cells.html |
|
| 215 |
+ |
|
| 200 | 216 |
Cleaning Up After DevStack |
| 201 | 217 |
-------------------------- |
| 202 | 218 |
|