Skip to content

[enterprise-4.2] Revoke "RHOSP" initialism treatment #17405

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bergerhoffer merged 1 commit into from
Oct 16, 2019
Merged

[enterprise-4.2] Revoke "RHOSP" initialism treatment #17405

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion modules/installation-initializing.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@ ifdef::osp[]
.. Select *openstack* as the platform to target.
.. Specify the {rh-openstack-first} external network name to use for installing the cluster.
.. Specify the Floating IP address to use for external access to the OpenShift API.
.. Specify an {rh-openstack} flavor with at least 16 GB RAM to use for control plane
.. Specify a {rh-openstack} flavor with at least 16 GB RAM to use for control plane
and compute nodes.
.. Select the base domain to deploy the cluster to. All DNS records will be
sub-domains of this base and will also include the cluster name.
Expand Down
2 changes: 1 addition & 1 deletion modules/installation-osp-about-kuryr.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Kuryr improves network performance by connecting Pods to the OpenStack SDN. It a

[IMPORTANT]
====
Kuryr is recommended for deployments on encapsulated {rh-openstack}-tenant networks to avoid double encapsulation. For example, on a deployment of an encapsulated OpenShift SDN over an {rh-openstack} network.
Kuryr is recommended for deployments on encapsulated {rh-openstack}-tenant networks to avoid double encapsulation. For example, on a deployment of an encapsulated OpenShift SDN over a {rh-openstack} network.

The default OpenShift SDN is recommended if:

Expand Down
2 changes: 1 addition & 1 deletion modules/installation-osp-balancing-external-loads.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ The load balancer serves ports 6443, 443, and 80 to any users of the system. Por

.Prerequisites

* Access to an {rh-openstack} administrator's account
* Access to a {rh-openstack} administrator's account
* The https://docs.openstack.org/python-openstackclient/latest/[{rh-openstack} client] installed on the target environment

.Procedure
Expand Down
2 changes: 1 addition & 1 deletion modules/installation-osp-enabling-swift.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ Swift is operated by a user account with the `swiftoperator` role and `temp-url`

.Prerequisites

* An {rh-openstack} administrator account on the target environment
* A {rh-openstack} administrator account on the target environment
* On Ceph RGW, https://docs.ceph.com/docs/master/radosgw/config-ref/#swift-settings[the `account in url` option must be enabled]

.Procedure
Expand Down