summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZuul <zuul@review.openstack.org>2018-06-07 05:10:33 +0000
committerGerrit Code Review <review@openstack.org>2018-06-07 05:10:33 +0000
commitfdd4340b82409e3fdc56f39174c0cc6a2eeee87d (patch)
tree248cedcd62e667c5c4a6e70c61aba7be455929be
parente3b1b471194be2a3d4c59c5d9a872aa3bbd620ba (diff)
parentfd805e212a38f8617b752e0f322acc95fe4dd622 (diff)
downloadironic-fdd4340b82409e3fdc56f39174c0cc6a2eeee87d.tar.gz
Merge "[Doc] Scheduling needs validated 'management' interface"
-rw-r--r--doc/source/install/enrollment.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/source/install/enrollment.rst b/doc/source/install/enrollment.rst
index 3dfd5bcb0..cb7a1e63e 100644
--- a/doc/source/install/enrollment.rst
+++ b/doc/source/install/enrollment.rst
@@ -18,8 +18,8 @@ they are in the ``available`` provision state.
.. note::
Any bare metal node that is visible to the Compute service may have a
- workload scheduled to it, if both the ``power`` and ``deploy`` interfaces
- pass the ``validate`` check.
+ workload scheduled to it, if both the ``power`` and ``management``
+ interfaces pass the ``validate`` check.
If you wish to exclude a node from the Compute service's scheduler, for
instance so that you can perform maintenance on it, you can set the node to
"maintenance" mode.