ostestr is no longer installed by default by infra and will be totally
removed longer term; stestr [1] is its replacement.
This is the reason out gate is failing with the following today:
nsx/tools/ostestr_compat_shim.sh: ostestr: not found
This patch moves us to stestr by:
- Updating tox.ini to use stestr rather than call ostestr_compat_shim.sh
and in turn ostestr.
- Removing ostestr_compat_shim.sh as its no longer used.
For more details on stestr see [1].
Also note that this is a quick migration to stestr to get the gate
working; additional tweaks may come up.
[1] http://stestr.readthedocs.io/en/latest/MANUAL.html
Change-Id: I9a871d3542c2f2615d757c0009ea3d6695f0e3f7
The public APIs that are part of neutron.plugins.common.utils were
rehomed into neutron-lib with Iabb155b5d2d0ec6104ebee5dd42cf292bdf3ec61
and will removed in neutron with commit
I1d63cbea463e92e1d2e053f8e1a564ed52cb84f8
This patch consumes the common plugin utils from neutron-lib
Change-Id: I54ef960de54bc3ae781af7ba9473729c94197d0d
The SHARED constant was rehomed into neutron-lib with commit
If123044496b54a8bfc115ab41b8506ec5d7ba5a3
This patch removes the SHARED constant from vmware-nsx and switches all
uses to neutron-lib's version.
Change-Id: I8ab75021399b5a85f5bfe8de858d8c4309b741dc
1. Better explain the security groups / nsx security groups / firewall sections
admiun utilities.
2. Also remove the unrelated firewall sections reorder form the fix-mismatch utility
3. fix some warnings that appeared when runnin g the utilities
4. Add new utilities to list/clean unused NSX sections:
- List NSX firewall sections that does not have a matching neutron security group::
nsxadmin -r firewall-section -o list-unused
- Delete NSX firewall sections that does not have a matching neutron security group::
nsxadmin -r firewall-section -o nsx-clean
Change-Id: Ie9868d1fb196964ce479bca2c42d4a6eea7ef427
When getting the AZ of a network for its DHCP profile, we need to
use the az-by-id api, so that the hints data is initialized correctly
Change-Id: I47525564af3622899b4f9ea1284207ec5c007679
The neutron.common.topics module was rehomed into neutron-lib with
commit Ie88b84949cbd55a4e7ad06341aab77b286cdc485
This patch consumes it by using neutron-lib's version of the module in
prep for Ia4a4604c259ce862597de80c6deeb3d408bf0e95
Change-Id: I34fb241499445e2a462b10815a26b79bded0fb78
NSX|V3: This feature will enable an admin user to configure a range
of VLAN IDs per VLAN Transport Zone, so when they create a VLAN,
the VLAN tag will be set accordingly.
The configuration is being done in the nsx.ini file, under the relevant
section for nsx-v3, the admin will note the tz-id, with either a
predefined range(s) (min/max values) or only the transport zone itself
(which means that any value can be chosen).
The admin user will create the network noting “provider:physical_network”,
if they select a VLAN ID, than it will be used, if not - one will be
chosen according to the configuration mentioned above.
New configuration variable in nsx.ini under nsx_v3: network_vlan_ranges
network_vlan_ranges=<TZ_UUID>:<min_val>:<max_val>
Change-Id: Id202ca28bda44286deacb5c9969ffd92aa564a90
Signed-off-by: Michal Kelner Mishali <mkelnermishal@vmware.com>
For each router interface subnets, we need to add NO DNAT rule whenever
NAT rules are added, or else internal traffic will be blocked.
Change-Id: I34d72b12289d6f6527bc114a32dac88281dd2cc4
Validate that the router does not remove the gateway if a VLAN is
attached. This is due to the fact that the router is centralized
and must be on a edge cluster.
Change-Id: I0d2d0ddb3c4beb8beeac9942db1e0259a5faf3a7
Initial version for an admin utility for migration of a project
from V to T
This code will first dump all the objects to a file, so the data
will not be lost.
Then it will delete each object using the V plugin,
move the project to the T plugin and recreate each object.
Usage:
nsxadmin -r projects -o nsx-migrate-v-v3 --property project-id=<V project to be migrated>
--property external-net=<T external network to be used>
Change-Id: I816b63f40ada945d321db4566224f8a964a39a8f
Adding service plugins for QoS, VPNaaS and L2Gateway
and updating the BGP plugin
to prevent users from getting objects belonging to a different
plugin
Change-Id: I3545c3acefaf50ca6937a0b7a65c131c569317cd
Treat a case where the spoofguard entry exists. One edge case may
be a reschedule and the port is not cleanued up.
Change-Id: I95fbbbd97d6ce1de55fe5a1f5016459e4fb200f9
The local address of the local endpoint for the VPN should be an unused
address on the external GW network of the Tier1 router
(and not the GW address itself).
To make sure this IP will not be used for anything else, a neutron port is
created.
The port will be deleted once the router (or its gw) is deleted.
The ip will be used for all the vpn services & connection on this tier1 router.
Change-Id: If956fd08f5c9cfde5cba9326c18d1d489c47a505
Certain resources require certain filters. For example, a V user,
where the service tenant is T will not show the IP addresses on the
'nova list' command. This requires that the 'id' be filtered.
Change-Id: I8b563d1b80974bcee3ed839eaec202052a8ec784
Traffic to ports that have port security and port security enabled
will by default be discarded. A configuration variable has been added
with default False so that there is not a degradation with the current
behaviour.
The variable is use_default_block_all.
Change-Id: I5569234de01c116d1ad3161cfaf54404467f6816
When creating a loadbalancer via TVD, we need to verify that the assigned
subnet belong to the same plugin as the lasdbalancer
Change-Id: Ia4a288177b06e5e795b3b7753d8571b36700f5b3
When getting networks/ports/etc with filters, we should filter by
the context plugin even if filters are added to the request,
unless the filters are very specific.
For example - when filtering by device id, the project should be ignored,
or else router GW ports (which have no project) will not be deleted.
Change-Id: Ib41bb5eca39ae0cd6b16ead60db0ecd528eb4638
The is_extension_supported function now lives in neutron-lib. This patch
uses lib's version rather than neutron's in prep for commit
Iccb72e00f85043b3dff0299df7eb1279655e313e
Change-Id: Icdfab398a452b4c1ee98863e88dbb6708e42a12c