Skip to content

[WIP] HCP docs update for IBM Power #92359

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.

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

alishaIBM
Copy link
Contributor

@alishaIBM alishaIBM commented Apr 18, 2025

@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Apr 18, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Apr 18, 2025

@openshift-ci openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Apr 18, 2025
@alishaIBM alishaIBM changed the title HCP docs update for IBM Power [WIP] HCP docs update for IBM Power Apr 18, 2025
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 18, 2025
@alishaIBM alishaIBM force-pushed the hcp_update branch 2 times, most recently from 5567681 to 025093f Compare April 24, 2025 06:27
Copy link

openshift-ci bot commented Apr 24, 2025

@alishaIBM: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Copy link
Contributor

@lahinson lahinson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Before I can do a more detailed review, you need to make some structural changes here to comply with the OCP documentation standards. I provided a few comments to indicate what needs to be changed. Thanks! cc @xenolinux

+
The above configuration allows you to create ISO for both x86_64 and ppc64le architectures.


Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The content in lines 68 - 100 should be in its own module.

--release-image=quay.io/openshift-release-dev/ocp-release:${OCP_RELEASE}
----


Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The content from lines 103 - 147 should be in its own module.


.Procedure

. to create heterogeneous nodepools
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Be sure to use complete sentences and capitalize the first word in a sentence.

Suggested change
. to create heterogeneous nodepools
. To create heterogeneous node pools, create a YAML file that contains the following content:

+
This selector block is used to select the agents which are matching the given label. Which will ensure it will select only the agents from ppc64le architecture when it is scaled.


Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The content from lines 150 - 196 should be in its own module.

----
+
This will create two infraenvs with x86_64 & ppc64le architectures. Before proceeding, make sure that the OS images for both architectures are added to the AgentServiceConfig. After this you can use the above infraenvs to get the minimal iso and follow the create-agent-cluster.md to add them to your cluster as agents.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The content from lines 198 - 201 should be in its own module.

.Procedure

. Configure AgentServiceConfig with two heterogeneous architecture OS images:
+
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From the OCP docs guidelines: Do not use more than one command per code block.

$ export ISO_URL_PPC64LE="https://mirror.openshift.com/pub/openshift-v4/${ARCH_PPC64LE}/dependencies/rhcos/${OCP_MAJMIN}/${OCP_VERSION}/rhcos-${OCP_VERSION}-${ARCH_PPC64LE}-live.${ARCH_PPC64LE}.iso"
$ export ROOT_FS_URL_PPC64LE="https://mirror.openshift.com/pub/openshift-v4/${ARCH_PPC64LE}/dependencies/rhcos/${OCP_MAJMIN}/${OCP_VERSION}/rhcos-${OCP_VERSION}-${ARCH_PPC64LE}-live-rootfs.${ARCH_PPC64LE}.img"
----
+
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the following code block and others like it in this file, the code needs to be rewritten to separate out the content that the user will enter in the YAML file and the command to apply the changes. For an example, see steps 1 - 3 in Creating an InfraEnv resource for hosted control planes on IBM Z.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To comply with the modular documentation guidelines that we follow for the OCP documentation, the various sections in this file need to be moved to their own modules. After you create those modules, in the assembly file, add the modules below your new include::modules/hcp-ibm-power-create-heterogeneous-nodepools-agent-hc.adoc[leveloffset=+1] module, and ensure that instead of using [leveloffset=+1], you use [leveloffset=+2].

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants