From de581d5518e844491d04e4b827428d48b5d4a875 Mon Sep 17 00:00:00 2001 From: Dmitry Tantsur Date: Sun, 6 Aug 2017 20:41:21 +0200 Subject: [PATCH] Release notes clean up for the next release Change-Id: I4b911928bcdb65a9950dfe955afc5a4f554d9bd1 --- .../notes/add-gmr-3c9278d5d785895f.yaml | 12 ++++---- ...added-redfish-driver-00ff5e3f7e9d6ee8.yaml | 14 ++++----- .../notes/bug-1694645-57289200e35bd883.yaml | 18 +++++++----- .../notes/bug-1702158-79bf57bd4d8087b6.yaml | 29 +++++++++++-------- ...t-using-ceph-radosgw-8c6f7b8bede2077c.yaml | 19 ++++++------ ...rac-fix-oob-cleaning-b4b717895e243c9b.yaml | 9 +++--- ...e-osprofiler-support-e3839b0fa90d3831.yaml | 26 ++++++++++------- .../fix-bug-1675529-479357c217819420.yaml | 11 +++---- ...identifier-overwrite-42b33a5a0f7742d8.yaml | 7 +++-- ...-drivers-log-message-c3c64c1ca0a0bca8.yaml | 4 +-- .../ilo-hardware-type-48fd1c8bccd70659.yaml | 11 ++++--- ...ep-reset-bios-config-a8bed625670b7fdf.yaml | 22 ++++++++------ ...timeout-configurable-b2365b7699b0f98b.yaml | 9 +++--- .../messaging-log-level-5f870ea69db53d26.yaml | 5 ++-- .../no-more-legacy-auth-eeb32f907d0ab5de.yaml | 12 ++++---- ...e-save-internal-info-c5cc8f56f1d0dab0.yaml | 3 +- ...de-storage-interface-7fd07ee7ee71cd22.yaml | 20 ++++++------- ...-agent-mixin-removal-b7277e8f20df5ef2.yaml | 6 ++-- ..._settings_to_neutron-a6aec830a82c38a3.yaml | 6 ++-- ...ort-physical-network-a7009dc514353796.yaml | 15 +--------- .../redfish-power-wait-c5d95432a3a714c4.yaml | 6 ---- ...ance-info-for-deploy-2fe165fc018010e4.yaml | 12 ++++---- ...dhcp-provider-method-89926a8f0f4793a4.yaml | 3 +- .../socat-address-conf-5cf043fabb10bd76.yaml | 7 ++--- 24 files changed, 140 insertions(+), 146 deletions(-) delete mode 100644 releasenotes/notes/redfish-power-wait-c5d95432a3a714c4.yaml diff --git a/releasenotes/notes/add-gmr-3c9278d5d785895f.yaml b/releasenotes/notes/add-gmr-3c9278d5d785895f.yaml index f31f263038..9505b4846c 100644 --- a/releasenotes/notes/add-gmr-3c9278d5d785895f.yaml +++ b/releasenotes/notes/add-gmr-3c9278d5d785895f.yaml @@ -1,8 +1,8 @@ --- features: - - Adds support to generate Guru Meditation Reports(GMR) for both - ironic-api and ironic-conductor services. GMR provides useful - debugging information that can be used to obtain an accurate - view on the current live state of the system. For example, what - threads are running, what configuration parameters are in effect, - and more. + - Adds support for generating `Guru Meditation Reports + `_ (GMR) for both + ironic-api and ironic-conductor services. GMR provides debugging + information that can be used to obtain an accurate view on the current + state of the system. For example, what threads are running, what + configuration parameters are in effect, and more. diff --git a/releasenotes/notes/added-redfish-driver-00ff5e3f7e9d6ee8.yaml b/releasenotes/notes/added-redfish-driver-00ff5e3f7e9d6ee8.yaml index d034f31b12..403af9e11e 100644 --- a/releasenotes/notes/added-redfish-driver-00ff5e3f7e9d6ee8.yaml +++ b/releasenotes/notes/added-redfish-driver-00ff5e3f7e9d6ee8.yaml @@ -1,12 +1,12 @@ --- features: - | - Adds support for Redfish with: + Adds support for the `Redfish `_ + standard via a new ``redfish`` hardware type. It uses two new interfaces: - * ``redfish`` hardware type - * ``redfish`` power interface that provides hard power - [on, off, reboot] and soft power [off, reboot] - * ``redfish`` management interface to set the boot device (PXE, disk, - cd-rom and bios) and its frequency (persistent or not); and NMI - injection SSL authentication + * ``redfish`` power interface supports all hard and soft power operations + * ``redfish`` management interface supports: + - getting and setting the boot device (PXE, disk, CD-ROM or BIOS) + - making the configured boot device persistent or not + - injecting NMI diff --git a/releasenotes/notes/bug-1694645-57289200e35bd883.yaml b/releasenotes/notes/bug-1694645-57289200e35bd883.yaml index a304d6a32c..c83c868e3f 100644 --- a/releasenotes/notes/bug-1694645-57289200e35bd883.yaml +++ b/releasenotes/notes/bug-1694645-57289200e35bd883.yaml @@ -1,12 +1,14 @@ --- fixes: - | - Fixes a bug whereby netboot was unavailable with virtual media boot in an - environment using syslinux 5.00 or later, such as Ubuntu 16.04. This was - caused by a syslinux change; the ldlinux.c32 file is required for creating - a boot ISO. To address this, the new configuration option - ``[DEFAULT]/ldlinux_32`` can be set to the path of the ldlinux.c32 file. - If not specified, the default is to look for the file in the paths: + Fixes netboot with virtual media boot in an environment using syslinux + 5.00 or later, such as Ubuntu 16.04. It was broken by a change in the + location of the ``ldlinux.c32`` file. +features: + - | + New configuration option ``[DEFAULT]/ldlinux_32`` can used to set the + location of the ``ldlinux.c32`` file (from the syslinux package). + The default behavior is to look for it in the following locations: - * /usr/lib/syslinux/modules/bios/ldlinux.c32 - * /usr/share/syslinux/ldlinux.c32 + * ``/usr/lib/syslinux/modules/bios/ldlinux.c32`` + * ``/usr/share/syslinux/ldlinux.c32`` diff --git a/releasenotes/notes/bug-1702158-79bf57bd4d8087b6.yaml b/releasenotes/notes/bug-1702158-79bf57bd4d8087b6.yaml index fe7ba44c6a..de600af34e 100644 --- a/releasenotes/notes/bug-1702158-79bf57bd4d8087b6.yaml +++ b/releasenotes/notes/bug-1702158-79bf57bd4d8087b6.yaml @@ -1,22 +1,27 @@ --- fixes: - | - Fixes a bug 1702158, where the wrong database engine is used for the - conductor_hardware_interfaces table, if the system is using MySQL prior to - version 5.5 (or the default_storage_engine option is set explicitly to - 'MyISAM' in my.cnf). In this case, a table could be created with MyISAM - engine and foreign key constraint conductor_id(conductors.id) ignored. + Fixes database schema that could cause the wrong database engine to be + utilized for the ``conductor_hardware_interfaces`` table, if the system + is using MySQL prior to version 5.5 or the ``default_storage_engine`` + option is set explicitly to 'MyISAM' in ``my.cnf``. + In this case, a table could be created with MyISAM engine, and the foreign + key constraint ``conductor_id(conductors.id)`` was ignored. + See `bug 1702158 `_ + for details. upgrade: - | - Due to a bug 1702158, conductor_hardware_interfaces table could be created - with MyISAM database engine, while all other tables in ironic database are + Due to `bug 1702158 `_, + the ``conductor_hardware_interfaces`` table could be created with MyISAM + database engine, while all other tables in ironic database are using InnoDB engine. This could happen during initial installation, or - upgrade to ocata release, if the system is using MySQL prior to version 5.5 - (or the default_storage_engine option is set explicitly to 'MyISAM' in - my.cnf). If this is the case, conductor_hardware_interfaces needs to be - manually migrated to InnoDB, and foreign key constraint re-created:: + upgrade to the Ocata release, if the system was using MySQL prior to + version 5.5 or the ``default_storage_engine`` option was set explicitly + to 'MyISAM' in ``my.cnf``. If this is the case, the + ``conductor_hardware_interfaces`` table needs to be manually migrated + to InnoDB, and the foreign key constraint needs to be re-created:: alter table conductor_hardware_interfaces engine='InnoDB'; alter table conductor_hardware_interfaces add constraint conductor_hardware_interfaces_ibfk_1 - foreign key (conductor_id) references conductors(id); \ No newline at end of file + foreign key (conductor_id) references conductors(id); diff --git a/releasenotes/notes/configdrive-support-using-ceph-radosgw-8c6f7b8bede2077c.yaml b/releasenotes/notes/configdrive-support-using-ceph-radosgw-8c6f7b8bede2077c.yaml index e47a9b1901..10daf5664f 100644 --- a/releasenotes/notes/configdrive-support-using-ceph-radosgw-8c6f7b8bede2077c.yaml +++ b/releasenotes/notes/configdrive-support-using-ceph-radosgw-8c6f7b8bede2077c.yaml @@ -1,16 +1,17 @@ --- features: - - Adds support for storing the configdrive in radosgw using - the swift API. + - | + Adds support for storing the configdrive in `Ceph Object Gateway + `_ (radosgw) instead + of the OpenStack Object service (swift) using the compatible API. - | Adds support to use the radosgw authentication mechanism that relies - on username and password instead of auth token. + on a user name and a password instead of an authentication token. The following options must be specified in ironic configuration file: - * ``[swift]/auth_url`` - * ``[swift]/username`` - * ``[swift]/password`` - + * ``[swift]/auth_url`` + * ``[swift]/username`` + * ``[swift]/password`` deprecations: - The ``[conductor]/configdrive_use_swift`` and ``[glance]/temp_url_endpoint_type`` options are deprecated and will be @@ -18,6 +19,6 @@ deprecations: Use ``[deploy]/configdrive_use_object_store`` and ``[deploy]/object_store_endpoint_type`` respectively instead. upgrade: - - Adds a ``[deploy]/object_store_endpoint_type`` option to specify the + - Adds the ``[deploy]/object_store_endpoint_type`` option to specify the type of endpoint to use for instance images and configdrive storage. - Allowed values are 'swift' or 'radosgw'. The default is 'swift'. + Allowed values are ``swift`` or ``radosgw``. The default is ``swift``. diff --git a/releasenotes/notes/drac-fix-oob-cleaning-b4b717895e243c9b.yaml b/releasenotes/notes/drac-fix-oob-cleaning-b4b717895e243c9b.yaml index 3d648c3d50..53a09d42ca 100644 --- a/releasenotes/notes/drac-fix-oob-cleaning-b4b717895e243c9b.yaml +++ b/releasenotes/notes/drac-fix-oob-cleaning-b4b717895e243c9b.yaml @@ -1,7 +1,6 @@ --- fixes: - - Fixes issue where RAID creation/deletion done as part of out-of-band - cleaning would frequently fail when using the iDRAC driver due to - Export Configuration job running. For more information, see - https://bugs.launchpad.net/ironic/+bug/1691808. Note that this fix - requires python-dracclient version 1.3.0 or higher. + - Fixes `bug 1691808 `_ + causing RAID creation/deletion to frequently fail when using the iDRAC + driver due to an *Export Configuration* job running. The fix requires + the ``python-dracclient`` library of version 1.3.0 or higher. diff --git a/releasenotes/notes/enable-osprofiler-support-e3839b0fa90d3831.yaml b/releasenotes/notes/enable-osprofiler-support-e3839b0fa90d3831.yaml index c001cb85bd..3bbf064ec8 100644 --- a/releasenotes/notes/enable-osprofiler-support-e3839b0fa90d3831.yaml +++ b/releasenotes/notes/enable-osprofiler-support-e3839b0fa90d3831.yaml @@ -1,17 +1,21 @@ --- features: - | - Adds OSProfiler support. This cross-project profiling library - provides the ability to trace various OpenStack requests through all - OpenStack services that support it. To initiate OpenStack request tracing, - `--profile ` option needs to be added to the CLI command. - As part of the output, there will be a message with . - To see the HTML graphs, the following command should be used - - `$ osprofiler trace show --html --out result.html`. See - OSProfiler documentation: http://docs.openstack.org/developer/osprofiler/. + Adds `OSProfiler `_ support. + This cross-project profiling library provides the ability to trace various + OpenStack requests through all OpenStack services that support it. + + To initiate OpenStack request tracing, ``--os-profile `` option + needs to be added to an OpenStackClient command. As part of the output, + there will be a message with a Trace ID. + + To see the HTML graphs, the following command should be used:: + + $ osprofiler trace show --html --out result.html + security: - OSProfiler support requires passing of trace information between various OpenStack services. This information is securely signed - by one of HMAC keys, defined in ironic.conf configuration file. - To allow cross-project tracing, user should use the key that is - common among all OpenStack services he or she wants to trace. + by one of HMAC keys, defined in the ``ironic.conf`` configuration file. + To allow cross-project tracing, the same key should be used for all + OpenStack services. diff --git a/releasenotes/notes/fix-bug-1675529-479357c217819420.yaml b/releasenotes/notes/fix-bug-1675529-479357c217819420.yaml index 952ccd2155..d83c32903e 100644 --- a/releasenotes/notes/fix-bug-1675529-479357c217819420.yaml +++ b/releasenotes/notes/fix-bug-1675529-479357c217819420.yaml @@ -14,8 +14,9 @@ fixes: Prevents the IPMI driver from needlessly checking status of the baremetal node if a power change action fails. Additionally, stops retrying power actions and power status polls on receipt of a non-retryable error from - ipmitool. For more information, see - https//bugs.launchpad.net/ironic/+bug/1675529. A new configuration option - ``[conductor]/power_state_change_timeout`` can be used to specify how many - seconds to wait for a baremetal node to change power state when a power - action is requested. + ipmitool. For more information, see `bug 1675529 + `_. + + A new configuration option ``[conductor]/power_state_change_timeout`` + can be used to specify how many seconds to wait for a baremetal node + to change the power state when a power action is requested. diff --git a/releasenotes/notes/fix-disk-identifier-overwrite-42b33a5a0f7742d8.yaml b/releasenotes/notes/fix-disk-identifier-overwrite-42b33a5a0f7742d8.yaml index 6404bc15ea..c27ee6b804 100644 --- a/releasenotes/notes/fix-disk-identifier-overwrite-42b33a5a0f7742d8.yaml +++ b/releasenotes/notes/fix-disk-identifier-overwrite-42b33a5a0f7742d8.yaml @@ -1,5 +1,6 @@ --- fixes: - - Fix handling of whole disk images with 0x00000000 disk identifier. - Instances failed to boot as the identifier in boot config was overwritten - during config drive creation. See https://bugs.launchpad.net/ironic/+bug/1685093 + - Fix handling of whole disk images with disk identifier 0x00000000. + Instances failed to boot as the identifier in the boot config was + overwritten during config drive creation. See `bug 1685093 + `_. diff --git a/releasenotes/notes/fix-ilo-drivers-log-message-c3c64c1ca0a0bca8.yaml b/releasenotes/notes/fix-ilo-drivers-log-message-c3c64c1ca0a0bca8.yaml index 6cf8e75447..eac64386f2 100644 --- a/releasenotes/notes/fix-ilo-drivers-log-message-c3c64c1ca0a0bca8.yaml +++ b/releasenotes/notes/fix-ilo-drivers-log-message-c3c64c1ca0a0bca8.yaml @@ -3,5 +3,5 @@ fixes: - | When the deletion of a swift temporary object fails because the object is no longer available in swift, a message is logged. - The log level of this message was changed from ``warning`` to - ``info``. + The log level of this message was changed from ``WARNING`` to + ``INFO``. diff --git a/releasenotes/notes/ilo-hardware-type-48fd1c8bccd70659.yaml b/releasenotes/notes/ilo-hardware-type-48fd1c8bccd70659.yaml index b749c36598..513d406317 100644 --- a/releasenotes/notes/ilo-hardware-type-48fd1c8bccd70659.yaml +++ b/releasenotes/notes/ilo-hardware-type-48fd1c8bccd70659.yaml @@ -1,17 +1,16 @@ --- features: - | - Adds a new hardware type ``ilo`` for iLO 4 based Proliant Gen 8 - and Gen 9 servers. - ``ilo`` hardware type will support virtual media and PXE based - provisioning using HPE iLO 4 management engine. It supports the - following driver interfaces: + Adds a new hardware type ``ilo`` for iLO 4 based Proliant Gen 8 and Gen 9 + servers. This hardware type supports virtual media and PXE based boot + using HPE iLO 4 management engine. The following driver interfaces + are supported: * boot: ``ilo-virtual-media`` and ``ilo-pxe`` * console: ``ilo`` and ``no-console`` * deploy: ``iscsi`` and ``direct`` * inspect: ``ilo``, ``inspector`` and ``no-inspect`` * management: ``ilo`` - * network: ``flat``, ``no-op`` and ``neutron`` + * network: ``flat``, ``noop`` and ``neutron`` * power: ``ilo`` * raid: ``no-raid`` and ``agent`` diff --git a/releasenotes/notes/irmc-add-clean-step-reset-bios-config-a8bed625670b7fdf.yaml b/releasenotes/notes/irmc-add-clean-step-reset-bios-config-a8bed625670b7fdf.yaml index 36325b66fd..decc26c266 100644 --- a/releasenotes/notes/irmc-add-clean-step-reset-bios-config-a8bed625670b7fdf.yaml +++ b/releasenotes/notes/irmc-add-clean-step-reset-bios-config-a8bed625670b7fdf.yaml @@ -1,16 +1,20 @@ --- features: - - Adds new boot interface named ``irmc-pxe``. + - Adds new boot interface named ``irmc-pxe`` for PXE booting + FUJITSU PRIMERGY servers. - Adds clean step ``restore_irmc_bios_config`` to restore BIOS config - for a node during automatic cleaning. + for a node with an ``irmc``-based driver during automatic cleaning. upgrade: - Adds new configuration option ``[irmc]clean_priority_restore_irmc_bios_config``, which - enables setting priority for the clean step. Default value for - this option is 0, which means the clean step is disabled. + enables setting priority for the ``restore_irmc_bios_config`` clean step. + The default value for this option is 0, which means the clean step + is disabled. deprecations: - - Deprecates the boot interface ``pxe`` from using with hardware type - ``irmc``. It is recommended for operator to switch to use the boot - iterface ``irmc-pxe`` as soon as possible. Using the interface - ``pxe`` with ``irmc`` drivers will cause the reset bios feature - not to work even the priority option is set to enable. + - The use of the ``pxe`` boot interface with the ``irmc`` hardware typed has + been deprecated. It is recommended for to switch to the new ``irmc-pxe`` + boot interface as soon as possible. +issues: + - The ``restore_irmc_bios_config`` clean step does not work for nodes using + the ``pxe`` boot interface with the ``irmc`` hardware type. + The ``irmc-pxe`` boot interface has to be used instead. diff --git a/releasenotes/notes/make-terminal-session-timeout-configurable-b2365b7699b0f98b.yaml b/releasenotes/notes/make-terminal-session-timeout-configurable-b2365b7699b0f98b.yaml index ad29f8de74..85e1291910 100644 --- a/releasenotes/notes/make-terminal-session-timeout-configurable-b2365b7699b0f98b.yaml +++ b/releasenotes/notes/make-terminal-session-timeout-configurable-b2365b7699b0f98b.yaml @@ -1,7 +1,6 @@ --- -other: +features: - | - Adds configuration parameter ``terminal_timeout`` to section [console] - to allow operators to set the timeout value for the Socat console session. - It is time of client inactivity, in seconds, after which the connection - will be closed. \ No newline at end of file + Adds configuration option ``[console]terminal_timeout`` to allow setting + the time (in seconds) of inactivity, after which a socat-based + console terminates. diff --git a/releasenotes/notes/messaging-log-level-5f870ea69db53d26.yaml b/releasenotes/notes/messaging-log-level-5f870ea69db53d26.yaml index 60bcde7eff..f6f8cdb9b2 100644 --- a/releasenotes/notes/messaging-log-level-5f870ea69db53d26.yaml +++ b/releasenotes/notes/messaging-log-level-5f870ea69db53d26.yaml @@ -1,4 +1,5 @@ --- fixes: - - Fixes an issue where oslo.messaging DEBUG logs were being logged when, by - default, they shouldn't have been. + - | + ``DEBUG``-level logging from the ``oslo.messaging`` library is no longer + displayed by default. diff --git a/releasenotes/notes/no-more-legacy-auth-eeb32f907d0ab5de.yaml b/releasenotes/notes/no-more-legacy-auth-eeb32f907d0ab5de.yaml index bb018d9dd0..06808d3d27 100644 --- a/releasenotes/notes/no-more-legacy-auth-eeb32f907d0ab5de.yaml +++ b/releasenotes/notes/no-more-legacy-auth-eeb32f907d0ab5de.yaml @@ -5,10 +5,10 @@ upgrade: options for accessing other services from the ``[keystone_authtoken]`` section. As a result, the following configuration sections now must contain - proper authentication options for appropriate service: + proper authentication options for appropriate services: - - glance - - neutron - - swift - - inspector - - service_catalog + - glance + - neutron + - swift + - inspector + - service_catalog diff --git a/releasenotes/notes/node-save-internal-info-c5cc8f56f1d0dab0.yaml b/releasenotes/notes/node-save-internal-info-c5cc8f56f1d0dab0.yaml index acba691c72..562045cb82 100644 --- a/releasenotes/notes/node-save-internal-info-c5cc8f56f1d0dab0.yaml +++ b/releasenotes/notes/node-save-internal-info-c5cc8f56f1d0dab0.yaml @@ -2,4 +2,5 @@ fixes: - | Fixes an issue where some internal information for a node was not being - saved to the database. + saved to the database. See `bug 1679297 + `_ for details. diff --git a/releasenotes/notes/notify-node-storage-interface-7fd07ee7ee71cd22.yaml b/releasenotes/notes/notify-node-storage-interface-7fd07ee7ee71cd22.yaml index c7d556702b..ab72f56118 100644 --- a/releasenotes/notes/notify-node-storage-interface-7fd07ee7ee71cd22.yaml +++ b/releasenotes/notes/notify-node-storage-interface-7fd07ee7ee71cd22.yaml @@ -1,15 +1,13 @@ --- features: - | - Adds storage interface field to node-related notifications: + Adds ``storage_interface`` field to the node-related notifications: - Affected notifications are: - - * baremetal.node.create.*, new payload version 1.2 - * baremetal.node.update.*, new payload version 1.2 - * baremetal.node.delete.*, new payload version 1.2 - * baremetal.node.maintenance.*, new payload version 1.4 - * baremetal.node.console.*, new payload version 1.4 - * baremetal.node.power_set.*, new payload version 1.4 - * baremetal.node.power_state_corrected.*, new payload version 1.4 - * baremetal.node.provision_set.*, new payload version 1.4 + * ``baremetal.node.create.*`` (new payload version 1.2) + * ``baremetal.node.update.*`` (new payload version 1.2) + * ``baremetal.node.delete.*`` (new payload version 1.2) + * ``baremetal.node.maintenance.*`` (new payload version 1.4) + * ``baremetal.node.console.*`` (new payload version 1.4) + * ``baremetal.node.power_set.*`` (new payload version 1.4) + * ``baremetal.node.power_state_corrected.*`` (new payload version 1.4) + * ``baremetal.node.provision_set.*`` (new payload version 1.4) diff --git a/releasenotes/notes/oneview-agent-mixin-removal-b7277e8f20df5ef2.yaml b/releasenotes/notes/oneview-agent-mixin-removal-b7277e8f20df5ef2.yaml index 78a6be2f53..ece2ea4a4f 100644 --- a/releasenotes/notes/oneview-agent-mixin-removal-b7277e8f20df5ef2.yaml +++ b/releasenotes/notes/oneview-agent-mixin-removal-b7277e8f20df5ef2.yaml @@ -1,6 +1,6 @@ --- features: - | - Oneview drivers caches the next boot device in node's internal - info when set_boot_device() is called. It is applied on the - bare metal when node is power cycled. + The OneView drivers now retain the next boot device in node's internal + info when setting a boot device is requested. It is applied on the node + when it is power cycled. diff --git a/releasenotes/notes/pass_portgroup_settings_to_neutron-a6aec830a82c38a3.yaml b/releasenotes/notes/pass_portgroup_settings_to_neutron-a6aec830a82c38a3.yaml index 8d960bad2a..704aeecc92 100644 --- a/releasenotes/notes/pass_portgroup_settings_to_neutron-a6aec830a82c38a3.yaml +++ b/releasenotes/notes/pass_portgroup_settings_to_neutron-a6aec830a82c38a3.yaml @@ -1,5 +1,5 @@ --- features: - - Passes port group information (``portgroup.mode`` and - ``portgroup.properties``) to Neutron via Neutron ``port.binding:profile`` - field. \ No newline at end of file + - Port group information (``mode`` and ``properties`` fields) + is now passed to Neutron via the port's ``binding:profile`` field. + This allows an ML2 driver to configure the port bonding automatically. diff --git a/releasenotes/notes/port-physical-network-a7009dc514353796.yaml b/releasenotes/notes/port-physical-network-a7009dc514353796.yaml index 6fe1c8c452..bfe2041593 100644 --- a/releasenotes/notes/port-physical-network-a7009dc514353796.yaml +++ b/releasenotes/notes/port-physical-network-a7009dc514353796.yaml @@ -15,25 +15,12 @@ features: provides information on how to configure and use physical networks. upgrade: - | - Adds a ``physical_network`` field to the port object in REST API version - 1.34. - - This field specifies the name of the physical network to which the port is - connected, and is empty by default. This field may be set by the operator - to allow the Bare Metal service to incorporate physical network information - when attaching virtual interfaces (VIFs). - - The REST API endpoints related to ports provide support for the - ``physical_network`` field. The `ironic developer documentation - `_ - provides information on how to configure and use physical networks. - Following an upgrade to this release, all ports will have an empty ``physical_network`` field. Attachment of Virtual Interfaces (VIFs) will continue to function as in the previous release until any ports have their physical network field set. During a live upgrade to this release, the ``physical_network`` field will - not be available. It will also not be possible to create ports which are + not be available. It will also not be possible to create ports which are members of a port group during a live upgrade, as the API service will be unable to validate the consistency of the request. diff --git a/releasenotes/notes/redfish-power-wait-c5d95432a3a714c4.yaml b/releasenotes/notes/redfish-power-wait-c5d95432a3a714c4.yaml deleted file mode 100644 index 65b79514a6..0000000000 --- a/releasenotes/notes/redfish-power-wait-c5d95432a3a714c4.yaml +++ /dev/null @@ -1,6 +0,0 @@ ---- -fixes: - - | - The ``redfish`` power interface now waits for a power action to apply. - Previously it used to return immediately, which was not consistent with - how other power interfaces work. diff --git a/releasenotes/notes/remove-deprecated-build-instance-info-for-deploy-2fe165fc018010e4.yaml b/releasenotes/notes/remove-deprecated-build-instance-info-for-deploy-2fe165fc018010e4.yaml index 3493ecb1ba..feed583b4f 100644 --- a/releasenotes/notes/remove-deprecated-build-instance-info-for-deploy-2fe165fc018010e4.yaml +++ b/releasenotes/notes/remove-deprecated-build-instance-info-for-deploy-2fe165fc018010e4.yaml @@ -1,8 +1,8 @@ --- -upgrade: +other: - | - The method build_instance_info_for_deploy() from - ironic.drivers.modules.agent was deprecated in Ocata cycle (7.0.0). - It is no longer supported. Please use the method - build_instance_info_for_deploy() from ironic.drivers.modules.deploy_utils - instead. + The method ``build_instance_info_for_deploy()`` from the + ``ironic.drivers.modules.agent`` module was deprecated in the Ocata cycle + (version 7.0.0). It is no longer available. Please use the method + ``build_instance_info_for_deploy()`` from the + ``ironic.drivers.modules.deploy_utils`` module instead. diff --git a/releasenotes/notes/remove-deprecated-dhcp-provider-method-89926a8f0f4793a4.yaml b/releasenotes/notes/remove-deprecated-dhcp-provider-method-89926a8f0f4793a4.yaml index d6e78c7726..fc6a648be0 100644 --- a/releasenotes/notes/remove-deprecated-dhcp-provider-method-89926a8f0f4793a4.yaml +++ b/releasenotes/notes/remove-deprecated-dhcp-provider-method-89926a8f0f4793a4.yaml @@ -10,8 +10,7 @@ upgrade: * ``vif_list``: List attached VIF IDs for a node. * ``vif_attach``: Attach a virtual network interface to a node. * ``vif_detach``: Detach a virtual network interface from a node. - * ``port_changed``: Handle any actions required when a port - changes. + * ``port_changed``: Handle any actions required when a port changes. * ``portgroup_changed``: Handle any actions required when a port group changes. * ``get_current_vif``: Return VIF ID attached to port or port group diff --git a/releasenotes/notes/socat-address-conf-5cf043fabb10bd76.yaml b/releasenotes/notes/socat-address-conf-5cf043fabb10bd76.yaml index 266aecdfa6..022bfda17b 100644 --- a/releasenotes/notes/socat-address-conf-5cf043fabb10bd76.yaml +++ b/releasenotes/notes/socat-address-conf-5cf043fabb10bd76.yaml @@ -1,7 +1,6 @@ --- features: - | - Adds configuration option ``[console]/socat_address`` so - that the binding address of socat based console can be - configured independently. The option is backward compatible - by keeping $my_ip as the default value. + Adds new configuration option ``[console]/socat_address`` to set the + binding address for socat-based console. The default is the value of the + ``[DEFAULT]my_ip`` option of the conductor responsible for the node.