Merge "Tidy up release notes for Ussuri"

releasenotes/notes/add-mechanism-for-prometheus-customization-0b173ff7c63ca30f.yaml

 ---
 features:
   - |
-    Added a mechanism to customize ``prometheus.yml``. Please read the the
-    `documentation <https://docs.openstack.org/kolla-ansible/latest/reference/logging-and-monitoring/prometheus-guide.html>`__.
+    Adds a mechanism to customize ``prometheus.yml``. Please read the the
+    `documentation
+    <https://docs.openstack.org/kolla-ansible/latest/reference/logging-and-monitoring/prometheus-guide.html>`__.
     for more details.

releasenotes/notes/allow-custom-ceilometer-upgrade-params-c07eec4c1ef5a3d3.yaml

@@ -4,9 +4,8 @@ features:
     Allow operators to use custom parameters with the ceilometer-upgrade
     command. This is quite useful when using the dynamic pollster subsystem;
     that sub-system provides flexibility to create and edit pollsters configs,
-    which affects gnocchi resource-type configurations. However, Ceilometer
+    which affects Gnocchi resource-type configurations. However, Ceilometer
     uses default and hard-coded resource-type configurations; if one customizes
     some of its default resource-types, he/she can get into trouble during
     upgrades. Therefore, the only way to work around it is to use the
-    "--skip-gnocchi-resource-types" flag. This release introduces a method for
-    operators to execute such customization, and many others if needed.
+    ``--skip-gnocchi-resource-types`` flag.

releasenotes/notes/ansible-max-version-support-d74258eec27d3549.yaml

 ---
 upgrade:
   - |
-    Adds maximum supported version check for Ansible. Kolla Ansible now
+    Adds a maximum supported version check for Ansible. Kolla Ansible now
     requires at least Ansible ``2.8`` and supports up to ``2.9``. See
     `blueprint
     <https://blueprints.launchpad.net/kolla-ansible/+spec/ansible-max-version>`__

releasenotes/notes/bug-1846789-fix-fernet-bootstrap-36f87e36e4dc6ec9.yaml

 ---
 fixes:
   - |
-    Rework keystone fernet bootstrap which had tendencies to fail on multinode
+    Reworks Keystone fernet bootstrap which had tendencies to fail on multinode
     setups. See `bug 1846789 <https://launchpad.net/bugs/1846789>`__ for
     details.

releasenotes/notes/bug-1858773-manila-cephfs-driver-f6a75bd15c002363.yaml

 ---
 fixes:
   - |
-    Change Manila cephfs share driver to
-    ``manila.share.drivers.cephfs.driver.CephFSDriver``, old driver was
+    Changes Manila cephfs share driver to
+    ``manila.share.drivers.cephfs.driver.CephFSDriver``, as the old driver was
     deprecated.

releasenotes/notes/ceph-keys-vars-6857d19d291c401d.yaml

 ---
 features:
   - |
-    Introduce user modifiable variables instead of fixed names for Ceph
+    Introduces user modifiable variables instead of fixed names for Ceph
     keyring files used by external Ceph functionality.
 upgrade:
   - |
-    For cinder (cinder-volume and cinder-backup), glance-api and manila
-    keyrings behavior has changed and kolla-ansible deployment will not copy
-    those keys using wildcards (ceph.*), instead will use newly introduced
-    variables. Your environment may render unusable after an upgrade if your
-    keys in /etc/kolla/config do not match default values for introduced
-    variables.
+    For cinder (``cinder-volume`` and ``cinder-backup``), ``glance-api`` and
+    ``manila`` keyrings behavior has changed and Kolla Ansible deployment will
+    not copy those keys using wildcards (``ceph.*``), instead will use newly
+    introduced variables. Your environment may render unusable after an upgrade
+    if your keys in ``/etc/kolla/config`` do not match default values for
+    introduced variables.

releasenotes/notes/configure-certificate-authority-aa21fa88234b021e.yaml

 ---
 features:
-  - Configure all openstack services to use the globally defined Certificate
-    Authority to verify HTTPs connections. The global CA is configured by the
-    'openstack_cacert' parameter.
+  - Configures all openstack services to use the globally defined Certificate
+    Authority file to verify HTTPS connections. The global CA file is
+    configured by the ``openstack_cacert`` parameter.

