Creating the Bare Metal Provisioning Database

1. Connect to the database service:

   # mysql -u root

2. Create the ironic database:

   mysql> CREATE DATABASE ironic CHARACTER SET utf8;

3. Create an ironic database user and grant the user access to the ironic database:

   mysql> GRANT ALL PRIVILEGES ON ironic.* TO 'ironic'@'%' IDENTIFIED BY 'PASSWORD';
   mysql> GRANT ALL PRIVILEGES ON ironic.* TO 'ironic'@'localhost' IDENTIFIED BY 'PASSWORD';

   Replace PASSWORD with a secure password that will be used to authenticate with the database server as this user.

4. Flush the database privileges to ensure that they take effect immediately:

   mysql> FLUSH PRIVILEGES;

5. Exit the mysql client:

   mysql> quit

Configuring OpenStack Compute for the Bare Metal Provisioning

1. Set Compute to use the Bare Metal Provisioning scheduler host manager:

   # openstack-config --set /etc/nova/nova.conf \
      DEFAULT scheduler_host_manager nova.scheduler.ironic_host_manager.IronicHostManager

2. Disable the Compute scheduler from tracking changes in instances:

   # openstack-config --set /etc/nova/nova.conf DEFAULT scheduler_tracks_instance_changes false

3. Set the default filters as follows:

   # openstack-config --set /etc/nova/nova.conf DEFAULT baremetal_scheduler_default_filters AvailabilityZoneFilter,ComputeFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter

4. Set Compute to use default Bare Metal Provisioning scheduling filters:

   # openstack-config --set /etc/nova/nova.conf \
      DEFAULT scheduler_use_baremetal_filters True

5. Set Compute to use the correct authentication details for Bare Metal Provisioning:

   # openstack-config --set /etc/nova/nova.conf \
      ironic admin_username ironic
   # openstack-config --set /etc/nova/nova.conf \
      ironic admin_password PASSWORD
   # openstack-config --set /etc/nova/nova.conf \
      ironic admin_url http://IDENTITY_IP:35357/v2.0
   # openstack-config --set /etc/nova/nova.conf \
      ironic admin_tenant_name service
   # openstack-config --set /etc/nova/nova.conf \
      ironic api_endpoint http://IRONIC_API_IP:6385/v1

   Replace the following values:

   • Replace PASSWORD with the password that Bare Metal Provisioning uses to authenticate with Identity.
   • Replace IDENTITY_IP with the IP address or host name of the server hosting Identity.
   • Replace IRONIC_API_IP with the IP address or host name of the server hosting the Bare Metal Provisioning API service.

6. Set the nova database credentials on the ironic Compute node:

   # openstack-config --set /etc/nova/nova.conf database connection "mysql+pymysql://nova:NOVA_DB_PASSWORD@DB_IP/nova"

7. Restart the Compute scheduler service on the Compute controller nodes:

   # systemctl restart openstack-nova-scheduler.service

8. Restart the compute service on the compute nodes:

   # systemctl restart openstack-nova-compute.service

1. On your overcloud controller, verify which dnsmasq file the DHCP Agent is using:

   # grep ^dnsmasq_config_file /etc/neutron/dhcp_agent.ini
   
   dnsmasq_config_file =/etc/neutron/dnsmasq-neutron.conf

2. Edit this file and add the following lines at the end of the file:

   # Create the "ipxe" tag if request comes from iPXE user class
   
   dhcp-userclass=set:ipxe,iPXE

3. Save the file and restart the OpenStack Networking DHCP Agent service:

   # systemctl restart neutron-dhcp-agent.service

Subscribing to the Required Channels

1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:

   # subscription-manager register

2. Find entitlement pools containing the channels required to install Bare Metal Provisioning:

   # subscription-manager list --available | grep -A13 "Red Hat Enterprise Linux Server"
   # subscription-manager list --available | grep -A13 "Red Hat OpenStack Platform"

3. Use the pool identifiers located in the previous step to attach the Red Hat Enterprise Linux 7 Server and Red Hat OpenStack Platform entitlements:

   # subscription-manager attach --pool=POOL_ID

4. Enable the required channels:

   # subscription-manager repos --enable=rhel-7-server-rpms \
   --enable=rhel-7-server-openstack-8-rpms \
   --enable=rhel-7-server-rh-common-rpms --enable=rhel-7-server-optional-rpms \
   --enable=rhel-7-server-openstack-8-optools-rpms

