mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
113 lines
3.3 KiB
Plaintext
113 lines
3.3 KiB
Plaintext
// This is included in the following assemblies:
|
|
//
|
|
// installing_ibm_cloud_classic/install-ibm-cloud-installing-on-ibm-cloud.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="configuring-the-install-config-file_{context}"]
|
|
= Configuring the install-config.yaml file
|
|
|
|
The `install-config.yaml` file requires some additional details. Most of the information is teaching the installer and the resulting cluster enough about the available {ibm-cloud-bm} hardware so that it is able to fully manage it. The material difference between installing on bare metal and installing on {ibm-cloud-bm} is that you must explicitly set the privilege level for IPMI in the BMC section of the `install-config.yaml` file.
|
|
|
|
.Procedure
|
|
|
|
. Configure `install-config.yaml`. Change the appropriate variables to match the environment, including `pullSecret` and `sshKey`.
|
|
+
|
|
[source,yaml]
|
|
----
|
|
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 <1>
|
|
username: <user>
|
|
password: <password>
|
|
bootMACAddress: <NIC1_mac_address> <2>
|
|
rootDeviceHints:
|
|
deviceName: "/dev/sda"
|
|
pullSecret: '<pull_secret>'
|
|
sshKey: '<ssh_pub_key>'
|
|
----
|
|
+
|
|
<1> The `bmc.address` provides a `privilegelevel` configuration setting with the value set to `OPERATOR`. This is required for {ibm-cloud-bm} infrastructure.
|
|
<2> 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.
|
|
|
|
[source,terminal]
|
|
----
|
|
$ ibmcloud sl hardware detail <id> --output JSON | \
|
|
jq '"(.networkManagementIpAddress) (.remoteManagementAccounts[0].password)"'
|
|
----
|
|
|
|
Replace `<id>` with the ID of the node.
|
|
====
|
|
|
|
. Create a directory to store the cluster configuration:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ mkdir ~/clusterconfigs
|
|
----
|
|
|
|
. Copy the `install-config.yaml` file into the directory:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ cp install-config.yaml ~/clusterconfig
|
|
----
|
|
|
|
. Ensure all bare metal nodes are powered off prior to installing the {product-title} cluster:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ ipmitool -I lanplus -U <user> -P <password> -H <management_server_ip> power off
|
|
----
|
|
|
|
. Remove old bootstrap resources if any are left over from a previous deployment attempt:
|
|
+
|
|
[source,bash]
|
|
----
|
|
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
|
|
----
|