mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
Changing on-premises to on-premise per RH supplementary style guide
This commit is contained in:
Michael Burke
@@ -46,5 +46,4 @@ You can also use xref:../applications/working_with_helm_charts/understanding-hel
|
||||
|
||||
[id="redhat-marketplace"]
|
||||
== Using the Red Hat Marketplace
|
||||
The xref:../applications/red-hat-marketplace.adoc#red-hat-marketplace[Red Hat Marketplace] is an open cloud marketplace where you can discover and access certified software for container-based environments that run on public clouds and on-premises.
|
||||
|
||||
The xref:../applications/red-hat-marketplace.adoc#red-hat-marketplace[Red Hat Marketplace] is an open cloud marketplace where you can discover and access certified software for container-based environments that run on public clouds and on-premise.
|
||||
|
||||
@@ -6,6 +6,6 @@ include::_attributes/common-attributes.adoc[]
|
||||
|
||||
toc::[]
|
||||
|
||||
The link:https://marketplace.redhat.com[Red Hat Marketplace] is an open cloud marketplace that makes it easy to discover and access certified software for container-based environments that run on public clouds and on-premises.
|
||||
The link:https://marketplace.redhat.com[Red Hat Marketplace] is an open cloud marketplace that makes it easy to discover and access certified software for container-based environments that run on public clouds and on-premise.
|
||||
|
||||
include::modules/red-hat-marketplace-features.adoc[leveloffset=+1]
|
||||
|
||||
@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
|
||||
|
||||
toc::[]
|
||||
|
||||
The Agent-based installation method provides the flexibility to boot your on-premises servers in any way that you choose. It combines the ease of use of the Assisted Installation service with the ability to run offline, including in air-gapped environments.
|
||||
The Agent-based installation method provides the flexibility to boot your on-premise servers in any way that you choose. It combines the ease of use of the Assisted Installation service with the ability to run offline, including in air-gapped environments.
|
||||
|
||||
Agent-based installation is a subcommand of the {product-title} installer. It generates a bootable ISO image containing all of the information required to deploy an {product-title} cluster with an available release image.
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ You can install {product-title} with the link:https://access.redhat.com/document
|
||||
== Agent-based Installer
|
||||
|
||||
You can install an {product-title} cluster on vSphere using the Agent-based Installer.
|
||||
The Agent-based Installer can be used to boot an on-premises server in a disconnected environment by using a bootable image.
|
||||
The Agent-based Installer can be used to boot an on-premise server in a disconnected environment by using a bootable image.
|
||||
With the Agent-based Installer, users also have the flexibility to provision infrastructure, customize network configurations, and customize installations within a disconnected environment.
|
||||
See xref:../../installing/installing_with_agent_based_installer/preparing-to-install-with-agent-based-installer.adoc#preparing-to-install-with-agent-based-installer[Preparing to install with the Agent-based Installer] for additional details.
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ toc::[]
|
||||
[id="about-the-agent-based-installer_{context}"]
|
||||
== About the Agent-based Installer
|
||||
|
||||
The Agent-based installation method provides the flexibility to boot your on-premises servers in any way that you choose. It combines the ease of use of the Assisted Installation service with the ability to run offline, including in air-gapped environments.
|
||||
The Agent-based installation method provides the flexibility to boot your on-premise servers in any way that you choose. It combines the ease of use of the Assisted Installation service with the ability to run offline, including in air-gapped environments.
|
||||
Agent-based installation is a subcommand of the {product-title} installer.
|
||||
It generates a bootable ISO image containing all of the information required to deploy an {product-title} cluster, with an available release image.
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
// * migration_toolkit_for_containers/advanced-migration-options-mtc.adoc
|
||||
:_mod-docs-content-type: PROCEDURE
|
||||
[id="migration-migrating-applications-on-prem-to-cloud_{context}"]
|
||||
= Migrating an application from on-premises to a cloud-based cluster
|
||||
= Migrating an application from on-premise to a cloud-based cluster
|
||||
|
||||
You can migrate from a source cluster that is behind a firewall to a cloud-based destination cluster by establishing a network tunnel between the two clusters. The `crane tunnel-api` command establishes such a tunnel by creating a VPN tunnel on the source cluster and then connecting to a VPN server running on the destination cluster. The VPN server is exposed to the client using a load balancer address on the destination cluster.
|
||||
|
||||
|
||||
@@ -15,7 +15,7 @@ Operators provide:
|
||||
--
|
||||
|
||||
Why deploy on Kubernetes?::
|
||||
Kubernetes (and by extension, {product-title}) contains all of the primitives needed to build complex distributed systems – secret handling, load balancing, service discovery, autoscaling – that work across on-premises and cloud providers.
|
||||
Kubernetes (and by extension, {product-title}) contains all of the primitives needed to build complex distributed systems – secret handling, load balancing, service discovery, autoscaling – that work across on-premise and cloud providers.
|
||||
|
||||
Why manage your app with Kubernetes APIs and `kubectl` tooling?::
|
||||
These APIs are feature rich, have clients for all platforms and plug into the cluster's access control/auditing. An Operator uses the Kubernetes extension mechanism, custom resource definitions (CRDs), so your custom object, link:https://marketplace.redhat.com/en-us/products/mongodb-enterprise-advanced-from-ibm[for example `MongoDB`], looks and acts just like the built-in, native Kubernetes objects.
|
||||
|
||||
@@ -73,7 +73,7 @@ Red Hat is responsible for enabling changes to the cluster infrastructure and se
|
||||
|
||||
|Virtual networking
|
||||
|* Set up and configure virtual networking components required to provision the cluster, including virtual private cloud, subnets, load balancers, internet gateways, NAT gateways, etc.
|
||||
* Provide the ability for the customer to manage VPN connectivity with on-premises resources, VPC to VPC connectivity, and Direct connectivity as required through {cluster-manager}.
|
||||
* Provide the ability for the customer to manage VPN connectivity with on-premise resources, VPC to VPC connectivity, and Direct connectivity as required through {cluster-manager}.
|
||||
* Setup and configure PSC attachments. ^[1]^
|
||||
* Enable customers to create and deploy public cloud load balancers for use with service load balancers.
|
||||
|* Set up and maintain optional public cloud networking components, such as VPC to VPC connection, VPN connection, or Direct connection.
|
||||
@@ -172,4 +172,4 @@ Disaster recovery includes data and configuration backup, replicating data and c
|
||||
|* Configure virtual networking connections with more than one tunnel where possible for protection against outages as recommended by the public cloud provider.
|
||||
* Maintain failover DNS and load balancing if using a global load balancer with multiple clusters.
|
||||
|
||||
|===
|
||||
|===
|
||||
|
||||
@@ -12,7 +12,7 @@
|
||||
|
||||
{rh-storage-first} integrates multiple storage types that you can use with the {product-registry}:
|
||||
|
||||
* Ceph, a shared and distributed file system and on-premises object storage
|
||||
* Ceph, a shared and distributed file system and on-premise object storage
|
||||
* NooBaa, providing a Multicloud Object Gateway
|
||||
|
||||
This document outlines the procedure to configure the image registry to use CephFS storage.
|
||||
|
||||
@@ -12,7 +12,7 @@
|
||||
|
||||
{rh-storage-first} integrates multiple storage types that you can use with the {product-registry}:
|
||||
|
||||
* Ceph, a shared and distributed file system and on-premises object storage
|
||||
* Ceph, a shared and distributed file system and on-premise object storage
|
||||
* NooBaa, providing a Multicloud Object Gateway
|
||||
|
||||
This document outlines the procedure to configure the image registry to use Ceph RGW storage.
|
||||
|
||||
@@ -12,7 +12,7 @@
|
||||
|
||||
{rh-storage-first} integrates multiple storage types that you can use with the {product-registry}:
|
||||
|
||||
* Ceph, a shared and distributed file system and on-premises object storage
|
||||
* Ceph, a shared and distributed file system and on-premise object storage
|
||||
* NooBaa, providing a Multicloud Object Gateway
|
||||
|
||||
This document outlines the procedure to configure the image registry to use Noobaa storage.
|
||||
|
||||
@@ -126,7 +126,7 @@ You can review the history of all cluster upgrade events in the {cluster-manager
|
||||
- Set up and configure Amazon VPC components required to provision the cluster, such as subnets, load balancers, internet gateways, and NAT gateways.
|
||||
|
||||
- Provide the ability for the customer to
|
||||
manage AWS VPN connectivity with on-premises resources, Amazon VPC-to-VPC connectivity, and AWS Direct Connect as required through {cluster-manager}.
|
||||
manage AWS VPN connectivity with on-premise resources, Amazon VPC-to-VPC connectivity, and AWS Direct Connect as required through {cluster-manager}.
|
||||
|
||||
- Enable customers to create and deploy AWS load balancers for use with service load balancers.
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ With its foundation in Kubernetes, {product-title} is a complete {OCP} cluster p
|
||||
|
||||
{product-title} is professionally managed by Red Hat and hosted on {GCP} or {AWS}. Each {product-title} cluster includes a fully managed link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/architecture/control-plane[control plane] (Control and Infrastructure nodes), application nodes, installation and management by Red Hat Site Reliability Engineers (SRE), premium Red Hat Support, and cluster services such as logging, metrics, monitoring, notifications portal, and a cluster portal.
|
||||
|
||||
{product-title} clusters are available on the link:https://console.redhat.com/openshift[Hybrid Cloud Console]. With the Red Hat {cluster-manager} application, you can deploy {product-title} clusters to either on-premises or cloud environments.
|
||||
{product-title} clusters are available on the link:https://console.redhat.com/openshift[Hybrid Cloud Console]. With the Red Hat {cluster-manager} application, you can deploy {product-title} clusters to either on-premise or cloud environments.
|
||||
|
||||
[id="osd-new-changes-and-updates_{context}"]
|
||||
== New changes and updates
|
||||
|
||||
@@ -9,7 +9,7 @@ toc::[]
|
||||
|
||||
{product-title} (ROSA) is a fully-managed, turnkey application platform that allows you to focus on delivering value to your customers by building and deploying applications. Red{nbsp}Hat and AWS site reliability engineering (SRE) experts manage the underlying platform so you do not have to worry about the complexity of infrastructure management. ROSA provides seamless integration with a wide range of AWS compute, database, analytics, machine learning, networking, mobile, and other services to further accelerate the building and delivering of differentiating experiences to your customers.
|
||||
|
||||
{product-title} clusters are available on the link:https://console.redhat.com/openshift[Hybrid Cloud Console]. With the Red{nbsp}Hat {cluster-manager} application for ROSA, you can deploy {product-title} clusters to either on-premises or cloud environments.
|
||||
{product-title} clusters are available on the link:https://console.redhat.com/openshift[Hybrid Cloud Console]. With the Red{nbsp}Hat {cluster-manager} application for ROSA, you can deploy {product-title} clusters to either on-premise or cloud environments.
|
||||
|
||||
[id="rosa-new-changes-and-updates_{context}"]
|
||||
== New changes and updates
|
||||
|
||||
@@ -8,7 +8,7 @@ toc::[]
|
||||
|
||||
== Overview
|
||||
|
||||
{product-title} is capable of provisioning persistent volumes (PVs) using the Container Storage Interface (CSI) driver for Azure Stack Hub Storage. Azure Stack Hub, which is part of the Azure Stack portfolio, allows you to run apps in an on-premises environment and deliver Azure services in your datacenter.
|
||||
{product-title} is capable of provisioning persistent volumes (PVs) using the Container Storage Interface (CSI) driver for Azure Stack Hub Storage. Azure Stack Hub, which is part of the Azure Stack portfolio, allows you to run apps in an on-premise environment and deliver Azure services in your datacenter.
|
||||
|
||||
Familiarity with xref:../../storage/understanding-persistent-storage.adoc#understanding-persistent-storage[persistent storage] and xref:../../storage/container_storage_interface/persistent-storage-csi.adoc#persistent-storage-csi[configuring CSI volumes] is recommended when working with a CSI Operator and driver.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user