This patch will create:
vmware_nsx/plugins/dvs for DVS specific files
vmware_nsx/plugins/nsx_mh for MH specific files
vmware_nsx/plugins/nsx_v for nsx_v specific files
vmware_nsx/plugins/nsx_v3 for nsx_v3 specific files
also move vmware_nsx/vsphere/ to vmware_nsx/plugins/nsx_v/vsphere/.
This is part of new vmware_nsx directory structure proposed in
https://goo.gl/GdWXyH.
Change-Id: I00ee12da2eea0add988bae3d4f3e12940ea829bb
When metadata configuration is deployed to a router or DHCP edge, it
overwrites the existing LB configuration. This operation cannot be concurrent
with any other transaction on the edge and therefore cannot be asynchronous.
Change-Id: I77465a572a8f07a3fd248386899dfd3de27791f1
This patch will create:
vmware_nsx/services/common for common plugin files
vmware_nsx/services/nsx_v3 for nsx_v3 specific plugin files
This is part of new vmware_nsx directory structure proposed in
https://goo.gl/GdWXyH.
Change-Id: I30753aef1c06e2a1b15d336e1d661f3b44ea669e
This is the minimum localrc required for setting up the nsx_v3 plugin and
openstack components (nova/glance/keystore/horizon).
Change-Id: Ia92ddfd1e39aa6edf350d5807902fbf33995581e
All opertaions that are menat to be atomic should be done across
multiple API workers. This patch ensure that this is done globally.
In general the plugin can and should run with multiple API workers.
Change-Id: Ifdd4aa7b4254d4a35783d9749085405c17b038ce
Having the neutron id in the nsx backend is helpful to aligning which
resources in the nsx backend match to their neutron counterpart since
their id's do not map one to one currently.
Change-Id: I2a438285e03333e2ca07921476f8fe5d56743b83
Because vmware plugin config nsx.ini is now moved
from neutron:/etc/neutron/plugins/vmware/ to vmware-nsx:/etc/,
we need to update associated references in setup.cfg.
The new path to nsx.ini is defined in Q_PLUGIN_SRC_CONF_PATH.
This is the first part of vmware plugin decomposition
(etc, extensions, and database).
Partial-bug: #1483453
Depends-On: I3caf25ce91ff425d815f35ed3efd599a572d595b
Change-Id: I326dc1eaf549ac631caf71e9adc3c7a218a7723f
The patch includes these parts:
1. add update resource with retry feature
2. add ext-gw-mode, extraroute extension support
3. add router interface basic implementation
4. add L3, FIP, ext-gw and extraroute unit tests
Change-Id: Ia5c28fd27d253c0938537f1c9a474d7d2f68d715
external network is attached to default tier0 router by default, else
attached to tier0 via --provider:physical_network
DocImpact
Change-Id: I3fa4e1a6955d47f68f86b36f214ce4a43daefe5b
When we detaching subnet from one dhcp edge and deploying a new dhcp edge
for the subnet, there is a chance that we would use a duplicate name for
the new dhcp edge and it would lead to duplicate name error at the
backend. Since the edge name is just a tag that we can easily read and
it would not be used in plugin, the patch fixed the problem by using a
randomly unique edge name.
Change-Id: Ia764ec8c7b54e78ed36f827df4e3025d6e309062
Fixes-bug: #1508633
When we delete a subnet from dhcp service edge, we would delete the
edge if this is the last network on the edge. there is a chance here
another creating subnet select the edge for dhcp service. Overlap problem
may happen under this condition. The patch fixed the problem by
ensure nsx-edge-pool lock on create_dhcp_edge_service,
update_dhcp_edge_server and delete_dhcp_edge_service.
Fixes-bug: #1505087
Change-Id: I28b0c28b917a3d98daf9449193ce53e383d15aaa