Switch from deprecated 'ironic' CLI to 'openstack baremetal'

Change-Id: Id7e65995bb1a93db4af72252dd70077fb028fc70

doc/source/install/advanced_deployment/introspect_single_node.rst

@@ -3,12 +3,12 @@ Introspecting a Single Node
 
 In addition to bulk introspection, you can also introspect nodes one by one.
 When doing so, you must take care to set the correct node states manually.
-Use ``ironic node-show UUID`` command to figure out whether nodes are in
+Use ``openstack baremetal node show UUID`` command to figure out whether nodes
-``manageable`` or ``available`` state. For all nodes in ``available`` state,
+are in ``manageable`` or ``available`` state. For all nodes in ``available``
-start with putting a node to ``manageable`` state (see
+state, start with putting a node to ``manageable`` state (see
 :doc:`../advanced_deployment/node_states` for details)::
 
-    ironic node-set-provision-state UUID manage
+    openstack baremetal node manage <UUID>
 
 Then you can run introspection::
 
@@ -25,5 +25,4 @@ or ``None`` if introspection succeeded for this node.
 
 Do not forget to make nodes available for deployment afterwards::
 
-    ironic node-set-provision-state UUID provide
+    openstack baremetal node provide <UUID>
-

doc/source/install/advanced_deployment/introspection_data.rst

@@ -48,7 +48,7 @@ and use that to collect a list of node mac addresses::
     export IRONIC_INSPECTOR_PASSWORD=xxxxxx
 
     # Download the extra introspection data from swift:
-    for node in $(ironic node-list | grep -v UUID | awk '{print $2}');
+    for node in $(openstack baremetal node list -f value -c UUID);
       do swift -U service:ironic -K $IRONIC_INSPECTOR_PASSWORD download ironic-inspector extra_hardware-$node;
     done
 

doc/source/install/advanced_deployment/node_placement.rst

@@ -21,7 +21,7 @@ by the Nova scheduler on deployment.
 This can either be done via the nodes json file when registering the nodes, or
 alternatively via manual adjustment of the node capabilities, e.g::
 
-    ironic node-update <id> replace properties/capabilities='node:controller-0,boot_option:local'
+    openstack baremetal node set <id> --property capabilities='node:controller-0,boot_option:local'
 
 This has assigned the capability ``node:controller-0`` to the node, and this
 must be repeated (using a unique continuous index, starting from 0) for all

doc/source/install/advanced_deployment/node_states.rst

@@ -37,8 +37,7 @@ Nodes get into ``manageable`` state automatically. The ``manage`` action
 can be used to bring nodes already moved to available_ state back to
 ``manageable`` for configuration::
 
-    ironic node-set-provision-state <NAME OR UUID> manage
+    openstack baremetal node manage <NAME OR UUID>
-
 
 available
 ---------
@@ -55,4 +54,4 @@ in this state.
    which failed introspection stay in ``manageable`` state and must be
    reintrospected or made ``available`` manually::
 
-    ironic node-set-provision-state <NAME OR UUID> provide
+    openstack baremetal node provide <NAME OR UUID>

doc/source/install/advanced_deployment/profile_matching.rst

@@ -27,17 +27,17 @@ Manual profile tagging
 
 To assign a profile to a node directly, issue the following command::
 
-    ironic node-update <UUID OR NAME> replace properties/capabilities=profile:<PROFILE>,boot_option:local
+    openstack baremetal node set <UUID OR NAME> --property capabilities=profile:<PROFILE>,boot_option:local
 
 Alternatively, you can provide a number of profiles as capabilities in form of
 ``<PROFILE>_profile:1``, which later can be automatically converted to one
 assigned profile (see `Use the flavors to deploy`_ for details). For example::
 
-    ironic node-update <UUID OR NAME> replace properties/capabilities=compute_profile:1,control_profile:1,boot_option:local
+    openstack baremetal node set <UUID OR NAME> --property capabilities=compute_profile:1,control_profile:1,boot_option:local
 
 Finally, to clean all profile information from a node use::
 
-    ironic node-update <UUID OR NAME> replace properties/capabilities=boot_option:local
+    openstack baremetal node set <UUID OR NAME> --property capabilities=boot_option:local
 
 .. note::
     We can not update only a single key from the capabilities dictionary, so we

doc/source/install/advanced_deployment/root_device.rst

@@ -11,17 +11,17 @@ for more details.
 
 For example::
 
-    ironic node-update <UUID>> add properties/root_device='{"wwn": "0x4000cca77fc4dba1"}'
+    openstack baremetal node set <UUID> --property root_device='{"wwn": "0x4000cca77fc4dba1"}'
 
 To remove a hint and fallback to the default behavior::
 
-    ironic node-update <UUID> remove properties/root_device
+    openstack baremetal node unset <UUID> --property root_device
 
 Note that the root device hints should be assigned *before* both introspection
 and deployment. After changing the root device hints you should either re-run
 introspection or manually fix the ``local_gb`` property for a node::
 
-    ironic node-update <UUID> add properties/local_gb=<NEW VALUE>
+    openstack baremetal node set <UUID> --property local_gb=<NEW VALUE>
 
 Where the new value is calculated as a real disk size in GiB minus 1 GiB to
 account for partitioning (the introspection process does this calculation