diff --git a/modules/apis.adoc b/modules/apis.adoc index 1d8126d3dfff..bb712df3b65e 100644 --- a/modules/apis.adoc +++ b/modules/apis.adoc @@ -6609,7 +6609,7 @@ The following table describes the parameters for CinderPersistentVolumeSource ob | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | `secretRef` | SecretReference -| Optional: points to a secret object containing parameters used to connect to OpenStack. +| Optional: points to a secret object containing parameters used to connect to {rh-openstack-first}. | `volumeID` | string | volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md @@ -9564,7 +9564,7 @@ The following table describes the parameters for CinderVolumeSource object: | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | `secretRef` | LocalObjectReference -| Optional: points to a secret object containing parameters used to connect to OpenStack. +| Optional: points to a secret object containing parameters used to connect to {rh-openstack}. | `volumeID` | string | volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md @@ -12827,7 +12827,7 @@ The following table describes the parameters for CinderVolumeSource object: | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | `secretRef` | LocalObjectReference -| Optional: points to a secret object containing parameters used to connect to OpenStack. +| Optional: points to a secret object containing parameters used to connect to {rh-openstack}. | `volumeID` | string | volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md @@ -15524,7 +15524,7 @@ The following table describes the parameters for CinderVolumeSource object: | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | `secretRef` | LocalObjectReference -| Optional: points to a secret object containing parameters used to connect to OpenStack. +| Optional: points to a secret object containing parameters used to connect to {rh-openstack}. | `volumeID` | string | volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md @@ -19325,7 +19325,7 @@ The following table describes the parameters for LoadBalancerIngress object: | Hostname is set for load-balancer ingress points that are DNS based (typically AWS load-balancers) | `ip` | string -| IP is set for load-balancer ingress points that are IP based (typically GCE or OpenStack load-balancers) +| IP is set for load-balancer ingress points that are IP based (typically GCE or {rh-openstack} load-balancers) |=== ==== SessionAffinityConfig [v1/core] @@ -26811,7 +26811,7 @@ The following table describes the parameters for CinderVolumeSource object: | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | `secretRef` | LocalObjectReference -| Optional: points to a secret object containing parameters used to connect to OpenStack. +| Optional: points to a secret object containing parameters used to connect to {rh-openstack}. | `volumeID` | string | volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md @@ -29680,7 +29680,7 @@ The following table describes the parameters for CinderVolumeSource object: | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | `secretRef` | LocalObjectReference -| Optional: points to a secret object containing parameters used to connect to OpenStack. +| Optional: points to a secret object containing parameters used to connect to {rh-openstack}. | `volumeID` | string | volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md @@ -32631,7 +32631,7 @@ The following table describes the parameters for CinderVolumeSource object: | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | `secretRef` | LocalObjectReference -| Optional: points to a secret object containing parameters used to connect to OpenStack. +| Optional: points to a secret object containing parameters used to connect to {rh-openstack}. | `volumeID` | string | volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md @@ -35920,7 +35920,7 @@ The following table describes the parameters for CinderVolumeSource object: | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | `secretRef` | LocalObjectReference -| Optional: points to a secret object containing parameters used to connect to OpenStack. +| Optional: points to a secret object containing parameters used to connect to {rh-openstack}. | `volumeID` | string | volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md @@ -38846,7 +38846,7 @@ The following table describes the parameters for CinderVolumeSource object: | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | `secretRef` | LocalObjectReference -| Optional: points to a secret object containing parameters used to connect to OpenStack. +| Optional: points to a secret object containing parameters used to connect to {rh-openstack}. | `volumeID` | string | volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md @@ -45542,7 +45542,7 @@ The following table describes the parameters for CinderVolumeSource object: | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | `secretRef` | LocalObjectReference -| Optional: points to a secret object containing parameters used to connect to OpenStack. +| Optional: points to a secret object containing parameters used to connect to {rh-openstack}. | `volumeID` | string | volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md @@ -48377,7 +48377,7 @@ The following table describes the parameters for CinderVolumeSource object: | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | `secretRef` | LocalObjectReference -| Optional: points to a secret object containing parameters used to connect to OpenStack. +| Optional: points to a secret object containing parameters used to connect to {rh-openstack}. | `volumeID` | string | volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md @@ -60002,7 +60002,7 @@ The following table describes the parameters for CinderVolumeSource object: | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | `secretRef` | LocalObjectReference -| Optional: points to a secret object containing parameters used to connect to OpenStack. +| Optional: points to a secret object containing parameters used to connect to {rh-openstack}. | `volumeID` | string | volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md @@ -62897,7 +62897,7 @@ The following table describes the parameters for CinderVolumeSource object: | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | `secretRef` | LocalObjectReference -| Optional: points to a secret object containing parameters used to connect to OpenStack. +| Optional: points to a secret object containing parameters used to connect to {rh-openstack}. | `volumeID` | string | volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md @@ -65004,7 +65004,7 @@ The following table describes the parameters for LoadBalancerIngress object: | Hostname is set for load-balancer ingress points that are DNS based (typically AWS load-balancers) | `ip` | string -| IP is set for load-balancer ingress points that are IP based (typically GCE or OpenStack load-balancers) +| IP is set for load-balancer ingress points that are IP based (typically GCE or {rh-openstack} load-balancers) |=== ==== IngressTLS [v1beta1/extensions] @@ -68700,7 +68700,7 @@ The following table describes the parameters for CinderVolumeSource object: | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | `secretRef` | LocalObjectReference -| Optional: points to a secret object containing parameters used to connect to OpenStack. +| Optional: points to a secret object containing parameters used to connect to {rh-openstack}. | `volumeID` | string | volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md @@ -75699,7 +75699,7 @@ The following table describes the parameters for LoadBalancerIngress object: | Hostname is set for load-balancer ingress points that are DNS based (typically AWS load-balancers) | `ip` | string -| IP is set for load-balancer ingress points that are IP based (typically GCE or OpenStack load-balancers) +| IP is set for load-balancer ingress points that are IP based (typically GCE or {rh-openstack} load-balancers) |=== ==== IngressTLS [v1beta1/networking] @@ -90729,7 +90729,7 @@ The following table describes the parameters for CinderVolumeSource object: | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | `secretRef` | LocalObjectReference -| Optional: points to a secret object containing parameters used to connect to OpenStack. +| Optional: points to a secret object containing parameters used to connect to {rh-openstack}. | `volumeID` | string | volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md @@ -92819,7 +92819,7 @@ The following table describes the parameters for CinderVolumeSource object: | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | `secretRef` | LocalObjectReference -| Optional: points to a secret object containing parameters used to connect to OpenStack. +| Optional: points to a secret object containing parameters used to connect to {rh-openstack}. | `volumeID` | string | volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md @@ -94915,7 +94915,7 @@ The following table describes the parameters for CinderVolumeSource object: | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | `secretRef` | LocalObjectReference -| Optional: points to a secret object containing parameters used to connect to OpenStack. +| Optional: points to a secret object containing parameters used to connect to {rh-openstack}. | `volumeID` | string | volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md @@ -99258,7 +99258,7 @@ The following table describes the parameters for CinderPersistentVolumeSource ob | Optional: Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts. More info: https://examples.k8s.io/mysql-cinder-pd/README.md | `secretRef` | SecretReference -| Optional: points to a secret object containing parameters used to connect to OpenStack. +| Optional: points to a secret object containing parameters used to connect to {rh-openstack}. | `volumeID` | string | volume id used to identify the volume in cinder. More info: https://examples.k8s.io/mysql-cinder-pd/README.md diff --git a/modules/cluster-storage-operator.adoc b/modules/cluster-storage-operator.adoc index fb483b5a164c..4ab526b00d5c 100644 --- a/modules/cluster-storage-operator.adoc +++ b/modules/cluster-storage-operator.adoc @@ -24,6 +24,6 @@ No configuration is required. [discrete] == Notes -* The Cluster Storage Operator supports Amazon Web Services (AWS) and Red Hat OpenStack. +* The Cluster Storage Operator supports Amazon Web Services (AWS) and {rh-openstack-first}. * The created storage class can be made non-default by editing its annotation, but -the storage class cannot be deleted as long as the Operator runs. +the storage class cannot be deleted as long as the Operator runs. \ No newline at end of file diff --git a/modules/cnf-understanding-low-latency.adoc b/modules/cnf-understanding-low-latency.adoc index a42e1469ee87..c33916c213ae 100644 --- a/modules/cnf-understanding-low-latency.adoc +++ b/modules/cnf-understanding-low-latency.adoc @@ -20,7 +20,7 @@ Many of the deployed applications in the Telco space require low latency that can only tolerate zero packet loss. Tuning for zero packet loss helps mitigate the inherent issues that degrade network performance. For more information, see link:https://www.redhat.com/en/blog/tuning-zero-packet-loss-red-hat-openstack-platform-part-1[Tuning -for Zero Packet Loss in Red Hat OpenStack Platform]. +for Zero Packet Loss in {rh-openstack-first}]. The Edge computing initiative also comes in to play for reducing latency rates. Think of it as literally being on the edge of the cloud and closer to the user. diff --git a/modules/dynamic-provisioning-available-plugins.adoc b/modules/dynamic-provisioning-available-plugins.adoc index 6f9937ff4fdf..bd1fe7050f85 100644 --- a/modules/dynamic-provisioning-available-plugins.adoc +++ b/modules/dynamic-provisioning-available-plugins.adoc @@ -17,7 +17,7 @@ configured provider's API to create new storage resources: |Provisioner plug-in name |Notes -|OpenStack Cinder +|{rh-openstack-first} Cinder |`kubernetes.io/cinder` | diff --git a/modules/dynamic-provisioning-cinder-definition.adoc b/modules/dynamic-provisioning-cinder-definition.adoc index 6ee6152a7136..712207f7445b 100644 --- a/modules/dynamic-provisioning-cinder-definition.adoc +++ b/modules/dynamic-provisioning-cinder-definition.adoc @@ -3,7 +3,7 @@ // * storage/dynamic-provisioning.adoc [id="openstack-cinder-storage-class_{context}"] -= OpenStack Cinder object definition += {rh-openstack} Cinder object definition .cinder-storageclass.yaml [source,yaml] diff --git a/modules/installation-initializing.adoc b/modules/installation-initializing.adoc index e48560d26f6d..cba063a3a96e 100644 --- a/modules/installation-initializing.adoc +++ b/modules/installation-initializing.adoc @@ -94,7 +94,7 @@ ifdef::gcp[] Google Cloud Platform (GCP). endif::gcp[] ifdef::osp[] -OpenStack. +{rh-openstack-first}. endif::osp[] ifdef::rhv[] {rh-virtualization-first}. diff --git a/modules/installation-osp-about-kuryr.adoc b/modules/installation-osp-about-kuryr.adoc index 0d92ba774572..293ffccf45fd 100644 --- a/modules/installation-osp-about-kuryr.adoc +++ b/modules/installation-osp-about-kuryr.adoc @@ -6,16 +6,16 @@ = About Kuryr SDN link:https://docs.openstack.org/kuryr-kubernetes/latest/[Kuryr] is a container -network interface (CNI) plug-in solution that uses -link:https://docs.openstack.org/neutron/latest/[OpenStack Neutron] and -link:https://docs.openstack.org/octavia/latest/[OpenStack Octavia] to provide -networking for Pods and Services. +network interface (CNI) plug-in solution that uses the +link:https://docs.openstack.org/neutron/latest/[Neutron] and +link:https://docs.openstack.org/octavia/latest/[Octavia] {rh-openstack-first} services +to provide networking for Pods and Services. Kuryr and {product-title} integration is primarily designed for -{product-title} clusters running on OpenStack VMs. Kuryr improves the -network performance by plugging OpenShift Pods into OpenStack SDN. -In addition, it provides interconnectivity between OpenShift Pods and -OpenStack virtual instances. +{product-title} clusters running on {rh-openstack} VMs. Kuryr improves the +network performance by plugging {product-title} Pods into {rh-openstack} SDN. +In addition, it provides interconnectivity between Pods and +{rh-openstack} virtual instances. Kuryr components are installed as Pods in {product-title} using the `openshift-kuryr` namespace: @@ -33,9 +33,9 @@ used to back {product-title} via Kuryr. This includes open source solutions such as Open vSwitch (OVS) and Open Virtual Network (OVN) as well as Neutron-compatible commercial SDNs. -Kuryr is recommended for OpenShift deployments on encapsulated OpenStack tenant +Kuryr is recommended for {product-title} deployments on encapsulated {rh-openstack} tenant networks to avoid double encapsulation, such as running an encapsulated -OpenShift SDN over an OpenStack network. +{product-title} SDN over an {rh-openstack} network. If you use provider networks or tenant VLANs, you do not need to use Kuryr to avoid double encapsulation. The performance benefit is negligible. Depending on diff --git a/modules/installation-osp-config-yaml.adoc b/modules/installation-osp-config-yaml.adoc index 1b32de5f54fa..18dddfbd7fca 100644 --- a/modules/installation-osp-config-yaml.adoc +++ b/modules/installation-osp-config-yaml.adoc @@ -4,7 +4,7 @@ // * installing/installing_openstack/installing-openstack-installer-kuryr.adoc [id="installation-osp-config-yaml_{context}"] -= Sample customized `install-config.yaml` file for OpenStack += Sample customized `install-config.yaml` file for {rh-openstack} This sample `install-config.yaml` demonstrates all of the possible {rh-openstack-first} customization options. diff --git a/modules/installation-osp-converting-ignition-resources.adoc b/modules/installation-osp-converting-ignition-resources.adoc index 046b6b9d959d..cf3b31a55d5d 100644 --- a/modules/installation-osp-converting-ignition-resources.adoc +++ b/modules/installation-osp-converting-ignition-resources.adoc @@ -8,7 +8,7 @@ The {product-title} installation process relies on bootstrap machines that are created from a bootstrap Ignition configuration file. Edit the file and upload it. Then, create a secondary bootstrap Ignition configuration file that -{rh-openstack} uses to download the primary file. +{rh-openstack-first} uses to download the primary file. .Prerequisites @@ -16,7 +16,7 @@ Edit the file and upload it. Then, create a secondary bootstrap Ignition configu * The infrastructure ID from the installer's metadata file is set as an environment variable (`$INFRA_ID`). ** If the variable is not set, see *Creating the Kubernetes manifest and Ignition config files*. * You have an HTTP(S)-accessible way to store the bootstrap ignition file. -** The documented procedure uses the OpenStack Image service (Glance), but you can also use the OpenStack Storage service (Swift), Amazon S3, an internal HTTP server, or an ad hoc Nova server. +** The documented procedure uses the {rh-openstack} Image service (Glance), but you can also use the {rh-openstack} Storage service (Swift), Amazon S3, an internal HTTP server, or an ad hoc Nova server. .Procedure @@ -69,7 +69,7 @@ with open('bootstrap.ign', 'w') as f: json.dump(ignition, f) ---- -. Using the OpenStack CLI, create an image that uses the bootstrap Ignition file: +. Using the {rh-openstack} CLI, create an image that uses the bootstrap Ignition file: + ---- $ openstack image create --disk-format=raw --container-format=bare --file bootstrap.ign diff --git a/modules/installation-osp-creating-image.adoc b/modules/installation-osp-creating-image.adoc index 0bf6a8eb7f77..ae660e9c4564 100644 --- a/modules/installation-osp-creating-image.adoc +++ b/modules/installation-osp-creating-image.adoc @@ -31,7 +31,7 @@ your {product-title} version if they are available. + [NOTE] ==== -You must decompress the OpenStack image before the cluster can use it. The name of the downloaded file might not contain a compression extension, like `.gz` or `.tgz`. To find out if or how the file is compressed, in a command line, enter: +You must decompress the {rh-openstack} image before the cluster can use it. The name of the downloaded file might not contain a compression extension, like `.gz` or `.tgz`. To find out if or how the file is compressed, in a command line, enter: ---- $ file diff --git a/modules/installation-osp-creating-network-resources.adoc b/modules/installation-osp-creating-network-resources.adoc index 8c754d225a02..1e448f83b0fa 100644 --- a/modules/installation-osp-creating-network-resources.adoc +++ b/modules/installation-osp-creating-network-resources.adoc @@ -679,7 +679,7 @@ $ ansible-playbook -i inventory.yaml 01_security-groups.yaml $ ansible-playbook -i inventory.yaml 02_network.yaml ---- -. _Optional_: If you want to control the default resolvers that Nova servers use, run the OpenStack CLI command: +. _Optional_: If you want to control the default resolvers that Nova servers use, run the {rh-openstack} CLI command: + ---- $ openstack subnet set --dns-nameserver --dns-nameserver "$INFRA_ID-nodes" diff --git a/modules/installation-osp-default-deployment.adoc b/modules/installation-osp-default-deployment.adoc index 84dbd0d49425..efad71970a13 100644 --- a/modules/installation-osp-default-deployment.adoc +++ b/modules/installation-osp-default-deployment.adoc @@ -5,7 +5,7 @@ // * installing/installing_openstack/installing-openstack-user.adoc [id="installation-osp-default-deployment_{context}"] -= Resource guidelines for installing {product-title} on OpenStack += Resource guidelines for installing {product-title} on {rh-openstack} To support a {product-title} installation, your {rh-openstack-first} quota must meet the following requirements: @@ -29,7 +29,7 @@ A cluster might function with fewer than recommended resources, but its performa [IMPORTANT] ==== -If OpenStack Object Storage (Swift) is available and operated by a user account with the `swiftoperator` role, it is used as the default backend for the {product-title} image registry. In this case, the volume storage requirement is 175 GB. Swift space requirements vary depending on the size of the image registry. +If {rh-openstack} Object Storage (Swift) is available and operated by a user account with the `swiftoperator` role, it is used as the default backend for the {product-title} image registry. In this case, the volume storage requirement is 175 GB. Swift space requirements vary depending on the size of the image registry. ==== [NOTE] diff --git a/modules/installation-osp-default-kuryr-deployment.adoc b/modules/installation-osp-default-kuryr-deployment.adoc index ecad7d2704e6..2eb44bc13dbe 100644 --- a/modules/installation-osp-default-kuryr-deployment.adoc +++ b/modules/installation-osp-default-kuryr-deployment.adoc @@ -3,7 +3,7 @@ // * installing/installing_openstack/installing-openstack-installer-kuryr.adoc [id="installation-osp-default-kuryr-deployment_{context}"] -= Resource guidelines for installing {product-title} on OpenStack with Kuryr += Resource guidelines for installing {product-title} on {rh-openstack} with Kuryr When using Kuryr SDN, the Pods, Services, namespaces, and network policies are using resources from the {rh-openstack} quota; this increases the minimum @@ -37,7 +37,7 @@ A cluster might function with fewer than recommended resources, but its performa [IMPORTANT] ==== -If OpenStack Object Storage (Swift) is available and operated by a user account with the `swiftoperator` role, it is used as the default backend for the {product-title} image registry. In this case, the volume storage requirement is 175 GB. Swift space requirements vary depending on the size of the image registry. +If {rh-openstack} Object Storage (Swift) is available and operated by a user account with the `swiftoperator` role, it is used as the default backend for the {product-title} image registry. In this case, the volume storage requirement is 175 GB. Swift space requirements vary depending on the size of the image registry. ==== [IMPORTANT] @@ -78,7 +78,7 @@ machines, and a bootstrap machine. To enable Kuryr SDN, your environment must meet the following requirements: -* Run OpenStack 13+. +* Run {rh-openstack} 13+. * Have Overcloud with Octavia. * Use Neutron Trunk ports extension. * Use `openvswitch` firewall driver if ML2/OVS Neutron driver is used instead diff --git a/modules/installation-osp-describing-cloud-parameters.adoc b/modules/installation-osp-describing-cloud-parameters.adoc index 8b9615817145..be110f950211 100644 --- a/modules/installation-osp-describing-cloud-parameters.adoc +++ b/modules/installation-osp-describing-cloud-parameters.adoc @@ -14,14 +14,14 @@ The {product-title} installation program relies on a file that is called `clouds . Create the `clouds.yaml` file: -** If your OpenStack distribution includes the Horizon web UI, generate a `clouds.yaml` file in it. +** If your {rh-openstack} distribution includes the Horizon web UI, generate a `clouds.yaml` file in it. + [IMPORTANT] ==== Remember to add a password to the `auth` field. You can also keep secrets in link:https://docs.openstack.org/os-client-config/latest/user/configuration.html#splitting-secrets[a separate file] from `clouds.yaml`. ==== -** If your OpenStack distribution does not include the Horizon web UI, or you do not want to use Horizon, create the file yourself. For detailed information about `clouds.yaml`, see https://docs.openstack.org/openstacksdk/latest/user/config/configuration.html#config-files[Config files] in the {rh-openstack} documentation. +** If your {rh-openstack} distribution does not include the Horizon web UI, or you do not want to use Horizon, create the file yourself. For detailed information about `clouds.yaml`, see https://docs.openstack.org/openstacksdk/latest/user/config/configuration.html#config-files[Config files] in the {rh-openstack} documentation. + ---- clouds: diff --git a/modules/installation-osp-enabling-swift.adoc b/modules/installation-osp-enabling-swift.adoc index 5a7174f6bd09..bae19ae43a1e 100644 --- a/modules/installation-osp-enabling-swift.adoc +++ b/modules/installation-osp-enabling-swift.adoc @@ -5,13 +5,12 @@ // * installing/installing_openstack/installing-openstack-installer-kuryr.adoc [id="installation-osp-enabling-swift_{context}"] -= Enabling Swift on OpenStack - += Enabling Swift on {rh-openstack} Swift is operated by a user account with the `swiftoperator` role. Add the role to an account before you run the installation program. [IMPORTANT] ==== -If link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0/html-single/storage_guide/index#ch-manage-containers[OpenStack Object Storage (Swift)] is available, {product-title} on {rh-openstack-first} uses it as the image registry storage. If it is unavailable, the installation program relies on the OpenStack Block Storage service (Cinder). +If link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0/html-single/storage_guide/index#ch-manage-containers[the {rh-openstack-first} Object Storage service], commonly known as Swift, is available, {product-title} uses it as the image registry storage. If it is unavailable, the installation program relies on the {rh-openstack} Block Storage service, commonly known as Cinder. If Swift is present and you want to use it, you must enable access to it. If it is not present, or if you do not want to use it, skip this section. ==== diff --git a/modules/installation-osp-kuryr-config-yaml.adoc b/modules/installation-osp-kuryr-config-yaml.adoc index bafcbfb74b36..5e7dceed0909 100644 --- a/modules/installation-osp-kuryr-config-yaml.adoc +++ b/modules/installation-osp-kuryr-config-yaml.adoc @@ -3,7 +3,7 @@ // * installing/installing_openstack/installing-openstack-installer-kuryr.adoc [id="installation-osp-kuryr-config-yaml_{context}"] -= Sample customized `install-config.yaml` file for OpenStack with Kuryr += Sample customized `install-config.yaml` file for {rh-openstack} with Kuryr To deploy with Kuryr SDN instead of the default OpenShift SDN, you must modify the `install-config.yaml` file to include `Kuryr` as the desired @@ -61,6 +61,6 @@ sshKey: ssh-ed25519 AAAA... Both `trunkSupport` and `octaviaSupport` are automatically discovered by the installer, so there is no need to set them. But if your environment does not meet both requirements, Kuryr SDN will not properly work. Trunks are needed -to connect the Pods to the OpenStack network and Octavia is required to create the +to connect the Pods to the {rh-openstack} network and Octavia is required to create the OpenShift Services. ==== diff --git a/modules/installation-osp-kuryr-increase-quota.adoc b/modules/installation-osp-kuryr-increase-quota.adoc index cbe85b307153..42e6d7596a34 100644 --- a/modules/installation-osp-kuryr-increase-quota.adoc +++ b/modules/installation-osp-kuryr-increase-quota.adoc @@ -5,7 +5,7 @@ [id="installation-osp-kuryr-increase-quota_{context}"] = Increasing quota -When using Kuryr SDN, you must increase quotas to satisfy the OpenStack +When using Kuryr SDN, you must increase quotas to satisfy the {rh-openstack-first} resources used by Pods, Services, namespaces, and network policies. .Procedure diff --git a/modules/installation-osp-kuryr-neutron-configuration.adoc b/modules/installation-osp-kuryr-neutron-configuration.adoc index ec5e48cbdbda..4341f276ffd7 100644 --- a/modules/installation-osp-kuryr-neutron-configuration.adoc +++ b/modules/installation-osp-kuryr-neutron-configuration.adoc @@ -6,7 +6,7 @@ = Configuring Neutron Kuryr CNI leverages the Neutron Trunks extension to plug containers into the -OpenStack SDN, so you must use the `trunks` extension for Kuryr to properly work. +{rh-openstack-first} SDN, so you must use the `trunks` extension for Kuryr to properly work. In addition, if you leverage the default ML2/OVS Neutron driver, the firewall must be set to `openvswitch` instead of `ovs_hybrid` so that security groups are diff --git a/modules/installation-osp-kuryr-octavia-configuration.adoc b/modules/installation-osp-kuryr-octavia-configuration.adoc index 2f56b63e8fee..10b6fb8b9390 100644 --- a/modules/installation-osp-kuryr-octavia-configuration.adoc +++ b/modules/installation-osp-kuryr-octavia-configuration.adoc @@ -5,19 +5,19 @@ [id="installation-osp-kuryr-octavia-configuration_{context}"] = Configuring Octavia -Kuryr SDN uses OpenStack Octavia LBaaS to implement OpenShift Services. Thus, -you must install and configure Octavia components in your OpenStack environment +Kuryr SDN uses {rh-openstack-first}'s Octavia LBaaS to implement {product-title} Services. Thus, +you must install and configure Octavia components in {rh-openstack} to use Kuryr SDN. To enable Octavia, you must include the Octavia Service during the installation -of the OpenStack Overcloud, or upgrade the Octavia Service if the Overcloud +of the {rh-openstack} Overcloud, or upgrade the Octavia Service if the Overcloud already exists. The following steps for enabling Octavia apply to both a clean install of the Overcloud or an Overcloud update. [NOTE] ==== The following steps only capture the key pieces required during the -https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/director_installation_and_usage/[deployment of OpenStack] +https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/director_installation_and_usage/[deployment of {rh-openstack}] when dealing with Octavia. It is also important to note that https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/director_installation_and_usage/configuring-a-container-image-source#registry-methods[registry methods] vary. @@ -87,7 +87,7 @@ parameter_defaults: + [NOTE] ==== -This is not needed for Red Hat OpenStack Platform 14+. +This is not needed for {rh-openstack} 14+. ==== . Install or update your Overcloud environment with Octavia: @@ -101,7 +101,7 @@ openstack overcloud deploy --templates \ [NOTE] ==== This command only includes the files associated with Octavia; it varies based on -your specific installation of OpenStack. See the official OpenStack +your specific installation of {rh-openstack}. See the {rh-openstack} documentation for further information. For more information on customizing your Octavia installation, see https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/networking_guide/#planning_your_octavia_deployment[installation @@ -199,7 +199,7 @@ controller-0$ sudo docker restart octavia_worker [NOTE] ==== Depending on your {rh-openstack} environment, Octavia might not support UDP -listeners. If you use Kuryr SDN on OpenStack version 15 or earlier, UDP services are not supported. +listeners. If you use Kuryr SDN on {rh-openstack} version 15 or earlier, UDP services are not supported. {rh-openstack} version 16 or later support UDP. ==== diff --git a/modules/installation-uninstall-infra.adoc b/modules/installation-uninstall-infra.adoc index bf66efb23671..88ff87b08b0f 100644 --- a/modules/installation-uninstall-infra.adoc +++ b/modules/installation-uninstall-infra.adoc @@ -3,7 +3,7 @@ // * installing/installing_osp/uninstalling-cluster-osp.adoc [id="installation-uninstall-infra_{context}"] -= Removing a cluster on OpenStack that uses your own infrastructure += Removing a cluster on {rh-openstack} that uses your own infrastructure You can remove an {product-title} cluster on {rh-openstack-first} that uses your own infrastructure. To complete the removal process quickly, create and run several Ansible playbooks. diff --git a/modules/nodes-containers-projected-volumes-about.adoc b/modules/nodes-containers-projected-volumes-about.adoc index d7f48720c516..99d8fede0f49 100644 --- a/modules/nodes-containers-projected-volumes-about.adoc +++ b/modules/nodes-containers-projected-volumes-about.adoc @@ -16,7 +16,7 @@ The following general scenarios show how you can use projected volumes. *ConfigMap, Secrets, Downward API.*:: Projected volumes allow you to deploy containers with configuration data that includes passwords. -An application using these resources could be deploying OpenStack on Kubernetes. The configuration data might have to be assembled differently depending on if the services are going to be used for production or for testing. If a pod is labeled with production or testing, the downward API selector `metadata.labels` can be used to produce the correct OpenStack configs. +An application using these resources could be deploying {rh-openstack-first} on Kubernetes. The configuration data might have to be assembled differently depending on if the services are going to be used for production or for testing. If a pod is labeled with production or testing, the downward API selector `metadata.labels` can be used to produce the correct {rh-openstack} configs. *ConfigMap + Secrets.*:: Projected volumes allow you to deploy containers involving configuration data and passwords. diff --git a/modules/openshift-cluster-maximums-major-releases.adoc b/modules/openshift-cluster-maximums-major-releases.adoc index d671561541d6..8e9138db104f 100644 --- a/modules/openshift-cluster-maximums-major-releases.adoc +++ b/modules/openshift-cluster-maximums-major-releases.adoc @@ -5,7 +5,7 @@ [id="cluster-maximums-major-releases_{context}"] = {product-title} Tested cluster maximums for major releases -Tested Cloud Platforms for {product-title} 3.x: Red Hat OpenStack, Amazon Web Services and Microsoft Azure. +Tested Cloud Platforms for {product-title} 3.x: {rh-openstack-first}, Amazon Web Services and Microsoft Azure. Tested Cloud Platforms for {product-title} 4.x: Amazon Web Services, Microsoft Azure and Google Cloud Platform. [options="header",cols="3*"] diff --git a/modules/persistent-storage-cinder-creating-pv.adoc b/modules/persistent-storage-cinder-creating-pv.adoc index 3ac59c3e4ce0..35b7a8621710 100644 --- a/modules/persistent-storage-cinder-creating-pv.adoc +++ b/modules/persistent-storage-cinder-creating-pv.adoc @@ -30,7 +30,7 @@ spec: ---- <1> The name of the volume that is used by persistent volume claims or pods. <2> The amount of storage allocated to this volume. -<3> Indicates `cinder` for OpenStack Cinder volumes. +<3> Indicates `cinder` for {rh-openstack-first} Cinder volumes. <4> The file system that is created when the volume is mounted for the first time. <5> The Cinder volume to use. + diff --git a/modules/persistent-storage-cinder-provisioning.adoc b/modules/persistent-storage-cinder-provisioning.adoc index f48be67e2b7d..d77c8ac59f31 100644 --- a/modules/persistent-storage-cinder-provisioning.adoc +++ b/modules/persistent-storage-cinder-provisioning.adoc @@ -9,5 +9,5 @@ Storage must exist in the underlying infrastructure before it can be mounted as .Prerequisites -* {product-title} configured for OpenStack +* {product-title} configured for {rh-openstack-first} * Cinder volume ID diff --git a/modules/persistent-storage-manila-install.adoc b/modules/persistent-storage-manila-install.adoc index 27c4f6ce4774..87fdec6805c5 100644 --- a/modules/persistent-storage-manila-install.adoc +++ b/modules/persistent-storage-manila-install.adoc @@ -5,7 +5,7 @@ [id="persistent-storage-manila-install_{context}"] = Installing the external provisioner -To use OpenStack Manila persistent storage you must install +To use {rh-openstack-first} Manila persistent storage you must install and configure an external provisioner in the {product-title} cluster. @@ -78,12 +78,12 @@ metadata: name: manila-secret <1> namespace: default <2> data: - os-authURL: + os-authURL: os-userName: os-password: - os-projectName: - os-domainName: - os-region: + os-projectName: + os-domainName: + os-region: ---- <1> The secret name will be referenced by the Manila volume's StorageClass. @@ -118,9 +118,9 @@ in. This field is optional, and defaults to `nova`. <4> Backend share used for granting access and creating the `PersistentVolumeSource`. Valid options are `nfs` and `cephfs`. This field is required. -<5> Name of the secret object containing OpenStack credentials. +<5> Name of the secret object containing {rh-openstack} credentials. This field is required. -<6> Namespace of the OpenStack credentials secret object. This field +<6> Namespace of the {rh-openstack} credentials secret object. This field is optional, and defaults to `default`. <7> Default NFS client for the share exported. This field is optional, and is only used for the `NFS` protocol. Defaults to `0.0.0.0`. diff --git a/modules/persistent-storage-manila-usage.adoc b/modules/persistent-storage-manila-usage.adoc index 69e72fe95240..2eda8b122e89 100644 --- a/modules/persistent-storage-manila-usage.adoc +++ b/modules/persistent-storage-manila-usage.adoc @@ -3,15 +3,15 @@ // * storage/persistent_storage/persistent-storage-manila.adoc [id="persistent-storage-manila-usage_{context}"] -= Provisioning an OpenStack Manila persistent volume += Provisioning an {rh-openstack} Manila persistent volume -OpenStack Manila shares are dynamically provisioned as needed. When the +{rh-openstack-first} Manila shares are dynamically provisioned as needed. When the PersistentVolumeClaim is deleted the provisioner will automatically -delete and unexport the OpenStack Manila share. +delete and unexport the {rh-openstack} Manila share. .Prerequisites -* The OpenStack Manila external provisioner must be installed. +* The {rh-openstack} Manila external provisioner must be installed. .Procedure diff --git a/modules/prometheus-database-storage-requirements.adoc b/modules/prometheus-database-storage-requirements.adoc index 03e9ac4ee9a9..2a535a2642bd 100644 --- a/modules/prometheus-database-storage-requirements.adoc +++ b/modules/prometheus-database-storage-requirements.adoc @@ -57,14 +57,14 @@ per 50 nodes and 1800 pods. *Lab environment* In a previous release, all experiments were performed in an {product-title} on -OpenStack environment: +{rh-openstack} environment: * Infra nodes (VMs) - 40 cores, 157 GB RAM. * CNS nodes (VMs) - 16 cores, 62 GB RAM, NVMe drives. [IMPORTANT] ==== -Currently, OpenStack environments are not supported for {product-title} {product-version}. +Currently, {rh-openstack} environments are not supported for {product-title} {product-version}. ==== *Recommendations for {product-title}* diff --git a/modules/recommended-configurable-storage-technology.adoc b/modules/recommended-configurable-storage-technology.adoc index 0636442728d3..810b0c5132ab 100644 --- a/modules/recommended-configurable-storage-technology.adoc +++ b/modules/recommended-configurable-storage-technology.adoc @@ -143,5 +143,5 @@ with the storage layer. * It is highly recommended that you use `etcd` with storage that handles serial writes (fsync) quickly, such as NVMe or SSD. Ceph, NFS, and spinning disks are not recommended. -* OpenStack Cinder: OpenStack Cinder tends to be adept in ROX access mode use cases. +* {rh-openstack-first} Cinder: {rh-openstack} Cinder tends to be adept in ROX access mode use cases. * Databases: Databases (RDBMSs, NoSQL DBs, etc.) tend to perform best with dedicated block storage. diff --git a/modules/registry-configuring-storage-openstack-user-infra.adoc b/modules/registry-configuring-storage-openstack-user-infra.adoc index 2f7d16c43ec5..50c0e1f3bba8 100644 --- a/modules/registry-configuring-storage-openstack-user-infra.adoc +++ b/modules/registry-configuring-storage-openstack-user-infra.adoc @@ -3,17 +3,17 @@ // * registry/configuring_registry_storage-openstack-user-infrastructure.adoc [id="registry-configuring-storage-openstack-user-infra_{context}"] -= Registry storage for OpenStack with user-provisioned infrastructure += Registry storage for {rh-openstack} with user-provisioned infrastructure You must set up the storage medium manually and configure the settings in the registry CRD. .Prerequisites -* A cluster on OpenStack with user-provisioned infrastructure. -* To configure registry storage for OpenStack, you need to provide Registry Operator +* A cluster on {rh-openstack-first} with user-provisioned infrastructure. +* To configure registry storage for {rh-openstack}, you need to provide Registry Operator cloud credentials. -* For Swift on OpenStack storage the secret is expected to contain the following two keys: +* For Swift on {rh-openstack} storage the secret is expected to contain the following two keys: ** `REGISTRY_STORAGE_SWIFT_USER` ** `REGISTRY_STORAGE_SWIFT_PASSWORD` diff --git a/modules/registry-operator-config-resources-secret-openstack.adoc b/modules/registry-operator-config-resources-secret-openstack.adoc index e1670d971152..12bc82d12686 100644 --- a/modules/registry-operator-config-resources-secret-openstack.adoc +++ b/modules/registry-operator-config-resources-secret-openstack.adoc @@ -14,7 +14,7 @@ The `image-registry-private-configuration-user` secret provides credentials needed for storage access and management. It overrides the default credentials used by the Operator, if default credentials were found. -For Swift on OpenStack storage, the secret is expected to contain the following two keys: +For Swift on {rh-openstack-first} storage, the secret is expected to contain the following two keys: * `REGISTRY_STORAGE_SWIFT_USER` * `REGISTRY_STORAGE_SWIFT_PASSWORD` diff --git a/modules/registry-operator-configuration-resource-overview-openstack-swift.adoc b/modules/registry-operator-configuration-resource-overview-openstack-swift.adoc index 48cee8d2fc81..7a7f8287f52b 100644 --- a/modules/registry-operator-configuration-resource-overview-openstack-swift.adoc +++ b/modules/registry-operator-configuration-resource-overview-openstack-swift.adoc @@ -3,9 +3,9 @@ // * registry/configuring_registry_storage/configuring-registry-storage-openstack-user-infrastructure.adoc [id="registry-operator-configuration-resource-overview-openstack-swift_{context}"] -= Image Registry Operator configuration parameters for OpenStack Swift += Image Registry Operator configuration parameters for {rh-openstack} Swift -The following configuration parameters are available for OpenStack Swift +The following configuration parameters are available for {rh-openstack-first} Swift registry storage. [cols="3a,8a",options="header"] diff --git a/welcome/index.adoc b/welcome/index.adoc index 0c61f0d92559..85ed3f1cd9ab 100644 --- a/welcome/index.adoc +++ b/welcome/index.adoc @@ -43,8 +43,8 @@ or using xref:../installing/installing_azure/installing-azure-user-infra.adoc#in - **xref:../installing/installing_bare_metal/installing-bare-metal.adoc#installing-bare-metal[Install a cluster on bare metal]**: If none of the available platform and cloud providers meet your needs, you can install {product-title} on bare metal. -- **Install a cluster on OpenStack Platform**: You can install a cluster on -xref:../installing/installing_openstack/installing-openstack-installer-custom.adoc#installing-openstack-installer-custom[OpenStack with customizations]. +- **Install a cluster on {rh-openstack-first}**: You can install a cluster on +xref:../installing/installing_openstack/installing-openstack-installer-custom.adoc#installing-openstack-installer-custom[{rh-openstack} with customizations]. //// You can configure an external load balancer for