Skip to content

Commit 2fa9f55

Browse files
authored
Merge pull request #50271 from johnwilkins/TELCDOCS-321-download-urls
TELCODOCS-321: D/S Docs & RN: METAL-1 (MPINSTALL-72) Metal Day 1 Networking
2 parents bb12602 + b9d620f commit 2fa9f55

File tree

2 files changed

+11
-17
lines changed

2 files changed

+11
-17
lines changed

modules/ipi-install-preparing-to-deploy-with-virtual-media-on-the-baremetal-network.adoc

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,13 +34,11 @@ oc edit provisioning
3434
resourceVersion: "551591"
3535
uid: f76e956f-24c6-4361-aa5b-feaf72c5b526
3636
spec:
37-
preProvisioningOSDownloadURLs: {}
3837
provisioningDHCPRange: 172.22.0.10,172.22.0.254
3938
provisioningIP: 172.22.0.3
4039
provisioningInterface: enp1s0
4140
provisioningNetwork: Managed
4241
provisioningNetworkCIDR: 172.22.0.0/24
43-
provisioningOSDownloadURL: http://192.168.111.1/images/rhcos-<version>.<architecture>.qcow2.gz?sha256=<sha256>
4442
virtualMediaViaExternalNetwork: true <1>
4543
status:
4644
generations:
@@ -62,7 +60,6 @@ oc edit provisioning
6260
+
6361
<1> Add `virtualMediaViaExternalNetwork: true` to the `provisioning` CR.
6462

65-
6663
. If the image URL exists, edit the `machineset` to use the API VIP address. This step only applies to clusters installed in versions 4.9 or earlier.
6764
+
6865
[source,terminal]

modules/nw-enabling-a-provisioning-network-after-installation.adoc

Lines changed: 11 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ $ oc get provisioning -o yaml > enable-provisioning-nw.yaml
3838
$ vim ~/enable-provisioning-nw.yaml
3939
----
4040
+
41-
Scroll down to the `provisioningNetwork` configuration setting and change it from `Disabled` to `Managed`. Then, add the `provisioningOSDownloadURL`, `provisioningIP`, `provisioningNetworkCIDR`, `provisioningDHCPRange`, `provisioningInterface`, and `watchAllNameSpaces` configuration settings after the `provisioningNetwork` setting. Provide appropriate values for each setting.
41+
Scroll down to the `provisioningNetwork` configuration setting and change it from `Disabled` to `Managed`. Then, add the `provisioningIP`, `provisioningNetworkCIDR`, `provisioningDHCPRange`, `provisioningInterface`, and `watchAllNameSpaces` configuration settings after the `provisioningNetwork` setting. Provide appropriate values for each setting.
4242
+
4343
[source,yaml]
4444
----
@@ -50,27 +50,24 @@ items:
5050
name: provisioning-configuration
5151
spec:
5252
provisioningNetwork: <1>
53-
provisioningOSDownloadURL: <2>
54-
provisioningIP: <3>
55-
provisioningNetworkCIDR: <4>
56-
provisioningDHCPRange: <5>
57-
provisioningInterface: <6>
58-
watchAllNameSpaces: <7>
53+
provisioningIP: <2>
54+
provisioningNetworkCIDR: <3>
55+
provisioningDHCPRange: <4>
56+
provisioningInterface: <5>
57+
watchAllNameSpaces: <6>
5958
----
6059
+
6160
<1> The `provisioningNetwork` is one of `Managed`, `Unmanaged`, or `Disabled`. When set to `Managed`, Metal3 manages the provisioning network and the CBO deploys the Metal3 pod with a configured DHCP server. When set to `Unmanaged`, the system administrator configures the DHCP server manually.
6261
+
63-
<2> The `provisioningOSDownloadURL` is a valid HTTPS URL with a valid sha256 checksum that enables the Metal3 pod to download a qcow2 operating system image ending in `.qcow2.gz` or `.qcow2.xz`. This field is required whether the provisioning network is `Managed`, `Unmanaged`, or `Disabled`. For example: `\http://192.168.0.1/images/{op-system-lowercase}-_<version>_.x86_64.qcow2.gz?sha256=_<sha>_`.
62+
<2> The `provisioningIP` is the static IP address that the DHCP server and ironic use to provision the network. This static IP address must be within the `provisioning` subnet, and outside of the DHCP range. If you configure this setting, it must have a valid IP address even if the `provisioning` network is `Disabled`. The static IP address is bound to the metal3 pod. If the metal3 pod fails and moves to another server, the static IP address also moves to the new server.
6463
+
65-
<3> The `provisioningIP` is the static IP address that the DHCP server and ironic use to provision the network. This static IP address must be within the `provisioning` subnet, and outside of the DHCP range. If you configure this setting, it must have a valid IP address even if the `provisioning` network is `Disabled`. The static IP address is bound to the metal3 pod. If the metal3 pod fails and moves to another server, the static IP address also moves to the new server.
64+
<3> The Classless Inter-Domain Routing (CIDR) address. If you configure this setting, it must have a valid CIDR address even if the `provisioning` network is `Disabled`. For example: `192.168.0.1/24`.
6665
+
67-
<4> The Classless Inter-Domain Routing (CIDR) address. If you configure this setting, it must have a valid CIDR address even if the `provisioning` network is `Disabled`. For example: `192.168.0.1/24`.
66+
<4> The DHCP range. This setting is only applicable to a `Managed` provisioning network. Omit this configuration setting if the `provisioning` network is `Disabled`. For example: `192.168.0.64, 192.168.0.253`.
6867
+
69-
<5> The DHCP range. This setting is only applicable to a `Managed` provisioning network. Omit this configuration setting if the `provisioning` network is `Disabled`. For example: `192.168.0.64, 192.168.0.253`.
68+
<5> The NIC name for the `provisioning` interface on cluster nodes. The `provisioningInterface` setting is only applicable to `Managed` and `Unmanaged` provisioning networks. Omit the `provisioningInterface` configuration setting if the `provisioning` network is `Disabled`. Omit the `provisioningInterface` configuration setting to use the `bootMACAddress` configuration setting instead.
7069
+
71-
<6> The NIC name for the `provisioning` interface on cluster nodes. The `provisioningInterface` setting is only applicable to `Managed` and `Unmanaged` provisioning networks. Omit the `provisioningInterface` configuration setting if the `provisioning` network is `Disabled`. Omit the `provisioningInterface` configuration setting to use the `bootMACAddress` configuration setting instead.
72-
+
73-
<7> Set this setting to `true` if you want metal3 to watch namespaces other than the default `openshift-machine-api` namespace. The default value is `false`.
70+
<6> Set this setting to `true` if you want metal3 to watch namespaces other than the default `openshift-machine-api` namespace. The default value is `false`.
7471

7572
. Save the changes to the provisioning CR file.
7673

0 commit comments

Comments
 (0)