openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

Merge pull request #20636 from openshift-cherrypick-robot/cherry-pick-20579-to-enterprise-4.4

Browse Source 
[enterprise-4.4] RHV-16816-lp Landing page for Installing OCP RHV
This commit is contained in:
Jason Boxman
2020-03-23 14:06:18 -04:00
committed by GitHub
parent 0e8eb2f47e 29d6f5190e
commit 154f69bd55
3 changed files with 22 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
_topic_map.yml
View File

@@ -149,6 +149,11 @@ Topics:
File: installing-restricted-networks-gcp
- Name: Uninstalling a cluster on GCP
File: uninstalling-cluster-gcp
- Name: Installing on RHV
Dir: installing_rhv
Topics:
- Name: Installing a cluster on Red Hat Virtualization
File: installing-rhv
- Name: Installing on bare metal
Dir: installing_bare_metal
Topics:

13
installing/installing_rhv/installing-rhv.adoc Normal file
View File

@@ -0,0 +1,13 @@
[id="installing-rhv"]
= Installing a cluster on Red Hat Virtualization
include::modules/common-attributes.adoc[]
:context: installing-rhv
toc::[]
In {product-title} version {product-version}, you can install a cluster
in a Red Hat Virtualization (RHV) environment.
The installer that deploys a cluster on RHV automates the process by using installer-provisioned infrastructure. This installer is available for Linux and macOS only.
To learn more about installing a {product-title} cluster on RHV, read link:https://access.redhat.com/articles/4903411[Quickstart Guide: Installing {product-title} on Red Hat Virtualization]

21
modules/installation-overview.adoc
View File

@@ -17,30 +17,16 @@ Both types of clusters have the following characteristics:
by default
* Administrators maintain control over what updates are applied and when
You use the same installation program to deploy both types of clusters. The main
assets generated by the installation program are the Ignition config files for the
bootstrap, master, and worker machines. With these three configurations and correctly
configured infrastructure, you can start an {product-title} cluster.
You use the same installation program to deploy both types of clusters. The main assets generated by the installation program are the Ignition config files for the bootstrap, master, and worker machines. With these three configurations and correctly configured infrastructure, you can start an {product-title} cluster.
The {product-title} installation program uses a set of targets and dependencies to manage
cluster installation. The installation program has a set of targets that it must achieve,
and each target has a set of dependencies. Because each target is only
concerned with its own dependencies, the installation program can act to achieve
multiple targets in parallel. The ultimate target is a running cluster. By
meeting dependencies instead of running commands, the installation program is
able to recognize and use existing components instead of running the commands to
create them again.
The {product-title} installation program uses a set of targets and dependencies to manage cluster installation. The installation program has a set of targets that it must achieve, and each target has a set of dependencies. Because each target is only concerned with its own dependencies, the installation program can act to achieve multiple targets in parallel. The ultimate target is a running cluster. By meeting dependencies instead of running commands, the installation program is able to recognize and use existing components instead of running the commands to create them again.
The following diagram shows a subset of the installation targets and dependencies:
.{product-title} installation targets and dependencies
image::targets-and-dependencies.png[{product-title} installation targets and dependencies]
After installation, each cluster machine uses {op-system-first} as the operating
system. {op-system} is the immutable container host version of
Red Hat Enterprise Linux (RHEL) and features a RHEL kernel with SELinux enabled
by default. It includes the `kubelet`, which is the Kubernetes node agent, and
the CRI-O container runtime, which is optimized for Kubernetes.
After installation, each cluster machine uses {op-system-first} as the operating system. {op-system} is the immutable container host version of Red Hat Enterprise Linux (RHEL) and features a RHEL kernel with SELinux enabled by default. It includes the `kubelet`, which is the Kubernetes node agent, and the CRI-O container runtime, which is optimized for Kubernetes.
Every control plane machine in an {product-title} {product-version} cluster must
use {op-system}, which includes a critical first-boot provisioning tool called
@@ -71,6 +57,7 @@ installer-provisioned infrastructure on the following platforms:
* Google Cloud Platform (GCP)
* Microsoft Azure
* Red Hat OpenStack Platform version 13 and 14
* Red Hat Virtualization (RHV)
For these clusters, all machines, including the computer that you run the installation process on, must have direct internet access to pull images for platform containers and provide telemetry data to Red Hat.