Reviewed: https://review.opendev.org/c/openstack/neutron/+/866127 Committed: https://opendev.org/openstack/neutron/commit/70a86637e71eb67e7785f090ebc1045040bca897 Submitter: "Zuul (22348)" Branch: master
commit 70a86637e71eb67e7785f090ebc1045040bca897 Author: Rodolfo Alonso Hernandez <[email protected]> Date: Tue Nov 29 19:43:09 2022 +0100 Allow shared resources between physical and tunnelled networks Since [1] it is possible to create resource providers for tunnelled networks and model the available bandwidth for overlay networks. In some deployments, the admin uses the same physical network interface for a physical network and the tunnelled networks. In that case it is complicated to correctly split the bandwidth between the inventories of the resource providers. This patch adds the ability to create a resource provider with traits of both the physical network and the tunnelled networks. E.g.: $ openstack resource provider trait list $brex +----------------------------------+ | name | +----------------------------------+ | CUSTOM_NETWORK_TUNNEL_PROVIDER | | CUSTOM_PHYSNET_PUBLIC | | ... | +----------------------------------+ With this resource provider, a request comming from a port in the physical network or an overlay network is provided by the same inventory. [1]https://review.opendev.org/c/openstack/neutron/+/860639 What is missing and will be added in next patches: * Tempest tests, that will be pushed to the corresponding repository. Closes-Bug: #1998202 Change-Id: I801e770fd8b4d6504f5407108e1d1fd848f96c09 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1998202 Title: [RFE] Allow shared resource providers for physical and tunnelled networks Status in neutron: Fix Released Bug description: This RFE is an extension of https://bugs.launchpad.net/neutron/+bug/1991965. The goal of this RFE is to allow to share the same resource provider for one physical network and the tunnelled networks. This is a very common deployment configuration: there is one physical network and one device connected to this physical network bridge. This is used both for the VLAN tagged traffic (physical network) and as VTEP/TEP for the tunnelled traffic. In this configuration, the resource provider used for the physical network (e.g.: br-ex), must be shared with the tunnelled traffic. Related bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2097932 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1998202/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
