Release notes clean up for the next release
Change-Id: I4b911928bcdb65a9950dfe955afc5a4f554d9bd1
This commit is contained in:
Dmitry Tantsur
parent
c08c21e308
commit
de581d5518
@ -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
|
||||
<https://wiki.openstack.org/wiki/GuruMeditationReport>`_ (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.
|
||||
|
||||
@ -1,12 +1,12 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Adds support for Redfish with:
|
||||
Adds support for the `Redfish <https://www.dmtf.org/standards/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
|
||||
|
||||
@ -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``
|
||||
|
||||
@ -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 <https://bugs.launchpad.net/ironic/+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 <https://bugs.launchpad.net/ironic/+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);
|
||||
foreign key (conductor_id) references conductors(id);
|
||||
|
||||
@ -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
|
||||
<http://docs.ceph.com/docs/master/radosgw/>`_ (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``.
|
||||
|
||||
@ -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 <https://bugs.launchpad.net/ironic/+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.
|
||||
|
||||
@ -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 <HMAC_KEY>` option needs to be added to the CLI command.
|
||||
As part of the output, there will be a message with <trace_id>.
|
||||
To see the HTML graphs, the following command should be used -
|
||||
`$ osprofiler trace show <trace_id> --html --out result.html`. See
|
||||
OSProfiler documentation: http://docs.openstack.org/developer/osprofiler/.
|
||||
Adds `OSProfiler <https://docs.openstack.org/osprofiler/latest/>`_ 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 <HMAC_KEY>`` 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 <trace_id> --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.
|
||||
|
||||
@ -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
|
||||
<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 the power state when a power action is requested.
|
||||
|
||||
@ -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
|
||||
<https://bugs.launchpad.net/ironic/+bug/1685093>`_.
|
||||
|
||||
@ -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``.
|
||||
|
||||
@ -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``
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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.
|
||||
Adds configuration option ``[console]terminal_timeout`` to allow setting
|
||||
the time (in seconds) of inactivity, after which a socat-based
|
||||
console terminates.
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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
|
||||
<https://bugs.launchpad.net/ironic/+bug/1679297>`_ for details.
|
||||
|
||||
@ -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)
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- Passes port group information (``portgroup.mode`` and
|
||||
``portgroup.properties``) to Neutron via Neutron ``port.binding:profile``
|
||||
field.
|
||||
- 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.
|
||||
|
||||
@ -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
|
||||
<https://docs.openstack.org/ironic/latest/admin/multitenancy.html>`_
|
||||
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.
|
||||
|
||||
@ -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.
|
||||
@ -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.
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user