Bug Fixes¶

• Fixed the incorrect handling of exceptions from openstacksdk when queryingthe list of ports from ironic, that caused the agent to stop reportingits state. Also when there are problems querying ports, agent now does notreport an empty state, and rather waits for the next iteration to retry.

Upgrade Notes¶

• Operators using ironic-neutron-agent withnoauth authenticationstrategy (i.e standalone ironic without keystone) must update theconfiguration. Replace[ironic]/auth_strategy=noauth with[ironic]/auth_type=none and set the[ironic]/endpoint_overrideoption accordingly.

Deprecation Notes¶

• With the switch from ironicclient to openstacksdk the following options hasbeen deprecated.

  • [ironic]/ironic_url replaced by[ironic]/endpoint_override

  • [ironic]/os_region replaced by[ironic]/region_name

  • [ironic]/retry_interval replaced by[ironic]/status_code_retries

  • [ironic]/max_retries replaced by[ironic]/status_code_retry_delay

  • [ironic]/auth_strategy isignored, please use[ironic]/auth_type instead.

Other Notes¶

• Communication with ironic is now using openstacksdk, removing the dependencyon ironicclient.

Upgrade Notes¶

• Python 2.7 support has been dropped. Last release of Networking Baremetalto support Python 2.7 is OpenStack Train. The minimum version of Python nowsupported by Networking Baremetal is Python 3.6.

Upgrade Notes¶

• To fixbug: 2004933oslo.messaging notification queues are now renamed and created withamqp_auto_delete=true. When upgrading the agent old queues should bedeleted to free up message broker resources. Previous queue that can bedeleted are namedironic-neutron-agent-heartbeat.info. There mayalso be queues with uuid of previous agent instances as name, these canalso safely be deleted. (Look in the agent logs for relevant agent uuids).

  On rabbitmq queues can be deleted via the web console. For example withcurl:

  curl-i-uusername:password \-H"content-type:application/json"-XDELETE \http://<host>:<web-port>/api/queues/<vhost>/<queue-name>

  Another example with vhost: ‘/’ deleting theironic-neutron-agent-heartbeat.info queue:

  curl-i-uusername: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 remainedin the broker without any consumer after agent restart. The notificationqueues will now be created withamqp_auto_delete=true. Seebug:2004933.

• Fixes an issue causing heavy RAM (and/or-storage) usage on the messagebroker back-end. Theironic-neutron-agent uses oslo.messagingnotifications, with all notification listeners using pools. Since alllisteneres are using pools the default notification queue in messaging isnot consumed (only the pool queues are consumed). The default notificationqueue was continously growing, consuming more and more resources on themessaging back-end. Seeoslo.messaging bug: 1814544 andbug:2004938 for moredetails.

New Features¶

• Issuing a SIGHUP (e.g.pkill-HUPironic-neutron-agent) to the agentservice will cause the service to reload and use any changed values formutable configuration options.

  Mutable configuration options are indicated as such in thesampleconfiguration filebyNote:Thisoptioncanbechangedwithoutrestarting.

  A warning is logged for any changes to immutable configuration options.

New Features¶

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

• Add neutron agentironic-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 typevlan networks in baremetal ml2 mechanism driver.This enables binding on networks using vlans for segmentation. It is onlysetting typevlan as supported. The intent is to use this incombination with another neutron mechanism driver that actually knows howto configure the network devices.

  Note

  The driver willnot do anything toset up the correctvlan tagging in the network infrastructure such as switchesor baremetal node ports.

  Another ml2 mechanism driver, or some other implementation, mustbe enabled to perform the necessary configuration on networkdevices.

Prelude¶

This is the initial release of the networking-baremetal. The project includes thebaremetal ml2 mechanism driver performing binding of the Networking service ports withbinding_vnic_type=baremetal in flat networks. It also includes the devstack plugin to simplify the development setup and testing.