This reverts commit dec28f6d2b83700e96180b1b10b712799f0c76f7.
We needed to revert this as it broke the nsx cleanup utility
for NSX|V. This broke the CI.
Change-Id: Iffb05ab0c0bcb8c8184a0c821dece1e88cdd3fb3
- Support the case of empty neutron names
- Fix NSX local endpoints tags
- Support connection/service admin-state configuration
Depends-on: Ieb9da32b6f3b908dda7b4c5b99cb4ca2b79c9286
Change-Id: If5509fdcf3c496ad446921a3fb57b48deb6179f4
When using the TVD plugin, sometimes nsx-v or nsx-v3 are not configured.
This patch ensures that the devstack cleanup will clean only the relevant
NSX backend, to avoid errors in the logs.
And also that the devstack configuration will skip unconfigured plugins
Change-Id: I27ad52ea9a4052c0b8f3d1ea4d485fcc44b19f6d
Move neutron to requirements.txt Since neutron is now in
global-requirements, we can remove the installation from
tools/tox_install.sh.
Change-Id: I3d5aa6d61d1601358f6972a606c5a0a6fb5c2dd0
Instead of always trying to load all 3 plugins (v, t, dvs), the customer
can now configure those he wishes to support.
This way we will be quicker on neutron restart (and CIs) and avoid the errors
in the logs.
Change-Id: I9b41dc4002e7bd758dd46810763e70dbfc9202b0
Adds missing methods. Something changed witht he way in which
the callbacks were invoked which showed that we did not support
the correct methods.
Change-Id: I253ceee343d829923b874057603a32ccd8c662f6
Commit a96d83ece64d1ab662be8ee62eca15c3e3ab4c19 set the internal
security group description to be None. This should be a string.
Change-Id: Ia4b1e0cea3f4e1493e41bf1e97bcf3016e389bf9
Commit I123ae390bec489a931180a2e33f4bf7b1d51edb2 broke the extended
security group code, by removing the 'is_default' attribute from the
list of fields that should have been updated in the DB.
Not sure exactly why it broke us.
Change-Id: I891bc792e62ac90683ce8745f98a3139c9ffd3d9
When getting floating ips by port id, we should ignore the requesting
tenant since this is called via nova with a service tenant.
Change-Id: I557a9bb7071481e15c8be064a14cad583140991f
When the neutron network updated, some related NSX objects may need
be updated as well: DHCP server & port & metadata port
Depends-on: I07658bdaabe919f94dc877585206c76a1191f16c
Change-Id: Id563788af4b41aa360f8e87b28c310d1bab33feb
When a port is deleted, the plugin should delete its backend dhcp
static binding only if it is a compute port, since it is added
only for compute ports.
Note that the case of changing the device owner of the port was already
handled in the update-port code.
Calling the delete on non-compute ports issues a warning in the logs
We keep callign it anyway to avoid edge cases but will skip the warnings.
Change-Id: I5e76b14de0c2f2b844c7411bc325e46746fda54d
In Rocky we are going to start working on decoupling neutron db. This
will be a long effort, so from a vmware-nsx POV we can hopefully pick
away at it as we go.
This patch changes to use of class references to fully qulified class
names when defining ORM relationships. This allows us to remove a few
of the neutron db related imports in vmware-nsx.
Change-Id: I1df4cb3eec59488a5b35fac9f943bbfdbb44df63
The tier0 router should belong to the same transport nodes as
the subnets attached to the tier1 router which uses this tier0 as a GW
Change-Id: Idf216699ce110e8cd790779d3c4e63522800a845
Removing abuse and using get_by_attachement function
in nsxlib, in order to get the API url.
Change-Id: I68786ca57275d3d1e358b1b877947188823013c2
Signed-off-by: Michal Kelner Mishali <mkelnermishal@vmware.com>
When setting the gateway of a logical router, we should set the
overlay transport-zone-id as well, to allow vlan switches traffic
Depends-on: I3a447202785b7b6ac320ddbb6a3f2cdeac1f78aa
Change-Id: If94474f907938e2997951f1a4e8269de45063ec5
Commit I5867f77fc5aedc169b42f50def0424ff209c164c added new security
groups tests which the MH plugin does not support.
Change-Id: I574f73b77f900e9650f47f806b6928f02883c76a
The nsx-v3 plugin can add default Tier-0 router configuration per
availability zone. The Tier-0 rotuer will be used as a default for
external networks creation in this AZ.
Change-Id: I18e917a6b3deb40429626f7f0018e5da7ab72a8b
Plugin init should not fail in case vlan transparent is configured
while not supported by the backend.
Issue a warning instead.
Change-Id: Ie91d581ef74f2b8f9e8014c36d520b106aab3e9b
When the plugin starts it will check if the global NS group and
OS DFW section are created on the NSX. If not it will create these.
There is a edge case where two servers are started in parallel and
they both create the default section. This will lead to traffic
being dropped.
This is dealt with in the following way:
1. We store the default OS section and NS group in the database
2. If the entries do not exist then we create them, the DB will
indicate if there is a duplicate and then the plugin will do a
cleanup of the incorrect resources.
In order to do this we need asecurity group. A default global one
with ID 00000000-def0-0000-0fed-000000000000 is created.
If the admin wishes to delete the global section then she/he should:
1. delete the NSX section
2. delete the security group
3. restart the neutron service
Change-Id: Ide7a7c75efac3e49d51e522a11c77e754f3d1447
The patch does the following:
1. set instance vNIC to a common network interface
2. Live migrates to T cluster
3. Updates the instance vNIC to opaque network
Example:
nsxadmin -r ports -o nsx-migrate-v-v3 \
--property project-id=01dd52ff4c7047f79f6259f916c83790 \
--property host-moref=host-11 --property respool-moref=resgroup-9 \
--property datastore-moref=datastore-22 \
--plugin nsxv3
There is also an option to use net-name. The default here is 'VM Network'
Change-Id: I24d9df3f7a3dbd11dffb86427367b809e2b49409
