Merge "Revise release notes for release"

releasenotes/notes/deploy-with-selinux-enabled-6c155cfa8f8720c0.yaml

@@ -1,9 +1,7 @@
 ---
 features:
-  - Currently bifrost deployments on RedHat/Suse systems
+  - Previously bifrost deployments on RedHat/Suse systems
     had to be performed with selinux at least in
-    permissive mode. This patch adds the right policies
+    permissive mode. This patch adds the necessary policies
-    to allow to run with selinux in enforcing mode.
+    to allow the components to operate with selinux in
-security:
+    enforcing mode.
-  - This increases security, because allows to run
-    on systems with selinux in enforcing mode.

releasenotes/notes/drop-amt-e4bfb6e2ae3c4301.yaml

@@ -1,6 +1,6 @@
 ---
 upgrade:
   - |
-    bifrost no longer supports installing ironic AMT drivers when PXE drivers
+    Bifrost no longer supports installing ironic AMT drivers when PXE drivers
-    are enabled (which is the default) due to AMT drivers have been removed
+    are enabled (which is the default) due to AMT drivers having been removed
     from ironic in Ocata release.

releasenotes/notes/enable_inspector_by_default-828fc1284d6a7c2b.yaml

@@ -1,6 +1,5 @@
 ---
-prelude: >
-    Inspector now installed and enabled by default.
 features:
-  - Changes default value for enable_inspector variable
+  - Inspector is now installed and enabled by default.
-    from false to true.
+    This changes default value for the ``enable_inspector``
+    variable from ``false`` to ``true``.

releasenotes/notes/more-clouds-7c0fccf5701918d7.yaml

@@ -1,21 +1,24 @@
 ---
 features:
   - |
-    'bifrost-keystone-client-config' role can now write 'clouds.yaml' file
+    The ``bifrost-keystone-client-config`` role can now write a
-    with several clouds settings. It starts to accept a single compound
+    ``clouds.yaml`` file with several clouds settings. It starts to
-    variable 'clouds' that should contain a dict of
+    accept a single compound variable ``clouds`` that must contain a
-    '<cloud-name>:<dict-of-cloud-settings>'.
+    dictionary describing key:value pairs in the format of
-    Previous way of passing 'config_*' vars to the role is supported for
+    ``<cloud-name>:<dict-of-cloud-settings>``.
-    backward compatibility but is deprecated.
+    The previous way of passing ``config_*`` vars to the role is supported for
+    backward compatibility but is deprecated and should be expected to be
+    removed in Pike.
 
-    In addition to previous 'bifrost' cloud, the default 'install.yaml'
+    In addition to previous ``bifrost`` cloud, the default ``install.yaml``
-    playbook now also writes 'bifrost-admin' cloud settings that contain
+    playbook now also writes ``bifrost-admin`` cloud settings that contain
     Keystone admin credentials so that when installed, the Keystone service
     is fully usable right away (users/projects etc can be managed).
 
 deprecations:
   - |
-    Passing 'config_*' variables defining credentials for 'bifrost'
+    Passing ``config_*`` variables defining credentials for ``bifrost``
-    cloud to 'bifrost-keystone-client-config' role is deprecated.
+    cloud to the ``bifrost-keystone-client-config`` role has been deprecated,
-    Instead a single compound variable named 'clouds' defining sets of
+    and will be removed in the Pike cycle.
-    settings to be written to 'clouds.yaml' should be passed to that role.
+    Instead a single compound variable named ``clouds`` defining sets of
+    settings to be written to ``clouds.yaml`` should be passed to that role.

releasenotes/notes/ocata-summary-040e557460bab2bc.yaml

@@ -0,0 +1,18 @@
+---
+prelude: >
+    During the Ocata cycle, a number of improvements have been made to bifrost
+    to improve the managability and longevity of a bifrost installation.
+    Coupled with a number of fixes, and improvements, users upgrading should
+    take the time to read the entire release notes. A few highlights are below:
+
+        * Bifrost now installs and utilizes Ansible 2.1 by default.
+        * Ironic's default of modifying a pre-existing ironic.conf upon the
+          installation being re-executed, has been changed to a utilize a
+          template file.
+        * Bifrost supports generating and reading from a os-client-config
+          ``clouds.yaml`` file for obtaining credentials.
+        * Bifrost can now leverage authentiation, as well as install and
+          configure keystone if requested by the installer.
+        * As a number of in-tree drivers in ironic were removed this past
+          cycle, due to lack of third-party CI, support has been added to
+          enable installation of the staging drivers repository.

releasenotes/notes/templated_ironic_conf-bd052f2b2897d37a.yaml

@@ -1,11 +1,7 @@
 ---
-prelude: >
-    Ironic.conf is templated and only sets required
-    options now, as opposed to editing the Sample
-    configuration of Ironic.
 features:
   - Ironic.conf is templated and only sets required
-    options now, as opposed to editing the Sample
+    options now, as opposed to editing the sample
     configuration of Ironic.
 other:
   - In the past, the sample config in Ironic may have