diff options
| author | kesper <paresh.h.sao@gmail.com> | 2020-09-09 13:11:25 +0000 |
|---|---|---|
| committer | kesper <paresh.h.sao@gmail.com> | 2020-09-10 09:24:45 +0000 |
| commit | c715e35c8748b1c144af21ac29deae8ba75e8c2f (patch) | |
| tree | 1f0549c8c12c15e7f46cc612bba20823f65ebc83 /doc/source/admin/drivers/ilo.rst | |
| parent | fc2247246b8d6543a862ca5de65b90bba3b6a77d (diff) | |
| download | ironic-c715e35c8748b1c144af21ac29deae8ba75e8c2f.tar.gz | |
Follow-up patch for One Button Secure Erase clean step
This commit addresses remaining comments on the One Button
Secure Erase clean step patch for iLO5 based Gen10 servers.
Change-Id: I606991b77dfc409a4ab0b966afdbb368fe8c2b54
Diffstat (limited to 'doc/source/admin/drivers/ilo.rst')
| -rw-r--r-- | doc/source/admin/drivers/ilo.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/source/admin/drivers/ilo.rst b/doc/source/admin/drivers/ilo.rst index 919a5064f..78a63b7d9 100644 --- a/doc/source/admin/drivers/ilo.rst +++ b/doc/source/admin/drivers/ilo.rst @@ -2052,7 +2052,7 @@ Below are the steps to perform this clean step: .. code-block:: console - openstack baremetal node clean test_node --clean-steps\ + openstack baremetal node clean $node_ident --clean-steps\ '[{"interface": "management", "step": "one_button_secure_erase"}]' * Once the clean step would triggered and node go to 'clean wait' state and @@ -2060,7 +2060,7 @@ Below are the steps to perform this clean step: .. code-block:: console - openstack baremetal node delete test_node + openstack baremetal node delete $node_ident .. note:: * Even after deleting the node, One Button Secure Erase operation would continue @@ -2071,7 +2071,7 @@ Below are the steps to perform this clean step: * One Button Secure Erase should be used with extreme caution, and only when a system is being decommissioned. During the erase the iLO network would keep disconnecting - and after the erase user will completly lose iLO access along with the credentials + and after the erase user will completely lose iLO access along with the credentials of the server, which needs to be regained by the administrator. The process can take up to a day or two to fully erase and reset all user data. |