Skip to content

[OSDOCS-20482]: CQA: Managing HCP on IBM Power #114541

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

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

[OSDOCS-20482]: CQA: Managing HCP on IBM Power #114541

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
5 changes: 3 additions & 2 deletions hosted_control_planes/hcp-manage/hcp-manage-ibm-power.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,13 @@
:_mod-docs-content-type: ASSEMBLY
[id="hcp-manage-ibm-power"]
include::_attributes/common-attributes.adoc[]
[id="hcp-manage-ibm-power"]
= Managing {hcp} on {ibm-power-title}
:context: hcp-manage-ibm-power

toc::[]

After you deploy {hcp} on {ibm-power-title}, you can manage a hosted cluster by completing the following tasks.
[role="_abstract"]
After you deploy {hcp} on {ibm-power-title}, you can manage a hosted cluster.

include::modules/hcp-ibm-power-infraenv.adoc[leveloffset=+1]

Expand Down
3 changes: 2 additions & 1 deletion modules/hcp-ibm-power-add-agents.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,12 @@
[id="hcp-ibm-power-add-agents_{context}"]
= Adding {ibm-power-title} agents to the InfraEnv resource

[role="_abstract"]
You can add agents by manually configuring the machine to start with the live ISO.

.Procedure

. Download the live ISO and use it to start a bare metal or a virtual machine (VM) host. You can find the URL for the live ISO in the `status.isoDownloadURL` field, in the `InfraEnv` resource. At startup, the host communicates with the Assisted Service and registers as an agent in the same namespace as the `InfraEnv` resource.
. Download the live ISO and use it to start a bare metal or a virtual machine (VM) host. You can find the URL for the live ISO in the `status.isoDownloadURL` field in the `InfraEnv` resource. At startup, the host communicates with the Assisted Service and registers as an agent in the same namespace as the `InfraEnv` resource.

. To list the agents and some of their properties, enter the following command:
+
Expand Down
17 changes: 9 additions & 8 deletions modules/hcp-ibm-power-infraenv.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,8 @@
[id="hcp-ibm-power-infraenv_{context}"]
= Creating an InfraEnv resource for {hcp} on {ibm-power-title}

An `InfraEnv` is a environment where hosts that are starting the live ISO can join as agents. In this case, the agents are created in the same namespace as your hosted control plane.
[role="_abstract"]
An `InfraEnv` resource is a environment where hosts that are starting the live ISO can join as agents. In this case, the agents are created in the same namespace as your hosted control plane.

You can create an `InfraEnv` resource for {hcp} on 64-bit x86 bare metal for {ibm-power-title} compute nodes.

Expand All @@ -19,18 +20,18 @@ You can create an `InfraEnv` resource for {hcp} on 64-bit x86 bare metal for {ib
apiVersion: agent-install.openshift.io/v1beta1
kind: InfraEnv
metadata:
name: <hosted_cluster_name> \// <1>
namespace: <hosted_control_plane_namespace> \// <2>
name: <hosted_cluster_name>
namespace: <hosted_control_plane_namespace>
spec:
cpuArchitecture: ppc64le
pullSecretRef:
name: pull-secret
sshAuthorizedKey: <path_to_ssh_public_key> <3>
sshAuthorizedKey: <path_to_ssh_public_key>
----
<1> Replace `<hosted_cluster_name>` with the name of your hosted cluster.
<2> Replace `<hosted_control_plane_namespace>` with the name of the hosted control plane namespace, for example, `clusters-hosted`.
<3> Replace `<path_to_ssh_public_key>` with the path to your SSH public key. The default file path is `~/.ssh/id_rsa.pub`.

+
* `metadata.name` specifies the name of your hosted cluster.
* `metadata.namespace` specifies the name of the hosted control plane namespace, for example, `clusters-hosted`.
* `spec.sshAuthorizedKey` specifies the path to your SSH public key. The default file path is `~/.ssh/id_rsa.pub`.

. Save the file as `infraenv-config.yaml`.

Expand Down
5 changes: 3 additions & 2 deletions modules/hcp-ibm-power-scale-np.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@
[id="hcp-ibm-power-scale-np_{context}"]
= Scaling the NodePool object for a hosted cluster on {ibm-power-title}

[role="_abstract"]
The `NodePool` object is created when you create a hosted cluster. By scaling the `NodePool` object, you can add more compute nodes to {hcp}.

.Procedure
Expand All @@ -17,7 +18,7 @@ The `NodePool` object is created when you create a hosted cluster. By scaling th
$ oc -n <hosted_cluster_namespace> scale nodepool <nodepool_name> --replicas 2
----
+
The Cluster API agent provider randomly picks two agents that are then assigned to the hosted cluster. Those agents go through different states and finally join the hosted cluster as {product-title} nodes. The agents pass through the transition phases in the following order:
The Cluster API agent provider randomly picks two agents that are then assigned to the hosted cluster. Those agents go through different states and finally join the hosted cluster as {product-title} nodes. The agents pass through the phases in the following order:

* `binding`
* `discovering`
Expand All @@ -41,7 +42,7 @@ BMH: Agent: 50c23cda-cedc-9bbd-bcf1-9b3a5c75804d State: known-unbound
BMH: Agent: 5e498cd3-542c-e54f-0c58-ed43e28b568a State: insufficient
----

. Run the following command to see the transition phases:
. Run the following command to see the phases:
+
[source,terminal]
----
Expand Down