Since l2gateway binds vxlan(virtual side) to vlan(physical side) segment.
We are extracting only vxlan segment from the virtual network.
Since multi segment network can have multiple segmentation id's belonging
to different network types(vlan, gre, vxlan, etc), we are extracting the
vxlan segment from it.
We are checking for multiple vxlan segments in the network since ovsdb
does not allow multiple vxlan segmentation id's to associate for same
vlan (physical side) while creating l2_gateway_connection.
For Ex: say multi segment network has two vxlan segment id's 1000 and 2000.
If we create a l2_gateway_connection for this network by providing physical
side vlan segment as 500, the bindings should be 1000:500 and 2000:500,
this is not allowed in ovsdb hardware vtep schema.
Closes-Bug:1511639
Change-Id: I5f704eaf40763686aa30320dff7a99a16b6c1772
call add_port_mac in l2gw_callback for port update event
as a normal call rather than in thread.
Change-Id: I95ebef23dc5d2bfc3d406c0ac0acd7318485973d
Closes-bug:1511651
This patchset implements the UcastMacRemote deletion after
the corresponding switch is deleted or disconnected from the
OVSDB.
Change-Id: I383412b523d7c96b85735e18202450edf71fc6f1
Closes-Bug:1453736
This allows neutron-db-manage to find the alembic migrations
automatically if this project is installed.
The config file alembic.ini is not needed in this project since it's
tables are in neutron's DB and so it depends on neutron's config.
Remove the l2gw-db-manage script since we will use
neutron-db-manage.
Update the alembic env to know about all neutron core tables when
generating diffs for --autogenerate.
Partial-Bug: #1470625
Depends-On: I9a06de64ce35675af28adf819de6f22dc832390d
Change-Id: I581932d333e378d91d5b581760018ec274330681
The patch set handles recreation of tunnels
when openvswitch is restarted and it also proposes
the fix for exception thrown while adding vm port
after l2gateway connection to ovsdb
Closes-Bug:1452192
Closes-Bug:1452149
Change-Id: I3ccdd64272adc2d008da69fdd2652b029368fb44
Co-Authored-By: Phani Pawan <ppawan@hp.com>
The patch set fixes the problem described in a launchpad
bug, where any failures in inserting/updating/delete MACs
into the OVSDB server do not get retried in a later
point in time. The failure may occur when the L2 gateway
agent is down or the OVSDB server is down.
Change-Id: I79956f498c3279e1c78be812563a32c2c41e77ca
Closes-Bug: 1446805
Closes-Bug: 1451765
This patchset addresses the changes where deactivating
switch/ovsdb should delete l2-gateway-connections.
Change-Id: I8be62153e24696c4b265b7634ab172fbd4a2bda5
Closes-bug: 1447453
Creating l2-gateway-connection gives internal
server error if invalid device or invalid interface
is specified.
Change-Id: I5a738b085400b3937dd4f03076233853d05133d0
Closes-bug: 1447467
The patch set fixes the problem described in launchpad
bug 1445770 where l2-gateway-connection-delete reports
an error when there are VMs on the network associated
with the connection.
Closes-Bug: 1445770
Change-Id: I76278bda7bfbd3cc997166ca13f985878e06a5cd
The patch set handles VM migration usecase for
L2GW. Basically, it updates Ucast_Macs_Remote
table record for the port associated with the
VM being migrated and inserts new entry in
Physical_Locators table if that locator does not
exist.
Closes-Bug:1438637
Co-Authored-By: Koteswara Rao Kelam <koteswara.kelam@hp.com>
Change-Id: Icf1a973cd3e3ac5e889c7a63405471062f1f9a0d
The patch set fixes the problem described in the launchpad
bug 1445153, where the L2 gateway service plugin was getting
an error while inserting VM MAC address into the OVSDB server
when a new VM is booted on a network for which l2-gateway
connection exists.
Change-Id: I7e84a91f6e37c4bf557f8536b95b91f4a08f427c
Closes-Bug: 1445153
L2Gateway creation for multiple segmentation ids for an interface input and output for rest api is not aligned.
This defect found only in case of user passes multiple segmentation id .
Change-Id: Ie615afbe71dc0bd746fe475a932ee0143ccebfe0
Closes-Bug: #1439035
The patch set fixes
1. a problem described in the
bug 1440301 where the L2gateway agent throws
a syntax error as the logical switch is passed
as a list inside a list.
2. a problem where the database model
cannot store the value of the string
"unspecified-fault" in 16 character column width
for the port fault status and switch fault status.
3. a problem where the L2gateway agent and the plugin
do not handle empty port and switch fault status
which makes validation of the logical gateway fail
when an l2-gateway-connection is created.
Closes-Bug:1440301
Change-Id: Id4530b26407f2a6d57de7254476d77a36bb70a27
port_fault_status and switch_fault_status implementation.
reflect the same status in neutron db from ovsdb.
raises appropriate error message while creating l2gateway connection
if switch_fault_status and port_fault_status is not UP.
Change-Id: Icc77392afeb62bd2b0b0b816a63f8f02b442b0d8
Changing the log imports from
neutron.openstack.common import log to
oslo_log import log, due to change in latest neutron.
Change-Id: Ic7de94602feb088005f0b61e7d7963dde35a8ac0
This patch set implements RPC calls that are initiated by the
L2 gateway agent destined to the L2 gateway service plugin
Change-Id: Id60565dca791cf0b104bb8d85a9b3c4c7b4537d7
Author: Phani Pawan <ppawan@hp.com>
Co-Authored-By: Manjunath Patil <mpatil@hp.com>
The patch set introduces callback registration
to the ML2 plugin for PORT CREATE, PORT UPDATE
and PORT DELETE operations so that it can
accordingly instruct the L2 gateway agent
to configure the OVSDB server when these events
get trigerred.
Change-Id: I1ab8e95600f0cc079eebfcc05ab7e2c476de1bc2
This patchset enables to provide the migration script
'neutron-l2gw-db-manage' for create database tables for
networking_l2gw project.
Change-Id: I89eb370996c5ae416484df1135e0b7b3517a8b1f
1. Handled for multiple devices and interfaces
2. handled for multiple segmentation id
3. segmentation id validation handled
4. handled for multi segmentation network
5. handled for connection create for multiple networks with same l2gateway
6. Fixed defect during l2gateway delete check for connection exists
7. update l2 gateway when invalid device name given
8. update l2 gateway for multiple devices
Change-Id: I283449c417b82322e85e37f5c23f06c5618a0ab7
The patch set moves the db models and helper methods
specific to OVSDB from
networking_l2gw/services/l2gateway/ovsdb
to networking_l2gw/db/l2gateway/ovsdb.
Change-Id: I5aad9e2910685cc1b9a9b1cbbf4a112bd9d5f140
This change is for adding initial alembic migration file
for networking_l2gw project and also db models down_revision
modified based on the initial migiration file
Change-Id: Iebc4649b8b26a3c274f7649c4949758b8c889c72
This is initial db related files required
for implementing l2gateway RESTful API
Implements: blueprint l2-gateway-api
Change-Id: Ie6bd6b506bd704e0a86273ec7240b7eebb3b18b1
These MYSQL DB models are introduced in order to
maintain a replica of OVSDB tables in Neutron DB
Change-Id: I013dc63925c77eec7c4499a2fb8d1484ca261f35
Author: Manjunath Patil <mpatil@hp.com>
Co-Authored-By: Phani Pawan <ppawan@hp.com>
vikas