Victoria Series Release Notes

17.7.0-4

New Features

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

17.7.0

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

  • The new neutron::keystone::authtoken::service_type parameter has been added to configure the service_type parameter in authtoken middleware.

  • 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

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

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

17.6.0

New Features

  • 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

  • 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

17.5.0

New Features

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

17.4.0

Deprecation Notes

  • The neutron_api_config type has been deprecated. Use the neutron_api_paste_ini type instead.

  • The neutron::config::api_config parameter has been deprecated and will be removed in a future release. Use the neutron::config::api_paste_ini parameter instead.

17.3.0

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.

17.2.0

New Features

  • The new neutron::server::notifications::http_retries parameter has been added to set number of client retries.

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

  • The new neutron::server::notifications::ironic class has been added to support configuration parameters to enable notifications to ironic.

  • The new server::notifications::nova class has been added to configure parameters 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 and neutron::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_overflow parameters in neutron::server is removed, use the neutron::db class instead.

Deprecation Notes

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

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

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

  • The following parameters in server::notifications class has been deprecated and will be removed in a future release. Use the corresponding parameters in server::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

17.1.0

New Features

  • The new neutron::agent::l3::ovs_integration_bridge parameter was added so that operators can set customized integration bridge name in l3 agent configuration.

Deprecation Notes

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

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

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

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

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