Bare Metal Provisioning

Procedure

1. Log in to the undercloud as the stack user.

2. Source the stackrc file:

   [stack@director ~]$ source ~/stackrc

3. Modify the /home/stack/templates/nic-configs/controller.yaml file to reuse the provisioning network interface on the Controller nodes, eth1, to create a bridge for the bare metal network:

   network_config:
   - type: ovs_bridge
     name: br-baremetal
     use_dhcp: false
     members:
       - type: interface
         name: eth1
     addresses:
       - ip_netmask:
           list_join:
           - /
           - - get_param: ControlPlaneIp
             - get_param: ControlPlaneSubnetCidr

   Note

   You cannot VLAN tag the bare metal network when you create it by reusing the provisioning network.

4. Add br-baremetal to the NeutronBridgeMappings parameter in your network-environment.yaml file:

   parameter_defaults:
     NeutronBridgeMappings: datacentre:br-ex,baremetal:br-baremetal

5. Add baremetal to the list of networks specified by the NeutronFlatNetworks parameter in your network-environment.yaml file:

   parameter_defaults:
     NeutronBridgeMappings: datacentre:br-ex,baremetal:br-baremetal
     NeutronFlatNetworks: datacentre,baremetal

Procedure

1. Log in to the undercloud host as the stack user.

2. Source the stackrc undercloud credentials file:

   $ source ~/stackrc

3. Copy the network_data.yaml file to your environment file directory:

   (undercloud) [stack@host01 ~]$ cp /usr/share/openstack-tripleo-heat-templates/network_data.yaml /home/stack/templates/network_data.yaml

4. Add a new network for overcloud provisioning to your network_data.yaml file:

   # custom network for overcloud provisioning
   - name: OcProvisioning
     name_lower: oc_provisioning
     vip: true
     vlan: 205
     ip_subnet: '<ipv4_subnet_address>/<ipv4_mask>'
     allocation_pools: [{'start': '<ipv4_start_address>', 'end': '<ipv4_end_address>'}]

   • Replace <ipv4_subnet_address> with the IPv4 address of your IPv4 subnet.
   • Replace <ipv4_mask> with the IPv4 network mask for your IPv4 subnet.
   • Replace <ipv4_start_address> and <ipv4_end_address> with the IPv4 range that you want to use for address allocation.

5. Configure IronicApiNetwork and IronicNetwork in your ServiceNetMap configuration to use the new IPv4 provisioning network:

   ServiceNetMap:
     IronicApiNetwork: oc_provisioning
     IronicNetwork: oc_provisioning

6. Add the new network as an interface to your local Controller NIC configuration file:

   network_config:
   - type: vlan
     vlan_id:
       get_param: OcProvisioningNetworkVlanID
     addresses:
     - ip_netmask:
         get_param: OcProvisioningIpSubnet

7. Copy the roles_data.yaml file to your environment file directory:

   (undercloud) [stack@host01 ~]$ cp /usr/share/openstack-tripleo-heat-templates/roles_data.yaml /home/stack/templates/roles_data.yaml

8. Add the new network for the controller to your roles_data.yaml file:

   networks:
     ...
     OcProvisioning:
       subnet: oc_provisioning_subnet

9. Include the IronicInspector service in the Ironic role in your roles_data.yaml file, if not already present:

   ServicesDefault:
     OS::TripleO::Services::IronicInspector

Procedure

1. Log in to the undercloud as the stack user.

2. Source the stackrc file:

   [stack@director ~]$ source ~/stackrc

3. Copy the network_data.yaml file to your environment file directory:

   (undercloud) [stack@host01 ~]$ cp /usr/share/openstack-tripleo-heat-templates/network_data.yaml /home/stack/templates/network_data.yaml

