Skip to content

Commit 8146d88

Browse files
authored
Merge pull request #48746 from johnwilkins/BZ-2004210-separate-networking
BZ 2004210: Separate the configuing networking steps into their own module.
2 parents 386ab95 + a9c7dd2 commit 8146d88

File tree

3 files changed

+110
-93
lines changed

3 files changed

+110
-93
lines changed

installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ include::modules/ipi-install-installing-rhel-on-the-provisioner-node.adoc[levelo
1010

1111
include::modules/ipi-install-preparing-the-provisioner-node-for-openshift-install.adoc[leveloffset=+1]
1212

13+
include::modules/ipi-install-configuring-networking.adoc[leveloffset=+1]
14+
1315
include::modules/ipi-install-retrieving-the-openshift-installer.adoc[leveloffset=+1]
1416

1517
include::modules/ipi-install-extracting-the-openshift-installer.adoc[leveloffset=+1]
Lines changed: 108 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,108 @@
1+
// This is included in the following assemblies:
2+
//
3+
// ipi-install-installation-workflow.adoc
4+
5+
:_content-type: PROCEDURE
6+
[id="configuring-networking_{context}"]
7+
= Configuring networking
8+
9+
Before installation, you must configure the networking on the provisioner node. Installer-provisioned clusters deploy with a `baremetal` bridge and network, and an optional `provisioning` bridge and network.
10+
11+
image::210_OpenShift_Baremetal_IPI_Deployment_updates_0122_1.png[Configure networking]
12+
13+
[NOTE]
14+
====
15+
You can also configure networking from the web console.
16+
====
17+
18+
.Procedure
19+
20+
. Export the `baremetal` network NIC name:
21+
+
22+
[source,terminal]
23+
----
24+
$ export PUB_CONN=<baremetal_nic_name>
25+
----
26+
27+
. Configure the `baremetal` network:
28+
+
29+
[source,terminal]
30+
----
31+
$ sudo nohup bash -c "
32+
nmcli con down \"$PUB_CONN\"
33+
nmcli con delete \"$PUB_CONN\"
34+
# RHEL 8.1 appends the word \"System\" in front of the connection, delete in case it exists
35+
nmcli con down \"System $PUB_CONN\"
36+
nmcli con delete \"System $PUB_CONN\"
37+
nmcli connection add ifname baremetal type bridge con-name baremetal
38+
nmcli con add type bridge-slave ifname \"$PUB_CONN\" master baremetal
39+
pkill dhclient;dhclient baremetal
40+
"
41+
----
42+
+
43+
[NOTE]
44+
====
45+
The ssh connection might disconnect after executing these steps.
46+
====
47+
48+
. Optional: If you are deploying with a `provisioning` network, export the `provisioning` network NIC name:
49+
+
50+
[source,terminal]
51+
----
52+
$ export PROV_CONN=<prov_nic_name>
53+
----
54+
55+
. Optional: If you are deploying with a `provisioning` network, configure the `provisioning` network:
56+
+
57+
[source,terminal]
58+
----
59+
$ sudo nohup bash -c "
60+
nmcli con down \"$PROV_CONN\"
61+
nmcli con delete \"$PROV_CONN\"
62+
nmcli connection add ifname provisioning type bridge con-name provisioning
63+
nmcli con add type bridge-slave ifname \"$PROV_CONN\" master provisioning
64+
nmcli connection modify provisioning ipv6.addresses fd00:1101::1/64 ipv6.method manual
65+
nmcli con down provisioning
66+
nmcli con up provisioning
67+
"
68+
----
69+
+
70+
[NOTE]
71+
====
72+
The ssh connection might disconnect after executing these steps.
73+
74+
The IPv6 address can be any address as long as it is not routable via the `baremetal` network.
75+
76+
Ensure that UEFI is enabled and UEFI PXE settings are set to the IPv6 protocol when using IPv6 addressing.
77+
====
78+
79+
. Optional: If you are deploying with a `provisioning` network, configure the IPv4 address on the `provisioning` network connection:
80+
+
81+
[source,terminal]
82+
----
83+
$ nmcli connection modify provisioning ipv4.addresses 172.22.0.254/24 ipv4.method manual
84+
----
85+
86+
. `ssh` back into the `provisioner` node (if required):
87+
+
88+
[source,terminal]
89+
----
90+
# ssh kni@provisioner.<cluster-name>.<domain>
91+
----
92+
93+
. Verify the connection bridges have been properly created:
94+
+
95+
[source,terminal]
96+
----
97+
$ sudo nmcli con show
98+
----
99+
+
100+
[source,terminal]
101+
----
102+
NAME UUID TYPE DEVICE
103+
baremetal 4d5133a5-8351-4bb9-bfd4-3af264801530 bridge baremetal
104+
provisioning 43942805-017f-4d7d-a2c2-7cb3324482ed bridge provisioning
105+
virbr0 d9bca40f-eee1-410b-8879-a2d4bb0465e7 bridge virbr0
106+
bridge-slave-eno1 76a8ed50-c7e5-4999-b4f6-6d9014dd0812 ethernet eno1
107+
bridge-slave-eno2 f31c3353-54b7-48de-893a-02d2b34c4736 ethernet eno2
108+
----

modules/ipi-install-preparing-the-provisioner-node-for-openshift-install.adoc

Lines changed: 0 additions & 93 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,6 @@ Perform the following steps to prepare the environment.
3434
# chmod 0440 /etc/sudoers.d/kni
3535
----
3636

37-
3837
. Create an `ssh` key for the new user:
3938
+
4039
[source,terminal]
@@ -119,98 +118,6 @@ $ sudo virsh pool-start default
119118
$ sudo virsh pool-autostart default
120119
----
121120

122-
. Configure networking.
123-
+
124-
[NOTE]
125-
====
126-
You can also configure networking from the web console.
127-
====
128-
+
129-
Export the `baremetal` network NIC name:
130-
+
131-
[source,terminal]
132-
----
133-
$ export PUB_CONN=<baremetal_nic_name>
134-
----
135-
+
136-
Configure the `baremetal` network:
137-
+
138-
[source,terminal]
139-
----
140-
$ sudo nohup bash -c "
141-
nmcli con down \"$PUB_CONN\"
142-
nmcli con delete \"$PUB_CONN\"
143-
# RHEL 8.1 appends the word \"System\" in front of the connection, delete in case it exists
144-
nmcli con down \"System $PUB_CONN\"
145-
nmcli con delete \"System $PUB_CONN\"
146-
nmcli connection add ifname baremetal type bridge con-name baremetal
147-
nmcli con add type bridge-slave ifname \"$PUB_CONN\" master baremetal
148-
pkill dhclient;dhclient baremetal
149-
"
150-
----
151-
+
152-
If you are deploying with a `provisioning` network, export the `provisioning` network NIC name:
153-
+
154-
[source,terminal]
155-
----
156-
$ export PROV_CONN=<prov_nic_name>
157-
----
158-
+
159-
If you are deploying with a `provisioning` network, configure the `provisioning` network:
160-
+
161-
[source,terminal]
162-
----
163-
$ sudo nohup bash -c "
164-
nmcli con down \"$PROV_CONN\"
165-
nmcli con delete \"$PROV_CONN\"
166-
nmcli connection add ifname provisioning type bridge con-name provisioning
167-
nmcli con add type bridge-slave ifname \"$PROV_CONN\" master provisioning
168-
nmcli connection modify provisioning ipv6.addresses fd00:1101::1/64 ipv6.method manual
169-
nmcli con down provisioning
170-
nmcli con up provisioning
171-
"
172-
----
173-
+
174-
[NOTE]
175-
====
176-
The `ssh` connection might disconnect after executing these steps.
177-
178-
The IPv6 address can be any address as long as it is not routable via the `baremetal` network.
179-
180-
Ensure that UEFI is enabled and UEFI PXE settings are set to the IPv6 protocol when using IPv6 addressing.
181-
====
182-
183-
. Configure the IPv4 address on the `provisioning` network connection:
184-
+
185-
[source,terminal]
186-
----
187-
$ nmcli connection modify provisioning ipv4.addresses 172.22.0.254/24 ipv4.method manual
188-
----
189-
190-
. `ssh` back into the `provisioner` node (if required):
191-
+
192-
[source,terminal]
193-
----
194-
# ssh kni@provisioner.<cluster-name>.<domain>
195-
----
196-
197-
. Verify the connection bridges have been properly created:
198-
+
199-
[source,terminal]
200-
----
201-
$ sudo nmcli con show
202-
----
203-
+
204-
[source,terminal]
205-
----
206-
NAME UUID TYPE DEVICE
207-
baremetal 4d5133a5-8351-4bb9-bfd4-3af264801530 bridge baremetal
208-
provisioning 43942805-017f-4d7d-a2c2-7cb3324482ed bridge provisioning
209-
virbr0 d9bca40f-eee1-410b-8879-a2d4bb0465e7 bridge virbr0
210-
bridge-slave-eno1 76a8ed50-c7e5-4999-b4f6-6d9014dd0812 ethernet eno1
211-
bridge-slave-eno2 f31c3353-54b7-48de-893a-02d2b34c4736 ethernet eno2
212-
----
213-
214121
. Create a `pull-secret.txt` file:
215122
+
216123
[source,terminal]

0 commit comments

Comments
 (0)