Queens Series Release Notes

Queens Series Release Notes

1.0.0-9

Upgrade Notes

  • To fix bug: 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.

  • 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 and bug: 2004938 for more details.

1.0.0

New Features

  • Adds support for load distribution when multiple instances of the networking-baremetal agent are running. Each instance will manage a subset of bare metal nodes. In case one or more instances of networking-baremetal agent is lost, the remaining instances will take over the bare metal nodes previously managed by the the lost instance(s).

  • Add neutron agent ironic-neutron-agent to enable integration with neutron routed provider networks. The ml2 agent reports the state of ironic ports associated with ironic nodes to neutron, it populates the bridge_mappings configuration for each ironic node. The agent data can be used by the neutron segments plug-in in conjunction with neutron ml2 mechanism driver to ensure that port binding and ipam ip address allocations are taken from subnets associated with physical network segments available to the ironic port.

  • Baremetal ml2 mechanism driver integration with the L2 agent. This enables the ml2 mechanism driver to use the agent_db data when binding ports. E.g the bridge mappings to enable binding on routed provider networks.

  • Add support for type vlan networks in baremetal ml2 mechanism driver. This enables binding on networks using vlans for segmentation. It is only setting type vlan as supported. The intent is to use this in combination with another neutron mechanism driver that actually knows how to configure the network devices.

    Note

    The driver will not do anything to set up the correct vlan tagging in the network infrastructure such as switches or baremetal node ports.

    Another ml2 mechanism driver, or some other implementation, must be enabled to perform the necessary configuration on network devices.

Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.