4. Add a new IPv6 network for overcloud provisioning to your network_data.yaml file:

   # custom network for IPv6 overcloud provisioning
   - name: OcProvisioningIPv6
     vip: true
     name_lower: oc_provisioning_ipv6
     vlan: 10
     ipv6: true
     ipv6_subnet: '<ipv6_subnet_address>/<ipv6_prefix>'
     ipv6_allocation_pools: [{'start': '<ipv6_start_address>', 'end': '<ipv6_end_address>'}]
     gateway_ipv6: '<ipv6_gw_address>'

   • Replace <ipv6_subnet_address> with the IPv6 address of your IPv6 subnet.
   • Replace <ipv6_prefix> with the IPv6 network prefix for your IPv6 subnet.
   • Replace <ipv6_start_address> and <ipv6_end_address> with the IPv6 range that you want to use for address allocation.
   • Replace <ipv6_gw_address> with the IPv6 address of your gateway.

5. Create a new file network_environment_overrides.yaml in your environment file directory:

   $ touch /home/stack/templates/network_environment_overrides.yaml

6. Configure IronicApiNetwork and IronicNetwork in your network_environment_overrides.yaml file to use the new IPv6 provisioning network:

   ServiceNetMap:
     IronicApiNetwork: oc_provisioning_ipv6
     IronicNetwork: oc_provisioning_ipv6

7. Set the IronicIpVersion parameter to 6:

   parameter_defaults:
     IronicIpVersion: 6

8. Enable the RabbitIPv6, MysqlIPv6, and RedisIPv6 parameters:

   parameter_defaults:
     RabbitIPv6: True
     MysqlIPv6: True
     RedisIPv6: True

9. Add the new network as an interface to your local Controller NIC configuration file:

   network_config:
   - type: vlan
     vlan_id:
       get_param: OcProvisioningIPv6NetworkVlanID
     addresses:
     - ip_netmask:
         get_param: OcProvisioningIPv6IpSubnet

10. Copy the roles_data.yaml file to your environment file directory:

    (undercloud) [stack@host01 ~]$ cp /usr/share/openstack-tripleo-heat-templates/roles_data.yaml /home/stack/templates/roles_data.yaml

11. Add the new network for the Controller role to your roles_data.yaml file:

    networks:
      ...
      - OcProvisioningIPv6

12. Include the IronicInspector service in the Ironic role in your roles_data.yaml file, if not already present:

    ServicesDefault:
      OS::TripleO::Services::IronicInspector

Procedure

1. Create an environment file in your local directory to configure the Bare Metal Provisioning service for your deployment, for example, ironic-overrides.yaml.

2. Optional: Configure the type of cleaning that is performed on the bare metal machines before and between provisioning:

   parameter_defaults:
     IronicCleaningDiskErase: <cleaning_type>

   Replace <cleaning_type> with one of the following values:

   • full: (Default) Performs a full clean.
   • metadata: Clean only the partition table. This type of cleaning substantially speeds up the cleaning process. However, because the deployment is less secure in a multi-tenant environment, use this option only in a trusted tenant environment.

3. Optional: Add additional drivers to the default drivers:

   parameter_defaults:
     IronicEnabledHardwareTypes: ipmi,idrac,ilo,[additional_driver_1],...,[additional_driver_n]

   Replace [additional_driver_1], and optionally all drivers up to [additional_driver_n], with the additional drivers you want to enable.

4. To enable bare metal introspection, add the following configuration to your local Bare Metal Provisioning service environment file, ironic-overrides.yaml:

   parameter_defaults:
     IronicInspectorSubnets:
       - ip_range: <ip_range>
     IPAImageURLs: '["http://<ip_address>:<port>/agent.kernel", "http://<ip_address>:<port>/agent.ramdisk"]'
     IronicInspectorInterface: '<baremetal_interface>'

   • Replace <ip_range> with the IP ranges for your environments, for example, 192.168.0.100,192.168.0.120.
   • Replace <ip_address>:<port> with the IP address and port of the web server that hosts the IPA kernel and ramdisk. To use the same images that you use on the undercloud, set the IP address to the undercloud IP address, and the port to 8088. If you omit this parameter, you must include alternatives on each Controller node.
   • Replace <baremetal_interface> with the bare metal network interface, for example, br-baremetal.

