5.3. Tagging Nodes into Profiles
After registering and inspecting the hardware of each node, you will tag them into specific profiles. These profile tags match your nodes to flavors, and in turn the flavors are assigned to a deployment role. Default profile flavors
block-storageare created during Undercloud installation and are usable without modification in most environments.
For a large number of nodes, use automatic profile tagging. See Appendix C, Automatic Profile Tagging for more details.
To tag a node into a specific profile, add a
profileoption to the
properties/capabilitiesparameter for each node. For example, to tag your nodes to use Controller and Compute profiles respectively, use the following commands:
$ ironic node-update 58c3d07e-24f2-48a7-bbb6-6843f0e8ee13 add properties/capabilities='profile:compute,boot_option:local' $ ironic node-update 1a4e30da-b6dc-499d-ba87-0bd8a3819bc0 add properties/capabilities='profile:control,boot_option:local'
The addition of the
profile:controloptions tag the two nodes into each respective profiles.
These commands also set the
boot_option:localparameter, which defines the boot mode for each node.
The director currently does not support UEFI boot mode.
After completing node tagging, check the assigned profiles or possible profiles:
$ openstack overcloud profiles list