From 8ed47ecbf8b57f0e41bfa91d952e58c8cc2b46bb Mon Sep 17 00:00:00 2001 From: SNiemann15 Date: Thu, 7 Nov 2024 14:13:30 +0100 Subject: [PATCH] sync ibm z file names --- .../hcp-deploy/hcp-deploy-ibmz.adoc | 18 +++++++++--------- .../hcp-destroy/hcp-destroy-ibmz.adoc | 2 +- .../disconnected-install-ibmz-hcp.adoc | 11 ++++++----- .../installing_ibm_z/ibmz-post-install.adoc | 10 +++++----- .../installing_ibm_z/installing-ibm-z-kvm.adoc | 11 +++-------- .../installing-ibm-z-lpar.adoc | 2 +- .../installing_ibm_z/installing-ibm-z.adoc | 8 ++------ ...stalling-restricted-networks-ibm-z-kvm.adoc | 10 +++------- ...talling-restricted-networks-ibm-z-lpar.adoc | 4 ++-- .../installing-restricted-networks-ibm-z.adoc | 4 ++-- .../install-sno-installing-sno.adoc | 2 +- .../prepare-pxe-assets-agent.adoc | 4 ++-- ...agent.adoc => adding-ibm-z-lpar-agent.adoc} | 2 +- ...> configuring-network-overrides-ibm-z.adoc} | 2 +- ...ibmz-cli.adoc => destroy-hc-ibm-z-cli.adoc} | 0 modules/hcp-bm-hc.adoc | 2 +- ...hcp-ibm-z-adding-credentials-registry.adoc} | 4 ++-- ...hcp-ibm-z-adding-reg-ca-hostedcluster.adoc} | 6 +++--- ...-prereqs.adoc => hcp-ibm-z-dc-prereqs.adoc} | 4 ++-- .../{hcp-ibmz-dns.adoc => hcp-ibm-z-dns.adoc} | 2 +- ...fra-reqs.adoc => hcp-ibm-z-infra-reqs.adoc} | 2 +- ...z-infraenv.adoc => hcp-ibm-z-infraenv.adoc} | 2 +- ...m-agents.adoc => hcp-ibm-z-kvm-agents.adoc} | 2 +- ...-agents.adoc => hcp-ibm-z-lpar-agents.adoc} | 2 +- ...bmz-prereqs.adoc => hcp-ibm-z-prereqs.adoc} | 2 +- ...z-scale-np.adoc => hcp-ibm-z-scale-np.adoc} | 2 +- ...eg-ca.adoc => hcp-ibm-z-update-reg-ca.adoc} | 4 ++-- ...m-agents.adoc => hcp-ibm-z-zvm-agents.adoc} | 6 +++--- ...c => ibm-z-configure-devices-manually.adoc} | 2 +- ...o.adoc => ibm-z-configure-devices-mco.adoc} | 2 +- ...> ibm-z-configure-nbde-with-static-ip.adoc} | 2 +- ...=> ibm-z-enable-multipathing-fcp-luns.adoc} | 2 +- modules/installing-ocp-agent-ibm-z.adoc | 2 +- 33 files changed, 64 insertions(+), 76 deletions(-) rename modules/{adding-ibmz-lpar-agent.adoc => adding-ibm-z-lpar-agent.adoc} (98%) rename modules/{configuring-network-overrides-ibmz.adoc => configuring-network-overrides-ibm-z.adoc} (92%) rename modules/{destroy-hc-ibmz-cli.adoc => destroy-hc-ibm-z-cli.adoc} (100%) rename modules/{hcp-ibmz-adding-credentials-registry.adoc => hcp-ibm-z-adding-credentials-registry.adoc} (94%) rename modules/{hcp-ibmz-adding-reg-ca-hostedcluster.adoc => hcp-ibm-z-adding-reg-ca-hostedcluster.adoc} (96%) rename modules/{hcp-ibmz-dc-prereqs.adoc => hcp-ibm-z-dc-prereqs.adoc} (77%) rename modules/{hcp-ibmz-dns.adoc => hcp-ibm-z-dns.adoc} (97%) rename modules/{hcp-ibmz-infra-reqs.adoc => hcp-ibm-z-infra-reqs.adoc} (94%) rename modules/{hcp-ibmz-infraenv.adoc => hcp-ibm-z-infraenv.adoc} (97%) rename modules/{hcp-ibmz-kvm-agents.adoc => hcp-ibm-z-kvm-agents.adoc} (98%) rename modules/{hcp-ibmz-lpar-agents.adoc => hcp-ibm-z-lpar-agents.adoc} (98%) rename modules/{hcp-ibmz-prereqs.adoc => hcp-ibm-z-prereqs.adoc} (97%) rename modules/{hcp-ibmz-scale-np.adoc => hcp-ibm-z-scale-np.adoc} (99%) rename modules/{hcp-ibmz-update-reg-ca.adoc => hcp-ibm-z-update-reg-ca.adoc} (97%) rename modules/{hcp-ibmz-zvm-agents.adoc => hcp-ibm-z-zvm-agents.adoc} (96%) rename modules/{ibmz-configure-devices-manually.adoc => ibm-z-configure-devices-manually.adoc} (95%) rename modules/{ibmz-configure-devices-mco.adoc => ibm-z-configure-devices-mco.adoc} (99%) rename modules/{ibmz-configure-nbde-with-static-ip.adoc => ibm-z-configure-nbde-with-static-ip.adoc} (99%) rename modules/{ibmz-enable-multipathing-fcp-luns.adoc => ibm-z-enable-multipathing-fcp-luns.adoc} (97%) diff --git a/hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc b/hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc index 56f042b08e..7337504615 100644 --- a/hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc +++ b/hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc @@ -23,7 +23,7 @@ Each {ibm-z-title} system host must be started with the PXE images provided by t When you create a hosted cluster with the Agent platform, HyperShift Operator installs the Agent Cluster API provider in the hosted control plane namespace. -include::modules/hcp-ibmz-prereqs.adoc[leveloffset=+1] +include::modules/hcp-ibm-z-prereqs.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources @@ -33,35 +33,35 @@ include::modules/hcp-ibmz-prereqs.adoc[leveloffset=+1] * xref:../../hosted_control_planes/hcp-prepare/hcp-cli.adoc#hcp-cli-terminal_hcp-cli[Installing the {hcp} command-line interface] * xref:../../hosted_control_planes/hcp-prepare/hcp-enable-disable.adoc[Enabling or disabling the {hcp} feature] -include::modules/hcp-ibmz-infra-reqs.adoc[leveloffset=+1] +include::modules/hcp-ibm-z-infra-reqs.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources * xref:../../hosted_control_planes/hcp-prepare/hcp-enable-disable.adoc[Enabling or disabling the {hcp} feature] -include::modules/hcp-ibmz-dns.adoc[leveloffset=+1] +include::modules/hcp-ibm-z-dns.adoc[leveloffset=+1] include::modules/hcp-bm-hc.adoc[leveloffset=+1] -include::modules/hcp-ibmz-infraenv.adoc[leveloffset=+1] +include::modules/hcp-ibm-z-infraenv.adoc[leveloffset=+1] -[id="hcp-ibmz-add-agents"] +[id="hcp-ibm-z-add-agents"] == Adding {ibm-z-title} agents to the InfraEnv resource To attach compute nodes to a hosted control plane, create agents that help you to scale the node pool. Adding agents in an {ibm-z-title} environment requires additional steps, which are described in detail in this section. Unless stated otherwise, these procedures apply to both z/VM and RHEL KVM installations on {ibm-z-title} and {ibm-linuxone-title}. -include::modules/hcp-ibmz-kvm-agents.adoc[leveloffset=+2] -include::modules/hcp-ibmz-lpar-agents.adoc[leveloffset=+2] +include::modules/hcp-ibm-z-kvm-agents.adoc[leveloffset=+2] +include::modules/hcp-ibm-z-lpar-agents.adoc[leveloffset=+2] [role="_additional-resources"] .Additional resources * link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/performing_a_standard_rhel_8_installation/installing-in-an-lpar_installing-rhel[Installing in an LPAR] -include::modules/hcp-ibmz-zvm-agents.adoc[leveloffset=+2] +include::modules/hcp-ibm-z-zvm-agents.adoc[leveloffset=+2] -include::modules/hcp-ibmz-scale-np.adoc[leveloffset=+1] +include::modules/hcp-ibm-z-scale-np.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources diff --git a/hosted_control_planes/hcp-destroy/hcp-destroy-ibmz.adoc b/hosted_control_planes/hcp-destroy/hcp-destroy-ibmz.adoc index 60e2c8f954..12439e1f9f 100644 --- a/hosted_control_planes/hcp-destroy/hcp-destroy-ibmz.adoc +++ b/hosted_control_planes/hcp-destroy/hcp-destroy-ibmz.adoc @@ -8,4 +8,4 @@ toc::[] You can destroy a hosted cluster on `x86` bare metal with {ibm-z-title} compute nodes and its managed cluster resource by using the command-line interface (CLI). -include::modules/destroy-hc-ibmz-cli.adoc[leveloffset=+1] +include::modules/destroy-hc-ibm-z-cli.adoc[leveloffset=+1] diff --git a/hosted_control_planes/hcp-disconnected/disconnected-install-ibmz-hcp.adoc b/hosted_control_planes/hcp-disconnected/disconnected-install-ibmz-hcp.adoc index e6e8775c8d..a034bfcd85 100644 --- a/hosted_control_planes/hcp-disconnected/disconnected-install-ibmz-hcp.adoc +++ b/hosted_control_planes/hcp-disconnected/disconnected-install-ibmz-hcp.adoc @@ -13,21 +13,22 @@ toc::[] * Control plane: Located in the management cluster, where the {hcp} pods are run and managed by the Control Plane Operator. * Data plane: Located in the workers of the hosted cluster, where the workload and a few other pods run, managed by the Hosted Cluster Config Operator. -The `ImageContentSourcePolicy` (ICSP) custom resource for the data plane is managed through the `ImageContentSources` API in the hosted cluster manifest. +The `ImageContentSourcePolicy` (ICSP) custom resource for the data plane is managed through the `ImageContentSources` API in the hosted cluster manifest. For the control plane, ICSP objects are managed in the management cluster. These objects are parsed by the HyperShift Operator and are shared as `registry-overrides` entries with the Control Plane Operator. These entries are injected into any one of the available deployments in the {hcp} namespace as an argument. To work with disconnected registries in the {hcp}, you must first create the appropriate ICSP in the management cluster. Then, to deploy disconnected workloads in the data plane, you need to add the entries that you want into the `ImageContentSources` field in the hosted cluster manifest. -include::modules/hcp-ibmz-dc-prereqs.adoc[leveloffset=+1] +include::modules/hcp-ibm-z-dc-prereqs.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources * xref:../../disconnected/mirroring/installing-mirroring-creating-registry.adoc#mirror-registry-introduction_installing-mirroring-creating-registry[Creating a mirror registry with mirror registry for Red Hat OpenShift] * xref:../../disconnected/mirroring/installing-mirroring-disconnected.adoc#installing-mirroring-disconnected[Mirroring images for a disconnected installation using the oc-mirror plugin] -include::modules/hcp-ibmz-adding-credentials-registry.adoc[leveloffset=+1] -include::modules/hcp-ibmz-update-reg-ca.adoc[leveloffset=+1] +include::modules/hcp-ibm-z-adding-credentials-registry.adoc[leveloffset=+1] -include::modules/hcp-ibmz-adding-reg-ca-hostedcluster.adoc[leveloffset=+1] \ No newline at end of file +include::modules/hcp-ibm-z-update-reg-ca.adoc[leveloffset=+1] + +include::modules/hcp-ibm-z-adding-reg-ca-hostedcluster.adoc[leveloffset=+1] \ No newline at end of file diff --git a/installing/installing_ibm_z/ibmz-post-install.adoc b/installing/installing_ibm_z/ibmz-post-install.adoc index cce73c28ff..0a7b0a1834 100644 --- a/installing/installing_ibm_z/ibmz-post-install.adoc +++ b/installing/installing_ibm_z/ibmz-post-install.adoc @@ -1,8 +1,8 @@ :_mod-docs-content-type: ASSEMBLY include::_attributes/common-attributes.adoc[] -[id="post-install-configure-additional-devices-ibmz"] +[id="post-install-configure-additional-devices-ibm-z"] = Configuring additional devices in an {ibm-z-title} or {ibm-linuxone-title} environment -:context: post-install-configure-additional-devices-ibmz +:context: post-install-configure-additional-devices-ibm-z toc::[] @@ -25,14 +25,14 @@ The procedures described here apply only to z/VM installations. If you have inst * xref:../../machine_configuration/index.adoc#machine-config-overview[Machine configuration overview] -include::modules/ibmz-configure-devices-mco.adoc[leveloffset=+1] +include::modules/ibm-z-configure-devices-mco.adoc[leveloffset=+1] .Next steps * xref:../../storage/persistent_storage/persistent_storage_local/persistent-storage-local.adoc#persistent-storage-using-local-volume[Install and configure the Local Storage Operator] * xref:../../networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc#k8s-nmstate-updating-node-network-config[Observing and updating the node network state and configuration] -include::modules/ibmz-configure-devices-manually.adoc[leveloffset=+1] +include::modules/ibm-z-configure-devices-manually.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources @@ -45,7 +45,7 @@ include::modules/ibmz-configure-devices-manually.adoc[leveloffset=+1] == 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] +include::modules/ibm-z-enable-multipathing-fcp-luns.adoc[leveloffset=+1] .Next steps diff --git a/installing/installing_ibm_z/installing-ibm-z-kvm.adoc b/installing/installing_ibm_z/installing-ibm-z-kvm.adoc index b2c1b004d9..1120f4a5ea 100644 --- a/installing/installing_ibm_z/installing-ibm-z-kvm.adoc +++ b/installing/installing_ibm_z/installing-ibm-z-kvm.adoc @@ -42,7 +42,6 @@ include::modules/installation-requirements-user-infra-ibm-z-kvm.adoc[leveloffset include::modules/csr-management.adoc[leveloffset=+2] [role="_additional-resources"] -[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 {ibm-z-name} & {ibm-linuxone-name} environments] @@ -50,7 +49,6 @@ include::modules/csr-management.adoc[leveloffset=+2] include::modules/installation-network-user-infra.adoc[leveloffset=+2] [role="_additional-resources"] -[id="additional-resources_ibmz-kvm-chrony-time-service"] .Additional resources * xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service] @@ -90,19 +88,17 @@ include::modules/installation-ibm-z-kvm-user-infra-installing-rhcos.adoc[levelof include::modules/ibm-z-secure-execution.adoc[leveloffset=+2] [role="_additional-resources"] -[id="additional-resources_Linux-as-an-IBM-Secure-Execution-host-or-guest"] .Additional resources * link:https://www.ibm.com/docs/en/linux-on-systems?topic=virtualization-secure-execution[Introducing {ibm-name} Secure Execution for Linux] -* link:https://www.ibm.com/docs/en/linux-on-systems?topic=ibmz-secure-execution[Linux as an {ibm-name} Secure Execution host or guest] +* link:https://www.ibm.com/docs/en/linux-on-systems?topic=ibm-z-secure-execution[Linux as an {ibm-name} Secure Execution host or guest] * link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_and_managing_virtualization/securing-virtual-machines-in-rhel_configuring-and-managing-virtualization#setting-up-secure-execution-on-ibm-z_securing-virtual-machines-in-rhel[Setting up {ibm-name} Secure Execution on {ibm-z-title}] -include::modules/ibmz-configure-nbde-with-static-ip.adoc[leveloffset=+2] +include::modules/ibm-z-configure-nbde-with-static-ip.adoc[leveloffset=+2] [role="_additional-resources"] -[id="additional-resources_configure-nbde-ibm-z-kvm"] .Additional resources * xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-butane_installing-customizing[Creating machine configs with Butane] @@ -132,14 +128,13 @@ include::modules/installation-complete-user-infra.adoc[leveloffset=+1] include::modules/cluster-telemetry.adoc[leveloffset=+1] [role="_additional-resources"] -[id="additional-resources_ibmz-kvm-remote-health-monitoring"] .Additional resources * See xref:../../support/remote_health_monitoring/about-remote-health-monitoring.adoc#about-remote-health-monitoring[About remote health monitoring] for more information about the Telemetry service * link:https://access.redhat.com/solutions/4387261[How to generate SOSREPORT within OpenShift4 nodes without SSH]. -[id="next-steps_ibmz-kvm"] +[id="next-steps_ibm-z-kvm"] == Next steps * xref:../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster]. diff --git a/installing/installing_ibm_z/installing-ibm-z-lpar.adoc b/installing/installing_ibm_z/installing-ibm-z-lpar.adoc index 2211505f08..bf52fd73bb 100644 --- a/installing/installing_ibm_z/installing-ibm-z-lpar.adoc +++ b/installing/installing_ibm_z/installing-ibm-z-lpar.adoc @@ -102,7 +102,7 @@ include::modules/nw-operator-cr.adoc[leveloffset=+1] include::modules/installation-user-infra-generate-k8s-manifest-ignition.adoc[leveloffset=+1] -include::modules/ibmz-configure-nbde-with-static-ip.adoc[leveloffset=+1] +include::modules/ibm-z-configure-nbde-with-static-ip.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources diff --git a/installing/installing_ibm_z/installing-ibm-z.adoc b/installing/installing_ibm_z/installing-ibm-z.adoc index 93342aad55..e642020f3c 100644 --- a/installing/installing_ibm_z/installing-ibm-z.adoc +++ b/installing/installing_ibm_z/installing-ibm-z.adoc @@ -57,7 +57,6 @@ include::modules/preferred-ibm-z-system-requirements.adoc[leveloffset=+2] include::modules/csr-management.adoc[leveloffset=+2] [role="_additional-resources"] -[id="additional-resources_ibmz-requirements"] .Additional resources * See link:https://www.ibm.com/docs/en/zvm/latest?topic=networks-bridging-hipersockets-lan-zvm-virtual-switch[Bridging a HiperSockets LAN with a z/VM Virtual Switch] in {ibm-name} Documentation. @@ -71,7 +70,6 @@ include::modules/csr-management.adoc[leveloffset=+2] include::modules/installation-network-user-infra.adoc[leveloffset=+2] [role="_additional-resources"] -[id="additional-resources_ibmz-chrony-time-service"] .Additional resources * xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service] @@ -106,10 +104,9 @@ include::modules/nw-operator-cr.adoc[leveloffset=+1] include::modules/installation-user-infra-generate-k8s-manifest-ignition.adoc[leveloffset=+1] -include::modules/ibmz-configure-nbde-with-static-ip.adoc[leveloffset=+1] +include::modules/ibm-z-configure-nbde-with-static-ip.adoc[leveloffset=+1] [role="_additional-resources"] -[id="additional-resources_configure-nbde-ibm-z"] .Additional resources * xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-butane_installing-customizing[Creating machine configs with Butane] @@ -137,14 +134,13 @@ include::modules/installation-complete-user-infra.adoc[leveloffset=+1] include::modules/cluster-telemetry.adoc[leveloffset=+1] [role="_additional-resources"] -[id="additional-resources_ibmz-remote-health-monitoring"] .Additional resources * See xref:../../support/remote_health_monitoring/about-remote-health-monitoring.adoc#about-remote-health-monitoring[About remote health monitoring] for more information about the Telemetry service * link:https://access.redhat.com/solutions/4387261[How to generate SOSREPORT within OpenShift4 nodes without SSH]. -[id="next-steps_ibmz-vm"] +[id="next-steps_ibm-z-vm"] == Next steps * xref:../../machine_configuration/machine-configs-configure.adoc#rhcos-enabling-multipath-day-2_machine-configs-configure[Enabling multipathing with kernel arguments on {op-system}]. diff --git a/installing/installing_ibm_z/installing-restricted-networks-ibm-z-kvm.adoc b/installing/installing_ibm_z/installing-restricted-networks-ibm-z-kvm.adoc index 827d9d648a..70e68797a8 100644 --- a/installing/installing_ibm_z/installing-restricted-networks-ibm-z-kvm.adoc +++ b/installing/installing_ibm_z/installing-restricted-networks-ibm-z-kvm.adoc @@ -49,7 +49,6 @@ include::modules/installation-requirements-user-infra-ibm-z-kvm.adoc[leveloffset include::modules/csr-management.adoc[leveloffset=+2] [role="_additional-resources"] -[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-name} & {ibm-linuxone-name} environments] @@ -57,7 +56,6 @@ include::modules/csr-management.adoc[leveloffset=+2] include::modules/installation-network-user-infra.adoc[leveloffset=+2] [role="_additional-resources"] -[id="additional-resources_ibmz-network-user-infra"] .Additional resources * xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-chrony_installing-customizing[Configuring chrony time service] @@ -97,7 +95,6 @@ include::modules/installation-ibm-z-kvm-user-infra-installing-rhcos.adoc[levelof include::modules/ibm-z-secure-execution.adoc[leveloffset=+2] [role="_additional-resources"] -[id="additional-resources_Linux-as-an-IBM-Secure-Execution-host-or-guest-restricted"] .Additional resources * link:https://www.ibm.com/docs/en/linux-on-systems?topic=virtualization-secure-execution[Introducing {ibm-name} Secure Execution for Linux] @@ -106,10 +103,9 @@ include::modules/ibm-z-secure-execution.adoc[leveloffset=+2] * link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_and_managing_virtualization/securing-virtual-machines-in-rhel_configuring-and-managing-virtualization#setting-up-secure-execution-on-ibm-z_securing-virtual-machines-in-rhel[Setting up {ibm-name} Secure Execution on {ibm-z-title}] -include::modules/ibmz-configure-nbde-with-static-ip.adoc[leveloffset=+2] +include::modules/ibm-z-configure-nbde-with-static-ip.adoc[leveloffset=+2] [role="_additional-resources"] -[id="additional-resources_configure-nbde-ibm-z-kvm-restricted"] .Additional resources * xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-butane_installing-customizing[Creating machine configs with Butane] @@ -139,12 +135,12 @@ include::modules/installation-registry-storage-non-production.adoc[leveloffset=+ include::modules/installation-complete-user-infra.adoc[leveloffset=+1] [role="_additional-resources"] -[id="additional-resources_ibmz-kvm-restricted-sosreport"] +[id="additional-resources_ibm-z-kvm-restricted-sosreport"] .Additional resources * link:https://access.redhat.com/solutions/4387261[How to generate SOSREPORT within {product-title} version 4 nodes without SSH]. -[id="next-steps_ibmz-kvm-restricted"] +[id="next-steps_ibm-z-kvm-restricted"] == Next steps * xref:../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster]. diff --git a/installing/installing_ibm_z/installing-restricted-networks-ibm-z-lpar.adoc b/installing/installing_ibm_z/installing-restricted-networks-ibm-z-lpar.adoc index 7baee4d5f4..f1710d4f9d 100644 --- a/installing/installing_ibm_z/installing-restricted-networks-ibm-z-lpar.adoc +++ b/installing/installing_ibm_z/installing-restricted-networks-ibm-z-lpar.adoc @@ -111,7 +111,7 @@ include::modules/nw-operator-cr.adoc[leveloffset=+1] include::modules/installation-user-infra-generate-k8s-manifest-ignition.adoc[leveloffset=+1] -include::modules/ibmz-configure-nbde-with-static-ip.adoc[leveloffset=+1] +include::modules/ibm-z-configure-nbde-with-static-ip.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources @@ -145,7 +145,7 @@ include::modules/installation-complete-user-infra.adoc[leveloffset=+1] * link:https://access.redhat.com/solutions/4387261[How to generate SOSREPORT within {product-title} version 4 nodes without SSH]. -[id="next-steps_ibmz-lpar-restricted"] +[id="next-steps_ibm-z-lpar-restricted"] == Next steps * xref:../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster]. diff --git a/installing/installing_ibm_z/installing-restricted-networks-ibm-z.adoc b/installing/installing_ibm_z/installing-restricted-networks-ibm-z.adoc index 9eaaab7daf..6dbd6c98bb 100644 --- a/installing/installing_ibm_z/installing-restricted-networks-ibm-z.adoc +++ b/installing/installing_ibm_z/installing-restricted-networks-ibm-z.adoc @@ -112,7 +112,7 @@ include::modules/nw-operator-cr.adoc[leveloffset=+1] include::modules/installation-user-infra-generate-k8s-manifest-ignition.adoc[leveloffset=+1] -include::modules/ibmz-configure-nbde-with-static-ip.adoc[leveloffset=+1] +include::modules/ibm-z-configure-nbde-with-static-ip.adoc[leveloffset=+1] [role="_additional-resources"] [id="additional-resources_Configure-nbde-ibm-z-restricted"] @@ -147,7 +147,7 @@ include::modules/installation-complete-user-infra.adoc[leveloffset=+1] * link:https://access.redhat.com/solutions/4387261[How to generate SOSREPORT within {product-title} version 4 nodes without SSH]. -[id="next-steps_ibmz-restricted"] +[id="next-steps_ibm-z-restricted"] == Next steps * xref:../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster]. diff --git a/installing/installing_sno/install-sno-installing-sno.adoc b/installing/installing_sno/install-sno-installing-sno.adoc index 1f74244f75..26b54623d8 100644 --- a/installing/installing_sno/install-sno-installing-sno.adoc +++ b/installing/installing_sno/install-sno-installing-sno.adoc @@ -140,7 +140,7 @@ include::modules/install-booting-from-an-iso-over-http-redfish.adoc[leveloffset= include::modules/creating-custom-live-rhcos-iso.adoc[leveloffset=+1] -[id="install-sno-with-ibmz"] +[id="install-sno-with-ibm-z"] == Installing {sno} with {ibm-z-title} and {ibm-linuxone-title} Installing a single-node cluster on {ibm-z-name} and {ibm-linuxone-name} requires user-provisioned installation using one of the following procedures: diff --git a/installing/installing_with_agent_based_installer/prepare-pxe-assets-agent.adoc b/installing/installing_with_agent_based_installer/prepare-pxe-assets-agent.adoc index b660ad332f..17a1bb7aa0 100644 --- a/installing/installing_with_agent_based_installer/prepare-pxe-assets-agent.adoc +++ b/installing/installing_with_agent_based_installer/prepare-pxe-assets-agent.adoc @@ -39,7 +39,7 @@ include::modules/pxe-assets-ocp-agent.adoc[leveloffset=+1] include::modules/installing-ocp-agent-ibm-z.adoc[leveloffset=+1] // Configuring network overrides in {ibm-z-title} -include::modules/configuring-network-overrides-ibmz.adoc[leveloffset=+2] +include::modules/configuring-network-overrides-ibm-z.adoc[leveloffset=+2] // Adding {ibm-z-title} agents with z/VM include::modules/installing-ocp-agent-ibm-z-zvm.adoc[leveloffset=+2] @@ -53,7 +53,7 @@ include::modules/installing-ocp-agent-ibm-z-zvm.adoc[leveloffset=+2] include::modules/installing-ocp-agent-ibm-z-kvm.adoc[leveloffset=+2] // Adding {ibm-z-title} Logical Partition (LPAR) as agents -include::modules/adding-ibmz-lpar-agent.adoc[leveloffset=+2] +include::modules/adding-ibm-z-lpar-agent.adoc[leveloffset=+2] [role="_additional-resources"] .Additional resources diff --git a/modules/adding-ibmz-lpar-agent.adoc b/modules/adding-ibm-z-lpar-agent.adoc similarity index 98% rename from modules/adding-ibmz-lpar-agent.adoc rename to modules/adding-ibm-z-lpar-agent.adoc index 6956149162..139758db37 100644 --- a/modules/adding-ibmz-lpar-agent.adoc +++ b/modules/adding-ibm-z-lpar-agent.adoc @@ -3,7 +3,7 @@ // * installing/installing_with_agent_based_installer/prepare-pxe-infra-agent.adoc :_mod-docs-content-type: PROCEDURE -[id="adding-ibmz-lpar-agents_{context}"] +[id="adding-ibm-z-lpar-agents_{context}"] = Adding {ibm-z-title} agents in a Logical Partition (LPAR) Use the following procedure to manually add {ibm-z-name} agents to your cluster that runs in an LPAR environment. Use this procedure only for {ibm-z-name} clusters running in an LPAR. diff --git a/modules/configuring-network-overrides-ibmz.adoc b/modules/configuring-network-overrides-ibm-z.adoc similarity index 92% rename from modules/configuring-network-overrides-ibmz.adoc rename to modules/configuring-network-overrides-ibm-z.adoc index fad6e0bdd7..0d9a31c2ee 100644 --- a/modules/configuring-network-overrides-ibmz.adoc +++ b/modules/configuring-network-overrides-ibm-z.adoc @@ -5,7 +5,7 @@ [id="configuring-network-overrides-ibm_{context}"] = Configuring network overrides in {ibm-z-title} -You can specify a static IP address on {ibm-z-title} machines that uses Logical Partition (LPAR) and z/VM. This is useful when the network devices do not have a static MAC address assigned to them. +You can specify a static IP address on {ibm-z-title} machines that use Logical Partition (LPAR) and z/VM. This is useful when the network devices do not have a static MAC address assigned to them. .Procedure diff --git a/modules/destroy-hc-ibmz-cli.adoc b/modules/destroy-hc-ibm-z-cli.adoc similarity index 100% rename from modules/destroy-hc-ibmz-cli.adoc rename to modules/destroy-hc-ibm-z-cli.adoc diff --git a/modules/hcp-bm-hc.adoc b/modules/hcp-bm-hc.adoc index 597369bc11..9fcf8ed627 100644 --- a/modules/hcp-bm-hc.adoc +++ b/modules/hcp-bm-hc.adoc @@ -1,7 +1,7 @@ // Module included in the following assemblies: // // * hosted_control_planes/hcp-deploy/hcp-deploy-bm.adoc -// * hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc +// * hosted_control_planes/hcp-deploy/hcp-deploy-ibm-z.adoc // * hosted_control_planes/hcp-deploy/hcp-deploy-ibm-power.adoc :_mod-docs-content-type: PROCEDURE diff --git a/modules/hcp-ibmz-adding-credentials-registry.adoc b/modules/hcp-ibm-z-adding-credentials-registry.adoc similarity index 94% rename from modules/hcp-ibmz-adding-credentials-registry.adoc rename to modules/hcp-ibm-z-adding-credentials-registry.adoc index 8d7710054f..3110462d98 100644 --- a/modules/hcp-ibmz-adding-credentials-registry.adoc +++ b/modules/hcp-ibm-z-adding-credentials-registry.adoc @@ -1,5 +1,5 @@ :_mod-docs-content-type: PROCEDURE -[id="hcp-ibmz-adding-credentials-registry_{context}"] +[id="hcp-ibm-z-adding-credentials-registry_{context}"] = Adding credentials and the registry certificate authority to the management cluster To pull the mirror registry images from the management cluster, you must first add credentials and the certificate authority of the mirror registry to the management cluster. Use the following procedure: @@ -43,7 +43,7 @@ spec: ---- $ oc get secret/pull-secret -n openshift-config -o json | jq -r '.data.".dockerconfigjson"' | base64 -d > authfile ---- -.. Edit the fetched secret JSON file to include a section with the credentials of the certificate authority: +.. Edit the fetched secret JSON file to include a section with the credentials of the certificate authority: + [source,terminal] ---- diff --git a/modules/hcp-ibmz-adding-reg-ca-hostedcluster.adoc b/modules/hcp-ibm-z-adding-reg-ca-hostedcluster.adoc similarity index 96% rename from modules/hcp-ibmz-adding-reg-ca-hostedcluster.adoc rename to modules/hcp-ibm-z-adding-reg-ca-hostedcluster.adoc index fe8501c901..9736b400b3 100644 --- a/modules/hcp-ibmz-adding-reg-ca-hostedcluster.adoc +++ b/modules/hcp-ibm-z-adding-reg-ca-hostedcluster.adoc @@ -1,17 +1,17 @@ :_mod-docs-content-type: PROCEDURE -[id="hcp-ibmz-adding-registry-ca-hostedcluster_{context}"] +[id="hcp-ibm-z-adding-registry-ca-hostedcluster_{context}"] = Adding the registry certificate authority to the hosted cluster When you are deploying {hcp} on {ibm-z-title} in a disconnected environment, include the `additional-trust-bundle` and `image-content-sources` resources. Those resources allow the hosted cluster to inject the certificate authority into the data plane workers so that the images are pulled from the registry. -. Create the `icsp.yaml` file with the `image-content-sources` information. +. Create the `icsp.yaml` file with the `image-content-sources` information. + The `image-content-sources` information is available in the `ImageContentSourcePolicy` YAML file that is generated after you mirror the images by using `oc-mirror`. + .Example ImageContentSourcePolicy file [source,terminal] ---- -# cat icsp.yaml +# cat icsp.yaml - mirrors: - /openshift/release source: quay.io/openshift-release-dev/ocp-v4.0-art-dev diff --git a/modules/hcp-ibmz-dc-prereqs.adoc b/modules/hcp-ibm-z-dc-prereqs.adoc similarity index 77% rename from modules/hcp-ibmz-dc-prereqs.adoc rename to modules/hcp-ibm-z-dc-prereqs.adoc index 07de95386d..9712d75d4b 100644 --- a/modules/hcp-ibmz-dc-prereqs.adoc +++ b/modules/hcp-ibm-z-dc-prereqs.adoc @@ -1,6 +1,6 @@ :_mod-docs-content-type: CONCEPT -[id="hcp-ibmz-dc-prereqs_{context}"] +[id="hcp-ibm-z-dc-prereqs_{context}"] = Prerequisites to deploy {hcp} on {ibm-z-title} in a disconnected environment -* A mirror registry. For more information, see "Creating a mirror registry with mirror registry for Red Hat OpenShift". +* A mirror registry. For more information, see "Creating a mirror registry with mirror registry for Red Hat OpenShift". * A mirrored image for a disconnected installation. For more information, see "Mirroring images for a disconnected installation using the oc-mirror plugin". \ No newline at end of file diff --git a/modules/hcp-ibmz-dns.adoc b/modules/hcp-ibm-z-dns.adoc similarity index 97% rename from modules/hcp-ibmz-dns.adoc rename to modules/hcp-ibm-z-dns.adoc index eb0c1a15d0..66a7e59b4f 100644 --- a/modules/hcp-ibmz-dns.adoc +++ b/modules/hcp-ibm-z-dns.adoc @@ -3,7 +3,7 @@ // * hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc :_mod-docs-content-type: CONCEPT -[id="hcp-ibmz-dns_{context}"] +[id="hcp-ibm-z-dns_{context}"] = DNS configuration for {hcp} on {ibm-z-title} The API server for the hosted cluster is exposed as a `NodePort` service. A DNS entry must exist for the `api..` that points to the destination where the API server is reachable. diff --git a/modules/hcp-ibmz-infra-reqs.adoc b/modules/hcp-ibm-z-infra-reqs.adoc similarity index 94% rename from modules/hcp-ibmz-infra-reqs.adoc rename to modules/hcp-ibm-z-infra-reqs.adoc index 159b15e76b..fc1d425e20 100644 --- a/modules/hcp-ibmz-infra-reqs.adoc +++ b/modules/hcp-ibm-z-infra-reqs.adoc @@ -3,7 +3,7 @@ // * hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc :_mod-docs-content-type: CONCEPT -[id="hcp-ibmz-infra-reqs_{context}"] +[id="hcp-ibm-z-infra-reqs_{context}"] = {ibm-z-title} infrastructure requirements The Agent platform does not create any infrastructure, but requires the following resources for infrastructure: diff --git a/modules/hcp-ibmz-infraenv.adoc b/modules/hcp-ibm-z-infraenv.adoc similarity index 97% rename from modules/hcp-ibmz-infraenv.adoc rename to modules/hcp-ibm-z-infraenv.adoc index 2a75ce8250..57979ff893 100644 --- a/modules/hcp-ibmz-infraenv.adoc +++ b/modules/hcp-ibm-z-infraenv.adoc @@ -3,7 +3,7 @@ // * hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc :_mod-docs-content-type: PROCEDURE -[id="hcp-ibmz-infraenv_{context}"] +[id="hcp-ibm-z-infraenv_{context}"] = Creating an InfraEnv resource for {hcp} on {ibm-z-title} An `InfraEnv` is an environment where hosts that are booted with PXE images can join as agents. In this case, the agents are created in the same namespace as your hosted control plane. diff --git a/modules/hcp-ibmz-kvm-agents.adoc b/modules/hcp-ibm-z-kvm-agents.adoc similarity index 98% rename from modules/hcp-ibmz-kvm-agents.adoc rename to modules/hcp-ibm-z-kvm-agents.adoc index 6356695ce6..9f3692c910 100644 --- a/modules/hcp-ibmz-kvm-agents.adoc +++ b/modules/hcp-ibm-z-kvm-agents.adoc @@ -3,7 +3,7 @@ // * hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc :_mod-docs-content-type: PROCEDURE -[id="hcp-ibmz-kvm-agents_{context}"] +[id="hcp-ibm-z-kvm-agents_{context}"] = Adding {ibm-z-title} KVM as agents For {ibm-z-title} with KVM, run the following command to start your {ibm-z-title} environment with the downloaded PXE images from the `InfraEnv` resource. After the Agents are created, the host communicates with the Assisted Service and registers in the same namespace as the `InfraEnv` resource on the management cluster. diff --git a/modules/hcp-ibmz-lpar-agents.adoc b/modules/hcp-ibm-z-lpar-agents.adoc similarity index 98% rename from modules/hcp-ibmz-lpar-agents.adoc rename to modules/hcp-ibm-z-lpar-agents.adoc index 5f79f253ad..3e726f9f39 100644 --- a/modules/hcp-ibmz-lpar-agents.adoc +++ b/modules/hcp-ibm-z-lpar-agents.adoc @@ -3,7 +3,7 @@ // * hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc :_mod-docs-content-type: PROCEDURE -[id="hcp-ibmz-lpar-agents_{context}"] +[id="hcp-ibm-z-lpar-agents_{context}"] = Adding {ibm-z-title} LPAR as agents You can add the Logical Partition (LPAR) on {ibm-z-title} or {ibm-linuxone-title} as a compute node to a hosted control plane. diff --git a/modules/hcp-ibmz-prereqs.adoc b/modules/hcp-ibm-z-prereqs.adoc similarity index 97% rename from modules/hcp-ibmz-prereqs.adoc rename to modules/hcp-ibm-z-prereqs.adoc index e71b140188..1672cd3cc4 100644 --- a/modules/hcp-ibmz-prereqs.adoc +++ b/modules/hcp-ibm-z-prereqs.adoc @@ -3,7 +3,7 @@ // * hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc :_mod-docs-content-type: CONCEPT -[id="hcp-ibmz-prereqs_{context}"] +[id="hcp-ibm-z-prereqs_{context}"] = Prerequisites to configure {hcp} on {ibm-z-title} * The {mce} version 2.5 or later must be installed on an {product-title} cluster. You can install {mce-short} as an Operator from the {product-title} OperatorHub. diff --git a/modules/hcp-ibmz-scale-np.adoc b/modules/hcp-ibm-z-scale-np.adoc similarity index 99% rename from modules/hcp-ibmz-scale-np.adoc rename to modules/hcp-ibm-z-scale-np.adoc index e52447e4a4..a039e10915 100644 --- a/modules/hcp-ibmz-scale-np.adoc +++ b/modules/hcp-ibm-z-scale-np.adoc @@ -3,7 +3,7 @@ // * hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc :_mod-docs-content-type: PROCEDURE -[id="hcp-ibmz-scale-np_{context}"] +[id="hcp-ibm-z-scale-np_{context}"] = Scaling the NodePool object for a hosted cluster on {ibm-z-title} The `NodePool` object is created when you create a hosted cluster. By scaling the `NodePool` object, you can add more compute nodes to the hosted control plane. diff --git a/modules/hcp-ibmz-update-reg-ca.adoc b/modules/hcp-ibm-z-update-reg-ca.adoc similarity index 97% rename from modules/hcp-ibmz-update-reg-ca.adoc rename to modules/hcp-ibm-z-update-reg-ca.adoc index 3c4bd52427..f20b6b0f42 100644 --- a/modules/hcp-ibmz-update-reg-ca.adoc +++ b/modules/hcp-ibm-z-update-reg-ca.adoc @@ -1,5 +1,5 @@ :_mod-docs-content-type: PROCEDURE -[id="hcp-ibmz-update-registry-ca_{context}"] +[id="hcp-ibm-z-update-registry-ca_{context}"] = Update the registry certificate authority in the AgentServiceConfig resource with the mirror registry When you use a mirror registry for images, agents need to trust the registry's certificate to securely pull images. You can add the certificate authority of the mirror registry to the `AgentServiceConfig` custom resource by creating a `ConfigMap`. @@ -8,7 +8,7 @@ When you use a mirror registry for images, agents need to trust the registry's c * You must have installed {mce}. -.Procedure +.Procedure . In the same namespace where you installed {mce-short}, create a `ConfigMap` resource with the mirror registry details. This `ConfigMap` resource ensures that you grant the hosted cluster workers the capability to retrieve images from the mirror registry. + diff --git a/modules/hcp-ibmz-zvm-agents.adoc b/modules/hcp-ibm-z-zvm-agents.adoc similarity index 96% rename from modules/hcp-ibmz-zvm-agents.adoc rename to modules/hcp-ibm-z-zvm-agents.adoc index 5c31b8b095..6d44424087 100644 --- a/modules/hcp-ibmz-zvm-agents.adoc +++ b/modules/hcp-ibm-z-zvm-agents.adoc @@ -3,7 +3,7 @@ // * hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc :_mod-docs-content-type: PROCEDURE -[id="hcp-ibmz-zvm-agents_{context}"] +[id="hcp-ibm-z-zvm-agents_{context}"] = Adding {ibm-title} z/VM as agents If you want to use a static IP for z/VM guest, you must configure the `NMStateConfig` attribute for the z/VM agent so that the IP parameter persists in the second start. @@ -12,7 +12,7 @@ Complete the following steps to start your {ibm-z-title} environment with the do .Procedure -. Update the parameter file to add the `rootfs_url`, `network_adaptor` and `disk_type` values. +. Update the parameter file to add the `rootfs_url`, `network_adaptor` and `disk_type` values. + .Example parameter file [source,yaml] @@ -72,7 +72,7 @@ NAME CLUSTER APPROVED ROLE STAGE 5e498cd3-542c-e54f-0c58-ed43e28b568a auto-assign ---- -. Run the following command to approve the agent. +. Run the following command to approve the agent. + [source,terminal] ---- diff --git a/modules/ibmz-configure-devices-manually.adoc b/modules/ibm-z-configure-devices-manually.adoc similarity index 95% rename from modules/ibmz-configure-devices-manually.adoc rename to modules/ibm-z-configure-devices-manually.adoc index 8ba18f25e3..fae22e7a27 100644 --- a/modules/ibmz-configure-devices-manually.adoc +++ b/modules/ibm-z-configure-devices-manually.adoc @@ -1,6 +1,6 @@ // Module included in the following assemblies: // -// * installing/installing_ibmz_z/ibmz-post-install.adoc +// * installing/installing_ibm_z/ibmz-post-install.adoc :_mod-docs-content-type: PROCEDURE [id="configure-additional-devices-manually_{context}"] diff --git a/modules/ibmz-configure-devices-mco.adoc b/modules/ibm-z-configure-devices-mco.adoc similarity index 99% rename from modules/ibmz-configure-devices-mco.adoc rename to modules/ibm-z-configure-devices-mco.adoc index 143c8d7b1a..dd21f17275 100644 --- a/modules/ibmz-configure-devices-mco.adoc +++ b/modules/ibm-z-configure-devices-mco.adoc @@ -1,6 +1,6 @@ // Module included in the following assemblies: // -// * installing/installing_ibmz_z/ibmz-post-install.adoc +// * installing/installing_ibm_z/ibmz-post-install.adoc :_mod-docs-content-type: PROCEDURE [id="configure-additional-devices-using-mco_{context}"] diff --git a/modules/ibmz-configure-nbde-with-static-ip.adoc b/modules/ibm-z-configure-nbde-with-static-ip.adoc similarity index 99% rename from modules/ibmz-configure-nbde-with-static-ip.adoc rename to modules/ibm-z-configure-nbde-with-static-ip.adoc index c7554c8ee1..99fd1c224c 100644 --- a/modules/ibmz-configure-nbde-with-static-ip.adoc +++ b/modules/ibm-z-configure-nbde-with-static-ip.adoc @@ -27,7 +27,7 @@ ifeval::["{context}" == "installing-restricted-networks-ibm-z-lpar"] endif::[] :_mod-docs-content-type: PROCEDURE -[id="configuring-nbde-static-ip-ibmz-linuxone-environment_{context}"] +[id="configuring-nbde-static-ip-ibm-z-linuxone-environment_{context}"] = Configuring NBDE with static IP in an {ibm-z-title} or {ibm-linuxone-title} environment Enabling NBDE disk encryption in an {ibm-z-name} or {ibm-linuxone-name} environment requires additional steps, which are described in detail in this section. diff --git a/modules/ibmz-enable-multipathing-fcp-luns.adoc b/modules/ibm-z-enable-multipathing-fcp-luns.adoc similarity index 97% rename from modules/ibmz-enable-multipathing-fcp-luns.adoc rename to modules/ibm-z-enable-multipathing-fcp-luns.adoc index 0afa9c461c..9ab116bac1 100644 --- a/modules/ibmz-enable-multipathing-fcp-luns.adoc +++ b/modules/ibm-z-enable-multipathing-fcp-luns.adoc @@ -1,6 +1,6 @@ // Module included in the following assemblies: // -// * installing/installing_ibmz_z/ibmz-post-install.adoc +// * installing/installing_ibm_z/ibmz-post-install.adoc :_mod-docs-content-type: PROCEDURE [id="enabling-multipathing-fcp-luns_{context}"] diff --git a/modules/installing-ocp-agent-ibm-z.adoc b/modules/installing-ocp-agent-ibm-z.adoc index 2bd1f19967..75cc220ad6 100644 --- a/modules/installing-ocp-agent-ibm-z.adoc +++ b/modules/installing-ocp-agent-ibm-z.adoc @@ -20,7 +20,7 @@ Depending on your {ibm-z-name} environment, you can choose from the following op Currently, ISO boot support on {ibm-z-name} (`s390x`) is available only for {op-system-base-full} KVM, which provides the flexibility to choose either PXE or ISO-based installation. For installations with z/VM and Logical Partition (LPAR), only PXE boot is supported. ==== -[id="networking-reqs-ibmz_{context}"] +[id="networking-reqs-ibm-z_{context}"] == Networking requirements for {ibm-z-title} In {ibm-z-title} environments, advanced networking technologies such as Open Systems Adapter (OSA), HiperSockets, and Remote Direct Memory Access (RDMA) over Converged Ethernet (RoCE) require specific configurations that deviate from the standard network settings and those needs to be persisted for multiple boot scenarios that occur in the Agent-based Installation.