Browse Source

Release notes cleanup for 13.0.0

Change-Id: I0a2c5345b7f72014528a73ece68f442745f64302
changes/85/679985/2
Dmitry Tantsur 2 weeks ago
parent
commit
68e6daf717

+ 0
- 6
releasenotes/notes/adds-ilo-ipxe-boot-interface-4fc75292122db80d.yaml View File

@@ -11,9 +11,3 @@ features:
11 11
       configuration
12 12
       <https://docs.openstack.org/ironic/latest/install/configure-pxe.html>`_
13 13
     * Create/Set baremetal node with ``--boot-interface ilo-ipxe``
14
-fixes:
15
-  - |
16
-    From Stein release, ``[pxe]ipxe_enabled`` option has been deprecated.
17
-    The ``ilo`` hardware type supports iPXE boot through
18
-    ``[pxe]ipxe_enabled`` option. To cope with this incompatibility,
19
-    ``ilo`` hardware type has added new ``ilo-ipxe`` boot interface.

+ 2
- 2
releasenotes/notes/allow-deleting-unbound-ports-fa78069b52f099ac.yaml View File

@@ -1,5 +1,5 @@
1 1
 ---
2 2
 fixes:
3 3
   - |
4
-    Allows deleting unbound ports on an active node. See
5
-    https://storyboard.openstack.org/#!/story/2006385 for details.
4
+    Allows deleting unbound ports on an active node. See `story 2006385
5
+    <https://storyboard.openstack.org/#!/story/2006385>`_ for details.

+ 22
- 22
releasenotes/notes/bp-nova-support-instance-power-update-49c531ef13982e62.yaml View File

@@ -2,33 +2,33 @@
2 2
 features:
3 3
   - |
4 4
     Adds power state change callbacks of an instance to the Compute service by
5
-    performing API notifications. This is configurable through the
6
-    ``nova.send_power_notifications`` config option. Whenever there is a change
7
-    in the power state of a physical instance (for example a "power on" or
8
-    "power off" API command is issued or during the periodic power state
9
-    synchronization between nova and ironic) the Baremetal service will create
10
-    and send a ``power-update`` external event to the Compute service which will
11
-    cause the power state of the instance to be updated in its database. It
12
-    also adds the possibility of bringing up/down a physical instance through
13
-    the Baremetal service API even if it was put down/up through the Compute
14
-    service API.
5
+    performing API notifications. This feature is enabled by default and can be
6
+    disabled via the new ``[nova]send_power_notifications`` configuration
7
+    option.
8
+
9
+    Whenever there is a change in the power state of a physical instance,
10
+    the Bare Metal service will send a ``power-update`` external event to
11
+    the Compute service which will cause the power state of the instance
12
+    to be updated in the Compute database. It also adds the possibility of
13
+    bringing up/down a physical instance through the Bare Metal service API
14
+    even if it was put down/up through the Compute service API.
15 15
 fixes:
16 16
   - |
17
-    By immediately conveying all the power state changes (note that the
18
-    Baremetal service only sends requests to the Compute service if the target
19
-    power state is either "power on" or "power off") of an instance through
20
-    external events to the Compute service, the Baremetal service becomes the
21
-    source of truth thus preventing the Compute service from forcing wrong
22
-    power states on the instance during the periodic power state
23
-    synchronization between nova and ironic. An exception would be if a race
24
-    condition were to occur due to the nova-ironic power sync task happening
25
-    a nano-second before the power state change event is received from the
26
-    Baremetal service in which case the nova instance state will be forced
27
-    on the baremetal node.
17
+    By immediately conveying power state changes of a node through
18
+    external events to the Compute service, the Bare Metal service becomes the
19
+    source of truth about the node's power state, preventing the Compute
20
+    service from forcing wrong power states on instances during the periodic
21
+    power state synchronization between the Compute and Bare Metal services.
22
+
23
+    .. note::
24
+        There is a possibility of a race condition due to the nova-ironic power
25
+        sync task happening during or right before the power state change
26
+        event is received from the Bare Metal service, in which case the
27
+        instance state will be forced on the baremetal node.
28 28
 upgrade:
29 29
   - |
30 30
     In order to support power state change call backs to nova, the ``[nova]``
31
-    section must be configured in the baremetal service configuration.
31
+    section must be configured in the Bare Metal service configuration.
32 32
     As the functionality to process the event is new to nova's Train release,
33 33
     this should only be set to ``True`` in ironic, once *ALL* ``nova-compute``
34 34
     instances have been upgraded to the Train release of nova.

+ 2
- 3
releasenotes/notes/bug-2006266-85da234583ca0c32.yaml View File

@@ -1,6 +1,5 @@
1 1
 ---
2 2
 fixes:
3 3
   - |
4
-      An issue regarding the ``ansible`` deploy interface. The discovery
5
-      playbook used to gather wwn and serials was broken for python3 due to the
6
-      dict().keys() object not being a list in python3.
4
+    Fixes an issue in the discovery playbook for the ``ansible`` deploy
5
+    interface that prevented gathering WWN and serial numbers under Python 3.

+ 2
- 5
releasenotes/notes/bug-35702-25da234580ca0c31.yaml View File

