openstack/fuel-docs
Code Issues Proposed changes

Add note about upgrading primary controller first

Browse Source 
Primary controller usually has the lowest ID number of all controllers
in the environment. Add note to select controller with minimal ID to
upgrade first in Upgrade Environment section of the Operations Guide.

Closes-bug: 1505641
Change-Id: I35b8440b6a4655c197b2b694e26f6760e6adad11
This commit is contained in:
Oleg Gelbukh
2015-10-24 21:24:25 +00:00
committed by Svetlana Karslioglu
parent 2005978d88
commit c5dffb4e8b
2 changed files with 14 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
pages/operations/upgrade/1010-quick-start.rst
View File

@@ -88,6 +88,11 @@ that ID:
fuel node list --env ${ORIG_ID} | awk -F\| '$7~/controller/{print($0)}'
.. note::
Select a controller node with the lowest ID to ensures that you upgrade
the `primary` controller first.
Use the ID of the Controller to upgrade it with the following command:
::

11
pages/operations/upgrade/3040-install-seed.rst
View File

@@ -29,6 +29,12 @@ Deployment settings can be downloaded from Fuel API as a set of files.
The upgrade script updates the settings by changing those files and
uploading the modified information back via Fuel API.
.. note::
Always upgrade the controller with the lowest ID number first.
The controller node with the lowest ID number is a so-called `primary`
controller and you must upgrade before other controllers in the
OpenStack environment.
The upgrade script keeps the deployment infromation for the environment
in a cache directory (by default, ``/tmp/octane/deployment``). The
deployment settings for the nodes are stored to subdirectory
@@ -43,8 +49,9 @@ Install Controller commands
^^^^^^^^^^^^^^^^^^^^^^^^^^^
The upgrade automation script allows upgrading a controller that
exists in the original 6.1 environment. Select which controller
you would like to upgrade and run the following command. Replace
exists in the original 6.1 environment. Select the controller with
minimal ID out of all controllers deployed in the environment and
run the following command. Make sure to replace
``<NODE-ID>`` with the actual ID of 6.1 Controller you'd like to
upgrade: