Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 16 additions & 6 deletions _topic_map.yml
Original file line number Diff line number Diff line change
Expand Up @@ -216,12 +216,22 @@ Topics:
File: ipi-install-installation-workflow
- Name: Troubleshooting
File: ipi-install-troubleshooting
# - Name: Installing on IBM Z and LinuxONE
# Dir: installing_ibm_z
# Distros: openshift-enterprise,openshift-webscale
# Topics:
# - Name: Installing a cluster on IBM Z and LinuxONE
# File: installing-ibm-z
- Name: Installing on IBM Z and LinuxONE
Dir: installing_ibm_z
Distros: openshift-enterprise,openshift-webscale
Topics:
- Name: Installing a cluster on IBM Z and LinuxONE
File: installing-ibm-z
- Name: Restricted network IBM Z installation
File: installing-restricted-networks-ibm-z
- Name: Installing on IBM Power
Dir: installing_ibm_power
Distros: openshift-enterprise,openshift-webscale
Topics:
- Name: Installing a cluster on IBM Power
File: installing-ibm-power
- Name: Restricted network IBM Power installation
File: installing-restricted-networks-ibm-power
- Name: Installing on OpenStack
Dir: installing_openstack
Topics:
Expand Down
2 changes: 1 addition & 1 deletion autocomment.sh
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ wget https://api.travis-ci.org/v3/job/"${TRAVIS_JOB_ID}"/log.txt
ERROR_LIST=$(grep '31m' travis-log-408052641.txt | sed -r "s/[[:cntrl:]]\[[0-9]{1,3}m//g")
echo "" > errors.txt

ALLOWED_USERS=("mburke5678" "vikram-redhat" "abrennan89" "ahardin-rh" "kalexand-rh" "adellape" "bmcelvee" "ousleyp" "lamek" "JStickler" "rh-max" "bergerhoffer" "huffmanca" "sheriff-rh" "jboxman" "bobfuru" "joaedwar" "aburdenthehand" "boczkowska" "Preeticp" "neal-timpe" "codyhoag" "pmacko1" "apinnick" "bgaydosrh" "lmandavi" "nkakkar81" "maxwelldb" "pneedle-rh" "lbarbeevargas" "jeana-redhat" "RichardHoch" "johnwilkins" "sjhala-ccs" "chrisnegus" "mgarrellRH" "SNiemann15" "sfortner-RH")
ALLOWED_USERS=("mburke5678" "vikram-redhat" "abrennan89" "ahardin-rh" "kalexand-rh" "adellape" "bmcelvee" "ousleyp" "lamek" "JStickler" "rh-max" "bergerhoffer" "huffmanca" "sheriff-rh" "jboxman" "bobfuru" "joaedwar" "aburdenthehand" "boczkowska" "Preeticp" "neal-timpe" "codyhoag" "pmacko1" "apinnick" "bgaydosrh" "lmandavi" "nkakkar81" "maxwelldb" "pneedle-rh" "lbarbeevargas" "jeana-redhat" "RichardHoch" "johnwilkins" "sjhala-ccs" "chrisnegus" "mgarrellRH" "SNiemann15" "sfortner-RH" "jonquilwilliams" "ktania46" "wking")
USERNAME=${TRAVIS_PULL_REQUEST_SLUG::-15}

if [ "$TRAVIS_PULL_REQUEST" != "false" ] ; then #to make sure it only runs on PRs and not all merges
Expand Down
2 changes: 1 addition & 1 deletion autopreview.sh
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
#!/bin/bash
set -ev

ALLOWED_USERS=("mburke5678" "vikram-redhat" "abrennan89" "ahardin-rh" "kalexand-rh" "adellape" "bmcelvee" "ousleyp" "lamek" "JStickler" "rh-max" "bergerhoffer" "huffmanca" "sheriff-rh" "jboxman" "bobfuru" "joaedwar" "aburdenthehand" "boczkowska" "Preeticp" "neal-timpe" "codyhoag" "pmacko1" "apinnick" "bgaydosrh" "lmandavi" "nkakkar81" "maxwelldb" "pneedle-rh" "lbarbeevargas" "jeana-redhat" "RichardHoch" "johnwilkins" "sjhala-ccs" "chrisnegus" "mgarrellRH" "SNiemann15" "sfortner-RH")
ALLOWED_USERS=("mburke5678" "vikram-redhat" "abrennan89" "ahardin-rh" "kalexand-rh" "adellape" "bmcelvee" "ousleyp" "lamek" "JStickler" "rh-max" "bergerhoffer" "huffmanca" "sheriff-rh" "jboxman" "bobfuru" "joaedwar" "aburdenthehand" "boczkowska" "Preeticp" "neal-timpe" "codyhoag" "pmacko1" "apinnick" "bgaydosrh" "lmandavi" "nkakkar81" "maxwelldb" "pneedle-rh" "lbarbeevargas" "jeana-redhat" "RichardHoch" "johnwilkins" "sjhala-ccs" "chrisnegus" "mgarrellRH" "SNiemann15" "sfortner-RH" "jonquilwilliams" "ktania46" "wking")
USERNAME=${TRAVIS_PULL_REQUEST_SLUG::-15}
COMMIT_HASH="$(git rev-parse @~)"
mapfile -t FILES_CHANGED < <(git diff --name-only "$COMMIT_HASH")
Expand Down
1 change: 1 addition & 0 deletions installing/installing_ibm_power/images
90 changes: 90 additions & 0 deletions installing/installing_ibm_power/installing-ibm-power.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,90 @@
[id="installing-ibm-power"]
= Installing a cluster on IBM Power
include::modules/common-attributes.adoc[]
:context: installing-ibm-power

toc::[]

In {product-title} version {product-version}, you can install a cluster on
IBM Power infrastructure that you provision.

[IMPORTANT]
====
Additional considerations exist for non-bare metal platforms. Review the information in the
link:https://access.redhat.com/articles/4207611[guidelines for deploying {product-title} on non-tested platforms]before you install an {product-title} cluster.
====

.Prerequisites

* Before you begin the installation process, you must clean the installation directory. This ensures that the required installation files are created and updated during the installation process.
* Provision
xref:../../storage/persistent_storage/persistent-storage-nfs.adoc#persistent-storage-nfs[persistent storage using NFS]
for your cluster. To deploy a private image registry, your storage must provide
ReadWriteMany access modes.
* Review details about the
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
processes.
* If you use a firewall, you must
xref:../../installing/install_config/configuring-firewall.adoc#configuring-firewall[configure it to allow the sites] that your cluster requires access to.
+
[NOTE]
====
Be sure to also review this site list if you are configuring a proxy.
====

include::modules/cluster-entitlements.adoc[leveloffset=+1]

include::modules/installation-requirements-user-infra.adoc[leveloffset=+1]

include::modules/installation-infrastructure-user-infra.adoc[leveloffset=+1]

include::modules/installation-network-user-infra.adoc[leveloffset=+2]

include::modules/installation-dns-user-infra.adoc[leveloffset=+2]

include::modules/ssh-agent-using.adoc[leveloffset=+1]

include::modules/installation-obtaining-installer.adoc[leveloffset=+1]

include::modules/cli-installing-cli.adoc[leveloffset=+1]

include::modules/installation-initializing-manual.adoc[leveloffset=+1]

include::modules/installation-bare-metal-config-yaml.adoc[leveloffset=+2]

include::modules/installation-configure-proxy.adoc[leveloffset=+2]

include::modules/installation-user-infra-generate-k8s-manifest-ignition.adoc[leveloffset=+1]

[id="creating-machines-bare-metal-power"]
== Creating {op-system-first} machines

Before you install a cluster on IBM Power infrastructure that you provision,
you must create {op-system} machines for it to use. Follow either the steps
to use an ISO image or network PXE booting to create the machines.

include::modules/installation-user-infra-machines-iso.adoc[leveloffset=+2]

include::modules/installation-user-infra-machines-pxe.adoc[leveloffset=+2]

include::modules/installation-installing-bare-metal.adoc[leveloffset=+1]

include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]

include::modules/installation-approve-csrs.adoc[leveloffset=+1]

