mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
add common attribute for IBM LinuxONE
This commit is contained in:
SNiemann15
committed by
openshift-cherrypick-robot
openshift-cherrypick-robot
parent
a74f72eaa0
commit
0a68d6570f
@@ -139,8 +139,11 @@ endif::[]
|
||||
:SMProductVersion1x: 1.1.18.2
|
||||
//Windows containers
|
||||
:productwinc: Red Hat OpenShift support for Windows Containers
|
||||
// IBM Power
|
||||
:ibmpowerProductName: IBM Power
|
||||
// IBM zSystems
|
||||
:ibmzProductName: IBM Z
|
||||
:ibmzProductName: IBM zSystems
|
||||
:linuxoneProductName: IBM(R) LinuxONE
|
||||
// Red Hat Quay Container Security Operator
|
||||
:rhq-cso: Red Hat Quay Container Security Operator
|
||||
:sno: single-node OpenShift
|
||||
|
||||
@@ -354,25 +354,25 @@ Topics:
|
||||
File: install-ibm-cloud-prerequisites
|
||||
- Name: Installation workflow
|
||||
File: install-ibm-cloud-installation-workflow
|
||||
- Name: Installing with z/VM on IBM Z and LinuxONE
|
||||
- Name: Installing with z/VM on IBM zSystems and IBM LinuxONE
|
||||
Dir: installing_ibm_z
|
||||
Distros: openshift-enterprise
|
||||
Topics:
|
||||
- Name: Preparing to install with z/VM on IBM Z and LinuxONE
|
||||
- Name: Preparing to install with z/VM on IBM zSystems and IBM LinuxONE
|
||||
File: preparing-to-install-on-ibm-z
|
||||
- Name: Installing a cluster with z/VM on IBM Z and LinuxONE
|
||||
- Name: Installing a cluster with z/VM on IBM zSystems and IBM LinuxONE
|
||||
File: installing-ibm-z
|
||||
- Name: Restricted network IBM Z installation with z/VM
|
||||
- Name: Restricted network IBM zSystems installation with z/VM
|
||||
File: installing-restricted-networks-ibm-z
|
||||
- Name: Installing with RHEL KVM on IBM Z and LinuxONE
|
||||
- Name: Installing with RHEL KVM on IBM zSystems and IBM LinuxONE
|
||||
Dir: installing_ibm_z
|
||||
Distros: openshift-enterprise
|
||||
Topics:
|
||||
- Name: Preparing to install with RHEL KVM on IBM Z and LinuxONE
|
||||
- Name: Preparing to install with RHEL KVM on IBM zSystems and IBM LinuxONE
|
||||
File: preparing-to-install-on-ibm-z-kvm
|
||||
- Name: Installing a cluster with RHEL KVM on IBM Z and LinuxONE
|
||||
- Name: Installing a cluster with RHEL KVM on IBM zSystems and IBM LinuxONE
|
||||
File: installing-ibm-z-kvm
|
||||
- Name: Restricted network IBM Z installation with RHEL KVM
|
||||
- Name: Restricted network IBM zSystems installation with RHEL KVM
|
||||
File: installing-restricted-networks-ibm-z-kvm
|
||||
- Name: Installing on IBM Power
|
||||
Dir: installing_ibm_power
|
||||
@@ -549,7 +549,7 @@ Topics:
|
||||
- Name: Enabling cluster capabilities
|
||||
File: enabling-cluster-capabilities
|
||||
Distros: openshift-origin,openshift-enterprise
|
||||
- Name: Configuring additional devices in an IBM Z or LinuxONE environment
|
||||
- Name: Configuring additional devices in an IBM zSystems or IBM LinuxONE environment
|
||||
File: ibmz-post-install
|
||||
- Name: Red Hat Enterprise Linux CoreOS image layering
|
||||
File: coreos-layering
|
||||
@@ -1956,7 +1956,7 @@ Topics:
|
||||
File: installing-sbo
|
||||
- Name: Getting started with service binding
|
||||
File: getting-started-with-service-binding
|
||||
- Name: Getting started with service binding on IBM Power, IBM Z, and LinuxONE
|
||||
- Name: Getting started with service binding on IBM Power, IBM zSystems, and IBM LinuxONE
|
||||
File: getting-started-with-service-binding-ibm-power-ibm-z
|
||||
- Name: Exposing binding data from a service
|
||||
File: exposing-binding-data-from-a-service
|
||||
@@ -2492,7 +2492,7 @@ Topics:
|
||||
- Name: Recommended performance and scalability practices
|
||||
File: recommended-host-practices
|
||||
Distros: openshift-origin,openshift-enterprise
|
||||
- Name: Recommended host practices for IBM Z & LinuxONE environments
|
||||
- Name: Recommended host practices for IBM zSystems & IBM LinuxONE environments
|
||||
File: ibm-z-recommended-host-practices
|
||||
Distros: openshift-enterprise
|
||||
- Name: Using the Node Tuning Operator
|
||||
@@ -3753,7 +3753,7 @@ Topics:
|
||||
- Name: Installing the Serverless Operator
|
||||
File: install-serverless-operator
|
||||
- Name: Installing the Knative CLI
|
||||
File: installing-kn
|
||||
File: installing-kn
|
||||
- Name: Installing Knative Serving
|
||||
File: installing-knative-serving
|
||||
- Name: Installing Knative Eventing
|
||||
@@ -3970,7 +3970,7 @@ Topics:
|
||||
Dir: tuning
|
||||
Topics:
|
||||
- Name: Overriding deployment configurations
|
||||
File: override-config
|
||||
File: override-config
|
||||
- Name: High availability
|
||||
File: serverless-ha
|
||||
- Name: kn-event plugin
|
||||
@@ -4088,12 +4088,12 @@ Topics:
|
||||
Dir: integrations
|
||||
Topics:
|
||||
- Name: Integrating Service Mesh with OpenShift Serverless
|
||||
File: serverless-ossm-setup
|
||||
File: serverless-ossm-setup
|
||||
- Name: Integrating Serverless with the cost management service
|
||||
File: serverless-cost-management-integration
|
||||
- Name: Using NVIDIA GPU resources with serverless applications
|
||||
File: gpu-resources
|
||||
# Removing
|
||||
# Removing
|
||||
- Name: Removing Serverless
|
||||
Dir: removing
|
||||
Topics:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
:_content-type: ASSEMBLY
|
||||
[id="getting-started-with-service-binding-ibm-power-ibm-z"]
|
||||
= Getting started with service binding on IBM Power Systems, IBM Z, and LinuxONE
|
||||
= Getting started with service binding on {ibmpowerProductName}, {ibmzProductName}, and {linuxoneProductName}
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
include::_attributes/servicebinding-document-attributes.adoc[]
|
||||
:context: getting-started-with-service-binding-ibm-power-ibm-z
|
||||
|
||||
@@ -11,7 +11,7 @@ Using {product-title}, you can create, edit, delete, and manage applications usi
|
||||
[id="working-on-a-project"]
|
||||
== Working on a project
|
||||
|
||||
Using projects, you can organize and manage applications in isolation. You can manage the entire project lifecycle, including xref:../applications/projects/working-with-projects.adoc#working-with-projects[creating, viewing, and deleting a project] in {product-title}.
|
||||
Using projects, you can organize and manage applications in isolation. You can manage the entire project lifecycle, including xref:../applications/projects/working-with-projects.adoc#working-with-projects[creating, viewing, and deleting a project] in {product-title}.
|
||||
|
||||
After you create the project, you can xref:../applications/projects/working-with-projects.adoc#odc-providing-project-permissions-using-developer-perspective_projects[grant or revoke access to a project] and xref:../applications/projects/working-with-projects.adoc#odc-customizing-available-cluster-roles-using-developer-perspective_projects[manage cluster roles] for the users using the Developer perspective. You can also xref:../applications/projects/configuring-project-creation.adoc#configuring-project-creation[edit the project configuration resource] while creating a project template that is used for automatic provisioning of new projects.
|
||||
|
||||
@@ -30,19 +30,19 @@ You can also use components that include source or binary code, images, and temp
|
||||
[id="maintaining-application"]
|
||||
=== Maintaining an application
|
||||
|
||||
After you create the application you can use the web console to xref:../applications/odc-monitoring-project-and-application-metrics-using-developer-perspective.adoc#odc-monitoring-project-and-application-metrics-using-developer-perspective[monitor your project or application metrics]. You can also xref:../applications/odc-editing-applications.adoc#odc-editing-applications[edit] or xref:../applications/odc-deleting-applications.adoc#odc-deleting-applications[delete] the application using the web console.
|
||||
When the application is running, not all applications resources are used. As a cluster administrator, you can choose to xref:../applications/idling-applications.adoc#idling-applications[idle these scalable resources] to reduce resource consumption.
|
||||
After you create the application you can use the web console to xref:../applications/odc-monitoring-project-and-application-metrics-using-developer-perspective.adoc#odc-monitoring-project-and-application-metrics-using-developer-perspective[monitor your project or application metrics]. You can also xref:../applications/odc-editing-applications.adoc#odc-editing-applications[edit] or xref:../applications/odc-deleting-applications.adoc#odc-deleting-applications[delete] the application using the web console.
|
||||
When the application is running, not all applications resources are used. As a cluster administrator, you can choose to xref:../applications/idling-applications.adoc#idling-applications[idle these scalable resources] to reduce resource consumption.
|
||||
|
||||
[id="connecting-application"]
|
||||
=== Connecting an application to services
|
||||
|
||||
An application uses backing services to build and connect workloads, which vary according to the service provider. Using the xref:../applications/connecting_applications_to_services/understanding-service-binding-operator.adoc#understanding-service-binding-operator[Service Binding Operator], as a developer, you can bind workloads together with Operator-managed backing services, without any manual procedures to configure the binding connection. You can apply service binding also on xref:../applications/connecting_applications_to_services/getting-started-with-service-binding-ibm-power-ibm-z.adoc#getting-started-with-service-binding-ibm-power-ibm-z[IBM Power Systems, IBM Z, and LinuxONE environments].
|
||||
An application uses backing services to build and connect workloads, which vary according to the service provider. Using the xref:../applications/connecting_applications_to_services/understanding-service-binding-operator.adoc#understanding-service-binding-operator[Service Binding Operator], as a developer, you can bind workloads together with Operator-managed backing services, without any manual procedures to configure the binding connection. You can apply service binding also on xref:../applications/connecting_applications_to_services/getting-started-with-service-binding-ibm-power-ibm-z.adoc#getting-started-with-service-binding-ibm-power-ibm-z[{ibmpowerProductName}, {ibmzProductName}, and {linuxoneProductName} environments].
|
||||
|
||||
[id="deploying-application"]
|
||||
=== Deploying an application
|
||||
You can deploy your application using xref:../applications/deployments/what-deployments-are.adoc#what-deployments-are[`Deployment` or `DeploymentConfig`] objects and xref:../applications/deployments/managing-deployment-processes.adoc#deployment-operations[manage] them from the web console. You can create xref:../applications/deployments/deployment-strategies.adoc#deployment-strategies[deployment strategies] that help reduce downtime during a change or an upgrade to the application.
|
||||
|
||||
You can also use xref:../applications/working_with_helm_charts/understanding-helm.adoc#understanding-helm[Helm], a software package manager that simplifies deployment of applications and services to {product-title} clusters.
|
||||
You can also use xref:../applications/working_with_helm_charts/understanding-helm.adoc#understanding-helm[Helm], a software package manager that simplifies deployment of applications and services to {product-title} clusters.
|
||||
|
||||
[id="redhat-marketplace"]
|
||||
== Using the Red Hat Marketplace
|
||||
|
||||
@@ -24,14 +24,14 @@ You can also find the URL to the latest binaries from the {product-title} web co
|
||||
# curl -L https://mirror.openshift.com/pub/openshift-v4/clients/helm/latest/helm-linux-amd64 -o /usr/local/bin/helm
|
||||
----
|
||||
|
||||
* Linux on IBM Z and LinuxONE (s390x)
|
||||
* Linux on {ibmzProductName} and {linuxoneProductName} (s390x)
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
# curl -L https://mirror.openshift.com/pub/openshift-v4/clients/helm/latest/helm-linux-s390x -o /usr/local/bin/helm
|
||||
----
|
||||
|
||||
* Linux on IBM Power (ppc64le)
|
||||
* Linux on {ibmpowerProductName} (ppc64le)
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
|
||||
@@ -41,7 +41,7 @@ The streaming strategy requires an additional Red Hat subscription for AMQ Strea
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
The streaming deployment strategy is currently unsupported on IBM Z.
|
||||
The streaming deployment strategy is currently unsupported on {ibmzProductName}.
|
||||
====
|
||||
|
||||
[NOTE]
|
||||
|
||||
@@ -29,9 +29,9 @@ endif::openshift-origin[]
|
||||
* {rh-openstack-first}
|
||||
* {rh-virtualization-first}
|
||||
* IBM Cloud VPC
|
||||
* IBM Z and LinuxONE
|
||||
* IBM Z and LinuxONE for {op-system-base-full} KVM
|
||||
* IBM Power
|
||||
* {ibmzProductName} or {linuxoneProductName}
|
||||
* {ibmzProductName} or {linuxoneProductName} for {op-system-base-full} KVM
|
||||
* {ibmpowerProductName}
|
||||
* Nutanix
|
||||
* VMware vSphere
|
||||
* VMware Cloud (VMC) on AWS
|
||||
@@ -65,7 +65,7 @@ You can use the installer-provisioned infrastructure method to create appropriat
|
||||
If you want to reuse extensive cloud infrastructure, you can complete a _user-provisioned infrastructure_ installation. With these installations, you manually deploy the machines that your cluster requires during the installation process. If you perform a user-provisioned infrastructure installation on xref:../installing/installing_aws/installing-aws-user-infra.adoc#installing-aws-user-infra[AWS], xref:../installing/installing_azure/installing-azure-user-infra.adoc#installing-azure-user-infra[Azure], xref:../installing/installing_azure_stack_hub/installing-azure-stack-hub-user-infra.adoc#installing-azure-stack-hub-user-infra[Azure Stack Hub], xref:../installing/installing_gcp/installing-gcp-user-infra.adoc#installing-gcp-user-infra[GCP], or xref:../installing/installing_vmc/installing-vmc-user-infra.adoc#installing-vmc-user-infra[VMC on AWS], you can use the provided templates to help you stand up all of the required components. You can also reuse a shared xref:../installing/installing_gcp/installing-gcp-user-infra-vpc.adoc#installing-gcp-user-infra-vpc[VPC on GCP]. Otherwise, you can use the xref:../installing/installing_platform_agnostic/installing-platform-agnostic.adoc#installing-platform-agnostic[provider-agnostic] installation method to deploy a cluster into other clouds.
|
||||
|
||||
|
||||
You can also complete a user-provisioned infrastructure installation on your existing hardware. If you use xref:../installing/installing_openstack/installing-openstack-user.adoc#installing-openstack-user[{rh-openstack}], xref:../installing/installing_rhv/installing-rhv-user-infra.adoc#installing-rhv-user-infra[{rh-virtualization}], xref:../installing/installing_ibm_z/installing-ibm-z.adoc#installing-ibm-z[IBM Z or LinuxONE], xref:../installing/installing_ibm_z/installing-ibm-z-kvm.adoc#installing-ibm-z-kvm[IBM Z or LinuxONE with {op-system-base} KVM], xref:../installing/installing_ibm_power/installing-ibm-power.adoc#installing-ibm-power[IBM Power], or xref:../installing/installing_vsphere/installing-vsphere.adoc#installing-vsphere[vSphere], use the specific installation instructions to deploy your cluster. If you use other supported hardware, follow the xref:../installing/installing_bare_metal/installing-bare-metal.adoc#installing-bare-metal[bare metal installation] procedure. For some of these platforms, such as xref:../installing/installing_openstack/installing-openstack-user-kuryr.adoc#installing-openstack-user-kuryr[{rh-openstack}], xref:../installing/installing_vsphere/installing-vsphere-network-customizations.adoc#installing-vsphere-network-customizations[vSphere],
|
||||
You can also complete a user-provisioned infrastructure installation on your existing hardware. If you use xref:../installing/installing_openstack/installing-openstack-user.adoc#installing-openstack-user[{rh-openstack}], xref:../installing/installing_rhv/installing-rhv-user-infra.adoc#installing-rhv-user-infra[{rh-virtualization}], xref:../installing/installing_ibm_z/installing-ibm-z.adoc#installing-ibm-z[{ibmzProductName} or {linuxoneProductName}], xref:../installing/installing_ibm_z/installing-ibm-z-kvm.adoc#installing-ibm-z-kvm[{ibmzProductName} and {linuxoneProductName} with {op-system-base} KVM], xref:../installing/installing_ibm_power/installing-ibm-power.adoc#installing-ibm-power[IBM Power], or xref:../installing/installing_vsphere/installing-vsphere.adoc#installing-vsphere[vSphere], use the specific installation instructions to deploy your cluster. If you use other supported hardware, follow the xref:../installing/installing_bare_metal/installing-bare-metal.adoc#installing-bare-metal[bare metal installation] procedure. For some of these platforms, such as xref:../installing/installing_openstack/installing-openstack-user-kuryr.adoc#installing-openstack-user-kuryr[{rh-openstack}], xref:../installing/installing_vsphere/installing-vsphere-network-customizations.adoc#installing-vsphere-network-customizations[vSphere],
|
||||
xref:../installing/installing_vmc/installing-vmc-network-customizations-user-infra.adoc#installing-vmc-network-customizations-user-infra[VMC on AWS], and xref:../installing/installing_bare_metal/installing-bare-metal-network-customizations.adoc#installing-bare-metal-network-customizations[bare metal], you can also customize additional network parameters during installation.
|
||||
|
||||
[id="installing-preparing-security"]
|
||||
@@ -75,7 +75,7 @@ If you use a user-provisioned installation method, you can configure a proxy for
|
||||
|
||||
If you want to prevent your cluster on a public cloud from exposing endpoints externally, you can deploy a private cluster with installer-provisioned infrastructure on xref:../installing/installing_aws/installing-aws-private.adoc#installing-aws-private[AWS], xref:../installing/installing_azure/installing-azure-private.adoc#installing-azure-private[Azure], or xref:../installing/installing_gcp/installing-gcp-private.adoc#installing-gcp-private[GCP].
|
||||
|
||||
If you need to install your cluster that has limited access to the internet, such as a disconnected or restricted network cluster, you can xref:../installing/disconnected_install/installing-mirroring-installation-images.adoc#installing-mirroring-installation-images[mirror the installation packages] and install the cluster from them. Follow detailed instructions for user provisioned infrastructure installations into restricted networks for xref:../installing/installing_aws/installing-restricted-networks-aws.adoc#installing-restricted-networks-aws[AWS], xref:../installing/installing_gcp/installing-restricted-networks-gcp.adoc#installing-restricted-networks-gcp[GCP], xref:../installing/installing_ibm_z/installing-restricted-networks-ibm-z.adoc#installing-restricted-networks-ibm-z[IBM Z or LinuxONE], xref:../installing/installing_ibm_z/installing-restricted-networks-ibm-z-kvm.adoc#installing-restricted-networks-ibm-z-kvm[IBM Z or LinuxONE with {op-system-base} KVM], xref:../installing/installing_ibm_power/installing-restricted-networks-ibm-power.adoc#installing-restricted-networks-ibm-power[IBM Power], xref:../installing/installing_vsphere/installing-restricted-networks-vsphere.adoc#installing-restricted-networks-vsphere[vSphere], xref:../installing/installing_vmc/installing-restricted-networks-vmc-user-infra.adoc#installing-restricted-networks-vmc-user-infra[VMC on AWS], or xref:../installing/installing_bare_metal/installing-restricted-networks-bare-metal.adoc#installing-restricted-networks-bare-metal[bare metal]. You can also install a cluster into a restricted network using installer-provisioned infrastructure by following detailed instructions for xref:../installing/installing_aws/installing-restricted-networks-aws-installer-provisioned.adoc#installing-restricted-networks-aws-installer-provisioned[AWS], xref:../installing/installing_gcp/installing-restricted-networks-gcp-installer-provisioned.adoc#installing-restricted-networks-gcp-installer-provisioned[GCP], xref:../installing/installing_nutanix/installing-restricted-networks-nutanix-installer-provisioned.adoc#installing-restricted-networks-nutanix-installer-provisioned[Nutanix], xref:../installing/installing_vmc/installing-restricted-networks-vmc.adoc#installing-restricted-networks-vmc[VMC on AWS], xref:../installing/installing_openstack/installing-openstack-installer-restricted.adoc#installing-openstack-installer-restricted[{rh-openstack}], xref:../installing/installing_rhv/installing-rhv-restricted-network.adoc#installing-rhv-restricted-network[{rh-virtualization}], and xref:../installing/installing_vsphere/installing-restricted-networks-installer-provisioned-vsphere.adoc#installing-restricted-networks-installer-provisioned-vsphere[vSphere].
|
||||
If you need to install your cluster that has limited access to the internet, such as a disconnected or restricted network cluster, you can xref:../installing/disconnected_install/installing-mirroring-installation-images.adoc#installing-mirroring-installation-images[mirror the installation packages] and install the cluster from them. Follow detailed instructions for user provisioned infrastructure installations into restricted networks for xref:../installing/installing_aws/installing-restricted-networks-aws.adoc#installing-restricted-networks-aws[AWS], xref:../installing/installing_gcp/installing-restricted-networks-gcp.adoc#installing-restricted-networks-gcp[GCP], xref:../installing/installing_ibm_z/installing-restricted-networks-ibm-z.adoc#installing-restricted-networks-ibm-z[{ibmzProductName} or {linuxoneProductName}], xref:../installing/installing_ibm_z/installing-restricted-networks-ibm-z-kvm.adoc#installing-restricted-networks-ibm-z-kvm[{ibmzProductName} or {linuxoneProductName} with {op-system-base} KVM], xref:../installing/installing_ibm_power/installing-restricted-networks-ibm-power.adoc#installing-restricted-networks-ibm-power[IBM Power], xref:../installing/installing_vsphere/installing-restricted-networks-vsphere.adoc#installing-restricted-networks-vsphere[vSphere], xref:../installing/installing_vmc/installing-restricted-networks-vmc-user-infra.adoc#installing-restricted-networks-vmc-user-infra[VMC on AWS], or xref:../installing/installing_bare_metal/installing-restricted-networks-bare-metal.adoc#installing-restricted-networks-bare-metal[bare metal]. You can also install a cluster into a restricted network using installer-provisioned infrastructure by following detailed instructions for xref:../installing/installing_aws/installing-restricted-networks-aws-installer-provisioned.adoc#installing-restricted-networks-aws-installer-provisioned[AWS], xref:../installing/installing_gcp/installing-restricted-networks-gcp-installer-provisioned.adoc#installing-restricted-networks-gcp-installer-provisioned[GCP], xref:../installing/installing_nutanix/installing-restricted-networks-nutanix-installer-provisioned.adoc#installing-restricted-networks-nutanix-installer-provisioned[Nutanix], xref:../installing/installing_vmc/installing-restricted-networks-vmc.adoc#installing-restricted-networks-vmc[VMC on AWS], xref:../installing/installing_openstack/installing-openstack-installer-restricted.adoc#installing-openstack-installer-restricted[{rh-openstack}], xref:../installing/installing_rhv/installing-rhv-restricted-network.adoc#installing-rhv-restricted-network[{rh-virtualization}], and xref:../installing/installing_vsphere/installing-restricted-networks-installer-provisioned-vsphere.adoc#installing-restricted-networks-installer-provisioned-vsphere[vSphere].
|
||||
|
||||
If you need to deploy your cluster to an xref:../installing/installing_aws/installing-aws-government-region.adoc#installing-aws-government-region[AWS GovCloud region], xref:../installing/installing_aws/installing-aws-china.adoc#installing-aws-china-region[AWS China region], or xref:../installing/installing_azure/installing-azure-government-region.adoc#installing-azure-government-region[Azure government region], you can configure those custom regions during an installer-provisioned infrastructure installation.
|
||||
|
||||
@@ -128,7 +128,7 @@ Not all installation options are supported for all platforms, as shown in the fo
|
||||
//This table is for all flavors of OpenShift, except OKD. A separate table is required because OKD does not support multiple AWS architecture types. Trying to maintain one table using conditions, while convenient, is very fragile and prone to publishing errors.
|
||||
ifndef::openshift-origin[]
|
||||
|===
|
||||
||Alibaba |AWS (x86_64) |AWS (arm64) |Azure (x86_64) |Azure (arm64)|Azure Stack Hub |GCP |Nutanix |{rh-openstack} |RHV |Bare metal (x86_64) |Bare metal (arm64) |vSphere |VMC |IBM Cloud VPC |IBM Z |IBM Power
|
||||
||Alibaba |AWS (x86_64) |AWS (arm64) |Azure (x86_64) |Azure (arm64)|Azure Stack Hub |GCP |Nutanix |{rh-openstack} |RHV |Bare metal (x86_64) |Bare metal (arm64) |vSphere |VMC |IBM Cloud VPC |{ibmzProductName} |{ibmpowerProductName}
|
||||
|
||||
|Default
|
||||
|xref:../installing/installing_alibaba/installing-alibaba-default.adoc#installing-alibaba-default[✓]
|
||||
@@ -307,7 +307,7 @@ endif::openshift-origin[]
|
||||
//This table is for OKD only. A separate table is required because OKD does not support multiple AWS architecture types. Trying to maintain one table using conditions, while convenient, is very fragile and prone to publishing errors.
|
||||
ifdef::openshift-origin[]
|
||||
|===
|
||||
||Alibaba |AWS |Azure |Azure Stack Hub |GCP |Nutanix |{rh-openstack} |oVirt |Bare metal |vSphere |VMC |IBM Cloud VPC |IBM Z |IBM Power
|
||||
||Alibaba |AWS |Azure |Azure Stack Hub |GCP |Nutanix |{rh-openstack} |oVirt |Bare metal |vSphere |VMC |IBM Cloud VPC |{ibmzProductName} |{ibmpowerProductName}
|
||||
|
||||
|Default
|
||||
|xref:../installing/installing_alibaba/installing-alibaba-default.adoc#installing-alibaba-default[✓]
|
||||
@@ -459,7 +459,7 @@ endif::openshift-origin[]
|
||||
//This table is for all flavors of OpenShift, except OKD. A separate table is required because OKD does not support multiple AWS architecture types. Trying to maintain one table using conditions, while convenient, is very fragile and prone to publishing errors.
|
||||
ifndef::openshift-origin[]
|
||||
|===
|
||||
||Alibaba |AWS (x86_64) |AWS (arm64) |Azure |Azure Stack Hub |GCP |Nutanix |{rh-openstack} |RHV |Bare metal (x86_64) |Bare metal (arm64) |vSphere |VMC |IBM Cloud VPC |IBM Z |IBM Z with {op-system-base} KVM |IBM Power |Platform agnostic
|
||||
||Alibaba |AWS (x86_64) |AWS (arm64) |Azure |Azure Stack Hub |GCP |Nutanix |{rh-openstack} |RHV |Bare metal (x86_64) |Bare metal (arm64) |vSphere |VMC |IBM Cloud VPC |{ibmzProductName} |{ibmzProductName} with {op-system-base} KVM |{ibmpowerProductName} |Platform agnostic
|
||||
|
||||
|Custom
|
||||
|
|
||||
@@ -549,7 +549,7 @@ endif::openshift-origin[]
|
||||
//This table is for OKD only. A separate table is required because OKD does not support multiple AWS architecture types. Trying to maintain one table using conditions, while convenient, is very fragile and prone to publishing errors.
|
||||
ifdef::openshift-origin[]
|
||||
|===
|
||||
||Alibaba |AWS |Azure |Azure Stack Hub |GCP |Nutanix |{rh-openstack} |oVirt |Bare metal |vSphere |VMC |IBM Cloud VPC |IBM Z |IBM Z with {op-system-base} KVM |IBM Power |Platform agnostic
|
||||
||Alibaba |AWS |Azure |Azure Stack Hub |GCP |Nutanix |{rh-openstack} |oVirt |Bare metal |vSphere |VMC |IBM Cloud VPC |{ibmzProductName} |{ibmzProductName} with {op-system-base} KVM |{ibmpowerProductName} |Platform agnostic
|
||||
|
||||
|Custom
|
||||
|
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
:_content-type: ASSEMBLY
|
||||
[id="installing-ibm-z-kvm"]
|
||||
= Installing a cluster with {op-system-base} KVM on {ibmzProductName} and LinuxONE
|
||||
= Installing a cluster with {op-system-base} KVM on {ibmzProductName} and {linuxoneProductName}
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: installing-ibm-z-kvm
|
||||
|
||||
@@ -8,11 +8,11 @@ toc::[]
|
||||
|
||||
[role="_abstract"]
|
||||
In {product-title} version {product-version}, you can install a cluster on
|
||||
{ibmzProductName} or LinuxONE infrastructure that you provision.
|
||||
{ibmzProductName} or {linuxoneProductName} infrastructure that you provision.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
While this document refers only to {ibmzProductName}, all information in it also applies to LinuxONE.
|
||||
While this document refers only to {ibmzProductName}, all information in it also applies to {linuxoneProductName}.
|
||||
====
|
||||
|
||||
[IMPORTANT]
|
||||
@@ -45,7 +45,7 @@ include::modules/csr-management.adoc[leveloffset=+2]
|
||||
[id="additional-resources_ibmz-kvm-recommended-host-practices"]
|
||||
.Additional resources
|
||||
|
||||
* xref:../../scalability_and_performance/ibm-z-recommended-host-practices.adoc#ibm-z-recommended-host-practices[Recommended host practices for {ibmzProductName} & LinuxONE environments]
|
||||
* xref:../../scalability_and_performance/ibm-z-recommended-host-practices.adoc#ibm-z-recommended-host-practices[Recommended host practices for {ibmzProductName} & {linuxoneProductName} environments]
|
||||
|
||||
include::modules/installation-network-user-infra.adoc[leveloffset=+2]
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
:_content-type: ASSEMBLY
|
||||
[id="installing-ibm-z"]
|
||||
= Installing a cluster with z/VM on {ibmzProductName} and LinuxONE
|
||||
= Installing a cluster with z/VM on {ibmzProductName} and {linuxoneProductName}
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: installing-ibm-z
|
||||
|
||||
@@ -8,11 +8,11 @@ toc::[]
|
||||
|
||||
[role="_abstract"]
|
||||
In {product-title} version {product-version}, you can install a cluster on
|
||||
{ibmzProductName} or LinuxONE infrastructure that you provision.
|
||||
{ibmzProductName} or {linuxoneProductName} infrastructure that you provision.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
While this document refers only to {ibmzProductName}, all information in it also applies to LinuxONE.
|
||||
While this document refers only to {ibmzProductName}, all information in it also applies to {linuxoneProductName}.
|
||||
====
|
||||
|
||||
[IMPORTANT]
|
||||
@@ -60,7 +60,7 @@ include::modules/csr-management.adoc[leveloffset=+2]
|
||||
|
||||
* See link:https://www.vm.ibm.com/library/presentations/lparperf.pdf[Topics in LPAR performance] for LPAR weight management and entitlements.
|
||||
|
||||
* xref:../../scalability_and_performance/ibm-z-recommended-host-practices.adoc#ibm-z-recommended-host-practices[Recommended host practices for IBM Z & LinuxONE environments]
|
||||
* xref:../../scalability_and_performance/ibm-z-recommended-host-practices.adoc#ibm-z-recommended-host-practices[Recommended host practices for {ibmzProductName} & {linuxoneProductName} environments]
|
||||
|
||||
include::modules/installation-network-user-infra.adoc[leveloffset=+2]
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
:_content-type: ASSEMBLY
|
||||
[id="installing-restricted-networks-ibm-z-kvm"]
|
||||
= Installing a cluster with {op-system-base} KVM on {ibmzProductName} and LinuxONE in a restricted network
|
||||
= Installing a cluster with {op-system-base} KVM on {ibmzProductName} and {linuxoneProductName} in a restricted network
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: installing-restricted-networks-ibm-z-kvm
|
||||
|
||||
@@ -8,11 +8,11 @@ toc::[]
|
||||
|
||||
[role="_abstract"]
|
||||
In {product-title} version {product-version}, you can install a cluster on
|
||||
{ibmzProductName} and LinuxONE infrastructure that you provision in a restricted network.
|
||||
{ibmzProductName} or {linuxoneProductName} infrastructure that you provision in a restricted network.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
While this document refers to only {ibmzProductName}, all information in it also applies to LinuxONE.
|
||||
While this document refers to only {ibmzProductName}, all information in it also applies to {linuxoneProductName}.
|
||||
====
|
||||
|
||||
[IMPORTANT]
|
||||
@@ -52,7 +52,7 @@ include::modules/csr-management.adoc[leveloffset=+2]
|
||||
[id="additional-resources_ibmz-kvm-restricted-recommended-host-practices"]
|
||||
.Additional resources
|
||||
|
||||
* xref:../../scalability_and_performance/ibm-z-recommended-host-practices.adoc#ibm-z-recommended-host-practices[Recommended host practices for IBM Z & LinuxONE environments]
|
||||
* xref:../../scalability_and_performance/ibm-z-recommended-host-practices.adoc#ibm-z-recommended-host-practices[Recommended host practices for {ibmzProductName} & {linuxoneProductName} environments]
|
||||
|
||||
include::modules/installation-network-user-infra.adoc[leveloffset=+2]
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
:_content-type: ASSEMBLY
|
||||
[id="installing-restricted-networks-ibm-z"]
|
||||
= Installing a cluster with z/VM on {ibmzProductName} and LinuxONE in a restricted network
|
||||
= Installing a cluster with z/VM on {ibmzProductName} and {linuxoneProductName} in a restricted network
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: installing-restricted-networks-ibm-z
|
||||
|
||||
@@ -8,11 +8,11 @@ toc::[]
|
||||
|
||||
[role="_abstract"]
|
||||
In {product-title} version {product-version}, you can install a cluster on
|
||||
{ibmzProductName} and LinuxONE infrastructure that you provision in a restricted network.
|
||||
{ibmzProductName} or {linuxoneProductName} infrastructure that you provision in a restricted network.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
While this document refers to only {ibmzProductName}, all information in it also applies to LinuxONE.
|
||||
While this document refers to only {ibmzProductName}, all information in it also applies to {linuxoneProductName}.
|
||||
====
|
||||
|
||||
[IMPORTANT]
|
||||
@@ -67,7 +67,7 @@ include::modules/csr-management.adoc[leveloffset=+2]
|
||||
|
||||
* See link:https://www.vm.ibm.com/library/presentations/lparperf.pdf[Topics in LPAR performance] for LPAR weight management and entitlements.
|
||||
|
||||
* xref:../../scalability_and_performance/ibm-z-recommended-host-practices.adoc#ibm-z-recommended-host-practices[Recommended host practices for {ibmzProductName} & LinuxONE environments]
|
||||
* xref:../../scalability_and_performance/ibm-z-recommended-host-practices.adoc#ibm-z-recommended-host-practices[Recommended host practices for {ibmzProductName} & {linuxoneProductName} environments]
|
||||
|
||||
include::modules/installation-network-user-infra.adoc[leveloffset=+2]
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
:_content-type: ASSEMBLY
|
||||
[id="preparing-to-install-on-ibm-z-kvm"]
|
||||
= Preparing to install with {op-system-base} KVM on IBM Z and LinuxONE
|
||||
= Preparing to install with {op-system-base} KVM on {ibmzProductName} and {linuxoneProductName}
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: preparing-to-install-on-ibm-z-kvm
|
||||
|
||||
@@ -13,10 +13,10 @@ toc::[]
|
||||
* You read the documentation on xref:../../installing/installing-preparing.adoc#installing-preparing[selecting a cluster installation method and preparing it for users].
|
||||
|
||||
[id="choosing-an-method-to-install-ocp-on-ibm-z-kvm"]
|
||||
== Choosing a method to install {product-title} with {op-system-base} KVM on IBM Z or LinuxONE
|
||||
== Choosing a method to install {product-title} with {op-system-base} KVM on {ibmzProductName} or {linuxoneProductName}
|
||||
|
||||
You can install a cluster with {op-system-base} KVM on IBM Z or LinuxONE infrastructure that you provision, by using one of the following methods:
|
||||
You can install a cluster with {op-system-base} KVM on {ibmzProductName} or {linuxoneProductName} infrastructure that you provision, by using one of the following methods:
|
||||
|
||||
* **xref:../../installing/installing_ibm_z/installing-ibm-z-kvm.adoc#installing-ibm-z-kvm[Installing a cluster with RHEL KVM on IBM Z and LinuxONE]**: You can install {product-title} with KVM on IBM Z or LinuxONE infrastructure that you provision.
|
||||
* **xref:../../installing/installing_ibm_z/installing-ibm-z-kvm.adoc#installing-ibm-z-kvm[Installing a cluster with RHEL KVM on {ibmzProductName} and {linuxoneProductName}]**: You can install {product-title} with KVM on {ibmzProductName} or {linuxoneProductName} infrastructure that you provision.
|
||||
|
||||
* **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 and LinuxONE in a restricted network]**: You can install {product-title} with {op-system-base} KVM on IBM Z or LinuxONE 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.
|
||||
* **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 {ibmzProductName} and {linuxoneProductName} in a restricted network]**: You can install {product-title} with {op-system-base} KVM on {ibmzProductName} or {linuxoneProductName} 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.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
:_content-type: ASSEMBLY
|
||||
[id="preparing-to-install-on-ibm-z"]
|
||||
= Preparing to install with z/VM on IBM Z and LinuxONE
|
||||
= Preparing to install with z/VM on {ibmzProductName} and {linuxoneProductName}
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: preparing-to-install-on-ibm-z
|
||||
|
||||
@@ -13,10 +13,10 @@ toc::[]
|
||||
* You read the documentation on xref:../../installing/installing-preparing.adoc#installing-preparing[selecting a cluster installation method and preparing it for users].
|
||||
|
||||
[id="choosing-an-method-to-install-ocp-on-ibm-z"]
|
||||
== Choosing a method to install {product-title} with z/VM on IBM Z or LinuxONE
|
||||
== Choosing a method to install {product-title} with z/VM on {ibmzProductName} or {linuxoneProductName}
|
||||
|
||||
You can install a cluster with z/VM on IBM Z or LinuxONE infrastructure that you provision, by using one of the following methods:
|
||||
You can install a cluster with z/VM on {ibmzProductName} or {linuxoneProductName} infrastructure that you provision, by using one of the following methods:
|
||||
|
||||
* **xref:../../installing/installing_ibm_z/installing-ibm-z.adoc#installing-ibm-z[Installing a cluster with z/VM on IBM Z and LinuxONE]**: You can install {product-title} with z/VM on IBM Z or LinuxONE infrastructure that you provision.
|
||||
* **xref:../../installing/installing_ibm_z/installing-ibm-z.adoc#installing-ibm-z[Installing a cluster with z/VM on {ibmzProductName} and {linuxoneProductName}]**: You can install {product-title} with z/VM on {ibmzProductName} or {linuxoneProductName} infrastructure that you provision.
|
||||
|
||||
* **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 and LinuxONE in a restricted network]**: You can install {product-title} with z/VM on IBM Z or LinuxONE 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.
|
||||
* **xref:../../installing/installing_ibm_z/installing-restricted-networks-ibm-z.adoc#installing-restricted-networks-ibm-z[Installing a cluster with z/VM on {ibmzProductName} and {linuxoneProductName} in a restricted network]**: You can install {product-title} with z/VM on {ibmzProductName} or {linuxoneProductName} 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.
|
||||
|
||||
@@ -159,8 +159,8 @@ $ oc -n openshift-logging edit ClusterLogging instance
|
||||
| Global proxy support | ✓ | ✓
|
||||
| x86 support | ✓ | ✓
|
||||
| ARM support | ✓ | ✓
|
||||
| PowerPC support | ✓ | ✓
|
||||
| IBM Z support | ✓ | ✓
|
||||
| {ibmpowerProductName} support | ✓ | ✓
|
||||
| {ibmzProductName} support | ✓ | ✓
|
||||
| IPv6 support | ✓ | ✓
|
||||
| Log event buffering | ✓ |
|
||||
| Disconnected Cluster | ✓ | ✓
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
|
||||
[id="installing-odo-on-linux-on-ibm-z"]
|
||||
|
||||
= Installing {odo-title} on Linux on IBM Z and LinuxONE
|
||||
= Installing {odo-title} on Linux on {ibmzProductName} and {linuxoneProductName}
|
||||
|
||||
== Binary installation
|
||||
|
||||
|
||||
@@ -7,14 +7,14 @@
|
||||
|
||||
= Installing {odo-title} on Linux
|
||||
|
||||
The `{odo-title}` CLI is available to download as a binary and as a tarball for multiple operating systems and architectures including:
|
||||
The `{odo-title}` CLI is available to download as a binary and as a tarball for multiple operating systems and architectures including:
|
||||
|
||||
[cols="2,1,1",options="header"]
|
||||
|===
|
||||
|Operating System|Binary|Tarball
|
||||
|Linux|link:https://developers.redhat.com/content-gateway/rest/mirror/pub/openshift-v4/clients/odo/latest/odo-linux-amd64[odo-linux-amd64] |link:https://developers.redhat.com/content-gateway/rest/mirror/pub/openshift-v4/clients/odo/latest/odo-linux-amd64.tar.gz[odo-linux-amd64.tar.gz]
|
||||
|Linux on IBM Power|link:https://developers.redhat.com/content-gateway/rest/mirror/pub/openshift-v4/clients/odo/latest/odo-linux-ppc64le[odo-linux-ppc64le] |link:https://developers.redhat.com/content-gateway/rest/mirror/pub/openshift-v4/clients/odo/latest/odo-linux-ppc64le.tar.gz[odo-linux-ppc64le.tar.gz]
|
||||
|Linux on IBM Z and LinuxONE|link:https://developers.redhat.com/content-gateway/rest/mirror/pub/openshift-v4/clients/odo/latest/odo-linux-s390x[odo-linux-s390x] |link:https://developers.redhat.com/content-gateway/rest/mirror/pub/openshift-v4/clients/odo/latest/odo-linux-s390x.tar.gz[odo-linux-s390x.tar.gz]
|
||||
|Linux on {ibmpowerProductName}|link:https://developers.redhat.com/content-gateway/rest/mirror/pub/openshift-v4/clients/odo/latest/odo-linux-ppc64le[odo-linux-ppc64le] |link:https://developers.redhat.com/content-gateway/rest/mirror/pub/openshift-v4/clients/odo/latest/odo-linux-ppc64le.tar.gz[odo-linux-ppc64le.tar.gz]
|
||||
|Linux on {ibmzProductName} and {linuxoneProductName}|link:https://developers.redhat.com/content-gateway/rest/mirror/pub/openshift-v4/clients/odo/latest/odo-linux-s390x[odo-linux-s390x] |link:https://developers.redhat.com/content-gateway/rest/mirror/pub/openshift-v4/clients/odo/latest/odo-linux-s390x.tar.gz[odo-linux-s390x.tar.gz]
|
||||
|===
|
||||
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ The streaming strategy requires an additional Red Hat subscription for AMQ Strea
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
The streaming deployment strategy is currently unsupported on IBM Z.
|
||||
The streaming deployment strategy is currently unsupported on {ibmzProductName}.
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
|
||||
@@ -6,7 +6,7 @@
|
||||
[id="ibm-z-choose-networking-setup_{context}"]
|
||||
= Choose your networking setup
|
||||
|
||||
The networking stack is one of the most important components for a Kubernetes-based product like {product-title}. For IBM Z setups, the networking setup depends on the hypervisor of your choice. Depending on the workload and the application, the best fit usually changes with the use case and the traffic pattern.
|
||||
The networking stack is one of the most important components for a Kubernetes-based product like {product-title}. For {ibmzProductName} setups, the networking setup depends on the hypervisor of your choice. Depending on the workload and the application, the best fit usually changes with the use case and the traffic pattern.
|
||||
|
||||
Depending on your setup, consider these best practices:
|
||||
|
||||
|
||||
@@ -6,14 +6,14 @@
|
||||
[id="ibm-z-ensure-high-disk-performance-hyperpav_{context}"]
|
||||
= Ensure high disk performance with HyperPAV on z/VM
|
||||
|
||||
DASD and ECKD devices are commonly used disk types in IBM Z environments. In a typical {product-title} setup in z/VM environments, DASD disks are commonly used to support the local storage for the nodes. You can set up HyperPAV alias devices to provide more throughput and overall better I/O performance for the DASD disks that support the z/VM guests.
|
||||
DASD and ECKD devices are commonly used disk types in {ibmzProductName} environments. In a typical {product-title} setup in z/VM environments, DASD disks are commonly used to support the local storage for the nodes. You can set up HyperPAV alias devices to provide more throughput and overall better I/O performance for the DASD disks that support the z/VM guests.
|
||||
|
||||
Using HyperPAV for the local storage devices leads to a significant performance benefit. However, you must be aware that there is a trade-off between throughput and CPU costs.
|
||||
|
||||
[id="use-the-mco-to-activate-hyperpav-aliases-in-nodes-using-zvm-full-pack-minidisks_{context}"]
|
||||
== Use the Machine Config Operator (MCO) to activate HyperPAV aliases in nodes using z/VM full-pack minidisks
|
||||
|
||||
For z/VM-based {product-title} setups that use full-pack minidisks, you can leverage the advantage of MCO profiles by activating HyperPAV aliases in all of the nodes. You must add YAML configurations for both control plane and compute nodes.
|
||||
For z/VM-based {product-title} setups that use full-pack minidisks, you can leverage the advantage of MCO profiles by activating HyperPAV aliases in all of the nodes. You must add YAML configurations for both control plane and compute nodes.
|
||||
|
||||
.Procedure
|
||||
|
||||
|
||||
@@ -6,11 +6,11 @@
|
||||
[id="ibm-z-managing-cpu-overcommitment_{context}"]
|
||||
= Managing CPU overcommitment
|
||||
|
||||
In a highly virtualized IBM Z environment, you must carefully plan the infrastructure setup and sizing. One of the most important features of virtualization is the capability to do resource overcommitment, allocating more resources to the virtual machines than actually available at the hypervisor level. This is very workload dependent and there is no golden rule that can be applied to all setups.
|
||||
In a highly virtualized {ibmzProductName} environment, you must carefully plan the infrastructure setup and sizing. One of the most important features of virtualization is the capability to do resource overcommitment, allocating more resources to the virtual machines than actually available at the hypervisor level. This is very workload dependent and there is no golden rule that can be applied to all setups.
|
||||
|
||||
Depending on your setup, consider these best practices regarding CPU overcommitment:
|
||||
|
||||
* At LPAR level (PR/SM hypervisor), avoid assigning all available physical cores (IFLs) to each LPAR. For example, with four physical IFLs available, you should not define three LPARs with four logical IFLs each.
|
||||
* At LPAR level (PR/SM hypervisor), avoid assigning all available physical cores (IFLs) to each LPAR. For example, with four physical IFLs available, you should not define three LPARs with four logical IFLs each.
|
||||
* Check and understand LPAR shares and weights.
|
||||
* An excessive number of virtual CPUs can adversely affect performance. Do not define more virtual processors to a guest than logical processors are defined to the LPAR.
|
||||
* Configure the number of virtual processors per guest for peak workload, not more.
|
||||
|
||||
@@ -4,11 +4,11 @@
|
||||
|
||||
:_content-type: PROCEDURE
|
||||
[id="ibm-z-rhel-kvm-host-recommendations_{context}"]
|
||||
= {op-system-base} KVM on IBM Z host recommendations
|
||||
= {op-system-base} KVM on {ibmzProductName} host recommendations
|
||||
|
||||
Optimizing a KVM virtual server environment strongly depends on the workloads of the virtual servers and on the available resources. The same action that enhances performance in one environment can have adverse effects in another. Finding the best balance for a particular setting can be a challenge and often involves experimentation.
|
||||
|
||||
The following section introduces some best practices when using {product-title} with {op-system-base} KVM on IBM Z and LinuxONE environments.
|
||||
The following section introduces some best practices when using {product-title} with {op-system-base} KVM on {ibmzProductName} and {linuxoneProductName} environments.
|
||||
|
||||
[id="use-multiple-queues-for-your-virtio-network-interfaces_{context}"]
|
||||
== Use multiple queues for your VirtIO network interfaces
|
||||
@@ -140,7 +140,7 @@ This setting applies only to KVM hosts with cgroups version 1. To enable CPU hot
|
||||
|
||||
. Go to the `cgroup_controllers` line.
|
||||
|
||||
. Duplicate the entire line and remove the leading number sign (#) from the copy.
|
||||
. Duplicate the entire line and remove the leading number sign (#) from the copy.
|
||||
|
||||
. Remove the `cpuset` entry, as follows:
|
||||
+
|
||||
|
||||
@@ -14,7 +14,7 @@ include::snippets/technology-preview.adoc[]
|
||||
|
||||
.Prerequisites
|
||||
|
||||
* IBM z15 or later, or IBM LinuxONE III or later.
|
||||
* IBM z15 or later, or {linuxoneProductName} III or later.
|
||||
* {op-system-base-full} 8 or later.
|
||||
* You have a bootstrap Ignition file. The file is not protected, enabling others to view and edit it.
|
||||
* You have verified that the boot image has not been altered after installation.
|
||||
@@ -30,7 +30,7 @@ include::snippets/technology-preview.adoc[]
|
||||
.. Add the kernel command line parameter `prot_virt=1`.
|
||||
.. Run the `zipl` command and reboot your system.
|
||||
+
|
||||
KVM hosts that successfully start with support for IBM Secure Execution for Linux issue the following kernel message:
|
||||
KVM hosts that successfully start with support for IBM Secure Execution for Linux issue the following kernel message:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
@@ -101,4 +101,4 @@ base64 <your-hostkey>.crt
|
||||
+
|
||||
Compared to guests not running IBM Secure Execution, the first boot of the machine is longer because the entire image is encrypted with a randomly generated LUKS passphrase before the Ignition phase.
|
||||
|
||||
. Follow the fast-track installation procedure to install nodes using the IBM Secure Exection QCOW image.
|
||||
. Follow the fast-track installation procedure to install nodes using the IBM Secure Exection QCOW image.
|
||||
@@ -4,9 +4,9 @@
|
||||
|
||||
:_content-type: PROCEDURE
|
||||
[id="configure-additional-devices-manually_{context}"]
|
||||
= Configuring additional devices manually
|
||||
= Configuring additional devices manually
|
||||
|
||||
Tasks in this section describe how to manually configure additional devices in an {ibmzProductName} or LinuxONE environment. This configuration method is persistent over node restarts but not {product-title} native and you need to redo the steps if you replace the node.
|
||||
Tasks in this section describe how to manually configure additional devices in an {ibmzProductName} or {linuxoneProductName} environment. This configuration method is persistent over node restarts but not {product-title} native and you need to redo the steps if you replace the node.
|
||||
|
||||
.Prerequisites
|
||||
|
||||
@@ -23,7 +23,7 @@ Tasks in this section describe how to manually configure additional devices in a
|
||||
$ ssh <user>@<node_ip_address>
|
||||
----
|
||||
+
|
||||
You can also start a debug session to the node by running the following command:
|
||||
You can also start a debug session to the node by running the following command:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
|
||||
@@ -4,9 +4,9 @@
|
||||
|
||||
:_content-type: PROCEDURE
|
||||
[id="configure-additional-devices-using-mco_{context}"]
|
||||
= Configuring additional devices using the Machine Config Operator (MCO)
|
||||
= Configuring additional devices using the Machine Config Operator (MCO)
|
||||
|
||||
Tasks in this section describe how to use features of the Machine Config Operator (MCO) to configure additional devices in an {ibmzProductName} or LinuxONE environment. Configuring devices with the MCO is persistent but only allows specific configurations for compute nodes. MCO does not allow control plane nodes to have different configurations.
|
||||
Tasks in this section describe how to use features of the Machine Config Operator (MCO) to configure additional devices in an {ibmzProductName} or {linuxoneProductName} environment. Configuring devices with the MCO is persistent but only allows specific configurations for compute nodes. MCO does not allow control plane nodes to have different configurations.
|
||||
|
||||
.Prerequisites
|
||||
|
||||
@@ -63,8 +63,8 @@ $ base64 /path/to/file/
|
||||
+
|
||||
[source,yaml]
|
||||
----
|
||||
apiVersion: machineconfiguration.openshift.io/v1
|
||||
kind: MachineConfig
|
||||
apiVersion: machineconfiguration.openshift.io/v1
|
||||
kind: MachineConfig
|
||||
metadata:
|
||||
labels:
|
||||
machineconfiguration.openshift.io/role: worker0 <1>
|
||||
@@ -120,8 +120,8 @@ $ base64 /path/to/file/
|
||||
+
|
||||
[source,yaml]
|
||||
----
|
||||
apiVersion: machineconfiguration.openshift.io/v1
|
||||
kind: MachineConfig
|
||||
apiVersion: machineconfiguration.openshift.io/v1
|
||||
kind: MachineConfig
|
||||
metadata:
|
||||
labels:
|
||||
machineconfiguration.openshift.io/role: worker0 <1>
|
||||
@@ -174,8 +174,8 @@ $ base64 /path/to/file/
|
||||
+
|
||||
[source,yaml]
|
||||
----
|
||||
apiVersion: machineconfiguration.openshift.io/v1
|
||||
kind: MachineConfig
|
||||
apiVersion: machineconfiguration.openshift.io/v1
|
||||
kind: MachineConfig
|
||||
metadata:
|
||||
labels:
|
||||
machineconfiguration.openshift.io/role: worker0 <1>
|
||||
@@ -239,8 +239,8 @@ $ base64 /path/to/file/
|
||||
+
|
||||
[source,yaml]
|
||||
----
|
||||
apiVersion: machineconfiguration.openshift.io/v1
|
||||
kind: MachineConfig
|
||||
apiVersion: machineconfiguration.openshift.io/v1
|
||||
kind: MachineConfig
|
||||
metadata:
|
||||
labels:
|
||||
machineconfiguration.openshift.io/role: worker0 <1>
|
||||
|
||||
@@ -4,13 +4,13 @@
|
||||
|
||||
:_content-type: PROCEDURE
|
||||
[id="enabling-multipathing-fcp-luns_{context}"]
|
||||
= Enabling multipathing for FCP LUNs
|
||||
= Enabling multipathing for FCP LUNs
|
||||
|
||||
Tasks in this section describe how to manually configure additional devices in an {ibmzProductName} or LinuxONE environment. This configuration method is persistent over node restarts but not {product-title} native and you need to redo the steps if you replace the node.
|
||||
Tasks in this section describe how to manually configure additional devices in an {ibmzProductName} or {linuxoneProductName} environment. This configuration method is persistent over node restarts but not {product-title} native and you need to redo the steps if you replace the node.
|
||||
|
||||
[IMPORTANT]
|
||||
====
|
||||
On {ibmzProductName} and LinuxONE, you can enable multipathing only if you configured your cluster for it during installation. For more information, see "Installing {op-system} and starting the {product-title} bootstrap process" in _Installing a cluster with z/VM on {ibmzProductName} and LinuxONE_.
|
||||
On {ibmzProductName} and {linuxoneProductName}, you can enable multipathing only if you configured your cluster for it during installation. For more information, see "Installing {op-system} and starting the {product-title} bootstrap process" in _Installing a cluster with z/VM on {ibmzProductName} and {linuxoneProductName}_.
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
@@ -27,7 +27,7 @@ On {ibmzProductName} and LinuxONE, you can enable multipathing only if you confi
|
||||
$ ssh <user>@<node_ip_address>
|
||||
----
|
||||
+
|
||||
You can also start a debug session to the node by running the following command:
|
||||
You can also start a debug session to the node by running the following command:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
|
||||
@@ -50,10 +50,10 @@ ifndef::ibm-z,ibm-z-kvm,ibm-power,agnostic,rhv[]
|
||||
= Sample install-config.yaml file for bare metal
|
||||
endif::ibm-z,ibm-z-kvm,ibm-power,agnostic,rhv[]
|
||||
ifdef::ibm-z,ibm-z-kvm[]
|
||||
= Sample install-config.yaml file for IBM Z
|
||||
= Sample install-config.yaml file for {ibmzProductName}
|
||||
endif::ibm-z,ibm-z-kvm[]
|
||||
ifdef::ibm-power[]
|
||||
= Sample install-config.yaml file for IBM Power
|
||||
= Sample install-config.yaml file for {ibmpowerProductName}
|
||||
endif::ibm-power[]
|
||||
ifdef::agnostic[]
|
||||
= Sample install-config.yaml file for other platforms
|
||||
@@ -249,8 +249,8 @@ Class E CIDR range is reserved for a future use. To use the Class E CIDR range,
|
||||
<10> The IP address pool to use for service IP addresses. You can enter only one IP address pool. This block must not overlap with existing physical networks. If you need to access the services from an external network, configure load balancers and routers to manage the traffic.
|
||||
<11> You must set the platform to `none`. You cannot provide additional platform configuration variables for
|
||||
ifndef::ibm-z,ibm-z-kvm,ibm-power,rhv[your platform.]
|
||||
ifdef::ibm-z,ibm-z-kvm[IBM Z infrastructure.]
|
||||
ifdef::ibm-power[IBM Power infrastructure.]
|
||||
ifdef::ibm-z,ibm-z-kvm[{ibmzProductName} infrastructure.]
|
||||
ifdef::ibm-power[{ibmpowerProductName} infrastructure.]
|
||||
ifdef::rhv[RHV infrastructure.]
|
||||
ifndef::openshift-origin[]
|
||||
+
|
||||
|
||||
@@ -7,8 +7,8 @@
|
||||
[id="installation-ibm-z-kvm-user-infra-installing-rhcos_{context}"]
|
||||
= Installing {op-system} and starting the {product-title} bootstrap process
|
||||
|
||||
To install {product-title} on IBM Z infrastructure that you provision, you must install {op-system-first} as {op-system-base-full} 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} machines have rebooted.
|
||||
To install {product-title} on {ibmzProductName} infrastructure that you provision, you must install {op-system-first} as {op-system-base-full} 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} machines have rebooted.
|
||||
|
||||
You can perform a fast-track installation of {op-system} that uses a prepackaged QEMU copy-on-write (QCOW2) disk image. Alternatively, you can perform a full installation on a new QCOW2 disk image.
|
||||
|
||||
To add further security to your system, you can optionally install {op-system} using IBM Secure Execution before proceeding to the fast-track installation.
|
||||
To add further security to your system, you can optionally install {op-system} using IBM Secure Execution before proceeding to the fast-track installation.
|
||||
|
||||
@@ -7,7 +7,7 @@
|
||||
= Collecting debugging information
|
||||
|
||||
You can gather debugging information that might help you to troubleshoot and
|
||||
debug certain issues with an {product-title} installation on IBM Z.
|
||||
debug certain issues with an {product-title} installation on {ibmzProductName}.
|
||||
|
||||
.Prerequisites
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@
|
||||
[id="installation-user-infra-machines-iso-ibm-z_{context}"]
|
||||
= Installing {op-system} and starting the {product-title} bootstrap process
|
||||
|
||||
To install {product-title} on IBM Z 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.
|
||||
To install {product-title} on {ibmzProductName} 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.
|
||||
|
||||
Complete the following steps to create the machines.
|
||||
|
||||
@@ -70,7 +70,7 @@ zfcp.allow_lun_scan=0 \
|
||||
rd.dasd=0.0.3490
|
||||
----
|
||||
+
|
||||
Write all options in the parameter file as a single line and make sure you have no newline characters.
|
||||
Write all options in the parameter file as a single line and make sure you have no newline characters.
|
||||
|
||||
** For installations on FCP-type disks, complete the following tasks:
|
||||
... Use `rd.zfcp=<adapter>,<wwpn>,<lun>` to specify the FCP disk where {op-system} is to be installed. For multipathing repeat this step for each additional path.
|
||||
|
||||
@@ -66,11 +66,11 @@ The {op-system-base} KVM host in your environment must meet the following requir
|
||||
You can install {product-title} version {product-version} on the following IBM hardware:
|
||||
|
||||
* IBM z16 (all models), IBM z15 (all models), IBM z14 (all models), IBM z13, and IBM z13s
|
||||
* IBM LinuxONE Emperor 4, IBM LinuxONE III (all models), IBM LinuxONE Emperor II, IBM LinuxONE Rockhopper II, IBM LinuxONE Emperor, and IBM LinuxONE Rockhopper
|
||||
* {linuxoneProductName} Emperor 4, {linuxoneProductName} III (all models), {linuxoneProductName} Emperor II, {linuxoneProductName} Rockhopper II, {linuxoneProductName} Emperor, and {linuxoneProductName} Rockhopper
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
Support for {op-system} functionality for IBM z13 all models, LinuxONE Emperor, and LinuxONE Rockhopper is deprecated. These hardware models remain fully supported in {product-title} 4.12. However, Red Hat recommends that you use later hardware models.
|
||||
Support for {op-system} functionality for IBM z13 all models, {linuxoneProductName} Emperor, and {linuxoneProductName} Rockhopper is deprecated. These hardware models remain fully supported in {product-title} 4.12. However, Red Hat recommends that you use later hardware models.
|
||||
====
|
||||
|
||||
[id="minimum-ibm-z-system-requirements_{context}"]
|
||||
|
||||
@@ -89,8 +89,8 @@ include::snippets/logging-outputs-5.6-snip.adoc[]
|
||||
| Global proxy support | ✓ | ✓
|
||||
| x86 support | ✓ | ✓
|
||||
| ARM support | ✓ | ✓
|
||||
| PowerPC support | ✓ | ✓
|
||||
| IBM Z support | ✓ | ✓
|
||||
| {ibmpowerProductName} support | ✓ | ✓
|
||||
| {ibmzProductName} support | ✓ | ✓
|
||||
| IPv6 support | ✓ | ✓
|
||||
| Log event buffering | ✓ |
|
||||
| Disconnected Cluster | ✓ | ✓
|
||||
|
||||
@@ -10,11 +10,11 @@
|
||||
You can install {product-title} version {product-version} on the following IBM hardware:
|
||||
|
||||
* IBM z16 (all models), IBM z15 (all models), IBM z14 (all models), IBM z13, and IBM z13s
|
||||
* IBM LinuxONE Emperor 4, IBM LinuxONE III (all models), IBM LinuxONE Emperor II, IBM LinuxONE Rockhopper II, IBM LinuxONE Emperor, and IBM LinuxONE Rockhopper
|
||||
* {linuxoneProductName} Emperor 4, {linuxoneProductName} III (all models), {linuxoneProductName} Emperor II, {linuxoneProductName} Rockhopper II, {linuxoneProductName} Emperor, and {linuxoneProductName} Rockhopper
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
Support for {op-system} functionality for IBM z13 all models, LinuxONE Emperor, and LinuxONE Rockhopper is deprecated. These hardware models remain fully supported in {product-title} 4.12. However, Red Hat recommends that you use later hardware models.
|
||||
Support for {op-system} functionality for IBM z13 all models, {linuxoneProductName} Emperor, and {linuxoneProductName} Rockhopper is deprecated. These hardware models remain fully supported in {product-title} 4.12. However, Red Hat recommends that you use later hardware models.
|
||||
====
|
||||
|
||||
[discrete]
|
||||
|
||||
@@ -15,10 +15,10 @@ The following strings are supported in Operator Lifecycle Manager (OLM) on {prod
|
||||
|AMD64
|
||||
|`amd64`
|
||||
|
||||
|64-bit PowerPC little-endian
|
||||
|{ibmpowerProductName}
|
||||
|`ppc64le`
|
||||
|
||||
|IBM Z
|
||||
|{ibmzProductName}
|
||||
|`s390x`
|
||||
|===
|
||||
|
||||
|
||||
@@ -127,7 +127,7 @@ $ opm index prune \
|
||||
----
|
||||
<1> Index to prune.
|
||||
<2> Comma-separated list of packages to keep.
|
||||
<3> Required only for IBM Power and IBM Z images: Operator Registry base image with the tag that matches the target {product-title} cluster major and minor version.
|
||||
<3> Required only for {ibmpowerProductName} and {ibmzProductName} images: Operator Registry base image with the tag that matches the target {product-title} cluster major and minor version.
|
||||
<4> Custom tag for new index image being built.
|
||||
|
||||
. Run the following command to push the new index image to your target registry:
|
||||
|
||||
@@ -12,8 +12,8 @@ Cluster administrators can use the `tkn-pac` and `opc` CLI tools on local machin
|
||||
You can install the `tkn-pac` and `opc` version `1.9.1` binaries for the supported platforms:
|
||||
|
||||
* link:https://mirror.openshift.com/pub/openshift-v4/clients/pipeline/1.9.1/tkn-linux-amd64.tar.gz[Linux (x86_64, amd64)]
|
||||
* link:https://mirror.openshift.com/pub/openshift-v4/clients/pipeline/1.9.1/tkn-linux-s390x.tar.gz[Linux on IBM zSystems and IBM(R) LinuxONE (s390x)]
|
||||
* link:https://mirror.openshift.com/pub/openshift-v4/clients/pipeline/1.9.1/tkn-linux-ppc64le.tar.gz[Linux on IBM Power (ppc64le)]
|
||||
* link:https://mirror.openshift.com/pub/openshift-v4/clients/pipeline/1.9.1/tkn-linux-s390x.tar.gz[Linux on {ibmzProductName} and {linuxoneProductName} (s390x)]
|
||||
* link:https://mirror.openshift.com/pub/openshift-v4/clients/pipeline/1.9.1/tkn-linux-ppc64le.tar.gz[Linux on {ibmpowerProductName} (ppc64le)]
|
||||
* link:https://mirror.openshift.com/pub/openshift-v4/clients/pipeline/1.9.1/tkn-macos-amd64.tar.gz[macOS]
|
||||
* link:https://mirror.openshift.com/pub/openshift-v4/clients/pipeline/1.9.1/tkn-windows-amd64.zip[Windows]
|
||||
|
||||
|
||||
@@ -16,9 +16,9 @@ For Linux distributions, you can download the CLI as a `tar.gz` archive.
|
||||
|
||||
* link:https://mirror.openshift.com/pub/openshift-v4/clients/pipeline/1.9.1/tkn-linux-amd64.tar.gz[Linux (x86_64, amd64)]
|
||||
|
||||
* link:https://mirror.openshift.com/pub/openshift-v4/clients/pipeline/1.9.1/tkn-linux-s390x.tar.gz[Linux on IBM zSystems and IBM(R) LinuxONE (s390x)]
|
||||
* link:https://mirror.openshift.com/pub/openshift-v4/clients/pipeline/1.9.1/tkn-linux-s390x.tar.gz[Linux on {ibmzProductName} and {linuxoneProductName} (s390x)]
|
||||
|
||||
* link:https://mirror.openshift.com/pub/openshift-v4/clients/pipeline/1.9.1/tkn-linux-ppc64le.tar.gz[Linux on IBM Power (ppc64le)]
|
||||
* link:https://mirror.openshift.com/pub/openshift-v4/clients/pipeline/1.9.1/tkn-linux-ppc64le.tar.gz[Linux on {ibmpowerProductName} (ppc64le)]
|
||||
|
||||
* link:https://mirror.openshift.com/pub/openshift-v4/clients/pipeline/1.9.1/tkn-linux-arm64.tar.gz[Linux on ARM (arm64)]
|
||||
|
||||
|
||||
@@ -15,8 +15,8 @@ If the cluster runs on bare metal and fully supports `LoadBalancer` services, th
|
||||
|
||||
If the cluster does not support `LoadBalancer` services, using a `NodePort` service could be an option if the nodes are accessible from the cluster running the other mesh. In the `ServiceMeshPeer` object, specify the IP addresses of the nodes in the `.spec.remote.addresses` field and the service's node ports in the `.spec.remote.discoveryPort` and `.spec.remote.servicePort` fields.
|
||||
|
||||
== Exposing the federation ingress on clusters running on IBM Power and IBM Z
|
||||
If the cluster runs on IBM Power or IBM Z infrastructure and fully supports `LoadBalancer` services, the IP address found in the `.status.loadBalancer.ingress.ip` field of the ingress gateway `Service` object should be specified as one of the entries in the `.spec.remote.addresses` field of the `ServiceMeshPeer` object.
|
||||
== Exposing the federation ingress on clusters running on {ibmpowerProductName} and {ibmzProductName}
|
||||
If the cluster runs on {ibmpowerProductName} or {ibmzProductName} infrastructure and fully supports `LoadBalancer` services, the IP address found in the `.status.loadBalancer.ingress.ip` field of the ingress gateway `Service` object should be specified as one of the entries in the `.spec.remote.addresses` field of the `ServiceMeshPeer` object.
|
||||
|
||||
If the cluster does not support `LoadBalancer` services, using a `NodePort` service could be an option if the nodes are accessible from the cluster running the other mesh. In the `ServiceMeshPeer` object, specify the IP addresses of the nodes in the `.spec.remote.addresses` field and the service's node ports in the `.spec.remote.discoveryPort` and `.spec.remote.servicePort` fields.
|
||||
|
||||
|
||||
@@ -40,9 +40,9 @@ Explicitly unsupported cases include:
|
||||
[id="ossm-supported-configurations-sm_{context}"]
|
||||
== Supported configurations for Service Mesh
|
||||
|
||||
* This release of {SMProductName} is only available on {product-title} x86_64, IBM Z, and IBM Power Systems.
|
||||
** IBM Z is only supported on {product-title} 4.6 and later.
|
||||
** IBM Power Systems is only supported on {product-title} 4.6 and later.
|
||||
* This release of {SMProductName} is only available on {product-title} x86_64, {ibmzProductName}, and {ibmpowerProductName}.
|
||||
** {ibmzProductName} is only supported on {product-title} 4.6 and later.
|
||||
** {ibmpowerProductName} is only supported on {product-title} 4.6 and later.
|
||||
* Configurations where all {SMProductShortName} components are contained within a single {product-title} cluster.
|
||||
* Configurations that do not integrate external services such as virtual machines.
|
||||
* {SMProductName} does not support `EnvoyFilter` configuration except where explicitly documented.
|
||||
|
||||
@@ -19,7 +19,7 @@ This tutorial walks you through how to create a sample application by creating a
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
The Bookinfo sample application cannot be installed on IBM Z and IBM Power Systems.
|
||||
The Bookinfo sample application cannot be installed on {ibmzProductName} and {ibmpowerProductName}.
|
||||
====
|
||||
|
||||
[NOTE]
|
||||
|
||||
@@ -14,7 +14,7 @@ Enabling multipathing during installation is supported and recommended for nodes
|
||||
====
|
||||
[IMPORTANT]
|
||||
====
|
||||
On IBM Z and LinuxONE, you can enable multipathing only if you configured your cluster for it during installation. For more information, see "Installing {op-system} and starting the {product-title} bootstrap process" in _Installing a cluster with z/VM on IBM Z and LinuxONE_.
|
||||
On {ibmzProductName} and {linuxoneProductName}, you can enable multipathing only if you configured your cluster for it during installation. For more information, see "Installing {op-system} and starting the {product-title} bootstrap process" in _Installing a cluster with z/VM on {ibmzProductName} and {linuxoneProductName}_.
|
||||
====
|
||||
// Add xref once it's allowed.
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ In setups where any I/O to non-optimized paths results in I/O system errors, you
|
||||
|
||||
[IMPORTANT]
|
||||
====
|
||||
On IBM Z and LinuxONE, you can enable multipathing only if you configured your cluster for it during installation. For more information, see "Installing {op-system} and starting the {product-title} bootstrap process" in _Installing a cluster with z/VM on IBM Z and LinuxONE_.
|
||||
On {ibmzProductName} and {linuxoneProductName}, you can enable multipathing only if you configured your cluster for it during installation. For more information, see "Installing {op-system} and starting the {product-title} bootstrap process" in _Installing a cluster with z/VM on {ibmzProductName} and {linuxoneProductName}_.
|
||||
====
|
||||
// Add xref once it's allowed.
|
||||
|
||||
@@ -28,7 +28,7 @@ The following procedure enables multipath at installation time and appends kerne
|
||||
+
|
||||
[NOTE]
|
||||
====
|
||||
{product-title} does not support enabling multipathing as a day-2 activity on nodes that have been upgraded from 4.6 or earlier.
|
||||
{product-title} does not support enabling multipathing as a day-2 activity on nodes that have been upgraded from 4.6 or earlier.
|
||||
====
|
||||
|
||||
* You are logged in to the cluster as a user with administrative privileges.
|
||||
|
||||
@@ -63,11 +63,11 @@ rules:
|
||||
- list
|
||||
EOD
|
||||
----
|
||||
<1> The Operator image.
|
||||
* For IBM Power: `quay.io/ibm/operator-registry-ppc64le:release-4.9`
|
||||
* For IBM Z and LinuxONE: `quay.io/ibm/operator-registry-s390x:release-4.8`
|
||||
<1> The Operator image.
|
||||
* For {ibmpowerProductName}: `quay.io/ibm/operator-registry-ppc64le:release-4.9`
|
||||
* For {ibmzProductName} and {linuxoneProductName}: `quay.io/ibm/operator-registry-s390x:release-4.8`
|
||||
|
||||
.Verification
|
||||
.Verification
|
||||
|
||||
. After the operator is installed, list the operator subscriptions in the `openshift-operators` namespace:
|
||||
+
|
||||
|
||||
@@ -17,7 +17,7 @@ After GPU resources are enabled for your {product-title} cluster, you can specif
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
Using NVIDIA GPU resources is not supported for IBM Z and IBM Power.
|
||||
Using NVIDIA GPU resources is not supported for {ibmzProductName} and {ibmpowerProductName}.
|
||||
====
|
||||
|
||||
.Procedure
|
||||
|
||||
@@ -46,14 +46,14 @@ For {op-system-base-full}, you can install the Knative (`kn`) CLI as an RPM by u
|
||||
# subscription-manager repos --enable="openshift-serverless-1-for-rhel-8-x86_64-rpms"
|
||||
----
|
||||
+
|
||||
* Linux on IBM Z and LinuxONE (s390x)
|
||||
* Linux on {ibmzProductName} and {linuxoneProductName} (s390x)
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
# subscription-manager repos --enable="openshift-serverless-1-for-rhel-8-s390x-rpms"
|
||||
----
|
||||
+
|
||||
* Linux on IBM Power (ppc64le)
|
||||
* Linux on {ibmpowerProductName} (ppc64le)
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
|
||||
@@ -29,9 +29,9 @@ $ kn: No such file or directory
|
||||
--
|
||||
* link:https://mirror.openshift.com/pub/openshift-v4/clients/serverless/latest/kn-linux-amd64.tar.gz[Linux (x86_64, amd64)]
|
||||
|
||||
* link:https://mirror.openshift.com/pub/openshift-v4/clients/serverless/latest/kn-linux-s390x.tar.gz[Linux on IBM Z and LinuxONE (s390x)]
|
||||
* link:https://mirror.openshift.com/pub/openshift-v4/clients/serverless/latest/kn-linux-s390x.tar.gz[Linux on {ibmzProductName} and {linuxoneProductName} (s390x)]
|
||||
|
||||
* link:https://mirror.openshift.com/pub/openshift-v4/clients/serverless/latest/kn-linux-ppc64le.tar.gz[Linux on IBM Power (ppc64le)]
|
||||
* link:https://mirror.openshift.com/pub/openshift-v4/clients/serverless/latest/kn-linux-ppc64le.tar.gz[Linux on {ibmpowerProductName} (ppc64le)]
|
||||
--
|
||||
+
|
||||
You can also download any version of `kn` by navigating to that version's corresponding directory in the link:https://mirror.openshift.com/pub/openshift-v4/clients/serverless/[Serverless client download mirror].
|
||||
|
||||
@@ -14,7 +14,7 @@ Knative Kafka provides integration options for you to use supported versions of
|
||||
ifdef::openshift-enterprise[]
|
||||
[NOTE]
|
||||
====
|
||||
Knative Kafka is not currently supported for IBM Z and IBM Power.
|
||||
Knative Kafka is not currently supported for {ibmzProductName} and {ibmpowerProductName}.
|
||||
====
|
||||
endif::[]
|
||||
|
||||
|
||||
@@ -44,8 +44,8 @@ In {product-title} {product-version}, you can install a cluster that uses user-p
|
||||
* VMware vSphere
|
||||
* VMware Cloud on AWS
|
||||
* Bare metal
|
||||
* IBM Z or LinuxONE
|
||||
* IBM Power
|
||||
* {ibmzProductName} or {linuxoneProductName}
|
||||
* {ibmpowerProductName}
|
||||
|
||||
Depending on the supported cases for the platform, installations on user-provisioned infrastructure allow you to run machines with full internet access, place your cluster behind a proxy, or perform a _restricted network installation_. In a restricted network installation, you can download the images that are required to install a cluster, place them in a mirror registry, and use that data to install your cluster. While you require internet access to pull images for platform containers, with a restricted network installation on vSphere or bare metal infrastructure, your cluster machines do not require direct internet access.
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ The Kubernetes NMState Operator provides a Kubernetes API for performing state-d
|
||||
|
||||
[IMPORTANT]
|
||||
====
|
||||
Red Hat supports the Kubernetes NMState Operator in production environments on bare-metal, IBM Power, IBM Z, LinuxONE, VMware vSphere, and OpenStack installations.
|
||||
Red Hat supports the Kubernetes NMState Operator in production environments on bare-metal, {ibmpowerProductName}, {ibmzProductName}, {linuxoneProductName}, VMware vSphere, and OpenStack installations.
|
||||
====
|
||||
|
||||
Before you can use NMState with {product-title}, you must install the Kubernetes NMState Operator.
|
||||
|
||||
@@ -49,7 +49,7 @@ Infrastructure features:: Disconnected
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
If you are using OLM in a restricted network on IBM Z, you must have at least 12 GB allocated to the directory where you place your registry.
|
||||
If you are using OLM in a restricted network on {ibmzProductName}, you must have at least 12 GB allocated to the directory where you place your registry.
|
||||
====
|
||||
|
||||
include::modules/olm-restricted-networks-configuring-operatorhub.adoc[leveloffset=+1]
|
||||
|
||||
@@ -15,7 +15,7 @@ You complete most of the cluster configuration and customization after you deplo
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
If you install your cluster on IBM Z, not all features and functions are available.
|
||||
If you install your cluster on {ibmzProductName}, not all features and functions are available.
|
||||
====
|
||||
|
||||
You modify the configuration resources to configure the major features of the
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
:_content-type: ASSEMBLY
|
||||
[id="post-install-configure-additional-devices-ibmz"]
|
||||
= Configuring additional devices in an {ibmzProductName} or LinuxONE environment
|
||||
= Configuring additional devices in an {ibmzProductName} or {linuxoneProductName} environment
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: post-install-configure-additional-devices-ibmz
|
||||
|
||||
toc::[]
|
||||
|
||||
After installing {product-title}, you can configure additional devices for your cluster in an {ibmzProductName} or LinuxONE environment, which is installed with z/VM. The following devices can be configured:
|
||||
After installing {product-title}, you can configure additional devices for your cluster in an {ibmzProductName} or {linuxoneProductName} environment, which is installed with z/VM. The following devices can be configured:
|
||||
|
||||
* Fibre Channel Protocol (FCP) host
|
||||
* FCP LUN
|
||||
@@ -17,13 +17,13 @@ You can configure devices by adding udev rules using the Machine Config Operator
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
The procedures described here apply only to z/VM installations. If you have installed your cluster with {op-system-base} KVM on {ibmzProductName} or LinuxONE infrastructure, no additional configuration is needed inside the KVM guest after the devices were added to the KVM guests. However, both in z/VM and {op-system-base} KVM environments the next steps to configure the Local Storage Operator and Kubernetes NMState Operator need to be applied.
|
||||
The procedures described here apply only to z/VM installations. If you have installed your cluster with {op-system-base} KVM on {ibmzProductName} or {linuxoneProductName} infrastructure, no additional configuration is needed inside the KVM guest after the devices were added to the KVM guests. However, both in z/VM and {op-system-base} KVM environments the next steps to configure the Local Storage Operator and Kubernetes NMState Operator need to be applied.
|
||||
====
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
* xref:../post_installation_configuration/machine-configuration-tasks.adoc#post-install-machine-configuration-tasks[Post-installation machine configuration tasks]
|
||||
* xref:../post_installation_configuration/machine-configuration-tasks.adoc#post-install-machine-configuration-tasks[Post-installation machine configuration tasks]
|
||||
|
||||
include::modules/ibmz-configure-devices-mco.adoc[leveloffset=+1]
|
||||
|
||||
@@ -39,8 +39,8 @@ include::modules/ibmz-configure-devices-manually.adoc[leveloffset=+1]
|
||||
See link:https://www.ibm.com/docs/en/linux-on-systems?topic=linuxonibm/com.ibm.linux.z.ludd/ludd_c_perscfg.html[Persistent device configuration] in IBM Documentation.
|
||||
|
||||
[id="roce-network-cards"]
|
||||
== RoCE network Cards
|
||||
RoCE (RDMA over Converged Ethernet) network cards do not need to be enabled and their interfaces can be configured with the Kubernetes NMState Operator whenever they are available in the node. For example, RoCE network cards are available if they are attached in a z/VM environment or passed through in a {op-system-base} KVM environment.
|
||||
== RoCE network Cards
|
||||
RoCE (RDMA over Converged Ethernet) network cards do not need to be enabled and their interfaces can be configured with the Kubernetes NMState Operator whenever they are available in the node. For example, RoCE network cards are available if they are attached in a z/VM environment or passed through in a {op-system-base} KVM environment.
|
||||
|
||||
include::modules/ibmz-enable-multipathing-fcp-luns.adoc[leveloffset=+1]
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
:_content-type: ASSEMBLY
|
||||
[id="ibm-z-recommended-host-practices"]
|
||||
= Recommended host practices for IBM Z & LinuxONE environments
|
||||
= Recommended host practices for {ibmzProductName} & {linuxoneProductName} environments
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: ibm-z-recommended-host-practices
|
||||
|
||||
toc::[]
|
||||
|
||||
This topic provides recommended host practices for {product-title} on IBM Z and LinuxONE.
|
||||
This topic provides recommended host practices for {product-title} on {ibmzProductName} and {linuxoneProductName}.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
@@ -15,7 +15,7 @@ The s390x architecture is unique in many aspects. Therefore, some recommendation
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
Unless stated otherwise, these practices apply to both z/VM and {op-system-base-full} KVM installations on IBM Z and LinuxONE.
|
||||
Unless stated otherwise, these practices apply to both z/VM and {op-system-base-full} KVM installations on {ibmzProductName} and {linuxoneProductName}.
|
||||
====
|
||||
|
||||
include::modules/ibm-z-managing-cpu-overcommitment.adoc[leveloffset=+1]
|
||||
|
||||
@@ -14,7 +14,7 @@ In addition to the Knative Eventing components that are provided as part of a co
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
Knative Kafka is not currently supported for IBM Z and IBM Power.
|
||||
Knative Kafka is not currently supported for {ibmzProductName} and {ibmpowerProductName}.
|
||||
====
|
||||
endif::[]
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ You can use WebAssembly extensions to add new features directly into the {SMProd
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
WebAssembly extensions are not supported on IBM Z and IBM Power Systems.
|
||||
WebAssembly extensions are not supported on {ibmzProductName} and {ibmpowerProductName}.
|
||||
====
|
||||
|
||||
include::modules/ossm-extensions-overview.adoc[leveloffset=+1]
|
||||
|
||||
@@ -19,8 +19,8 @@ ifdef::openshift-enterprise[]
|
||||
** xref:../../installing/installing_aws/installing-aws-user-infra.adoc#installing-aws-user-infra[Install {product-title} {product-version} on user-provisioned AWS]
|
||||
** xref:../../installing/installing_bare_metal/installing-bare-metal.adoc#installing-bare-metal[Install {product-title} {product-version} on bare metal]
|
||||
** xref:../../installing/installing_vsphere/installing-vsphere.adoc#installing-vsphere[Install {product-title} {product-version} on vSphere]
|
||||
** xref:../../installing/installing_ibm_z/installing-ibm-z.adoc#installing-ibm-z[Install {product-title} {product-version} on IBM Z and LinuxONE]
|
||||
** xref:../../installing/installing_ibm_power/installing-ibm-power.adoc#installing-ibm-power[Install {product-title} {product-version} on IBM Power]
|
||||
** xref:../../installing/installing_ibm_z/installing-ibm-z.adoc#installing-ibm-z[Install {product-title} {product-version} on {ibmzProductName} and {linuxoneProductName}]
|
||||
** xref:../../installing/installing_ibm_power/installing-ibm-power.adoc#installing-ibm-power[Install {product-title} {product-version} on {ibmpowerProductName}]
|
||||
endif::[]
|
||||
|
||||
* Install the version of the {product-title} command line utility (the `oc` client tool) that matches your {product-title} version and add it to your path.
|
||||
|
||||
@@ -92,7 +92,7 @@ You can also deploy a cluster on AWS infrastructure that you provisioned yoursel
|
||||
ifndef::openshift-origin[]
|
||||
- **xref:../installing/installing_ibm_cloud_public/preparing-to-install-on-ibm-cloud.adoc#preparing-to-install-on-ibm-cloud[Install a cluster on IBM Cloud VPC]**: You can install {product-title} on IBM Cloud VPC on installer-provisioned infrastructure.
|
||||
|
||||
- **xref:../installing/installing_ibm_power/installing-ibm-power.adoc#installing-ibm-power[Install a cluster on IBM Power]**: You can install {product-title} on IBM Power on user-provisioned infrastructure.
|
||||
- **xref:../installing/installing_ibm_power/installing-ibm-power.adoc#installing-ibm-power[Install a cluster on {ibmpowerProductName}]**: You can install {product-title} on {ibmpowerProductName} on user-provisioned infrastructure.
|
||||
endif::openshift-origin[]
|
||||
|
||||
- **xref:../installing/installing_vsphere/installing-vsphere-installer-provisioned.adoc#installing-vsphere-installer-provisioned[Install a cluster on VMware vSphere]**: You can install {product-title} on supported versions of vSphere.
|
||||
@@ -100,9 +100,9 @@ endif::openshift-origin[]
|
||||
- **xref:../installing/installing_vmc/preparing-to-install-on-vmc.adoc#preparing-to-install-on-vmc[Install a cluster on VMware Cloud]**: You can install OpenShift Container Platform on supported versions of VMware Cloud (VMC) on AWS.
|
||||
|
||||
ifndef::openshift-origin[]
|
||||
- **xref:../installing/installing_ibm_z/installing-ibm-z.adoc#installing-ibm-z[Install a cluster with z/VM on IBM Z and LinuxONE]**: You can install {product-title} with z/VM on IBM Z and LinuxONE on user-provisioned infrastructure.
|
||||
- **xref:../installing/installing_ibm_z/installing-ibm-z.adoc#installing-ibm-z[Install a cluster with z/VM on {ibmzProductName} and {linuxoneProductName}]**: You can install {product-title} with z/VM on {ibmzProductName} and {linuxoneProductName} on user-provisioned infrastructure.
|
||||
|
||||
- **xref:../installing/installing_ibm_z/installing-ibm-z-kvm.adoc#installing-ibm-z-kvm[Install a cluster with RHEL KVM on IBM Z and LinuxONE]**: You can install {product-title} with RHEL KVM on IBM Z and LinuxONE on user-provisioned infrastructure.
|
||||
- **xref:../installing/installing_ibm_z/installing-ibm-z-kvm.adoc#installing-ibm-z-kvm[Install a cluster with RHEL KVM on {ibmzProductName} and {linuxoneProductName}]**: You can install {product-title} with RHEL KVM on {ibmzProductName} and {linuxoneProductName} on user-provisioned infrastructure.
|
||||
endif::openshift-origin[]
|
||||
|
||||
- **xref:../installing/installing_bare_metal_ipi/ipi-install-overview.adoc#ipi-install-overview[Install an installer-provisioned cluster on bare metal]**: You can install {product-title} on bare metal with an installer-provisioned architecture.
|
||||
@@ -131,7 +131,7 @@ user-provisioned infrastructure on
|
||||
xref:../installing/installing_aws/installing-restricted-networks-aws.adoc#installing-restricted-networks-aws[AWS],
|
||||
xref:../installing/installing_gcp/installing-restricted-networks-gcp.adoc#installing-restricted-networks-gcp[GCP],
|
||||
xref:../installing/installing_vsphere/installing-restricted-networks-vsphere.adoc#installing-restricted-networks-vsphere[vSphere],
|
||||
xref:../installing/installing_ibm_z/installing-restricted-networks-ibm-z.adoc#installing-restricted-networks-ibm-z[IBM Z and LinuxONE with z/VM], xref:../installing/installing_ibm_z/installing-restricted-networks-ibm-z-kvm.adoc#installing-restricted-networks-ibm-z-kvm[IBM Z and LinuxONE with RHEL KVM], xref:../installing/installing_ibm_power/installing-restricted-networks-ibm-power.adoc#installing-restricted-networks-ibm-power[IBM Power],
|
||||
xref:../installing/installing_ibm_z/installing-restricted-networks-ibm-z.adoc#installing-restricted-networks-ibm-z[{ibmzProductName} and {linuxoneProductName} with z/VM], xref:../installing/installing_ibm_z/installing-restricted-networks-ibm-z-kvm.adoc#installing-restricted-networks-ibm-z-kvm[{ibmzProductName} and {linuxoneProductName} with RHEL KVM], xref:../installing/installing_ibm_power/installing-restricted-networks-ibm-power.adoc#installing-restricted-networks-ibm-power[{ibmpowerProductName}],
|
||||
or
|
||||
xref:../installing/installing_bare_metal/installing-restricted-networks-bare-metal.adoc#installing-restricted-networks-bare-metal[bare metal]
|
||||
does not have full access to the internet, then mirror the OpenShift Container Platform installation images using one of the following methods and install a cluster in a restricted network.
|
||||
|
||||
Reference in New Issue
Block a user