5. Add your new role and custom environment files to the stack with your other environment files and deploy the overcloud:

   (undercloud)$ openstack overcloud deploy --templates \
     -e [your environment files] \
     -e /home/stack/templates/node-info.yaml
     -r /home/stack/templates/roles_data.yaml \
     -e /usr/share/openstack-tripleo-heat-templates/network-environment.yaml \
     -e /usr/share/openstack-tripleo-heat-templates/environments/services/<default_ironic_template> \
     -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-inspector.yaml \
     -e /home/stack/templates/network_environment_overrides.yaml
     -n /home/stack/templates/network_data.yaml
     -e /home/stack/templates/ironic-overrides.yaml \

   • Replace <default_ironic_template> with either ironic.yaml or ironic-overcloud.yaml, depending on the Networking service mechanism driver for your deployment.
   Note

   The order that you pass your environment files to the openstack overcloud deploy command is important, as the configuration in the later files takes precedence. Therefore, your environment file that enables and configures bare metal provisioning on your overcloud must be passed to the command after any network configuration files.

Additional verification methods for the Bare Metal Provisioning service:

1. Configure 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 changed the default ironic drivers, ensure that the required drivers are enabled:

   $ openstack baremetal driver list

4. Ensure that the ironic endpoints are listed:

   $ openstack catalog list

Procedure

1. Source the overcloud credentials file:

   $ source ~/overcloudrc

2. Create a new instance flavor for bare metal nodes:

   (overcloud)$ openstack flavor create --id auto \
    --ram <ram_size_mb> --disk <disk_size_gb> \
    --vcpus <no_vcpus> baremetal

   • Replace <ram_size_mb> with the RAM of the bare metal node, in MB.
   • Replace <disk_size_gb> with the size of the disk on the bare metal node, in GB.

   • Replace <no_vcpus> with the number of CPUs on the bare metal node.

     Note

     These properties are not used for scheduling instances. However, the Compute scheduler does use the disk size to determine the root partition size.

3. Retrieve a list of your nodes to identify their UUIDs:

   (overcloud)$ openstack baremetal node list

4. Tag each bare metal node with a custom bare metal resource class:

   (overcloud)$ openstack baremetal node set \
    --resource-class baremetal.<CUSTOM> <node>

   • Replace <CUSTOM> with a string that identifies the purpose of the resource class. For example, set to GPU to create a custom GPU resource class that you can use to tag bare metal nodes that you want to designate for GPU workloads.
   • Replace <node> with the ID of the bare metal node.

5. Associate the new instance flavor for bare metal nodes with the custom resource class:

   (overcloud)$ openstack flavor set \
    --property resources:CUSTOM_BAREMETAL_<CUSTOM>=1 \
    baremetal

   To determine the name of a custom resource class that corresponds to a resource class of a Bare Metal service node, convert the resource class to uppercase, replace each punctuation mark with an underscore, and prefix with CUSTOM_.

   Note

   A flavor can request only one instance of a bare metal resource class.

6. Set the following flavor properties to prevent the Compute scheduler from using the bare metal flavor properties to schedule instances:

   (overcloud)$ openstack flavor set \
    --property resources:VCPU=0 \
    --property resources:MEMORY_MB=0 \
    --property resources:DISK_GB=0 baremetal

7. Verify that the new flavor has the correct values:

   (overcloud)$ openstack flavor list

Procedure

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 that virtual instances use:

   $ 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 you deployed the overcloud, add it now to the existing list under scheduler_default_filters in the _/etc/nova/nova.conf_ file:

   AggregateInstanceExtraSpecsFilter

Procedure