1. Create the necessary directories for iPXE, map-files and copy the undionly.kpxe boot image, iPXE and map-file into place:

   # mkdir /httpboot
   # mkdir /tftpboot
   # echo 'r ([/]) /tftpboot/\1' > /tftpboot/map-file
   # echo 'r ^(/tftpboot/) /tftpboot/\2' >> /tftpboot/map-file
   # cp /usr/share/ipxe/undionly.kpxe /tftpboot/
   # chown -R ironic:ironic /httpboot
   # chown -R ironic:ironic /tftpboot

2. By default, the Compute node deployed by the director runs SELinux in Enforcing mode. To avoid getting permission errors when trying iPXE boot, make sure you set the appropriate labels on these directories. To apply these labels, run the following commands as a root user:

   # semanage fcontext -a -t httpd_sys_content_t "/httpboot(/.*)?"
   # restorecon -Rv /httpboot
   # semanage fcontext -a -t tftpdir_t "/tftpboot(/.*)?"
   # restorecon -Rv /tftpboot

3. Configure HTTP so that it can serve requests for the images. The httpd package is already installed, so it is a matter of creating the appropriate virtual host entry and starting the service.

   Note

   The /etc/httpd/conf.d contains number of files. As Red Hat utilizes a single overcloud full image for all the nodes, it includes these files on all the nodes even though it is only used on the Controller node. You can delete the contents of /etc/httpd/conf.d or copy them somewhere else as they are not used.

   Create a new file in for iPXE configuration. You can name this file anything, making sure it is in the .conf format and has the following contents:

   # cat 10-ipxe_vhost.conf
   Listen 8088
   <VirtualHost *:8088>
       DocumentRoot "/httpboot"
       <Directory "/httpboot">
           Options Indexes FollowSymLinks
           AllowOverride None
           Order allow,deny
           Allow from all
           Require all granted
       </Directory>
   
       ## Logging
       ErrorLog "/var/log/httpd/ironic_error.log"
       ServerSignature Off
       CustomLog "/var/log/httpd/ironic_access.log" combined
   </VirtualHost>

   The above virtual host configuration configures HTTPD to listed on all addresses on port 8088 and sets the document root for all requests to that port to go to /httpboot.

4. Save this file and enable and restart HTTPD service on the Compute node:

   # systemctl enable httpd.service
   # systemctl start httpd.service

Configuring OpenStack Compute to Use Bare Metal Provisioning

1. Set Compute to use the clustered compute manager:

   # openstack-config --set /etc/nova/nova.conf \
      DEFAULT compute_manager ironic.nova.compute.manager.ClusteredComputeManager

2. Set the virtual RAM to physical RAM allocation ratio:

   # openstack-config --set /etc/nova/nova.conf \
      DEFAULT ram_allocation_ratio 1.0

3. Set the amount of disk space in MB to reserve for the host:

   # openstack-config --set /etc/nova/nova.conf \
      DEFAULT reserved_host_memory_mb 0

4. Set Compute to use the Bare Metal Provisioning driver:

   # openstack-config --set /etc/nova/nova.conf \
      DEFAULT compute_driver nova.virt.ironic.IronicDriver

5. Set Compute to use the correct authentication details for Bare Metal Provisioning:

   # openstack-config --set /etc/nova/nova.conf \
      ironic admin_username ironic
   # openstack-config --set /etc/nova/nova.conf \
      ironic admin_password PASSWORD
   # openstack-config --set /etc/nova/nova.conf \
      ironic admin_url http://IDENTITY_IP:35357/v2.0
   # openstack-config --set /etc/nova/nova.conf \
      ironic admin_tenant_name service
   # openstack-config --set /etc/nova/nova.conf \
      ironic api_endpoint http://IRONIC_API_IP:6385/v1

   Replace the following values:

   • Replace PASSWORD with the password that Bare Metal Provisioning uses to authenticate with Identity.
   • Replace IDENTITY_IP with the IP address or host name of the server hosting Identity.
   • Replace IRONIC_API_IP with the IP address or host name of the server hosting the Bare Metal Provisioning API service.

6. Restart the Compute scheduler service on the Compute controller nodes:

   # systemctl restart openstack-nova-scheduler.service

7. Restart the compute service on the compute nodes:

   # systemctl restart openstack-nova-compute.service

Configuring OpenStack Networking to Communicate with Bare Metal Provisioning

1. Set up the shell to access Identity as the administrative user:

   # source ~stack/overcloudrc

