Skip to content

[enterprise-4.14] [MULTIARCH-3707] OCP 4.14: Installation doc updates for IBM Power #66087

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 11, 2023
Merged

[enterprise-4.14] [MULTIARCH-3707] OCP 4.14: Installation doc updates for IBM Power #66087

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions modules/minimum-ibm-power-system-requirements.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ Support for {op-system} functionality for all IBM Power8 models, IBM Power AC922
[discrete]
== Hardware requirements

* Six IBM Power bare metal servers or six LPARs across multiple PowerVM servers
* Six logical partitions (LPARs) across multiple PowerVM servers

[discrete]
== Operating system requirements
Expand All @@ -28,9 +28,9 @@ Support for {op-system} functionality for all IBM Power8 models, IBM Power AC922

On your IBM Power instance, set up:

* Three guest virtual machines for {product-title} control plane machines
* Two guest virtual machines for {product-title} compute machines
* One guest virtual machine for the temporary {product-title} bootstrap machine
* Three LPARs for {product-title} control plane machines
* Two LPARs for {product-title} compute machines
* One LPAR for the temporary {product-title} bootstrap machine

[discrete]
== Disk storage for the IBM Power guest virtual machines
Expand Down
8 changes: 4 additions & 4 deletions modules/recommended-ibm-power-system-requirements.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@
[discrete]
== Hardware requirements

* Six IBM Power bare metal servers or six LPARs across multiple PowerVM servers
* Six LPARs across multiple PowerVM servers

[discrete]
== Operating system requirements
Expand All @@ -19,9 +19,9 @@

On your IBM Power instance, set up:

* Three guest virtual machines for {product-title} control plane machines
* Two guest virtual machines for {product-title} compute machines
* One guest virtual machine for the temporary {product-title} bootstrap machine
* Three LPARs for {product-title} control plane machines
* Two LPARs for {product-title} compute machines
* One LPAR for the temporary {product-title} bootstrap machine

[discrete]
== Disk storage for the IBM Power guest virtual machines
Expand Down
2 changes: 1 addition & 1 deletion modules/rhcos-enabling-multipath-day-1-power.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
[id="rhcos-enabling-multipathday-1-power_{context}"]
= Enabling multipathing with kernel arguments on {op-system}

In {product-title} 4.9 or later, during installation, you can enable multipathing for provisioned nodes. {op-system} supports multipathing on the primary disk. Multipathing provides added benefits of stronger resilience to hardware failure to achieve higher host availability.
In {product-title} version {product-version}, during installation, you can enable multipathing for provisioned nodes. {op-system} supports multipathing on the primary disk. Multipathing provides added benefits of stronger resilience to hardware failure to achieve higher host availability.

During the initial cluster creation, you might want to add kernel arguments to all master or worker nodes. To add kernel arguments to master or worker nodes, you can create a `MachineConfig` object and inject that object into the set of manifest files used by Ignition during cluster setup.

Expand Down