Chapter 2. Setting up the environment for an OpenShift Container Platform installation

Procedure

1. Log in to the provisioner node via ssh.

2. Create a non-root user (kni) and provide that user with sudo privileges:

   # useradd kni

   Copy to Clipboard

   # passwd kni

   Copy to Clipboard

   # echo "kni ALL=(root) NOPASSWD:ALL" | tee -a /etc/sudoers.d/kni

   Copy to Clipboard

   # chmod 0440 /etc/sudoers.d/kni

   Copy to Clipboard

3. Create an ssh key for the new user:

   # su - kni -c "ssh-keygen -f /home/kni/.ssh/id_rsa -N ''"

   Copy to Clipboard

4. Log in as the new user on the provisioner node:

   # su - kni

   Copy to Clipboard

5. Use Red Hat Subscription Manager to register the provisioner node:

   $ sudo subscription-manager register --username=<user> --password=<pass> --auto-attach

   Copy to Clipboard

   $ sudo subscription-manager repos --enable=rhel-8-for-x86_64-appstream-rpms \
                                     --enable=rhel-8-for-x86_64-baseos-rpms

   Copy to Clipboard
   Note

   For more information about Red Hat Subscription Manager, see Using and Configuring Red Hat Subscription Manager.

6. Install the following packages:

   $ sudo dnf install -y libvirt qemu-kvm mkisofs python3-devel jq ipmitool

   Copy to Clipboard

7. Modify the user to add the libvirt group to the newly created user:

   $ sudo usermod --append --groups libvirt kni

   Copy to Clipboard

8. Start firewalld:

   $ sudo systemctl start firewalld

   Copy to Clipboard

9. Enable firewalld:

   $ sudo systemctl enable firewalld

   Copy to Clipboard

10. Start the http service:

    $ sudo firewall-cmd --zone=public --add-service=http --permanent

    Copy to Clipboard

    $ sudo firewall-cmd --reload

    Copy to Clipboard

11. Start and enable the libvirtd service:

    $ sudo systemctl enable libvirtd --now

    Copy to Clipboard

12. Set the ID of the provisioner node:

    $ PRVN_HOST_ID=<ID>

    Copy to Clipboard

    You can view the ID with the following ibmcloud command:

    $ ibmcloud sl hardware list

    Copy to Clipboard

13. Set the ID of the public subnet:

    $ PUBLICSUBNETID=<ID>

    Copy to Clipboard

    You can view the ID with the following ibmcloud command:

    $ ibmcloud sl subnet list

    Copy to Clipboard

14. Set the ID of the private subnet:

    $ PRIVSUBNETID=<ID>

    Copy to Clipboard

    You can view the ID with the following ibmcloud command:

    $ ibmcloud sl subnet list

    Copy to Clipboard

15. Set the provisioner node public IP address:

    $ PRVN_PUB_IP=$(ibmcloud sl hardware detail $PRVN_HOST_ID --output JSON | jq .primaryIpAddress -r)

    Copy to Clipboard

16. Set the CIDR for the public network:

    $ PUBLICCIDR=$(ibmcloud sl subnet detail $PUBLICSUBNETID --output JSON | jq .cidr)

    Copy to Clipboard

17. Set the IP address and CIDR for the public network:

    $ PUB_IP_CIDR=$PRVN_PUB_IP/$PUBLICCIDR

    Copy to Clipboard

18. Set the gateway for the public network:

    $ PUB_GATEWAY=$(ibmcloud sl subnet detail $PUBLICSUBNETID --output JSON | jq .gateway -r)

    Copy to Clipboard

19. Set the private IP address of the provisioner node:

    $ PRVN_PRIV_IP=$(ibmcloud sl hardware detail $PRVN_HOST_ID --output JSON | \
                     jq .primaryBackendIpAddress -r)

    Copy to Clipboard

20. Set the CIDR for the private network:

    $ PRIVCIDR=$(ibmcloud sl subnet detail $PRIVSUBNETID --output JSON | jq .cidr)

    Copy to Clipboard