2. Create the flat network over which to provision bare metal instances:

   # neutron net-create --tenant-id TENANT_ID sharednet1 --shared \
   --provider:network_type flat --provider:physical_network PHYSNET

   Replace TENANT_ID with the unique identifier of the tenant on which to create the network. Replace PHYSNET with the name of the physical network.

3. Create the subnet on the flat network:

   # neutron subnet-create sharednet1 NETWORK_CIDR --name SUBNET_NAME \
   --ip-version 4 --gateway GATEWAY_IP --allocation-pool \
   start=START_IP,end=END_IP --enable-dhcp

   Replace the following values:

   • Replace NETWORK_CIDR with the Classless Inter-Domain Routing (CIDR) representation of the block of IP addresses the subnet represents. The block of IP addresses specified by the range started by START_IP and ended by END_IP must fall within the block of IP addresses specified by NETWORK_CIDR.
   • Replace SUBNET_NAME with a name for the subnet.
   • Replace GATEWAY_IP with the IP address or host name of the system that will act as the gateway for the new subnet. This address must be within the block of IP addresses specified by NETWORK_CIDR, but outside of the block of IP addresses specified by the range started by START_IP and ended by END_IP.
   • Replace START_IP with the IP address that denotes the start of the range of IP addresses within the new subnet from which floating IP addresses will be allocated.
   • Replace END_IP with the IP address that denotes the end of the range of IP addresses within the new subnet from which floating IP addresses will be allocated.

4. Attach the network and subnet to the router to ensure the metadata requests are served by the OpenStack Networking service.

   # neutron router-create ROUTER_NAME

   Replace ROUTER_NAME with a name for the router.

5. Add the Bare Metal subnet as an interface on this router:

   # neutron router-interface-add ROUTER_NAME BAREMETAL_SUBNET

   Replace ROUTER_NAME with the name of your router and BAREMETAL_SUBNET with the ID or subnet name that you previously created. This allows the metadata requests from cloud-init to be served and the node configured.

6. Update the /etc/ironic/ironic.conf file on the Compute node running the Bare Metal Provisioning service to utilize the same network for the cleaning service. Login to the Compute node where the Bare Metal Provisioning service is running and execute the following as a root user:

   # openstack-config --set /etc/ironic/ironic.conf neutron cleaning_network_uuid NETWORK_UUID

   Replace the NETWORK_UUID with the ID of the Bare Metal Provisioning Network created in the previous steps.

7. Restart the Bare Metal Provisioning service:

   # systemctl restart openstack-ironic-conductor.service

1. List existing flavors:

   # openstack flavor list

2. Create a new flavor for the Bare Metal Provisioning service:

   # openstack flavor create --id auto --ram RAM --vcpus VCPU --disk DISK --public baremetal

   Replace RAM with the RAM memory, VCPU with the number of vCPUs and DISK with the disk storage value.

3. Set the flavor to boot from the local disk, otherwise the default netboot method will be used.

   # openstack flavor set --property capabilities:boot_option='local' baremetal

4. Verify that the new flavor is created with the respective values:

   # openstack flavor list

1. Source the overcloudrc file and import the .json file:

   # source ~stack/overcloudrc
   # openstack baremetal import --json ./baremetal.json

2. Update the bare metal node in the Bare Metal Provisioning service to use the deployed images as the initial boot image by specifying the deploy_kernel and deploy_ramdisk in the driver_info section of the node:

   # ironic node-update NODE_UUID add driver_info/deploy_kernel=DEPLOY_KERNEL_ID driver_info/deploy_ramdisk=DEPLOY_RAMDISK_ID

Adding a Node with Hardware Introspection

1. Set up the shell to use Identity as the administrative user:

   # source ~/keystonerc_admin

2. Add a new node:

   # ironic node-create -d DRIVER_NAME

   Replace DRIVER_NAME with the name of the driver that Bare Metal Provisioning will use to provision this node. You must have enabled this driver in the /etc/ironic/ironic.conf file. To create a node, you must, at a minimum, specify the driver name.

   Important

   Note the unique identifier for the node.

3. You can refer to a node by a logical name or by its UUID. Optionally assign a logical name to the node:

   # ironic node-update NODE_UUID add name=NAME

   Replace NODE_UUID with the unique identifier for the node. Replace NAME with a logical name for the node.

