Merge pull request #9675 from tmorriso-rh/BZ1583143

BZ 1583143 - Add info on configuring zone labels

Author: Traci Morrison

install_config/configuring_openstack.adoc

@@ -12,21 +12,15 @@ toc::[]
 
 == Overview
 When deployed on link:https://www.openstack.org/[OpenStack], {product-title} can
-be configured to access OpenStack infrastructure, including
+be configured to access the OpenStack infrastructure, including
 xref:../install_config/persistent_storage/persistent_storage_cinder.adoc#install-config-persistent-storage-persistent-storage-cinder[using OpenStack Cinder volumes as persistent storage] for application data.
 
 [[configuring-openstack-permissions]]
 == Permissions
 Configuring OpenStack for {product-title} requires the following role:
 
-[cols='1,3']
-|===
-
-| member
-| For creating assets(instances, networking ports, floating ips, volumes, and so
-on.) you need the member role for the tenant.
-
-|===
+Member:: For creating assets such as instances, networking ports, floating IPs, volumes, and so
+on. You need the member role for the tenant.
 
 [[configuring-a-security-group-openstack]]
 == Configuring a Security Group
@@ -40,7 +34,6 @@ To set the required OpenStack variables, create a *_/etc/cloud.conf_* file with
 the following contents on all of your {product-title} hosts, both masters and
 nodes:
 
-====
 ----
 [Global]
 auth-url = <OS_AUTH_URL>
@@ -53,7 +46,6 @@ region = <OS_REGION_NAME>
 [LoadBalancer]
 subnet-id = <UUID of the load balancer subnet>
 ----
-====
 
 Consult your OpenStack administrators for values of the `*OS_*` variables, which
 are commonly used in OpenStack configuration.
@@ -86,7 +78,7 @@ xref:../install_config/install/advanced_install.adoc#advanced-install-configurin
 - `*openshift_cloudprovider_openstack_lb_subnet_id*`
 
 .Example OpenStack Configuration with Ansible
-====
+
 ----
 # Cloud Provider Configuration
 #
@@ -108,7 +100,6 @@ xref:../install_config/install/advanced_install.adoc#advanced-install-configurin
 #openshift_cloudprovider_openstack_region=region
 #openshift_cloudprovider_openstack_lb_subnet_id=subnet_id
 ----
-====
 
 [[openstack-configuring-masters-manually]]
 === Manually Configuring {product-title} Masters for OpenStack
@@ -119,7 +110,6 @@ master configuration file on all masters
 (*_/etc/origin/master/master-config.yaml_* by default) and update the
 contents of the `*apiServerArguments*` and `*controllerArguments*` sections:
 
-====
 [source,yaml]
 ----
 kubernetesMasterConfig:
@@ -135,7 +125,6 @@ kubernetesMasterConfig:
     cloud-config:
       - "/etc/cloud.conf"
 ----
-====
 
 [IMPORTANT]
 ====
@@ -154,7 +143,6 @@ the node configuration file on all nodes (*_/etc/origin/node/node-config.yaml_*
 by default) and update the contents of the `*kubeletArguments*` and `*nodeName*`
 sections:
 
-====
 [source,yaml]
 ----
 nodeName:
@@ -166,12 +154,13 @@ kubeletArguments:
   cloud-config:
     - "/etc/cloud.conf"
 ----
-<1> Name of the OpenStack instance where the node runs (i.e., name of the virtual machine)
-====
+<1> The RFC1123-compliant OpenStack instance name of the node host.
 
-Currently, the `nodeName` *must* match the instance name in Openstack in order
-for the cloud provider integration to work properly.  The name must also be
-RFC1123 compliant.
+[NOTE]
+====
+If the `nodeName` does not match the OpenStack instance name, the cloud provider
+integration will not work.
+====
 
 [IMPORTANT]
 ====
@@ -184,3 +173,31 @@ container. Therefore, *_cloud.conf_* should be in *_/etc/origin/_* instead of
 [[openstack-applying-configuration-changes]]
 == Applying Configuration Changes
 include::install_config/topics/applying_configuration_changes.adoc[]
+
+[[openstack-configuring-zone-labels]]
+=== Configuring Zone Labels for Dynamically Created OpenStack PVs 
+
+Administrators can configure zone labels for dynamically
+created OpenStack PVs. This option is useful if the OpenStack Cinder zone name
+does not match the compute zone names, for example, if there is only one Cinder
+zone and many compute zones. Administrators can create Cinder volumes
+dynamically and then check the labels.
+
+To view the zone labels for the PVs:
+
+----
+# oc get pv --show-labels
+NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS    CLAIM                 STORAGECLASS   REASON    AGE       LABELS
+pvc-1faa6f93-64ac-11e8-930c-fa163e3c373c   1Gi        RWO            Delete           Bound     openshift-node/pvc1   standard                 12s       failure-domain.beta.kubernetes.io/zone=nova
+----
+
+The default setting is enabled. Using the `oc get pv --show-labels` command returns the `failure-domain.beta.kubernetes.io/zone=nova` label.
+
+To disable the zone label, update the cloud.conf file by adding:
+
+----
+[BlockStorage]
+ignore-volume-az = yes
+----
+
+The PVs created after restarting the master services will not have the zone label.