Since NAT is not a use case for ipv6, all connected ipv6 subnets
need to be advertised. There seems to be no way to add single rule
for all ipv6 subnets, therefore an allow rule will be added for all
ipv6 subnets.
Change-Id: Iaf89738f8d71a2f743ba699bebd5c8361c130a3c
While creating a LB service on a LB service, the router id is not
available and should be set while setting connectivity during member
creation.
Change-Id: I7667311e4d4721bc8b19697c3dbf2e9fc31214d7
IPv4 dhcp config could take the wrong fixed IP for dhcp port. This
patch ensures IP from correct subnet is taken.
Change-Id: Ieceeba30c6f4f7ee703f84f45173f6e172af9557
Ensure the right NSX client library is used, add
method for creating tags on session persistence
profile.
Change-Id: Ic2998af1f629d55b3cde4d4e1c14f3aa620cee8b
Since vlan subnets are attached using service interface, the plugin
can assign ndra profile on subnet level.
For same reason, exclude vlan subnets from consideration when removing
slaac profile from router.
Change-Id: I742795ee80543d5a18ad701a964f3e40d07a2699
When deleting a backend resource after the neutron resource was
already deleted, ignore resource not found error, but fail the
neutron action with a message to make sure the user is aware of
the zombie resources on the backend
Change-Id: Id1d949c3fb462a4a9eff4e0b87700ec988700098
Subscribe to a callback that will be called upon security group deletion,
and will look for rules with this SG as their remote-group-id and
delete them explicitly.
Else, those rules will only be deleted from the neutron DB, without
the NSX backend being aware of this.
This code was added in the common plugin, and will affect the V, V3 & P plugins.
Change-Id: Ie01dc29efaa3bf30ac314f45542d83f5a4cf238f
Deleting and recreating a service may fail becasue the purge cycle was
not over yet.
Instead of waiting for it, a random id will be used.
Change-Id: I2421146592f18bf77cd4c6631aa4af03086fe0ae
In neutron, slaac is enabled per subnet. However on policy
slaac is router configuration.
In order to avoid another passthrough API, router will be
configured with slaac profile if at least one of its subnet
has slaac enabled.
Change-Id: I7a055aa4d73425011c22248c8d7d9d2e0a383dc8
Following updated support on backend, removing the need for
passthrough API when enabling enable_standby_relocation.
Change-Id: Ic1588f8aeb83115d5c51c94477b4f8e93fefafa8
Signed-off-by: Michal Kelner Mishali <mkelnermishal@vmware.com>
1. Even if the group was already created,
verify it is a part of the exclude list.
2. Add the new group to the ex clude list,
without removing existing groups.
Change-Id: I65e1b8aff6a250185c4cb6bdfac82e8a8e9289bf
Until I1a566353b7fb125184849b3a0f864d3ef6896d94 is merged, switching back
to use octavia exceptions directly instead of octavia-lib ones
Change-Id: I515c6b31a9921ce213a3e80dd1c06b2c3b3d2352
Upon network create, for the MD proxy support hte plugin needs
the nsx id of the newly created segment.
The first cehck for realized id will surely fail, so this patch
adds a short sleep before that.
Change-Id: Ieba153b3441b8db875c78c94ff4d4d80441d76b1
According to RFC ND solicitation and advertisiment messages can
be from unspecified address or to multicast. Thus address-based
membership would not always work.
This patch allows ND packets globally.
Change-Id: I0e926986e0446d5f67b7f1ddc4bf051e7513d4ac
