Newton version of neutron_lib does not have L3 defined in constants. Using plugin_constants instead.
Change-Id: I6c665ab55c0a47281919acb52a5f7238a6d6180a
Latest neutron has shuffled the 'callbacks' module to neutron_lib,
updating the imports in mech_vpp.py to reflect this.
Change-Id: I6e02fa2d995a7ee48f1497ad422424624083ba7b
This recently (Pike-Queens) moved from neutron.plugins.ml2.config to
neutron.conf.plugins.ml2.config and this patch adds a layer in compat.py
to insulate us from that, and also rejigs ml2_vpp config so that the
options for etcd live nearer the code that uses them and in general all
option registering works in a similar fashion.
Addresses-the config problems that were band-aided over in change
Idbf622591e8d92d8e29e3a92799d0e7ff460354a.
Change-Id: I18767336f05a0fdcebfe16ddd46c2a5325d4e661
The usage of get_random_mac in the neutron.common.utils
is deprecated for removal in version Pike, and usage of the
get_random_mac from neutron_lib.utils.net is recommended in
new version Queens
Change-Id: I54b40da91c2d7c3c5632993352d5c1a9c4aa7814
Co-Authored-By: Ian Wells <iawells@cisco.com>
When running Mitaka with certain combinations of plugins, the
enable_security_group option is already added and should not
be added again. This prevents that.
Change-Id: I30423480751fbf884dd8108b85db7664bee9de45
This is imperfect, because our compatibility layer that allows
us to work with older versions doesn't cover all the necessary
Neutron inclusions, but excluding N530 we have a pass.
Changes fit into categories:
- LOG.warn -> LOG.warning
- log messages now have kwargs if more than one argument
(not essential, but used to be for translation and seems
to be a good practice anyway)
- exception messages must be translated
- translated messages must have named positional arguments
- oslo_serialization.jsonutils must be used, not json
- [] can't be a default argument
- compat is marked with N530 as, there, neutron imports are
expected. In other places the mark has been left off, and
the tox check has been disabled (for later enablement via an
RFE)
This should not include changes outside of that set.
Change-Id: I1dc050f83a5199bf40117eac6c9adae221ae6857
This patch supports the VXLAN-GPE overlay networking capability using ml2
vxlan type driver. To deploy the GPE overlay, set the following options in
devstack - GPE_SRC_CIDR and GPE_LOCATORS. These devstack variables are
translated into ml2 config options named gpe_src_cidr and gpe_locators.
The gpe_src_cidr is the source IPv4 or IPv6 subnet/mask used for the GPE
underlay (uplink) interface. The gpe_locators is the name the physnet
functioning as the uplink source interface used by vxlan-gpe for overlay
encapsulation. In the current version, only one GPE locator
interface is supported. Also vxlan-gpe requires static ARP entries on
tenant instances for reachability.
Closes-Bug:#1676496
Change-Id: I8ddbf01e1436e2a1a258d602297b0426f194f295
BridgeDevice doesn't come with disable_ipv6 function in Liberty,
port this function from newer neutron upstream.
Change-Id: I035954a14e56be8a13ddb56844f35e2e4b740d51
Closes-bug: #1666354
This patch refactors networking-vpp to use portbindings
from neutron-lib. For more details see [1].
NeutronLibImpact
[1] https://review.openstack.org/422210/
Change-Id: Id97094de943fc1fea57390e6a4abb98c30a659c7
Signed-off-by: Christophe Fontaine <christophe.fontaine@enea.com>
One of the imports works for Newton but not Mitaka, leaving Mitaka
to fall back to a bunch of imports that don't work for it. Break
conditionals up.
Change-Id: If8d2ba23728646786ab29752b4207de9eece4d2d
Move all the backward compatibility conditions into
backward_compatibility.py for sanity. This includes a number
of module name-change management bits, and some monkey patching,
all of which existed in the codebase before; we're just trying
to rationalise the locations and the conditionals.
Change-Id: Ifa7769758c2f66f094da40fef67f5213094c43cd
