We are jazzed to announce the release of:
networking-baremetal 1.2.1: Neutron plugin that provides deep Ironic/Neutron integration.
This release is part of the rocky stable release series.
The source is available from:
https://opendev.org/openstack/networking-baremetal
Download the package from:
https://pypi.org/project/networking-baremetal
Please report issues through:
https://storyboard.openstack.org/#!/project/openstack/networking- baremetal
For more details, please see below.
1.2.1 ^^^^^
Upgrade Notes *************
* To fix bug: 2004933 (https://storyboard.openstack.org/#!/story/2004933) oslo.messaging notification queues are now renamed and created with "amqp_auto_delete=true". When upgrading the agent old queues should be deleted to free up message broker resources. Previous queue that can be deleted are named "ironic-neutron-agent-heartbeat.info". There may also be queues with uuid of previous agent instances as name, these can also safely be deleted. (Look in the agent logs for relevant agent uuids).
On rabbitmq queues can be deleted via the web console. For example with curl:
curl -i -u username:password \ -H "content-type:application/json" -XDELETE \ http://<host>:<web-port>/api/queues/<vhost>/<queue-name>
Another example with vhost: '/' deleting the ironic-neutron-agent- heartbeat.info queue:
curl -i -u username:password \ -H "content-type:application/json" \ -XDELETE \ http://172.20.0.1:15672/api/queues/%2F/ironic-neutron-agent-heartbeat.info
Note: In the example above the vhost is "/". To ensure the vhost is correctly encoded the use of "%2F", instead of "/" is required.
Bug Fixes *********
* Fixes an issue where old oslo.messaging notification pool queues remained in the broker without any consumer after agent restart. The notification queues will now be created with "amqp_auto_delete=true". See bug: 2004933 (https://storyboard.openstack.org/#!/story/2004933).
* Fixes an issue causing heavy RAM (and/or-storage) usage on the message broker back-end. The "ironic-neutron-agent" uses oslo.messaging notifications, with all notification listeners using pools. Since all listeneres are using pools the default notification queue in messaging is not consumed (only the pool queues are consumed). The default notification queue was continously growing, consuming more and more resources on the messaging back-end. See oslo.messaging bug: 1814544 (https://bugs.launchpad.net/oslo.messaging/+bug/1814544) and bug: 2004938 (https://storyboard.openstack.org/#!/story/2004938) for more details.
Changes in networking-baremetal 1.2.0..1.2.1 --------------------------------------------
a48fe19 OpenDev Migration Patch d35d97e Replace openstack.org git:// URLs with https:// a023687 Rename agent queue - fixes broken minor update 1359655 Ensure notifications are consumed from non-pool queue 1da5a11 Set amqp_auto_delete=true for notifications transport. a5a1d08 Rocky - Fix docs job b7a05db import zuul job settings from project-config fd03423 Update UPPER_CONSTRAINTS_FILE for stable/rocky a87bac4 Update .gitreview for stable/rocky
Diffstat (except docs and test files) -------------------------------------
.gitreview | 3 +- lower-constraints.txt | 2 +- networking_baremetal/agent/ironic_neutron_agent.py | 36 ++++++++++++++++++---- .../run.yaml | 14 ++++----- ...cation-auto-delete-queues-a3782fbeea2b57b1.yaml | 36 ++++++++++++++++++++++ ...cation-queue-not-consumed-449738d4fd799634.yaml | 13 ++++++++ requirements.txt | 2 +- tox.ini | 2 +- zuul.d/legacy-networking-baremetal-jobs.yaml | 4 +-- zuul.d/project.yaml | 6 ++++ 13 files changed, 104 insertions(+), 23 deletions(-)
Requirements updates --------------------
diff --git a/requirements.txt b/requirements.txt index d564867..3ec233c 100644 --- a/requirements.txt +++ b/requirements.txt @@ -14 +14 @@ tooz>=1.58.0 # Apache-2.0 -neutron>=13.0.0.0b1 # Apache-2.0 +neutron>=13.0.0 # Apache-2.0