include::modules/installation-operators-config.adoc[leveloffset=+1]

include::modules/installation-registry-storage-config.adoc[leveloffset=+2]

include::modules/registry-configuring-storage-baremetal.adoc[leveloffset=+3]

include::modules/installation-registry-storage-non-production.adoc[leveloffset=+3]

include::modules/installation-complete-user-infra.adoc[leveloffset=+1]

.Next steps

* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
* If necessary, you can
xref:../../support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting_opting-out-remote-health-reporting[opt out of remote health reporting].
Original file line number Diff line number Diff line change
@@ -0,0 +1,100 @@
[id="installing-restricted-networks-ibm-power"]
= Installing a cluster on IBM Power in a restricted network
include::modules/common-attributes.adoc[]
:context: installing-restricted-networks-ibm-power

toc::[]

In {product-title} version {product-version}, you can install a cluster on
IBM Power infrastructure that you provision in a restricted network.

[IMPORTANT]
====
Additional considerations exist for non-bare metal platforms. Review the information in the
link:https://access.redhat.com/articles/4207611[guidelines for deploying {product-title} on non-tested platforms] before you install an {product-title} cluster.
====

.Prerequisites

* xref:../../installing/install_config/installing-restricted-networks-preparations.adoc#installing-restricted-networks-preparations[Create a mirror registry for installation in a restricted network] and obtain the `imageContentSources` data for your version of {product-title}.
* Before you begin the installation process, you must move or remove any existing installation files. This ensures that the required installation files are created and updated during the installation process.
+
[IMPORTANT]
====
Ensure that installation steps are performed on a machine with access to the installation media.
====
* Provision
xref:../../storage/understanding-persistent-storage.adoc#understanding-persistent-storage[persistent storage]
for your cluster. To deploy a private image registry, your storage must provide
ReadWriteMany access modes.
* Review details about the
xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
processes.
* If you use a firewall and plan to use telemetry, you must
xref:../../installing/install_config/configuring-firewall.adoc#configuring-firewall[configure the firewall to allow the sites] that your cluster requires access to.
+
[NOTE]
====
Be sure to also review this site list if you are configuring a proxy.
====

include::modules/installation-about-restricted-network.adoc[leveloffset=+1]

include::modules/cluster-entitlements.adoc[leveloffset=+1]

include::modules/installation-requirements-user-infra.adoc[leveloffset=+1]

include::modules/installation-infrastructure-user-infra.adoc[leveloffset=+1]

include::modules/installation-network-user-infra.adoc[leveloffset=+2]

include::modules/installation-dns-user-infra.adoc[leveloffset=+2]

include::modules/ssh-agent-using.adoc[leveloffset=+1]

//You extract the installation program from the mirrored content.

//You install the CLI on the bastion host.

include::modules/installation-initializing-manual.adoc[leveloffset=+1]

include::modules/installation-bare-metal-config-yaml.adoc[leveloffset=+2]

include::modules/installation-configure-proxy.adoc[leveloffset=+2]

include::modules/installation-user-infra-generate-k8s-manifest-ignition.adoc[leveloffset=+1]

[id="creating-machines-ibm-power-restricted-network"]
== Creating {op-system-first} machines

Before you install a cluster on IBM Power infrastructure that you provision,
you must create {op-system} machines for it to use. Follow either the steps
to use an ISO image or network PXE booting to create the machines.

include::modules/installation-user-infra-machines-iso.adoc[leveloffset=+2]

include::modules/installation-user-infra-machines-static-network.adoc[leveloffset=+3]

include::modules/installation-user-infra-machines-pxe.adoc[leveloffset=+2]

include::modules/installation-installing-bare-metal.adoc[leveloffset=+1]

include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]

include::modules/installation-approve-csrs.adoc[leveloffset=+1]

include::modules/installation-operators-config.adoc[leveloffset=+1]

include::modules/installation-registry-storage-config.adoc[leveloffset=+2]

include::modules/registry-change-management-state.adoc[leveloffset=+3]

include::modules/registry-configuring-storage-baremetal.adoc[leveloffset=+3]

include::modules/installation-registry-storage-non-production.adoc[leveloffset=+3]