releasenotes/notes/copy-certificate-authority-into-containers-860cbda3384dd731.yaml

 ---
 features:
   - |
-    When 'kolla_copy_ca_into_containers' is configured to 'yes', the
-    certificate authority files in /etc/kolla/certificates/ca will be copied
-    into service containers to enable trust for those CA certificates. This
-    is required for any certificates that are either self-signed or signed by
-    a private CA, and are not already present in the service image trust store.
-    Otherwise, either CA validation will need to be explicitly disabled or the
-    path to the CA certificate must be configured in the service using
+    When ``kolla_copy_ca_into_containers`` is configured to ``yes``, the
+    certificate authority files in ``/etc/kolla/certificates/ca`` will be
+    copied into service containers to enable trust for those CA certificates.
+    This is required for any certificates that are either self-signed or signed
+    by a private CA, and are not already present in the service image trust
+    store.  Otherwise, either CA validation will need to be explicitly disabled
+    or the path to the CA certificate must be configured in the service using
     the ``openstack_cacert`` parameter.
 
 issues:

releasenotes/notes/docker-image-pruning-fffcffa7e99c6e63.yaml

 ---
 features:
   - |
-    Adds command ``prune-images`` for Docker image pruning on hosts. See
+    Adds a ``prune-images`` command for Docker image pruning on hosts. See
     `blueprint
     <https://blueprints.launchpad.net/kolla-ansible/+spec/docker-image-pruning>`__
     for details.

releasenotes/notes/drop-py27-509835da35f047b4.yaml

 ---
 upgrade:
   - |
-    Python 2.7 support has been dropped. Last release of kolla-ansible to
+    Python 2.7 support has been dropped. The last release of Kolla Ansible to
     support Python 2.7 is OpenStack Train. The minimum version of Python now
-    supported by kolla-ansible is Python 3.6.
+    supported by Kolla Ansible is Python 3.6.

releasenotes/notes/encrypt-backend-haproxy-fb96285d74fb464c.yaml

 ---
 features:
   - |
-    Added configuration options to enable backend TLS encryption from HAProxy
+    Adds configuration options to enable backend TLS encryption from HAProxy
     to the Keystone, Glance, Heat, Placement, Horizon, Barbican, and Cinder
     services. When used in conjunction with enabling TLS for service API
     endpoints, network communcation will be encrypted end to end, from client

releasenotes/notes/execute-rest-methods-inside-containers-ce2a1410dbdc71f3.yaml

 ---
 features:
   - |
-    Delegate executing ansible uri REST methods to service containers using
-    kolla_toolbox. This will enable any certificates that are already copied
-    and extracted into the service container to be automatically validated.
-    This is particularly useful in the case that the certificate is either
-    self-signed or signed by a local (private) CA.
+    Delegates execution of the Ansible ``uri`` module to service containers
+    using ``kolla_toolbox``. This will enable any certificates that are already
+    copied and extracted into the service container to be automatically
+    validated.  This is particularly useful in the case that the certificate is
+    either self-signed or signed by a local (private) CA.

releasenotes/notes/external-ceph-cinder-template-40dc0bc07e717837.yaml

 ---
 upgrade:
   - |
-    Default behavior for generating cinder.conf template has changed,
-    now cinder.conf with rbd-1 section will be generated when external Ceph
-    functionality is used i.e. cinder_backend_ceph is set to true.
-    Previously it was only included when Kolla-Ansible internal
-    Ceph deployment mechanism was used.
+    The default behavior for generating the ``cinder.conf`` template has
+    changed.  An ``rbd-1`` section will be generated when external Ceph
+    functionality is used, i.e. ``cinder_backend_ceph`` is set to ``true``.
+    Previously it was only included when Kolla Ansible internal Ceph
+    deployment mechanism was used.

releasenotes/notes/external-ceph-users-2715eebf8a8df1af.yaml

 ---
 features:
   - |
-    Introduce External Ceph user ids as variables to allow non-standard ceph
-    authentication ids in OpenStack services configuration without the need to
+    Introduce External Ceph user IDs as variables to allow non-standard Ceph
+    authentication IDs in OpenStack service configuration without the need to
     override configuration files.
 upgrade:
   - |
