Additional Ways to Verify the Bare Metal Service:

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

   $ source ~/overcloudrc

2. Check that the nova-compute service is running on the controller nodes:

   $ openstack compute service list -c Binary -c Host -c Status

3. If you have changed the default ironic drivers, make sure the required drivers are enabled:

   $ openstack baremetal driver list

4. Ensure that the ironic endpoints are listed:

   $ openstack catalog list

Configuring OpenStack Networking to Communicate with the Bare Metal Service

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

   $ source ~/overcloudrc

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

   $ openstack network create \
     --provider-network-type flat \
     --provider-physical-network baremetal \
     --share NETWORK_NAME

   Replace NETWORK_NAME with a name for this network. The name of the physical network over which the virtual network is implemented, (in this case baremetal), was set earlier in ~/templates/network-environment.yaml, with the parameter NeutronBridgeMappings.

3. Create the subnet on the flat network:

   $ openstack subnet create \
     --network NETWORK_NAME \
     --subnet-range NETWORK_CIDR \
     --ip-version 4 \
     --gateway GATEWAY_IP \
     --allocation-pool start=START_IP,end=END_IP \
     --dhcp SUBNET_NAME

   Replace the following values:

   • Replace SUBNET_NAME with a name for the subnet.
   • Replace NETWORK_NAME with the name of the provisioning network you created in the previous step.
   • 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 GATEWAY_IP with the IP address or host name of the router interface 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.

   $ openstack router create ROUTER_NAME

   Replace ROUTER_NAME with a name for the router.

5. Add the Bare Metal subnet to this router:

   $ openstack router add subnet 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. Configure cleaning by providing the provider network UUID on the controller running the Bare Metal Service:

   ~/templates/ironic.yaml

   parameter_defaults:
       ControllerExtraConfig:
           ironic::conductor::cleaning_network_uuid: UUID

   Replace UUID with the UUID of the bare metal network created in the previous steps.

   You can find the UUID using openstack network show:

   openstack network show NETWORK_NAME -f value -c id

   Note

   This configuration must be done after the initial overcloud deployment, because the UUID for the network isn’t available beforehand.

7. Apply the changes by redeploying the overcloud with the openstack overcloud deploy command as described in Section 3.4, “Deploying the Overcloud”.

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

   $ source ~/overcloudrc

2. List existing flavors:

   $ openstack flavor list

3. Create a new flavor for the Bare Metal service:

   $ openstack flavor create \
     --id auto --ram RAM \
     --vcpus VCPU --disk DISK \
     --property baremetal=true \
     --public baremetal

   Replace RAM with the amount of memory, VCPU with the number of vCPUs and DISK with the disk storage value. The property baremetal is used to distinguish bare metal from virtual instances.

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

   $ openstack flavor list

1. Prepare an inventory file with the node details, import the file into the Bare Metal service, then make the nodes available.
2. Register a physical machine as a bare metal node, then manually add its hardware details and create ports for each of its Ethernet MAC addresses. These steps can be performed on any node which has your overcloudrc file.

Creating a Host Aggregate

1. Set the baremetal property to true on the baremetal flavor.

   $ openstack flavor set baremetal --property baremetal=true

2. Set the baremetal property to false on the flavors used for virtual instances.

   $ openstack flavor set FLAVOR_NAME --property baremetal=false

3. Create a host aggregate called baremetal-hosts:

   $ openstack aggregate create --property baremetal=true baremetal-hosts

4. Add each controller node to the baremetal-hosts aggregate:

   $ openstack aggregate add host baremetal-hosts HOSTNAME

   Note

   If you have created a composable role with the NovaIronic service, add all the nodes with this service to the baremetal-hosts aggregate. By default, only the controller nodes have the NovaIronic service.

5. Create a host aggregate called virtual-hosts:

   $ openstack aggregate create --property baremetal=false virtual-hosts

6. Add each compute node to the virtual-hosts aggregate:

   $ openstack aggregate add host virtual-hosts HOSTNAME

7. If you did not add the following Compute filter scheduler when deploying the overcloud, add it now to the existing list under scheduler_default_filters in /etc/nova/nova.conf:

   AggregateInstanceExtraSpecsFilter

Deploying an Instance on the Command Line

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

   $ source ~/overcloudrc

2. Deploy the instance:

   $ openstack server create \
     --nic net-id=NETWORK_UUID \
     --flavor baremetal \
     --image IMAGE_UUID \
     INSTANCE_NAME

   Replace the following values:

   • Replace NETWORK_UUID with the unique identifier for the network that was created for use with the Bare Metal service.
   • 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.

3. Check the status of the instance:

   $ openstack server list --name INSTANCE_NAME

Deploying an Instance in the Dashboard

1. Log in to the dashboard at http[s]://DASHBOARD_IP/dashboard.
2. Click Project > Compute > Instances

3. Click Launch Instance.

   • In the Details tab, specify the Instance Name and select 1 for Count.
   • In the Source tab, select an Image from Select Boot Source, then click the + (plus) symbol to select an operating system disk image. The chosen image will move to Allocated.
   • In the Flavor tab, select baremetal.
   • In the Networks tab, use the + (plus) and - (minus) buttons to move required networks from Available to Allocated. Ensure that the shared network created for the Bare Metal service is selected here.
4. Click Launch Instance.

1. Update the value in the ironic.conf file
2. Restart the Bare Metal service
3. Re-deploy the bare metal instance

1. Check the hypervisor resources that are available:

   $ openstack hypervisor stats show

   The resources reported here should match the resources that the Bare Metal nodes provide.

2. Check that Compute recognizes the Bare Metal nodes as hypervisors:

   $ openstack hypervisor list

   The nodes, identified by UUID, should appear in the list.

3. Check the details for a Bare Metal node:

   $ openstack baremetal node list
   $ openstack baremetal node show NODE_UUID

   Verify that the node’s details match those reported by Compute.

4. Check that the selected flavor does not exceed the available resources of the Bare Metal nodes:

   $ openstack flavor show FLAVOR_NAME

5. Check the output of openstack baremetal node list to ensure that Bare Metal nodes are not in maintenance mode. Remove maintenance mode if necessary:

   $ openstack baremetal node maintenance unset NODE_UUID

6. Check the output of openstack baremetal node list to ensure that Bare Metal nodes are in an available state. Move the node to available if necessary:

   $ openstack baremetal node provide NODE_UUID