New Features¶

• 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

• The newneutron::keystone::authtoken::service_type parameter has beenadded to configure the service_type parameter in authtoken middleware.

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

  • neutron::agent::l3

  • neutron::agent::ml2::ovs

  • neutron::plugins::ml2::ovn

• 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.

• 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 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

• 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

New Features¶

• 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.

Deprecation Notes¶

• Theneutron_api_config type has been deprecated.Use theneutron_api_paste_ini type instead.

• Theneutron::config::api_config parameter has been deprecated and willbe removed in a future release. Use theneutron::config::api_paste_iniparameter instead.

New Features¶

• Add mysql_enable_ndb parameter to select mysql storage engine.

Upgrade Notes¶

• The deprecated neutron::plugins::ml2::firewall_driver parameter is removed.Please set the firewall_driver in the ML2 agent classes in neutron::agents::ml2 instead.

New Features¶

• The newneutron::server::notifications::http_retries parameter has beenadded to set number of client retries.

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

• The newneutron::server::notifications::ironic class has been addedto support configuration parameters to enable notifications to ironic.

• The newserver::notifications::nova class has been added to configureparameters for notifications to nova.

Upgrade Notes¶

• The following deprecated parameters has been removed

  • neutron::server::notifications::project_domain_id

  • neutron::server::notifications::user_domain_id

  • neutron::server::notifications::tenant_id

  • neutron::server::notifications::tenant_name

  • neutron::designate::project_domain_id

  • neutron::designate::user_domain_id

• The neutron::server::database_min_pool_size andneutron::db::database_min_pool_size parameters is removed.

• The database_connection, database_max_retries, database_idle_timeout,database_retry_interval, database_max_pool_size and database_max_overflowparameters in neutron::server is removed, use the neutron::db class instead.

Deprecation Notes¶

• The neutron::server::ensure_fwaas_package is deprecated and will be removedin a future release.

• The neutron::services::fwaas class is deprecated and will be removed ina future release.

• The neutron_fwaas_service_config resource is deprecated and will be removedin a future release.

• The following parameters inserver::notifications class has beendeprecated and will be removed in a future release. Use the correspondingparameters inserver::notifications::nova class.

  • password

  • auth_type

  • username

  • project_name

  • user_domain_name

  • project_domain_name

  • auth_url

  • region_name

  • endpoint_type

  • notify_nova_on_port_status_changes

  • notify_nova_on_port_data_changes

New Features¶

• The newneutron::agent::l3::ovs_integration_bridge parameter was addedso that operators can set customized integration bridge name in l3 agentconfiguration.

Deprecation Notes¶

• Support for Arista plugin has been deprecated and will be removed in afuture release.

• Support for FUJITSU plugin has been deprecated and will be removed in afuture release.

• 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.

• Support for plumgrid plugin has been deprecated and will be removed in afuture release.

• The neutron::agents::l3::gateway_external_network_id parameter has beendeprecated and has no effect.