This patch moves the code over to neutron-lib's version of the
RESOURCE_ATTRIBUTE_MAP in prep for neutron commit
Iaacee584d499c4d33d6d2dd9609c7ac0f2cfc386
Change-Id: I09ad5d3a079ffe4494a5f609443be632f1cc9a21
The serailizes the threads.
This also removes unnecessary check the number of
member in a pool before adding the member to the pool.
Co-Authored-By: Tong Liu <tongl@vmware.com>
Change-Id: Ief2c655fcc7652f16ae1fc2c0b3ed0697f15ef27
When adding the FWaaS V2 rules to the NSX router, logical router ports
should not be used as source or destination.
Instead the logical swith id sghould be used.
Change-Id: I819127363f58a1fa9e63306ee4dbc7ca0819394f
For devstack: Content of policy.d should be copied over and
not the entire folder, or it creates dup of policy.d
and breaks things.
Change-Id: I8666d88d04c7a320922edcd4f7b03f588becdbc1
Signed-off-by: Michal Kelner Mishali <mkelnermishal@vmware.com>
Log a warning if the plugin is not supported, that is, if there is
an invalid configuration for the specific plaugin.
Change-Id: I3637337162bd31347be8bd40b3605ea4c4cb44f2
1. ensure that only the as_provider supported plugins are used for
metadata requests
2. make sure that we filter subnets according to the relevant project
type
Change-Id: I51a0a4453ee1f0e356c9b27bf4da3d81c865a39c
Today neutron-lib defines the CORE and L3 service plugin aliases in
neutron_lib.constants as well as neutron_lib.plugins.constants. The
later is preferred and the former will be removed.
This patch switches the code to use the plugin constants from
neutron-lib.
Change-Id: Ic41b180cb0e084f271d715d7433e22e1688c6498
New support for VPNaaS on NSX-V3 2.2
Creating a vpn service per neutron service,
and ike/ipsec/dpd policies + endpoints + connection per neutron connection
Change-Id: Iad3778c1d826ae67f1b602625f5be0fe2f4c8fe3
This patch switches callbacks over to the payload object style events
[1] for BEFORE_SPAWN and AFTER_SPAWN based notifications. As no event
data is passed for SPAWN notifications, an actual payload object is
not needed and thus this change uses publish() rather than notify()
and updates and callback receivers to accept the payload parameter.
Depends-On: Ifad4781d82aa07f213f4e075b0c9455aa95e94bb
[1] https://docs.openstack.org/neutron-lib/latest/contributor/callbacks.html#event-payloads
Change-Id: Icca5213d7372ea28204db50108d5f77e1acf400d
Both NSX backend does not support adding a static route with destination
0.0.0.0/#.
Commit Ibb4f81a484de48f7ea65cb2bb6968e55eae087ad failed the request for
destination 0.0.0.0/0, but it should be failed for any prefix size.
Change-Id: Id1c299ad49ef8f34aede9b876f23fdb7ac7203e4
When using the fwaas callbacks via the admin utils, we need to make
sure the init_complete method of the core plugin will not be called,
as it was override by the wrapper plugin used by the admin utils.
Change-Id: I79387d4d1757d89f31951a9ba60ef1322c4f59a7
If there are V and T security groups we should not thrown an
exception at boot time.
In addition to this the patch does not raise if an exception
occurs, it logs and continues. This will ensure that all configured
security groups will be treated correctly.
Change-Id: I39c36e6f72186ca41426a37b9091f2f08ece0c7d
In order for network availability zone field to have the right value
in the |TVD plugin, we need to separate the az-hints code from the az code.
the az hints is the same for v&v3 plugins and updated using a registered
extend method.
the az field logic is different in each plugin and updated direction by
get_network_availability_zones
Change-Id: Ife423b92d8861d8cde9a7ae265f86382505d2541
When there is a failure during the recycling of an edge appliace to the
backup pool, the edge at the backend may still be attached to networks
and use IP addresses which are free for reuse by Neutron.
Housekeeping job should address such cases.
Change-Id: I3a8ba622f742064bdc8906ba745da0a54a4576ac
