- Interface names in worker nodes have the inteface naming convention: ens2, ens3, ens4, ens5, etc.
- Interface names in master nodes have the inteface naming convention: ens1f0, ens1f1, ens1f2, ens1f3, etc.
This script creates the ignition files for master and worker nodes, and inserts network-scripts into those, in order to integrate Openshift installed on baremetal devices with an ACI fabric.
Note: Find the full Openshift on Baremetal installation with Cisco ACI here.
The script will allow you to choose between use cases listed in the table below. Depending on your use case, you need to edit config.yaml accordingly.
| Case | What to provide in config.yaml |
|---|---|
| Single interface for node network and bond interface for infra network | Single node network interface name and two ACI infra network interface names under both os_cp_nodes and os_compute_nodes |
| Bond interface for both node and infra networks | Two node network interface names and two ACI infra network interface names under both os_cp_nodes and os_compute_nodes |
| Bond interface for node network and single interface for infra network | Two node network interface names and single ACI infra network interface name under both os_cp_nodes and os_compute_nodes |
| Single interface for both node and infra networks | Single node network interface name and single ACI infra network interface name under both os_cp_nodes and os_compute_nodes |
Before running this script please update the config.yaml file.
To run this script:
~/<installation_dir>/upi$ python3 update_ign.pyExpected Output: Ignition files for worker and master nodes including the bootstrap created in the upi directory with the naming convention: <Infra-Id>-<bootstrap|master|worker>-ignition.json
Next Steps: After running the script, copy the generated ignition files to directory where they will be served from at install time, and proceed with the installation.