Commit I14702ddcc5c32ba34b5f905a15cd816a69ef2b49 broke our tests
becasue of a missing import.
This is a temporary fix until the import will be added to the sfc
tests base class.
Change-Id: Ib24b346f651d07cc869d95f82d250065f5c3ce0f
The maximum page size is 1k in nsxv3 API response. Current read
logical resources only return maximum 1k. Change the nsxv3 client
to read all of the logical resources.
The update applies to GET API calls of logical resources.
Change-Id: I4d1f51c900e5ca89f1da8a5df13a535991765720
This patch adds logic to distinguish when to reset or
make no change on the attachment in the backend during
create_port and update_port.
Change-Id: I46017a9756d807267b489e32bfdd20b4a2f65800
The addCleanup_with_wait method has been deleted from upstream.
(Ief79a6cee55ff5faf64465f6cbc84bec8253a3e1)
A few of scenario tests failed because of this. Migrate this
function back to our internal manager_topo_deployment class.
Change-Id: Ia0a491df7ca93249e31ac014ba38e55c2c2289f8
When a shared router is the only router on an edge, and the gateway
is cleared, we should remove the static routes and default gateway
before removing the interface, or else the backend will fail because
the default gateway is illegal.
Change-Id: I7d1ff6e30d3e51f84d76292b76e550792c19315a
Address some broken IPv6 unit tests. These broke the gate. They
will need to be addressed when the plugin supports IPv6 for the
NSX|V.
Change-Id: Ide0b7a13f5104c998a19d06eaa851c9abe044edb
When the attachment is reset on a neutron port
(for example, a VM is deleted on a pre-created neutron port),
the attachment type/id will be reset on the corresponding
logical port. But currently the plugin doesn't do it
because it skips passing the attachment attribute if it is None.
Change-Id: Iacccf6dce1780c0cb6bc8332e065482d699e5cb9
In case of multiple NSX managers in the nsx_api_managers configuration,
it is now possible to configure a different username/password/ca_file for each
of the managers.
The nsxv3 configuration parameters ca_file, nsx_api_user & nsx_api_password are
now lists.
If they contain only 1 value, it will be used for all the managers.
Else, the order of of the values is expected to match the order of the
nsx_api_managers.
Change-Id: I31b955c9ee449126acde96de48a1887b94c38e29
This commit creates a vmware-nsx REST API extension
API reference document in github flavored markdown
format. The API ref herein only includes extensions for
NSX-v and NSX-v3 as MH will be deprecated.
To view this document as-is rendered see:
https://github.com/bodenr/vmware-nsx/blob/api-ref/api-ref/rest.md
Moving forward we can keep this doc in sync with our
plugins so that consumers can just view the git tag
on github to see the related api ref for their release version
of the plugin. e.g.
https://github.com/openstack/vmware-nsx/tree/stable/{REL}/api-ref/rest.md
Closes-Bug: #1601861
Change-Id: Id2af02fc629c398835ea216cfc19d8bbf583fa4c
When a shared router or a DHCP edge is removed, a metadata network
port might be associated with it. If so - we should associate with
a different router_id which resides on the same edge.
Change-Id: Idb2aa73dd44bed25c58d9d2294a48520fbb4ac66
When a shared router is updated to become an exclusive router,
the metadata interface should also be created (if supported)
Change-Id: I515641055b74b4b1b7e75a6c2b48ae5f2ece2531
Fix the problem where the change of dns_servers or gateway_ip
during update_subnet is not pushed to NSX backend.
Change-Id: I79af8d7ac593acad0d129b0252ece82372ab5440
When a nova instance is deleted without removing the associated
neutron port, the device_owner of the neutron port will be reset.
Thus the plugin still needs to clean the old DHCP binding.
Change-Id: Ie0e5f59a7ee2dfcc7238d6982ff6aa32e34520d5
While removing the last DHCP-enabled subnet interface from VDR, a
regular DHCP edge should be attached to the subnet's network.
Change-Id: Ie87fb708c561fa54a457f006f60d407a369dd0bf