You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/bmo-about-the-baremetalhost-resource.adoc
+9-2Lines changed: 9 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,7 +90,14 @@ raid:
90
90
hardwareRAIDVolumes:
91
91
softwareRAIDVolumes:
92
92
----
93
-
a| (Optional) Contains the information about the RAID configuration for bare metal hosts. If not specified, it retains the current configuration. Currently, `raid` is only supported by iRMC, iDRAC, and iLO5 BMCs. The fields are:
93
+
a| (Optional) Contains the information about the RAID configuration for bare metal hosts. If not specified, it retains the current configuration.
94
+
95
+
[NOTE]
96
+
====
97
+
{product-title} {product-version} supports hardware RAID for BMCs using the iRMC protocol only. {product-title} {product-version} does not support software RAID.
98
+
====
99
+
100
+
See the following configuration settings:
94
101
95
102
* `hardwareRAIDVolumes`: Contains the list of logical drives for hardware RAID, and defines the desired volume configuration in the hardware RAID. If you don't specify `rootDeviceHints`, the first volume is the root volume. The sub-fields are:
96
103
@@ -102,7 +109,7 @@ a| (Optional) Contains the information about the RAID configuration for bare me
102
109
** `rotational`: If set to `true`, it will only select rotational disk drives. If set to `false`, it will only select solid-state and NVMe drives. If not set, it selects any drive types, which is the default behavior.
103
110
** `sizeGibibytes`: The size of the logical drive as an integer to create in GiB. If unspecified or set to `0`, it will use the maximum capacity of physical drive for the logical drive.
104
111
105
-
* `softwareRAIDVolumes`: Contains the list of logical disks for software RAID. If you don't specify `rootDeviceHints`, the first volume is the root volume. If you set `HardwareRAIDVolumes`, this item will be invalid. Software RAIDs will always be deleted. The number of created software RAID devices must be `1` or `2`. If there is only one software RAID device, it must be `RAID-1`. If there are two RAID devices, the first device must be `RAID-1`, while the RAID level for the second device can be `0`, `1`, or `1+0`. The first RAID device will be the deployment device. Therefore, enforcing `RAID-1` reduces the risk of a non-booting node in case of a device failure. The `softwareRAIDVolume` field defines the desired configuration of the volume in the software RAID. The sub-fields are:
112
+
* `softwareRAIDVolumes`: {product-title} {product-version} does not support software RAID. The following information is for reference only. This configuration contains the list of logical disks for software RAID. If you don't specify `rootDeviceHints`, the first volume is the root volume. If you set `HardwareRAIDVolumes`, this item will be invalid. Software RAIDs will always be deleted. The number of created software RAID devices must be `1` or `2`. If there is only one software RAID device, it must be `RAID-1`. If there are two RAID devices, the first device must be `RAID-1`, while the RAID level for the second device can be `0`, `1`, or `1+0`. The first RAID device will be the deployment device. Therefore, enforcing `RAID-1` reduces the risk of a non-booting node in case of a device failure. The `softwareRAIDVolume` field defines the desired configuration of the volume in the software RAID. The sub-fields are:
106
113
107
114
** `level`: The RAID level for the logical drive. The following levels are supported: `0`,`1`,`1+0`.
108
115
** `physicalDisks`: A list of device hints. The number of items should be greater than or equal to `2`.
Copy file name to clipboardExpand all lines: modules/ipi-install-configuring-the-raid.adoc
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,8 +10,8 @@ The following procedure configures a redundant array of independent disks (RAID)
10
10
11
11
[NOTE]
12
12
====
13
-
. Only nodes with baseboard management controller (BMC) type `irmc` are supported. Other types of nodes are currently not supported.
14
-
. If you want to configure a hardware RAID for the node, make sure the node has a RAID controller.
13
+
. {product-title} supports hardware RAID for baseboard management controllers (BMCs) using the iRMC protocol only. {product-title} {product-version} does not support software RAID.
14
+
. If you want to configure a hardware RAID for the node, verify that the node has a RAID controller.
15
15
====
16
16
17
17
.Procedure
@@ -27,7 +27,7 @@ $ vim clusterconfigs/openshift/99_openshift-cluster-api_hosts-*.yaml
27
27
+
28
28
[NOTE]
29
29
====
30
-
Because nodes with BMC type `irmc` do not support software RAID, the following RAID configuration uses hardware RAID as an example.
30
+
The following example uses a hardware RAID configuration because {product-title} {product-version} does not support software RAID.
31
31
====
32
32
+
33
33
.. If you added a specific RAID configuration to the `spec` section, this causes the node to delete the original RAID configuration in the `preparing` phase and perform a specified configuration on the RAID. For example:
0 commit comments