4. Determine the node information that is required by the driver, then update the node driver information to allow Bare Metal Provisioning to manage the node:

   # ironic driver-properties DRIVER_NAME
   # ironic node-update NODE_UUID add \
      driver_info/PROPERTY=VALUE \
      driver_info/PROPERTY=VALUE

   Replace the following values:

   • Replace DRIVER_NAME with the name of the driver for which to show properties. The information is not returned unless the driver has been enabled in the /etc/ironic/ironic.conf file.
   • Replace NODE_UUID with the unique identifier for the node. Alternatively, use the node’s logical name.
   • Replace PROPERTY with a required property returned by the ironic driver-properties command.
   • Replace VALUE with a valid value for that property.

5. Specify the deploy kernel and deploy ramdisk for the node driver:

   # ironic node-update NODE_UUID add \
     driver_info/deploy_kernel=KERNEL_UUID \
     driver_info/deploy_ramdisk=INITRAMFS_UUID

   Replace the following values:

   • Replace NODE_UUID with the unique identifier for the node. Alternatively, use the node’s logical name.
   • Replace KERNEL_UUID with the unique identifier for the .kernel image that was uploaded to the Image service.
   • Replace INITRAMFS_UUID with the unique identifier for the .initramfs image that was uploaded to the Image service.

6. Configure the node to reboot after initial deployment from a local boot loader installed on the node’s disk, instead of via PXE or virtual media. The local boot capability must also be set on the flavor used to provision the node. To enable local boot, the image used to deploy the node must contain grub2. Configure local boot:

   # ironic node-update NODE_UUID add \
      properties/capabilities="boot_option:local"

   Replace NODE_UUID with the unique identifier for the node. Alternatively, use the node’s logical name.

7. Move the bare metal node to manageable state:

   # ironic node-set-provision-state NODE_UUID manage

   Replace NODE_UUID with the unique identifier for the node. Alternatively, use the node’s logical name.

8. Start introspection:

   # openstack baremetal introspection start NODE_UUID --discoverd-url http://overcloud IP:5050

   • Replace NODE_UUID with the unique identifier for the node. Alternatively, use the node’s logical name. The node discovery and introspection process must run to completion before the node can be provisioned. To check the status of node introspection, run ironic node-list and look for Provision State. Nodes will be in available state after successful introspection.
   • Replace overcloud IP with the service_url value that was previously set in ironic.conf.

9. Validate the node’s setup:

   # ironic node-validate NODE_UUID
   +------------+--------+----------------------------+
   | Interface  | Result | Reason                     |
   +------------+--------+----------------------------+
   | console    | None   | not supported              |
   | deploy     | True   |                            |
   | inspect    | True   |                            |
   | management | True   |                            |
   | power      | True   |                            |
   +------------+--------+----------------------------+

   Replace NODE_UUID with the unique identifier for the node. Alternatively, use the node’s logical name. The output of the command above should report either True or None for each interface. Interfaces marked None are those that you have not configured, or those that are not supported for your driver.

Adding a Node without Hardware Introspection

1. Set up the shell to use Identity as the administrative user:

   # source ~/keystonerc_admin

2. Add a new node:

   # ironic node-create -d DRIVER_NAME

   Replace DRIVER_NAME with the name of the driver that Bare Metal Provisioning will use to provision this node. You must have enabled this driver in the /etc/ironic/ironic.conf file. To create a node, you must, at a minimum, specify the driver name.

   Important

   Note the unique identifier for the node.

3. You can refer to a node by a logical name or by its UUID. Optionally assign a logical name to the node:

   # ironic node-update NODE_UUID add name=NAME

   Replace NODE_UUID with the unique identifier for the node. Replace NAME with a logical name for the node.

4. Determine the node information that is required by the driver, then update the node driver information to allow Bare Metal Provisioning to manage the node:

   # ironic driver-properties DRIVER_NAME
   # ironic node-update NODE_UUID add \
      driver_info/PROPERTY=VALUE \
      driver_info/PROPERTY=VALUE

   Replace the following values:

   • Replace DRIVER_NAME with the name of the driver for which to show properties. The information is not returned unless the driver has been enabled in the /etc/ironic/ironic.conf file.
   • Replace NODE_UUID with the unique identifier for the node. Alternatively, use the node’s logical name.
   • Replace PROPERTY with a required property returned by the ironic driver-properties command.
   • Replace VALUE with a valid value for that property.

5. Specify the deploy kernel and deploy ramdisk for the node driver:

   # ironic node-update NODE_UUID add \
     driver_info/deploy_kernel=KERNEL_UUID \
     driver_info/deploy_ramdisk=INITRAMFS_UUID

   Replace the following values:

   • Replace NODE_UUID with the unique identifier for the node. Alternatively, use the node’s logical name.
   • Replace KERNEL_UUID with the unique identifier for the .kernel image that was uploaded to the Image service.
   • Replace INITRAMFS_UUID with the unique identifier for the .initramfs image that was uploaded to the Image service.