1. Run the following command to display the IP address for each host:

   (undercloud) [stack@host01 ~]$ openstack stack output show overcloud HostsEntry --max-width 80
   
   +--------------+---------------------------------------------------------------+
   | Field        | Value                                                         |
   +--------------+---------------------------------------------------------------+
   | description  | The content that should be appended to your /etc/hosts if you |
   |              | want to get                                                   |
   |              | hostname-based access to the deployed nodes (useful for       |
   |              | testing without                                               |
   |              | setting up a DNS).                                            |
   |              |                                                               |
   | output_key   | HostsEntry                                                    |
   | output_value | 172.17.0.10 overcloud-controller-0.localdomain overcloud-     |
   |              | controller-0                                                  |
   |              | 10.8.145.18 overcloud-controller-0.external.localdomain       |
   |              | overcloud-controller-0.external                               |
   |              | 172.17.0.10 overcloud-controller-0.internalapi.localdomain    |
   |              | overcloud-controller-0.internalapi                            |
   |              | 172.18.0.15 overcloud-controller-0.storage.localdomain        |
   |              | overcloud-controller-0.storage                                |
   |              | 172.21.2.12 overcloud-controller-0.storagemgmt.localdomain    |
   |              | overcloud-controller-0.storagemgmt                            |
   |              | 172.16.0.15 overcloud-controller-0.tenant.localdomain         |
   |              | overcloud-controller-0.tenant                                 |
   |              | 10.8.146.13 overcloud-controller-0.management.localdomain     |
   |              | overcloud-controller-0.management                             |
   |              | 10.8.146.13 overcloud-controller-0.ctlplane.localdomain       |
   |              | overcloud-controller-0.ctlplane                               |
   |              |                                                               |
   |              | 172.17.0.21 overcloud-compute-0.localdomain overcloud-        |
   |              | compute-0                                                     |
   |              | 10.8.146.12 overcloud-compute-0.external.localdomain          |
   |              | overcloud-compute-0.external                                  |
   |              | 172.17.0.21 overcloud-compute-0.internalapi.localdomain       |
   |              | overcloud-compute-0.internalapi                               |
   |              | 172.18.0.20 overcloud-compute-0.storage.localdomain           |
   |              | overcloud-compute-0.storage                                   |
   |              | 10.8.146.12 overcloud-compute-0.storagemgmt.localdomain       |
   |              | overcloud-compute-0.storagemgmt                               |
   |              | 172.16.0.16 overcloud-compute-0.tenant.localdomain overcloud- |
   |              | compute-0.tenant                                              |
   |              | 10.8.146.12 overcloud-compute-0.management.localdomain        |
   |              | overcloud-compute-0.management                                |
   |              | 10.8.146.12 overcloud-compute-0.ctlplane.localdomain          |
   |              | overcloud-compute-0.ctlplane                                  |
   |              |                                                               |
   |              |                                                               |
   |              |                                                               |
   |              |                                                               |
   |              | 10.8.145.16  overcloud.localdomain                            |
   |              | 10.8.146.7  overcloud.ctlplane.localdomain                    |
   |              | 172.17.0.19  overcloud.internalapi.localdomain                |
   |              | 172.18.0.19  overcloud.storage.localdomain                    |
   |              | 172.21.2.16  overcloud.storagemgmt.localdomain                |
   +--------------+---------------------------------------------------------------+

2. To filter a particular host, run the following command:

   (undercloud) [stack@host01 ~]$ openstack stack output show overcloud HostsEntry -c output_value -f value | grep overcloud-controller-0
   
   172.17.0.12 overcloud-controller-0.localdomain overcloud-controller-0
   10.8.145.18 overcloud-controller-0.external.localdomain overcloud-controller-0.external
   172.17.0.12 overcloud-controller-0.internalapi.localdomain overcloud-controller-0.internalapi
   172.18.0.12 overcloud-controller-0.storage.localdomain overcloud-controller-0.storage
   172.21.2.13 overcloud-controller-0.storagemgmt.localdomain overcloud-controller-0.storagemgmt
   172.16.0.19 overcloud-controller-0.tenant.localdomain overcloud-controller-0.tenant
   10.8.146.13 overcloud-controller-0.management.localdomain overcloud-controller-0.management
   10.8.146.13 overcloud-controller-0.ctlplane.localdomain overcloud-controller-0.ctlplane

