Enable admin to control if ENS networks can be used.
In nsx_v3 section a new flag ens_support is added.
Change-Id: I99b885072964870fe61a26a5bab71c7ed0790c87
The vlantransparent extension's API definition was rehomed into
neutron-lib with commit I78c3e0c0b74dd154b6133963dfc8b65f9527bd2c
This patch consumes it by using neutron-lib's implementation in prep
for Ibfaa1ebf24caec62f5743975b206400fcd30436d
Change-Id: I8e2bf3fb75b3ccbcb269677fb2aa826659fbbdd2
Adding FWaaS v1/v2 plugins to be used with the TVD core plugin.
The plugins will make sure to separate the v/t returned lists
using the same solution that was introduced for the LBass, now as a
general class decorator.
Change-Id: I5f01b8cf093d5ef3b340dce2d12fc41031dd12e9
The multiprovidernet API extension's definition was rehomed into
neutron-lib with If3367e6a14074a6225bba527e8f7e38c51280f85 and will be
consumed in neutron via I12c15c360f8bf5a45fbe70e5ed1202ef0e7ec0f0
This patch switches the code over to use neutron-lib's multiprovidernet
API definition rather than neutron's extension.
Change-Id: I6803fdf363a674303f21241a59dc6a281c84d433
A service tenant may do a request for a speicific tenants data,
for example, ports (as in the case with a nova boot). So we need
to ensure that the filters requested by the tenant are met.
Change-Id: Ic7ff59a813347f943e6c84478d9f036c90473c9e
Upstream now supportes FWaaS v2 on compute ports, but our driver does not.
When trying to add a compute port to the Firewall group, its status should
set to Error.
Change-Id: Id5965197c58b940e2d33892023ff321a77eac82a
filter get_<>s results in AdminUtils to retirve only the neutron objects
that belong to the nsxv/v3 plugin
Change-Id: I2d0675764c6b10861949c69b2f152e585d790f21
The user of the TVD plugin can use the admin utilities of the nsxv/nsxv3 plugins
by calling:
nsxadmin --plugin nsxv -r <> -o <>
or:
nsxadmin --plugin nsxv3 -r <> -o <>
A separate patch will make sure that only the relevant neutron objects are being
retrived when using those utilities.
Change-Id: I813f69bf2e08f3845f0135fdb00666746f5d20c6
Catching up with different VPN api changes done in the NSX
Change-Id: I78263af403056c9282da5799b9f64b3d8f22b80d
Depends-on: I32d6593860844bd23bb251c3fe30957c6efb9c2a
1. Do not allow the same availability zone to be configured for both
NSX-V and NSX-T
2. Adding separate configurations for the nsx-v/t default availability
zones under the tvd configuration section:
[nsx_tvd]
nsx_v_default_availability_zones = zone2
nsx_v3_default_availability_zones = zone1
Change-Id: Ic77dae9398b8281b8ea4d2988447907d1ac55c90
The patch ensures that only a V tenant can see v resources and the
same for a T tenant/project.
NOTES:
1. In the neutron configuration file a new service plugin is created.
So we need the following:
[DEFAULT]
service_plugins = vmware_nsxtvd_lbaasv2
2. The extensions path needs to be updated so that the default LBaaS
extensions can be loaded.
So for example in the devstack case we need to configure:
[DEFAULT]
api_extensions_path = /opt/stack/neutron-lbaas/neutron_lbaas/extensions
Change-Id: Iea497cbb150048bedf712a195c7854e4836ad4a5
In FWaaS v2, the firewall group is attached to router interface ports.
When the last interface is removed, the firewall status should be set to
inactive until addign a new port.
Change-Id: I20a7566d80fa011772066ecd076a303b0fb07f99
If the nsx-v/v3 init fails, the registration to init_complete should
not be done, since the init_complete method might fail too.
Change-Id: I2b9550394f67f4dfb79dba9455f2d75af5d28802