6. Update the node’s properties to match the hardware specifications on the node:

   # ironic node-update NODE_UUID add \
      properties/cpus=CPU \
      properties/memory_mb=RAM_MB \
      properties/local_gb=DISK_GB \
      properties/cpu_arch=ARCH

   Replace the following values:

   • Replace NODE_UUID with the unique identifier for the node. Alternatively, use the node’s logical name.
   • Replace CPU with the number of CPUs to use.
   • Replace RAM_MB with the RAM (in MB) to use.
   • Replace DISK_GB with the disk size (in GB) to use.
   • Replace ARCH with the architecture type to use.

7. Configure the node to reboot after initial deployment from a local boot loader installed on the node’s disk, instead of via PXE or virtual media. The local boot capability must also be set on the flavor used to provision the node. To enable local boot, the image used to deploy the node must contain grub2. Configure local boot:

   # ironic node-update NODE_UUID add \
      properties/capabilities="boot_option:local"

   Replace NODE_UUID with the unique identifier for the node. Alternatively, use the node’s logical name.

8. Inform Bare Metal Provisioning of the network interface cards on the node. Create a port with each NIC’s MAC address:

   # ironic port-create -n NODE_UUID -a MAC_ADDRESS

   Replace NODE_UUID with the unique identifier for the node. Replace MAC_ADDRESS with the MAC address for a NIC on the node.

9. Validate the node’s setup:

   # ironic node-validate NODE_UUID
   +------------+--------+----------------------------+
   | Interface  | Result | Reason                     |
   +------------+--------+----------------------------+
   | console    | None   | not supported              |
   | deploy     | True   |                            |
   | inspect    | None   | not supported              |
   | management | True   |                            |
   | power      | True   |                            |
   +------------+--------+----------------------------+

   Replace NODE_UUID with the unique identifier for the node. Alternatively, use the node’s logical name. The output of the command above should report either True or None for each interface. Interfaces marked None are those that you have not configured, or those that are not supported for your driver.

Creating Virtualized Bare Metal Nodes

1. Access the Virtual Machine Manager from the libvirt host.

2. Create two virtual machines with the following configuration:

   • 1 vCPU
   • 2048 MB of memory
   • Network Boot (PXE)
   • 20 GB storage
   • Network source: Host device eth0: macvtap and Source mode: Bridge. Selecting macvtap sets the virtual machines to share the host’s Ethernet network interface. This way the Bare Metal Provisioning node has direct access to the virtualized nodes.
3. Shut down both virtual machines.

Creating an SSH Key Pair

1. On the Bare Metal Provisioning node, create a new SSH key:

   # ssh-keygen -t rsa -b 2048 -C "user@domain.com" -f ./virtkey

   Replace user@domain.com with an email address or other comment that identifies this key. When the command prompts you for a passphrase, press Enter to proceed without a passphrase. The command creates two files: the private key (virtkey) and the public key (virtkey.pub).

2. Copy the contents of the public key into the /root/.ssh/authorized_keys file of the libvirt host’s root user:

   # ssh-copy-id -i virtkey root@LIBVIRT_HOST

   Replace LIBVIRT_HOST with the IP address or host name of the libvirt host.

Adding Virtualized Nodes as Bare Metal Nodes

1. On the Bare Metal Provisioning conductor service node, enable the pxe_ssh driver:

   # openstack-config --set /etc/ironic/ironic.conf \
      DEFAULT enabled_drivers pxe_ssh

   If you are adding pxe_ssh to a list of existing drivers, open the file and add the driver to the list in enabled_drivers, separated by a comma.

2. Set up the shell to use Identity as the administrative user:

   # source ~/keystonerc_admin

3. Add the first node, and register the SSH details for the libvirt host:

   # ironic node-create -d pxe_ssh -n Node1 \
      -i ssh_virt_type=virsh \
      -i ssh_username=root \
      -i ssh_key_filename=VIRTKEY_FILE_PATH \
      -i ssh_address=LIBVIRT_HOST_IP \
      -i deploy_kernel=KERNEL_UUID \
      -i deploy_ramdisk=INITRAMFS_UUID

   Replace the following values:

   • Replace VIRTKEY_FILE_PATH with the absolute file path of the virtkey SSH private key file.
   • Replace LIBVIRT_HOST_IP with the IP address or host name of the libvirt host.
   • Replace KERNEL_UUID with the unique identifier for the .kernel image that was uploaded to the Image service.
   • Replace INITRAMFS_UUID with the unique identifier for the .initramfs image that was uploaded to the Image service.