3. To map the hosts to bare metal nodes, run the following command:

   (undercloud) [stack@host01 ~]$ openstack baremetal node list --fields uuid name instance_info -f json
   [
     {
       "UUID": "c0d2568e-1825-4d34-96ec-f08bbf0ba7ae",
       "Instance Info": {
         "root_gb": "40",
         "display_name": "overcloud-compute-0",
         "image_source": "24a33990-e65a-4235-9620-9243bcff67a2",
         "capabilities": "{\"boot_option\": \"local\"}",
         "memory_mb": "4096",
         "vcpus": "1",
         "local_gb": "557",
         "configdrive": "******",
         "swap_mb": "0",
         "nova_host_id": "host01.lab.local"
       },
       "Name": "host2"
     },
     {
       "UUID": "8c3faec8-bc05-401c-8956-99c40cdea97d",
       "Instance Info": {
         "root_gb": "40",
         "display_name": "overcloud-controller-0",
         "image_source": "24a33990-e65a-4235-9620-9243bcff67a2",
         "capabilities": "{\"boot_option\": \"local\"}",
         "memory_mb": "4096",
         "vcpus": "1",
         "local_gb": "557",
         "configdrive": "******",
         "swap_mb": "0",
         "nova_host_id": "host01.lab.local"
       },
       "Name": "host3"
     }
   ]

Procedure

1. List the VIF IDs currently connected to the bare metal node:

   $ openstack baremetal node vif list baremetal-0
   +--------------------------------------+
   | ID                                   |
   +--------------------------------------+
   | 4475bc5a-6f6e-466d-bcb6-6c2dce0fba16 |
   +--------------------------------------+

2. After the VIF is attached, the Bare Metal Provisioning service updates the virtual port in the OpenStack Networking service with the actual MAC address of the physical port. Check this port address:

   $ openstack port show 4475bc5a-6f6e-466d-bcb6-6c2dce0fba16 -c mac_address -c fixed_ips
   +-------------+-----------------------------------------------------------------------------+
   | Field       | Value                                                                       |
   +-------------+-----------------------------------------------------------------------------+
   | fixed_ips   | ip_address='192.168.24.9', subnet_id='1d11c677-5946-4733-87c3-23a9e06077aa' |
   | mac_address | 00:2d:28:2f:8d:95                                                           |
   +-------------+-----------------------------------------------------------------------------+

3. Create a new port on the network where you created the baremetal-0 node:

   $ openstack port create --network baremetal --fixed-ip ip-address=192.168.24.24 baremetal-0-extra

4. Remove a port from the instance:

   $ openstack server remove port overcloud-baremetal-0 4475bc5a-6f6e-466d-bcb6-6c2dce0fba16

5. Check that the IP address no longer exists on the list:

   $ openstack server list

6. Check if there are VIFs attached to the node:

   $ openstack baremetal node vif list baremetal-0
   $ openstack port list

7. Add the newly created port:

   $ openstack server add port overcloud-baremetal-0 baremetal-0-extra

