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
Neutron allows deleting a router with gw set. For distributed router's
gw, we actually nees a plr and a internal virtualwire to support
implementation. When deleting a distributed router, we needs to verify
and clear all these components.
Change-Id: I7088a90acf1635ea0dbc20bbc6835835df24b07e
Fixes-bug: #1505008
VDR dhcp edge is exclusivly for vdr and in concurrency environment,
there is a chance that subnet would use this edge for dhcp service
and lead to errors.
Fixes-bug: #1502401
Change-Id: I66f5e291d760543a38281b9b17783fa6c1ee974b
When a VDR is attached to a network, but not as a default gateway, it will not
receive metadata requests and therefore should not be attached to the VDR
dedicated DHCP server.
Change-Id: I3707b469842002c7721ecfa144062293e1d198ac
Generated this test-list from tempest. Commented out tests
that are expected to fail due to missing feature integration.
We will uncomment those once security group, L3 patches are merged.
Change-Id: I622a788a3d5fe8394c2daafaab31a84dfc5a3825
This patch fixes NSX-v unit tests to deal with some recent changes
in neutron concerning tests for subnets with prefix delegation (pd).
Also, the logic for creating v6 subnets is updated in order to take
into account pd subnets, and ensuring the CIDR's IP version is
correctly verified.
Change-Id: Iaa428417a816f0436cc637797cbd220059518962
Hopefully this will allow the Zuul "Depends-On" thing to work better.
Adopting the solution developed by Doug Wiegley for LBaaS:
c61f920f2a54fd829ee37484b3743ab77b909847 and then shamelessly stolen
from armando-migliaccio here: If358edd5cf34fd63b508dc089615bf19d59ee334
Change-Id: I69c53bb2098b30927726e03c6c492a2fb58d4cc2
In addition to dhcp extra opt support, this
commit also enables the dhcp extra opts
unit tests for the nsx v3 plugin.
Change-Id: If9e51fe93bd62fa27abdf6349ddd053fc6e1d325
Add test which checks whether database models and alembic migration
scripts are in sync.
Change-Id: I64f2f468c7d6cf6ecb21172781b8126478003f28
Related-bug: #1470678
When adding interface on vdr or update subnet, we would update the
present dhcp edge's static bindings by DB query. But we lose some static
bindings since not elevate the query right to admin right.
Change-Id: Ic23262c48913c9fbda0cc1295908692590ea9ef6
Fixes-bug: #1502401
This happens when mixing metadata and routing. The patch fix the problem
by integrating static, routing and metadata routes whenever update TLR routes
Change-Id: I20e3edb53df6eea24fc3c5670d40a747db5cefed
Fixes-bug: #1500817
When creating a router, sometimes db process succeed but edge failed
at the backend. The patch add exception handle for creating router
and delete the router db if failed at the backend.
Change-Id: I81d683b201d44abeb6049b3b91139f2f898f1777
Fixes-bug: #1497869
agentless metadata mode works only in NSX-mh 4.1 - nsx.ini
incorrectly states is supported from 4.2 onwards.
Change-Id: I315665ffdd3f36205dba9e02a3a9dfaca12d0faf
When tenant creates fip associated with a provider router
(exclusive/distributed), nsxv plugin would report "Router not found"
error due to not elevating context.
Fixes-bug: #1500128
Change-Id: I61b9c4344c712d16b1f4510305224ff4ca7ed7ae
rp_filter configuration differs between NSXv 6.1.x and 6.2.
As future versions' behaivor is same as 6.2, version checking should change
accordingly.
Change-Id: Id6afcc17deee4fd9741b1cd245bd24918380b73e
It makes people confused that distributed router is exclusive/shared router.
This patch disable router_type configuration when creating router and remove
router_type when displaying distributed router.
Fixes-bug: #1499248
Change-Id: Ie427dc5fae118567e45b48953e24afbceed6f754