@@ -1,7 +1,4 @@
1 1
 ---
2 2
 fixes:
3
-      - |
4
-          Fixes an issue regarding the ``ansible`` deploy interface. Node
5
-          deployment was broken for any image that was not public because
6
-          the original request context was not available anymore at the time
7
-          some image information was fetched.
3
+  - |
4
+    Fixes deploying non-public images using the ``ansible`` deploy interface.

+ 8
- 8
releasenotes/notes/drac-fix-power-on-reboot-race-condition-fe712aa9c79ee252.yaml View File

@@ -1,16 +1,16 @@
1 1
 ---
2 2
 features:
3 3
   - |
4
-    Adds a new configuration option ``boot_device_job_status_timeout`` that
5
-    specifies the Maximum amount of time (in seconds) to wait for the boot
4
+    Adds a new configuration option ``[drac]boot_device_job_status_timeout``
5
+    that specifies the maximum amount of time (in seconds) to wait for the boot
6 6
     device configuration job to transition to the scheduled state to allow a
7 7
     reboot or power on action to complete.
8 8
 fixes:
9 9
   - |
10
-    Fixes an issue where a configuration job does not transition to the
11
-    correct state and start execution during a power on or reboot operation. If
12
-    the boot device is being changed, the system might complete its POST before
13
-    the job is ready, leaving the job in the queue, and the system will boot
14
-    from the wrong device.
10
+    Fixes an issue in the ``idrac`` hardware type where a configuration job
11
+    does not transition to the correct state and start execution during
12
+    a power on or reboot operation. If the boot device is being changed,
13
+    the system might complete its POST before the job is ready, leaving
14
+    the job in the queue, and the system will boot from the wrong device.
15 15
     See bug `2004909 <https://storyboard.openstack.org/#!/story/2004909>`_ for
16
-    details.
16
+    details.

+ 6
- 5
releasenotes/notes/intel-ipmi-hardware-30aaa65cdbcb779a.yaml View File

@@ -1,9 +1,10 @@
1 1
 ---
2 2
 features:
3 3
   - |
4
-    Adds support for the Intel IPMI Hardware with hardware type
5
-    ``intel-ipmitool``. This hardware type is same as ``ipmi`` hardware type
6
-    with additional support of `Intel Speed Select Performance Profile
7
-    Technology <https://www.intel.com/content/www/us/en/architecture-and-technology/speed-select-technology-article.html>`.
8
-    It uses management interface ``intel-ipmitool``. It supports setting
4
+    Adds support for the Intel IPMI Hardware with a new hardware type
5
+    ``intel-ipmitool``. This hardware type is the same as the ``ipmi`` hardware
6
+    type with additional support of `Intel Speed Select Performance Profile
7
+    Technology
8
+    <https://www.intel.com/content/www/us/en/architecture-and-technology/speed-select-technology-article.html>`_.
9
+    It uses the ``intel-ipmitool`` management interface, which supports setting
9 10
     the desired configuration level for Intel SST-PP.

+ 5
- 12
releasenotes/notes/irmc-dealing-with-ipxe-boot-interface-incompatibility-7d0b2bdb8f9deb46.yaml View File

@@ -1,17 +1,10 @@
1 1
 ---
2 2
 upgrade:
3 3
   - |
4
-    iRMC hardware type deals with iPXE boot interface incompatibility.
5
-    To iPXE boot with ``ipxe`` boot interface, *(1)* add ``ipxe`` to
6
-    ``enabled_boot_interfaces`` in ``ironic.conf``, *(2)* set up tftp &
7
-    http server following `Ironic document on iPXE boot configuration
8
-    <https://docs.openstack.org/ironic/latest/install/configure-pxe.html>`,
9
-    then *(3)* create/set baremetal node with ``--boot-interface ipxe``.
4
+    Users of the ``irmc`` hardware type with iPXE should switch to the ``ipxe``
5
+    boot interface from the deprecated ``[pxe]ipxe_enabled`` option.
10 6
 fixes:
11 7
   - |
12
-    iRMC hardware type deals with iPXE boot interface incompatibility.
13
-    From Stein, ``[pxe]ipxe_enabled`` option has been deprecated and will be
14
-    removed in preference to ``ipxe`` boot interface in Train cycle. Till then,
15
-    iRMC hardware type supports iPXE boot through ``[pxe]ipxe_enabled`` option.
16
-    To cope with this incompatibility, iRMC hardware type supports ``ipxe``
17
-    boot interface.
8
+    Adds the missing ``ipxe`` boot interface to the ``irmc`` hardware type.
9
+    It is supposed to be used instead of the deprecated ``[pxe]ipxe_enabled``
10
+    configuration option.

+ 2
- 2
releasenotes/notes/remove-app-wsgi-d5887ca28e4b9f00.yaml View File

@@ -1,5 +1,5 @@
1 1
 ---
2 2
 upgrade:
3
-  - remove deprecated ``ironic/api/app.wsgi`` script.
4
-    The automatically generated ``ironic-api-wsgi`` script should be used
3
+  - The deprecated ``ironic/api/app.wsgi`` script has been removed.
4
+    The automatically generated ``ironic-api-wsgi`` script must be used
5 5
     instead.

Loading…
Cancel
Save