8. Verify that the new IP address shows the new port:

   $ openstack server list
   +--------------------------------------+-------------------------+--------+------------------------+------------------------------+---------+
   | ID                                   | Name                    | Status | Networks               | Image                        | Flavor  |
   +--------------------------------------+-------------------------+--------+------------------------+------------------------------+---------+
   | 53095a64-1646-4dd1-bbf3-b51cbcc38789 | overcloud-controller-2  | ACTIVE | ctlplane=192.168.24.7  | overcloud-hardened-uefi-full | control |
   | 3a1bc89c-5d0d-44c7-a569-f2a3b4c73d65 | overcloud-controller-0  | ACTIVE | ctlplane=192.168.24.8  | overcloud-hardened-uefi-full | control |
   | 6b01531a-f55d-40e9-b3a2-6d02be0b915b | overcloud-controller-1  | ACTIVE | ctlplane=192.168.24.16 | overcloud-hardened-uefi-full | control |
   | c61cc52b-cc48-4903-a971-073c60f53091 | overcloud-novacompute-0overcloud-baremetal-0 | ACTIVE | ctlplane=192.168.24.24 | overcloud-hardened-uefi-full | compute |
   +--------------------------------------+-------------------------+--------+------------------------+------------------------------+---------+

9. Check if the VIF ID is the UUID of the new port:

   $ openstack baremetal node vif list baremetal-0
   +--------------------------------------+
   | ID                                   |
   +--------------------------------------+
   | 6181c089-7e33-4f1c-b8fe-2523ff431ffc |
   +--------------------------------------+

10. Check if the OpenStack Networking port MAC address is updated and matches one of the Bare Metal Provisioning service ports:

    $ openstack port show 6181c089-7e33-4f1c-b8fe-2523ff431ffc -c mac_address -c fixed_ips
    +-------------+------------------------------------------------------------------------------+
    | Field       | Value                                                                        |
    +-------------+------------------------------------------------------------------------------+
    | fixed_ips   | ip_address='192.168.24.24', subnet_id='1d11c677-5946-4733-87c3-23a9e06077aa' |
    | mac_address | 00:2d:28:2f:8d:95                                                            |
    +-------------+------------------------------------------------------------------------------+

11. Reboot the bare metal node so that it recognizes the new IP address:

    $ openstack server reboot overcloud-baremetal-0

    After you detach or attach interfaces, the bare metal OS removes, adds, or modifies the network interfaces that have changed. When you replace a port, a DHCP request obtains the new IP address, but this might take some time because the old DHCP lease is still valid. To initiate these changes immediately, reboot the bare metal host.

Procedure

1. Log in to the undercloud host as the stack user.

2. Source the overcloudrc credentials file:

   $ source ~/overcloudrc

3. Run the introspection command:

   $ openstack baremetal introspection start [--wait] <NODENAME>

   Replace <NODENAME> with the name or UUID of the node that you want to inspect.

4. Check the introspection status:

   $ openstack baremetal introspection status <NODENAME>

   Replace <NODENAME> with the name or UUID of the node.

Procedure

1. Source the overcloud credentials file:

   $ source ~/<credentials_file>

   • Replace <credentials_file> with the name of your credentials file, for example, overcloudrc.

2. Set the iscsi_boot capability to true and the storage-interface to cinder for the selected node:

   $ openstack baremetal node set --property capabilities=iscsi_boot:true --storage-interface cinder <NODEID>

   Replace <NODEID> with the ID of the chosen node.

3. Create an iSCSI connector for the node:

   $ openstack baremetal volume connector create --node <NODEID> --type iqn --connector-id iqn.2010-10.org.openstack.node<NUM>

   The connector ID for each node must be unique. In this example, the connector is iqn.2010-10.org.openstack.node<NUM> where <NUM> is an incremented number for each node.

Prerequisites

1. Download a Red Hat Enterprise Linux QCOW2 image and copy it to the /home/stack/ directory on the undercloud. You can download Red Hat Enterprise Linux KVM images in QCOW2 format from the following pages:

   • Red Hat Enterprise Linux 7
   • Red Hat Enterprise Linux 8

Procedure

1. Log in to the undercloud as the stack user.

