openstack/ironic
Code Issues Proposed changes

Fixes wrong steps to perform migration of nodes

Browse Source 
In the OneView drive docs, the steps to migrate active nodes from
pre-allocation do dynamic allocation were wrongly indicating to
remove the Server Profile.

Closes-Bug: 1626548
Change-Id: I5b9d6a975af7002a95a941e5e102fb044be9621c
This commit is contained in:
Ricardo Araújo Santos 2016-09-22 10:58:16 -03:00
parent e041e238be
commit f9f318e9cc
1 changed files with 14 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/source/drivers/oneview.rst
View File

@ -337,16 +337,24 @@ List nodes that are in `active` state doing::
Execute the following steps for each node:
1. Remove the node's ``Server Profile`` from the ``Server Hardware`` in OneView.
To identify which ``Server Profile`` is associated with a node check the
property ``server_hardware_uri`` in the ``driver_info`` namespace doing::
1. Identify the ``Server Hardware`` UUID looking at ``server_hardware_uri``
property (formatted as ``/rest/server-hardware/<server-hardware-uuid>``) in
the node's ``driver_info`` namespace doing::
$ ironic node-show <node-uuid> --fields driver_info
2. Then, using the ``server_hardware_uri``, log into OneView and remove the
``Server Profile``.
2. Log into OneView and find the ``Server Hardware`` searching for the
``Server Hardware`` UUID identified in step 1. On the overview section,
find the applied ``Server Profile`` entry, click on it and copy the
``Server Profile`` URI. The copied excerpt should look like
``/rest/server-profiles/<server-profile-uuid>``.
3. Finally, set the `dynamic_allocation` flag in the ``driver_info`` namespace
3. Then, set the copied excerpt from the ``Server Profile`` URI to the property
``applied_server_profile_uri`` in the ``driver_info`` namespace doing::
$ ironic node-update <node-uuid> add driver_info/applied_server_profile_uri=<server_profile_uri>
4. Finally, set the `dynamic_allocation` flag in the ``driver_info`` namespace
to ``True`` in order to finish the migration of the node doing::
$ ironic node-update <node-uuid> add driver_info/dynamic_allocation=True