-    Now the rbd part of ``nova.conf`` in ``nova-compute`` is being generated
-    when ``nova_backend`` is set to ``"rbd"`` (previously it was generated when
-    both ``enable_ceph`` was ``"yes"`` and ``nova_backend`` was set to
-    ``"rbd"``).
+    The ``rbd`` section of ``nova.conf`` for ``nova-compute`` is now generated
+    when ``nova_backend`` is set to ``"rbd"``. Previously it was only generated
+    when both ``enable_ceph`` was ``"yes"`` and ``nova_backend`` was set to
+    ``"rbd"``.

releasenotes/notes/feature-mergepwd-clean-18cbed4d39967e70.yaml

 ---
 features:
   - |
-    Adds ``--clean`` argument to ``kolla-mergepwd``. It allows to clean old
-    (not used anymore) keys from the passwords file.
+    Adds a ``--clean`` argument to ``kolla-mergepwd``. It allows to clean old
+    (no longer used) keys from the passwords file.

releasenotes/notes/fix-issue-with-elasticsearch-kolla-logs-a0ba85d91d1a2c31.yaml

 ---
 fixes:
   - |
-    The kolla_logs Docker volume is now mounted into the Elasticsearch
+    The ``kolla_logs`` Docker volume is now mounted into the Elasticsearch
     container to expose logs which were previously written erroneously
-    to the container filesystem (bug 1859162). It is up to the user to
+    to the container filesystem.  `LP#1859162
+    <https://bugs.launchpad.net/kolla-ansible/+bug/1859162>`__
+upgrade:
+  - |
+    The ``kolla_logs`` Docker volume is now mounted into the Elasticsearch
+    container to expose logs which were previously written erroneously
+    to the container filesystem. It is up to the user to
     migrate any existing logs if they so desire and this should be
-    done before applying this fix.
+    done before applying this fix. `LP#1859162
+    <https://bugs.launchpad.net/kolla-ansible/+bug/1859162>`__

releasenotes/notes/fix-octavia-cert-config-28f0ef2799406957.yaml

 ---
 fixes:
   - |
-    Adapt Octavia to the latest dual CA certificate configuration. The
+    Adapts Octavia to the latest dual CA certificate configuration. The
     following files should exist in ``/etc/kolla/config/octavia/``:
 
     * ``client.cert-and-key.pem``

releasenotes/notes/generate-internal-external-self-signed-certs-c631a9d934d31fac.yaml

 ---
 features:
   - |
-    Generate self signed certificates for both the internal and external
-    (public) networks. If they are the same network, then the certificate
-    files will be the same.
+    Adds support for generating self-signed certificates for both the internal
+    and external (public) networks via the ``kolla-ansible certificates``
+    command. If they are the same network, then the certificate files will be
+    the same.
 upgrade:
   - |
     The default value for ``kolla_external_fqdn_cacert`` has been changed

releasenotes/notes/horizon_keystone_dropdown-6b9b4e5e9a64f979.yaml

 ---
 features:
   - |
-    Added ``horizon_keystone_domain_choices`` hash. It can be used to set the
-    available domains to choose from on the horizon login page. This feature
-    was introduced in Pike release.
-    Please see `<https://docs.openstack.org/horizon/latest/configuration/settings.html#openstack-keystone-domain-choices>`__
+    Adds support for configuring the available domains to choose from on the
+    horizon login page via ``horizon_keystone_domain_choices`` hash.  This
+    feature was introduced in Pike release.  Please see
+    `<https://docs.openstack.org/horizon/latest/configuration/settings.html#openstack-keystone-domain-choices>`__

releasenotes/notes/implement-ovn-80b3a73e6c8a44e7.yaml

 ---
 features:
   - |
-    Implement OVN and its integration with Neutron. This includes deployment
-    of:
+    Adds support for deployment of OVN and integration of it with Neutron. This
+    includes deployment of:
 
     * OVN databases (``ovn-sb-db`` and ``ovn-nb-db``)
     * Southbound and Northbound databases connector (``ovn-northd``)