Document node auto-enrollment
Change-Id: I4efd48f84ce9747a85bdcf26da84add95500ed04
This commit is contained in:
Dmitry Tantsur
parent
8cf7e34ea9
commit
d83d063c70
|
|
@ -7,6 +7,7 @@ Documentation on how to do advanced configuration of baremetal nodes in
|
|||
.. toctree::
|
||||
|
||||
node_states
|
||||
node_discovery
|
||||
root_device
|
||||
introspect_single_node
|
||||
profile_matching
|
||||
|
|
|
|||
|
|
@ -0,0 +1,113 @@
|
|||
Node Discovery
|
||||
==============
|
||||
|
||||
As an alternative to creating an inventory file (``instackenv.json``) and
|
||||
enrolling nodes from it, you can discover and enroll the nodes automatically.
|
||||
|
||||
Automatic enrollment of new nodes
|
||||
---------------------------------
|
||||
|
||||
You can enable **ironic-inspector** to automatically enroll all unknown nodes
|
||||
that boot the introspection ramdisk. See `ironic-inspector discovery
|
||||
documentation`_ for more details on the process.
|
||||
|
||||
Configuration
|
||||
~~~~~~~~~~~~~
|
||||
|
||||
Set the following in your ``undercloud.conf`` before installing the undercloud:
|
||||
|
||||
.. code-block:: ini
|
||||
|
||||
enable_node_discovery = True
|
||||
|
||||
Make sure to get (or build) and upload the introspection image, as described
|
||||
in :doc:`../basic_deployment/basic_deployment_cli`.
|
||||
|
||||
Basic usage
|
||||
~~~~~~~~~~~
|
||||
|
||||
After the discovery is enabled, any node that boots the introspection ramdisk
|
||||
and posts back to **ironic-inspector** will be enrolled in **ironic**. Make
|
||||
sure the nodes are connected to the provisioning network, and default to
|
||||
booting from PXE. Power them on using any available means (e.g. by pushing the
|
||||
power button on them).
|
||||
|
||||
New nodes appear in the ``enroll`` state by default and use the
|
||||
``pxe_ipmitool`` driver (configurable via the ``discovery_default_driver``
|
||||
option in ``undercloud.conf``). You have to set the power credentials
|
||||
for these nodes and make them available. See :doc:`node_states` for details.
|
||||
|
||||
Using introspection rules
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Alternatively, you can use **ironic-inspector** introspection rules to
|
||||
automatically set the power credentials based on certain properties.
|
||||
|
||||
For example, to set the same credentials for all new nodes, you can use
|
||||
the following rules:
|
||||
|
||||
.. code-block:: json
|
||||
|
||||
[
|
||||
{
|
||||
"description": "Set default IPMI credentials",
|
||||
"conditions": [
|
||||
{"op": "eq", "field": "data://auto_discovered", "value": true}
|
||||
],
|
||||
"actions": [
|
||||
{"action": "set-attribute", "path": "driver_info/ipmi_username",
|
||||
"value": "admin"},
|
||||
{"action": "set-attribute", "path": "driver_info/ipmi_password",
|
||||
"value": "paSSw0rd"}
|
||||
]
|
||||
}
|
||||
]
|
||||
|
||||
To set specific credentials for a certain vendor, use something like:
|
||||
|
||||
.. code-block:: json
|
||||
|
||||
[
|
||||
{
|
||||
"description": "Set default IPMI credentials",
|
||||
"conditions": [
|
||||
{"op": "eq", "field": "data://auto_discovered", "value": true},
|
||||
{"op": "ne", "field": "data://inventory.system_vendor.manufacturer",
|
||||
"value": "Dell Inc."}
|
||||
],
|
||||
"actions": [
|
||||
{"action": "set-attribute", "path": "driver_info/ipmi_username",
|
||||
"value": "admin"},
|
||||
{"action": "set-attribute", "path": "driver_info/ipmi_password",
|
||||
"value": "paSSw0rd"}
|
||||
]
|
||||
},
|
||||
{
|
||||
"description": "Set the vendor driver for Dell hardware",
|
||||
"conditions": [
|
||||
{"op": "eq", "field": "data://auto_discovered", "value": true},
|
||||
{"op": "eq", "field": "data://inventory.system_vendor.manufacturer",
|
||||
"value": "Dell Inc."}
|
||||
],
|
||||
"actions": [
|
||||
{"action": "set-attribute", "path": "driver", "value": "pxe_drac"},
|
||||
{"action": "set-attribute", "path": "driver_info/drac_username",
|
||||
"value": "admin"},
|
||||
{"action": "set-attribute", "path": "driver_info/drac_password",
|
||||
"value": "paSSw0rd"},
|
||||
{"action": "set-attribute", "path": "driver_info/drac_address",
|
||||
"value": "{data[inventory][bmc_address]}"}
|
||||
]
|
||||
}
|
||||
]
|
||||
|
||||
The rules should be put to a file and uploaded to **ironic-inspector** before
|
||||
the discovery process:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
openstack baremetal introspection rule import /path/to/rules.json
|
||||
|
||||
See :doc:`profile_matching` for more examples on introspection rules.
|
||||
|
||||
.. _ironic-inspector discovery documentation: https://docs.openstack.org/developer/ironic-inspector/usage.html#discovery
|
||||
|
|
@ -297,6 +297,9 @@ as a root device. Please see :ref:`root_device` for details.
|
|||
with nodes after registration, please follow
|
||||
:ref:`node_registration_problems`.
|
||||
|
||||
Another approach to enrolling node is
|
||||
:doc:`../advanced_deployment/node_discovery`.
|
||||
|
||||
.. _introspection:
|
||||
|
||||
Introspect Nodes
|
||||
|
|
|
|||
|
|
@ -239,6 +239,10 @@ For example::
|
|||
]
|
||||
}
|
||||
|
||||
.. note::
|
||||
You don't need to create this file, if you plan on using
|
||||
:doc:`../advanced_deployment/node_discovery`.
|
||||
|
||||
Ironic Drivers
|
||||
^^^^^^^^^^^^^^
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue