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
In {product-title} version {product-version}, you can install a cluster in
11
-
a logical partition (LPAR) on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision.
10
+
In {product-title} version {product-version}, you can install a cluster in a logical partition (LPAR) on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision.
* See link:https://www.ibm.com/docs/en/systems-hardware/zsystems/3932-A02?topic=library-prsm-planning-guide[Processors Resource/Systems Manager Planning Guide] in {ibm-name} Documentation for PR/SM mode considerations.
* xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service]
* See xref:../../support/remote_health_monitoring/about-remote-health-monitoring.adoc#about-remote-health-monitoring[About remote health monitoring] for more information about the Telemetry service
144
139
145
140
* link:https://access.redhat.com/solutions/4387261[How to generate SOSREPORT within OpenShift4 nodes without SSH].
146
141
147
-
[id="next-steps_ibmz-lpar"]
142
+
[id="next-steps_installing-ibm-z-lpar"]
148
143
== Next steps
149
144
150
145
* xref:../../post_installation_configuration/machine-configuration-tasks.adoc#rhcos-enabling-multipath_post-install-machine-configuration-tasks[Enabling multipathing with kernel arguments on {op-system}].
In {product-title} version {product-version}, you can install a cluster in a logical partition (LPAR) on
11
-
{ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision in a restricted network.
10
+
In {product-title} version {product-version}, you can install a cluster in a logical partition (LPAR) on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision in a restricted network.
* See link:https://www.ibm.com/docs/en/systems-hardware/zsystems/3932-A02?topic=library-prsm-planning-guide[Processors Resource/Systems Manager Planning Guide] in {ibm-name} Documentation for PR/SM mode considerations.
67
+
* link:https://www.ibm.com/docs/en/systems-hardware/zsystems/3932-A02?topic=library-prsm-planning-guide[Processors Resource/Systems Manager Planning Guide] in {ibm-name} Documentation for PR/SM mode considerations.
70
68
71
-
* See link:https://www.ibm.com/docs/en/systems-hardware/zsystems/3932-A02?topic=library-dynamic-partition-manager-dpm-guide[IBM Dynamic Partition Manager (DPM) Guide] in {ibm-name} Documentation for DPM mode considerations.
69
+
* link:https://www.ibm.com/docs/en/systems-hardware/zsystems/3932-A02?topic=library-dynamic-partition-manager-dpm-guide[IBM Dynamic Partition Manager (DPM) Guide] in {ibm-name} Documentation for DPM mode considerations.
72
70
73
-
* See link:https://www.vm.ibm.com/library/presentations/lparperf.pdf[Topics in LPAR performance] for LPAR weight management and entitlements.
71
+
* link:https://www.vm.ibm.com/library/presentations/lparperf.pdf[Topics in LPAR performance] for LPAR weight management and entitlements.
74
72
75
73
* xref:../../scalability_and_performance/ibm-z-recommended-host-practices.adoc#ibm-z-recommended-host-practices[Recommended host practices for {ibm-z-name} & {ibm-linuxone-name} environments]
Copy file name to clipboardExpand all lines: installing/installing_ibm_z/preparing-to-install-on-ibm-z.adoc
+8-6Lines changed: 8 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -27,9 +27,11 @@ The {product-title} installation program offers the following methods for deploy
27
27
28
28
* *Interactive*: You can deploy a cluster with the web-based link:https://access.redhat.com/documentation/en-us/assisted_installer_for_openshift_container_platform[{ai-full}]. This method requires no setup for the installer, and is ideal for connected environments like {ibm-z-name}.
29
29
30
-
* *Local Agent-based*: You can deploy a cluster locally with the xref:../../installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.adoc#preparing-to-install-with-agent-based-installer[agent-based installer] for air-gapped or restricted networks. It provides many of the benefits of the {ai-full}, but you must download and configure the link:https://console.redhat.com/openshift/install/ibmz/agent-based[agent-based installer] first. Configuration is done with a command line interface (CLI). This approach is ideal for air-gapped or restricted networks.
30
+
* *Local Agent-based*: You can deploy a cluster locally with the xref:../../installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.adoc#preparing-to-install-with-agent-based-installer[Agent-based Installer]. It provides many of the benefits of the {ai-full}, but you must download and configure the link:https://console.redhat.com/openshift/install/ibmz/agent-based[Agent-based Installer] first. Configuration is done with a command line interface (CLI).
31
+
// with 4.15 only connected for IBM Z. I will readd this sentence once air-gaped works: This approach is ideal for air-gapped or restricted networks.
31
32
//agent-based link for IBM Z not available yet needs to be verified shortly before GA
32
-
* *Full control*: You can deploy a cluster on xref:../../installing/installing_ibm_z/installing-ibm-z.adoc#installing-ibm-z[infrastructure that you prepare and maintain], which provides maximum customizability. You can deploy clusters with both connected or air-gapped or restricted networks.
33
+
34
+
* *Full control*: You can deploy a cluster on xref:../../installing/installing_ibm_z/installing-ibm-z.adoc#installing-ibm-z[infrastructure that you prepare and maintain], which provides maximum customizability. You can deploy clusters in connected or disconnected environments.
33
35
34
36
.{ibm-z-name} installation options
35
37
[cols="4,1,1,1,1",options="header"]
@@ -73,7 +75,7 @@ The {product-title} installation program offers the following methods for deploy
73
75
|
74
76
|===
75
77
76
-
See the xref:../../architecture/architecture-installation.adoc#installation-process_architecture-installation[Installation process] for more information about the installation processes.
78
+
For more information about the installation process, see the xref:../../architecture/architecture-installation.adoc#installation-process_architecture-installation[Installation process].
77
79
78
80
=== User-provisioned infrastructure installation of {product-title} on {ibm-z-title}
79
81
@@ -86,12 +88,12 @@ The steps for performing a user-provisioned infrastructure installation are prov
86
88
87
89
* **xref:../../installing/installing_ibm_z/installing-ibm-z.adoc#installing-ibm-z[Installing a cluster with z/VM on {ibm-z-name} and {ibm-linuxone-name}]**: You can install {product-title} with z/VM on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision.
88
90
89
-
* **xref:../../installing/installing_ibm_z/installing-restricted-networks-ibm-z.adoc#installing-restricted-networks-ibm-z[Installing a cluster with z/VM on {ibm-z-name} and {ibm-linuxone-name} in a restricted network]**: You can install {product-title} with z/VM on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision in a restricted or disconnected network, by using an internal mirror of the installation release content. You can use this method to install a cluster that does not require an active internet connection to obtain the software components. You can also use this installation method to ensure that your clusters only use container images that satisfy your organizational controls on external content.
91
+
* **xref:../../installing/installing_ibm_z/installing-restricted-networks-ibm-z.adoc#installing-restricted-networks-ibm-z[Installing a cluster with z/VM on {ibm-z-name} and {ibm-linuxone-name} in a restricted network]**: You can install {product-title} with z/VM on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision in a restricted or disconnected network by using an internal mirror of the installation release content. You can use this method to install a cluster that does not require an active internet connection to obtain the software components. You can also use this installation method to ensure that your clusters only use container images that satisfy your organizational controls on external content.
90
92
91
93
* **xref:../../installing/installing_ibm_z/installing-ibm-z-kvm.adoc#installing-ibm-z-kvm[Installing a cluster with RHEL KVM on {ibm-z-name} and {ibm-linuxone-name}]**: You can install {product-title} with KVM on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision.
92
94
93
-
* **xref:../../installing/installing_ibm_z/installing-restricted-networks-ibm-z-kvm.adoc#installing-restricted-networks-ibm-z-kvm[Installing a cluster with {op-system-base} KVM on {ibm-z-name} and {ibm-linuxone-name} in a restricted network]**: You can install {product-title} with {op-system-base} KVM on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision in a restricted or disconnected network, by using an internal mirror of the installation release content. You can use this method to install a cluster that does not require an active internet connection to obtain the software components. You can also use this installation method to ensure that your clusters only use container images that satisfy your organizational controls on external content.
95
+
* **xref:../../installing/installing_ibm_z/installing-restricted-networks-ibm-z-kvm.adoc#installing-restricted-networks-ibm-z-kvm[Installing a cluster with {op-system-base} KVM on {ibm-z-name} and {ibm-linuxone-name} in a restricted network]**: You can install {product-title} with {op-system-base} KVM on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision in a restricted or disconnected network by using an internal mirror of the installation release content. You can use this method to install a cluster that does not require an active internet connection to obtain the software components. You can also use this installation method to ensure that your clusters only use container images that satisfy your organizational controls on external content.
94
96
95
97
* **xref:../../installing/installing_ibm_z/installing-ibm-z-lpar.adoc#installing-ibm-z-lpar[Installing a cluster in an LPAR on {ibm-z-name} and {ibm-linuxone-name}]**: You can install {product-title} in a logical partition (LPAR) on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision.
96
98
97
-
* **xref:../../installing/installing_ibm_z/installing-restricted-networks-ibm-z-lpar.adoc#installing-restricted-networks-ibm-z-lpar[Installing a cluster in an LPAR on {ibm-z-name} and {ibm-linuxone-name} in a restricted network]**: You can install {product-title} in an LPAR on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision in a restricted or disconnected network, by using an internal mirror of the installation release content. You can use this method to install a cluster that does not require an active internet connection to obtain the software components. You can also use this installation method to ensure that your clusters only use container images that satisfy your organizational controls on external content.
99
+
* **xref:../../installing/installing_ibm_z/installing-restricted-networks-ibm-z-lpar.adoc#installing-restricted-networks-ibm-z-lpar[Installing a cluster in an LPAR on {ibm-z-name} and {ibm-linuxone-name} in a restricted network]**: You can install {product-title} in an LPAR on {ibm-z-name} or {ibm-linuxone-name} infrastructure that you provision in a restricted or disconnected network by using an internal mirror of the installation release content. You can use this method to install a cluster that does not require an active internet connection to obtain the software components. You can also use this installation method to ensure that your clusters only use container images that satisfy your organizational controls on external content.
Copy file name to clipboardExpand all lines: modules/installation-ibm-z-user-infra-machines-iso.adoc
+7-4Lines changed: 7 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -26,9 +26,9 @@ endif::[]
26
26
ifdef::ibm-z[]
27
27
To install {product-title} on {ibm-z-name} infrastructure that you provision, you must install {op-system-first} on z/VM guest virtual machines. When you install {op-system}, you must provide the Ignition config file that was generated by the {product-title} installation program for the type of machine you are installing. If you have configured suitable networking, DNS, and load balancing infrastructure, the {product-title} bootstrap process begins automatically after the {op-system} z/VM guest virtual machines have rebooted.
28
28
endif::ibm-z[]
29
-
ifndef::ibm-z[]
29
+
ifdef::ibm-z-lpar[]
30
30
To install {product-title} on {ibm-z-name} infrastructure that you provision, you must install {op-system-first} in an LPAR. When you install {op-system}, you must provide the Ignition config file that was generated by the {product-title} installation program for the type of machine you are installing. If you have configured suitable networking, DNS, and load balancing infrastructure, the {product-title} bootstrap process begins automatically after the {op-system} guest machines have rebooted.
31
-
endif::ibm-z[]
31
+
endif::ibm-z-lpar[]
32
32
33
33
Complete the following steps to create the machines.
34
34
@@ -156,11 +156,11 @@ $ ipl c
156
156
See link:https://www.ibm.com/docs/en/zvm/latest?topic=commands-ipl[IPL] in IBM Documentation.
157
157
+
158
158
endif::ibm-z[]
159
-
ifndef::ibm-z[]
159
+
ifdef::ibm-z-lpar[]
160
160
. Transfer the initramfs, kernel, parameter files, and {op-system} images to the LPAR, for example with FTP. For details about how to transfer the files with FTP and boot, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/performing_a_standard_rhel_8_installation/installing-in-an-lpar_installing-rhel[Installing in an LPAR].
161
161
162
162
. Boot the machine
163
-
endif::ibm-z[]
163
+
endif::ibm-z-lpar[]
164
164
165
165
. Repeat this procedure for the other machines in the cluster.
Copy file name to clipboardExpand all lines: modules/installation-load-balancing-user-infra.adoc
-1Lines changed: 0 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,6 @@ Before you install {product-title}, you must provision the API and application I
26
26
endif::user-managed-lb[]
27
27
28
28
ifdef::user-managed-lb[]
29
-
30
29
Before you install {product-title}, you can provision your own API and application ingress load balancing infrastructure to use in place of the default, internal load balancing solution. In production scenarios, you can deploy the API and application Ingress load balancers separately so that you can scale the load balancer infrastructure for each in isolation.
To install on {ibm-z-name} under z/VM, you require a single z/VM virtual NIC in layer 2 mode. You also need:
76
76
77
-
* A direct-attached OSA or RoCE network adapter
78
-
* A z/VM VSwitch set up. For a preferred setup, use OSA link aggregation.
77
+
* A direct-attached OSA or RoCE network adapter
78
+
* A z/VM VSwitch set up. For a preferred setup, use OSA link aggregation.
79
79
endif::ibm-z[]
80
-
ifndef::ibm-z[]
80
+
ifdef::ibm-z-lpar[]
81
81
To install on {ibm-z-name} in an LPAR, you need:
82
82
83
-
* A direct-attached OSA or RoCE network adapter
84
-
* For a preferred setup, use OSA link aggregation.
85
-
endif::ibm-z[]
83
+
* A direct-attached OSA or RoCE network adapter
84
+
* For a preferred setup, use OSA link aggregation.
85
+
endif::ibm-z-lpar[]
86
86
87
87
[discrete]
88
88
=== Disk storage
@@ -94,10 +94,10 @@ ifdef::ibm-z[]
94
94
* FICON attached disk storage (DASDs). These can be z/VM minidisks, fullpack minidisks, or dedicated DASDs, all of which must be formatted as CDL, which is the default. To reach the minimum required DASD size for {op-system-first} installations, you need extended address volumes (EAV). If available, use HyperPAV to ensure optimal performance.
95
95
* FCP attached disk storage
96
96
endif::ibm-z[]
97
-
ifndef::ibm-z[]
97
+
ifdef::ibm-z-lpar[]
98
98
* FICON attached disk storage (DASDs). This can be dedicated DASDs that must be formatted as CDL, which is the default. To reach the minimum required DASD size for {op-system-first} installations, you need extended address volumes (EAV). If available, use HyperPAV to ensure optimal performance.
0 commit comments