- Fixed below error while running testr tool
- Module changed from oslotest to tempest.lib
Error:
File "/opt/stack/vmware-nsx/vmware_nsx_tempest/tests/base.py", line 18, in <module>
from oslotest import base
ImportError: No module named oslotest
Change-Id: Ibda31e166db20ecb3422897c5c8194f57a3ceca6
NSX backend doesn't allow a subnet in 100.64.0.0/10 range
attached to a router. Thus we enforce this in the plugin
when creating a subnet.
Change-Id: Icf3c62a40744577d29bb052e5b90b5999c0ba7df
Contexts are not thread safe and therefore, methods which are called
as thread entry point should create their own context, and pass to
any called methods which are using contexts.
Change-Id: Ia8629c211807972d228358893a7b787c55b5be7f
Filters accept list of ports in the query instead of a single
port id. This led to get_floatingips returning empty list
even if a floating ip exists for a given port.
This patch removes the redundant get_floatingips method and
passes a list instead of a single item in TaaS driver.
Change-Id: I349f9ad16edb4e5069c70d209ccd7537f59620ec
For devstack ensure that this is always set. This willenable the code
to work for native and non native matadata support
Change-Id: Ibdf0031d99fedbe3cbeb1f40dd19d52b7669d4bb
For IPv4 external networks and provider networks, NSX-V plugin will use
the NSX-V backend IPAM.
To enable this option set 'ipam_driver = vmware_nsxv_ipam' in the
neutron.conf
Change-Id: Icdc3e7d24dac08a29f045f10fcea9ec4496b8446
Make sure that the credentials are set when spinning up a devstack
component that requires the OVS then we enforce that the NSX validations
are done.
This is necessary to determine how we configure the OVS manager.
Change-Id: Ibeec9e72ddea45b24ffde5e25b2ca8347c34bd43
A admin may create a provider network with a port group that already
belongs to a spoofguard policy. This patch does three things:
1. Enables the portgroup to have an existing spoofguard policy
2. On roolback does not blow away the portgroup
3. Ensures that a predefined spoofguard policy is not deleted
Change-Id: I66a73e9b697cd4afbecaa8df84a07164df5eda2a
Backend edge pool have more than maximum number of edges at the backend.
The bug is introduced partly due to commit
I42b632ba7c66cd4fc5e57e6bb91c9c91ec513622. When we try to collect one
edge into backup edge pool, we would first put its status to UPDATE in
case of other service using it. But we didn't add the UPDATE status edge
when we getting backup edge number. The patch fixed the bug.
Change-Id: I674c2f74fc03dceb7911f59353176ebad1637947
curl command without -1 doesn't work on RHEL in case of https so
need to use -1 to force it to use TLS version 1.
Also verified that it works on Ubuntu w/wo -1
Change-Id: I855e41c3348233a395ad94ac46a8d1eaef6dd7ff
This follows the commit 60ae70dde196191217c8c46242be283c7fd30039.
That code has been approved upstream
Change-Id: Ibe283886cf81822750db4b1dedfa69cdac1f7e43
When disabling snat flag of router, we would consider it a NOSNAT user
case. For this case, we need to advertise connected route so that the
internal networks of router would be accessible from outside network.
Change-Id: I6f92384bd19563ac4f9e812765a4a9a93e0c2087
This patch restricts the deleting of an provider security group only
to the admin thus preventing the tenant from deleting it.
It also prevents a non admin user from adding or deleting rules from
this group.
NOTE: we are using the following policy.json entry to prevent the
creation of a provider security group by a normal tenant:
"create_security_group:provider": "rule:admin_only"
Change-Id: Ie195225654b0c7cd8cfb715691c5a3bb4c8ee13d
The following patch in neutron:
a92647300d0148d5d23f7c16631b192923702a1f
checked the paths to where the securitygroup_db models were located. This
patch fixes the issue by updating the path in the vmware-nsx repo so the
tests pass again.
Change-Id: I7d81ce5cd7ee76928f607d6976ae90b1a7d976a1
Ensure that a AZ is returned. There may be an edge case after a
migration that there is no AZ configured.
Change-Id: I56c33f5f331781c1874b8d3fed73f6c2ad90095c
Under load the NSX may throw an exception when trying to update a
attached router port. A update to the port would
lead to the following exception:
"Managing the LogicalRouter attachment on LogicalPort is not
supported. Please use LogicalRouter APIs to do these operations."
We should not fail on this.
Change-Id: I0f7e0489c2797f0f84c0b33206c203650eec1e7e
If router_update fails with a ManagerError then the exception
handling may use an unassigned variable.
Change-Id: I46f44dea7e08c5c5108480ddd0ec449f006aca7e
Recent change If2fe1e014b78703ff0a9cdff1e4e8d45f3a4a16d
broke L2GW driver for NSXv3. This patch makes sure that the driver
starts and creates bridge clusters using the new nsxlib.
This patch adds a callback to create default l2 gw after the core
plugin is initialized.
Change-Id: Iced699b13e265f515c23fcc952ba9bb1e64b5762
This patch changes the workflow for L3 SPAN such that the destination
port must have a L3 reachable IP address i.e. a floating IP so that
L3 SPAN can work. Unit tests will be added in a separate patch.
Change-Id: Ie0c2aed71988cbbd9cba60bb1fcb1ec30d0b4bc4
