From 0e0d5bf1c8969a324712bcd36407458b567e5936 Mon Sep 17 00:00:00 2001 From: Sylvain Bauza Date: Wed, 19 Sep 2018 10:07:12 +0200 Subject: [PATCH] cells: Be explicit in docs about service restarts Some operators could be confused if they start conductor workers with an imcomplete setup. Just adding a clear note on the dependency. Change-Id: I142de27f045ddb4c298ecae5a35bcb98ac863e3d --- doc/source/user/cells.rst | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/doc/source/user/cells.rst b/doc/source/user/cells.rst index 37c830c08be2..b14f95c72900 100644 --- a/doc/source/user/cells.rst +++ b/doc/source/user/cells.rst @@ -245,6 +245,14 @@ scheduled are relegated to the cell0 database, which is effectively a graveyard of instances that failed to start. All successful/running instances are stored in "cell1". + +.. note:: Since Nova services make use of both configuration file and some + databases records, starting or restarting those services with an + incomplete configuration could lead to an incorrect deployment. + Please only restart the services once you are done with the described + steps below. + + First Time Setup ~~~~~~~~~~~~~~~~ @@ -493,7 +501,7 @@ database yet. This will set up a single cell Nova deployment. matches the transport URL for the cell created in step 5, and start the nova-compute service. Before step 7, make sure you have compute hosts in the database by running:: - + nova service-list --binary nova-compute 7. Run the ``discover_hosts`` command to map compute hosts to the single cell