eifrach / kcli-openshift4-baremetal Goto Github PK

This repository provides a plan which deploys a vm where:

• openshift-baremetal-install is downloaded or compiled from source (with an additional list of PR numbers to apply)
• stop the nodes to deploy through ipmi
• launch the install against a set of baremetal nodes. Virtual masters can also be deployed.

To deploy baremetal using bare minimum on the provisioning node

• kcli installed (for rhel8/cento8/fedora, look here)
• an openshift pull secret (stored by default in openshift_pull.json)

• libvirt daemon (with fw_cfg support)
• two physical bridges:
  • baremetal with a nic from the external network
  • provisioning with a nic from the provisioning network. Ideally assign it an ip of 172.22.0.1/24
• If you're not running as root, configure extra permissions with sudo setfacl -m u:$(id -un):rwx /var/lib/libvirt/openshift-images/*

Here's a script you can run on the provisioning node for that (adjust the nics variable as per your environment)

export MAIN_CONN=eno2
sudo nmcli connection add ifname baremetal type bridge con-name baremetal
sudo nmcli con add type bridge-slave ifname "$MAIN_CONN" master baremetal
sudo nmcli con down "System $MAIN_CONN"; sudo pkill dhclient; sudo dhclient baremetal
export PROV_CONN=eno1
sudo nmcli connection add ifname provisioning type bridge con-name provisioning
sudo nmcli con add type bridge-slave ifname "$PROV_CONN" master provisioning
sudo nmcli connection modify provisioning ipv4.addresses 172.22.0.1/24 ipv4.method manual
sudo nmcli con down provisioning
sudo nmcli con up provisioning

If using vlans on the provisioning interface, the following can be used:

VLANID=1200
BRIDGE=prov$VLAN
IP="172.22.0.100/24"
nmcli connection add ifname $BRIDGE type bridge con-name $BRIDGE
nmcli connection add type vlan con-name vlan$VLAN ifname eno1.$VLAN dev eno1 id $VLAN master $BRIDGE slave-type bridge
nmcli connection modify $BRIDGE ipv4.addresses $IP ipv4.method manual
nmcli con down $BRIDGE
nmcli con up $BRIDGE

Prepare a valid parameter file with the information needed. At least, you need to specify the following elements:

• api_ip
• ingress_ip
• dns_ip (optional)
• bmc_user (for real baremetal)
• bmc_password (for real baremetal)
• an array of your masters (if thet are not virtual). Each entry in this array needs at least the provisioning_mac and ipmi_address. Optionally you can indicate for each entry a specific bmc_user, bmc_password and disk (to be used as rootdevice hint) either as /dev/XXX or simply XXX
• an array of your workers (can be left empty if you only want to deploy masters). The format of those entries follow the one indicated for masters.

Here's a snippet what the workers variable might look like:

workers:
- ipmi_address: 192.168.1.5
  provisioning_mac: 98:03:9b:62:ab:19
- ipmi_address: 192.168.1.6
  provisioning_mac: 98:03:9b:62:ab:17
  disk: /dev/sde

You can have a look at:

• parameters.yml.sample for a parameter file targetting baremetal nodes only
• parameters_virtual.yml.sample for one combining virtual masters and physical workers.

Call the resulting file kcli_parameters.yml to avoid having to specify it in the creation command.

Then you can launch deployment with:

kcli create plan

The deployed vm comes with a set of helpers for you:

• scripts deploy.sh and clean.sh allow you to manually launch an install or clean a failed one
• you can run baremetal node list during deployment to check the status of the provisioning of the nodes (Give some time after launching an install before ironic is accessible).
• script ipmi.py can be used to check the power status of the baremetal node or to stop them (using ipmi.py off). When not using provisioning network, a script named redfish.py provides a similar functionality

when specifying masters or workers as an array, the specification can be created with something like this

- ipmi_address: 192.168.123.45
  provisioning_mac: 98:03:9b:62:81:49

The following parameters can be used in this case:

• ipmi_address. Redfish ip
• redfish_address. Redfish url
• provisioning_mac. It needs to be set to the mac to use along with provisioning network or any of the macs of the node when provisioning is disabled
• boot_mode (optional). Should either be set to Legacy, UEFI or UEFISecureBoot

A lab available here is provided to get people familiarized with Baremetal Ipi workflow.