21. Set the IP address and CIDR for the private network:

    $ PRIV_IP_CIDR=$PRVN_PRIV_IP/$PRIVCIDR

    Copy to Clipboard

22. Set the gateway for the private network:

    $ PRIV_GATEWAY=$(ibmcloud sl subnet detail $PRIVSUBNETID --output JSON | jq .gateway -r)

    Copy to Clipboard

23. Set up the bridges for the baremetal and provisioning networks:

    $ sudo nohup bash -c "
        nmcli --get-values UUID con show | xargs -n 1 nmcli con delete
        nmcli connection add ifname provisioning type bridge con-name provisioning
        nmcli con add type bridge-slave ifname eth1 master provisioning
        nmcli connection add ifname baremetal type bridge con-name baremetal
        nmcli con add type bridge-slave ifname eth2 master baremetal
        nmcli connection modify baremetal ipv4.addresses $PUB_IP_CIDR ipv4.method manual ipv4.gateway $PUB_GATEWAY
        nmcli connection modify provisioning ipv4.addresses 172.22.0.1/24,$PRIV_IP_CIDR ipv4.method manual
        nmcli connection modify provisioning +ipv4.routes \"10.0.0.0/8 $PRIV_GATEWAY\"
        nmcli con down baremetal
        nmcli con up baremetal
        nmcli con down provisioning
        nmcli con up provisioning
        init 6
    "

    Copy to Clipboard
    Note

    For eth1 and eth2, substitute the appropriate interface name, as needed.

24. If required, SSH back into the provisioner node:

    # ssh kni@provisioner.<cluster-name>.<domain>

    Copy to Clipboard

25. Verify the connection bridges have been properly created:

    $ sudo nmcli con show

    Copy to Clipboard

    Example output

    NAME               UUID                                  TYPE      DEVICE
    baremetal          4d5133a5-8351-4bb9-bfd4-3af264801530  bridge    baremetal
    provisioning       43942805-017f-4d7d-a2c2-7cb3324482ed  bridge    provisioning
    virbr0             d9bca40f-eee1-410b-8879-a2d4bb0465e7  bridge    virbr0
    bridge-slave-eth1  76a8ed50-c7e5-4999-b4f6-6d9014dd0812  ethernet  eth1
    bridge-slave-eth2  f31c3353-54b7-48de-893a-02d2b34c4736  ethernet  eth2

    Copy to Clipboard

26. Create a pull-secret.txt file:

    $ vim pull-secret.txt

    Copy to Clipboard

    In a web browser, navigate to Install on Bare Metal with user-provisioned infrastructure. In step 1, click Download pull secret. Paste the contents into the pull-secret.txt file and save the contents in the kni user’s home directory.

Procedure

1. Install dnsmasq:

   $ sudo dnf install dnsmasq

   Copy to Clipboard

2. Open the dnsmasq configuration file:

   $ sudo vi /etc/dnsmasq.conf

   Copy to Clipboard

3. Add the following configuration to the dnsmasq configuration file:

   interface=baremetal
   except-interface=lo
   bind-dynamic
   log-dhcp
   
   dhcp-range=<ip_addr>,<ip_addr>,<pub_cidr> 

   1

   
   dhcp-option=baremetal,121,0.0.0.0/0,<pub_gateway>,<prvn_priv_ip>,<prvn_pub_ip> 

   2

   
   
   dhcp-hostsfile=/var/lib/dnsmasq/dnsmasq.hostsfile

   Copy to Clipboard

   1

   Set the DHCP range. Replace both instances of <ip_addr> with one unused IP address from the public subnet so that the dhcp-range for the baremetal network begins and ends with the same the IP address. Replace <pub_cidr> with the CIDR of the public subnet.

   2

   Set the DHCP option. Replace <pub_gateway> with the IP address of the gateway for the baremetal network. Replace <prvn_priv_ip> with the IP address of the provisioner node’s private IP address on the provisioning network. Replace <prvn_pub_ip> with the IP address of the provisioner node’s public IP address on the baremetal network.

   To retrieve the value for <pub_cidr>, execute:

   $ ibmcloud sl subnet detail <publicsubnetid> --output JSON | jq .cidr

   Copy to Clipboard

   Replace <publicsubnetid> with the ID of the public subnet.

   To retrieve the value for <pub_gateway>, execute:

   $ ibmcloud sl subnet detail <publicsubnetid> --output JSON | jq .gateway -r

   Copy to Clipboard

   Replace <publicsubnetid> with the ID of the public subnet.

   To retrieve the value for <prvn_priv_ip>, execute:

   $ ibmcloud  sl hardware detail <id> --output JSON | \
               jq .primaryBackendIpAddress -r

   Copy to Clipboard

   Replace <id> with the ID of the provisioner node.

   To retrieve the value for <prvn_pub_ip>, execute:

   $ ibmcloud sl hardware detail <id> --output JSON | jq .primaryIpAddress -r

   Copy to Clipboard

   Replace <id> with the ID of the provisioner node.

