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
* See xref:../../scalability_and_performance/ibm-z-recommended-host-practices.adoc#ibm-z-recommended-host-practices[Recommended host practices for IBM Z & LinuxONE environments].
43
+
* xref:../../scalability_and_performance/ibm-z-recommended-host-practices.adoc#ibm-z-recommended-host-practices[Recommended host practices for IBM Z & LinuxONE environments]
* See link:http://public.dhe.ibm.com/software/dw/linux390/perf/zvm_hpav00.pdf[Scaling HyperPAV alias devices on Linux guests on z/VM] for performance optimization.
46
46
47
-
* See xref:../../scalability_and_performance/ibm-z-recommended-host-practices.adoc#ibm-z-recommended-host-practices[Recommended host practices for IBM Z & LinuxONE environments].
47
+
* See link:https://www.vm.ibm.com/library/presentations/lparperf.pdf[Topics in LPAR performance] for LPAR weight management and entitlements.
48
+
49
+
* xref:../../scalability_and_performance/ibm-z-recommended-host-practices.adoc#ibm-z-recommended-host-practices[Recommended host practices for IBM Z & LinuxONE environments]
* See xref:../../scalability_and_performance/ibm-z-recommended-host-practices.adoc#ibm-z-recommended-host-practices[Recommended host practices for IBM Z & LinuxONE environments].
52
+
* xref:../../scalability_and_performance/ibm-z-recommended-host-practices.adoc#ibm-z-recommended-host-practices[Recommended host practices for IBM Z & LinuxONE environments]
* See link:http://public.dhe.ibm.com/software/dw/linux390/perf/zvm_hpav00.pdf[Scaling HyperPAV alias devices on Linux guests on z/VM] for performance optimization.
54
54
55
-
* See xref:../../scalability_and_performance/ibm-z-recommended-host-practices.adoc#ibm-z-recommended-host-practices[Recommended host practices for IBM Z & LinuxONE environments].
55
+
* See link:https://www.vm.ibm.com/library/presentations/lparperf.pdf[Topics in LPAR performance] for LPAR weight management and entitlements.
56
+
57
+
* xref:../../scalability_and_performance/ibm-z-recommended-host-practices.adoc#ibm-z-recommended-host-practices[Recommended host practices for IBM Z & LinuxONE environments]
Copy file name to clipboardExpand all lines: modules/installation-requirements-user-infra-ibm-z-kvm.adoc
+18-7Lines changed: 18 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,8 +73,18 @@ You can install {product-title} version {product-version} on the following IBM h
73
73
[discrete]
74
74
=== Hardware requirements
75
75
76
-
* 1 LPAR with 6 IFLs that supports SMT2
77
-
* 1 OSA or RoCE network adapter
76
+
* The equivalent of 6 IFLs, which are SMT2 enabled, for each cluster.
77
+
* At least one network connection to both connect to the `LoadBalancer` service and to serve data for traffic outside the cluster.
78
+
79
+
[NOTE]
80
+
====
81
+
You can use dedicated or shared IFLs to assign sufficient compute resources. Resource sharing is one of the key strengths of IBM Z. However, you must adjust capacity correctly on each hypervisor layer and ensure sufficient resources for every {product-title} cluster.
82
+
====
83
+
84
+
[IMPORTANT]
85
+
====
86
+
Since the overall performance of the cluster can be impacted, the LPARs that are used to setup the {product-title} clusters must provide sufficient compute capacity. In this context, LPAR weight management, entitlements, and CPU shares on the hypervisor level play an important role.
87
+
====
78
88
79
89
[discrete]
80
90
=== Operating system requirements
@@ -134,8 +144,8 @@ Each cluster virtual machine must meet the following minimum requirements:
134
144
[discrete]
135
145
=== Hardware requirements
136
146
137
-
* 3 LPARs with 6 IFLs each that support SMT2
138
-
* 1 or 2 OSA or RoCE network adapters, or both
147
+
* 3 LPARS that each have the equivalent of 6 IFLs, which are SMT2 enabled, for each cluster.
148
+
* Two network connections to connect to both connect to the `LoadBalancer` service and to serve data for traffic outside the cluster.
139
149
140
150
[discrete]
141
151
=== Operating system requirements
@@ -144,9 +154,10 @@ Each cluster virtual machine must meet the following minimum requirements:
144
154
145
155
On your {op-system-base} KVM host, set up:
146
156
147
-
* 3 guest virtual machines for {product-title} control plane machines, distributed across the {op-system-base} KVM host machines
148
-
* At least 6 guest virtual machines for {product-title} compute machines, distributed across the {op-system-base} KVM host machines
149
-
* 1 guest virtual machine for the temporary {product-title} bootstrap machine
157
+
* 3 guest virtual machines for {product-title} control plane machines, distributed across the {op-system-base} KVM host machines.
158
+
* At least 6 guest virtual machines for {product-title} compute machines, distributed across the {op-system-base} KVM host machines.
159
+
* 1 guest virtual machine for the temporary {product-title} bootstrap machine.
160
+
* To ensure the availability of integral components in an overcommitted environment, increase the priority of the control plane by using `cpu_shares`. Do the same for infrastructure nodes, if they exist. See link:https://www.ibm.com/docs/en/linux-on-systems?topic=domain-schedinfo[schedinfo] in IBM Documentation.
You can install {product-title} version {product-version} on the following IBM hardware:
220
220
221
-
* IBM Z, versions 13, 14, or 15
221
+
* IBM z15 (all models), IBM z14 (all models), IBM z13, and IBM z13s
222
222
* LinuxONE, any version
223
223
224
224
[discrete]
225
225
=== Hardware requirements
226
226
227
-
* 1 LPAR with 6 IFLs that supports SMT2
228
-
* 1 OSA or RoCE network adapter
227
+
* The equivalent of 6 IFLs, which are SMT2 enabled, for each cluster.
228
+
* At least one network connection to both connect to the `LoadBalancer` service and to serve data for traffic outside the cluster.
229
+
230
+
[NOTE]
231
+
====
232
+
You can use dedicated or shared IFLs to assign sufficient compute resources. Resource sharing is one of the key strengths of IBM Z. However, you must adjust capacity correctly on each hypervisor layer and ensure sufficient resources for every {product-title} cluster.
233
+
====
234
+
235
+
[IMPORTANT]
236
+
====
237
+
Since the overall performance of the cluster can be impacted, the LPARs that are used to setup the {product-title} clusters must provide sufficient compute capacity. In this context, LPAR weight management, entitlements, and CPU shares on the hypervisor level play an important role.
238
+
====
229
239
230
240
[discrete]
231
241
=== Operating system requirements
@@ -260,14 +270,14 @@ To install on IBM Z under z/VM, you require a single z/VM virtual NIC in layer 2
260
270
* 16 GB for the temporary {product-title} bootstrap machine
* Hipersockets, which are attached to a node either directly as a device or by bridging with one z/VM VSWITCH to be transparent to the z/VM guest. To directly connect Hipersockets to a node, you must set up a gateway to the external network via a {op-system-base} 8 guest to bridge to the Hipersockets network.
278
+
* 3 LPARS that each have the equivalent of 6 IFLs, which are SMT2 enabled, for each cluster.
279
+
* Two network connections to connect to both connect to the `LoadBalancer` service and to serve data for traffic outside the cluster.
280
+
* HiperSockets, which are attached to a node either directly as a device or by bridging with one z/VM VSWITCH to be transparent to the z/VM guest. To directly connect HiperSockets to a node, you must set up a gateway to the external network via a {op-system-base} 8 guest to bridge to the HiperSockets network.
271
281
272
282
[discrete]
273
283
=== Operating system requirements
@@ -276,10 +286,10 @@ To install on IBM Z under z/VM, you require a single z/VM virtual NIC in layer 2
276
286
277
287
On your z/VM instances, set up:
278
288
279
-
* 3 guest virtual machines for {product-title} control plane machines, one per z/VM instance
280
-
* At least 6 guest virtual machines for {product-title} compute machines, distributed across the z/VM instances
281
-
* 1 guest virtual machine for the temporary {product-title} bootstrap machine
282
-
* To ensure the availability of integral components in an overcommitted environment, increase the priority of the control plane using the CP command `SET SHARE`. Do the same for infrastructure plane machines if they exist. See link:https://www.ibm.com/docs/en/zvm/7.1?topic=commands-set-share[SET SHARE] in IBM Documentation.
289
+
* 3 guest virtual machines for {product-title} control plane machines, one per z/VM instance.
290
+
* At least 6 guest virtual machines for {product-title} compute machines, distributed across the z/VM instances.
291
+
* 1 guest virtual machine for the temporary {product-title} bootstrap machine.
292
+
* To ensure the availability of integral components in an overcommitted environment, increase the priority of the control plane by using the CP command `SET SHARE`. Do the same for infrastructure nodes, if they exist. See link:https://www.ibm.com/docs/en/zvm/7.1?topic=commands-set-share[SET SHARE] in IBM Documentation.
0 commit comments