You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/usage/index.rst
+18-1Lines changed: 18 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -195,7 +195,7 @@ Image-based provisioning can be accomplished through the use of `Metalsmith`_. I
195
195
Volume
196
196
~~~~~~
197
197
198
-
The process for booting a node from a volume is described in the `Ironic boot-from-volume documentation`_. There are two things to note for non-admin deployments:
198
+
In order to boot a node from a volume, two node attributes must be set as follows:
199
199
200
200
* The node owner or admin should set the `iscsi_boot` node capability prior to leasing the node.
201
201
* The node lessee should not be allowed to edit the `storage_interface` node attribute. Instead, they can run the following command to temporarily override that value (until the node is cleaned):
@@ -206,6 +206,14 @@ The process for booting a node from a volume is described in the `Ironic boot-fr
The process for booting a node from a volume is described in the `Ironic boot-from-volume documentation`_. You can also use `python-esiclient`_ to run that workflow with a single command:
0 commit comments