4. Obtain the list of hardware for the cluster:

   $ ibmcloud sl hardware list

   Copy to Clipboard

5. Obtain the MAC addresses and IP addresses for each node:

   $ ibmcloud sl hardware detail <id> --output JSON | \
     jq '.networkComponents[] | \
     "\(.primaryIpAddress) \(.macAddress)"' | grep -v null

   Copy to Clipboard

   Replace <id> with the ID of the node.

   Example output

   "10.196.130.144 00:e0:ed:6a:ca:b4"
   "141.125.65.215 00:e0:ed:6a:ca:b5"

   Copy to Clipboard

   Make a note of the MAC address and IP address of the public network. Make a separate note of the MAC address of the private network, which you will use later in the install-config.yaml file. Repeat this procedure for each node until you have all the public MAC and IP addresses for the public baremetal network, and the MAC addresses of the private provisioning network.

6. Add the MAC and IP address pair of the public baremetal network for each node into the dnsmasq.hostsfile file:

   $ sudo vim /var/lib/dnsmasq/dnsmasq.hostsfile

   Copy to Clipboard

   Example input

   00:e0:ed:6a:ca:b5,141.125.65.215,master-0
   <mac>,<ip>,master-1
   <mac>,<ip>,master-2
   <mac>,<ip>,worker-0
   <mac>,<ip>,worker-1
   ...

   Copy to Clipboard

   Replace <mac>,<ip> with the public MAC address and public IP address of the corresponding node name.

7. Start dnsmasq:

   $ sudo systemctl start dnsmasq

   Copy to Clipboard

8. Enable dnsmasq so that it starts when booting the node:

   $ sudo systemctl enable dnsmasq

   Copy to Clipboard

9. Verify dnsmasq is running:

   $ sudo systemctl status dnsmasq

   Copy to Clipboard

   Example output

   ● dnsmasq.service - DNS caching server.
   Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2021-10-05 05:04:14 CDT; 49s ago
   Main PID: 3101 (dnsmasq)
   Tasks: 1 (limit: 204038)
   Memory: 732.0K
   CGroup: /system.slice/dnsmasq.service
   └─3101 /usr/sbin/dnsmasq -k

   Copy to Clipboard

10. Open ports 53 and 67 with UDP protocol:

    $ sudo firewall-cmd --add-port 53/udp --permanent

    Copy to Clipboard

    $ sudo firewall-cmd --add-port 67/udp --permanent

    Copy to Clipboard

11. Add provisioning to the external zone with masquerade:

    $ sudo firewall-cmd --change-zone=provisioning --zone=external --permanent

    Copy to Clipboard

    This step ensures network address translation for IPMI calls to the management subnet.

12. Reload the firewalld configuration:

    $ sudo firewall-cmd --reload

    Copy to Clipboard

Procedure

1. Set the environment variables:

   $ export cmd=openshift-baremetal-install

   Copy to Clipboard

   $ export pullsecret_file=~/pull-secret.txt

   Copy to Clipboard

   $ export extract_dir=$(pwd)

   Copy to Clipboard