2. Mount the QCOW2 image and access it as the root user:

   1. Load the nbd kernel module:

      $ sudo modprobe nbd

   2. Connect the QCOW image as /dev/nbd0:

      $ sudo qemu-nbd --connect=/dev/nbd0 <IMAGE>

   3. Check the partitions on the NBD:

      $ sudo fdisk /dev/nbd0 -l

      New Red Hat Enterprise Linux QCOW2 images contain only one partition, which is usually named /dev/nbd0p1 on the NBD.

   4. Create a mount point for the image:

      mkdir /tmp/mountpoint

   5. Mount the image:

      sudo mount /dev/nbd0p1 /tmp/mountpoint/

   6. Mount your dev directory so that the image has access to device information on the host:

      sudo mount -o bind /dev /tmp/mountpoint/dev

   7. Change the root directory to the mount point:

      sudo chroot /tmp/mountpoint /bin/bash

3. Configure iSCSI on the image:

   Note

   Some commands in this step might report the following error:

   lscpu: cannot open /proc/cpuinfo: No such file or directory

   This error is not critical and you can ignore the error.

   1. Move the resolv.conf file to a temporary location:

      # mv /etc/resolv.conf /etc/resolv.conf.bak

   2. Create a temporary resolv.conf file to resolve DNS requests for the Red Hat Content Delivery Network. This example uses 8.8.8.8 for the nameserver:

      # echo "nameserver 8.8.8.8" > /etc/resolv.conf

   3. Register the mounted image to the Red Hat Content Delivery Network:

      # subscription-manager register

      Enter your user name and password when the command prompts you.

   4. Attach a subscription that contains Red Hat Enterprise Linux:

      # subscription-manager list --all --available
      # subscription-manager attach --pool <POOLID>

      Substitute <POOLID> with the pool ID of the subscription.

   5. Disable the default repositories:

      # subscription-manager repos --disable "*"

   6. Enable the Red Hat Enterprise Linux repository:

      • Red Hat Enterprise Linux 7:

        # subscription-manager repos --enable "rhel-7-server-rpms"

      • Red Hat Enterprise Linux 8:

        # subscription-manager repos --enable "rhel-8-for-x86_64-baseos-eus-rpms"

   7. Install the iscsi-initiator-utils package:

      # yum install -y iscsi-initiator-utils

   8. Unregister the mounted image:

      # subscription-manager unregister

   9. Restore the original resolv.conf file:

      # mv /etc/resolv.conf.bak /etc/resolv.conf

   10. Check the kernel version on the mounted image:

       # rpm -qa kernel

       For example, if the output is kernel-3.10.0-1062.el7.x86_64, the kernel version is 3.10.0-1062.el7.x86_64. Note this kernel version for the next step.

       Note

       New Red Hat Enterprise Linux QCOW2 images have only one kernel version installed. If more than one kernel version is installed, use the latest one.

   11. Add the network and iscsi dracut modules to the initramfs image:

       # dracut --force --add "network iscsi" /boot/initramfs-<KERNELVERSION>.img <KERNELVERSION>

       Replace <KERNELVERSION> with the version number that you obtained from rpm -qa kernel. The following example uses 3.10.0-1062.el7.x86_64 as the kernel version:

       # dracut --force --add "network iscsi" /boot/initramfs-3.10.0-1062.el7.x86_64.img 3.10.0-1062.el7.x86_64

   12. Exit from the mounted image back to your host operating system:

       # exit

4. Unmount the image:

   1. Unmount the dev directory from the temporary mount point:

      $ sudo umount /tmp/mountpoint/dev

   2. Unmount the image from the mount point:

      $ sudo umount /tmp/mountpoint

   3. Disconnect the QCOW2 image from /dev/nbd0/:

      $ sudo qemu-nbd --disconnect /dev/nbd0

