Ussuri Series Release Notes


New Features

  • It is now possible to set the report interval for the networking-baremetal ml2 agent by using new parameter report_interval in the neutron::agents::ml2::networking_baremetal class.

  • The neutron::agents::ovn_metadata class now supports the following two new parameters.

    • ovsdb_probe_interval parameter to configure [ovn]ovsdb_probe_interval in ovn metadata agent config file.

    • ovsdb_retry_max_interval parameter to configure [ovn]ovsdb_retry_max_interval in ovn metadata agent config file.

  • The neutron::plugins::ml2::ovn class now supports the following two new parameters.

    • ovsdb_retry_max_interval

    • ovsdb_probe_interval

Bug Fixes

  • Bug #1987460: Previously the neutron::agents::ml2::mlnx class causes duplicate resources when used with the neutron::agents::dhcp class or the neutron::agents::l3 class. Now it is possible to workaround the error by implementing the following mitigation.

    • Include the neutron::agents::ml2::mlnx class AFTER the neutron::agents::dhcp class or the neutron::agents::l3

    • Set the interface_driver parameter and the dhcp_broadcast_reply parameter consistently.


New Features

  • The following new parameters have been added to support arbitrary configurations for openvsiwtch_agent.ini and sriov_agent.ini

    • neutron::config::ovs_agent_config

    • neutron::config::sriov_agent_config

  • Support for the logging serivce plugin parameters has been added to the following classes.

    • neutron::agent::l3

    • neutron::agent::ml2::ovs

    • neutron::plugins::ml2::ovn

  • Now the neutron::agents::ml2::ovs class and the neutron::agents::ml2::sriov class supports the resource_provider_default_hypervisor parameter to set the corresponding parameter in ovs-agent and sriov-agent.


New Features

  • The new neutron::keystone::authtoken::interface parameter has been added, which can be used to set the interface parameter in authtoken middleware.

  • The following two new classes have been added, to set up parameters in ovs_driver and sriov_driver section.

    • neutron::plugins::ml2::ovs_driver

    • neutron::plugins::ml2::sriov_driver

  • Add new configuration parameter explicitly_egress_direct for ML2 OVS agent When set to True, the accepted egress unicast traffic will not use action NORMAL. The accepted egress packets will be taken care of in the final egress tables direct output flows for unicast traffic so that operators can set customized integration bridge name in l3 agent configuration. This can be enabled on some nodes to prevent flooding on integration bridge.

  • The following two parameters have been added to define mapping of bridge name and hyper visor name to locate the parent of the resource provider tree.

    • neutron::agents::ml2::ovs::resource_provider_hypervisors

    • neutorn::agents::ml2::sriov::resource_provider_hypervisors

Deprecation Notes

  • Usage of config option firewall_driver in the neutron::plugins::ml2 class is now deprecated and has no effect on the deployment. Config option firewall_driver should be set in the classes for agents’ configuration like neutron::agents::ml2::ovs instead. Usage of this option in the Neutron server was there just for backward compatibility with old agents which can’t report what driver they are using. Since Newton all Neutron drivers are reporting that in heartbeat messages and there is no need to keep configure this in the neutron server’s side.


New Features

  • Add ‘dnsmasq_enable_addr6_list’ option support to dhcp agent settings. (See bug: #1861032)

  • The following parameters are now deprecated, and will be removed in a future release. Please use project_domain_name and user_domain_name instead.

    • neutron::ml2::networking_baremetal::project_domain_id

    • neutron::ml2::networking_baremetal::user_domain_id

    • neutron::ml2::designate::project_domain_id

    • neutron::ml2::designate::user_domain_id

    • neutron::ml2::server::placement::project_domain_id

    • neutron::ml2::server::placement::user_domain_id

    • neutron::ml2::server::notifications::project_domain_id

    • neutron::ml2::server::notifications::user_domain_id

  • Add support for resource provider bandwidth.

Upgrade Notes

  • The database_connection, database_max_retries, database_idle_timeout, database_retry_interval, database_max_pool_size and database_max_overflow parameters in neutron::server class is deprecated. Please set them in the neutron::db class instead.

  • Deprecated idle_timeout option has been removed.

Deprecation Notes

  • database_min_pool_size option is now deprecated for removal, the parameter has no effect.

  • The database_connection, database_max_retries, database_idle_timeout, database_retry_interval, database_max_pool_size and database_max_overflow parameters in neutron::server class is deprecated.


New Features

  • Added new parameters of_connect_timeout and of_request_timeout in the neutron::agents::ml2::ovs class.

  • Added new parameter neutron::agents::ml2::ovs::of_inactivity_probe.

  • Added new parameter neutron::agents::ml2::ovs::ovsdb_timeout.

Upgrade Notes

  • Switched the default value of the metadata_workers configuration option for the OVN metadata agents to 2 (from $::os_workers). While the OVS metadata agents runs on the controllers/gateway nodes (and defaults to $::os_workers) the OVN metadata agents are distributed and runs on the compute nodes instead so, there’s no point in running dozen of them on each compute. Also, by reducing the number of workers we also reduce the burden on the OVSDB that the OVN metadata agent connects to making OVN more scalable.

  • The deprecated parameter neutron::agents::metadata::metadata_ip is removed. Please use the neutron::agents::metadata::metadata_host parameter.

  • The parameter neutron::agents::ml2::ovs::of_interface is now removed.

Deprecation Notes

  • The neutron::agents::ml2::ovs::ovsdb_interface is deprecated and has no effect.


New Features

  • Added new parameters radvd_user that can define the username passed to radvd.

  • Add possibility to configure the size of executor thread pool.

  • Add a new configuration option called “ovn_emit_need_to_frag” to the “ovn” section of etc/neutron/plugins/ml2_conf.ini. This new option tells ovn whether it should emit “need to frag” packets in case of MTU mismatch. Before enabling this configuration make sure that its supported by the host kernel (version >= 5.2) or by checking the output of the following command: ovs-appctl -t ovs-vswitchd dpif/show-dp-features br-int | grep “Check pkt length action”. Defaults to False.

  • This parameter sets inactive probe interval of the JSON session from ovn-metadata to the OVN SB database. By default this it is 5s which not be sufficient in loaded systems or during high control-plane activity spikes, leading to unnecessary reconnections to OVSDB server. Now it is extended by default to 1 min and it is configurable by param OVNRemoteProbeInterval.