New Features¶

• It is now possible to set the report interval for the networking-baremetalml2 agent by using new parameterreport_interval in theneutron::agents::ml2::networking_baremetal class.

• Theneutron::agents::ovn_metadata class now supportsthe following two new parameters.

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

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

• Theneutron::plugins::ml2::ovn class now supports the following twonew parameters.

  • ovsdb_retry_max_interval

  • ovsdb_probe_interval

Bug Fixes¶

• Bug #1987460:Previously theneutron::agents::ml2::mlnx class causes duplicateresources when used with theneutron::agents::dhcp class ortheneutron::agents::l3 class. Now it is possible to workaroundthe error by implementing the following mitigation.

  • Include theneutron::agents::ml2::mlnx class AFTERtheneutron::agents::dhcp class or theneutron::agents::l3

  • Set theinterface_driver parameter and thedhcp_broadcast_replyparameter consistently.

New Features¶

• The following new parameters have been added to support arbitraryconfigurations 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 tothe following classes.

  • neutron::agent::l3

  • neutron::agent::ml2::ovs

  • neutron::plugins::ml2::ovn

• Now theneutron::agents::ml2::ovs class andtheneutron::agents::ml2::sriov class supportsthe resource_provider_default_hypervisor parameter to set the correspondingparameter in ovs-agent and sriov-agent.

New Features¶

• The newneutron::keystone::authtoken::interface parameter has beenadded, which can be used to set the interface parameter in authtokenmiddleware.

• The following two new classes have been added, to set up parameters inovs_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 agentWhen set to True, the accepted egress unicast traffic will not use actionNORMAL. The accepted egress packets will be taken care of in the finalegress tables direct output flows for unicast traffic so that operators canset 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 ofbridge name and hyper visor name to locate the parent of the resourceprovider tree.

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

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

Deprecation Notes¶

• Usage of config optionfirewall_driver in theneutron::plugins::ml2class is now deprecated and has no effect on the deployment.Config optionfirewall_driver should be set in the classes for agents’configuration likeneutron::agents::ml2::ovs instead.Usage of this option in the Neutron server was there just for backwardcompatibility with old agents which can’t report what driver they are using.Since Newton all Neutron drivers are reporting that in heartbeat messages andthere 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 afuture release. Please use project_domain_name and user_domain_nameinstead.

  • 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_overflowparameters in neutron::server class is deprecated. Please set them in theneutron::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_overflowparameters in neutron::server class is deprecated.

New Features¶

• Added new parameters of_connect_timeout and of_request_timeout in theneutron::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 themetadata_workers configurationoption for the OVN metadata agents to 2 (from $::os_workers). Whilethe OVS metadata agents runs on the controllers/gateway nodes (anddefaults to $::os_workers) the OVN metadata agents are distributedand runs on the compute nodes instead so, there’s no point in runningdozen of them on each compute. Also, by reducing the number of workerswe also reduce the burden on the OVSDB that the OVN metadata agentconnects 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 usernamepassed to radvd.

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

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

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