# SOME DESCRIPTIVE TITLE. # Copyright (C) 2015, Neutron Developers # This file is distributed under the same license as the Neutron Release Notes package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Neutron Release Notes \n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2024-05-17 18:41+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../../:341 msgid "" "\"ipv6_pd_enabled\" has been marked as deprecated and marked as " "experimental. To continue using it, deployers have to set to True the " "\"ipv6_pd_enabled\" option in the \"experimental\" section of neutron.conf. " "See `Dibbler project concluded `_." msgstr "" #: ../../:108 stable/2023.2>:98 #: stable/2024.1>:435 msgid "" "\"vlan\" or \"flat\" network types configured in the ML2 configuration " "variable ``tenant_network_types``" msgstr "" #: ../../:142 msgid "10.0.0" msgstr "" #: ../../:121 msgid "10.0.3" msgstr "" #: ../../:83 msgid "10.0.5" msgstr "" #: ../../:5 msgid "10.0.7-88" msgstr "" #: ../../:220 msgid "11.0.0" msgstr "" #: ../../:200 msgid "11.0.2" msgstr "" #: ../../:162 msgid "11.0.3" msgstr "" #: ../../:143 msgid "11.0.5" msgstr "" #: ../../:118 msgid "11.0.6" msgstr "" #: ../../:42 msgid "11.0.7" msgstr "" #: ../../:5 msgid "11.0.8-45" msgstr "" #: ../../:404 msgid "12.0.0" msgstr "" #: ../../:368 msgid "12.0.1" msgstr "" #: ../../:335 msgid "12.0.2" msgstr "" #: ../../:316 msgid "12.0.3" msgstr "" #: ../../:278 msgid "12.0.4" msgstr "" #: ../../:215 msgid "12.0.6" msgstr "" #: ../../:178 msgid "12.1.0" msgstr "" #: ../../:146 msgid "12.1.1" msgstr "" #: ../../:5 msgid "12.1.1-142" msgstr "" #: ../../:394 msgid "13.0.0" msgstr "" #: ../../:376 msgid "13.0.1" msgstr "" #: ../../:313 msgid "13.0.3" msgstr "" #: ../../:239 msgid "13.0.4" msgstr "" #: ../../:198 msgid "13.0.5" msgstr "" #: ../../:176 msgid "13.0.6" msgstr "" #: ../../:128 msgid "13.0.7" msgstr "" #: ../../:5 msgid "13.0.7-119" msgstr "" #: ../../:430 msgid "14.0.0" msgstr "" #: ../../:361 msgid "14.0.2" msgstr "" #: ../../:320 msgid "14.0.3" msgstr "" #: ../../:287 msgid "14.0.4" msgstr "" #: ../../:222 msgid "14.1.0" msgstr "" #: ../../:145 msgid "14.2.0" msgstr "" #: ../../:121 msgid "14.3.0" msgstr "" #: ../../:104 msgid "14.3.1" msgstr "" #: ../../:86 msgid "14.4.0" msgstr "" #: ../../:65 msgid "14.4.1" msgstr "" #: ../../:46 msgid "14.4.2" msgstr "" #: ../../:5 msgid "14.4.2-57" msgstr "" #: ../../:414 msgid "15.0.0" msgstr "" #: ../../:381 msgid "15.0.1" msgstr "" #: ../../:300 msgid "15.0.2" msgstr "" #: ../../:192 msgid "15.1.0" msgstr "" #: ../../:156 msgid "15.2.0" msgstr "" #: ../../:138 msgid "15.3.0" msgstr "" #: ../../:101 msgid "15.3.1" msgstr "" #: ../../:84 msgid "15.3.4" msgstr "" #: ../../:5 msgid "15.3.4-114" msgstr "" #: ../../:320 msgid "16.0.0" msgstr "" #: ../../:253 msgid "16.1.0" msgstr "" #: ../../:235 msgid "16.2.0" msgstr "" #: ../../:200 msgid "16.3.0" msgstr "" #: ../../:182 msgid "16.3.1" msgstr "" #: ../../:158 msgid "16.3.2" msgstr "" #: ../../:131 msgid "16.4.0" msgstr "" #: ../../:114 msgid "16.4.1" msgstr "" #: ../../:5 msgid "16.4.2-138" msgstr "" #: ../../:307 msgid "17.0.0" msgstr "" #: ../../:266 msgid "17.1.0" msgstr "" #: ../../:236 msgid "17.1.1" msgstr "" #: ../../:218 msgid "17.1.2" msgstr "" #: ../../:168 msgid "17.2.0" msgstr "" #: ../../:151 msgid "17.2.1" msgstr "" #: ../../:129 msgid "17.3.0" msgstr "" #: ../../:102 msgid "17.4.0" msgstr "" #: ../../:5 msgid "17.4.1-76" msgstr "" #: ../../:465 msgid "18.0.0" msgstr "" #: ../../:405 msgid "18.1.0" msgstr "" #: ../../:388 msgid "18.1.1" msgstr "" #: ../../:366 msgid "18.2.0" msgstr "" #: ../../:328 msgid "18.3.0" msgstr "" #: ../../:243 msgid "18.6.0" msgstr "" #: ../../:5 msgid "18.6.0-144" msgstr "" #: ../../:445 msgid "19.0.0" msgstr "" #: ../../:429 msgid "19.1.0" msgstr "" #: ../../:385 msgid "19.2.0" msgstr "" #: ../../:368 msgid "19.3.0" msgstr "" #: ../../:267 msgid "19.5.0" msgstr "" #: ../../:200 msgid "19.6.0" msgstr "" #: ../../:148 msgid "19.7.0" msgstr "" #: ../../:5 msgid "19.7.0-79" msgstr "" #: ../../:412 msgid "20.0.0" msgstr "" #: ../../:384 msgid "20.2.0" msgstr "" #: ../../:231 msgid "20.3.0" msgstr "" #: ../../:152 msgid "20.3.1" msgstr "" #: ../../:101 msgid "20.4.0" msgstr "" #: ../../:35 msgid "20.5.0" msgstr "" #: ../../:5 msgid "20.5.0-21" msgstr "" #: ../../:346 msgid "21.0.0" msgstr "" #: ../../:254 msgid "21.1.0" msgstr "" #: ../../:175 msgid "21.1.1" msgstr "" #: ../../:75 msgid "21.2.0" msgstr "" #: ../../:5 msgid "21.2.1" msgstr "" #: ../../:246 msgid "22.0.1" msgstr "" #: ../../:136 msgid "22.1.0" msgstr "" #: ../../:5 msgid "22.1.0-71" msgstr "" #: ../../:153 msgid "23.0.0" msgstr "" #: ../../:325 msgid "23.0.0.0b1" msgstr "" #: ../../:126 msgid "23.1.0" msgstr "" #: ../../:5 msgid "23.1.0-61" msgstr "" #: ../../:22 msgid "24.0.0" msgstr "" #: ../../:5 msgid "24.0.0-3" msgstr "" #: ../../:5 current msgid "24.0.0.0rc1-66" msgstr "" #: ../../:150 msgid "7.0.1" msgstr "" #: ../../:125 msgid "7.0.3" msgstr "" #: ../../:100 msgid "7.0.4" msgstr "" #: ../../:20 msgid "7.1.0" msgstr "" #: ../../:5 msgid "7.2.0" msgstr "" #: ../../:186 msgid "8.0.0" msgstr "" #: ../../:146 msgid "8.1.0" msgstr "" #: ../../:94 msgid "8.2.0" msgstr "" #: ../../:40 msgid "8.3.0" msgstr "" #: ../../:5 msgid "8.4.0" msgstr "" #: ../../:143 msgid "9.0.0" msgstr "" #: ../../:114 msgid "9.1.0" msgstr "" #: ../../:65 msgid "9.2.0" msgstr "" #: ../../:40 msgid "9.4.0" msgstr "" #: ../../:5 msgid "9.4.1" msgstr "" #: ../../:356 msgid "" "A DHCP agent is assigned to an availability zone; the network will be hosted " "by the DHCP agent with availability zone specified by the user." msgstr "" #: ../../:234 stable/2023.2>:514 msgid "" "A ML2/OVN virtual port cannot be bound to a virtual machine. If a port IP " "address is assigned as an allowed address pair into another port, the first " "one is considered a virtual port. If the second port (non-virtual) is bound " "to ML2/OVN, the virtual port cannot be bound to a virtual machine; a virtual " "port is created only to reserve a set of IP addresses to be used by other " "ports. The OVN mechanism driver prevents that a virtual port has a device " "ID; a device ID is provided when the port is being bound." msgstr "" #: ../../:55 stable/rocky>:62 stable/stein>:170 #: stable/train>:261 stable/ussuri>:540 msgid "" "A change was made to the metadata proxy to not allow a user to override " "header values, it will now always insert the correct information and remove " "unnecessary fields before sending requests to the metadata agent. For more " "information, see bug `1865036 `_." msgstr "" #: ../../:433 msgid "" "A compute owned port can have one active binding and many inactive bindings." msgstr "" #: ../../:492 msgid "A floating IP can have many ``port_forwardings``." msgstr "" #: ../../:347 msgid "" "A list of IPv6 addresses for a dhcp-host entry in the dnsmasq DHCP agent " "driver can be configured. This solves problems with failing boot process " "when only one IP address is available. See `#1861032 `_) for details about the issue." msgstr "" #: ../../:480 msgid "" "A new API endpoint /v2.0/network-ip-availabilities that allows an admin to " "quickly get counts of used_ips and total_ips for network(s) is available. " "New endpoint allows filtering by network_id, network_name, tenant_id, and " "ip_version. Response returns network and nested subnet data that includes " "used and total IPs." msgstr "" #: ../../:172 msgid "" "A new API extension ``network-ha`` has been added. This extension adds a new " "field to the network API: \"ha\". This field is not visible and can be " "passed only in POST (create) operations. That will define that this network " "is a high availability (HA) network and will create, in the same database " "transaction, a ``ha_router_networks`` register." msgstr "" #: ../../:537 msgid "" "A new API resource ``address group`` and its CRUD operations are introduced " "to represent a group of IPv4 and IPv6 address blocks. A new option ``--" "remote-address-group`` is added to the ``security group rule create`` " "command to allow network connectivity with a group of address blocks. And " "the backend support is added to the ``openvswitch`` firewall. When IP " "addresses are updated in the address groups, changes will also be reflected " "in the firewall rules of the associated security group rules. For more " "information, see RFE: `1592028 `_" msgstr "" #: ../../:162 msgid "" "A new API which allows a cloud administrator to define their own set of " "security group rules added automatically to every new ``default`` and/or " "custom security group created for projects." msgstr "" #: ../../:433 stable/queens>:532 msgid "" "A new DVR agent mode of ``dvr_no_external`` was added. Changing between this " "mode and ``dvr`` is a disruptive operation to the dataplane." msgstr "" #: ../../:300 stable/queens>:473 msgid "" "A new DVR agent type ``dvr_no_external`` has been introduced with this " "release. This agent type allows the Floating IPs (DNAT/North-South routing) " "to be centralized while the East/West routing is still distributed." msgstr "" #: ../../:52 msgid "" "A new OVN driver Northbound DB column has been added to allow configuring " "gateway port for NAT rule. If the OVN backend supports the `gateway_port` " "column in the Northbound DB NAT table, the gateway port uuid will be " "configured to any floating IP to prevent North/South traffic issues. " "Previously created FIP rules will be updated only once during the " "maintenance task to include the gateway_port reference (if OVN backend " "supports it). In case all FIP entries are already configured no maintenance " "action will be performed." msgstr "" #: ../../:196 stable/2023.2>:443 #: unmaintained/wallaby>:175 unmaintained/xena>:108 unmaintained/yoga>:125 #: unmaintained/zed>:135 msgid "" "A new OVN maintenance method ``remove_duplicated_chassis_registers`` is " "added. This method will periodically check the OVN Southbound \"Chassis\" " "and \"Chassis_Private\" tables looking for duplicated registers. The older " "ones (based on the \"Chassis_Private.nb_cfg_timestamp\" value) will be " "removed when more than one register has the same hostname, that should be " "unique." msgstr "" #: ../../:344 msgid "" "A new ``network_link_prefix`` configuration option is introduced that allows " "to alter the domain returned in the URLs included in the API responses. It " "behaves the same way as the ``compute_link_prefix`` and " "``glance_link_prefix`` options do for Nova and Glance." msgstr "" #: ../../:229 stable/queens>:418 msgid "" "A new agent_mode(``dvr_no_external``) for DVR routers has been added to " "allow the server to configure Floating IPs associated with DVR at the " "centralized node." msgstr "" #: ../../:571 msgid "A new attribute ``qos_policy_id`` is added to the L3 router gateway." msgstr "" #: ../../:14 stable/pike>:127 stable/queens>:287 #: stable/rocky>:499 msgid "" "A new config option ``bridge_mac_table_size`` has been added for Neutron OVS " "agent. This value will be set on every Open vSwitch bridge managed by the " "openvswitch-neutron-agent in ``other_config:mac-table-size`` column in " "ovsdb. Default value for this new option is set to 50000 and it should be " "enough for most systems. More details about this option can be found in " "`Open vSwitch documentation `_ For more information see bug `1775797 " "`_." msgstr "" #: ../../:82 msgid "" "A new config option ``enable_signals`` has been added to neutron.conf to " "control whether neutron-server registers signal handlers or not (like " "SIGTERM, etc). The default value for this new option is True to mimic the " "original behavior of registering signal handlers. The recommendation is to " "set this option to False when neutron-server is running behind a WSGI " "server, because in that situation the signals are taken over by the WSGI " "server and neutron will print a stack trace letting us know that signals " "cannot be registered." msgstr "" #: ../../:557 msgid "" "A new config option ``resync_throttle`` has been added for Neutron DHCP " "agent. This new option allows to throttle the number of resync state events " "between the local DHCP state and Neutron to only once per " "``resync_throttle`` seconds. Default value for this new option is set to 1 " "and it should be configured per a user's specific scenario, i.e. how " "responsive the user would like his/her system to be for those DHCP resync " "state events. The option is introduced together with the event driven " "periodic task for DHCP agents. This enhances the agent with a faster " "reaction on the resync request but ensuring a minimum interval taken between " "them to avoid too frequent resyncing. For more information see bug `1780370 " "`_." msgstr "" #: ../../:132 stable/rocky>:168 stable/stein>:279 #: stable/train>:661 msgid "" "A new config option, ``host_dvr_for_dhcp``, was added to neutron.conf for " "DVR to determine whether to host the DVR local router to the scheduled DHCP " "node(s)." msgstr "" #: ../../:185 stable/stein>:307 stable/train>:401 #: stable/ussuri>:667 msgid "" "A new config option, ``radvd_user``, was added to l3_agent.ini for the L3 " "agent. This option defines the username passed to radvd, used to drop \"root" "\" privileges and change user ID to username and group ID to the primary " "group of the user. If no user specified (by default), the user executing the " "L3 agent will be passed. If \"root\" specified, because radvd is spawned as " "root, no \"username\" parameter will be passed. (For more information see " "bug `1844688 `_.)" msgstr "" #: ../../:14 stable/rocky>:14 stable/stein>:130 #: stable/train>:165 stable/ussuri>:262 unmaintained/victoria>:326 msgid "" "A new configuration option ``http_retries`` was added. This option allows " "configuring the number of times the nova or ironic client should retry on a " "failed HTTP call." msgstr "" #: ../../:522 msgid "" "A new configuration option called ``[ovn]/" "disable_ovn_dhcp_for_baremetal_ports`` has been added to ML2/OVN for IPv4. " "Since PXE booting nodes can be very sensitive depending on the hardware and " "some operators may prefer to use a fully-fledged DHCP server instead of " "OVN's DHCP server this option allows for disabling OVN's built-in DHCP " "server for baremetal ports (vnic type \"baremetal\") when set to True. It " "defaults to False." msgstr "" #: ../../:429 msgid "" "A new configuration option, ``cleanup_on_shutdown``, was added to the L3 " "agent. If set to True the L3 agent will explicitly delete all routers on " "shutdown. For L3 HA routers it includes a graceful shutdown of keepalived " "and the state change monitor, which will allow a faster failover in certain " "conditions. The default value of ``cleanup_on_shutdown`` is False to " "maintain backward compatibility. Setting to True could affect the data plane " "when stopping or restarting the L3 agent." msgstr "" #: ../../:74 msgid "" "A new mechanism has been added to netns_cleanup to kill processes that are " "listening on any port/unix socket within the namespace. This will try to " "kill them gracefully via SIGTERM and, if they don't die, then a SIGKILL will " "be sent to the remaining processes to ensure a proper cleanup." msgstr "" #: ../../:185 msgid "" "A new mechanism has been added to the ``neutron-netns-cleanup`` tool that " "allows to kill processes listening on any ``Unix`` or network socket within " "a namespace. The new mechanism will try to kill those processes gracefully " "using the ``SIGTERM`` signal and, if they refuse to die, then the " "``SIGKILL`` signal will be sent to each remaining process to ensure a proper " "cleanup." msgstr "" #: ../../:495 msgid "" "A new method ``get_router_info`` has been added to ``L3AgentExtensionAPI``." msgstr "" #: ../../:499 msgid "" "A new method ``ha_state_change`` has been added to " "``L3AgentExtensionsManager``." msgstr "" #: ../../:33 stable/queens>:206 stable/rocky>:293 #: stable/stein>:421 stable/train>:677 msgid "" "A new option ``[ovs] of_inactivity_probe`` has been added to allow changing " "the inactivity probe interval when using the OVS ML2 agent with the native " "OpenFlow driver. Operators can increase this if they are experiencing " "OpenFlow timeouts. The default value is 10 seconds." msgstr "" #: ../../:14 stable/mitaka>:74 #: stable/newton>:137 stable/ocata>:237 msgid "" "A new option ``ha_keepalived_state_change_server_threads`` has been added to " "configure the number of concurrent threads spawned for keepalived server " "connection requests. Higher values increase the CPU load on the agent nodes. " "The default value is half of the number of CPUs present on the node. This " "allows operators to tune the number of threads to suit their environment. " "With more threads, simultaneous requests for multiple HA routers state " "change can be handled faster." msgstr "" #: ../../:14 stable/2023.2>:14 stable/2024.1>:93 msgid "" "A new ovn-cms-options option called ``enable-chassis-as-extport-host`` is " "now recognized by ML2/OVN and is used to identify nodes that are eligible " "for scheduling OVN's external ports. This feature is backward compatible and " "if no nodes contain this new option the external ports will continue to be " "scheduled using the ``enable-chassis-as-gw`` option as before. This change " "also introduces a limit to the number of members for each HA Chassis Group " "to 5, matching the limit of gateway router port replicas. This is because " "OVN uses BFD to monitor the connectivity of each member and having an " "unlimited number of members could potentially put a lot of stress in OVN." msgstr "" #: ../../:455 msgid "" "A new parameter ``router_factory`` has been added to ``neutron.agent.l3." "L3AgentExtensionAPI``. Developers can register ``neutron.agent.l3.agent." "RouterInfo`` class and delegate it for ``RouterInfo`` creation." msgstr "" #: ../../:67 msgid "" "A new policy rule check ``rule_default_sg`` has been added. This rule allows " "to check if a security group rule belongs or not to the project default " "security group. The administrator can override the rule creation and rule " "deletion, disallowing a non-privileged user from these actions." msgstr "" #: ../../:496 msgid "" "A new quota driver is added: ``DbQuotaNoLockDriver``. This driver, unlike " "``DbQuotaDriver``, does not create a unique lock per (resource, project_id). " "That may lead to a database deadlock state if the number of server requests " "exceeds the number of resolved resource creations, as described in " "`LP#1926787 `_. This driver " "relays on the database transactionality isolation and counts the number of " "used and reserved resources and, if available, creates the new resource " "reservations in one single database transaction." msgstr "" #: ../../:179 msgid "" "A new rule has been added to the API that allows for tagging traffic with " "DSCP values. This is currently supported by the Open vSwitch QoS driver." msgstr "" #: ../../:260 unmaintained/xena>:290 #: unmaintained/yoga>:262 unmaintained/zed>:474 msgid "" "A new script to remove the duplicated port bindings was added. This script " "will list all ``ml2_port_bindings`` records in the database, finding those " "ones with the same port ID. Then the script removes those ones with " "status=INACTIVE. This script is useful to remove those leftovers that remain " "in the database after a failed live migration. It is important to remark " "that this script should not be executed during any live migration process." msgstr "" #: ../../:495 msgid "" "A new subnet of type ``network:routed`` has been added. If such a subnet is " "used, the IPs of that subnet will be advertized with BGP over a provider " "network, which itself can use segments. This basically achieves a BGP-to-the-" "rack feature, where the L2 connectivity can be confined to a rack only, and " "all external routing is done by the switches, using BGP. In this mode, it is " "still possible to use VXLAN connectivity between the compute nodes, and only " "floating IPs and router gateways are using BGP routing." msgstr "" #: ../../:381 msgid "" "A new table 'subnet_service_types' has been added to cater for this feature. " "It uses the ID field from the 'subnets' table as a foreign key." msgstr "" #: ../../:566 msgid "" "A new vnic type ``vdpa`` has been added to allow requesting port that " "utilize a vHost-vDPA offload. The ML2/OVS and ML2/OVN mech drivers now have " "support for the vHost-vDPA vnic type. vHost-vDPA is similar to vHost-user or " "kernel vhost offload but utilizes the newly added vDPA bus introduced in the " "Linux 5.7 kernel. vDPA interface can be implemented in software or hardware, " "when implemented in hardware they provide equivalent performance to SR-IOV " "or hardware offloaded OVS while providing two main advantages over both SR-" "IOV and hardware offloaded OVS. Unlike the alternatives, vHost-vDPA enables " "live migration of instance transparently and provides a standard virtio-net " "interface to the guest avoiding the need to install vendor specific drivers " "in the guest." msgstr "" #: ../../:482 msgid "" "A notifier for the Openstack Baremetal service (``ironic``) is introduced. " "When enabled notifications are sent to the Baremetal service on relevant " "resource events/changes. By default notifications to the Baremetal service " "is *disabled*. To *enable* notifications to the Baremetal service set " "``[ironic]/enable_notifications`` to ``True`` in the Networking service " "configuration (``neutron.conf``)." msgstr "" #: ../../:600 msgid "" "A previous bug fix changed the behaviour of the DHCP agent to use a " "network's ``dns_domain`` as the search path provided to instances overriding " "the ``dns_domain`` configuration option used by both the DHCP agent and the " "main server process when generate port DNS assignments. This broke the " "original design intent of the ``dns_domain`` attribute of a network which " "was for integration with external DNS systems such as Designate rather than " "for use in Neutron's internal DNS support. This incorrect change in " "behaviour has now been reverted - the DHCP agent will only ever use the " "``dns_domain`` configuration option." msgstr "" #: ../../:387 msgid "" "A previous change to set neutron-server child process names also modified " "neutron agent ones. This can impact monitoring systems relying on /proc/PID/" "environ formatting or `ps -e` output. Now neutron agents all have process " "names formatted this way (showing both an old style process name and full " "process name visible in recent releases) ``neutron-agent-name`` (``original " "process name including interpreter``)" msgstr "" #: ../../:495 msgid "" "A security group rule added for the entire port range, for example, TCP " "ports 1-65535, is not optimal for backends that implement the rule. Rules " "like this will now automatically be converted to apply to the procotol " "itself, in other words, all TCP - the port ranges will be ignored. See bug " "`1848213 `_ for more " "details." msgstr "" #: ../../:104 msgid "" "A special case has been added to allow the creation of DHCP ports on Service " "Subnets that do not have the service type \"network:dhcp\", provided that " "the subnet has 'enable_dhcp' set to 'True'. This fixes the recurring error " "seen when neutron attempts to automatically create a DHCP port on a dhcp-" "enabled subnet after the subnet is created. See bug report `1636963 `_ for more details." msgstr "" #: ../../:557 msgid "" "A unique constraint for (network_id, network_type, physical_network) is " "added to the networksegments table. This was done to prevent race conditions " "on dynamic segment allocation. Operators having networks with multiple " "segments (e.g. when using hierarchical portbinding) should check that this " "constraint is not violated with the included upgrade-check." msgstr "" #: ../../:490 msgid "" "A user cannot create ``port_forwardings`` for a floating IP that is already " "associated with a Neutron port." msgstr "" #: ../../:365 msgid "" "A version of dnsmasq that includes dhcp_release6 should be installed on " "systems running the DHCP agent. Failure to do this could cause DHCPv6 " "stateful addressing to not function properly." msgstr "" #: ../../:397 msgid "API sorting and pagination features are now enabled by default." msgstr "" #: ../../:576 msgid "" "API users might observe that requests that received a successful response " "now receive a failure response. If they encounter such experience, they are " "suggested to confirm if the API extension ``filter-validation`` is present " "and validate filter parameters in their requests." msgstr "" #: ../../:355 msgid "" "Absence of dhcp_release6 when DHCPv6 stateful addressing is in use may lead " "to bug `1521666 `_. Neutron " "supports dhcp_release6 now, but if the tool is not available this leads to " "increased log warnings. Read bug report `1622002 `_ for more details." msgstr "" #: ../../:33 stable/rocky>:40 stable/stein>:154 #: stable/train>:245 stable/ussuri>:284 unmaintained/victoria>:457 msgid "" "Abstract method ``plug_new`` from the neutron.agent.linux.interface." "LinuxInterfaceDriver class now accepts an optional parameter ``link_up``. " "Usage of this method, which takes from 5 to 9 positional arguments, without " "``link_up`` is now deprecated and will not be possible starting in the W " "release. Third-party drivers which inherit from this base class should " "update the implementation of their ``plug_new`` method." msgstr "" #: ../../:629 msgid "" "Abstract method ``plug_new`` from the neutron.agent.linux.interface." "LinuxInterfaceDriver now has additional positional argument ``link_up``. " "Usage of this method without ``link_up`` is now not possible. Third-party " "drivers which inherit from this base class now have to update the " "implementation of their ``plug_new`` method." msgstr "" #: ../../:66 stable/mitaka>:564 msgid "" "Actions that create virtual network interfaces on an existing network with " "the 'mtu' attribute containing a value greater than zero could cause issues " "for network traffic traversing existing and new virtual network interfaces." msgstr "" #: ../../:59 msgid "" "Activation of this feature enables gateway connectivity validation and " "rescheduling of the \"master\" router to another node when connectivity is " "lost. If all routers lose connectivity to the gateways, the election process " "will be repeated round-robin until one of the routers restores its gateway " "connection. In the mean time, all of the routers will be reported as \"master" "\"." msgstr "" #: ../../:277 msgid "" "Add 'default' behaviour to QoS policies Neutron now supports having a " "default QoS policy in a project, assigned automatically to all new networks " "created." msgstr "" #: ../../:430 msgid "" "Add Support for Smart NIC in ML2/OVS mechanism driver, by extending the " "Neutron OVS mechanism driver and Neutron OVS Agent to bind the Neutron port " "for the baremetal host with Smart NIC." msgstr "" #: ../../:440 msgid "Add ``BEFORE_UPDATE`` callback event for router gateway." msgstr "" #: ../../:265 msgid "" "Add ``data_plane_status`` attribute to port resources to represent the " "status of the underlying data plane. This attribute is to be managed by " "entities outside of the Networking service, while the ``status`` attribute " "is managed by the Networking service. Both status attributes are independent " "from one another. Third parties can report via Neutron API issues in the " "underlying data plane affecting connectivity from/to Neutron ports. " "Attribute can take values ``None`` (default), ``ACTIVE`` or ``DOWN``, and is " "readable by users and writable by admins and users granted the ``data-plane-" "integrator`` role. Append ``data_plane_status`` to ``[ml2] " "extension_drivers`` config option to load the extension driver." msgstr "" #: ../../:74 msgid "" "Add ``enable_default_route_bfd`` and ``enable_default_route_ecmp`` " "configuration options which control default behavior for enabling BFD and " "ECMP on default routes for newly created routers. Both configuration " "options have a default value of 'False' and are only supported with the OVN " "driver." msgstr "" #: ../../:435 msgid "" "Add ``request_body`` field to router callback event payloads. The field " "record the origin request body from user." msgstr "" #: ../../:385 stable/stein>:736 msgid "" "Add ``resource_type`` into log object query to distinguish between security " "group and firewall group log objects. For more information see bug `1787119 " "`_." msgstr "" #: ../../:20 stable/ussuri>:27 #: unmaintained/victoria>:21 unmaintained/wallaby>:270 unmaintained/xena>:300 #: unmaintained/yoga>:272 unmaintained/zed>:484 msgid "" "Add ``use_random_fully`` setting to allow an operator to disable the " "iptables random-fully property on an iptable rules." msgstr "" #: ../../:667 msgid "" "Add a generic coordination lock mechanism for various scenarios. This " "decorator allows flexible lock name with parameters and names of underlying " "functions. And in order to achive backward compatibility with python2.7 " "several functions was copied from the old version of python inspect. Once " "python2.7 is retired, we can drop such duplication." msgstr "" #: ../../:489 msgid "" "Add a new config option in DEFAULT section named ``my_ip``. This new config " "option will be set by default to the local IPv4 configured to reach the " "default gateway. This new setting might be useful for operators that need to " "configure this IP in another part of their config (like OVS/local_ip) " "without relying on any external templating system." msgstr "" #: ../../:498 msgid "" "Add a new config option in DEFAULT section named ``my_ipv6``. This new " "config option will be set by default to the local IPv6 configured to reach " "the default gateway. This new setting might be useful for operators that " "need to configure this IP in another part of their config (like OVS/" "local_ip) without relying on any external templating system." msgstr "" #: ../../:173 msgid "" "Add a new configuration section, ``[placement]``, with two new options that " "allow to make ``segments`` plugin to use the ``Compute`` placement ReST API. " "This API allows to influence node placement of instances based on " "availability of IPv4 addresses in routed networks. The first option, " "`region_name`, indicates the placement region to use. This option is useful " "if keystone manages more than one region. The second option, " "`endpoint_type`, determines the type of a placement endpoint to use. This " "endpoint will be looked up in the keystone catalog and should be one of " "``public``, ``internal`` or ``admin``." msgstr "" #: ../../:374 msgid "Add a new field ``description`` to the ``PortForwarding`` resource." msgstr "" #: ../../:118 stable/rocky>:106 stable/stein>:212 #: stable/train>:636 msgid "" "Add a new match rule based on physical VLAN tag for OpenFlow firewall " "traffic identifying mechanism to the TRANSIENT table. This fixes the " "distributed router east-west traffic between VLAN type networks. For more " "information, see bug `1831534 `_." msgstr "" #: ../../:543 msgid "" "Add an API extension ``filter-validation`` to indicate this new API " "behavior. This extension can be disabled by operators via a config option." msgstr "" #: ../../:452 msgid "" "Add attribute ``port_details`` to floating IP. The value of this attribute " "contains information of the associated port." msgstr "" #: ../../:524 msgid "" "Add config option ``rpc_response_max_timeout`` to configure the maximum time " "waiting for an RPC response." msgstr "" #: ../../:444 msgid "" "Add derived attributes to the network to tell users which address scopes the " "network is in." msgstr "" #: ../../:245 msgid "" "Add description field to security group rules, networks, ports, routers, " "floating IPs, and subnet pools." msgstr "" #: ../../:586 msgid "" "Add get_standard_device_mappings to SriovNicSwitchMechanismDriver and " "OpenvswitchMechanismDriver so they can return the interface or bridge " "mappings in a standard way. The common format is a dict like: " "{'physnet_name': ['device_or_bridge_1', 'device_or_bridge_2']}." msgstr "" #: ../../:164 msgid "Add ip_allocation attribute to port resources" msgstr "" #: ../../:650 msgid "Add log file for ``neutron-keepalived-state-change`` daemon." msgstr "" #: ../../:285 msgid "Add new VNIC type for SR-IOV physical functions." msgstr "" #: ../../:800 msgid "" "Add new configuration group ``ovs_driver`` and new configuration option " "under it ``vnic_type_blacklist``, to make the previously hardcoded " "``supported_vnic_types`` parameter of the OpenvswitchMechanismDriver " "configurable. The ``vnic_types`` listed in the blacklist will be removed " "from the supported_vnic_types list." msgstr "" #: ../../:809 msgid "" "Add new configuration group ``sriov_driver`` and new configuration option " "under it ``vnic_type_blacklist``, to make the previously hardcoded " "``supported_vnic_types`` parameter of the SriovNicSwitchMechanismDriver " "configurable. The ``vnic_types`` listed in the blacklist will be removed " "from the supported_vnic_types list." msgstr "" #: ../../:20 stable/rocky>:20 stable/stein>:136 #: stable/train>:171 stable/ussuri>:378 msgid "" "Add new configuration option ``igmp_snooping_enable``. New option is in " "``OVS`` config section and is used by openvswitch agent. This option is used " "to enable support for Internet Group Management Protocol (IGMP) in " "integration bridge." msgstr "" #: ../../:439 msgid "Add new tool ``neutron-status upgrade check``." msgstr "" #: ../../:103 stable/newton>:152 msgid "" "Add options to designate external dns driver of neutron for SSL based " "connections. This makes it possible to use neutron with designate in " "scenario where endpoints are SSL based. Users can specify to skip cert " "validation or specify path to a valid cert in [designate] section of neutron." "conf file." msgstr "" #: ../../:548 msgid "Add popular IP protocols to security group code." msgstr "" #: ../../:230 msgid "" "Add popular IP protocols to the security group code. End-users can specify " "protocol names instead of protocol numbers in both RESTful API and python-" "neutronclient CLI." msgstr "" #: ../../:137 stable/stein>:248 stable/train>:585 msgid "" "Add sort-keys validation logic to method ``get_sorts`` in ``neutron.api." "api_common``. See the link below for more: https://bugs.launchpad.net/" "neutron/+bug/1659175" msgstr "" #: ../../:460 msgid "" "Add support for VNIC type ``remote-managed`` in OVN. The OVN driver can now " "bind remote managed ports to SmartNIC DPUs. SmartNIC DPU portbinding " "requires OVN version 21.12 or above, compiled with OVN VIF version 21.12 or " "above." msgstr "" #: ../../:20 unmaintained/victoria>:14 #: unmaintained/wallaby>:549 msgid "" "Add support for deleting ML2/OVN agents. Previously, deleting an agent would " "return a Bad Request error. In addition to deleting the agent, this change " "also drastically improves the scalability of the ML2/OVN agent handling code." msgstr "" #: ../../:533 msgid "" "Add support for filtering attributes with value as empty string. A shim " "extension is added to indicate if this feature is supported." msgstr "" #: ../../:473 msgid "" "Add support for listing floating ip pools (subnets) in L3 plugin. A new API " "resource ``floatingip-pools`` is introduced. This API endpoint can return a " "list of floating ip pools which are essentially mappings between network " "UUIDs and subnet CIDRs. Users can use this API to find out the pool to " "create the floating IPs." msgstr "" #: ../../:376 msgid "" "Add support for port ranges in the port forwarding rules. The supported " "ranges are N:M with N <= M. Also, the ranges of internal and external ports " "relation must be: internal range = external range or internal range = 1." msgstr "" #: ../../:457 msgid "" "Add support for setting the ``segment_id`` for an existing subnet. This " "enables users to convert a non-routed network with no subnet/segment " "association to a routed one. It is only possible to do this migration if " "both of the following conditions are met - the current ``segment_id`` is " "``None`` and the network contains a single segment and subnet." msgstr "" #: ../../:250 msgid "Add tag mechanism for network resources" msgstr "" #: ../../:421 msgid "" "Add the shared field to security group API responses and support using " "shared as a query filter. For more information see bug `1942615 `_." msgstr "" #: ../../:412 msgid "" "Add timestamp fields 'created_at', 'updated_at' into neutron core resources " "like network, subnet, port and subnetpool." msgstr "" #: ../../:653 msgid "" "Added QoS support for direct ports in neutron. The support requires Open " "vSwitch 2.11.0 or newer and is based on Linux kernel 5.4.0 or newer. [`bug " "1843165 `_]." msgstr "" #: ../../:526 msgid "" "Added ``qos-pps-minimum-rule-alias`` API extension to enable GET, PUT and " "DELETE operations on QoS minimum packet rate rule without specifying policy " "ID." msgstr "" #: ../../:542 msgid "" "Added a check to verify if all rows of ``ml2_port_bindings`` table in the DB " "are using the new format for ``profile`` column. This check is part of " "upgrade check, that can be executed with ``neutron-status upgrade check`` " "command. If some rows are using obsolete format, they can be sanitized with " "a script that can be executed with ``neutron-sanitize-port-binding-profile-" "allocation`` command." msgstr "" #: ../../:364 msgid "" "Added a new OVN Neutron Agent extension: QoS for hardware offloaded ports. " "This extension will enforce the minimum and maximum bandwidth egress QoS " "rules for ports with hardware offload (DevLink ports). This extension uses " "the \"ip-link\" commands to set the \"ceil\" and \"rate\" parameters on the " "corresponding virtual functions." msgstr "" #: ../../:465 msgid "" "Added a new OVS agent extension ``dhcp`` to support distributed DHCP for VMs " "in compute nodes directly. To enable this just set ``extensions=dhcp`` to " "OVS agent config file under ``[agent]`` section. We also add a new config " "section ``[dhcp]`` which has options ``enable_ipv6 = True/False`` for " "indicating whether enable the DHCPv6 for VM ports." msgstr "" #: ../../:356 msgid "" "Added a new agent: the OVN Agent. This new agent will run on a compute or a " "controller node using OVN as network backend, similar to other ML2 mechanism " "drivers as ML2/OVS or ML2/SRIOV. This new agent will perform those actions " "that the ovn-controller service cannot execute. The agent functionality will " "be plugable and added via configuration knob." msgstr "" #: ../../:700 msgid "" "Added a new config option ``enable_traditional_dhcp`` for neutron server, if " "it is set to False, neutron server will disable DHCP provisioning block, " "DHCP scheduler API extension, network scheduling mechanism and DHCP RPC/" "notification. This option can be used with the ``dhcp`` extension of the OVS " "agent to enable distributed DHCP, or for a deployment which needs to disable " "the DHCP agent related functions permanently." msgstr "" #: ../../:432 msgid "" "Added a new configuration variable, in ``[OVS]`` section, to control the OVS " "OpenFlow rule processing operations when using the OVS native firewall " "driver (``securitygroup.firewall_driver=openvswitch``):" msgstr "" #: ../../:130 stable/2023.2>:120 #: stable/2024.1>:457 unmaintained/yoga>:29 unmaintained/zed>:69 msgid "" "Added extension ``subnetpool-prefix-ops`` to the ML2/OVN mechanism driver." msgstr "" #: ../../:531 msgid "" "Added new API extension to QoS service plugin to support CRUD actions for " "packet rate limit (packet per second) rule in Neutron server side." msgstr "" #: ../../:537 msgid "" "Added new API extension to QoS service plugin to support CRUD operations for " "minimum packet rate rule in Neutron server." msgstr "" #: ../../:448 msgid "" "Added new ``unknown`` state for HA routers. Sometimes l3 agents may not be " "able to update health status to Neutron server due to communication issues. " "During that time the server may not know whether HA routers hosted by that " "agent are active or standby." msgstr "" #: ../../:490 msgid "" "Added port-resource-request-groups API extension, that provides support for " "the new format of port's ``resource_request`` and ``binding:profile." "allocation`` attributes. The new format allows to request multiple groups of " "resources and traits from the same RP subtree." msgstr "" #: ../../:402 msgid "" "Added support for QoS minimum bandwidth rules (egress only) in ML2/OVN. OVN " "supports setting these rule types in the logical switch ports since `release " "22.06.0 `_." msgstr "" #: ../../:444 msgid "" "Added support for a new stateful-security-group api extension that " "implements stateless security groups for the iptables drivers." msgstr "" #: ../../:370 stable/train>:423 msgid "" "Added support for custom scripts used to kill external processes managed by " "neutron agents, such as ``dnsmasq`` or ``keepalived``. Such custom scripts, " "if defined, will be used instead default ``kill`` command to kill such " "external processes." msgstr "" #: ../../:316 msgid "Added support for floating IPs port forwarding in OVN." msgstr "" #: ../../:413 msgid "Added support for floating IPs port forwarding." msgstr "" #: ../../:444 msgid "" "Added support for network segment range management. This introduces the " "ability for administrators to control the segment ranges globally or on a " "per-tenant basis via the Neutron API." msgstr "" #: ../../:272 unmaintained/victoria>:381 msgid "" "Added support for router availability zones in OVN. The OVN driver can now " "read from the router's availability_zone_hints field and schedule router " "ports accordingly with the given availability zones." msgstr "" #: ../../:420 msgid "" "Added support for router gateway IP QoS in OVN backend. The L3 OVN router " "plugin now can apply router QoS policy rules on the router gateway port." msgstr "" #: ../../:127 msgid "" "Added support for the ``external-gateway-multihoming`` API extension. The L3 " "service plugins supporting it can now create multiple gateway ports per " "router. At the time of writing this is limited to the OVN L3 plugin." msgstr "" #: ../../:506 msgid "Added support for the ``vlan-transparent`` in the OVN mechanism driver." msgstr "" #: ../../:528 msgid "" "Added support in SR-IOV agent for ``accelerator-direct`` VNIC type. This " "type represents a port that supports any kind of hardware acceleration and " "is provided by Cyborg (https://wiki.openstack.org/wiki/Cyborg). `RFE: " "1909100 `_. ``accelerator-" "direct-physical`` is still not supported." msgstr "" #: ../../:359 msgid "Added support to create stateless security groups." msgstr "" #: ../../:227 stable/2023.2>:507 #: stable/ussuri>:101 unmaintained/victoria>:93 unmaintained/wallaby>:224 #: unmaintained/xena>:139 unmaintained/yoga>:92 unmaintained/zed>:166 msgid "" "Added the missing extension ``uplink-status-propagation`` to the ML2/OVN " "mechanism driver. This extension is used by the ML2/SR-IOV mechanism driver, " "that could be loaded with ML2/OVN. Now it is possible to create ports with " "the \"uplink-status-propagation\" flag defined." msgstr "" #: ../../:175 msgid "" "Added the tags policies for the following resources: network, subnet, port, " "router, floating IP, network segment, network segment range, security group " "and security group rule. The policies control the creation, the update and " "the deletion of the resource tags." msgstr "" #: ../../:507 unmaintained/yoga>:452 msgid "" "Added two new API methods to ``QuotaDriverAPI`` class. " "``get_resource_usage`` returns the current resource usage. " "``quota_limit_check`` checks the current resource usage of several resources " "against a set of deltas (a dictionary of resource names and resource " "counters)." msgstr "" #: ../../:310 msgid "Adding MacVtap ML2 driver and L2 Agent as new vswitch choice" msgstr "" #: ../../:111 stable/pike>:190 stable/queens>:598 msgid "" "Adding security group rules by protocol number is documented, but somehow " "was broken without being noticed in one of the last couple of releases. " "This is now fixed. For more information see bug `1716045 `_." msgstr "" #: ../../:612 msgid "" "Address group now has standard attributes. In the alembic migration, the " "original ``description`` column of ``address_groups`` is dropped after data " "migrated to the ``standardattributes`` table. The ``description`` field is " "also removed from the address group object and DB model. This change " "requires a restart of ``neutron-server`` service after the DB migration " "otherwise users will get server errors when making calls to address group " "APIs." msgstr "" #: ../../:334 unmaintained/wallaby>:14 #: unmaintained/xena>:276 unmaintained/yoga>:240 unmaintained/zed>:263 msgid "" "Address scope is now added to all OVN LSP port registers in the northbound. " "Northd then writes the address scope from the northbound to the southbound " "so it can be used there by the ovn-bgp-agent." msgstr "" #: ../../:369 msgid "" "Address scope is now supported via the network RBAC mechanism. Please refer " "to the admin guide for further details." msgstr "" #: ../../:335 msgid "" "Address scopes and subnetpools can now be shared with other tenants using " "the Role Based Access Control (``RBAC``) mechanism." msgstr "" #: ../../:513 msgid "" "Adds api extenstion ``port-mac-address-regenerate``. When passing " "``'null'`` (``None``) as the ``mac_address`` on port update a converter will " "generate a new mac address that will be assigned to the port. `RFE: " "#1768690 `_." msgstr "" #: ../../:620 msgid "" "Adds Floating IP port forwarding table column ``protocol`` to the uniq " "constraints. In one expand script, we drop the original uniq constraints " "first, then create the new uniq constraints with column ``protocol``." msgstr "" #: ../../:221 stable/2023.2>:483 #: unmaintained/wallaby>:218 unmaintained/xena>:133 unmaintained/yoga>:86 #: unmaintained/zed>:160 msgid "" "Adds a maintenance task that runs once a day and is responsible for cleaning " "up Hash Ring nodes that haven't been updated in 5 days or more. See LP " "#2033281 for more information." msgstr "" #: ../../:520 msgid "" "Adds host routes for subnets on the same network when using routed networks. " "Static routes will be configured for subnets associated with other segments " "on the same network. This ensures that traffic within an L3 routed network " "stays within the network even when the default route is on a different " "interface." msgstr "" #: ../../:439 msgid "" "Adds support for IGMP snooping (Multicast) in the OVN driver. Defaults to " "False. IGMP snooping requires OVN version 2.12 or above." msgstr "" #: ../../:515 msgid "" "Adds support for Network Availability Zones to the OVN driver. When Network " "AZ is used, OVN's \"external\" ports will now be scheduled onto nodes " "belonging to the AZs specified in the network that the port belongs to. This " "feature also removes the limitation where all \"external\" ports were part " "of to a single HA Chassis Group (meaning they would all be bond to a single " "host) now the \"external\" ports will be better distributed across different " "hosts." msgstr "" #: ../../:491 msgid "" "Adds support for OVS DPDK port representors, a direct port on a netdev " "datapath is considered a DPDK representor port." msgstr "" #: ../../:201 stable/ussuri>:394 msgid "" "Adds support for configuring a list of IPv6 addresses for a dhcp-host entry " "in the dnsmasq DHCP agent driver. For a port with multiple IPv6 fixed-ips in " "the same subnet a single dhcp-host entry including all the addresses are " "written to the dnsmasq dhcp-hostsfile." msgstr "" #: ../../:267 stable/stein>:775 msgid "" "Adds the ``router`` service plugin to the ``port_forwarding`` service plugin " "required list. For more info see https://bugs.launchpad.net/neutron/" "+bug/1809238" msgstr "" #: ../../:263 stable/2023.2>:239 #: unmaintained/victoria>:40 unmaintained/wallaby>:38 unmaintained/xena>:32 #: unmaintained/yoga>:169 unmaintained/zed>:192 msgid "" "Administrators may observe the IPv6 metadata address in \"dadfailed\" state " "in the DHCP namespace for this reason, which is only an indication it is not " "highly available. Until a redesign is made to the isolated metadata service " "there is not a better deployment option. See `bug 1953165 `_ for information." msgstr "" #: ../../:252 unmaintained/xena>:282 #: unmaintained/yoga>:246 unmaintained/zed>:383 msgid "" "After the port is considered as provisioned, the Nova port binding update " "could have not been received, leaving the port as not bound. Now the port " "provisioning method has an active wait that will retry several times, " "waiting for the port binding update. If received, the port status will be " "set as active if the admin state flag is set." msgstr "" #: ../../:253 stable/pike>:461 msgid "" "After upgrade, a macvtap agent without physical_interface_mappings " "configured can not be started. Specify a valid mapping to be able to start " "and use the macvtap agent." msgstr "" #: ../../:377 msgid "" "All existing ports are considered to have 'immediate' IP allocation. Any " "ports that do not have this attribute should also be considered to have " "immediate IP allocation." msgstr "" #: ../../:88 stable/newton>:548 msgid "Allow SR-IOV agent to run with 0 vfs" msgstr "" #: ../../:440 msgid "" "Allow configuration of DHCP renewal (T1) and rebinding (T2) timers in " "``neutron-dhcp-agent``. By allowing these timers to be set (options 58 and " "59 as per RFC2132) in ``dnsmasq`` it allows users to change other " "parameters, like MTU, on instances without having to wait for the lease time " "to expire. The advantage of changing T1 over the lease time is that if the " "DHCP server becomes unreachable within the lease time, instances will not " "drop their IP addresses and it will not cause a dataplane disruption." msgstr "" #: ../../:424 msgid "Allow non-admin users to define \"external\" extra-routes." msgstr "" #: ../../:251 msgid "" "Allow to configure ``router`` service plugin without ``dvr`` API extension " "loaded and exposed. To achieve that, set the new ``enable_dvr`` option to " "``False`` in ``neutron.conf`` file." msgstr "" #: ../../:29 stable/mitaka>:265 msgid "" "Allowed address pairs can now be cleared by passing None in addition to an " "empty list. This is to make it possible to use the --action=clear option " "with the neutron client. neutron port-update --allowed-address-pairs " "action=clear" msgstr "" #: ../../:507 msgid "" "Allows the unbound port Floating IPs to be configured properly with DVR " "routers irrespective of its device_owner." msgstr "" #: ../../:360 msgid "" "An L3 agent is assigned to an availability zone; the router will be hosted " "by the L3 agent with availability zone specified by the user. This supports " "the use of availability zones with HA routers. DVR isn't supported now " "because L3HA and DVR integration isn't finished." msgstr "" #: ../../:134 msgid "" "An OVS agent configured to run in DVR mode will fail in case it can't get " "proper DVR configs from server on start. Such agent will no longer fallback " "to non-DVR mode since it may lead to inconsistency in the DVR enabled " "cluster as Neutron server does not really distinguish DVR and non-DVR OVS " "agents." msgstr "" #: ../../:295 msgid "" "An OVS agent configured to run in DVR mode will fail to start if it cannot " "get proper DVR configuration values from the server on start-up. The agent " "will no longer fallback to non-DVR mode, since it may lead to inconsistency " "in the DVR-enabled cluster as the Neutron server does not distinguish " "between DVR and non-DVR OVS agents." msgstr "" #: ../../:416 msgid "" "And support for querying these resources by changed-since, it will return " "the resources changed after the specfic time string like YYYY-MM-DDTHH:MM:SS" msgstr "" #: ../../:432 msgid "" "Announcement of floating IP host routes via BGP using the centralized " "Neutron router gateway port as the next-hop" msgstr "" #: ../../:436 msgid "" "Announcement of floating IP host routes via BGP using the floating IP agent " "gateway as the next-hop when the floating IP is associated through a " "distributed router" msgstr "" #: ../../:260 msgid "" "Announcement of tenant prefixes and host routes for floating IP's via BGP is " "supported" msgstr "" #: ../../:428 msgid "" "Announcement of tenant subnets via BGP using centralized Neutron router " "gateway port as the next-hop" msgstr "" #: ../../:277 msgid "" "Any \"Logical_Router_Port\" with a gateway chassis named \"neutron-ovn-" "invalid-chassis\" will be updated and this chassis will be deleted. An " "unhosted (unbound) \"Logical_Router_Port\" will have no gateway assigned." msgstr "" #: ../../:646 msgid "" "Any L3 agent extension must inherit from ``neutron_lib.agent.l3_extension." "L3AgentExtension``. The ``L3AgentExtensionsManager`` makes this check during " "the initial loading. A ``L3ExtensionException`` will be raised if the " "condition is not met." msgstr "" #: ../../:440 msgid "" "As a consequence of the multiple port bindings implementation, the " "``port_binding`` relationship in the SQLAlchemy ``Port`` object has been " "renamed ``port_bindings``. Similarly, the ``binding`` attribute of the " "``Port`` OVO has been renamed ``bindings``." msgstr "" #: ../../:723 msgid "" "As defined in `Migrate from oslo.rootwrap to oslo.privsep `_, all OpenStack proyects should migrate from oslo.rootwrap to " "oslo.privsep because \"oslo.privsep offers a superior security model, faster " "and more secure\". This migration will end with the deprecation and removal " "of oslo.rootwrap from Neutron. To ensure the quality of the Neutron code, " "this migration will be done sequentially in several patches, checking none " "of them breaks the current functionality. In order to easily migrate to " "execute all external commands inside a privsep context, a new input variable " "\"privsep_exec\", that defaults to \"False\", is added to ``neutron.agent." "linux.utils.execute``. That will divert the code to a privsep decorated " "executor. Once the migration finishes, this new input parameter will be " "removed." msgstr "" #: ../../:495 msgid "" "Assigning a new ``QoS policy`` with ``minimum_packet_rate`` rule to an " "``already bound port`` updates the allocation in Placement. ``NOTE``: " "Placement allocation update is not supported if original QoS policy had no " "``minimum_packet_rate`` rule. Changing from direction-less " "``minimum_packet_rate`` rule to a direction-oriented ``minimum_packet_rate`` " "rule is not supported." msgstr "" #: ../../:576 msgid "" "At the moment, only bandwidth limit rules are supported in the QoS polices." msgstr "" #: ../../:582 msgid "" "At the time of writing, Neutron bandwidth booking is not integrated with " "Compute scheduler, which means that minimal bandwidth is not guaranteed but " "provided as best effort." msgstr "" #: ../../:624 msgid "" "Before Mitaka, when a default subnetpool was defined in the configuration, a " "request to create a subnet would fall back to using it if no specific subnet " "pool was specified. This behavior broke the semantics of subnet create " "calls in this scenario and is now considered an API bug. This bug has been " "fixed so that there is no automatic fallback with the presence of a default " "subnet pool. Workflows which depended on this new behavior will have to be " "modified to set the new use_default_subnetpool attribute when creating a " "subnet." msgstr "" #: ../../:481 msgid "" "Before Stein, network segment ranges were configured as an entry in ML2 " "config file ``/etc/neutron/plugins/ml2/ml2_conf.ini`` that was statically " "defined for tenant network allocation and therefore had to be managed as " "part of the host deployment and management. The new ``network-segment-" "range`` API extension has been introduced, which exposes the network segment " "ranges to be administered via API. This allows users with admin privileges " "to be able to dynamically manage the shared and/or tenant specific network " "segment ranges. Standard attributes with tagging support are introduced to " "the new resource. The feature is controlled by the newly-added service " "plugin ``network_segment_range``. A set of ``default`` network segment " "ranges will be created out of the ranges that are defined in the host ML2 " "config file ``/etc/neutron/plugins/ml2/ml2_conf.ini``, such as " "``network_vlan_ranges``, ``vni_ranges`` for ml2_type_vxlan, " "``tunnel_id_ranges`` for ml2_type_gre and ``vni_ranges`` for ml2_type_geneve." msgstr "" #: ../../:463 msgid "Both filter flags are exclusive and not required." msgstr "" #: ../../:617 msgid "" "Both the server and the agent RPC versions have been bumped to 1.9; to " "provide a smooth upgrade transition, the `Upgrade Procedure `_ should be followed, " "upgrading first the servers and then the agents. The agent RPC methods " "returned values are not modified to keep compatibility with other agents " "(Linux Bridge, Open vSwitch). The RPC server side is capable of attending " "calls from agent API < 1.9, in order to provide backwards compatibility. If " "the device PCI slot is not provided, the behavior will be the previous one." msgstr "" #: ../../:556 msgid "" "Bug 1561200 has been fixed by including the timezone with Neutron " "'created_at' and 'updated_at' fields." msgstr "" #: ../../:32 current stable/2023.1>:64 #: stable/2023.1>:156 stable/2023.1>:282 stable/2023.1>:447 stable/2023.2>:52 #: stable/2023.2>:131 stable/2023.2>:356 stable/2024.1>:331 stable/liberty>:72 #: stable/liberty>:140 stable/liberty>:275 stable/mitaka>:30 stable/mitaka>:80 #: stable/mitaka>:166 stable/mitaka>:608 stable/newton>:30 stable/newton>:100 #: stable/newton>:523 stable/ocata>:51 stable/ocata>:102 stable/ocata>:282 #: stable/pike>:68 stable/pike>:148 stable/pike>:181 stable/pike>:205 #: stable/pike>:503 stable/queens>:65 stable/queens>:166 stable/queens>:241 #: stable/queens>:321 stable/queens>:352 stable/queens>:394 stable/queens>:580 #: stable/rocky>:72 stable/rocky>:133 stable/rocky>:218 stable/rocky>:263 #: stable/rocky>:339 stable/rocky>:381 stable/rocky>:590 stable/stein>:70 #: stable/stein>:109 stable/stein>:180 stable/stein>:244 stable/stein>:292 #: stable/stein>:340 stable/stein>:391 stable/stein>:717 stable/train>:56 #: stable/train>:116 stable/train>:180 stable/train>:271 stable/train>:322 #: stable/train>:386 stable/train>:575 stable/ussuri>:51 stable/ussuri>:136 #: stable/ussuri>:187 stable/ussuri>:219 stable/ussuri>:296 stable/ussuri>:558 #: unmaintained/victoria>:61 unmaintained/victoria>:107 #: unmaintained/victoria>:134 unmaintained/victoria>:196 #: unmaintained/victoria>:241 unmaintained/victoria>:285 #: unmaintained/victoria>:486 unmaintained/wallaby>:74 #: unmaintained/wallaby>:309 unmaintained/wallaby>:333 #: unmaintained/wallaby>:371 unmaintained/wallaby>:443 #: unmaintained/wallaby>:666 unmaintained/xena>:51 unmaintained/xena>:168 #: unmaintained/xena>:219 unmaintained/xena>:339 unmaintained/xena>:373 #: unmaintained/xena>:390 unmaintained/xena>:434 unmaintained/xena>:662 #: unmaintained/yoga>:10 unmaintained/yoga>:40 unmaintained/yoga>:121 #: unmaintained/yoga>:188 unmaintained/yoga>:319 unmaintained/yoga>:587 #: unmaintained/zed>:38 unmaintained/zed>:95 unmaintained/zed>:211 #: unmaintained/zed>:300 unmaintained/zed>:554 msgid "Bug Fixes" msgstr "" #: ../../:69 stable/rocky>:76 stable/stein>:184 #: stable/train>:326 stable/ussuri>:562 msgid "" "Bug https://bugs.launchpad.net/neutron/+bug/1732067 described a flooding " "issue on the neutron-ovs-agent integration bridge. And bug https://bugs." "launchpad.net/neutron/+bug/1841622 proposed a solution for it. The accepted " "egress packets will be taken care in the final egress tables (61 when " "openflow firewall is not enabled, table 94 otherwise) with direct output " "flows for unicast traffic with a minimum influence on the existing cloud " "networking. A new config option ``explicitly_egress_direct``, with default " "value False, was added for the aim of distinguishing clouds which are " "running the network node mixed with compute services, upstream neutron CI " "should be an example. In such situation, this ``explicitly_egress_direct`` " "should be set to False, because there are numerous cases from HA routers " "which can not be covered, particularly when you have centralized floating " "IPs running in such mixed hosts. Otherwise, set ``explicitly_egress_direct`` " "to True to avoid the flooding. One more note is if your network nodes are " "for networing services only, we recommand you disable all the security_group " "to get a higher performance." msgstr "" #: ../../:390 msgid "" "By default localnet ports don't learn MAC addresses and therefore they are " "not stored in the FDB table at OVN SB DB. This leads to flooding issues when " "the destination traffic is an unknown IP by OpenStack. In OVN 22.09 the " "option \"localnet_learn_fdb\" was added, enabling those ports to learn MAC " "addresses and store them at the FDB table. Note there is no aging mechanism " "for those MACs, thus this is not enabled by default and needs to be used " "carefully, specially when provider networks are big, and/or performing " "manual cleanup of FDB table over time to avoid scalability issues, until OVN " "implements it at https://bugzilla.redhat.com/show_bug.cgi?id=2179942." msgstr "" #: ../../:390 msgid "" "By default the dnsmasq agent is restarted for every port created, deleted or " "updated. When there are many port changes on the same network it can and " "will take a very long time for all of the port changes to be realised. This " "enhancement adds in a new configuration variable that will enable bulk " "updates. This means that the dnsmasq will only be restarted once in a period " "and not N times. The new option 'bulk_reload_interval' indicates how often " "the agent should be reloaded. The default value is 0 which means that the " "original functionality is the default." msgstr "" #: ../../:420 msgid "" "By default, the DHCP agent provides a network MTU value to instances using " "the corresponding DHCP option if core plugin calculates the value. For ML2 " "plugin, calculation mechanism is enabled by setting [ml2] path_mtu option to " "a value greater than zero." msgstr "" #: ../../:54 stable/newton>:234 msgid "" "By default, the QoS driver for the Open vSwitch and Linuxbridge agents " "calculates the burst value as 80% of the available bandwidth." msgstr "" #: ../../:409 msgid "" "By default, the native interface will have the Ryu controller listen on " "127.0.0.1:6633. The listen address can be configured with of_listen_address " "and of_listen_port options. Ensure that the controller has permission to " "listen at the configured address." msgstr "" #: ../../:487 msgid "" "CRUD operations for ``port_forwardings`` are implemented by a Neutron API " "extension and a service plugin. Please refer to the Neutron API reference " "documentation for details." msgstr "" #: ../../:157 msgid "" "Call dhcp_release6 command line utility when releasing unused IPv6 leases " "for DHCPv6 stateful subnets. dhcp_release6 first appeared in dnsmasq 2.76" msgstr "" #: ../../:194 msgid "" "Certain performance enhancements when deploying Neutron with Ubuntu Trusty " "Tahr were found and should be used. Additionally, utilizing the Octavia " "Neutron-LBaaS driver has some performance considerations to be aware of " "during deployment." msgstr "" #: ../../:67 unmaintained/victoria>:138 #: unmaintained/wallaby>:375 unmaintained/xena>:400 unmaintained/yoga>:591 msgid "" "Changes the API behaviour while using OVN driver to enforce that it's not " "possible to delete all the IPs from a router port. For more info see `bug " "LP#1948457 `_" msgstr "" #: ../../:518 msgid "" "Changing MTU configuration options (``global_physnet_mtu``, " "``physical_network_mtus``, and ``path_mtu``) and restarting ``neutron-" "serer`` no longer affects existing networks' MTUs. Nevertheless, new " "networks will use new option values for MTU calculation. To reflect " "configuration changes for existing networks, one may use the new ``net-mtu-" "writable`` API extension to update ``mtu`` attribute for those networks." msgstr "" #: ../../:638 msgid "" "Class \"PortBindingMixin\" is removed. Last time this class was used in-tree " "was in Kilo release, in \"N1kvNeutronPluginV2\" and \"SdnvePluginV2\" " "classes. No active project is using it anymore. Table \"portbindingports\" " "is dropped from the database; it was used only in \"PortBindingMixin\"." msgstr "" #: ../../:36 current msgid "" "Cleaned non-harmful stack trace errors from DNS integration plugin. This " "prevents the logs from filling with stack traces where error log messages " "would have been sufficient." msgstr "" #: ../../:490 msgid "" "Config option ``agent_type``, which has been deprecated since Mitaka, is now " "removed. Agents should now use hardcoded values for agent type." msgstr "" #: ../../:571 msgid "" "Config option ``allow_overlapping_ips`` is deprecated for removal now. " "Default value for that option is now changed to the ``True`` in the default " "IPAM module of Neutron, as the only reason it was defaulting to ``False`` " "was to keep compatibility with Nova security group code that was removed " "already. The config option itself will removed in the ``Z`` release." msgstr "" #: ../../:438 msgid "" "Config option ``allow_stateless_action_supported`` is deprecated to removal " "and will be removed in ``2023.2 (Bobcat)`` release. This option will not be " "needed anymore as Neutron will not be supported to be run with OVN < 21.06." msgstr "" #: ../../:409 msgid "" "Consider setting ``enable_dvr`` to ``False`` in ``neutron.conf`` file if " "your setup doesn't support DVR. This will make Neutron stop advertising " "support for the ``dvr`` API extension via its ``/v2.0/extensions`` API " "endpoint." msgstr "" #: ../../:254 unmaintained/zed>:412 msgid "" "Core OVN now can set the destination host on the logical switch port during " "a live migration. That allows to prepare the destination host earlier, " "achieving a quicker live migration and a lower downtime during the switch " "between hosts. Neutron includes this information in the port options." msgstr "" #: ../../:270 msgid "Core configuration files are automatically generated." msgstr "" #: ../../:628 msgid "" "Create DVR router namespaces pro-actively on the destination node during " "live migration events. This helps minimize packet loss to floating IP " "traffic." msgstr "" #: ../../:431 msgid "" "Create, update, list, show and activate operations are supported for port " "bindings by the ReST API." msgstr "" #: ../../:394 msgid "" "Creating DVR floating IP namespace on all nodes proactively might consume " "public IP Address, but by using subnet service-types as explained in `the " "networking guide `__ consumers can use the private IPs for floating IP " "agent gateway ports and need not consume any public IP addresses." msgstr "" #: ../../:269 msgid "" "Creating Neutron-LBaaS load balancers in environments without hardware " "virtualization may be slow when using the Octavia driver. This is due to " "QEMU using the TCG accelerator instead of the KVM accelerator in " "environments without hardware virtualization available. We recommend " "enabling hardware virtualization on your compute nodes, or enabling nested " "virtualization when using the Octavia driver inside a virtual environment. " "See `this link explaining devstack with nested KVM `_ for details " "on setting up nested virtualization for DevStack running inside KVM." msgstr "" #: ../../:30 stable/pike>:47 stable/queens>:220 #: stable/rocky>:318 stable/stein>:696 msgid "Critical Issues" msgstr "" #: ../../:513 msgid "" "Currently existing security groups will all be set to stateful during the " "alembic migration." msgstr "" #: ../../:215 msgid "DHCP and L3 Agent scheduling is availability zone aware." msgstr "" #: ../../:329 msgid "" "DHCP schedulers use \"filter_host_with_network_access\" plugin method to " "filter hosts with access to dhcp network. Plugins can overload it to define " "their own filtering logic. In particular, ML2 plugin delegates the filtering " "to mechanism drivers." msgstr "" #: ../../:413 msgid "" "DNS server assignment can now be disabled in replies sent from the DHCP " "agent." msgstr "" #: ../../:436 msgid "" "DSCP can also be inherited from the inner header through a new boolean " "configuration option ``dscp_inherit`` for both openvswitch and linuxbridge. " "If this option is set to true, then the value of ``dscp`` will be ignored." msgstr "" #: ../../:416 msgid "" "Default quotas were bumped for the following resources: networks (from 10 to " "100), subnets (from 10 to 100), ports (from 50 to 500). If you want to stick " "to old values, consider explicitly setting them in the ``neutron.conf`` file." msgstr "" #: ../../:413 msgid "" "Define the 'overlay_ip_version' option and value appropriate for the " "environment. Only required if not using the Default of '4'." msgstr "" #: ../../:649 msgid "" "Deprecate ``keepalived_use_no_track`` config option, as keepalived version " "check is a safe source to decide if ``no_track`` can be used in keepalived " "configuration file." msgstr "" #: ../../:524 msgid "" "Deprecate ``ovs_integration_bridge``. This configuration option is a " "duplicate of ``OVS:integration_bridge``. Currently both options must be the " "same to avoid configuration clashes. Previously used in the DHCP agent. It " "will be removed in next releases." msgstr "" #: ../../:467 msgid "" "Deprecate the use of ``remote_ip_prefix`` in metering label rules, and it " "will be removed in future releases. One should use instead the " "``source_ip_prefix`` and/or ``destination_ip_prefix`` parameters. For more " "details, please refer to the spec: https://review.opendev.org/#/c/744702/." msgstr "" #: ../../:434 stable/2023.2>:332 #: stable/2024.1>:320 stable/mitaka>:582 stable/newton>:90 stable/newton>:460 #: stable/ocata>:263 stable/pike>:467 stable/queens>:29 stable/queens>:545 #: stable/rocky>:36 stable/stein>:150 stable/stein>:665 stable/train>:241 #: stable/train>:548 stable/ussuri>:280 stable/ussuri>:520 #: unmaintained/victoria>:453 unmaintained/wallaby>:636 unmaintained/xena>:631 #: unmaintained/yoga>:567 unmaintained/zed>:541 msgid "Deprecation Notes" msgstr "" #: ../../:177 msgid "" "Designate driver can now use Keystone v3 authentication options. \"The " "``[designate]`` section now accepts the ``auth_type`` option, as well as " "other ``keystoneauth`` options (e.g. ``auth_url``, ``username``, " "``user_domain_name``, ``password``, ``project_name``, " "``project_domain_name``).\"" msgstr "" #: ../../:62 stable/mitaka>:560 msgid "Does not change MTU for existing virtual network interfaces." msgstr "" #: ../../:388 msgid "" "Driver is configured in the default section of neutron.conf using parameter " "'external_dns_driver'" msgstr "" #: ../../:384 msgid "Drivers for other DNSaaS can be implemented" msgstr "" #: ../../:300 msgid "" "Due to changes in internal L3 logic, a server crash/backend failure during " "FIP creation may leave dangling ports attached on external networks. These " "ports can be identified by a ``PENDING`` ``device_id`` parameter. While " "those ports can also be removed by admins, the ``neutron-server`` service " "will now also trigger periodic (approximately once in 10 minutes) cleanup to " "address the issue." msgstr "" #: ../../:164 msgid "" "During Liberty, some Neutron APIs and options were deprecated. This included " "the FWaaS API, the LBaaS V1 API, and the 'external_network_bridge' option " "for the L3 agent." msgstr "" #: ../../:169 msgid "" "During Liberty, some plugins and drivers have been deprecated, including the " "metaplugin, the IBM SDN-VE plugin, the Cisco N1KV monolithic plugin, and the " "Embrane plugin." msgstr "" #: ../../:254 stable/stein>:641 msgid "" "During the dependency resolution procedure, the code that loads service " "plugins was refactored to not raise an exception if one plugin is configured " "multiple times, with the last one taking effect. This is a change from the " "previous behavior." msgstr "" #: ../../:189 stable/2023.2>:144 #: stable/2024.1>:402 unmaintained/wallaby>:152 unmaintained/xena>:101 #: unmaintained/yoga>:73 unmaintained/zed>:128 msgid "" "During the port bulk creation, if an IPAM allocation fails (for example, if " "the IP address is outside of the subnet CIDR), the other IPAM allocations " "already created are deleted before raising the exception. Fixes bug `2039550 " "`_." msgstr "" #: ../../:282 msgid "" "During the upgrade process, a set of four default security group rules will " "be created in the Neutron database. Those rules are the same default rules " "added to every new security group up to now:" msgstr "" #: ../../:429 msgid "" "During upgrade 'internal' ipam driver becomes default for 'ipam_driver' " "config option and data is migrated to new tables using alembic migration." msgstr "" #: ../../:656 msgid "" "Each plugin can decide if it wants to support filter validation by setting " "``__filter_validation_support`` to True or False. If this field is not set, " "the default value is False. Right now, the ML2 plugin and all the in-tree " "service plugins support filter validation. Out-of-tree plugins will have " "filter validation disabled by default but they can turn it on if they choose " "to. For filter validation to be supported, the core plugin and all the " "services plugins in a deployment must support it." msgstr "" #: ../../:376 msgid "" "Enable creation of VXLANs with different multicast addresses in linuxbridge " "agent allocated by VNI-address mappings. A new config option " "``multicast_ranges`` was introduced." msgstr "" #: ../../:48 stable/mitaka>:464 msgid "" "Enable end-to-end support for arbitrary MTUs including jumbo frames between " "instances and provider networks by moving MTU disparities between flat or " "VLAN networks and overlay networks from layer-2 devices to layer-3 devices " "that support path MTU discovery (PMTUD)." msgstr "" #: ../../:467 msgid "" "Enabled ``DbQuotaDriverNull`` as production ready database quota driver. " "This driver does not have access to the database and will return empty " "values to the request queries. This driver can be used to override the " "Neutron quota engine." msgstr "" #: ../../:532 msgid "" "Enabled placement enforcement for QoS minimum packet rate rule in OVS " "backend." msgstr "" #: ../../:133 msgid "" "Enabled the ``ha`` API extension for OVN routers. Now the high availability " "flag ``ha`` can be set and read for OVN routers. NOTE: currently OVN routers " "are always HA; the flag is mandatory and cannot be unset (but now can be " "read)." msgstr "" #: ../../:61 unmaintained/victoria>:111 #: unmaintained/wallaby>:337 unmaintained/xena>:394 msgid "" "Enforce policy for 'qos_policy_id' attribute of Floating IP so only " "authorized users can set/unset it. For more info see `bug LP#1957175 " "`_." msgstr "" #: ../../:48 current stable/2024.1>:14 msgid "" "Enhance error handling in the Neutron metadata service for cases when the " "Nova metadata service is unavailable, ensuring correct HTTP status codes are " "returned." msgstr "" #: ../../:672 msgid "" "Ensures that OVN's mechanism driver does not start when ``[ml2_type_geneve]/" "max_header_size`` is set below the required 38. `LP#1868137 `__" msgstr "" #: ../../:209 unmaintained/victoria>:275 #: unmaintained/wallaby>:591 msgid "" "Even with the \"igmp_snooping_enable\" configuration option stating that " "traffic would not be flooded to unregistered VMs when this option was " "enabled, the ML2/OVN driver didn't follow that behavior. This has now been " "fixed and ML2/OVN will no longer flood traffic to unregistered VMs when this " "configuration option is set to True." msgstr "" #: ../../:528 msgid "" "Example configuration of ``multicast_ranges`` in ml2_conf.ini under the " "``[vxlan]`` config. section ``multicast_ranges = " "224.0.0.10:10:90,225.0.0.15:100:900``. For VNI between 10 and 90, the " "multicast address 224.0.0.0.10 will be used, and for 100 through 900 " "225.0.0.15 will be used. Other VNI values will get standard ``vxlan_group`` " "address. For more info see RFE https://bugs.launchpad.net/neutron/" "+bug/1579068" msgstr "" #: ../../:540 msgid "" "Existing IPv6 ICMP security group rules created by using legacy protocol " "names ``icmpv6`` and ``icmp`` will now be returned as ``ipv6-icmp`` in an " "API GET call." msgstr "" #: ../../:401 msgid "" "Existing networks with MTU values that don't reflect configuration will " "receive new MTU values after controller upgrade. Note that to propagate new " "correct MTU values to your backend, you may need to resync all agents that " "set up ports, as well as re-attach VIFs to affected instances." msgstr "" #: ../../:604 msgid "" "Existing subnets can now be moved into a subnet pool, and by extension can " "be moved into address scopes they were not initially participating in." msgstr "" #: ../../:454 msgid "" "Existing subnets that were created outside of a subnet pool can know be " "moved, or \"onboarded\" into an existing subnet pool. This provides a way " "for subnets to be brought under the management of a subnet pool and begin " "participating in an address scope. By enabling onboarding, existing subnets " "can be used with features that build on subnet pools and address scopes. " "Subnet onboarding is subject to all the same restrictions as and guarantees " "currently enforced by subnet pools and address scopes." msgstr "" #: ../../:80 stable/mitaka>:632 msgid "" "Explicitly configure MTU of virtual network interfaces rather than using " "default values or incorrect values that do not account for overlay protocol " "overhead." msgstr "" #: ../../:346 msgid "" "Extend routed provider networks to allow provisioning more than one segment " "per physical network." msgstr "" #: ../../:460 msgid "" "Extensions can extend ``RouterInfo`` itself which correspond to each " "features (ha, distribtued, ha + distributed)." msgstr "" #: ../../:210 msgid "" "External networks can now be controlled using the RBAC framework that was " "added in Liberty. This allows networks to be made available to specific " "tenants (as opposed to all tenants) to be used as an external gateway for " "routers and floating IPs." msgstr "" #: ../../:352 msgid "" "External networks can now be controlled using the RBAC framework that was " "added in Liberty. This allows networks to be made available to specific " "tenants (as opposed to all tenants) to be used as an external gateway for " "routers and floating IPs. By default this feature will also allow regular " "tenants to make their networks available as external networks to other " "individual tenants (or even themselves), but they are prevented from using " "the wildcard to share to all tenants. This behavior can be adjusted via " "policy.json by the operator if desired." msgstr "" #: ../../:122 stable/newton>:273 msgid "" "First option `insecure` allows to skip SSL validation when creating a " "keystone session to initate a designate client. Default value is False, " "which means to always verify connection." msgstr "" #: ../../:144 stable/mitaka>:648 msgid "Fix SR-IOV agent macvtap assigned VF check when linux kernel < 3.13" msgstr "" #: ../../:49 stable/rocky>:56 stable/stein>:26 #: stable/train>:48 stable/ussuri>:123 unmaintained/victoria>:160 #: unmaintained/wallaby>:397 unmaintained/xena>:654 msgid "" "Fix `bug 1939733 `_ by " "dropping from the dhcp extra option values everything what is after first " "newline (``\\n``) character before passing them to the dnsmasq." msgstr "" #: ../../:296 stable/2023.2>:410 #: stable/ussuri>:84 unmaintained/victoria>:76 unmaintained/wallaby>:135 #: unmaintained/xena>:84 unmaintained/yoga>:202 unmaintained/zed>:225 msgid "" "Fix an issue in the OVN driver where network metadata could become " "unavailable if the metadata port was ever deleted, even if accidental. To re-" "create the port, a user can now disable, then enable, DHCP for one of the " "subnets associated with the network using the Neutron API. This will try and " "create the port, similar to what happens in the DHCP agent for ML2/OVS. For " "more information, see bug `2015377 `_." msgstr "" #: ../../:602 msgid "" "Fix an issue that standard attributes, such as ``created_at``, " "``updated_at`` and ``revision_number``, are not rendered in the response of " "segment resource." msgstr "" #: ../../:89 stable/rocky>:96 stable/stein>:74 #: stable/train>:126 stable/ussuri>:223 unmaintained/victoria>:295 msgid "" "Fixed MAC learning issue when ovs offload enabled. OVS firewall reduce the " "usage of normal actions to reduce cpu utilization. This causing flood rule " "because there is no MAC learning on ingress traffic. While this ok for none " "offload case, when using ovs offload flood rule is not offloaded. This fix " "the MAC learning in the offload, so we avoid flood rule. `#1897637 `_." msgstr "" #: ../../:676 msgid "" "Fixed a MAC learning issue when OVS offload is enabled. The OVS firewall " "reduces the usage of normal actions to reduce CPU utilization. This causes " "insertion of a flood rule because there is no MAC learning on ingress " "traffic. While this is okay for the non-offload case, when using OVS offload " "the flood rule is not being offloaded. This fixes the MAC learning in the " "offload case, so we avoid the flood rule. For more information, see bug " "`1897637 `_." msgstr "" #: ../../:281 stable/ussuri>:591 msgid "" "Fixed an issue where IP allocation for IPv6 stateless subnets would allocate " "on invalid subnets when segments are used. Auto-addressing now filters on " "segment ids when allocating IP addresses. See bugs: `#1864225 `_, `#1864333 `_, `#1865138 `_." msgstr "" #: ../../:275 stable/ussuri>:312 #: unmaintained/victoria>:508 msgid "" "Fixed an issue where the client on a dual-stack (IPv4 + IPv6) network failed " "to get configuration from the dnsmasq DHCP server. See bug: `1876094 " "`_." msgstr "" #: ../../:120 stable/ussuri>:306 #: unmaintained/victoria>:502 msgid "" "Fixed bug `1876092 `_ which " "caused DUP ICMP replies on the ``flat`` networks used with ``DVR`` routers." msgstr "" #: ../../:167 stable/2023.2>:135 #: stable/2024.1>:348 unmaintained/wallaby>:113 unmaintained/xena>:68 #: unmaintained/yoga>:51 unmaintained/zed>:106 msgid "" "Fixed the scenario where the DHCP agent is deployed in conjunction with the " "OVN metadata agent in order to serve metadata for baremetal nodes. In this " "scenario, the DHCP agent would not set the route needed for the OVN metadata " "agent service resulting in baremetal nodes not being able to query the " "metadata service. For more information see `bug 1982569 `_." msgstr "" #: ../../:540 msgid "" "Fixes Bug 1548193, removing 'force_gateway_on_subnet' configuration option. " "This will always allow adding gateway outside the subnet, and gateway cannot " "be forced onto the subnet range." msgstr "" #: ../../:335 msgid "" "Fixes L3 OVN schedulers (chance, leastloaded) to distribute Logical Router " "Port (LRP) gateways among all eligible AZs (if any). For more information, " "see bug `2030741 `_" msgstr "" #: ../../:191 unmaintained/victoria>:245 #: unmaintained/wallaby>:687 msgid "" "Fixes a configuration problem in the OVN driver that prevented external IGMP " "queries from reaching the Virtual Machines. See `bug 1918108 `_ for details." msgstr "" #: ../../:80 stable/queens>:253 stable/rocky>:351 #: stable/stein>:743 msgid "" "Fixes an issue causing IP allocation on port update to fail when the initial " "IP allocation was deferred due to lack of binding info. If both the port " "mac_address and binding info (binding_host_id) were updated in the same " "request, the fixed_ips field was added to the request internally. The code " "to complete the deferred allocation failed to execute in that case. (For " "more information see bug `1811905 `_.)" msgstr "" #: ../../:319 unmaintained/xena>:343 #: unmaintained/yoga>:341 unmaintained/zed>:578 msgid "" "Fixes an issue in the ML2/OVN driver where the network segment tag was not " "being updated in the OVN Northbound database. For more information, see bug " "`1944708 `_." msgstr "" #: ../../:99 stable/rocky>:143 stable/stein>:204 #: stable/train>:290 stable/ussuri>:600 msgid "" "Fixes an issue that the OVS firewall driver does not configure security " "group rules using remote group properly when a corresponding remote group " "has no port on a local hypervisor. For more information see bugs: `1862703 " "`_ and `1854131 `__." msgstr "" #: ../../:222 stable/stein>:344 stable/train>:612 msgid "" "Fixes an issue where deletion of a provider network could result in ML2 " "mechanism drivers not being passed information about the network's provider " "fields. The consequences of this depend on the mechanism driver in use, but " "could result in the event being ignored, leading to an incorrectly " "configured network. See `bug 1841967 `__ for details." msgstr "" #: ../../:76 stable/mitaka>:616 msgid "Fixes bug 1537734" msgstr "" #: ../../:84 stable/newton>:544 msgid "Fixes bug 1572670" msgstr "" #: ../../:106 stable/pike>:185 stable/queens>:584 msgid "" "Fixes bug 1736674, security group rules are now properly applied by " "``Linuxbridge L2 agent`` with ``QoS extension driver`` enabled." msgstr "" #: ../../:72 stable/queens>:245 stable/rocky>:343 #: stable/stein>:728 msgid "" "Fixes bug `1501206 `_. This " "ensures that DHCP agent instances running dnsmasq as a DNS server can no " "longer be exploited as DNS amplifiers when the tenant network is using " "publicly routed IP addresses by adding an option that will allow them to " "only serve DNS requests from local networks." msgstr "" #: ../../:598 msgid "Fixes bug `1682145 `_." msgstr "" #: ../../:398 stable/rocky>:594 msgid "Fixes bug `1745468 `_." msgstr "" #: ../../:356 stable/rocky>:629 msgid "" "Fixes bug `1763604 `_. " "Override default value of ``ovsdb_timeout`` config option in ``neutron-ovs-" "cleanup`` script. The default value is 10 seconds, but that is not enough " "for the ``neutron-ovs-cleanup`` script when there are many ports to remove " "from a single bridge, for example, 5000. Because of that, we now override " "the default value for the config option to be 600 seconds (10 minutes)." msgstr "" #: ../../:614 msgid "Fixes bug `1943724 `_." msgstr "" #: ../../:519 msgid "" "Floating IP QoS network inheritance is now available for OVN L3 plugin QoS " "extension. If a network, hosting a floating IP, has a QoS associated, the " "floating IP addresses will inherit the network QoS policy and will apply on " "the OVN backend." msgstr "" #: ../../:721 msgid "" "Floating IP port forwardings with different protocols could not have the " "same internal or external port number to the same VM port. After this fix we " "will allow creating port forwardings with same internal or external port " "number in different protocols." msgstr "" #: ../../:376 msgid "" "Floating IPs and ports will be published in an external DNS service if they " "have dns_name and dns_domain attributes associated with them." msgstr "" #: ../../:310 msgid "" "Floating IPs associated with an unbound port with DVR routers will not be " "distributed, but will be centralized and implemented in the SNAT namespace " "of the Network node or ``dvr_snat`` node. Floating IPs associated with " "allowed_address_pair port IP and are bound to multiple active VMs with DVR " "routers will be implemented in the SNAT namespace in the Network node or " "``dvr_snat`` node. This will address VRRP use cases. More information about " "this is captured in `bug 1583694 `__." msgstr "" #: ../../:368 msgid "" "Floating IPs can have dns_name and dns_domain attributes associated with them" msgstr "" #: ../../:225 msgid "" "Floating IPs should be centralized (``enable_distributed_floating_ip`` = " "``False``)." msgstr "" #: ../../:73 unmaintained/victoria>:65 #: unmaintained/wallaby>:343 unmaintained/xena>:406 unmaintained/yoga>:603 msgid "" "For IPv4 subnets when dns_nameservers is not set in the subnet, servers " "defined in 'ovn/dns_servers' config option or system's resolv.conf are used, " "but for IPv6 subnets these are not used. The same will now be used for IPv6 " "subnets too. Additionally dns servers added in 'ovn/dns_servers' config " "option or system's resolv.conf will be filtered as per the subnet's IP " "version. For more info see the bug report `1951816 `_." msgstr "" #: ../../:152 stable/queens>:325 stable/rocky>:621 msgid "" "For Infiniband support, Ironic needs to send the 'client-id' DHCP option as " "a number in order for IP address assignment to work. This is now supported " "in Neutron, and can be specified as option number 61 as defined in RFC " "4776. For more information see bug `1770932 `_" msgstr "" #: ../../:176 stable/2023.2>:403 #: unmaintained/wallaby>:128 unmaintained/xena>:77 unmaintained/yoga>:60 #: unmaintained/zed>:115 msgid "" "For OVN versions v22.09.0 and above, the ``mcast_flood_reports`` option is " "now set to ``false`` on all ports except \"localnet\" types. In the past, " "this option was set to ``true`` as a workaround for a bug in core OVN " "multicast implementation." msgstr "" #: ../../:94 stable/mitaka>:682 msgid "" "For details please read `Blueprint mtu-selection-and-advertisement `_." msgstr "" #: ../../:227 msgid "" "For more details see `bug 2028846 `_." msgstr "" #: ../../:666 msgid "" "For overlay networks managed by ML2 core plugin, the calculation algorithm " "subtracts the overlay protocol overhead from the value of [ml2] path_mtu. " "The DHCP agent provides the resulting (smaller) MTU to instances using " "overlay networks." msgstr "" #: ../../:231 stable/train>:309 stable/ussuri>:474 msgid "" "For users affected by `bug 1853840 `_ " "the hypervisor name now can be set per physical network device in config " "option ``resource_provider_hypervisors`` which is located in the ``[ovs]`` " "ini-section for ``ovs-agent`` and ``[sriov_nic]`` ini-section for ``sriov-" "agent``. Hypervisor names default to ``socket.gethostname()`` which works " "out of the box with ``libvirt`` even when the ``DEFAULT.host`` config option " "is set to a non-default value." msgstr "" #: ../../:572 msgid "" "Forbid the creation of a duplicate NDP proxy entry on the same router, since " "the IP address of a router is unique and an IPv6 address only needs one NDP " "proxy." msgstr "" #: ../../:603 msgid "" "From now on, gateway interface will be kept up on all nodes where HA router " "is hosted, regardless of their state (active or standby). For more " "information see bug `1952907 `_." msgstr "" #: ../../:681 msgid "" "Function ``get_binding_levels`` from ``neutron.plugins.ml2.db`` module is " "deprecated and will be removed in the future. New function " "``get_binding_levels_objs`` should be used instead. This new function " "returns ``PortBindingLevel`` OVO objects." msgstr "" #: ../../:528 msgid "" "Function neutron.plugins.ml2.db.get_binding_levels was deprecated in favor " "of neutron.plugins.ml2.db.get_binding_level_objs and now is removed." msgstr "" #: ../../:450 msgid "" "Gateway IP QoS network inheritance is now available for OVN L3 plugin QoS " "extension. If the router external network (gateway network) has a QoS policy " "associated, the gateway IP port will inherit the network QoS policy." msgstr "" #: ../../:290 msgid "" "High Availability (HA) of SNAT service is supported for Distributed Virtual " "Routers (DVRs)." msgstr "" #: ../../:456 msgid "" "High Availability support for SNAT services on Distributed Virtual Routers. " "Routers can now be created with the flags distributed=True and ha=True. The " "created routers will provide Distributed Virtual Routing as well as SNAT " "high availability on the l3 agents configured for dvr_snat mode." msgstr "" #: ../../:151 msgid "" "Hyper-V Neutron Agent has been fully decomposed from Neutron. Therefore, the " "`neutron.plugins.hyperv.agent.security_groups_driver." "HyperVSecurityGroupsDriver` firewall driver has been deleted. Update the " "`neutron_hyperv_agent.conf` / `neutron_ovs_agent.conf` files on the Hyper-V " "nodes to use `hyperv.neutron.security_groups_driver." "HyperVSecurityGroupsDriver`, which is the networking_hyperv security groups " "driver." msgstr "" #: ../../:344 msgid "" "IGMP snooping (multicast) can now be enabled in the ``OVS`` and ``OVN`` " "drivers." msgstr "" #: ../../:140 msgid "" "IPv6 Metadata support was added to the ML2/OVN driver. The agent now " "provisions the ``fe80::a9fe:a9fe/128`` address to the OVN metadata namespace " "and makes haproxy listen on it to serve metadata requests to instances over " "IPv6." msgstr "" #: ../../:14 msgid "" "IPv6 addresses in DHCP namespaces will now be (correctly) statically " "configured by the DHCP agent." msgstr "" #: ../../:174 msgid "IPv6 prefix delegation support was added to Neutron." msgstr "" #: ../../:255 msgid "" "If ML2/OVS is used and ``igmp_snooping_enable`` is enabled, in order to make " "the IGMP related traffic run as before please ensure that the following " "configuration options are enabled after the upgrade." msgstr "" #: ../../:443 msgid "" "If ``uplink-status-propagation`` extension is enabled, all existing ports " "before enabling it will have the flag \"propagate_uplink_status\" enabled by " "default. This is aligned with the aim of an administrator that enables this " "extension. Now only new ports can be created with this flag disabled." msgstr "" #: ../../:286 stable/stein>:793 msgid "" "If an instance port is under a dvr router, and the port already has binding " "port forwarding(s). Neutron will no longer allow binding a floating IP to " "that port again, because dvr floating IP traffic rules will break the " "existing port forwarding functionality." msgstr "" #: ../../:31 stable/ussuri>:38 #: unmaintained/victoria>:48 unmaintained/wallaby>:281 unmaintained/xena>:311 #: unmaintained/yoga>:291 unmaintained/zed>:495 msgid "" "If the ``use_random_fully`` setting is disabled, it will prevent random " "fully from being used and if there're 2 guests in different networks using " "the same source_ip and source_port and they try to reach the same dest_ip " "and dest_port, packets might be dropped in the kernel do to the racy tuple " "generation . Disabling this setting should only be done if source_port is " "really important such as in network firewall ACLs and that the source_ip are " "never repeating within the platform." msgstr "" #: ../../:312 msgid "" "If you want to disable them then modify the below config options value in " "``neutron.conf`` file::" msgstr "" #: ../../:479 msgid "" "Implementation of floating IP QoS. A new parameter ``qos_policy_id`` was " "added to floating IP related API." msgstr "" #: ../../:326 msgid "" "Implements a new extension, ``quota_details`` which extends existing quota " "API to show detailed information for a specified tenant. The new API shows " "details such as ``limits``, ``used``, ``reserved``." msgstr "" #: ../../:300 msgid "Improve DVR's resiliency during Nova VM live migration events." msgstr "" #: ../../:159 msgid "" "In Liberty, some changes were made to agent scheduling to enable a more " "flexible agent scheduling configuration." msgstr "" #: ../../:56 stable/2023.2>:324 msgid "" "In ML2/OVN, any new router gateway port (OVN logical router port) will be " "scheduled only on those chassis configured as gateway. Any existing router " "gateway port will preserve the current chassis assignation." msgstr "" #: ../../:344 msgid "" "In Mitaka, queries to the Networking API for network objects will now return " "network objects that contain a sane MTU value." msgstr "" #: ../../:340 msgid "" "In Mitaka, the combination of 'path_mtu' defaulting to 1500 and " "'advertise_mtu' defaulting to True provides a value of MTU accounting for " "any overlay protocol overhead on the network to instances using DHCP. For " "example, an instance attaching to a VXLAN network receives a 1450 MTU from " "DHCP accounting for 50 bytes of overhead from the VXLAN overlay protocol if " "using IPv4 endpoints." msgstr "" #: ../../:247 msgid "" "In OVN 22.09 the option \"localnet_learn_fdb\" was added, enabling localnet " "ports to learn MAC addresses and store them at the FDB table. There is no " "aging mechanism for those MACs (that is the reason for not having this " "option enabled by default) and therefore it needs to be used with care, " "specially when provider networks are big. It is recommended to perform " "periodic manual cleanups of FDB table, to avoid scalability issues -- until " "OVN implements an aging mechanism for this, tracked at https://bugzilla." "redhat.com/show_bug.cgi?id=2179942." msgstr "" #: ../../:182 msgid "" "In OVN 22.09 the option ``localnet_learn_fdb`` was added, enabling localnet " "ports to learn MAC addresses and store them at the FDB table. There was no " "aging mechanism for those MACs until OVN 23.06, where the configuration " "option ``fdb_age_threshold`` was added. This enables to set the maximum time " "the learned MACs will stay in the FDB table (in seconds). When the " "``localnet_learn_fdb`` configuration option is enabled, the proper value for " "``fdb_age_threshold`` should also be set, to avoid performance/scalability " "issues due to the table growing too much -- especially when provider " "networks are large. In addition the configuration option " "``fdb_removal_limit`` was also added to avoid removing a large number of " "entries at once." msgstr "" #: ../../:425 msgid "" "In case you rely on the default ML2 path_mtu value of 1500 to cap MTU used " "for new network resources, please set it explicitly in your ml2_conf.ini " "file." msgstr "" #: ../../:211 msgid "" "In kernels < 3.19 ``net.ipv4.ip_nonlocal_bind`` sysctl option was not " "isolated to network namespace scope. L3 HA sets this option to zero to avoid " "sending gratuitous ARPs for IP addresses that were removed while processing. " "If this happens, then gratuitous ARPs will be sent. It may populate ARP " "cache tables of peer machines with wrong MAC addresses." msgstr "" #: ../../:14 stable/newton>:84 msgid "" "In kernels < 3.19 net.ipv4.ip_nonlocal_bind was not a per-namespace kernel " "option. L3 HA sets this option to zero to avoid sending gratuitous ARPs for " "IP addresses that were removed while processing. If this happens then " "gratuitous ARPs are going to be sent which might populate ARP caches of peer " "machines with the wrong MAC address." msgstr "" #: ../../:428 msgid "" "In order to better support instance migration, multiple port bindings can be " "associated to compute owned ports." msgstr "" #: ../../:531 msgid "" "In order to fix the communication issues between SR-IOV instances and " "regular instances the FDB population extension is added to the OVS or " "linuxbridge agent. the cause was that messages from SR-IOV direct port " "instance to normal port instances located on the same hypervisor were sent " "directly to the wire because the FDB table was not yet updated. FDB " "population extension tracks instances boot/delete operations using the " "handle_port delete_port extension interface messages and update the " "hypervisor's FDB table accordingly. Please note this L2 agent extension " "doesn't support allowed address pairs extension." msgstr "" #: ../../:74 stable/pike>:26 stable/queens>:199 #: stable/rocky>:279 stable/stein>:414 stable/train>:654 msgid "" "In order to improve heavy load ovs agent restart success rate, instead a " "retry or fullsync, the native driver ``of_connect_timeout`` and " "``of_request_timeout`` are now set to 300s. The value does not have side " "effect for the regular pressure ovs agent." msgstr "" #: ../../:251 msgid "" "In order to make IGMP configuration consistent across drivers some defaults " "had to be changed for ML2/OVS. This change did not affect the defaults in " "the ML2/OVN driver." msgstr "" #: ../../:368 msgid "" "In order to reduce metadata proxy memory footprint, ``haproxy`` is now used " "as a replacement for ``neutron-ns-metadata-proxy`` Python implementation." msgstr "" #: ../../:377 stable/rocky>:403 msgid "" "In order to reduce the time spent processing security group updates in the " "L2 agent, conntrack deletion is now performed in a set of worker threads " "instead of the main agent thread, so it can return to processing other " "events quickly." msgstr "" #: ../../:566 msgid "" "In order to use QoS egress minimum bandwidth limit feature, 'ip-link' must " "support the extended VF management parameter ``min_tx_rate``. Minimum " "version of ``ip-link`` supporting this parameter is ``iproute2-ss140804``, " "git tag ``v3.16.0``." msgstr "" #: ../../:418 msgid "" "In previous versions, an administrator was allowed to update a port " "``binding:vnic_type`` attribute even if it was bound. This is now blocked " "and the update operation of the attribute returns the ``Conflict (409)`` " "response code." msgstr "" #: ../../:606 msgid "" "In security group rules API, API level validation for port_range values has " "been performed only against TCP and UDP. Now it is performed against DCCP, " "SCTP and UDP-Lite, too." msgstr "" #: ../../:344 stable/rocky>:554 msgid "" "In the case when the number of ports to clean up in a single bridge is " "larger than about 10000, it might require an increase in the " "``ovsdb_timeout`` config option to some value higher than 600 seconds." msgstr "" #: ../../:197 msgid "" "Initial support for ``oslo.privsep`` has been added. Most external commands " "are still executed using ``oslo.rootwrap``." msgstr "" #: ../../:164 msgid "" "Introduce the attribute ``hardware_offload_type`` to ports, that specifies " "the hardware offload type this port will request when attached to the " "network backend." msgstr "" #: ../../:510 msgid "" "Introduce the attribute ``port_device_profile`` to ports that specifies the " "device profile needed per port. This parameter is a string. This parameter " "is passed to Nova and Nova retrieves the requested profile from Cyborg: " "`Device profiles `_." msgstr "" #: ../../:509 msgid "" "Introduce the attribute ``propagate_uplink_status`` to ports. Right now, the " "SRIOV mechanism driver leverages this attribute to decide if the VF link " "should follow the state of the PF. For example, if the PF is down, the VF " "link state is automatically set to down as well. Operators can turn on this " "feature via the configuration option::" msgstr "" #: ../../:355 msgid "Introduce the experimental features framework." msgstr "" #: ../../:468 msgid "" "Introduced a database constraint to limit the number of " "``ha_router_networks`` registers per project to one only. This register is " "used to bind projects and networks, defining the corresponding network as " "high availability (HA) network. By definition, only one HA network per " "project can exist." msgstr "" #: ../../:685 msgid "" "Introduced config option for RPC agent step size customization: " "rpc_resources_processing_step - Number of resources for neutron to divide " "the large RPC call data sets. It can be reduced if RPC timeout occurred. " "Default value equals 20. The best value can be determined empirically in " "your environment." msgstr "" #: ../../:466 msgid "" "Introduces extension parent resources owner check in ``neutron.policy." "OwnerCheck``. It can be used by registering an extension parent resource and " "service plugin which introduced the corresponding parent resource into " "``EXT_PARENT_RESOURCE_MAPPING`` located in ``neutron.common.constants``. And " "introduces a new policy role ``admin_or_ext_parent_owner`` into ``policy." "json`` for this function." msgstr "" #: ../../:351 msgid "" "Introducing `clean_devices`, a new DHCP driver's API that can be called to " "clean stale devices." msgstr "" #: ../../:574 msgid "" "It enables users to associate QoS policies to L3 router gateways to control " "the rate of transmission of the associated SNAT traffic." msgstr "" #: ../../:662 msgid "" "It is assumed now that OVN supports Northbound table ``Port_Group`` by " "default. This table was added in the DB schema version 5.11. A sanity check " "is included if OVN is defined in ``ml2.mechanism_drivers`` configuration " "option." msgstr "" #: ../../:458 msgid "" "It is now possible to instruct the DHCP agent not to supply any DNS server " "address to their clients by setting the ``dns_nameservers`` attribute for " "the corresponding subnet to ``0.0.0.0`` or ``::``, for IPv4 or IPv6 subnets " "(respectively)." msgstr "" #: ../../:49 msgid "" "Keepalived VRRP health check functionality to enable verification of " "connectivity from the \"master\" router to all gateways." msgstr "" #: ../../:169 msgid "" "Keepalived VRRP health check functionality to enable verification of " "connectivity from the \"master\" router to all gateways. Activation of this " "feature enables gateway connectivity validation and rescheduling of the " "\"master\" router to another node when connectivity is lost. If all routers " "lose connectivity to the gateways, the election process will be repeated " "round-robin until one of the routers restores its gateway connection. In the " "mean time, all of the routers will be reported as \"master\"." msgstr "" #: ../../:38 stable/2023.1>:141 #: stable/2023.1>:251 stable/2023.1>:390 stable/2023.2>:38 stable/2023.2>:214 #: stable/2024.1>:213 stable/liberty>:257 stable/mitaka>:10 stable/mitaka>:506 #: stable/newton>:80 stable/newton>:351 stable/ocata>:207 stable/pike>:382 #: stable/queens>:340 stable/queens>:506 stable/rocky>:550 stable/train>:27 #: stable/ussuri>:34 stable/ussuri>:205 unmaintained/victoria>:28 #: unmaintained/victoria>:173 unmaintained/victoria>:271 #: unmaintained/wallaby>:26 unmaintained/wallaby>:277 unmaintained/wallaby>:420 #: unmaintained/wallaby>:587 unmaintained/xena>:20 unmaintained/xena>:153 #: unmaintained/xena>:205 unmaintained/xena>:307 unmaintained/xena>:565 #: unmaintained/yoga>:106 unmaintained/yoga>:157 unmaintained/yoga>:279 #: unmaintained/zed>:24 unmaintained/zed>:80 unmaintained/zed>:180 #: unmaintained/zed>:271 unmaintained/zed>:491 msgid "Known Issues" msgstr "" #: ../../:92 stable/pike>:171 stable/queens>:465 msgid "" "L2 agents based on ``ML2`` ``_common_agent`` have now the L2 extension API " "available. This API can be used by L2 extension drivers to request resources " "from the L2 agent. It is used, for example, to pass an instance of the " "``IptablesManager`` to the ``Linuxbridge`` L2 agent ``QoS extension driver``." msgstr "" #: ../../:502 msgid "" "L3 agent supports QoS bandwidth limit functionality for port forwarding " "floating IPs now. If floating IP has binding QoS policy (with bandwidth " "limit rules), the traffic bandwidth will be limited." msgstr "" #: ../../:227 msgid "" "LBaaS V2 reference driver is now based on Octavia, an operator grade " "scalable, reliable Load Balancer platform." msgstr "" #: ../../:279 msgid "" "Launchpad `Bug 1383674 `_ " "has details on the agent restart fix which went into Liberty to address OVS " "agent restartability." msgstr "" #: ../../:579 msgid "" "Leverage the coordination lock to the resource processing and notification " "thread functions to minimize the lock granularity." msgstr "" #: ../../:472 msgid "" "Libvirt qemu/kvm instances can now be attached via MacVtap in bridge mode to " "a network. VLAN and FLAT attachments are supported. Other attachmentes than " "compute are not supported." msgstr "" #: ../../:414 msgid "" "Limit the ML2 VLAN allocations to [1, 4094] values in the database engine. " "This constraint, enforced in the database engine, could not be supported " "yet. In this case, it will be ignored. For more information, see the note in " "``neutron.db.migration.alembic_migrations.versions.victoria.expand." "dfe425060830_limit_vlan_allocation_id_values.py``." msgstr "" #: ../../:332 msgid "" "Linuxbridge L2 agent supports ingress bandwidth limit. The linuxbridge L2 " "agent now supports bi-directional bandwidth limiting." msgstr "" #: ../../:652 msgid "" "Loaded agent extensions of SR-IOV agent are now shown in agent state API." msgstr "" #: ../../:444 msgid "" "Local IP - a virtual IP that can be shared across multiple ports/VMs " "(similar to anycast IP) and is guaranteed to only be reachable within the " "same physical server/node boundaries. The feature is primarily focused on " "high efficiency and performance of the networking data plane for very large " "scale clouds and/or clouds with high network throughput demands." msgstr "" #: ../../:196 msgid "" "MAC address aging in the OVN ML2 mech driver is now supported and can be " "configured globally with the new ``[ovn] mac_binding_age_threshold`` and " "``[ovn_nb_global] mac_binding_removal_limit`` configuration options. Setting " "the value per-router is not currently supported. This feature is available " "in OVN versions >= 22.09.0+. Previous versions will ignore the new options." msgstr "" #: ../../:372 msgid "" "ML2/OVS and ML2/OVN now support modelling tunnelled networks in the " "Placement API. The \"tunnelled_network_rp_name\" configuration option " "defines the resource provider name used to represent all tunnelled networks " "in a compute node (by default \"rp_tunnelled\"). If this string is present " "in the \"resource_provider_bandwidths\" dictionary, the corresponding " "mechanism driver will create a resource provider for the overlay traffic." msgstr "" #: ../../:109 stable/mitaka>:235 msgid "ML2: ports can now recover from binding failed state." msgstr "" #: ../../:353 msgid "" "Make the metadata service available over the IPv6 link-local address ``fe80::" "a9fe:a9fe``. Metadata over IPv6 works on both isolated networks and networks " "with an IPv6 subnet connected to a Neutron router as well as on dual-stack " "and on IPv6-only networks. There are no new config options. The usual " "config options (``enable_isolated_metadata``, ``force_metadata``, " "``enable_metadata_proxy``) now control the metadata service over both IPv4 " "and IPv6. This change only affects the guests' access to the metadata " "service over tenant networks. This feature changes nothing about how the " "metadata-agent talks to Nova's metadata service. The guest OS is expected to " "pick up routes from Router Advertisements for this feature to work on " "networks connected to a router. At least the following IPv6 subnet modes " "work:" msgstr "" #: ../../:340 msgid "" "Manila owned ports can now have multiple port bindings associated in order " "to support nondisruptive Manila share server migration across physical " "networks." msgstr "" #: ../../:123 msgid "" "Middleware was added to parse the X-Forwarded-Proto HTTP header or the Proxy " "protocol in order to help neutron respond with the correct URL refs when " "it's put behind a TLS proxy (such as HAProxy). This adds http_proxy_to_wsgi " "middleware to the pipeline. This middleware is disabled by default, but can " "be enabled via a configuration option in the oslo_middleware group." msgstr "" #: ../../:161 msgid "" "Middleware was added to parse the ``X-Forwarded-Proto`` HTTP header or the " "Proxy protocol in order to help Neutron respond with the correct URL " "references when it's put behind a TLS proxy such as ``haproxy``. This adds " "``http_proxy_to_wsgi`` middleware to the pipeline. This middleware is " "disabled by default, but can be enabled via a configuration option in the " "``[oslo_middleware]`` group." msgstr "" #: ../../:527 msgid "" "Missing OSprofiler support was added. This cross-project profiling library " "allows to trace various OpenStack requests through all OpenStack services " "that support it. To initiate OpenStack request tracing `--profile " "` option needs to be added to the CLI command. This key needs to " "present one of the secret keys defined in neutron.conf configuration file " "with `hmac_keys` option under the `[profiler]` configuration section. To " "enable or disable Neutron profiling the appropriate `enabled` option under " "the same section needs to be set either to `True` or `False`. By default " "Neutron will trace all API and RPC requests, but there is an opportunity to " "trace DB requests as well. For this purpose `trace_sqlalchemy` option needs " "to be set to `True`. As a prerequisite OSprofiler library and its storage " "backend needs to be installed to the environment. If so (and if profiling is " "enabled in neutron.conf) the trace can be generated via command - `$ neutron " "--profile SECRET_KEY `. At the end of output there will be " "message with , and to plot nice HTML graphs the following command " "should be used - `$ osprofiler trace show --html --out result." "html`" msgstr "" #: ../../:446 msgid "" "Monitoring tools relying on exact process names should be checked after " "upgrade, and modified if needed." msgstr "" #: ../../:522 msgid "" "More synchronization between Nova and Neutron is needed to properly handle " "live migration failures on either side. For instance, if live migration is " "reverted or canceled, some dangling Neutron resources may be left on the " "destination host." msgstr "" #: ../../:355 msgid "" "Network QoS policies are now supported for network:router_gateway ports. " "Neutron QoS policies set on an external network now apply to external router " "ports (DVR or not)." msgstr "" #: ../../:408 msgid "" "Networks can be filtered by tags. The supported filters are 'tags', 'tags-" "any', 'not-tags' and 'not-tags-any'." msgstr "" #: ../../:251 msgid "" "Networks used for VRRP traffic for HA routers may now be configured to use a " "specific segmentation type or physical network tag." msgstr "" #: ../../:273 msgid "" "Neutron API can now be managed by a ``mod_wsgi`` compatible web server (e.g. " "``apache2`` (``httpd``), ``nginx``, etc.)" msgstr "" #: ../../:342 msgid "" "Neutron API now allows tagging resources directly in the ``POST`` request." msgstr "" #: ../../:753 msgid "" "Neutron API workers default to the number of CPU cores. This can lead to " "high cpu/low memory boxes getting into trouble. The defaults have been " "tweaked to attempt to put an upper bound on the default of either the number " "of cores, or half of system memory, whichever is lower. In addition, the " "default number of RPC workers has been changed from a value of ``1``, to a " "value of half the number of API workers." msgstr "" #: ../../:552 msgid "" "Neutron LBaaS has now been retired. References to neutron-lbaas have been " "removed from neutron. For more information see https://wiki.openstack.org/" "wiki/Neutron/LBaaS/Deprecation" msgstr "" #: ../../:483 msgid "" "Neutron agents now support SSL connections to OVSDB server. To enable an SSL " "based connection, use an ``ssl`` prefixed URI for the ``ovsdb_connection`` " "setting. When using SSL it is also required to set new ``ovs`` group " "options which include ``ssl_key_file``, ``ssl_cert_file``, and " "``ssl_ca_cert_file``." msgstr "" #: ../../:168 msgid "" "Neutron allows cloud administrators to limit the rate at which VMs query the " "Nova metadata service in order to protect the OpenStack deployment from DoS " "or misbehaved instances. This new feature can be configured in the neutron." "conf file. Please see the \"Metadata service query rate limiting\" section " "under Neutron configuration in the documentation for more details." msgstr "" #: ../../:63 msgid "" "Neutron allows users to create routers with flavors with the L3 OVN plugin. " "This new feature can be configured in the neutron.conf file. Please see the " "\"Creating a L3 OVN router with a user defined flavor\" section under " "Neutron configuration in the documentation for more details. This document " "also describes the steps users have to take to create a router with a flavor " "assigned to it." msgstr "" #: ../../:294 msgid "" "Neutron can apply a QoS rule to ports that mark outgoing traffic's type of " "service packet header field." msgstr "" #: ../../:500 msgid "Neutron can interact with keystone v3." msgstr "" #: ../../:475 unmaintained/wallaby>:184 #: unmaintained/xena>:241 unmaintained/yoga>:348 unmaintained/zed>:322 msgid "" "Neutron can record full connection using log-related feature introduced in " "OVN 21.12. For more info see `bug LP#`" msgstr "" #: ../../:600 msgid "" "Neutron child processes now set their process titles to match their roles " "('api worker', 'rpc worker', 'periodic worker', 'services worker', or any " "other defined by workers from out-of-tree plugins.) This behavior can be " "disabled by setting the ``setproctitle`` config option in the ``[default]`` " "section in neutron.conf to ``off``. The original process string is also " "appended to the end, to help with scripting that is looking for the old " "strings. There is also an option called ``brief``, which results in much " "shorter and easier to read process names. The default setting for this " "option is ``on``, for a combination of backwards compatibility and " "identifying different processes easily. The recommended setting is " "``brief``, once the deployer has verified that none of their tooling depends " "on the older strings." msgstr "" #: ../../:472 msgid "" "Neutron controller service currently allows to load ``service_providers`` " "options from some files that are not passed to it via --config-dir or --" "config-file CLI options. This behaviour is now deprecated and will be " "disabled in Ocata. Current users are advised to switch to aforementioned CLI " "options." msgstr "" #: ../../:627 msgid "" "Neutron currently does not fully respect the network-auto-schedule " "configuration option. If the network-auto-schedule option is set to False, " "the network - a) Is still scheduled on the DHCP agent when it is created b) " "Is scheduled on a new DHCP agent if the old DHCP mapping is removed by the " "user/admin. It is especially necessary where the Network Backends provide " "DHCP directly. This has been fixed now and if the network-auto-schedule is " "set to False in the config file, networks would not be automatically " "scheduled to the DHCP Agents. If mapping/scheduling is required, it can be " "done manually or by setting the network-auto-schedule to True." msgstr "" #: ../../:576 msgid "Neutron depends on keystoneauth instead of keystoneclient." msgstr "" #: ../../:325 msgid "Neutron is integrated with Guru Meditation Reports library." msgstr "" #: ../../:440 msgid "" "Neutron no longer includes static example configuration files. Instead, use " "tools/generate_config_file_samples.sh to generate them. The files are " "generated with a .sample extension." msgstr "" #: ../../:523 msgid "" "Neutron now experimentally supports new API policies with the system scope " "and the default roles (member, reader, admin)." msgstr "" #: ../../:204 msgid "" "Neutron now exposes a QoS API, initially offering bandwidth limitation on " "the port level. See the `QoS devref `_ for additional information." msgstr "" #: ../../:199 msgid "Neutron now has a pluggable IP address management framework." msgstr "" #: ../../:254 stable/train>:346 stable/ussuri>:614 msgid "" "Neutron now locates the root resource provider of the resource provider tree " "it creates by using the hypervisor name instead of the hostname. These are " "different in rare cases only. The hypervisor name can be set per physical " "network device in config option ``resource_provider_hypervisors`` which is " "located in the ``[ovs]`` ini-section for ``ovs-agent`` and ``[sriov_nic]`` " "ini-section for ``sriov-agent``. Hypervisor names default to ``socket." "gethostname()`` which works out of the box with ``libvirt`` even when the " "``DEFAULT.host`` config option is set to a non-default value. We believe " "this change fixes `bug 1853840 `_." msgstr "" #: ../../:184 msgid "Neutron now offers role base access control (RBAC) for networks." msgstr "" #: ../../:219 msgid "" "Neutron now provides a way for admins to manually schedule agents, allowing " "host resources to be tested before they are enabled for tenant use." msgstr "" #: ../../:320 msgid "Neutron now provides network IP availability information." msgstr "" #: ../../:205 msgid "" "Neutron now sets different process titles for RPC workers ('rpc worker') and " "RPC reports worker ('rpc reports worker') so that these two types of workers " "can be distinguished." msgstr "" #: ../../:382 msgid "" "Neutron now supports API policies with the new default roles " "``project_member`` and ``project_reader``. Role ``admin`` is working in the " "same way as with old policies." msgstr "" #: ../../:223 msgid "" "Neutron now supports IPv6 Prefix Delegation for the automatic assignment of " "CIDRs to IPv6 subnets. For more information on the usage and configuration " "of this feature, see the `OpenStack Networking Guide `_." msgstr "" #: ../../:452 msgid "" "Neutron now supports creation of ports for exposing physical functions as " "network devices to guests." msgstr "" #: ../../:300 stable/stein>:833 msgid "" "Neutron now supports having service plugins require other plugin(s) as " "dependencies. For example, the ``port_forwarding`` service plugin requires " "the ``router`` service plugin to achieve full functionality. A new list, " "``required_service_plugins``, was added to each service plugin so the " "required dependencies of each service plugin can be initialized. If one " "service plugin requires another, but the requirement is not set in the " "config file, neutron will now initialize it to the plugin directory." msgstr "" #: ../../:396 msgid "" "Neutron now supports sharing of QoS policies between a subset of tenants." msgstr "" #: ../../:428 msgid "" "Neutron now supports the placement enforcement for the guaranteed minimum " "bandwidth QoS rule type with direct-phyisical vnic_type as well. The data " "plane enforcement of such rule and vnic_type combination is still not " "supported." msgstr "" #: ../../:708 msgid "" "Neutron resource tags can now be 255 characters long, previously resource " "tags was limited to 60 characters." msgstr "" #: ../../:209 msgid "" "Neutron routers underwent some changes and enhancements during Liberty " "around L2 population integration, VPNaaS, and segmentation types." msgstr "" #: ../../:825 msgid "" "Neutron server now rejects (as ``NotImplementedError``) updates of " "``minimum_bandwidth`` QoS rules if the rule is already in effect on bound " "ports. Implementing updates will require updates to Placement allocations " "and possibly migrating servers where the new ``minimum_bandwidth`` can be " "satisifed." msgstr "" #: ../../:492 msgid "" "Neutron services should respond to SIGUSR2 signal by dumping valuable debug " "information to standard error output." msgstr "" #: ../../:489 msgid "" "Neutron supports ECMP routes now, with this change, neutron will consolidate " "multiple routes with the same destination address into a single ECMP route. " "For more information see bug `1880532 `_." msgstr "" #: ../../:458 msgid "" "Neutron supports creating IPv4 subnet with prefixlen /31 and /32, via " "disabling dhcp on a subnet. For more information, see bug `1580927 `_." msgstr "" #: ../../:321 msgid "" "Neutron switched to using oslo.cache library to cache port state in metadata " "agent. With it, more caching backends are now available, including Memcached " "and Mongo. More details in oslo.cache documentation." msgstr "" #: ../../:341 msgid "" "New API extensions, 'sorting' and 'pagination', have been added to allow API " "users to detect if sorting and pagination features are enabled. These " "features are controlled by ``allow_sorting`` and ``allow_pagination`` " "configuration options." msgstr "" #: ../../:361 msgid "" "New API to get details of supported rule types. The QoS service plugin can " "now expose details about supported QoS rule types in Neutron deployment. The " "new API call is allowed only for users with admin priviliges." msgstr "" #: ../../:10 current stable/2023.1>:10 #: stable/2023.1>:330 stable/2023.2>:10 stable/2023.2>:158 stable/2024.1>:42 #: stable/liberty>:40 stable/liberty>:115 stable/liberty>:215 stable/mitaka>:60 #: stable/mitaka>:114 stable/mitaka>:336 stable/newton>:55 stable/newton>:70 #: stable/newton>:119 stable/newton>:259 stable/ocata>:10 stable/ocata>:88 #: stable/ocata>:126 stable/ocata>:157 stable/pike>:123 stable/pike>:167 #: stable/pike>:235 stable/queens>:10 stable/queens>:283 stable/queens>:424 #: stable/rocky>:10 stable/rocky>:424 stable/stein>:10 stable/stein>:91 #: stable/stein>:126 stable/stein>:366 stable/stein>:460 stable/train>:10 #: stable/train>:106 stable/train>:143 stable/train>:161 stable/train>:197 #: stable/train>:419 stable/ussuri>:10 stable/ussuri>:240 stable/ussuri>:258 #: stable/ussuri>:365 unmaintained/victoria>:10 unmaintained/victoria>:322 #: unmaintained/wallaby>:10 unmaintained/wallaby>:248 unmaintained/wallaby>:410 #: unmaintained/wallaby>:470 unmaintained/xena>:10 unmaintained/xena>:272 #: unmaintained/xena>:450 unmaintained/yoga>:236 unmaintained/yoga>:389 #: unmaintained/yoga>:417 unmaintained/zed>:10 unmaintained/zed>:259 #: unmaintained/zed>:361 msgid "New Features" msgstr "" #: ../../:27 stable/stein>:95 stable/train>:147 #: stable/ussuri>:244 unmaintained/victoria>:332 msgid "" "New config option ``keepalived_use_no_track`` was added. If keepalived " "version used on the deployment does not support ``no_track`` flag in its " "config file (e.g. keepalived 1.x), this option should be set to ``False``. " "Default value of this option is ``True``." msgstr "" #: ../../:107 msgid "" "New configuration options for IGMP were added in the [OVS] section: " "``igmp_flood``, ``igmp_flood_reports`` and ``igmp_flood_unregistered``. This " "gives operators full control on how IGMP should be configured for their " "deployments." msgstr "" #: ../../:533 msgid "" "New configuration options for neutron-ovs-agent under section ``[ovs]``: " "``resource_provider_bandwidths`` and " "``resource_provider_inventory_defaults``. The former controls the ``total`` " "(available bandwidth) field of the physical network interface resource " "provider inventories. It defaults to not creating resource providers in " "Placement. The latter can be used to tune the other fields " "(``allocation_ratio``, ``min_unit``, ``max_unit``, ``reserved``, " "``step_size``) of resource provider inventories." msgstr "" #: ../../:504 msgid "" "New configuration options for neutron-ovs-agent under section ``[ovs]``: " "``resource_provider_packet_processing_without_direction``, " "``resource_provider_packet_processing_with_direction`` and " "``resource_provider_packet_processing_inventory_defaults``. " "``resource_provider_packet_processing_without_direction`` controls the " "minimum packet rate the OVS backend can guarantee in kilo (1000) packet per " "second. ``resource_provider_packet_processing_with_direction`` is similar to " "the first option, but used in case the OVS backend has hardware offload " "capabilities. The last option can be used to tune the other fields " "(``allocation_ratio``, ``min_unit``, ``max_unit``, ``reserved``, " "``step_size``) of resource provider inventories." msgstr "" #: ../../:545 msgid "" "New configuration options for neutron-sriov-agent under section " "``[sriov_nic]``: ``resource_provider_bandwidths`` and " "``resource_provider_inventory_defaults``. The former controls the ``total`` " "(available bandwidth) field of the physical network interface resource " "provider inventories. It defaults to not creating resource providers in " "Placement. The latter can be used to tune the other fields " "(``allocation_ratio``, ``min_unit``, ``max_unit``, ``reserved``, " "``step_size``) of resource provider inventories." msgstr "" #: ../../:421 msgid "" "New default API policies are not enabled by default. A cloud operator can " "enable them by setting ``oslo_policy/enforce_new_defaults`` to ``true`` in " "the Neutron config file. It is also possible to switch the ``oslo_policy/" "enforce_scope`` config option to ``true`` but currently Neutron does not " "support any system scope APIs. All Neutron API policies are currently " "project scoped so setting ``oslo_policy/enforce_scope`` to ``true`` will " "cause ``Forbidden`` responses to any API calls made with the system scope " "token." msgstr "" #: ../../:464 msgid "" "New framework for ``neutron-status upgrade check`` command is added. This " "framework allows adding various checks which can be run before a Neutron " "upgrade to ensure if the upgrade can be performed safely. Stadium and 3rd " "party projects can register their own checks to this new neutron-status CLI " "tool using entrypoints in ``neutron.status.upgrade.checks`` namespace." msgstr "" #: ../../:496 msgid "" "New security groups firewall driver is introduced. It's based on OpenFlow " "using connection tracking." msgstr "" #: ../../:653 msgid "" "New service plugin and openvswitch agent extension could be configured in " "order to enable Local IP feature: ``local_ip``" msgstr "" #: ../../:469 unmaintained/wallaby>:122 #: unmaintained/xena>:235 unmaintained/yoga>:335 unmaintained/zed>:316 msgid "" "Normalise OVN agent heartbeat timestamp format to match other agent types. " "This fixes parsing of ``GET /v2.0/agents`` for some clients, such as " "gophercloud." msgstr "" #: ../../:488 msgid "" "Now it is possible to define a gateway IP when creating a subnet using a " "subnet pool. If the gateway IP can be allocated in one of the subnet pool " "available subnets, this subnet is created; otherwise a ``Conflict`` " "exception is raised." msgstr "" #: ../../:242 msgid "" "Now setting ``[DEFAULT] rpc_workers = 0`` completely disables rpc workers. " "In a deployment with additional agents, like the dhcp-agent, this option " "should be set to a positive value. Note that all notifications from neutron-" "server to agents were disabled when ``[DEFAULT] rpc_workers = 0`` is set in " "22.0.0 release, so this was the requiremenet actually added in that release." msgstr "" #: ../../:479 msgid "" "Now that rootwrap daemon mode is supported for XenServer, the ``neutron-" "rootwrap-xen-dom0`` script is deprecated and will be removed in a next " "release." msgstr "" #: ../../:183 stable/2023.2>:421 #: unmaintained/wallaby>:146 unmaintained/xena>:95 unmaintained/yoga>:67 #: unmaintained/zed>:122 msgid "" "Now the ML2/OVN trunk driver prevents a trunk creation if the parent port is " "already bound. In the same way, if a parent port being used in a trunk is " "bound, the trunk cannot be deleted." msgstr "" #: ../../:219 msgid "OFAgent has been removed in the Newton cycle." msgstr "" #: ../../:280 msgid "OFAgent is decomposed and deprecated in the Mitaka cycle." msgstr "" #: ../../:506 msgid "" "OSprofiler support requires passing of trace information between various " "OpenStack services. This information is securely signed by one of HMAC keys, " "defined in neutron.conf configuration file. To allow cross-project tracing " "user should use the key, that is common among all OpenStack services he or " "she wants to trace." msgstr "" #: ../../:373 msgid "" "OSprofiler support was introduced. To allow its usage the api-paste.ini file " "needs to be modified to contain osprofiler middleware. Also `[profiler]` " "section needs to be added to the neutron.conf file with `enabled`, " "`hmac_keys` and `trace_sqlalchemy` flags defined." msgstr "" #: ../../:106 stable/2023.2>:96 #: stable/2024.1>:433 msgid "OVN L3 service plugin (``ovn-router``)" msgstr "" #: ../../:580 msgid "" "OVN driver now supports VXLAN type for networks. This requires OVN version " "to be 20.09 or newer." msgstr "" #: ../../:669 msgid "" "OVN driver now uses stateless NAT for floating IP implementation. This " "allows to avoid hitting conntrack, potentially improving performance and " "also allowing to offload NAT rules to hardware." msgstr "" #: ../../:403 unmaintained/zed>:610 msgid "" "OVN driver reverted to using stateful NAT for floating IP implementation. " "The previous switch to stateless didn't materialize the expected performance " "benefits and instead introduced problems with potential hardware offloading." msgstr "" #: ../../:108 unmaintained/victoria>:123 #: unmaintained/wallaby>:360 unmaintained/xena>:423 unmaintained/yoga>:658 msgid "" "OVN mechanism driver allows only to have one physical network per bridge." msgstr "" #: ../../:497 msgid "" "OVN mechanism driver has now got config option " "``allow_stateless_action_supported`` which allows manually disable " "``stateful-security-group`` API extension in case when OVN older than 21.06 " "is used because support for ``allow-stateful`` action in OVN's ACL was added " "in OVN 21.06. By default this option is set to ``True`` so ``stateful-" "security-group`` API extension is enabled. If this option is set to ``True`` " "and OVN < 21.06 is used, Neutron will fallback to the statefull ACLs even if " "SG is set to be stateless in Neutron database." msgstr "" #: ../../:20 unmaintained/xena>:14 #: unmaintained/yoga>:393 unmaintained/zed>:408 msgid "OVN mechanism driver refuses to bind a port to a dead agent." msgstr "" #: ../../:22 current msgid "" "OVN routers can be attached to tunnelled external gateway networks. The " "Logical Router is pinned to a gateway chassis, instead of the gateway " "Logical Router Port. The mechanism driver monitors the status of the gateway " "chassis to re-schedule the Logical Router in case of failure, providing high " "availability." msgstr "" #: ../../:147 msgid "" "OVN routers now expose the \"distributed\" flag depending on the " "configuration option ``enable_distributed_floating_ip``. Because this is a " "common configuration option, all routers will expose the same value. This " "value can flap if the Neutron API is restarted and the configuration option " "changes. NOTE: Once the RFE that allows us to define the distributed flag " "per floating IP address is implemented in ML2/OVN, this flag will be useless " "(no Launchpad bug has been created yet for this RFE, that is only a proposed " "idea during several PTGs)." msgstr "" #: ../../:530 msgid "" "OVS firewall driver doesn't work well with other features using openflow." msgstr "" #: ../../:686 msgid "" "OVS firewall driver requires OVS 2.5 version or higher with linux kernel 4.3 " "or higher. More info at `OVS github page `_." msgstr "" #: ../../:241 msgid "" "Obsolete ``oslo.messaging.notify.drivers`` entrypoints that were left in " "tree for backwards compatibility with pre-Icehouse releases have been " "removed. Those are ``neutron.openstack.common.notifier.log_notifier``, " "``neutron.openstack.common.notifier.no_op_notifier``, ``neutron.openstack." "common.notifier.test_notifier``, ``neutron.openstack.common.notifier." "rpc_notifier2``, ``neutron.openstack.common.notifier.rpc_notifier``. Use " "values provided by ``oslo.messaging`` library to configure notification " "drivers." msgstr "" #: ../../:660 msgid "Old API policies are deprecated now. They will be removed in future." msgstr "" #: ../../:324 msgid "" "Old role ``advsvc`` used in the Neutron API policies is now deprecated. New " "``service`` role should be used for service-to-service communication." msgstr "" #: ../../:387 stable/rocky>:566 msgid "" "On an upgrade, conntrack entries will now be cleaned-up in a worker thread, " "instead of in the calling thread." msgstr "" #: ../../:229 msgid "" "On upgrade, IPv6 addresses in DHCP namespaces that have been created " "dynamically via SLAAC will be removed, and static IPv6 addresses will be " "added instead." msgstr "" #: ../../:24 msgid "" "On upgrade, IPv6 addresses in the DHCP namespaces that have been created " "dynmically via SLAAC will be removed, and a static IPv6 address will be " "added instead." msgstr "" #: ../../:364 msgid "" "Once Nova takes advantage of this feature, a user can launch an instance " "without explicitly provisioning network resources." msgstr "" #: ../../:518 msgid "" "Only creation of dvr/ha routers is currently supported. Upgrade from other " "types of routers to dvr/ha router is not supported on this release." msgstr "" #: ../../:614 msgid "" "Operator can now use new CLI tool ``neutron-status upgrade check`` to check " "if Neutron deployment can be safely upgraded from N-1 to N release." msgstr "" #: ../../:581 msgid "" "Operators can disable this feature if they want to maintain backward-" "compatibility. If they choose to do that, the API extension ``filter-" "validation`` will not be present and the API behavior is unchanged." msgstr "" #: ../../:168 unmaintained/wallaby>:516 msgid "Operators can turn on this feature via the configuration option::" msgstr "" #: ../../:180 stable/newton>:570 msgid "" "Operators may want to tune the ``max_overflow`` and " "``wsgi_default_pool_size`` configuration options according to the " "investigations outlined in this `mailing list post `_. The default value " "of ``wsgi_default_pool_size`` inherits from that of oslo.config, which is " "currently 100. This is a change in default from the previous Neutron-" "specific value of 1000." msgstr "" #: ../../:540 msgid "" "Operators using the ML2 plug-in with 'path_mtu' defaulting to 0 may need to " "perform a database migration to update the MTU for existing networks and " "possibly disable existing workarounds for MTU problems such as increasing " "the physical network MTU to 1550." msgstr "" #: ../../:544 msgid "" "Operators using the ML2 plug-in with existing data may need to perform a " "database migration to update the MTU for existing networks" msgstr "" #: ../../:44 current stable/2023.1>:100 #: stable/2023.1>:207 stable/2023.1>:483 stable/2023.2>:90 stable/2023.2>:454 #: stable/2024.1>:10 stable/2024.1>:427 stable/liberty>:90 stable/liberty>:289 #: stable/mitaka>:136 stable/mitaka>:176 stable/mitaka>:658 stable/newton>:562 #: stable/ocata>:70 stable/ocata>:296 stable/pike>:22 stable/pike>:105 #: stable/pike>:514 stable/queens>:128 stable/queens>:195 stable/queens>:303 #: stable/rocky>:116 stable/rocky>:164 stable/rocky>:181 stable/rocky>:275 #: stable/rocky>:641 stable/stein>:34 stable/stein>:275 stable/stein>:303 #: stable/stein>:410 stable/stein>:783 stable/train>:89 stable/train>:367 #: stable/train>:397 stable/train>:646 stable/ussuri>:97 stable/ussuri>:163 #: stable/ussuri>:649 unmaintained/victoria>:89 unmaintained/victoria>:119 #: unmaintained/victoria>:223 unmaintained/victoria>:254 #: unmaintained/victoria>:516 unmaintained/wallaby>:192 #: unmaintained/wallaby>:356 unmaintained/wallaby>:696 unmaintained/xena>:119 #: unmaintained/xena>:249 unmaintained/xena>:352 unmaintained/xena>:419 #: unmaintained/xena>:704 unmaintained/yoga>:25 unmaintained/yoga>:82 #: unmaintained/yoga>:136 unmaintained/yoga>:356 unmaintained/yoga>:399 #: unmaintained/yoga>:625 unmaintained/zed>:65 unmaintained/zed>:146 #: unmaintained/zed>:330 unmaintained/zed>:587 msgid "Other Notes" msgstr "" #: ../../:425 msgid "" "Ovn configuration items \"ovn_nb_connection\" and \"ovn_sb_connection\" can " "set multiple addresses separated by commas. Setting NB/SB \"connection\" " "inactivity probe can also work well, if multiple connection be specified." msgstr "" #: ../../:112 stable/rocky>:156 stable/stein>:267 #: stable/train>:359 stable/ussuri>:641 msgid "" "Owners of security groups now see all security group rules which belong to " "the security group, even if the rule was created by the admin user. Fixes " "bug `1824248 `_." msgstr "" #: ../../:418 msgid "Perform validation on filter parameters on listing resources." msgstr "" #: ../../:371 msgid "" "Please note that the metadata IPv6 address (being link-local) is not " "complete without a zone identifier (in a Linux guest that is usually the " "interface name concatenated after a percent sign). Please also note that in " "URLs you should URL-encode the percent sign itself. For example, assuming " "that the primary network interface in the guest is ``eth0`` the base " "metadata URL is ``http://[fe80::a9fe:a9fe%25eth0]:80/``." msgstr "" #: ../../:329 msgid "" "Please read the `Neutron RBAC spec `_. for more information on " "how Neutron RBAC works and can be configured." msgstr "" #: ../../:662 msgid "" "Please read the `OpenStack Networking Guide `_." msgstr "" #: ../../:297 msgid "" "Please read the `enabling new agents specification `_ " "for more information on how to manually schedule agents." msgstr "" #: ../../:235 msgid "Pluggable IPAM enables the use of alternate or third-party IPAM." msgstr "" #: ../../:476 msgid "" "PluginReportStateAPI has a new version (1.3) in which " "has_alive_neutron_server() no longer returns always True, but performs a DB " "connection check and returns True/False accordingly. Using this, an agent " "can check not just MQ but the server's DB connectivity too." msgstr "" #: ../../:107 stable/2023.2>:97 #: stable/2024.1>:434 msgid "Port forwarding service plugin (``port_forwarding``)" msgstr "" #: ../../:493 msgid "" "Port forwardings can only be created for floating IPs that are managed by " "centralized routers in the network node: legacy, HA, DVR+HA." msgstr "" #: ../../:372 msgid "" "Ports can have a dns_name attribute associated with them. The network where " "a port is created can have a dns_domain associated with it" msgstr "" #: ../../:247 stable/queens>:428 msgid "" "Ports have now a ``dns_domain`` attribute. A port's ``dns_domain`` attribute " "has precedence over the network's ``dns_domain`` from the point of view of " "publishing it to the external DNS service." msgstr "" #: ../../:200 msgid "" "Ports now have a ``hints`` attribute, in which backend specific tuning " "options can be passed to Neutron. The availability of the ``hints`` " "attribute is signaled by the ``port-hints`` extension. The ``hints`` " "attribute is admin-only by default. Its value is a dict, keyed by mechanism " "driver aliases. The possible values are defined by the mechanism drivers. An " "admin user can ask for a hint in a port create or update request. As the " "name suggests a hint is not a demand - Neutron applies the hint when it can, " "but it is free to ignore it, when it can't." msgstr "" #: ../../:119 stable/mitaka>:392 msgid "" "Ports that failed to bind when an L2 agent was offline can now recover after " "the agent is back online." msgstr "" #: ../../:27 stable/liberty>:25 #: stable/liberty>:105 stable/liberty>:130 stable/liberty>:155 #: stable/mitaka>:45 stable/mitaka>:99 stable/mitaka>:151 stable/mitaka>:191 #: stable/newton>:10 stable/newton>:45 stable/newton>:148 stable/ocata>:147 #: stable/pike>:225 stable/queens>:373 stable/queens>:409 stable/rocky>:399 #: stable/stein>:435 stable/ussuri>:325 unmaintained/victoria>:312 #: unmaintained/zed>:351 msgid "Prelude" msgstr "" #: ../../:608 stable/stein>:395 msgid "" "Previously a network's ``dns_domain`` attribute was ignored by the DHCP " "agent. With this release, OpenStack deployments using Neutron's DHCP agent " "will be able to specify a per network ``dns_domain`` and have instances " "configure that domain in their dns resolver configuration files (Linux's /" "etc/resolv.conf) to allow for local partial DNS lookups. The per-network " "``dns_domain`` value will override the DHCP agent's default ``dns_domain`` " "configuration value. Note that it's also possible to update a network's " "``dns_domain``, and that new value will be propogated to new instances or " "when instances renew their DHCP lease. However, existing leases will live on " "with the old ``dns_domain`` value." msgstr "" #: ../../:512 msgid "" "Previously deprecated configuration option ``allow_overlapping_ips`` is now " "removed." msgstr "" #: ../../:423 msgid "" "Previously, ``neutron-server`` was using configuration values for ``oslo." "db`` that were different from library defaults. Specifically, it used the " "following values when they were not overridden in configuration files: " "``max_pool_size`` = 10, ``max_overflow`` = 20, ``pool_timeout`` = 10. In " "this release, ``neutron-server`` instead relies on default values defined by " "the library itself. If you rely on old default values, you may need to " "adjust your configuration files to explicitly set the new values." msgstr "" #: ../../:620 msgid "" "Prior to Mitaka, name resolution in instances requires specifying DNS " "resolvers via the 'dnsmasq_dns_servers' option in the DHCP agent " "configuration file or via neutron subnet options. In this case, the data " "plane must provide connectivity between instances and upstream DNS " "resolvers. Omitting both of these methods causes the dnsmasq service to " "offer the IP address on which it resides to instances for name resolution. " "However, the static dnsmasq '--no-resolv' process argument prevents name " "resolution via dnsmasq, leaving instances without name resolution. Mitaka " "introduces the 'dnsmasq_local_resolv' option, default value False to " "preserve backward-compatibility, that enables the dnsmasq service to provide " "name resolution for instances via DNS resolvers on the host running the DHCP " "agent. In this case, the data plane must provide connectivity between the " "host and upstream DNS resolvers rather than between the instances and " "upstream DNS resolvers. Specifying DNS resolvers via the " "'dnsmasq_dns_servers' option in the DHCP agent configuration overrides the " "'dnsmasq_local_resolv' option for all subnets using the DHCP agent." msgstr "" #: ../../:612 msgid "" "Prior to Mitaka, the settings that control the frequency of router " "advertisements transmitted by the radvd daemon were not able to be adjusted. " "Larger deployments may wish to decrease the frequency in which radvd sends " "multicast traffic. The 'min_rtr_adv_interval' and 'max_rtr_adv_interval' " "settings in the L3 agent configuration file map directly to the " "'MinRtrAdvInterval' and 'MaxRtrAdvInterval' in the generated radvd.conf " "file. Consult the manpage for radvd.conf for more detailed information." msgstr "" #: ../../:204 msgid "" "Prior to Newton, the default option for 'ovsdb_interface' was 'vsctl'. In " "Newton 'ovsdb_interface' defaults to 'native'. This change switches the way " "of communication with OVSDB from the ovs-vsctl tool to Open vSwitch python " "api to improve out-of-the-box performance for typical deployments." msgstr "" #: ../../:189 msgid "" "Prior to Newton, the neutron-openvswitch-agent used 'ovs-ofctl' of_interface " "driver by default. In Newton, 'of_interface' defaults to 'native'. This " "mostly eliminates spawning ovs-ofctl and improves performance a little." msgstr "" #: ../../:571 msgid "" "Prior to the upgrade, if a request contains an unknown or unsupported " "parameter, the server will silently ignore the invalid input. After the " "upgrade, the server will return a 400 Bad Request response instead." msgstr "" #: ../../:306 msgid "" "Proactively create DVR floating IP namespace on all compute nodes when a " "gateway is configured." msgstr "" #: ../../:194 msgid "" "Properly calculate overlay (tunnel) protocol overhead for environments using " "IPv4 or IPv6 endpoints. The ML2 plug-in configuration file contains a new " "configuration option, 'overlay_ip_version', in the '[ml2]' section that " "indicates the IP version of all overlay network endpoints. Use '4' for IPv4 " "and '6' for IPv6. Defaults to '4'. Additionally, all layer-2 agents must use " "the same IP version for endpoints." msgstr "" #: ../../:333 msgid "Python 2 is no longer supported by Neutron, Python 3.6 and 3.7 are." msgstr "" #: ../../:469 msgid "" "Python 2.7 support has been dropped. The minimum version of Python now " "supported by Neutron is Python 3.6." msgstr "" #: ../../:517 msgid "" "Python 3.6 & 3.7 support has been dropped. The minimum version of Python now " "supported is Python 3.8." msgstr "" #: ../../:456 msgid "QoS rule type list accepts two filter flags:" msgstr "" #: ../../:240 msgid "RBAC support for QoS policies" msgstr "" #: ../../:770 msgid "" "Reject QoS minimum bandwidth rule operations on ports, networks without " "physnet, see bug `1819029 `_." msgstr "" #: ../../:557 msgid "" "Reject any router route or gateway update if not all route nexthops have " "connectivity with any gateway subnets CIDRs; in other words, all route " "nexthops IP addresses should belong to one gateway subnet CIDR." msgstr "" #: ../../:14 current stable/2023.1>:28 stable/2023.2>:28 #: stable/2024.1>:114 unmaintained/zed>:14 msgid "" "Remote address group support was added to the iptables-based firewall " "drivers (IptablesFirewallDriver and OVSHybridIptablesFirewallDriver), " "Previously it was only available in the OVSFirewallDriver. For more " "information, see bug `2058138 `_." msgstr "" #: ../../:437 msgid "Remove 'quota_items' configuration option from neutron.conf file." msgstr "" #: ../../:224 msgid "" "Remove 'quota_items' configuration option from neutron.conf file. This " "option was deprecated since Liberty release and has no effect now." msgstr "" #: ../../:441 msgid "Remove 'router_id' configuration option from the l3_agent.ini file." msgstr "" #: ../../:229 msgid "" "Remove 'router_id' configuration option from the l3_agent.ini file. " "'router_id' option has been defined in order to associate an l3-agent to a " "specific router when use_namespaces=False. It was deprecated after " "use_namespaces was removed in Mitaka release." msgstr "" #: ../../:300 msgid "" "Remove ``[DEFAULT] ovs_integration_bridge`` configuration option, which was " "deprecated in the 'Ussuri' release, as it was a duplicate of ``[OVS] " "integration_bridge``." msgstr "" #: ../../:653 msgid "" "Removed ``XenAPI`` support in Neutron. This driver is no longer supported in " "Nova and Neutron. The configuration options have been marked as \"deprecated " "for removal\" and will be removed in X release." msgstr "" #: ../../:159 msgid "" "Removed support for OVN versions under 20.09. The \"Chassis_Private\" OVN " "Southbound table is expected in the database definition." msgstr "" #: ../../:666 msgid "" "Report external dns service OverQuota exception as new neutron " "ConflictException (409) i.e. ExternalDNSOverQuota. Report the failure as " "\"External DNS Quota exceeded for resources: recordset\"." msgstr "" #: ../../:477 msgid "" "Report packet processing capacity on the OVS agent resource provider as the " "new ``NET_PACKET_RATE_KILOPACKET_PER_SEC``, " "``NET_PACKET_RATE_EGR_KILOPACKET_PER_SEC`` or " "``NET_PACKET_RATE_IGR_KILOPACKET_PER_SEC`` resource inventory. This is " "similar to how the bandwidth resource is reported today. The former is used " "for non-hardware-offloaded OVS deployments, where packets processed from " "both ingress and egress directions are handled by the same set of CPU cores. " "Remaining inventories are used for hardware-offloaded OVS, where the " "incoming and outgoing packets are handled by independent hardware resources." msgstr "" #: ../../:140 stable/newton>:578 msgid "" "Requires OVS 2.5+ version or higher with linux kernel 4.3 or higher. More " "info at `OVS github page `_." msgstr "" #: ../../:206 stable/ussuri>:399 msgid "" "Reserving multiple addresses for a host eases problems related to network " "and chain-booting where each step in the boot process requests an address " "using different DUID/IAID combinations. With a single address, only one gets " "the \"static\" address and the boot process will fail on the following " "steps. By reserving enough addresses for all the stages of the boot process " "this problem is resolved. (See bug: `#1861032 `_)" msgstr "" #: ../../:181 stable/pike>:322 msgid "" "Resource tag mechanism now supports subnet, port, subnetpool and router " "resources." msgstr "" #: ../../:263 msgid "" "Return code for `quota delete` for a tenant whose quota has not been " "previously defined has been changed from 204 to 404." msgstr "" #: ../../:243 msgid "" "Router high availability (L3 HA / VRRP) now works when layer 2 population " "(l2pop) is enabled." msgstr "" #: ../../:231 stable/ussuri>:505 msgid "" "SR-IOV agent code no longer supports old kernels (<3.13) for MacVtap ports. " "This change is not expected to affect existing deployments since most OS " "distributions already have the relevant kernel patches. In addition, latest " "major release of all Supported distributions already have a newer kernel." msgstr "" #: ../../:548 msgid "" "SR-IOV agent now can handle ports from different networks with the same MAC " "addresses. This feature implies an upgrade in the agent and the server RPC " "version (see ``neutron.plugins.ml2.rpc.RpcCallbacks`` version 1.9). Some " "agent RPC methods have been updated to pass not only the device MAC address " "but the PCI slot too. In case of having more than one port with the same MAC " "address, the PCI slot will discriminate the requested port." msgstr "" #: ../../:281 msgid "SR-IOV now supports egress minimum bandwidth configuration." msgstr "" #: ../../:209 msgid "Schedule networks on dhcp-agents with access to network" msgstr "" #: ../../:126 stable/newton>:277 msgid "" "Second option `ca_cert` allows setting path to a valid cert file. Default is " "None." msgstr "" #: ../../:502 stable/queens>:45 #: stable/queens>:151 stable/rocky>:52 stable/rocky>:203 stable/stein>:22 #: stable/stein>:166 stable/stein>:325 stable/train>:44 stable/train>:257 #: stable/train>:560 stable/ussuri>:119 stable/ussuri>:536 #: unmaintained/victoria>:156 unmaintained/wallaby>:393 unmaintained/xena>:650 msgid "Security Issues" msgstr "" #: ../../:627 msgid "" "Security group rule code has been changed to better detect duplicate rules " "by standardizing on ``ipv6-icmp`` as the protocol field value for IPv6 ICMP " "rules. The legacy names ``icmpv6`` and ``icmp`` can still be used in API " "POST calls, but API GET calls will return ``ipv6-icmp``. Partial fix for bug " "`1582500 `_." msgstr "" #: ../../:474 msgid "" "Security group rule has now new, read only attribute ``normalized_cidr`` " "which contains network address from the CIDR provided in the " "``remote_ip_prefix`` attribute. This new attribute shows actual CIDR used by " "backend firewall drivers." msgstr "" #: ../../:400 msgid "" "Security group rules, networks, ports, routers, floating IPs, and subnet " "pools may now contain an optional description which allows users to easily " "store details about entities." msgstr "" #: ../../:528 msgid "" "Security groups are now supported via the network RBAC mechanism. Please " "refer to the admin guide for further details." msgstr "" #: ../../:338 msgid "" "Security groups can now be set as ``stateful``. Conntrack will not be used " "for any rules from such a group. This is currently supported only by the " "``iptables`` and ``iptables_hybrid`` drivers." msgstr "" #: ../../:283 msgid "" "See `bug 1365476 `_ and " "`bug 1481443 `_ for more " "details on the fix L3 HA and L2 population." msgstr "" #: ../../:394 msgid "" "See bug `1881297 `_ for " "more details." msgstr "" #: ../../:380 msgid "" "See bug `1988069 `_ for " "more information." msgstr "" #: ../../:24 msgid "" "Server notifies L3 HA agents when HA router interface port status becomes " "active. Then L3 HA agents spawn keepalived process. So, server has to be " "restarted before the L3 agents during upgrade." msgstr "" #: ../../:160 stable/newton>:239 msgid "Several NICs per physical network can be used with SR-IOV." msgstr "" #: ../../:487 unmaintained/wallaby>:231 #: unmaintained/xena>:356 unmaintained/yoga>:372 unmaintained/zed>:334 msgid "" "Since OVN 20.06, the \"Chassis\" register configuration is stored in the " "\"other_config\" field and replicated into \"external_ids\". This " "replication is stopped in OVN 22.09. The ML2/OVN plugin tries to retrieve " "the \"Chassis\" configuration from the \"other_config\" field first; if this " "field does not exist (in OVN versions before 20.06), the plugin will use " "\"external_ids\" field instead. Neutron will be compatible with the " "different OVN versions (with and without \"other_config\" field)." msgstr "" #: ../../:453 msgid "" "Since ``haproxy`` was not used before by ``neutron-l3-agent`` and ``neutron-" "dhcp-agent``, rootwrap filters for both agents have to be copied over when " "upgrading." msgstr "" #: ../../:218 stable/ussuri>:411 msgid "" "Since the new configuration format is invalid in previous versions of " "dnsmasq this feauture is *disabled* by default. To *enable* the feature set " "the option ``dnsmasq_enable_addr6_list`` in DHCP agent configuration to " "``True``." msgstr "" #: ../../:467 msgid "" "Since this version, the support for stateless security groups is mandatory. " "The minimum OVN NB schema version must be 5.17." msgstr "" #: ../../:365 msgid "" "Some Neutron features are not supported due to lack of resources or " "technical expertise to maintain them. As they arise, those features will be " "marked as experimental by the Neutron core team. Deployers will be able to " "continue using experimental features by explicitly enabling them in the " "'experimental' section of neutron.conf. The ML2 linuxbridge driver is the " "first feature to be marked as experimental. To continue using it, deployers " "have to set to True the 'linuxbridge' option in the 'experimental' section " "of neutron.conf." msgstr "" #: ../../:130 stable/pike>:281 msgid "" "Some scenario tests require advanced ``Glance`` images (for example, " "``Ubuntu`` or ``CentOS``) in order to pass. They are now skipped by default. " "If you need to execute those tests, please configure ``tempest.conf`` to use " "an advanced image, and set ``image_is_advanced`` in " "``neutron_plugin_options`` section of ``tempest.conf`` file to ``True``. The " "first scenario test case that requires the new option set to execute is " "``test_trunk``." msgstr "" #: ../../:474 msgid "" "Special keywords ````, ````, ```` and " "```` can be used in the network's, port's and floating IP's " "``dns_domain`` attribute. Those special keywords will be replaced by the " "corresponding data from the request context. With that cloud admin can " "define dns_domain for shared network and ports which belongs to the other " "projects in the way that each project can use separate DNS zones which needs " "to be pre-created by users. To enable this feature ``dns_domain_keywords`` " "ML2 plugin extension has to be enabled in the Neutron config. Enabling " "multiple dns_integration extensions at the same time leads to an error." msgstr "" #: ../../:484 msgid "" "SriovNicSwitchMechanismDriver driver now exposes a new VIF type " "'hostdev_physical' for ports with vnic type 'direct-physical' (used for SR-" "IOV PF passthrough). This will enable Nova to provision PFs as Neutron ports." msgstr "" #: ../../:293 msgid "Start using reno to manage release notes." msgstr "" #: ../../:538 msgid "" "Starting from this release, neutron server will perform validation on filter " "parameters on list requests. Neutron will return a 400 response if the " "request contains invalid filter parameters. The list of valid parameters is " "documented in the neutron API reference." msgstr "" #: ../../:231 msgid "" "Starting with OVN version v21.12.0, OVN replies to ARP requests for ports " "that are in a DOWN status. It does not reply in versions older than " "v21.12.0. In order to keep the same behavior in Neutron, the default OVN " "behavior is overridden by Neutron and Neutron ports will no longer reply to " "ARP packets if the ports are in a DOWN state. If it is required to reply to " "ARP for such ports, the config option ``ignore_lsp_down`` from " "``[ovn_nb_global]`` section can be set to True in the Neutron config. It is " "set to False by default." msgstr "" #: ../../:289 unmaintained/wallaby>:670 msgid "" "Stop sending agent heartbeat from ovs agent when it detects OVS is dead. " "This helps to alarm cloud operators that there is something wrong on the " "given node." msgstr "" #: ../../:385 msgid "" "Subnetpool is now supported via the network RBAC mechanism. Please refer to " "the admin guide for further details." msgstr "" #: ../../:290 msgid "" "Subnets now have a new property 'service_types'. This is a list of port " "device owners, such that only ports with a matching device owner will be " "given an IP from this subnet. If no matching service subnet exists for the " "given device owner, or no service subnets have been defined on the network, " "the port will be assigned an IP from a subnet with no service-types. This " "preserves backwards compatibility with older deployments." msgstr "" #: ../../:372 msgid "" "Subport segmentation details can now accept ``inherit`` as segmentation type " "during a trunk creation/update request. The trunk plugin will determine the " "segmentation type and ID and replace them with those of the network to which " "the port is connected. Only single-segment VLAN networks are set to have " "expected and correct results at this point." msgstr "" #: ../../:449 msgid "Support alias end points for rules in QoS API." msgstr "" #: ../../:155 stable/newton>:174 msgid "Support configuration of greenthreads pool for WSGI." msgstr "" #: ../../:787 msgid "" "Support fetching specific db column in OVO. A new method ``get_values`` is " "added to neutron object classes. This method can be leveraged to fetch " "specific field of the object." msgstr "" #: ../../:391 msgid "" "Support for IPv6 NDP proxy has been added. Read the related `specification " "`_ for more details." msgstr "" #: ../../:108 stable/newton>:199 msgid "Support for IPv6 addresses as tunnel endpoints in OVS." msgstr "" #: ../../:465 msgid "Support for L3 conntrack helpers has been added." msgstr "" #: ../../:34 stable/mitaka>:315 msgid "Support for MTU selection and advertisement." msgstr "" #: ../../:336 msgid "" "Support for Neutron on Windows operating systems is deprecated since 2023.2 " "release and will be removed in 2024.2." msgstr "" #: ../../:122 msgid "" "Support for PXE baremetal provisioning using OVN's built-in DHCP server has " "been added for IPv6." msgstr "" #: ../../:397 msgid "" "Support for baremetal provisioning using OVN's built-in DHCP server has been " "added for IPv4." msgstr "" #: ../../:349 msgid "Support for floating IPs port forwarding has been added to OVN backend." msgstr "" #: ../../:475 msgid "Support for floating IPs port forwarding has been added." msgstr "" #: ../../:481 msgid "" "Support for network logging based on security groups added to OVN backend. " "For more information see bug `1914757 `_." msgstr "" #: ../../:46 msgid "" "Support for new ``service`` role is added to the Neutron API policies as " "part of the Secure-RBAC initiative. This new role is designed to be used for " "the service-to-service communication." msgstr "" #: ../../:599 msgid "" "Support for new policies and system scope context is experimentatal in " "Neutron. When config option ``enforce_new_defaults`` is enabled in Neutron, " "new default rules will be enforced and things may not work properly in some " "cases." msgstr "" #: ../../:313 unmaintained/xena>:377 #: unmaintained/yoga>:597 msgid "" "Support for the extensions ``dns_domain_ports`` and " "``subnet_dns_publish_fixed_ip`` belonging to the DNS integration is now " "properly announced by the OVN driver. See bug `1947127 `_" msgstr "" #: ../../:225 msgid "Support integration with external DNS service." msgstr "" #: ../../:408 msgid "Support multiple bindings for compute owned ports." msgstr "" #: ../../:528 msgid "" "Support port filtering on security group IDs. The feature can be used if " "'port-security-group-filtering' extension is available." msgstr "" #: ../../:525 msgid "" "Support stateless security groups with the latest OVN 21.06+. The " "stateful=False security groups are mapped to the new \"allow-stateless\" OVN " "ACL verb." msgstr "" #: ../../:491 msgid "Support substring matching when filtering ports by IP address." msgstr "" #: ../../:451 msgid "" "Tenants who can access shared networks, can now create/update ports on a " "specified subnet instead of the default subnet. This is now the default " "behavior and can be changed by modifying policy.json file." msgstr "" #: ../../:474 msgid "" "Terminology such as ``master`` and ``slave`` have been replaced with more " "inclusive words, such as ``primary`` and ``backup`` wherever possible." msgstr "" #: ../../:220 msgid "" "The \"get-me-a-network\" feature simplifies the process for launching an " "instance with basic network connectivity (via an externally connected " "private tenant network)." msgstr "" #: ../../:253 msgid "" "The \"vlan-aware-vms\" feature allows Nova users to launch VMs on a single " "port (trunk parent port) that connects multiple Neutron logical networks " "together." msgstr "" #: ../../:464 msgid "" "The 'advertise_mtu' option is deprecated and will be removed in Ocata. There " "should be no use case to disable the feature, hence the option is considered " "redundant. DHCP and L3 agents will continue advertising MTU values to " "instances. Other plugins not using those agents are also encouraged to " "advertise MTU to instances. The actual implementation of MTU advertisement " "depends on the plugin in use, but it's assumed that at least DHCP option for " "IPv4 clients and Router Advertisements for IPv6 clients is supported." msgstr "" #: ../../:309 msgid "" "The 'external_network_bridge' option for the L3 agent has been deprecated in " "favor of a bridge_mapping with a physnet. For more information, see the " "`Network Node `_ section of this scenario in the networking guide." msgstr "" #: ../../:590 msgid "" "The 'force_gateway_on_subnet' option is deprecated and will be removed in " "the 'Newton' cycle." msgstr "" #: ../../:594 msgid "" "The 'network_device_mtu' option is deprecated and will be removed in the " "'Newton' cycle. Please use the system-wide segment_mtu setting which the " "agents will take into account when wiring VIFs." msgstr "" #: ../../:170 stable/newton>:552 msgid "" "The 'physical_device_mappings' of sriov_nic configuration now can accept " "more than one NIC per physical network. For example, if 'physnet2' is " "connected to enp1s0f0 and enp1s0f1, 'physnet2:enp1s0f0,physnet2:enp1s0f1' " "will be a valid option." msgstr "" #: ../../:602 msgid "" "The 'segment_mtu' option of the ML2 configuration has been deprecated and " "replaced with the 'global_physnet_mtu' option in the main Neutron " "configuration. This option is meant to be used by all plugins for an " "operator to reference their physical network's MTU, regardless of the " "backend plugin. Plugins should access this config option via the " "'get_deployment_physnet_mtu' method added to neutron.plugins.common.utils to " "avoid being broken on any potential renames in the future." msgstr "" #: ../../:480 msgid "" "The 'supported_pci_vendor_devs' option is deprecated in Newton and will be " "removed in Ocata. The validation of supported pci vendors is done in nova-" "scheduler through the pci_passthrough_whitelist option when it selects a " "suitable hypervisor, hence the option is considered redundant." msgstr "" #: ../../:454 msgid "" "The 'timestamp_core' extension has been removed and replaced with the " "'standard-attr-timestamp' extension. Objects will still have timestamps in " "the 'created_at' and 'updated_at' fields, but they will have the timestamp " "appended to the end of them to be consistent with other OpenStack projects." msgstr "" #: ../../:329 msgid "The 16.0.0 release includes many bug fixes and new features." msgstr "" #: ../../:519 msgid "" "The API extension ``uplink_status_propagation`` is introduced to indicate if " "this feature is turned on." msgstr "" #: ../../:321 msgid "" "The Cisco N1kV monolithic plugin is removed in the Liberty release (replaced " "by the ML2 mechanism driver)." msgstr "" #: ../../:432 msgid "" "The DSCP value for outer headers in openvswitch overlay tunnel ports can now " "be set through a configuration option ``dscp`` for both OVS and linuxbridge " "agents." msgstr "" #: ../../:325 msgid "" "The Embrane plugin is deprecated and will be removed in the Mitaka release." msgstr "" #: ../../:301 msgid "" "The FWaaS API is marked as experimental for Liberty. Further, the current " "API will be removed in Mitaka and replaced with a new FWaaS API, which the " "team is in the process of developing." msgstr "" #: ../../:568 msgid "" "The Hyper-V Neutron Agent has been fully decomposed from Neutron. The " "`neutron.plugins.hyperv.agent.security_groups_driver." "HyperVSecurityGroupsDriver` firewall driver has been deprecated and will be " "removed in the 'O' cycle. Update the `neutron_hyperv_agent.conf` files on " "the Hyper-V nodes to use `hyperv.neutron.security_groups_driver." "HyperVSecurityGroupsDriver`, which is the networking_hyperv security groups " "driver." msgstr "" #: ../../:317 msgid "The IBM SDN-VE monolithic plugin is removed in the Liberty release." msgstr "" #: ../../:688 msgid "" "The L2 population ``agent_boot_time`` config option is deprecated in favor " "of the direct RPC agent restart state transfer. It will be removed in the " "``Train`` release." msgstr "" #: ../../:267 msgid "" "The L3 agent ``send_arp_for_ha configuration`` option is deprecated and will " "be removed in Pike. The functionality will remain, and the agent will send " "three gratuitious ARPs whenever a new floating IP is configured." msgstr "" #: ../../:305 msgid "" "The LBaaS V1 API is marked as deprecated and is planned to be removed in a " "future release. Going forward, the LBaaS V2 API should be used." msgstr "" #: ../../:179 msgid "The LBaaS V2 API is no longer experimental. It is now stable." msgstr "" #: ../../:165 msgid "The Linux Bridge agent now supports QoS DSCP marking rules." msgstr "" #: ../../:348 msgid "" "The LinuxBridge agent can now configure basic bandwidth limiting QoS rules " "set for ports and networks. It introduces two new config options for " "LinuxBridge agent. First is 'kernel_hz' option which is value of host kernel " "HZ setting. It is necessary for proper calculation of minimum burst value in " "tbf qdisc setting. Second is 'tbf_latency' which is value of latency to be " "configured in tc-tbf setting. Details about this option can be found in `tc-" "tbf manual `_." msgstr "" #: ../../:205 msgid "The LinuxBridge agent now supports QoS bandwidth limiting." msgstr "" #: ../../:468 msgid "" "The Linuxbridge agent can now be extended by 3rd parties using a pluggable " "mechanism." msgstr "" #: ../../:305 msgid "The Linuxbridge agent now supports l2 agent extensions." msgstr "" #: ../../:84 msgid "" "The Linuxbridge agent now supports the ability to toggle the local ARP " "responder when L2Population is enabled. This ensures compatibility with the " "allowed-address-pairs extension. Closes `bug 1445089 `__." msgstr "" #: ../../:644 msgid "" "The Linuxbridge agent now supports the ability to toggle the local ARP " "responder when L2Population is enabled. This ensures compatibility with the " "allowed-address-pairs extension. closes bug 1445089" msgstr "" #: ../../:545 msgid "" "The ML2 linuxbridge agent has been marked as experimental due to lack of " "resources to maintain it. To continue using it, deployers have to set to " "True the 'linuxbridge' option in the 'experimental' section of neutron.conf" msgstr "" #: ../../:195 msgid "" "The ML2 plug-in supports calculating the MTU for instances using overlay " "networks by subtracting the overlay protocol overhead from the value of " "'path_mtu', ideally the physical (underlying) network MTU, and providing the " "smaller value to instances via DHCP. Prior to Mitaka, 'path_mtu' defaults to " "0 which disables this feature. In Mitaka, 'path_mtu' defaults to 1500, a " "typical MTU for physical networks, to improve the \"out of box\" experience " "for typical deployments." msgstr "" #: ../../:200 msgid "" "The ML2 plug-in supports calculating the MTU for networks that are realized " "as flat or VLAN networks, by consulting the 'segment_mtu' option. Prior to " "Mitaka, 'segment_mtu' defaults to 0 which disables this feature. This " "creates slightly confusing API results when querying Neutron networks, since " "the plugins that support the MTU API extension would return networks with " "the MTU equal to zero. Networks with an MTU of zero make little sense, since " "nothing could ever be transmitted. In Mitaka, 'segment_mtu' now defaults to " "1500 which is the standard MTU for Ethernet networks in order to improve the " "\"out of box\" experience for typical deployments." msgstr "" #: ../../:36 msgid "" "The ML2/OVS and ML2/OVN drivers had inconsistencies on how IGMP was " "configured. Prior to this patch Neutron only exposed a single IGMP " "configuration option (``igmp_snooping_enabled``) and other features such as " "flooding IGMP packets, flooding reports and flooding to unregistered ports " "were hard coded differently in each driver. This patch introduces Neutron " "configuration options for those listed IGMP features. As part of this work, " "default values in the IGMP snooping configuration had to be changed for the " "ML2/OVS backend. Please check in the following sections for more details." msgstr "" #: ../../:333 msgid "" "The Networking API now supports the 'project_id' field in requests and " "responses, for compatibility with the Identity (Keystone) API V3. A new API " "extension, 'project-id', has been added to allow API users to detect if the " "'project_id' field is supported. Note that the 'tenant_id' field is still " "supported, and the two fields are functionally equivalent." msgstr "" #: ../../:363 msgid "" "The Neutron API has been changed to validate network MTU minimums. A " "network's MTU is now only valid if it is the minimum value allowed based on " "the IP version of the associated subnets, 68 for IPv4 and 1280 for IPv6." msgstr "" #: ../../:652 msgid "" "The Neutron API now enforces that ports are a valid option for security " "group rules based on the protocol given, instead of relying on the backend " "firewall driver to do this enforcement, typically silently ignoring the port " "option in the rule. The valid set of whitelisted protocols that support " "ports are TCP, UDP, UDPLITE, SCTP and DCCP. Ports used with other protocols " "will now generate an HTTP 400 error. For more information, see bug `1818385 " "`_." msgstr "" #: ../../:291 msgid "" "The Neutron API now supports conditional updates to resources with the " "'revision_number' attribute by setting the desired revision number in an " "HTTP If-Match header. This allows clients to ensure that a resource hasn't " "been modified since it was retrieved by the client. Support for conditional " "updates on the server can be checked for by looking for the 'revision-if-" "match' extension in the supported extensions." msgstr "" #: ../../:561 msgid "" "The Neutron L3 and DHCP agents now dynamically tune the number of processing " "greenthreads they run based on the number of objects they are managing, with " "the current values for this range being between eight and thirty-two " "threads, which is an increase over the previous static value of eight " "threads. This should help address some of the scaling problems in the " "agents. For more information see bug `1813787 `_." msgstr "" #: ../../:49 stable/newton>:184 msgid "" "The Neutron server no longer needs to be configured with a firewall driver " "and it can support mixed environments of hybrid iptables firewalls and the " "pure OVS firewall." msgstr "" #: ../../:64 stable/newton>:302 msgid "" "The Neutron server now learns the appropriate firewall wiring behavior from " "each OVS agent so it no longer needs to be configured with the " "firewall_driver. This means it also supports multiple agents with different " "types of firewalls." msgstr "" #: ../../:300 msgid "" "The Neutron service enable the API policies (RBAC) new defaults and scope by " "default. The Default value of config options ``[oslo_policy] enforce_scope`` " "and ``[oslo_policy] oslo_policy.enforce_new_defaults`` have been changed to " "``True``." msgstr "" #: ../../:180 msgid "" "The OVN L3 scheduler will assign chassis explicitly configured as gateways " "to the router gateway ports (OVN logical router ports). If no candidates are " "available, the \"neutron-ovn-invalid-chassis\" will be used instead and a " "warning message will be printed in the logs." msgstr "" #: ../../:468 msgid "" "The OVN L3 scheduler will now update lower priorities of exising LRPs in " "case of a chassis change. This can create increased load on OVN during " "chassis shutdown, but improves the load distribution of LRPs." msgstr "" #: ../../:31 msgid "" "The OVN changed support for NAT rules including a new column and auto-" "discovery logic to know about logical router gateway ports for NAT on a " "Logical Router." msgstr "" #: ../../:418 msgid "" "The OVN driver now makes uses of the \"external\" ports concept that was " "introduced by Core OVN. For example, with this work a VM with a SR-IOV port " "attached (VNIC type \"direct\" and no \"switchdev\" capability) will now be " "translated into an \"external\" port which is able reply to packets (e.g " "DHCP) from another host that were bypassed in the hypervisor before. Note " "that, for this first interaction all external ports will belong to the same " "HA group and will be scheduled onto the same node." msgstr "" #: ../../:110 stable/2023.2>:100 #: stable/2024.1>:437 msgid "" "The OVN floating IP traffic is distributed " "(``enable_distributed_floating_ip`` = ``True``)" msgstr "" #: ../../:196 unmaintained/xena>:253 #: unmaintained/yoga>:360 unmaintained/zed>:591 msgid "" "The OVN migration performs validation by default. This validation means an " "instance is spawned and is tested by simple ping after the migration is " "finished. Also it tries to create new workload post migration. This is " "useful for very simple scenarios when migration is tested but is not really " "useful in production since likely the production envrionments already have " "running workloads. It makes more sense to require the validation explicitly " "rather than implicitly run it as the migration is mostly intended for " "production. The VALIDATE_MIGRATION now defaults to False and needs to be " "changed to True if validation upon request." msgstr "" #: ../../:155 stable/rocky>:207 stable/stein>:329 #: stable/train>:564 msgid "" "The OVS Firewall blocks traffic that does not have either the IPv4 or IPv6 " "ethertypes at present. This is a behavior change compared to the " "iptables_hybrid firewall, which only operates on IP packets and thus does " "not address other ethertypes. There is now a configuration option in the " "neutron openvswitch agent configuration file for permitted ethertypes and " "then ensures that the requested ethertypes are permitted on initialization." msgstr "" #: ../../:189 msgid "The OVS agent had changes made to better handle restartability." msgstr "" #: ../../:231 msgid "" "The OVS agent may now be restarted without affecting data plane connectivity." msgstr "" #: ../../:298 msgid "" "The Open vSwitch Neutron agent has been extended to mark the Type of Service " "IP header field of packets egressing from the VM when the QoS rule has been " "applied." msgstr "" #: ../../:586 msgid "" "The Openflow Agent(OFAgent) mechanism driver and its agent have been removed " "in favor of OpenvSwitch mechanism driver with \"native\" of_interface in the " "Newton cycle." msgstr "" #: ../../:678 msgid "" "The Openflow Agent(OFAgent) mechanism driver is decomposed completely from " "neutron tree in the Mitaka. The OFAgent driver and its agent also are " "deprecated in favor of OpenvSwitch mechanism driver with \"native\" " "of_interface in the Mitaka and will be removed in the next release." msgstr "" #: ../../:209 stable/queens>:589 msgid "" "The Openvswitch agent has an extension called ``fdb`` that uses the Linux " "``bridge`` command. The ``bridge`` command has been added to the rootwrap " "openvswitch-plugin.filters file. For more information, see bug: `1730407 " "`_" msgstr "" #: ../../:189 msgid "" "The QoS driver architecture has been refactored to overcome several previous " "limitations, the main one was the coupling of QoS details into the mechanism " "drivers, and the next one was the need of configuration knobs to enable each " "specific notification driver, that will be handled automatically from now on." msgstr "" #: ../../:243 msgid "" "The QoS service plugin now supports new attribute in " "``qos_bandwidth_limit_rule``. This new parameter is called ``direction`` and " "allows to specify direction of traffic for which the limit should be applied." msgstr "" #: ../../:488 msgid "" "The RPC and notification queues have been separated into different queues. " "Specify the transport_url to be used for notifications within the " "[oslo_messaging_notifications] section of the configuration file. If no " "transport_url is specified in [oslo_messaging_notifications], the " "transport_url used for RPC will be used." msgstr "" #: ../../:670 msgid "" "The [DEFAULT] advertise_mtu option must contain a consistent value on all " "hosts running the DHCP agent." msgstr "" #: ../../:173 unmaintained/victoria>:227 #: unmaintained/wallaby>:716 msgid "" "The ``OVN Metadata Agent`` now creates the network namespaces including the " "Neutron network UUID in its name. Previously, the OVN datapath UUID was used " "and it was not obvious for operators and during debugging to figure out " "which namespace corresponded to what Neutron network." msgstr "" #: ../../:510 msgid "" "The ``ProcessManager`` class will now, by default, add an environment " "variable when starting a new process. This default tag is named \"PROCESS_TAG" "\" and will contain a unique identifier for this specific process. It could " "be used, for example, by TripleO to univocally tag any new container spawned " "and find it using the same tag." msgstr "" #: ../../:265 msgid "" "The ``[DEFAULT] api_workers`` option no longer accepts 0 or negative values. " "Previously 0 or a negative value was translated to 1 and neutron-server " "launched 1 api worker." msgstr "" #: ../../:271 msgid "" "The ``[DEFAULT] rpc_workers`` option and the ``[DEFAULT] " "rpc_state_report_workers`` option no longer accept negative values. To " "disable these workers, set these options to 0." msgstr "" #: ../../:306 msgid "" "The ``[DEFAULT] segment_mtu`` configuration option has been removed. It was " "replaced by the ``[DEFAULT] global_physnet_mtu`` option in the Mitaka " "release." msgstr "" #: ../../:579 msgid "" "The ``[agent] veth_mtu`` parameter of ML2 OVS mechanism driver configuration " "has been deprecated. This parameter has had no effect since the Wallaby " "release." msgstr "" #: ../../:284 msgid "" "The ``[agent] veth_mtu`` parameter of ML2 OVS mechanism driver configuration " "has been removed. This parameter has had no effect since the Wallaby release." msgstr "" #: ../../:245 msgid "" "The ``advertise_mtu`` option is removed. Now Neutron always uses all " "available means to advertise MTUs to instances (including DHCPv4 and IPv6 " "RA)." msgstr "" #: ../../:304 msgid "" "The ``allow_pagination`` and ``allow_sorting`` configuration options are now " "removed. Now, sorting and pagination are always enabled for plugins that " "support the features." msgstr "" #: ../../:468 msgid "" "The ``allow_sorting`` and ``allow_pagination`` configuration options are " "deprecated and will be removed in a future release." msgstr "" #: ../../:221 msgid "" "The ``api-paste.ini`` configuration file for the paste pipeline was updated " "to add the ``http_proxy_to_wsgi`` middleware." msgstr "" #: ../../:193 msgid "" "The ``created_at`` and ``updated_at`` resource fields now include a timezone " "indicator at the end. Because this is a change in field format, the old " "``timestamp_core`` extension has been removed and replaced with a ``standard-" "attr-timestamp`` extension." msgstr "" #: ../../:225 msgid "" "The ``dhcp_domain`` DHCP agent configuration option was deprecated in " "Liberty cycle, and now is no longer used. The ``dns_domain`` option should " "be used instead." msgstr "" #: ../../:626 msgid "" "The ``external_network_bridge`` config option has been removed. Existing " "users of this option will now have their router's gateway interface created " "in the integration bridge and it will be wired by the L2 agent." msgstr "" #: ../../:475 msgid "" "The ``gateway_external_network_id`` L3 agent option is deprecated and will " "be removed in next releases, with ``external_network_bridge`` that it " "depends on." msgstr "" #: ../../:520 msgid "" "The ``gateway_external_network_id`` config option has been removed. Systems " "where this option was set will now be able to support multiple external " "networks for routers." msgstr "" #: ../../:271 msgid "" "The ``iptables`` firewall driver will no longer enable bridge firewalling in " "next versions of Neutron. If your distribution overrides the default value " "for any of relevant sysctl settings (``net.bridge.bridge-nf-call-" "arptables``, ``net.bridge.bridge-nf-call-ip6tables``, and ``net.bridge." "bridge-nf-call-iptables``) then make sure you set them back to upstream " "kernel default (``1``) using /etc/sysctl.conf or /etc/sysctl.d/* " "configuration files." msgstr "" #: ../../:553 msgid "" "The ``ivs`` interface driver is deprecated in Queens and will be removed in " "Rocky." msgstr "" #: ../../:532 msgid "" "The ``live_migration_events`` configuration option is removed. Now Neutron " "assumes this flag is always set. This configuration option depended on the " "Nova patch `only wait for plugtime events in pre-live-migration `_." msgstr "" #: ../../:443 msgid "" "The ``max_fixed_ips_per_port`` configuration option was deprecated in the " "Newton cycle and removed in Pike." msgstr "" #: ../../:249 msgid "" "The ``min_l3_agents_per_router`` configuration option was deprecated in " "Newton cycle and removed in Ocata. HA routers no longer require a minimal " "number of L3 agents to be created, although obviously they require at least " "two L3 agents to provide HA guarantees. The rationale for the removal of the " "option is the case a router was created just when an agent was not " "operational. The creation of the router will now succeed, and when a second " "agent resumes operation the router will be scheduled to it providing HA." msgstr "" #: ../../:487 msgid "" "The ``nova_metadata_ip`` option is deprecated and will be removed in Queens. " "It is deprecated in favor of the new ``nova_metadata_host`` option because " "it reflects better that the option accepts an IP address and also a DNS name." msgstr "" #: ../../:351 msgid "" "The ``openvswitch`` mechanism driver now supports hardware offload via SR-" "IOV. It allows binding direct (SR-IOV) ports. Using ``openvswitch`` 2.8.0 " "and 'Linux Kernel' 4.8 allows to control the SR-IOV VF via OpenFlow control " "plane and gain accelerated 'Open vSwitch'." msgstr "" #: ../../:572 msgid "" "The ``ovs_vsctl_timeout`` option is renamed into ``ovsdb_timeout`` to " "reflect that it's not specific to ``vsctl`` implementation of " "``ovsdb_interface``. It is also moved under ``[OVS]`` section." msgstr "" #: ../../:558 msgid "" "The ``ovsdb_interface`` configuration option is now deprecated. In future " "releases, the value of the option will be ignored. The ``native`` driver " "will then be used." msgstr "" #: ../../:537 msgid "" "The ``port.mac_address`` field is sanitized to have a common format \"xx:xx:" "xx:xx:xx:xx\". The values stored in the database can be sanitized executing " "the new script provided ``neutron-sanitize-port-mac-addresses``. This script " "will read all ``port`` registers and fix, if needed, the stored MAC address " "format. The ``port`` API is also modified to sanitize the user input. This " "change was added to neutron-lib 2.12.0 in `788300 `_." msgstr "" #: ../../:593 msgid "" "The ``qos-rules-alias`` API extension was implemented to enable users to " "perform GET, PUT and DELETE operations on QoS rules as though they are first " "level resources. In other words, the user doesn't have to specify the QoS " "policy ID." msgstr "" #: ../../:438 msgid "" "The ``send_arp_for_ha`` configuration option is removed. Neutron now always " "sends three gratuitous ARP requests on address assigned to a port." msgstr "" #: ../../:548 msgid "" "The ``stateless security group`` feature does not work with OVS nor OVN " "driver as the driver is not aware of the ``stateful`` attribute in the " "security group. If ``stateful`` attribute is provided with a ``False`` value " "then the attribute value is ignored and the security group would behave as " "stateful." msgstr "" #: ../../:449 msgid "" "The ``subnet-dns-publish-fixed-ip`` extension adds a new attribute to the " "definition of the subnet resource. When set to ``true`` it will allow " "publishing DNS records for fixed IPs from that subnet independent of the " "restrictions described in the `DNS integration with an external service " "`_ " "documentation." msgstr "" #: ../../:459 msgid "" "The ``tag_ports_during_bulk_creation`` ML2 plugin extension has been " "implemented to support tagging ports during bulk creation. As a side effect, " "this extension also allows tagging ports during non-bulk creation." msgstr "" #: ../../:257 msgid "" "The ``timestamp_core`` extension has been removed and replaced with the " "``standard-attr-timestamp`` extension. Resources will still have timestamps " "in the ``created_at`` and ``updated_at`` fields, but timestamps will have " "time zone info appended to the end to be consistent with other OpenStack " "projects." msgstr "" #: ../../:271 stable/2023.2>:258 #: unmaintained/wallaby>:54 unmaintained/xena>:157 unmaintained/yoga>:177 #: unmaintained/zed>:200 msgid "" "The `redirect-type=bridged` option is only used if all the tenant networks " "connected to the router are of type VLAN or FLAT. In this case their traffic " "will be distributed. However, if there is a mix of VLAN/FLAT and geneve " "networks connected to the same router, the redirect-type option is not set, " "and therefore the traffic for the VLAN/FLAT networks will also be " "centralized but not tunneled." msgstr "" #: ../../:144 unmaintained/wallaby>:381 #: unmaintained/xena>:438 unmaintained/yoga>:618 msgid "" "The agent reporting state to the server now uses a RPC timeout set to the " "report_interval configuration option value. See `1948676 `_." msgstr "" #: ../../:564 msgid "" "The api-paste entrypoint ``neutron.api.versions:Versions.factory`` has been " "deprecated and will be removed in the Rocky release. Please update your api-" "paste.ini file to use the one that ships with Queens or update any " "references to the Versions factory to point to ``neutron.pecan_wsgi.app:" "versions_factory`` instead." msgstr "" #: ../../:133 msgid "" "The api-paste.ini configuration file for the paste pipeline was updated to " "add the http_proxy_to_wsgi middleware." msgstr "" #: ../../:461 msgid "" "The artifact of creating a gateway chassis called \"neutron-ovn-invalid-" "chassis\" when a \"Logical_Router_Port\" cannot be assigned to any chassis " "is removed. Now no gateway chassis is created and the \"Logical_Router_Port" "\" field will be empty." msgstr "" #: ../../:492 msgid "" "The cache_url configuration option is deprecated as of Newton, and will be " "removed in Ocata. Please configure metadata cache using [cache] group, " "setting enable = True and configuring your backend." msgstr "" #: ../../:648 msgid "" "The change to the process title happens by default with the new " "``setproctitle`` config option. The old string is still part of the new " "process title, but any scripts looking for exact string matches of the old " "string may need to be modified." msgstr "" #: ../../:510 msgid "" "The combination of 'path_mtu' and 'advertise_mtu' only adjusts the MTU for " "instances rather than all virtual network components between instances and " "provider/public networks. In particular, setting 'path_mtu' to a value " "greater than 1500 can cause packet loss even if the physical network " "supports it. Also, the calculation does not consider additional overhead " "from IPv6 endpoints." msgstr "" #: ../../:68 stable/2023.2>:360 #: unmaintained/wallaby>:78 unmaintained/xena>:55 unmaintained/zed>:42 msgid "" "The config option ``agent_down_time`` is now limited to a maximum value of " "`2147483`, as neutron-server will fail to start if it is configured higher. " "See bug `2028724 `_ for " "more information." msgstr "" #: ../../:590 msgid "" "The configuration option 'force_gateway_on_subnet' is removed. This will " "always allow adding gateway outside the subnet, and gateway cannot be forced " "onto the subnet range." msgstr "" #: ../../:405 msgid "" "The configuration option ``firewall_driver`` is no longer used by neutron-" "server, it only applies to the L2 agent. This was required for backward-" "compatibility for hybrid plugging, but since the Newton release the L2 agent " "has been able to report hybrid plugging is needed in it's report message " "back to the server." msgstr "" #: ../../:478 msgid "" "The configuration option ``vnic_type_blacklist`` has been deprecated for " "both the OpenvSwitch and SRIOV mechanism drivers, and replaced with " "``vnic_type_prohibit_list``. They will be removed in a future release." msgstr "" #: ../../:389 msgid "" "The configuration option dhcp_lease_time was deprecated in the Havana cycle. " "This option is no longer supported. The option was replaced by " "dhcp_lease_duration." msgstr "" #: ../../:393 msgid "" "The configuration option dnsmasq_dns_server was deprecated in the kilo " "cycle. This value is no longer supported." msgstr "" #: ../../:612 msgid "" "The configuration options for XenAPI support has been removed, because these " "options were already ineffective." msgstr "" #: ../../:445 msgid "" "The configuration options for ``default_ipv4_subnet_pool`` and " "``default_ipv6_subnet_pool`` have been removed. Please use the " "``is_default`` option of the create/update subnetpool API instead." msgstr "" #: ../../:244 msgid "" "The created_at and updated_at fields available on Neutron resources now " "include a timezone indicator at the end. Because this is a change in format, " "the old 'timestamp_core' extension has been removed and replaced with a " "'timestamp' extension." msgstr "" #: ../../:385 msgid "" "The default value for 'external_network_bridge' has been changed to '' since " "that is the preferred way to configure the L3 agent and will be the only way " "in future releases. If you have not explicitly set this value and you use " "the L3 agent, you will need to set this value to 'br-ex' to match the old " "default. If you are using 'br-ex', you should switch to '', ensure your " "external network has a flat segment and ensure your L2 agent has a " "bridge_mapping entry between the external network's flat segment physnet and " "'br-ex' to get the same connectivity. If the external network did not " "already have the flat segment, you will need to detach all routers from the " "external networks, delete the incorrect segment type, add the flat segment, " "and re-attach the routers." msgstr "" #: ../../:169 msgid "" "The default value for 'external_network_bridge' in the L3 agent is now ''." msgstr "" #: ../../:536 msgid "" "The default value for ML2 path_mtu option is changed from 1500 to 0, " "effectively disabling its participation in network MTU calculation unless " "it's overridden in the ml2_conf.ini configuration file." msgstr "" #: ../../:408 unmaintained/wallaby>:298 #: unmaintained/xena>:328 unmaintained/yoga>:308 unmaintained/zed>:289 msgid "" "The default value for the ``metadata_workers`` configuration option has " "changed to 0 for the ML2/OVN driver. Since `[OVN] Allow to execute " "\"MetadataProxyHandler\" in a local thread `_, the OVN metadata proxy handler can be spawned " "in the same process of the OVN metadata agent, in a local thread. That " "reduces the number of OVN SB database connections to one." msgstr "" #: ../../:434 msgid "" "The default value for the ``metadata_workers`` configuration option has " "changed to 2 for the ML2/OVN driver. For ML2/OVS the default value remains " "the same. Each driver has different approaches when serving metadata to the " "instances and the previous default value of \" / 2\" did not " "make sense for ML2/OVN as the OVN metadata agents are distributed running on " "Compute nodes instead of Controller nodes. In fact, the previous default " "value could cause scalability issues with ML2/OVN and was overwritten by the " "deployment tools to avoid problems." msgstr "" #: ../../:622 msgid "" "The default value of ``[oslo_policy] policy_file`` config option has been " "changed from ``policy.json`` to ``policy.yaml``. Operators who are utilizing " "customized or previously generated static policy JSON files (which are not " "needed by default), should generate new policy files or convert them in YAML " "format. Use the `oslopolicy-convert-json-to-yaml `_ tool to " "convert a JSON to YAML formatted policy file in backward compatible way." msgstr "" #: ../../:586 msgid "" "The default_subnet_pools option is now deprecated and will be removed in the " "Newton release. The same functionality is now provided by setting " "is_default attribute on subnetpools to True using the API or client." msgstr "" #: ../../:526 msgid "" "The deprecated L2 population ``agent_boot_time`` config option was removed " "and is no longer needed as of the Stein release." msgstr "" #: ../../:645 msgid "" "The deprecated ``IVSInterfaceDriver`` class has been removed from the code " "base. This means neither the ``ivs`` nor the ``neutron.agent.linux." "interface.IVSInterfaceDriver`` can any longer be used as a value for the " "``interface_driver`` config option in ``neutron.conf``." msgstr "" #: ../../:531 msgid "" "The deprecated ``of_interface`` option is removed. Neutron will always use " "the ``native`` driver, which has been the default since Pike (11.0). If old " "driver ``ovs-ofctl`` was used before upgrade, automatically done change to " "``native`` driver will cause short break of data plane connectivity during " "neutron-ovs-agent upgrade." msgstr "" #: ../../:634 msgid "" "The deprecated ``ovsdb_interface`` configuration option has been removed, " "the default ``native`` driver is now always used. In addition, the " "deprecated ``ovs_vsctl_timeout`` option, which was renamed to " "``ovsdb_timeout`` in Queens, has also been removed." msgstr "" #: ../../:447 msgid "" "The deprecated ``prevent_arp_spoofing`` option has been removed and the " "default behavior is to always prevent ARP spoofing unless port security is " "disabled on the port (or network)." msgstr "" #: ../../:417 msgid "The deprecated config option ``keepalived_use_no_track`` is removed." msgstr "" #: ../../:14 stable/train>:14 stable/ussuri>:14 #: unmaintained/victoria>:343 msgid "" "The dns-assignment will reflect the dns-domain defined in the network or " "sent by user when creating the port using --dns-domain rather than just take " "the dns-domain defined in the neutron configuration" msgstr "" #: ../../:211 stable/2023.2>:458 #: unmaintained/wallaby>:208 unmaintained/xena>:123 unmaintained/yoga>:140 #: unmaintained/zed>:150 msgid "" "The external_mac entry in the NAT table is used to distribute/centralize the " "traffic to the FIPs. When there is an external_mac set the traffic is " "distributed (DVR). When it is empty it is centralized through the gateway " "port (no DVR). Upon port status transition to down, the external_mac was " "removed regardless of DVR being enabled or not, leading to centralize the " "FIP traffic for DVR -- though it was for down ports that won't accept " "traffic anyway." msgstr "" #: ../../:345 msgid "" "The feature \"vlan-aware-vms\" is available. To enable it, a service plugin " "named 'trunk' must be added to the option ``service_plugins`` in your " "neutron.conf. The plugin exposes two new extensions ``trunk`` and " "``trunk_details``. The plugin can work with multiple backends and in " "particular Neutron has support for `ML2/openvswitch `_ and ML2/linuxbridge. Even though Neutron API " "compatibility should be preserved for ports associated to trunks, since this " "is the first release where the feature is available, it is reasonable to " "expect possible functionality gaps for one or both drivers. These will be " "filled over time as being reported. The CLI is available via " "openstackclient, and python-neutronclient 5.1.0 or above. For more details, " "please check the networking guide." msgstr "" #: ../../:14 stable/queens>:187 stable/rocky>:248 #: stable/stein>:383 stable/train>:514 msgid "" "The first address in an IPv6 network is now a valid, usable IP for routers. " "It had previously been reserved, but now can be assigned to a router so that " "an IPv6 address ending in \"::\" could be a valid default route." msgstr "" #: ../../:187 msgid "" "The first hint using the new ``hints`` port attribute is the ``ovs-tx-" "steering`` hint. The availability of this is marked by the extension: ``port-" "hint-ovs-tx-steering``. This hint is specific to the ``openvswitch`` " "mechanism driver. It enables the control of Open vSwitch's Userspace Tx " "packet steering feature. For details about the Open vSwitch feature please " "see: https://docs.openvswitch.org/en/latest/topics/userspace-tx-steering/ " "The valid values for the ``hints`` attribute introduced by the 2nd extension " "are: ``{\"openvswitch\": {\"other_config\": {\"tx-steering\": \"hash|thread" "\"}}}``" msgstr "" #: ../../:42 stable/2023.2>:42 stable/2024.1>:217 #: unmaintained/zed>:28 msgid "" "The fix of `bug 2048785 `_ " "only fixes newly created trunk parent ports. If the fix of already existing " "trunks is needed, then either delete and re-create the affected trunks or " "set tpt ports' vlan_mode and tag manually: ``ovs-vsctl set Port tpt-... " "vlan_mode=access tag=0``" msgstr "" #: ../../:635 msgid "" "The following parameters in the ``designate`` section have been deprecated " "and will be removed in a future release. The ``[designate] auth_type`` " "parameter and required keystoneauth parameters should be used instead." msgstr "" #: ../../:290 msgid "" "The following parameters in the ``designate`` section have been removed." msgstr "" #: ../../:524 msgid "" "The functionality when a subnet has its DNS server set to ``0.0.0.0`` or ``::" "`` has been changed with this release. The old behaviour was that each DHCP " "agent would supply only its own IP address as the DNS server to its clients. " "The new behaviour is that the DHCP agent will not supply any DNS server IP " "address at all." msgstr "" #: ../../:255 stable/2023.2>:231 #: unmaintained/victoria>:32 unmaintained/wallaby>:30 unmaintained/xena>:24 #: unmaintained/yoga>:161 unmaintained/zed>:184 msgid "" "The high availability of metadata service on isolated networks is limited or " "non-existent. IPv4 metadata is redundant when the DHCP agent managing it is " "redundant, but recovery is tied to the renewal of the DHCP lease, making " "most recoveries very slow. IPv6 metadata is not redundant at all as the IPv6 " "metadata address can only be configured in a single place at a time as it is " "link-local. Multiple agents trying to configure it will generate an IPv6 " "duplicate address detection failure." msgstr "" #: ../../:214 msgid "" "The internal pluggable IPAM implementation -- added in the Liberty release " "-- is now the default for both old and new deployments. Old deployments are " "unconditionally switched to pluggable IPAM during upgrade. Old non-pluggable " "IPAM is deprecated and removed from code base." msgstr "" #: ../../:94 msgid "" "The iptables firewall driver will no longer enable bridge firewalling in " "next versions of Neutron. If your distribution overrides the default value " "for any of relevant sysctl settings (``net.bridge.bridge-nf-call-" "arptables``, ``net.bridge.bridge-nf-call-ip6tables``, and ``net.bridge." "bridge-nf-call-iptables``) then make sure you set them back to upstream " "kernel default (``1``) using /etc/sysctl.conf or /etc/sysctl.d/* " "configuration files." msgstr "" #: ../../:130 stable/newton>:325 msgid "" "The local_ip value in ml2_conf.ini can now be set to an IPv6 address " "configured on the system." msgstr "" #: ../../:422 msgid "" "The metadata over IPv6 feature makes each dhcp-agent restart trigger a quick " "restart of dhcp-agent-controlled metadata-proxies, so they can pick up their " "new config making them also bind to ``fe80::a9fe:a9fe``. These restarts make " "the metadata service transiently unavailable. This is done in order to " "enable the metadata service on pre-existing isolated networks during an " "upgrade. Please also note that pre-existing instances may need to re-acquire " "all information acquired over Router Discovery and/or DHCP for this feature " "to start working." msgstr "" #: ../../:313 msgid "The metaplugin is removed in the Liberty release." msgstr "" #: ../../:340 msgid "" "The metering agent driver can now be specified with a stevedore alias in the " "``metering_agent.ini`` file. For example, ``driver = iptables`` instead of " "``driver = neutron.services.metering.iptables.iptables_driver:" "IptablesMeteringDriver``." msgstr "" #: ../../:109 stable/queens>:307 stable/rocky>:649 #: stable/stein>:818 msgid "" "The metering agent iptables driver can now load its interface driver by " "using a stevedore alias in the ``metering_agent.ini`` file. For example, " "``interface_driver = openvswitch`` instead of ``interface_driver = neutron." "agent.linux.interface.OVSInterfaceDriver``" msgstr "" #: ../../:331 msgid "The most important improvements worth mentioning are:" msgstr "" #: ../../:421 msgid "" "The native interface configures ovsdb-server to listen for connections on " "127.0.0.1:6640 by default. The address can be configured with the " "ovsdb_connection config option. Ensure that ovsdb-server has permissions to " "listen on the configured address." msgstr "" #: ../../:485 msgid "" "The network ``mtu`` attribute is set to be non-nullable. If the ``mtu`` is " "empty(create before Pike version), it is set to the default value of 1500." msgstr "" #: ../../:433 msgid "" "The network_device_mtu option is removed. Existing users of the option are " "advised to adopt new configuration options to accommodate for their " "underlying physical infrastructure. The relevant options are " "global_physnet_mtu for all plugins, and also path_mtu and " "physical_network_mtus for ML2." msgstr "" #: ../../:353 msgid "" "The networking-ovn mechanism driver has been merged into the neutron " "repository and is now an in-tree driver for ML2." msgstr "" #: ../../:317 msgid "" "The neutron L3 agent now has the ability to load agent extensions, which " "allows other services to integrate without additional agent changes. An API " "for exposing the l3 agent's router info data to the extensions is also " "provided so that extensions can remain consistent with router state." msgstr "" #: ../../:34 stable/pike>:51 stable/queens>:224 #: stable/rocky>:322 stable/stein>:700 msgid "" "The neutron-openvswitch-agent can sometimes spend too much time handling a " "large number of ports, exceeding its timeout value, ``agent_boot_time``, for " "L2 population. Because of this, some flow update operations will not be " "triggerred, resulting in lost flows during agent restart, especially for " "host-to-host vxlan tunnel flows, causing the original tunnel flows to be " "treated as stale due to the different cookie IDs. The agent's first RPC loop " "will also do a stale flow clean-up procedure and delete them, leading to a " "loss of connectivity. Please ensure that all neutron-server and neutron-" "openvswitch-agent binaries are upgraded for the changes to take effect, " "after which the L2 population ``agent_boot_time`` config option will no " "longer be used." msgstr "" #: ../../:55 stable/pike>:90 stable/queens>:263 #: stable/rocky>:361 stable/stein>:757 msgid "" "The neutron-openvswitch-agent was changed to notify the neutron-server in " "its first RPC loop that it has restarted. This signals neutron-server to " "provide updated L2 population information to correctly program FDB entries, " "ensuring connectivity to instances is not interrupted. This fixes the " "following bugs: `1794991 `_, `1799178 `_, `1813703 `_, `1813714 `_, `1813715 `_." msgstr "" #: ../../:443 msgid "" "The new API extension ``extraroute-atomic`` introduces two new member " "actions on routers to add/remove routes atomically on the server side. The " "use of these new member actions (``PUT /v2.0/routers/ROUTER-ID/" "add_extraroutes`` and ``PUT /v2.0/routers/ROUTER-ID/remove_extraroutes``) is " "always preferred to the old way (``PUT /v2.0/routers/ROUTER-ID``) when " "multiple clients edit the extra routes of a router since the old way is " "prone to race conditions between concurrent clients and therefore to " "possible lost updates." msgstr "" #: ../../:257 msgid "" "The new ``net-mtu-writable`` extension API definition has been added. The " "new extension indicates that the network ``mtu`` attribute is writeable. " "Plugins supporting the new extension are expected to also support ``net-" "mtu``. The first plugin that gets support for the new extension is ``ml2``." msgstr "" #: ../../:73 stable/ussuri>:147 #: unmaintained/victoria>:207 unmaintained/wallaby>:454 unmaintained/xena>:693 msgid "" "The new ``resource_provider_defualt_hypervisor`` option has been added, to " "replace the default hypervisor name to locates the root resource provider " "without giving a complete list of interfaces or bridges in the " "``resource_provider_hypervisors`` option. This option is located in the " "``[ovs]`` ini-section for ``ovs-agent`` and ``[sriov_nic]`` ini-section for " "``sriov-agent``." msgstr "" #: ../../:476 msgid "" "The new configuration option ``[l3-conntrack-helpers]/" "allowed_conntrack_helpers`` allow the operator to configure allowed helpers, " "and the helper protocol constraints." msgstr "" #: ../../:310 msgid "" "The new l2_adjacency extension adds an l2_adjacency field to the network, to " "indicate whether or not there is guaranteed L2 adjacency between the ports " "on that Network. Routed network implementations would typically set " "l2_adjacency to False." msgstr "" #: ../../:121 stable/2023.2>:111 #: stable/2024.1>:448 msgid "" "The new value for 'device_owner' for OVN loadbalancer health monitor ports " "(ovn-lb-hm:distributed) is now supported by Neutron, providing a LOCALPORT " "behavior to these ports. The responsibility to define these ports with the " "new value instead of the old one (network:distributed) is under the OVN-" "Octavia Provider driver, which will take care of database conversion for " "these ports." msgstr "" #: ../../:496 msgid "" "The non-pluggable ipam implementatios is deprecated and will be removed in " "Newton release cycle." msgstr "" #: ../../:630 msgid "" "The number of api and rpc workers may change on upgrade. It is strongly " "recommended that all deployers set these values in their neutron " "configurations, rather than using the defaults." msgstr "" #: ../../:483 msgid "" "The of_interface Open vSwitch agent configuration option is deprecated and " "will be removed in the future. After option removal, the current default " "driver (native) will be the only supported of_interface driver." msgstr "" #: ../../:239 msgid "" "The openvswitch L2 agent now supports bi-directional bandwidth limiting." msgstr "" #: ../../:488 msgid "" "The option ``[AGENT] prevent_arp_spoofing`` has been deprecated and will be " "removed in Ocata release. ARP spoofing protection should always be enabled " "unless its explicitly disabled via the port security extension via the API. " "The primary reason it was a config option was because it was merged at the " "end of Kilo development cycle so it was not considered stable. It has been " "enabled by default since Liberty and is considered stable and there is no " "reason to keep this configurable." msgstr "" #: ../../:476 msgid "" "The option min_l3_agents_per_router is deprecated and will be removed for " "the Ocata release where the scheduling of new HA routers will always be " "allowed." msgstr "" #: ../../:239 msgid "The original, non-pluggable version of IPAM is enabled by default." msgstr "" #: ../../:690 msgid "" "The oslo.messaging.notify.drivers entry points that were left in tree for " "backward compatibility with Icehouse are deprecated and will be removed " "after liberty-eol. Configure notifications using the oslo_messaging " "configuration options in neutron.conf." msgstr "" #: ../../:285 msgid "" "The port resource now has an ip_allocation attribute. The value of this " "attribute will be set to 'immediate', 'deferred', or 'none' at the time the " "port is created. It will not be changed when the port is updated. " "'immediate' means that the port is expected to have an IP address and " "Neutron attempted IP allocation on port creation. 'deferred' means that the " "port is expected to have an IP address but Neutron deferred IP allocation " "until a port update provides the host to which the port will be bound. " "'none' means that the port was created explicitly with no addresses by " "passing [] in fixed_ips when creating it." msgstr "" #: ../../:312 msgid "" "The process title for RPC reports worker has been changed from 'rpc worker' " "to 'rpc reports worker'. Please update any external scripts or services " "which look up the process title accordingly." msgstr "" #: ../../:380 msgid "The reference driver integrates neutron with designate" msgstr "" #: ../../:269 msgid "" "The resource tag mechanism is refactored so that the tag support for new " "resources can be supported easily. The resources with tag support are " "network, subnet, port, subnetpool, trunk, floatingip, policy, " "security_group, and router." msgstr "" #: ../../:369 msgid "" "The rootwrap filters file dhcp.filters must be updated to include " "dhcp_release6, otherwise trying to run the utility will result in a " "NoFilterMatched exception." msgstr "" #: ../../:556 msgid "" "The router_id option is deprecated and will be removed in the 'N' cycle." msgstr "" #: ../../:435 msgid "" "The segmentation ID of a provider network can be now modified, even with OVS " "ports bound. Note that, during this process, the traffic of the bound ports " "tagged with the former segmentation ID (external VLAN) will be mapped to the " "new one. This can provoke a traffic disruption while the external network " "VLAN is migrated to the new tag." msgstr "" #: ../../:636 msgid "" "The server will fail to start if any of the declared required extensions, as " "needed by core and service plugins, are not properly configured." msgstr "" #: ../../:669 msgid "" "The signature of notifications for resource ``agent`` for events " "``after_create`` and ``after_update`` was extended. A new keyword argument " "was added: ``status``. This is to make the same status information available " "to notification consumers as it was available already where the notification " "is sent in class ``AgentDbMixin``. Valid status values are defined in " "``neutron_lib.agent.constants``. Consuming notifications by the old " "signature is deprecated. Unless processing arguments as ``**kwargs``, out-of-" "tree notification consumers need to adapt." msgstr "" #: ../../:265 msgid "" "The stock Ubuntu Trusty Tahr kernel (3.13) shows linear performance " "degradation when running \"ip netns exec\" as the number of namespaces " "increases. In cases where scale is important, a later version kernel (e.g. " "3.19) should be used. This regression should be fixed in Trusty Tahr since " "3.13.0-36.63 and later kernel versions. For more information, please see " "`Launchpad bug 1328088. `_" msgstr "" #: ../../:448 msgid "" "The subnet API now includes a new use_default_subnetpool attribute. This " "attribute can be specified on creating a subnet in lieu of a subnetpool_id. " "The two are mutually exclusive. If it is specified as True, the default " "subnet pool for the requested ip_version will be looked up and used. If no " "default exists, an error will be returned." msgstr "" #: ../../:484 msgid "" "The tool neutron-debug is now deprecated, to be replaced with a new set of " "troubleshooting and diagnostic tools. There is no plan for removal in the " "immediate term, and not until comparable tools will be adequate enough to " "supplant neutron-debug altogether. For more information, please see https://" "blueprints.launchpad.net/neutron/+spec/troubleshooting" msgstr "" #: ../../:348 msgid "" "The tool neutron-debug is now removed. With removal of the neutron client " "shell code this tool is no longer usable. It had been marked for deprecation " "since the Newton (9.0) cycle and unmaintained." msgstr "" #: ../../:574 msgid "" "The value of the 'overlay_ip_version' option adds either 20 bytes for IPv4 " "or 40 bytes for IPv6 to determine the total tunnel overhead amount." msgstr "" #: ../../:599 msgid "" "The way the ML2 plugin filters out API extensions which are not supported by " "loaded mechanism drivers has changed. Before, the API extension was on the " "list if at least one of the mechanism drivers supported it, but now the " "extension needs to be supported by all the mechanism drivers. If at least " "one of them filters it out, it will be removed from the final list of " "enabled API extensions. Currently, only the OVN mechanism driver is " "filtering out some of the ML2 API extensions, thus if that mechanism driver " "is loaded in Neutron with any other mechanism driver, the list of the " "enabled API extensions may be smaller than it was before." msgstr "" #: ../../:494 msgid "" "The web_framework option has been deprecated and will be removed during " "Queens. This option was just added to make the transition to pecan easier so " "there is no reason operators should be using the non-default option anyway." msgstr "" #: ../../:537 msgid "" "The web_framework option has been removed. This should have no impact on " "operators/users since it was just an option used for development of the new " "web framework." msgstr "" #: ../../:386 stable/queens>:510 msgid "" "There can be a mixture of ``dvr`` agents and ``dvr_no_external`` agents. But " "please avoid any VM with Floating IP migration between a ``dvr`` agent and a " "``dvr_no_external`` agent. All VM ports with Floating IPs should be migrated " "to same agent_mode. This would be one of the restrictions." msgstr "" #: ../../:435 msgid "There can be only one binding (active or inactive) per compute host." msgstr "" #: ../../:34 msgid "" "There is a race condition when adding ports in DHCP namespaces where an IPv6 " "address could be dynamically created via SLAAC from a Router Advertisement " "sent from the L3 agent, leading to a failure to start the DHCP agent. This " "bug has been fixed, but care must be taken on an upgrade dealing with any " "possibly stale dynamic addresses. For more information, see bug `1627902 " "`_." msgstr "" #: ../../:286 msgid "" "There is a race condition when adding ports in DHCP namespaces where an IPv6 " "address could be dynamically created via SLAAC from a Router Advertisement " "sent from the L3 agent, leading to a failure to start the DHCP agent. This " "bug has been fixed, but care must be taken on an upgrade dealing with any " "potentially stale dynamic addresses. For more information, see bug `1627902 " "`_." msgstr "" #: ../../:480 msgid "" "This is accomplished by associating ``port_forwarding`` sub-resources to " "floating IPs." msgstr "" #: ../../:306 msgid "" "This means if you are using system scope token to access Neutron API then " "the request will be failed with 403 error code. Also, new defaults will be " "enforced by default. To know about the new defaults of each policy rule, " "refer to the `Policy New Defaults`_. For more detail about the Neutron API " "policies changes, refer to `Policy Concepts`_." msgstr "" #: ../../:368 msgid "This minimum is now enforced in the following ways:" msgstr "" #: ../../:214 stable/ussuri>:407 msgid "" "This requires dnsmasq version 2.81 or later. Some distributions may backport " "this feauture to earlier dnsmasq version as part of the packaging, check the " "distributions releasenotes." msgstr "" #: ../../:295 msgid "" "Those rules can now be modified by a cloud administrator using the ``default-" "security-group-rules`` API." msgstr "" #: ../../:255 msgid "Timestamp fields are now added to neutron core resources." msgstr "" #: ../../:482 msgid "" "To create a ``port_forwarding``, the user specifies: a floating IP ID, the " "floating IP's ``external_port`` number, the Neutron port ID " "``internal_port_id``, an ``internal_ip_address`` (one of the Neutron port's " "fixed IPs), the ``internal_port`` number and the ``protocol`` to be used " "(TCP or UDP for example)." msgstr "" #: ../../:552 msgid "To disable, use [DEFAULT] advertise_mtu = False." msgstr "" #: ../../:578 msgid "" "To enable this feature, the ``qos`` service plugin has to be configured in " "the Neutron server and the ``gateway_ip_qos`` extension has to be configured " "in the L3 agents. Please refer to the ``QoS`` section of the ``OpenStack " "Networking Guide`` for more specific details." msgstr "" #: ../../:526 msgid "" "To ensure any kind of migration works between all compute nodes, make sure " "that the same physical_interface_mappings is configured on each MacVtap " "compute node. Having different mappings could cause live migration to fail " "(if the configured physical network interface does not exist on the target " "host), or even worse, result in an instance placed on the wrong physical " "network (if the physical network interface exists on the target host, but is " "used by another physical network or not used at all by OpenStack). Such an " "instance does not have access to its configured networks anymore. It then " "has layer 2 connectivity to either another OpenStack network, or one of the " "hosts networks." msgstr "" #: ../../:138 stable/rocky>:120 stable/stein>:38 #: stable/train>:93 stable/ussuri>:167 unmaintained/victoria>:258 #: unmaintained/wallaby>:710 msgid "" "To improve performance of the DHCP agent, it will no longer configure the " "DHCP server for every port type created in Neutron. For example, for " "floating IP or router HA interfaces there is no need since a client will not " "make a DHCP request for them" msgstr "" #: ../../:417 msgid "" "To keep the old default value use 'ovsdb_interface = vsctl' in '[ovs]' " "section of openvswitch_agent.ini (common path '/etc/neutron/plugins/ml2/" "openvswitch_agent.ini') if there is a separate openvswitch agent " "configuration file; otherwise apply changes mentioned above to ml2_conf.ini " "(common path '/etc/neutron/plugins/ml2/ml2_conf.ini')." msgstr "" #: ../../:405 msgid "" "To retain the old default for neutron-openvswitch-agent, use 'of_interface = " "ovs-ofctl' in the '[ovs]' section of your openvswitch agent configuration " "file." msgstr "" #: ../../:457 msgid "" "To upgrade to the ``haproxy`` based metadata proxy, ``neutron-l3-agent`` and " "``neutron-dhcp-agent`` have to be restarted. On startup, old proxy processes " "will be detected and replaced with ``haproxy``." msgstr "" #: ../../:118 stable/newton>:269 msgid "Two new options are added to `[designate]` section to support SSL." msgstr "" #: ../../:674 msgid "Typical networks can use [ml2] path_mtu = 1500." msgstr "" #: ../../:336 msgid "" "UDP ports used by VXLAN in the LinuxBridge agent can be configured now with " "the VXLAN.udp_srcport_min, VXLAN.udp_srcport_max and VXLAN.udp_dstport " "config options. To use the IANA assigned port number, set VXLAN.udp_dstport " "to 4789. The default is not changed from the Linux kernel default 8472." msgstr "" #: ../../:394 unmaintained/wallaby>:46 #: unmaintained/xena>:209 unmaintained/yoga>:283 unmaintained/zed>:275 msgid "" "Until the OVN bug (https://bugzilla.redhat.com/show_bug.cgi?id=2162756) is " "fixed, setting the \"reside-on-redirect-chassis\" to true for the logical " "router port associated to vlan provider network is needed. This workaround " "makes the traffic centrallized, but not tunneled, through the node with the " "gateway port, thus avoiding MTU issues." msgstr "" #: ../../:55 msgid "" "Update from versions ``14.3.1``, ``14.4.0`` or ``14.4.1`` versions to the " "``14.4.2`` or newer will cause problem with compatibility between older " "neutron agents and new neutron server. For more information see bug `1903531 " "`_. Update from older " "versions will not cause the same problem." msgstr "" #: ../../:556 msgid "" "Update of an already bound port with a QoS ``minimum_bandwidth`` rule with a " "new QoS policy with a ``minimum_bandwidth`` rule now changes the allocations " "in placement as well." msgstr "" #: ../../:233 msgid "" "Update the `neutron_hyperv_agent.conf` / `neutron_ovs_agent.conf` files on " "the Hyper-V nodes to use `hyperv.neutron.security_groups_driver." "HyperVSecurityGroupsDriver`, which is the networking_hyperv security groups " "driver." msgstr "" #: ../../:560 msgid "" "Updating the ``minimum_bandwidth`` rule of a QoS policy that is attached to " "a port which is bound to a VM is still not possible." msgstr "" #: ../../:52 stable/2023.1>:404 #: stable/2023.2>:278 stable/2024.1>:227 stable/liberty>:10 stable/liberty>:58 #: stable/mitaka>:20 stable/mitaka>:70 stable/mitaka>:536 stable/newton>:20 #: stable/newton>:129 stable/newton>:361 stable/ocata>:217 stable/pike>:10 #: stable/pike>:405 stable/queens>:183 stable/queens>:383 stable/queens>:520 #: stable/rocky>:244 stable/rocky>:562 stable/stein>:51 stable/stein>:227 #: stable/stein>:379 stable/stein>:610 stable/train>:227 stable/train>:305 #: stable/train>:510 stable/ussuri>:465 unmaintained/victoria>:401 #: unmaintained/wallaby>:294 unmaintained/wallaby>:608 unmaintained/xena>:324 #: unmaintained/xena>:595 unmaintained/yoga>:304 unmaintained/yoga>:553 #: unmaintained/zed>:285 unmaintained/zed>:508 msgid "Upgrade Notes" msgstr "" #: ../../:844 msgid "" "Use ``publish`` for ``AGENT's`` ``AFTER_CREATE`` and ``AFTER_UPDATE`` events " "with ``DBEventPayload`` instead of the deprecated notify callback." msgstr "" #: ../../:640 msgid "" "Use of JSON policy files was deprecated by the ``oslo.policy`` library " "during the Victoria development cycle. As a result, this deprecation is " "being noted in the Wallaby cycle with an anticipated future removal of " "support by ``oslo.policy``. As such operators will need to convert to YAML " "policy files. Please see the upgrade notes for details on migration of any " "custom policy files." msgstr "" #: ../../:44 stable/mitaka>:460 msgid "" "Use the value of the network 'mtu' attribute for the MTU of virtual network " "interfaces such as veth pairs, patch ports, and tap devices involving a " "particular network." msgstr "" #: ../../:337 msgid "" "Users can now apply a QoS rule to a port or network to setup the minimum " "egress bandwidth per queue and port. The minimum egress bandwidth rule is " "applied to each port individually." msgstr "" #: ../../:467 msgid "" "Users can now configure conntrack helper target rules to be set for a " "``Router``. This is accomplished by associating a ``conntrack_helper`` sub-" "resource to a router. To create a ``conntrack_helper``, the user specifies: " "a router ID, the protocol (TCP or UDP, for example), the port number and the " "conntrack helper module alias (tftp or ftp, for example). CRUD operations " "for ``conntrack_helpers`` are implemented by a Neutron API extension and a " "service plugin. Please refer to the Neutron API reference documentation for " "details. A router can have multiple ``conntack_helpers``." msgstr "" #: ../../:477 msgid "" "Users can now forward the traffic from a TCP/UDP/other protocol port of a " "floating IP address to a TCP/UDP/other protocol port associated to one of " "the fixed IP addresses of a Neutron port." msgstr "" #: ../../:404 msgid "Users can set tags on their network resources." msgstr "" #: ../../:471 msgid "" "Users can use 'tagging' extension instead of the 'tag' extension and 'tag-" "ext' extension. Those extensions are now deprecated and will be removed in " "the Queens release." msgstr "" #: ../../:247 msgid "VPNaaS reference drivers now work with HA routers." msgstr "" #: ../../:290 msgid "" "Versions of ``keepalived`` < 1.2.20 don't send gratuitous ARPs when " "keepalived process receives a ``SIGHUP`` signal. These versions are not " "packaged in some Linux distributions like Red Hat Enterprise Linux 7, CentOS " "7, or Ubuntu Xenial. Not sending gratuitous ARPs may lead to peer ARP cache " "tables containing wrong entries about floating IP addresses until those " "entries are invalidated. To fix that scenario, Neutron now sends gratuitous " "ARPs for all new IP addresses that appear on non-HA interfaces in router " "namespaces. This behavior simulates behavior of new versions of " "``keepalived``." msgstr "" #: ../../:34 stable/newton>:108 msgid "" "Versions of keepalived < 1.2.20 don't send gratuitous ARPs when keepalived " "process receives SIGHUP signal. These versions are not packaged in some " "Linux distributions like RHEL, CentOS or Ubuntu Xenial. Not sending " "gratuitous ARPs may lead to peer ARP caches containing wrong information " "about floating IP addresses until the entry is invalidated. Neutron now " "sends gratuitous ARPs for all new IP addresses that appear on non-HA " "interfaces in router namespace which simulates behavior of new versions of " "keepalived." msgstr "" #: ../../:472 msgid "" "Virtual ports are supported in OVN since version 2.12. Since Yoga, this " "support is mandatory. The minimum OVN SB schema version must be 2.5." msgstr "" #: ../../:218 msgid "" "When ``ML2/OVN`` backend and it's L3 service plugin (``ovn-router``) are " "used together with \"vlan\" or \"flat\" network types used as tenant network " "type, floating IP port forwarding (FIP PF) will not work if distributed " "Floating IPs are enabled (``enable_distributed_floating_ip`` = ``True``). To " "workaround this issue one of the following changes needs to be done:" msgstr "" #: ../../:414 unmaintained/xena>:454 msgid "" "When ``noauth`` auth_strategy is used, neutron no longer requires a resource " "creation request to include a dummy 'project_id' in request body. A default " "project_id ``fake_project_id`` would be populated automatically in that case " "and would make the use of ``noauth`` usage simpler." msgstr "" #: ../../:520 msgid "" "When ``uplink-status-propagation`` extension is enabled, new ports created " "will default the value of ``propagate_uplink_status`` to True." msgstr "" #: ../../:376 msgid "" "When a network MTU is changed, validate the MTU is large enough for any " "currently associated subnets. Allowing a smaller MTU would render any " "existing subnets unusable." msgstr "" #: ../../:370 msgid "" "When a subnet is associated with a network, validate the MTU is large enough " "for the IP version. Not only would the subnet be unusable if it was allowed, " "but the Linux kernel can fail adding addresses and configuring network " "settings like the MTU." msgstr "" #: ../../:52 stable/mitaka>:476 msgid "" "When advertise_mtu is set in the config, Neutron supports advertising the " "LinkMTU using Router Advertisements." msgstr "" #: ../../:496 msgid "" "When different subnet pools participate in the same address scope, the " "constraints disallowing subnets to be allocated from different pools on the " "same network have been relaxed. As long as subnet pools participate in the " "same address scope, subnets can now be created from different subnet pools " "when multiple subnets are created on a network. When address scopes are not " "used, subnets with the same ``ip_version`` on the same network must still be " "allocated from the same subnet pool. For more information, see bug `1830240 " "`_." msgstr "" #: ../../:582 msgid "" "When listing ports using the ``openstack port list --mac-address A:B:C:D:E:" "F`` command we might not return any result when trying to list ports by MAC " "address if the cases differ. This fix makes the search based on MAC address " "case insensitive. For more information see `bug 1843428 `_." msgstr "" #: ../../:740 msgid "" "When new default values for API policies are enabled, some API requests may " "not be available for project admin users anymore as they are possible only " "for system scope users. Please note that system scope tokens don't have " "project_id included so for example creation of the provider network, with " "specified physical network details will now require from system scope admin " "user to explicitly set project_id." msgstr "" #: ../../:80 stable/2023.2>:62 stable/2024.1>:385 #: unmaintained/yoga>:14 unmaintained/zed>:54 msgid "" "When synchronizing the OVN databases, either when running the migration " "command or during startup, the code responsible for synchronization will " "only clean up segment-to-host mappings for hosts with agent_type ``OVN " "Controller agent``. Before, the synchronization would clean up (delete) " "segment-to-host mappings for non-OVN hosts. Fixes bug: `2040172 `_." msgstr "" #: ../../:437 msgid "" "When the ``activate`` operation is executed, a previously inactive binding " "is made active. The previously active binding becomes inactive." msgstr "" #: ../../:371 stable/ussuri>:659 msgid "" "When the ``enable_distributed_routing`` (DVR) configuration option is set to " "``True`` and tunneling is enabled, the ``arp_responder`` option will be " "forced to ``True`` since it is now required in order for ARP to work " "properly. For more information, see bug `1774459 `_." msgstr "" #: ../../:104 stable/2023.2>:94 #: stable/2024.1>:431 msgid "When the following configuration is enabled at the same time:" msgstr "" #: ../../:170 stable/rocky>:231 stable/stein>:353 #: stable/train>:621 stable/ussuri>:608 msgid "" "When updating the fixed-ips of a port residing on a routed provider network " "the port update would always fail if *host* was not set. See bug: `1844124 " "`_." msgstr "" #: ../../:514 msgid "" "When using DVR, if a floating IP is associated to a fixed IP direct access " "to the fixed IP is not possible when traffic is sent from outside of a " "Neutron tenant network (north-south traffic). Traffic sent between tenant " "networks (east-west traffic) is not affected. When using a distributed " "router, the floating IP will mask the fixed IP making it inaccessible, even " "though the tenant subnet is being announced as accessible through the " "centralized SNAT router. In such a case, traffic sent to the instance should " "be directed to the floating IP. This is a limitation of the Neutron L3 agent " "when using DVR and will be addressed in a future release." msgstr "" #: ../../:586 msgid "" "When using Linux Bridge mechanism driver in newer operating systems that use " "``nftables`` by default, it is needed to switch back to the legacy tool, as " "documented in the admin documentation for ``Linux bridge mechanism driver``." msgstr "" #: ../../:572 msgid "" "When using ML2 and the Linux Bridge agent, the default value for the ARP " "Responder under L2Population has changed. The responder is now disabled to " "improve compatibility with the allowed-address-pair extension and to match " "the default behavior of the ML2 OVS agent. The logical network will now " "utilize traditional flood and learn through the overlay. When upgrading, " "existing vxlan devices will retain their old setup and be unimpacted by " "changes to this flag. To apply this to older devices created with the " "Liberty agent, the vxlan device must be removed and then the Mitaka agent " "restarted. The agent will recreate the vxlan devices with the current " "settings upon restart. To maintain pre-Mitaka behavior, enable the " "arp_responder in the Linux Bridge agent VXLAN config file prior to starting " "the updated agent." msgstr "" #: ../../:145 stable/2023.2>:267 #: unmaintained/wallaby>:63 unmaintained/xena>:40 unmaintained/yoga>:110 #: unmaintained/zed>:84 msgid "" "When using ML2/OVN, during an upgrade procedure, the OVS system-id stored " "value can be changed. The ovn-controller service will create the \"Chassis\" " "and \"Chassis_Private\" registers based on this OVS system-id. If the ovn-" "controller process is not gracefully stopped, that could lead to the " "existence of duplicated \"Chassis\" and \"Chassis_Private\" registers in the " "OVN Southbound database." msgstr "" #: ../../:177 unmaintained/wallaby>:424 #: unmaintained/xena>:569 msgid "" "When using the minimim-bandwidth QoS feature due to bug https://launchpad." "net/bugs/1921150 physical NIC resource providers were for some time created " "with the wrong parent (i.e. the hypervisor RP). This is now partially fixed " "and new resource providers are created now with the expected parent (i.e. " "the agent RP). However Placement does not allow re-parenting an already " "existing resource provider, therefore the following Placement DB update may " "be needed after the fix for bug 1921150 is applied: neutron/tools/" "bug-1921150-re-parent-device-rps.sql Until all resource providers have the " "proper parent, neutron-server will retry the re-parenting update, which will " "be rejected every time, therefore expect polluted logs and some wasted load " "on Placement. However please note that the bandwidth-aware scheduling is " "supposed to work even with the wrongly parented resource providers." msgstr "" #: ../../:510 msgid "" "When working with the ML2/openvswitch driver, the \"vlan-aware-vms\" feature " "has the following limitations:" msgstr "" #: ../../:398 msgid "" "While the bound port Floating IPs are distributed, the unbound port Floating " "IPs are centralized." msgstr "" #: ../../:261 msgid "" "With regards to Neutron RBAC, an issue exists when trying to delete another " "tenant's port on your own network if you are not an admin. This is being " "tracked with `this bug `_." msgstr "" #: ../../:591 msgid "" "[`bug 1811166 `_] Changes " "the API behavior to enforce that a router's administrative state must be " "down (``router.admin_state_up==False`` ) before modifying its distributed " "attribute. If the router ``admin_state_up==True`` when trying to change the " "``distributed`` attribute, a BadRequest exception will be thrown." msgstr "" #: ../../:107 stable/rocky>:151 stable/stein>:296 #: stable/train>:390 msgid "" "[`bug 1812168 `_] Remove " "Floating IP DNS record upon associated port deletion." msgstr "" #: ../../:376 msgid "" "[`bug 1999209 `_] Neutron-" "API now prevents internal IP change for floating IP. It will raise an error " "when deleting/changing the fixed IP which is linked to a floating IP." msgstr "" #: ../../:307 stable/2023.2>:427 #: unmaintained/wallaby>:159 unmaintained/xena>:182 unmaintained/yoga>:213 #: unmaintained/zed>:236 msgid "" "[`bug 2003455 `_] As part " "of a previous commit (https://review.opendev.org/c/openstack/neutron/" "+/875644) the `redirect-type=bridged` option was set in all the router " "gateway ports (cr-lrp ovn ports). However this was breaking the N/S traffic " "for geneve tenant networks connected to the provider networks through those " "routers with the redirect-type option enabled. To fix this we ensure that " "the redirect-type option is only set if all the networks connected to the " "router are of VLAN or FLAT type, otherwise we fall back to the default " "option. This also means that if there is a mix of VLAN and geneve tenant " "networks connected to the same router, the VLAN traffic will be centralized " "(but not tunneled). If the traffic for the VLAN/FLAT needs to be " "distributed, then it should use a different router." msgstr "" #: ../../:457 unmaintained/wallaby>:94 #: unmaintained/xena>:223 unmaintained/yoga>:323 unmaintained/zed>:304 msgid "" "[`bug 2003455 `_] It is " "added an extra checking to ensure the \"reside-on-redirect-chassis\" is set " "to true for the logical router port associated to vlan provider network " "despite having the \"ovn_distributed_floating_ip\" enabled or not. This is " "needed as there is an OVN bug (https://bugzilla.redhat.com/show_bug.cgi?" "id=2162756) making it not work as expected. Until that is fixed, we need " "these workaround that makes the traffic centrallized, but not tunneled, " "through the node with the gateway port, thus avoiding MTU issues." msgstr "" #: ../../:160 stable/2023.2>:383 #: unmaintained/wallaby>:106 unmaintained/xena>:61 unmaintained/yoga>:44 #: unmaintained/zed>:99 msgid "" "[`bug 2022914 `_] Neutron-" "API supports using relays as the southbound connection in a ML2/OVN setup. " "Before the maintenance worker of the API required a leader_only connection, " "which was removed." msgstr "" #: ../../:74 stable/2023.2>:56 stable/2024.1>:357 #: unmaintained/zed>:48 msgid "" "[`bug 2036423 `_] Now it is " "not possible to delete a subnet gateway IP if that subnet has a router " "interface; the subnet gateway IP modification was already forbidden." msgstr "" #: ../../:89 stable/2023.2>:79 stable/2024.1>:409 msgid "" "[`bug 2036705 `_] The " "Neutron ``port.status`` field (\"ACTIVE\", \"DOWN\") is now set based on the " "ML2/OVN Logical Switch Port ``up`` and ``enabled`` flags. The user can now " "set the ``port.admin_state_up``, that is replicated in the ``lsp.enabled`` " "flag, to enable or disable the port. If the port is disabled, the traffic is " "stopped and the ``port.status`` is set to \"DOWN\"." msgstr "" #: ../../:71 stable/2024.1>:394 msgid "" "[`bug 2045889 `_] The ports " "bound to ML2/OVN now contain the OVS bridge name and datapath type in the " "VIF details dictionary. NOTE: in the ML2/OVS to ML2/OVN migration, the local " "host OVN bridge (integration bridge) per port is not known; \"br-int\" will " "be used by default (that value is rarely changed)." msgstr "" #: ../../:341 msgid "" "[`bug 2052484 `_] Now " "setting ``[DEFAULT] rpc_workers = 0`` completely disables rpc workers. " "Previously one rpc worker was launched even though ``0`` is specifically " "requested." msgstr "" #: ../../:60 stable/ussuri>:55 #: unmaintained/victoria>:490 msgid "" "`1671448 `_ Access for " "Neutron quotas now governed using standard configurable RBAC policies: " "'get_quota', 'update_quota', 'delete_quota'" msgstr "" #: ../../:113 stable/train>:184 stable/ussuri>:300 #: unmaintained/victoria>:496 msgid "" "`1875981 `_ Neutron now " "correctly removes associated DNS records when an admin deletes ports, " "servers or floation IPs." msgstr "" #: ../../:66 stable/ussuri>:140 #: unmaintained/victoria>:200 unmaintained/wallaby>:447 unmaintained/xena>:678 msgid "" "`1926693 `_ The logic to " "detect the hypervisor hostname, which was introduced by `change 69660 " "`_, has been fixed " "and now returns the result consistent with libvirt." msgstr "" #: ../../:558 msgid "" "`1942329 `_ Port binding " "logic for direct-physical ports has been extended to allow providing the MAC " "address of the physical device via the binding profile. If it is provided " "then Neutron overwrites the value of the ``device_mac_address`` field of the " "port object in the database with the value from the active binding profile. " "If there are ports bound before `the nova side of this fix is depolyed " "`_ then the VM using " "the port needs to be moved or the port needs to be detached and re-attached " "to force nova to provide the MAC address of the direct-physical port in the " "port binding." msgstr "" #: ../../:286 stable/2023.2>:366 #: unmaintained/wallaby>:84 unmaintained/xena>:172 unmaintained/yoga>:192 #: unmaintained/zed>:215 msgid "" "`1986003 `_ Fixed an issue " "with concurrent requests to activate the same port binding where one of the " "requests returned a 500 Internal Server Error. With the fix one request will " "return successfully and the other will return a 409 Conflict (Binding " "already active). This fixes errors in nova live-migrations where those " "concurrent requests might be sent. Nova handles the 409/Conflict response " "gracefully." msgstr "" #: ../../:451 msgid "" "`1996677 `_ When the " "fixed_ips of metadata port is modified, the ip address of tap device in " "metadata agent is modified." msgstr "" #: ../../:369 msgid "``--ipv6-ra-mode dhcpv6-stateful --ipv6-address-mode dhcpv6-stateful``" msgstr "" #: ../../:368 msgid "" "``--ipv6-ra-mode dhcpv6-stateless --ipv6-address-mode dhcpv6-stateless``" msgstr "" #: ../../:367 msgid "``--ipv6-ra-mode slaac --ipv6-address-mode slaac``" msgstr "" #: ../../:110 stable/ussuri>:268 #: unmaintained/victoria>:339 msgid "``DVR`` routers now support ``flat`` networks." msgstr "" #: ../../:259 msgid "" "``[OVS]/igmp_flood_unregistered`` = True ``[OVS]/igmp_flood`` = True ``[OVS]/" "igmp_flood_reports`` = True" msgstr "" #: ../../:296 unmaintained/xena>:644 msgid "``admin_auth_url``" msgstr "" #: ../../:293 unmaintained/xena>:641 msgid "``admin_password``" msgstr "" #: ../../:294 unmaintained/xena>:642 msgid "``admin_tenant_id``" msgstr "" #: ../../:295 unmaintained/xena>:643 msgid "``admin_tenant_name``" msgstr "" #: ../../:292 unmaintained/xena>:640 msgid "``admin_username``" msgstr "" #: ../../:460 msgid "" "``all_rules``: if True, the listing call will print all QoS rule types " "supported by the Neutron server." msgstr "" #: ../../:458 msgid "" "``all_supported``: if True, the listing call will print all QoS rule types " "supported by at least one loaded mechanism driver." msgstr "" #: ../../:436 msgid "" "``openflow_processed_per_port``: by default \"False\". If enabled, all " "OpenFlow rules associated to a port will be processed at once, in a single " "transaction. If disabled, the flows will be processed in batches of " "\"AGENT_RES_PROCESSING_STEP=100\" number of OpenFlow rules." msgstr "" #: ../../:515 msgid "" "if security groups are desired, the use of the stateful OVS firewall is " "required, however that prevents the use of the DPDK datapath for OVS " "versions 2.5 or lower." msgstr "" #: ../../:275 msgid "" "max_fixed_ips_per_port has been deprecated and will be removed in the Newton " "or Ocata cycle depending on when all identified usecases of the options are " "satisfied via another quota system." msgstr "" #: ../../:598 msgid "" "max_fixed_ips_per_port has been deprecated and will be removed in the Newton " "or Ocata cycle depending on when all identified usecases of the options are " "satisfied via another quota system. If you depend on this configuration " "option to stop tenants from consuming IP addresses, please leave a comment " "on the `bug report `_." msgstr "" #: ../../:306 msgid "" "net-mtu extension now recalculates network MTU on each network access, not " "just on creation. It now allows operators to tweak MTU related configuration " "options and see them applied to all network resources right after controller " "restart, both old and new." msgstr "" #: ../../:275 msgid "" "notification_drivers from [qos] section has been deprecated. It will be " "removed in a future release." msgstr "" #: ../../:330 msgid "oslo.messaging.notify.drivers entry points are deprecated" msgstr "" #: ../../:640 msgid "partially closes bug 1468803" msgstr "" #: ../../:286 msgid "" "rule to allow all egress IPv4 traffic (for all default and custom Security " "groups)," msgstr "" #: ../../:288 msgid "" "rule to allow all egress IPv6 traffic (for all default and custom Security " "groups)," msgstr "" #: ../../:290 msgid "" "rule to allow all ingress IPv4 traffic from the same security group (for " "default security group in each project)," msgstr "" #: ../../:292 msgid "" "rule to allow all ingress IPv6 traffic from the same security group (for " "default security group in each project)." msgstr "" #: ../../:513 msgid "" "security groups do not work in conjunction with the iptables-based firewall " "driver." msgstr "" #: ../../:449 msgid "" "tenant_id column has been renamed to project_id. This database migration is " "required to be applied as offline migration." msgstr "" #: ../../:113 stable/2023.2>:103 #: stable/2024.1>:440 msgid "" "the Neutron server will report a warning during plugin initialization " "because this is an invalid configuration matrix. Floating IPs need to always " "be centralized in such a case. For more details see `bug report `_." msgstr "" #: ../../:549 msgid "" "the ``tos`` configuration option in vxlan group for linuxbridge is " "deprecated and replaced with the more precise option ``dscp``. The TOS value " "is made of DSCP and ECN bits. It is not possible to set the ECN value " "through the TOS value, and ECN is always inherited from the inner in case of " "tunneling." msgstr "" #: ../../:224 msgid "" "tunnel networks (\"geneve\" or \"vxlan\") should be used as tenant network " "types or" msgstr "" #: ../../:201 msgid "" "vhost-user reconnect is a mechanism which allows a vhost-user frontend to " "reconnect to a vhost-user backend in the event the backend terminates either " "as a result of a graceful shutdown or a crash. This allows a VM utilising a " "vhost-user interface to reconnect automatically to the backend e.g. Open " "vSwitch without requiring the VM to reboot. In this release, support was " "added to the neutron Open vSwitch agent and ``ml2`` driver for vhost-user " "reconnect." msgstr "" #: ../../:308 msgid "" "vhost-user reconnect requires dpdk 16.07 and qemu 2.7 and openvswitch 2.6 to " "function. if an older qemu is used, reconnect will not be available but " "vhost-user will still function." msgstr "" #: ../source/2023.1.rst:3 msgid "2023.1 Series Release Notes" msgstr "" #: ../source/2023.2.rst:3 msgid "2023.2 Series Release Notes" msgstr "" #: ../source/2024.1.rst:3 msgid "2024.1 Series Release Notes" msgstr "" #: ../source/README.rst:3 msgid "Neutron Release Notes Howto" msgstr "" #: ../source/README.rst:5 msgid "" "Release notes are a new feature for documenting new features in OpenStack " "projects. Background on the process, tooling, and methodology is documented " "in a `mailing list post by Doug Hellmann `_." msgstr "" #: ../source/README.rst:10 msgid "Writing release notes" msgstr "" #: ../source/README.rst:12 msgid "" "For information on how to create release notes, please consult the `reno " "documentation `__." msgstr "" #: ../source/README.rst:15 msgid "Please keep the following in your mind when you write release notes." msgstr "" #: ../source/README.rst:17 msgid "" "**Avoid using \"prelude\" section** for individual release notes. \"prelude" "\" section is for general comments about the release." msgstr "" #: ../source/README.rst:19 msgid "" "**Use one entry per section** (like \"feature\" or \"upgrade\"). All entries " "which belong to a same release will be merged and rendered, so there is less " "meaning to use multiple entries by a single topic." msgstr "" #: ../source/README.rst:24 msgid "Maintaining release notes" msgstr "" #: ../source/README.rst:28 msgid "" "Avoid modifying an existing release note file even though it is related to " "your change. If you modify a release note file of a past release, the whole " "content will be shown in a latest release. The only allowed case is to " "update a release note in a same release." msgstr "" #: ../source/README.rst:33 msgid "" "If you need to update a release note of a past release, edit a corresponding " "release note file in a stable branch directly." msgstr "" #: ../source/index.rst:16 msgid "Neutron Release Notes" msgstr "" #: ../source/liberty.rst:3 msgid "Liberty Series Release Notes" msgstr "" #: ../source/mitaka.rst:3 msgid "Mitaka Series Release Notes" msgstr "" #: ../source/newton.rst:3 msgid "Newton Series Release Notes" msgstr "" #: ../source/ocata.rst:3 msgid "Ocata Series Release Notes" msgstr "" #: ../source/pike.rst:3 msgid "Pike Series Release Notes" msgstr "" #: ../source/queens.rst:3 msgid "Queens Series Release Notes" msgstr "" #: ../source/rocky.rst:3 msgid "Rocky Series Release Notes" msgstr "" #: ../source/stein.rst:3 msgid "Stein Series Release Notes" msgstr "" #: ../source/train.rst:3 msgid "Train Series Release Notes" msgstr "" #: ../source/unreleased.rst:3 msgid "Current Series Release Notes" msgstr "" #: ../source/ussuri.rst:3 msgid "Ussuri Series Release Notes" msgstr "" #: ../source/victoria.rst:3 msgid "Victoria Series Release Notes" msgstr "" #: ../source/wallaby.rst:3 msgid "Wallaby Series Release Notes" msgstr "" #: ../source/xena.rst:3 msgid "Xena Series Release Notes" msgstr "" #: ../source/yoga.rst:3 msgid "Yoga Series Release Notes" msgstr "" #: ../source/zed.rst:3 msgid "Zed Series Release Notes" msgstr ""