We jubilantly announce the release of:
python-ironicclient 5.6.0: OpenStack Bare Metal Provisioning API Client Library
This release is part of the dalmatian release series.
The source is available from:
https://opendev.org/openstack/python-ironicclient
Download the package from:
https://pypi.org/project/python-ironicclient
Please report issues through:
https://bugs.launchpad.net/python-ironicclient/+bugs
For more details, please see below.
5.6.0 ^^^^^
New Features ************
* Increments the supported API version to 1.87.
* Adds the ability to request Ironic execute service steps upon an "active" node, utilizing the "baremetal node service" command.
Bug Fixes *********
* Fixes the list of fields permitted when creating a node. The following fields can now be set: firmware_interface, automated_clean, network_data, parent_node, owner, lessee, shard, desription.
Changes in python-ironicclient 5.5.0..5.6.0 -------------------------------------------
bc19ec2 reno: Update master for unmaintained/zed 7a3852e Remove old excludes 8b9be99 Add Service Steps to client 52467b5 Replace appdirs by platformdirs ff17b54 Fix on-creation ability 20d0a88 Update master for stable/2024.1
Diffstat (except docs and test files) -------------------------------------
ironicclient/common/filecache.py | 4 +- ironicclient/common/http.py | 2 +- ironicclient/osc/v1/baremetal_node.py | 29 ++++- ironicclient/v1/node.py | 17 ++- ironicclient/v1/utils.py | 2 + .../notes/add-service-steps-0c517e64563f6bbe.yaml | 7 ++ ...x-on-create-field-setting-60eb1ead99c69b12.yaml | 6 + releasenotes/source/2024.1.rst | 6 + releasenotes/source/index.rst | 1 + releasenotes/source/zed.rst | 2 +- requirements.txt | 9 +- setup.cfg | 1 + test-requirements.txt | 5 +- 16 files changed, 204 insertions(+), 41 deletions(-)
Requirements updates --------------------
diff --git a/requirements.txt b/requirements.txt index e218bc6..77be99f 100644 --- a/requirements.txt +++ b/requirements.txt @@ -5,6 +5,3 @@ -# The order of packages is significant, because pip processes them in the order -# of appearance. Changing the order has an impact on the overall integration -# process, which may cause wedges in the gate later. -pbr!=2.1.0,>=2.0.0 # Apache-2.0 -appdirs>=1.3.0 # MIT License -cliff!=2.9.0,>=2.8.0 # Apache-2.0 +pbr>=2.0.0 # Apache-2.0 +platformdirs>=3 # MIT License +cliff>=2.8.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index 7b19fae..de1c881 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -1,4 +1 @@ -# The order of packages is significant, because pip processes them in the order -# of appearance. Changing the order has an impact on the overall integration -# process, which may cause wedges in the gate later. -coverage!=4.4,>=4.0 # Apache-2.0 +coverage>=4.0 # Apache-2.0