4. Add a second node, using the same command as above, and replacing Node1 with Node2.

5. Configure the node to reboot after initial deployment from a local boot loader installed on the node’s disk, instead of via PXE or virtual media. The local boot capability must also have been set on the flavor you will use to provision the node. To enable local boot, the image used to deploy the node must contain grub2. Configure local boot:

   # ironic node-update Node1 add \
      properties/capabilities="boot_option:local"
   # ironic node-update Node2 add \
      properties/capabilities="boot_option:local"

6. Move the nodes to the manageable state:

   # ironic node-set-provision-state Node1 manage
   # ironic node-set-provision-state Node2 manage

7. Start introspection on the nodes:

   # ironic node-set-provision-state Node1 inspect
   # ironic node-set-provision-state Node2 inspect

   The node discovery and introspection process must run to completion before the node can be provisioned. To check the status of node introspection, run ironic node-list and look for Provision State. Nodes will be in the available state after successful introspection.

8. Validate the node’s setup:

   # ironic node-validate Node1
   # ironic node-validate Node2
   +------------+--------+----------------------------+
   | Interface  | Result | Reason                     |
   +------------+--------+----------------------------+
   | console    | None   | not supported              |
   | deploy     | True   |                            |
   | inspect    | True   |                            |
   | management | True   |                            |
   | power      | True   |                            |
   +------------+--------+----------------------------+

   The output of the command above should report either True or None for each interface. Interfaces marked None are those that you have not configured, or those that are not supported for your driver.

9. When the nodes have been successfully added, launch two instances using Chapter 3, Launch Bare Metal Instances.

1. Register the physical node in ironic by specifying the hardware components. For example:

   # ironic node-create -d fake_pxe -p cpus=1 -p memory_mb=1024 -p local_gb=15 -p cpu_arch=amd64

2. Retrieve the new node’s UUID:

   # ironic node-list

3. Create a port for the node that matches the MAC address of the physical Windows node.

   # ironic port-create -n [NODE_UUID] -a [NIC_MAC]

   For example:

   # ironic port-create -n 3b3d3fd4-4621-427f-a78d-054a1ef17a0a -a 52:54:00:85:76:53

4. Set the node to maintenance mode:

   # ironic node-set-maintenance [NODE_UUID] true
   # ironic node-set-provision-state [NODE_UUID] manage

5. Perform introspection of the new node:

   # openstack baremetal introspection start [NODE_UUID] --discoverd-url http://[KEYSTONE_URL]:5050

   • Replace [KEYSTONE_URL] with the IP address of the keystone service.

     Note: If using the FAKE_PXE driver, power on the node manually once the ironic node-list state moves to deploy wait-callback.

6. Once introspection has completed, turn off maintenance mode:

   # ironic node-set-maintenance [NODE UUID] false
   # ironic node-set-provision-state [NODE UUID] provide

7. Create a keypair for authentication to the instance:

   # nova keypair-add --pub_key ~/.ssh/id_rsa.pub [KEY_NAME]

8. Enable local boot for the node:

   # ironic node-update [NODE_UUID] add properties/capabilities="boot_option:local"

9. Use nova to boot the node:

   # nova boot --nic net-id=[NETWORK_UUID] --flavor [FLAVOR_NAME] --image [IMAGE_UUID/IMAGE_NAME] --keyname [INSTANCE_NAME]

   Replace the following values:

   • Replace [NETWORK_UUID] with the unique identifier for the network that was created for use with Bare Metal Provisioning.
   • Replace [FLAVOR_NAME] with the name of the flavor that was created for the node.
   • Replace [IMAGE_UUID] with the unique identifier for the disk image that was uploaded to the Image service.
   • Replace [INSTANCE_NAME] with a name for the bare metal instance.

10. Retrieve the instance password:

    # nova get-password [INSTANCE_NAME]  /path/to/your/keypairs/private/key

11. Review the status of the instance:

    # nova list

1. Add a security group rule allowing Remote Desktop traffic on TCP/UDP 3389.

2. Use the nova command to retrieve the security keys:

   # nova get-password [INSTANCE_NAME] /path/to/your/keypairs/private/key

   • Replace [INSTANCE_NAME] with the name of the bare metal instance.