Prepare release 16.1

Change-Id: Ia37075d4aa2f39ca0862b03ca02c85bac17400e5

ironic/common/release_mappings.py

@@ -265,6 +265,24 @@ RELEASE_MAPPING = {
             'VolumeTarget': ['1.0'],
         }
     },
+    '16.1': {
+        'api': '1.68',
+        'rpc': '1.51',
+        'objects': {
+            'Allocation': ['1.1'],
+            'Node': ['1.35'],
+            'Conductor': ['1.3'],
+            'Chassis': ['1.3'],
+            'Deployment': ['1.0'],
+            'DeployTemplate': ['1.1'],
+            'Port': ['1.9'],
+            'Portgroup': ['1.4'],
+            'Trait': ['1.0'],
+            'TraitList': ['1.0'],
+            'VolumeConnector': ['1.0'],
+            'VolumeTarget': ['1.0'],
+        }
+    },
     'master': {
         'api': '1.68',
         'rpc': '1.51',

releasenotes/notes/empty-physical-network-2248a4adef210289.yaml

@@ -1,5 +1,5 @@
 ---
 fixes:
   - |
-    fixes an issue that physical_network could be set to an empty string,
-    which makes the port unusable.
+    It is no longer possible to set a port's ``physical_network`` to an empty
+    string, making the port unusable.

releasenotes/notes/fix-inspection-for-idrac-34b3ea09452af8be.yaml

@@ -1,4 +1,4 @@
 ---
 fixes:
   - |
-    Fix an issue when using idrac with vmedia and trying to inspect a node.
+    Fixes inspection with the ``idrac-redfish-virtual-media`` boot interface.

releasenotes/notes/ipmi_command_retry_timeout-889a49b402e82b97.yaml

@@ -1,9 +1,10 @@
 ---
 fixes:
   - |
-    Calculating the ipmitool `-N` and `-R` arguments from ironic.conf [ipmi]
-    `command_retry_timeout` and `min_command_interval` now takes into account the
-    1 second interval increment that ipmitool adds on each retry event.
+    Calculating the ipmitool ``-N`` and ``-R`` arguments from the configuration
+    options ``[ipmi]command_retry_timeout`` and ``[ipmi]min_command_interval``
+    now takes into account the 1 second interval increment that ipmitool adds
+    on each retry event.
 
     Failure-path ipmitool run duration will now be just less than
-    `command_retry_timeout` instead of much longer.
+    ``command_retry_timeout`` instead of much longer.

releasenotes/notes/json-rpc-ipv6-host-30eca350f34bc091.yaml

@@ -1,6 +1,6 @@
 ---
 fixes:
   - |
-    When configured to use json-rpc, the ``[DEFAULT].host`` configuration
-    option to ironic-conductor can now be set to an IPv6 address. Previously
-    it could only be an IPv4 address or a DNS name.
+    When configured to use JSON RPC, the ``[DEFAULT]host`` configuration
+    option can now be set to an IPv6 address. Previously it could only be
+    an IPv4 address or a DNS name.

releasenotes/notes/optimize-ramdisk-log-filename-270c401780b16e9c.yaml

@@ -1,4 +1,4 @@
 ---
 features:
   - |
-    The ramdisk log filename will contain the node name when it exists.
+    The ramdisk log file name now contains the node name when it is set.

releasenotes/notes/raid-remove-root-hint-ec87efd18e894256.yaml

@@ -1,10 +1,10 @@
 ---
 upgrade:
   - |
-    Agent raid will remove the root device hint after the RAID configuration
-    is successfully deleted.
+    The ``agent`` RAID interface now removes any root device hint after
+    the RAID configuration is successfully deleted.
 fixes:
   - |
-    Fixes the issue that root device hint is not removed after agent raid
-    interface has successfully deleted RAID configuration, the previous hint
-    is not guranteed to be valid thus will cause a deployment failed.
+    Fixes the issue that root device hint is not removed after the ``agent``
+    RAID interface has successfully deleted RAID configuration. The previous
+    hint is not guranteed to be valid and may cause a deployment failure.

releasenotes/notes/sync-boot-mode-after-changing-redfish-device-f60ef90ba5675215.yaml

@@ -1,8 +1,8 @@
 ---
 fixes:
   - |
-    After changing the boot device via Redfish, check that the boot mode being
-    reported matches what is configured and, if not, set it to the configured
-    value.  Some BMCs change the boot mode when the device is
+    After changing the boot device via Redfish, checks that the boot mode being
+    reported matches what is configured and, if not, sets it to the configured
+    value. Some BMCs change the boot mode when the device is
     set via Redfish, see `story 2008252
-    <https://storyboard.openstack.org/#!/story/2008252>`__ for details.
+    <https://storyboard.openstack.org/#!/story/2008252>`_ for details.