2. Get the oc binary:

   $ curl -s https://mirror.openshift.com/pub/openshift-v4/clients/ocp/$VERSION/openshift-client-linux.tar.gz | tar zxvf - oc

   Copy to Clipboard

3. Extract the installer:

   $ sudo cp oc /usr/local/bin

   Copy to Clipboard

   $ oc adm release extract --registry-config "${pullsecret_file}" --command=$cmd --to "${extract_dir}" ${RELEASE_IMAGE}

   Copy to Clipboard

   $ sudo cp openshift-baremetal-install /usr/local/bin

   Copy to Clipboard

Procedure

1. Configure install-config.yaml. Change the appropriate variables to match the environment, including pullSecret and sshKey.

   apiVersion: v1
   baseDomain: <domain>
   metadata:
     name: <cluster_name>
   networking:
     machineNetwork:
     - cidr: <public-cidr>
     networkType: OVNKubernetes
   compute:
   - name: worker
     replicas: 2
   controlPlane:
     name: master
     replicas: 3
     platform:
       baremetal: {}
   platform:
     baremetal:
       apiVIP: <api_ip>
       ingressVIP: <wildcard_ip>
       provisioningNetworkInterface: <NIC1>
       provisioningNetworkCIDR: <CIDR>
       hosts:
         - name: openshift-master-0
           role: master
           bmc:
             address: ipmi://10.196.130.145?privilegelevel=OPERATOR 

   1

   
             username: root
             password: <password>
           bootMACAddress: 00:e0:ed:6a:ca:b4 

   2

   
           rootDeviceHints:
             deviceName: "/dev/sda"
         - name: openshift-worker-0
           role: worker
           bmc:
             address: ipmi://<out-of-band-ip>?privilegelevel=OPERATOR 

   3

   
             username: <user>
             password: <password>
           bootMACAddress: <NIC1_mac_address> 

   4

   
           rootDeviceHints:
             deviceName: "/dev/sda"
   pullSecret: '<pull_secret>'
   sshKey: '<ssh_pub_key>'

   Copy to Clipboard

   1 3

   The bmc.address provides a privilegelevel configuration setting with the value set to OPERATOR. This is required for IBM Cloud® Bare Metal (Classic) infrastructure.

   2 4

   Add the MAC address of the private provisioning network NIC for the corresponding node.

   Note

   You can use the ibmcloud command-line utility to retrieve the password.

   $ ibmcloud sl hardware detail <id> --output JSON | \
     jq '"(.networkManagementIpAddress) (.remoteManagementAccounts[0].password)"'

   Copy to Clipboard

   Replace <id> with the ID of the node.

2. Create a directory to store the cluster configuration:

   $ mkdir ~/clusterconfigs

   Copy to Clipboard

3. Copy the install-config.yaml file into the directory:

   $ cp install-config.yaml ~/clusterconfigs

   Copy to Clipboard

4. Ensure all bare metal nodes are powered off prior to installing the OpenShift Container Platform cluster:

   $ ipmitool -I lanplus -U <user> -P <password> -H <management_server_ip> power off

   Copy to Clipboard

5. Remove old bootstrap resources if any are left over from a previous deployment attempt:

   for i in $(sudo virsh list | tail -n +3 | grep bootstrap | awk {'print $2'});
   do
     sudo virsh destroy $i;
     sudo virsh undefine $i;
     sudo virsh vol-delete $i --pool $i;
     sudo virsh vol-delete $i.ign --pool $i;
     sudo virsh pool-destroy $i;
     sudo virsh pool-undefine $i;
   done

   Copy to Clipboard

1. Create the OpenShift Container Platform manifests.

   $ ./openshift-baremetal-install --dir ~/clusterconfigs create manifests

   Copy to Clipboard

   INFO Consuming Install Config from target directory
   WARNING Making control-plane schedulable by setting MastersSchedulable to true for Scheduler cluster settings
   WARNING Discarding the OpenShift Manifest that was provided in the target directory because its dependencies are dirty and it needs to be regenerated

   Copy to Clipboard