Merge "Clean up release notes for 6.2.0"6.2.0stable/newton

16 files changed, 39 insertions, 45 deletions

diff --git a/releasenotes/notes/add-notifications-97b6c79c18b48073.yaml b/releasenotes/notes/add-notifications-97b6c79c18b48073.yaml
index 6310b6f93..cd1582448 100644
--- a/releasenotes/notes/add-notifications-97b6c79c18b48073.yaml
+++ b/releasenotes/notes/add-notifications-97b6c79c18b48073.yaml
@@ -1,6 +1,8 @@
 ---
 features:
-  - Add support for inter-service notifications (disabled by default until the
+  - Adds support for inter-service notifications (disabled by default until the
     ``notification_level`` configuration option is set). For more information,
     see the notifications documentation in the developer's guide
     (http://docs.openstack.org/developer/ironic/dev/notifications.html).
+    Notifications are not actually emitted yet, but will be added in a future
+    release.
diff --git a/releasenotes/notes/add_infiniband_support-f497767f77277a1a.yaml b/releasenotes/notes/add_infiniband_support-f497767f77277a1a.yaml
index 10b369b67..6d52db598 100644
--- a/releasenotes/notes/add_infiniband_support-f497767f77277a1a.yaml
+++ b/releasenotes/notes/add_infiniband_support-f497767f77277a1a.yaml
@@ -1,4 +1,4 @@
 ---
 features:
-  - Add support for InfiniBand network to allow
-    Hardware inspection and PXE boot over InfiniBand.
+  - Adds support for InfiniBand networking to allow
+    hardware inspection and PXE boot over InfiniBand.
diff --git a/releasenotes/notes/add_standalone_ports_supported_field-4c59702a052acf38.yaml b/releasenotes/notes/add_standalone_ports_supported_field-4c59702a052acf38.yaml
index 79908fda3..d92b6d84c 100644
--- a/releasenotes/notes/add_standalone_ports_supported_field-4c59702a052acf38.yaml
+++ b/releasenotes/notes/add_standalone_ports_supported_field-4c59702a052acf38.yaml
@@ -3,4 +3,4 @@ features:
   - Add the field `standalone_ports_supported` to the
     portgroup object. This field indicates whether
     ports that are members of this portgroup can be
-    used as stand alone ports. By default is True.
+    used as stand-alone ports. The default is True.
diff --git a/releasenotes/notes/check-dynamic-allocation-enabled-e94f3b8963b114d0.yaml b/releasenotes/notes/check-dynamic-allocation-enabled-e94f3b8963b114d0.yaml
index 0ed4179e0..6befc37a6 100644
--- a/releasenotes/notes/check-dynamic-allocation-enabled-e94f3b8963b114d0.yaml
+++ b/releasenotes/notes/check-dynamic-allocation-enabled-e94f3b8963b114d0.yaml
@@ -1,5 +1,6 @@
 ---
 fixes:
-  - dynamic_allocation flag in node's driver_info can now accept all
-    the values that can be converted to booleans by bool_from_string
-    function from oslo_utils.
+  - The ``dynamic_allocation`` flag in a node's driver_info previously
+    only accepted a Boolean. It now also accepts the strings 't', 'true',
+    'on', 'y', 'yes', or '1' as True, and the strings 'f', 'false', 'off', 'n',
+    'no', or '0' as False. These are matched case-insensitively.
diff --git a/releasenotes/notes/deny-too-long-chassis-description-0690d6f67ed002d5.yaml b/releasenotes/notes/deny-too-long-chassis-description-0690d6f67ed002d5.yaml
index fcd2dbf54..e024588f5 100644
--- a/releasenotes/notes/deny-too-long-chassis-description-0690d6f67ed002d5.yaml
+++ b/releasenotes/notes/deny-too-long-chassis-description-0690d6f67ed002d5.yaml
@@ -1,4 +1,3 @@
 fixes:
-  - Deny too long description of chassis
-    (more than 255 chars) with appropriate
-    correct message.
+  - The API now returns an appropriate error message when a chassis
+    description over 255 characters is specified.
diff --git a/releasenotes/notes/deprecate-clustered-compute-manager-3dd68557446bcc5c.yaml b/releasenotes/notes/deprecate-clustered-compute-manager-3dd68557446bcc5c.yaml
index 539f91760..17353799d 100644
--- a/releasenotes/notes/deprecate-clustered-compute-manager-3dd68557446bcc5c.yaml
+++ b/releasenotes/notes/deprecate-clustered-compute-manager-3dd68557446bcc5c.yaml
@@ -1,12 +1,10 @@
 ---
 deprecations:
   - |
-    In Nova commit 6047d790a32ef5a65d4d6b029f673ce53c3d4141,
-    functionality is added to the ironic virt
-    driver to support multiple compute hosts without using the hack
-    we call ClusteredComputeManager.
+    The ClusteredComputeManager is now deprecated.
 
-    We anticipate this being included in the Newton release of Nova.
-    In advance of that, we are marking this unsupported component
-    as deprecated, and plan to remove it before the end of the Ocata
+    The Newton version of Nova adds functionality to the ironic virt driver to
+    support multiple compute hosts without using the hack we call
+    ClusteredComputeManager. As such, we are marking this unsupported
+    component as deprecated, and plan to remove it before the end of the Ocata
     development cycle.
diff --git a/releasenotes/notes/drac-raid-interface-f4c02b1c4fb37e2d.yaml b/releasenotes/notes/drac-raid-interface-f4c02b1c4fb37e2d.yaml
index 23b61768a..f2cc94632 100644
--- a/releasenotes/notes/drac-raid-interface-f4c02b1c4fb37e2d.yaml
+++ b/releasenotes/notes/drac-raid-interface-f4c02b1c4fb37e2d.yaml
@@ -3,9 +3,8 @@ features:
   - Adds out-of-band RAID management to DRAC driver using the generic RAID
     interface which makes the functionality available via manual cleaning
     steps.
-upgrade:
-  - New configuration option, ``[drac]query_raid_config_job_status_interval``
-    is added. After Ironic has created the RAID config job on the DRAC card,
+  - New configuration option, ``[drac]/query_raid_config_job_status_interval``
+    was added. After Ironic has created the RAID config job on the DRAC card,
     it continues to check for status update on the config job to determine
-    whether the RAID configuration was successfully finished at this interval.
-    Default is 120 seconds.
+    whether the RAID configuration was successfully finished within
+    this interval. Default is 120 seconds.
diff --git a/releasenotes/notes/erase-devices-metadata-config-f39b6ca415a87757.yaml b/releasenotes/notes/erase-devices-metadata-config-f39b6ca415a87757.yaml
index d063d1972..02fe04f32 100644
--- a/releasenotes/notes/erase-devices-metadata-config-f39b6ca415a87757.yaml
+++ b/releasenotes/notes/erase-devices-metadata-config-f39b6ca415a87757.yaml
@@ -1,7 +1,7 @@
 ---
 features:
   - Adds a new ``[deploy]/erase_devices_metadata_priority`` configuration
-    option to allow operators to configure the priority (or disable) of the
+    option to allow operators to configure the priority of (or disable) the
     "erase_devices_metadata" cleaning step.
 upgrade:
   - The new "erase_devices_metadata" cleaning step is enabled by
diff --git a/releasenotes/notes/fix-url-collisions-43abfc8364ca34e7.yaml b/releasenotes/notes/fix-url-collisions-43abfc8364ca34e7.yaml
index 8a4332cfb..0e52d8e7e 100644
--- a/releasenotes/notes/fix-url-collisions-43abfc8364ca34e7.yaml
+++ b/releasenotes/notes/fix-url-collisions-43abfc8364ca34e7.yaml
@@ -1,4 +1,4 @@
 ---
 fixes:
-  - Removed invalid accidental API URL v1/nodes/ports
-    See https://bugs.launchpad.net/ironic/+bug/1580997
+  - Removed invalid API URL ``/v1/nodes/ports``.
+    For more information, see https://bugs.launchpad.net/ironic/+bug/1580997.
diff --git a/releasenotes/notes/inspector-session-179f83cbb0dc169b.yaml b/releasenotes/notes/inspector-session-179f83cbb0dc169b.yaml
index 546e1be3e..f39d45ebf 100644
--- a/releasenotes/notes/inspector-session-179f83cbb0dc169b.yaml
+++ b/releasenotes/notes/inspector-session-179f83cbb0dc169b.yaml
@@ -1,6 +1,6 @@
 ---
 fixes:
-  - Ironic Inspector inspection interface will not fetch the service endpoint
+  - Ironic Inspector inspection interface will now fetch the service endpoint
     for the service catalog, if "service_url" is not provided and keystone
     support is enabled.
 upgrade:
diff --git a/releasenotes/notes/ipxe-use-swift-5ccf490daab809cc.yaml b/releasenotes/notes/ipxe-use-swift-5ccf490daab809cc.yaml
index dc6fe708d..81bd9947f 100644
--- a/releasenotes/notes/ipxe-use-swift-5ccf490daab809cc.yaml
+++ b/releasenotes/notes/ipxe-use-swift-5ccf490daab809cc.yaml
@@ -2,10 +2,10 @@
 features:
   - By default, the ironic-conductor service caches the node's deploy
     ramdisk and kernel images locally and serves them via a separate
-    HTTP server. A new ``[pxe]ipxe_use_swift`` configuration option
+    HTTP server. A new ``[pxe]/ipxe_use_swift`` configuration option
     (disabled by default) allows images to be accessed directly
     from object store via Swift temporary URLs.
-    This is only applicable if iPXE is enabled (via ``[pxe]ipxe_enabled``
+    This is only applicable if iPXE is enabled (via ``[pxe]/ipxe_enabled``
     configuration option) and image store is in Glance/Swift.
     For user images that are partition images requiring non-local boot,
     the default behavior with local caching and an HTTP server
diff --git a/releasenotes/notes/mask-configdrive-contents-77fc557d6bc63b2b.yaml b/releasenotes/notes/mask-configdrive-contents-77fc557d6bc63b2b.yaml
index beb768161..9446fea34 100644
--- a/releasenotes/notes/mask-configdrive-contents-77fc557d6bc63b2b.yaml
+++ b/releasenotes/notes/mask-configdrive-contents-77fc557d6bc63b2b.yaml
@@ -1,11 +1,11 @@
 ---
 features:
-  - This change adds a new policy rule that may be used to mask
+  - Adds a new policy rule that may be used to mask
     instance-specific secrets, such as configdrive contents or the temp URL
     used to store a configdrive or instance image.  This is similar to how
     passwords are already masked.
 upgrade:
-  - After this change, instance secrets will, by default, be masked in API
+  - Instance secrets will now, by default, be masked in API
     responses.  Operators wishing to expose the configdrive or instance image
     to specific users will need to update their policy.json file and grant the
     relevant keystone roles.
@@ -14,6 +14,6 @@ security:
     own images, which could also contain sensitive information.  The Agent
     drivers may store this information in a Swift temp URL to allow access from
     the Agent ramdisk. These URLs are considered sensitive information because
-    they grant unauthenticated access to sensitive information.  With this
-    change, we being to only selectively expose this information to privileged
+    they grant unauthenticated access to sensitive information.  Now,
+    we only selectively expose this information to privileged
     users, whereas previously it was exposed to all authenticated users.
diff --git a/releasenotes/notes/proliantutils_version_update-b6e5ff0e496215a5.yaml b/releasenotes/notes/proliantutils_version_update-b6e5ff0e496215a5.yaml
index ef7b42470..574cbb03f 100644
--- a/releasenotes/notes/proliantutils_version_update-b6e5ff0e496215a5.yaml
+++ b/releasenotes/notes/proliantutils_version_update-b6e5ff0e496215a5.yaml
@@ -1,6 +1,6 @@
 ---
 upgrade:
-  - Updated proliantutils required version number for iLO drivers
-    to 2.1.11. This version includes fixes for the bugs caused by
-    python request library version 2.11.0, Proliant Gen7 support
-    and iLO based RAID configuration.
+  - The minimum required version of proliantutils (needed for iLO
+    drivers) was bumped to 2.1.11. This version includes fixes for the bugs
+    caused by python request library version 2.11.0, Proliant Gen7 support and
+    iLO based RAID configuration.
diff --git a/releasenotes/notes/scciclient-0.4.0-6f01c0f0a5c39062.yaml b/releasenotes/notes/scciclient-0.4.0-6f01c0f0a5c39062.yaml
index ad6ac343f..6848910ec 100644
--- a/releasenotes/notes/scciclient-0.4.0-6f01c0f0a5c39062.yaml
+++ b/releasenotes/notes/scciclient-0.4.0-6f01c0f0a5c39062.yaml
@@ -1,4 +1,4 @@
 ---
 upgrade:
-  - Updated python-scciclient required version number for iRMC driver to
-    0.4.0 which contains the bug fix '#1561852' and miscellaneous improvement.
+  - The minimum required version of python-scciclient (needed for the iRMC
+    driver) was bumped to 0.4.0.
diff --git a/releasenotes/notes/update-live-port-ee3fa9b77f5d0cf7.yaml b/releasenotes/notes/update-live-port-ee3fa9b77f5d0cf7.yaml
index 7abd8c1c2..4eb0a8a7d 100644
--- a/releasenotes/notes/update-live-port-ee3fa9b77f5d0cf7.yaml
+++ b/releasenotes/notes/update-live-port-ee3fa9b77f5d0cf7.yaml
@@ -1,6 +1,6 @@
 ---
 fixes:
   - Fixed updating a MAC on a port for active instances in maintenance mode
-    (used to return HTTP 500 previously).
+    (previously returned HTTP 500).
   - Return HTTP 400 for requests to update a MAC on a port for an active
-    instance without maintenance mode set (used to return HTTP 500 previously).
+    instance without maintenance mode set (previously returned HTTP 500).
diff --git a/releasenotes/notes/update-proliant-required-version-71665e87bfad0a4d.yaml b/releasenotes/notes/update-proliant-required-version-71665e87bfad0a4d.yaml
deleted file mode 100644
index d30f82147..000000000
--- a/releasenotes/notes/update-proliant-required-version-71665e87bfad0a4d.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
----
-upgrade:
-  - Updated proliantutils required version number for iLO drivers
-    to 2.1.10 which fixes the defects of iLO based firmware upgrade
-    and iLO based RAID configuration.