Planning and prerequisites for your Bare Metal Hosted Control Plane

Choose your configuration

Networking prerequisites

Red Hat Advanced Cluster Management for Kubernetes (ACM)

Step 1: Configure Host Inventory Settings

After the initial setup, configure the host inventory settings. For more information about the host inventory settings, see Red Hat documentation.

Step 2: Create your infrastructure environment

The next step is to create an infrastructure environment in Red Hat Advanced Cluster Management for Kubernetes (ACM) or using the Hosted Control Plane CLI. This infrastructure environment contains the list of Bare Metal hosts that you can select to create a Bare Metal Hosted Control Plane.

Important: Create one infrastructure environment per hosted control plane cluster. Each Hosted Control Plane can only add hosts from a single infrastructure.

1. In the ACM user interface, go to Infrastructure > Host Inventory.
2. Select Create infrastructure environment.
3. On the Create infrastructure environment page, enter the following details:

   Name

   Name of the infrastructure. No specific name is required.

   Network type

   Select Static IP, Bridges, and Bonds.

   Location

   Label on all hosts

   Labels

   Optional value.

   Pull Secret

   The pull secret must include the following:

   • cloud.openshift.com
   • cp.icr.io
   • quay.io
   • registry.connect.redhat.com
   • registry.redhat.io

   SSH public key

   It is the key used by the IBM Fusion HCI System.

Step 3: Import the hosts by using ACM

With the infrastructure environment created, the next steps are to boot individual servers with an ISO to import them into the host inventory.

Step 3.1: Create the NMStateConfig for each host

The NMStateConfig allows the server to be recognized by the IBM Fusion HCI System cluster. For additional information, see Red Hat documentation.

Note: What goes into NMStateConfig for internal is available through the CRs. For external, consult your network administrator.

Example:

apiVersion: agent-install.openshift.io/v1beta1
kind: NMStateConfig
metadata:
  name: fusion-bm-ru9
  namespace: fusion-bm
  labels:
    infraenvs.agent-install.openshift.io: fusion-bm
spec:
  interfaces:
    - name: ens3f0np0
      macAddress: 08:c0:eb:d4:14:fa
      state: up
      type: ethernet
      ipv4:
        enabled: false
      ipv6:
        enabled: false
    - name: ens3f1np1
      macAddress: 08:c0:eb:d4:14:fb
      state: up
      type: ethernet
      ipv4:
        enabled: false
      ipv6:
        enabled: false
  config:
    interfaces:
      - name: bond0
        type: bond
        mtu: 9000
        state: up
        mac-address: 08:c0:eb:d4:14:fa
        ipv4:
          address:
            - ip: 17.0.1.42
              prefix-length: 24
          enabled: true
        ipv6:
          enabled: false
        link-aggregation:
          mode: 802.3ad
          options:
            lacp_rate: "1"
            miimon: "140"
            xmit_hash_policy: "1"
          ports:
            - ens3f0np0
            - ens3f1np1
    dns-resolver:
      config:
        server:
        - 17.0.1.250
    routes:
      config:
      - destination: 0.0.0.0/0
        next-hop-address: 17.0.1.1
        next-hop-interface: bond0

The NMStateConfig is dependent on the network environment and must be created in consultation with your network administrators.

Fill the fields in the NMStateConfig.yaml based on the following guidance. These fields within the NMStateConfig are unique per host:

name

Unique name for each node

namespace

Namespace is the infraenv namespace.

labels

infraenvs.agent-install.openshift.io: infraNamespace. The infraNamespace must match the name of the infraenvironment into which the host is imported.

ports

The correct ports can be found in the ComputeConfiguration CR. The ComputeConfiguration for the particular node to be imported to ACM. Within the ComputeConfiguration, there is a section “NetworkInterfaces”. Within this section, the interfaceName with “bond0” has the name of the two interfaces interfaceLeg1 and interfaceLeg2. The values under interfaceLeg1 and interfaceLeg2 are the ports.

This guidance is for internal. Consult your network administrator for external.

ipaddress

It is the ipv4 address for that node or server.

interfaces > port: macaddress: and port: macaddress:

You can find these values in the ComputeConfiguration CR. Each port is an entry from the ports. The macaddress is for that port. The macaddress can be ComputeConfiguration for the node by looking for the bond0 port: macaddress. Map that macaddress to the networkCards: -slot-#: There will be one matching macaddress and one new one, use those in the NMStateConfig.yaml. Important: change any letters to lower case.

Example:

ens1f0np1: macaddress: macaddress can be found in the ComputeConfiguration for the node under networkCards: slot-1: macaddress:

This guidance is for internal. Consult your network administrator for external.

NMstate information is from the switch and for unmanaged servers, you need to provide the values:

After the NMStateConfig.yaml is created for a server. It must be added to IBM Fusion HCI System cluster with the following commands:

1. Go to the infraenvnamespace namespace.

   oc project infraenvnamespace

2. Apply the YAML.

   oc apply -f nmstate.yaml

Step 3.2: Download the discovery.iso

Use the wget command to download the discovery.iso to the service node or another jumpbox.

Note: Keep this ISO secure as you can use this to add a server to the cluster with sensitive information.

To get the retrieval command do the following:

1. Log into the hub IBM Fusion HCI System cluster.
2. In the ACM section, go to Infrastructure > Host inventory.
3. In the infrastructure environment, select the infrastructure you intend to import the host into and select that infrastructure environment.
4. Select Add Hosts > With Discovery ISO. There exists either a URL or a wget command. Use the command or URL to transfer the ISO to your jumpbox.

Step 3.4: Boot the host with the discovery.iso

This task requires you to log into the IMM, mount the ISO image, and reboot the server.

Note: For internal, go through the steps in this section. For external, go through the Red Hat documentation.

Mount the ISO on to the server through the IMM:

1. Get the IPv6 from ComputeConfiguration for that server.
2. Log in to the IMM.
3. Use the USER/Password from secretName secret in the ComputeConfiguration. The defaultUserName and defaultUserPasswrd fields.
4. Select Remote Console tab.
5. In the Remote Console tab, select Launch remote console and Media.
6. In the Media page, go to the Mount media from Client Browser section.
7. Select the discovery.iso image and mount it.
8. Select one virtual media to boot on the next restart.
9. Select the mounted discovery.iso and restart immediately.
10. Close windows and monitor that the remote console is showing the reboot.

Step 4: Accept the host into the ACM Inventory

After the server gets restarted with discovery.iso, accept the host into the host inventory.

1. In the ACM user interface, go to Infrastructure > Host inventory.
2. From the table, select the infrastructure environment where the host got imported.
   Note: In the hosts table, you can see the approve host after the server gets booted up completely. It can take 10-15 minutes. Verify the server before you accept. If the server name is not recognizable, then look at the details to confirm. You can change the host name but ensure it is unique.
3. Accept the host into the inventory.

Step 5: Labeling hosts

After you accept the hosts, add labels to them through the Agent CR. It can be useful to identify a specific cluster or nodepool.

To add the label, do the following steps:

1. Log into the OpenShift console.
2. Go to Administration > CustomResourceDefinitions.
3. Search for Agent of type agent-install-openshift.io.
4. In the instances, find the agent to modify the label.
5. Edit the label of the agent to add a new label.

When you create the cluster, use these labels to filter or assign nodes to different node pools within the cluster.