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: hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc
+6-17Lines changed: 6 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,13 @@
1
1
:_mod-docs-content-type: ASSEMBLY
2
-
[id="hcp-deploy-ibmz"]
3
2
include::_attributes/common-attributes.adoc[]
3
+
[id="hcp-deploy-ibmz"]
4
4
= Deploying {hcp} on {ibm-z-title}
5
5
:context: hcp-deploy-ibmz
6
6
7
7
toc::[]
8
8
9
-
You can deploy {hcp} by configuring a cluster to function as a management cluster. The management cluster is the {product-title} cluster where the control planes are hosted. The management cluster is also known as the _hosting_ cluster.
9
+
[role="_abstract"]
10
+
You can deploy {hcp} on {ibm-z-title} by configuring a cluster to function as a management cluster. The management cluster is the {product-title} cluster where the control planes are hosted. The management cluster is also known as the _hosting_ cluster.
== Creating a hosted cluster on bare metal for {ibm-z-title}
42
-
43
-
You can create a hosted cluster or import one. When the Assisted Installer is enabled as an add-on to {mce-short} and you create a hosted cluster with the Agent platform, the HyperShift Operator installs the Agent Cluster API provider in the hosted control plane namespace.
== Adding {ibm-z-title} agents to the InfraEnv resource
57
-
58
-
To attach compute nodes to a hosted control plane, create agents that help you to scale the node pool. Adding agents in an {ibm-z-title} environment requires additional steps, which are described in detail in this section.
59
-
60
-
Unless stated otherwise, these procedures apply to both z/VM and RHEL KVM installations on {ibm-z-title} and {ibm-linuxone-title}.
The API server for the hosted cluster is exposed as a `NodePort` service. A DNS entry must exist for the `api.<hosted_cluster_name>.<base_domain>` that points to the destination where the API server is reachable.
10
11
11
12
The DNS entry can be as simple as a record that points to one of the nodes in the managed cluster that is running the hosted control plane.
@@ -29,15 +30,15 @@ $ TTL 900
29
30
IN NS bastion.example.krnl.es.com.
30
31
;
31
32
;
32
-
api IN A 1xx.2x.2xx.1xx <1>
33
+
api IN A 1xx.2x.2xx.1xx
33
34
api-int IN A 1xx.2x.2xx.1xx
34
35
;
35
36
;
36
37
*.apps IN A 1xx.2x.2xx.1xx
37
38
;
38
39
;EOF
39
40
----
40
-
<1> The record refers to the IP address of the API load balancer that handles ingress and egress traffic for {hcp}.
41
+
The`api` record refers to the IP address of the API load balancer that handles ingress and egress traffic for {hcp}.
41
42
42
43
For {ibm-title} z/VM, add IP addresses that correspond to the IP address of the agent.
Copy file name to clipboardExpand all lines: modules/hcp-ibm-z-infra-reqs.adoc
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,10 +6,11 @@
6
6
[id="hcp-ibm-z-infra-reqs_{context}"]
7
7
= {ibm-z-title} infrastructure requirements
8
8
9
-
The Agent platform does not create any infrastructure, but requires the following resources for infrastructure:
9
+
[role="_abstract"]
10
+
The Agent platform does not create any infrastructure, but requires several resources for infrastructure.
10
11
11
12
* Agents: An _Agent_ represents a host that is booted with a discovery image, or PXE image and is ready to be provisioned as an {product-title} node.
12
13
13
14
* DNS: The API and Ingress endpoints must be routable.
14
15
15
-
The {hcp} feature is enabled by default. If you disabled the feature and want to manually enable it, or if you need to disable the feature, see _Enabling or disabling the {hcp} feature_.
16
+
The {hcp} feature is enabled by default. If you disabled the feature and want to manually enable it, or if you need to disable the feature, see "Enabling or disabling the {hcp}feature".
Copy file name to clipboardExpand all lines: modules/hcp-ibm-z-infraenv.adoc
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,8 @@
6
6
[id="hcp-ibm-z-infraenv_{context}"]
7
7
= Creating an InfraEnv resource for {hcp} on {ibm-z-title}
8
8
9
-
An `InfraEnv` is an environment where hosts that are booted with PXE images can join as agents. In this case, the agents are created in the same namespace as your hosted control plane.
9
+
[role="_abstract"]
10
+
Before you can create a hosted cluster, you need an `InfraEnv` resource, which is the environment where hosts that are booted with PXE images can join as agents. In this case, the agents are created in the same namespace as your hosted control plane.
Copy file name to clipboardExpand all lines: modules/hcp-ibm-z-kvm-agents.adoc
+25-18Lines changed: 25 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,13 @@
6
6
[id="hcp-ibm-z-kvm-agents_{context}"]
7
7
= Adding {ibm-z-title} KVM as agents
8
8
9
+
[role="_abstract"]
10
+
To attach compute nodes to a hosted control plane, create agents that help you to scale the node pool.
11
+
12
+
Adding agents in an {ibm-z-title} environment requires additional steps, which are described in detail in this section.
13
+
14
+
Unless stated otherwise, this procedure applies to both z/VM and RHEL KVM installations on {ibm-z-title} and {ibm-linuxone-title}.
15
+
9
16
For {ibm-z-title} with KVM, run the following command to start your {ibm-z-title} environment with the downloaded PXE images from the `InfraEnv` resource. After the Agents are created, the host communicates with the Assisted Service and registers in the same namespace as the `InfraEnv` resource on the management cluster.
10
17
11
18
.Procedure
@@ -15,46 +22,46 @@ For {ibm-z-title} with KVM, run the following command to start your {ibm-z-title
<1> For the `coreos.live.rootfs_url` artifact, specify the matching `rootfs` artifact for the `kernel` and `initramfs` that you are starting. Only HTTP and HTTPS protocols are supported.
32
-
<2> For the `ip` parameter, manually assign the IP address, as described in _Installing a cluster with z/VM on {ibm-z-title} and {ibm-linuxone-title}_.
33
-
<3> For installations on DASD-type disks, use `rd.dasd` to specify the DASD where {op-system-first} is to be installed. For installations on FCP-type disks, use `rd.zfcp=<adapter>,<wwpn>,<lun>` to specify the FCP disk where {op-system} is to be installed.
34
-
<4> Specify this parameter when you use an Open Systems Adapter (OSA) or HiperSockets.
38
+
where:
39
+
+
40
+
`coreos.live.rootfs_url`:: For the `coreos.live.rootfs_url` artifact, specify the matching `rootfs` artifact for the `kernel` and `initramfs` that you are starting. Only HTTP and HTTPS protocols are supported.
41
+
`ip`:: For the `ip` parameter, manually assign the IP address, as described in "Installing a cluster with z/VM on {ibm-z-title} and {ibm-linuxone-title}".
42
+
`rd`:: For installations on DASD-type disks, use `rd.dasd` to specify the DASD where {op-system-first} is to be installed. For installations on FCP-type disks, use `rd.zfcp=<adapter>,<wwpn>,<lun>` to specify the FCP disk where {op-system} is to be installed.
43
+
`ai.ip_cfg_override`:: Specify this parameter when you use an Open Systems Adapter (OSA) or HiperSockets.
35
44
36
45
. Download the `.ins` and `initrd.img.addrsize` files from the `InfraEnv` resource.
Copy file name to clipboardExpand all lines: modules/hcp-ibm-z-prereqs.adoc
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,9 @@
6
6
[id="hcp-ibm-z-prereqs_{context}"]
7
7
= Prerequisites to configure {hcp} on {ibm-z-title}
8
8
9
+
[role="_abstract"]
10
+
Ensure you meet the prerequisites to configure {hcp} on {ibm-z-title}.
11
+
9
12
* The {mce} version 2.7 or later must be installed on an {product-title} cluster. You can install {mce-short} as an Operator from the {product-title} OperatorHub.
10
13
11
14
* The {mce-short} must have at least one managed {product-title} cluster. The `local-cluster` is automatically imported in {mce-short} 2.7 and later. For more information about the `local-cluster`, see _Advanced configuration_ in the Red{nbsp}Hat Advanced Cluster Management documentation. You can check the status of your hub cluster by running the following command:
@@ -17,9 +20,9 @@ $ oc get managedclusters local-cluster
17
20
18
21
* You need a hosting cluster with at least three worker nodes to run the HyperShift Operator.
19
22
20
-
* You need to enable the central infrastructure management service. For more information, see _Enabling the central infrastructure management service_.
23
+
* You need to enable the central infrastructure management service. For more information, see "Enabling the central infrastructure management service".
21
24
22
-
* You need to install the hosted control plane command-line interface. For more information, see _Installing the hosted control plane command-line interface_.
25
+
* You need to install the hosted control plane command-line interface. For more information, see "Installing the hosted control plane command-line interface".
Copy file name to clipboardExpand all lines: modules/hcp-ibm-z-scale-np.adoc
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,7 @@
6
6
[id="hcp-ibm-z-scale-np_{context}"]
7
7
= Scaling the NodePool object for a hosted cluster on {ibm-z-title}
8
8
9
+
[role="_abstract"]
9
10
The `NodePool` object is created when you create a hosted cluster. By scaling the `NodePool` object, you can add more compute nodes to the hosted control plane.
10
11
11
12
When you scale up a node pool, a machine is created. The Cluster API provider finds an Agent that is approved, is passing validations, is not currently in use, and meets the requirements that are specified in the node pool specification. You can monitor the installation of an Agent by checking its status and conditions.
$ oc --kubeconfig <hosted_cluster_name>.kubeconfig get clusteroperators
123
124
----
124
-
125
+
+
125
126
For each component of your cluster, the output shows the following cluster operator statuses: `NAME`, `VERSION`, `AVAILABLE`, `PROGRESSING`, `DEGRADED`, `SINCE`, and `MESSAGE`.
126
-
127
-
For an output example, see _Initial Operator configuration_.
127
+
+
128
+
For an output example, see "Initial Operator configuration".
Copy file name to clipboardExpand all lines: modules/hcp-ibm-z-zvm-agents.adoc
+16-13Lines changed: 16 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,7 @@
6
6
[id="hcp-ibm-z-zvm-agents_{context}"]
7
7
= Adding {ibm-title} z/VM as agents
8
8
9
+
[role="_abstract"]
9
10
If you want to use a static IP for z/VM guest, you must configure the `NMStateConfig` attribute for the z/VM agent so that the IP parameter persists in the second start.
10
11
11
12
Complete the following steps to start your {ibm-z-title} environment with the downloaded PXE images from the `InfraEnv` resource. After the Agents are created, the host communicates with the Assisted Service and registers in the same namespace as the `InfraEnv` resource on the management cluster.
@@ -14,24 +15,26 @@ Complete the following steps to start your {ibm-z-title} environment with the do
14
15
15
16
. Update the parameter file to add the `rootfs_url`, `network_adaptor` and `disk_type` values.
<1> For the `coreos.live.rootfs_url` artifact, specify the matching `rootfs` artifact for the `kernel` and `initramfs` that you are starting. Only HTTP and HTTPS protocols are supported.
33
-
<2> For the `ip` parameter, manually assign the IP address, as described in _Installing a cluster with z/VM on {ibm-z-title} and {ibm-linuxone-title}_.
34
-
<3> For installations on DASD-type disks, use `rd.dasd` to specify the DASD where Red Hat Enterprise Linux CoreOS (RHCOS) is to be installed. For installations on FCP-type disks, use `rd.zfcp=<adapter>,<wwpn>,<lun>` to specify the FCP disk where RHCOS is to be installed.
32
+
+
33
+
where:
34
+
+
35
+
`coreos.live.rootfs_url`:: For the `coreos.live.rootfs_url` artifact, specify the matching `rootfs` artifact for the `kernel` and `initramfs` that you are starting. Only HTTP and HTTPS protocols are supported.
36
+
`ip`:: For the `ip` parameter, manually assign the IP address, as described in "Installing a cluster with z/VM on {ibm-z-title} and {ibm-linuxone-title}".
37
+
`rd`:: For installations on DASD-type disks, use `rd.dasd` to specify the DASD where Red Hat Enterprise Linux CoreOS (RHCOS) is to be installed. For installations on FCP-type disks, use `rd.zfcp=<adapter>,<wwpn>,<lun>` to specify the FCP disk where RHCOS is to be installed.
0 commit comments