5. Rebuild the grub menu configuration on the image:

   1. Install the libguestfs-tools package:

      $ sudo yum -y install libguestfs-tools

      Important

      If you install the libguestfs-tools package on the undercloud, disable iscsid.socket to avoid port conflicts with the tripleo_iscsid service on the undercloud:

      $ sudo systemctl disable --now iscsid.socket

   2. Set the libguestfs backend to use QEMU directly:

      $ export LIBGUESTFS_BACKEND=direct

   3. Update the grub configuration on the image:

      $ guestfish -a /tmp/images/{{ dib_image }} -m /dev/sda3 sh "mount /dev/sda2 /boot/efi && rm /boot/grub2/grubenv && /sbin/grub2-mkconfig -o /boot/grub2/grub.cfg && cp /boot/grub2/grub.cfg /boot/efi/EFI/redhat/grub.cfg && grubby --update-kernel=ALL --args=\"rd.iscsi.firmware=1\" && cp /boot/grub2/grubenv /boot/efi/EFI/redhat/grubenv && echo Success"

Procedure

1. Log in to the undercloud as the stack user.

2. Upload the iSCSI-enabled image to glance:

   $ openstack image create --disk-format qcow2 --container-format bare --file rhel-server-7.7-x86_64-kvm.qcow2 rhel-server-7.7-iscsi

3. Create a volume from the image:

   $ openstack volume create --size 10 --image rhel-server-7.7-iscsi --bootable rhel-test-volume

4. Create a bare metal instance that uses the boot volume in cinder:

   $ openstack server create --flavor baremetal --volume rhel-test-volume --key default rhel-test

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

Modifying KernelArgs with heat during deployment

1. Log in to the undercloud host as the stack user.

2. Source the stackrc credentials file:

   $ source stackrc

3. Create an environment file overcloud-console.yaml with the following content:

   parameter_defaults:
     <role>Parameters:
       KernelArgs: "console=<console-name>"

   Replace <role> with the name of the overcloud role that you want to configure, and replace <console-name> with the ID of the console that you want to use. For example, use the following snippet to configure all overcloud nodes in the default roles to use tty0:

   parameter_defaults:
     ControllerParameters:
       KernelArgs: "console=tty0"
     ComputeParameters:
       KernelArgs: "console=tty0"
     BlockStorageParameters:
       KernelArgs: "console=tty0"
     ObjectStorageParameters:
       KernelArgs: "console=tty0"
     CephStorageParameters:
       KernelArgs: "console=tty0"

4. Include the overcloud-console-tty0.yaml file in your deployment command with the -e option.

Modifying the overcloud-hardened-uefi-full.qcow2 image

1. Log in to the undercloud host as the stack user.

2. Source the stackrc credentials file:

   $ source stackrc

3. Modify the kernel arguments in the overcloud-hardened-uefi-full.qcow2 image to set the correct console for your hardware. For example, set the console to tty1:

   $ virt-customize --selinux-relabel -a overcloud-hardened-uefi-full.qcow2 --run-command 'grubby --update-kernel=ALL --args="console=tty1"'

4. Import the image into director:

   $ openstack overcloud image upload --image-path overcloud-hardened-uefi-full.qcow2

5. Deploy the overcloud.

Verification

1. Log in to an overcloud node from the undercloud:

   $ ssh tripleo-admin@<IP-address>

   Replace <IP-address> with the IP address of an overcloud node.

2. Inspect the contents of the /proc/cmdline file and ensure that console= parameter is set to the value of the console that you want to use:

   [tripleo-admin@controller-0 ~]$ cat /proc/cmdline
   BOOT_IMAGE=(hd0,msdos2)/boot/vmlinuz-4.18.0-193.29.1.el8_2.x86_64 root=UUID=0ec3dea5-f293-4729-b676-5d38a611ce81 ro console=tty0 console=ttyS0,115200n81 no_timer_check crashkernel=auto rhgb quiet

1. Enable the sensor method in the ironic.conf file:

   $ openstack-config --set /etc/ironic/ironic.conf \
      irmc sensor_method METHOD

   Replace METHOD with scci or ipmitool.

2. If you enabled SCCI, install the python-scciclient package:

   # dnf install python-scciclient

3. Restart the Bare Metal conductor service:

   # systemctl restart openstack-ironic-conductor.service