include::modules/installation-complete-user-infra.adoc[leveloffset=+1]

.Next steps

* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].
1 change: 1 addition & 0 deletions installing/installing_ibm_power/modules
33 changes: 25 additions & 8 deletions installing/installing_ibm_z/installing-ibm-z.adoc
Original file line number Diff line number Diff line change
@@ -1,26 +1,28 @@
[id="installing-ibm-z"]
= Installing a cluster on IBM Z
= Installing a cluster on IBM Z and LinuxONE
include::modules/common-attributes.adoc[]
:context: installing-ibm-z

toc::[]

In {product-title} version {product-version}, you can install a cluster on
IBM Z infrastructure that you provision.
IBM Z or LinuxONE infrastructure that you provision.

[IMPORTANT]
[NOTE]
====
Additional considerations exist for non-bare metal platforms. Review the information in the
link:https://access.redhat.com/articles/4207611[guidelines for deploying {product-title} on non-tested platforms] before you install an {product-title} cluster.
While this document refers only to IBM Z, all information in it also applies to LinuxONE.
====

[WARNING]
[IMPORTANT]
====
Restricted network installations are not tested or supported on IBM Z in {product-title} {product-version}.
Additional considerations exist for non-bare metal platforms. Review the information in the
link:https://access.redhat.com/articles/4207611[guidelines for deploying {product-title} on non-tested platforms] before you install an {product-title} cluster.
====

== Prerequisites

* Before you begin the installation process, you must clean the installation directory. This ensures that the required installation files are created and updated during the installation process.

* Provision
xref:../../storage/persistent_storage/persistent-storage-nfs.adoc#persistent-storage-nfs[persistent storage using NFS]
for your cluster. To deploy a private image registry, your storage must provide
Expand All @@ -30,7 +32,7 @@ xref:../../architecture/architecture-installation.adoc#architecture-installation
processes.
* If you use a firewall, you must
xref:../../installing/install_config/configuring-firewall.adoc#configuring-firewall[configure it to allow the sites] that your cluster requires access to.
+

[NOTE]
====
Be sure to also review this site list if you are configuring a proxy.
Expand All @@ -40,6 +42,12 @@ include::modules/cluster-entitlements.adoc[leveloffset=+1]

include::modules/installation-requirements-user-infra.adoc[leveloffset=+1]

.Additional resources

* See link:https://www.ibm.com/support/knowledgecenter/en/SSB27U_7.1.0/com.ibm.zvm.v710.hcpa6/bhslzvs.htm[Bridging a HiperSockets LAN with a z/VM Virtual Switch] in the IBM Knowledge Center.

* See link:http://public.dhe.ibm.com/software/dw/linux390/perf/zvm_hpav00.pdf[Scaling HyperPAV alias devices on Linux guests on z/VM] for performance optimization.

include::modules/installation-infrastructure-user-infra.adoc[leveloffset=+1]

include::modules/installation-network-user-infra.adoc[leveloffset=+2]
Expand All @@ -56,6 +64,8 @@ include::modules/installation-initializing-manual.adoc[leveloffset=+1]

include::modules/installation-bare-metal-config-yaml.adoc[leveloffset=+2]

include::modules/installation-configure-proxy.adoc[leveloffset=+1]

include::modules/installation-user-infra-generate-k8s-manifest-ignition.adoc[leveloffset=+1]

include::modules/installation-ibm-z-user-infra-machines-iso.adoc[leveloffset=+1]
Expand All @@ -76,8 +86,15 @@ include::modules/installation-registry-storage-non-production.adoc[leveloffset=+

include::modules/installation-complete-user-infra.adoc[leveloffset=+1]

include::modules/installation-ibm-z-troubleshooting-and-debugging.adoc[leveloffset=+1]

.Additional resources

* See also link:https://access.redhat.com/solutions/4387261[How to generate SOSREPORT within OpenShift4 nodes without SSH].

== Next steps

* xref:../../installing/install_config/customizations.adoc#customizations[Customize your cluster].

* If necessary, you can
xref:../../support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting_opting-out-remote-health-reporting[opt out of remote health reporting].
Loading