There is no good reason why these must be explicitly set
in local.conf by the poor guy or gal. We can be nice and
have them be automatically set by the devstack plugin.
Change-Id: Idf39758147e8f3ea8fe9beb4f580fff391bf8380
Related-bug: #1541244
Ensure that configure_neutron runs before we try to
manage l2gw service plugin and l2gw service-agent related
configuration files under /etc/neutron.
Change-Id: I77fbd99bfa4f86b64c1f88f00bb9e4d3b43a3d8c
Closes-Bug: 1541244
while retreving the information from port details which belongs to specific host,
we are checking whether ovs agent is running on that host or not. if not,
exception is raised saying ovs agent not found in the host.
Closes-Bug:1515877
Change-Id: I23fccd8751ce791e1c6fd6920a0510c943714126
Commit 87a79256c494c36f2d9597313f430b24c0110161 added neutron_lib
for shared constants. This patch moves us to make use of the
aforementioned library.
Change-Id: I9f8c04d710bff2323d8259634097ea1738c50cdf
ovsdb_identifier parameter is missing while calling
delete_logical_switch and insert_ucast_macs_remote
function when enable_manager flag is set to False.
Closes-Bug:1546132
Change-Id: I93869f240a9000c7e0298e7ce7a8ec343b6d0982
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
Coverage for networking_l2gw using tox -ecover is not working due to wrong project name
specified in .coverage file. So removed the ovsvapp reference from .coverage file
Change-Id: I09ad8250f01801d5244561419e4a19e09c1b3149
../networking_l2gw/services/l2gateway/common/l2gw_validators.py:101:
DeprecationWarning: Using function/method 'instance.ugettext()' is
deprecated: Builtin _ translation function is deprecated in OpenStack;
use the function from _i18n module for your project.
msg = _("Segmentation id must be a valid integer")
TrivialFix
Change-Id: Id713e48c48b1815795112baa4a9a862ccca62b08
After creating a gateway and connection, then trying to delete the
connection, we hit the problem at the last call to
delete_ucast_macs_remote in delete_vif_from_gateway. The call requires
4 parameters, but only 3 are given.
Change-Id: I39337261d17b5031f17def0d1d2dfa43f1920bb3
Closes-bug: 1541155
Follow new infra setup for translations, see spec
http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_setup.html
for full details.
This basically renames
networking-l2gw/locale/networking-l2gw.pot to
networking_l2gw/locale/networking_l2gw.pot. For this we need to update
setup.cfg.
Update also domain name in _i18n.py.
Let's remove the po and pot files in the outdated paths.
The updated scripts work without them. So, we can just
delete the files and once the infra script runs,
an updated pot file together with translations
will be imported automatically.
Change-Id: I5e2db2ff767c25db9bb62aac8b826ba557393a5f
This patchset fixes the problem in HP L2GW CI due to
parallel execution of api test cases.
Patchset also ensures that all the tests run in sequential order.
Change-Id: I2d9313132393c0ad55acdf84d15c8d7ae9188833
Closes-bug: 1517758
This reverts commit 4f5b96e84c.
The commit edited .testr.conf which caused unit tests to be skipped
altogehter, and that is obviously not the right thing to do.
Conflicts:
tox.ini
Change-Id: I404e725f33e20f75c33bb794f326e46176d54f10
OpenStack projects are no longer being tested under Python 2.6, so
remove the trove classifier implying that this project supports 2.6.
Change-Id: I708b86e375f3b5b6bfefb956ae785181f6f8164a
To start translation, we need to initially import the translation
file - and place it at the proper place so that the usual CI
scripts can handle it. The proper place is for all python
projects $PROJECT/locale/$PROJECT.pot - see setup.cfg.
Further imports will be done by the OpenStack Proposal bot.
Change-Id: Ieb77ef2a336f89ce006964bf0cc08677489bff10
The patch set provides a framework to support
service drivers so that the south bound implementation
need not be tied to only the L2gw agent communicating
over the RabbitMQ message bus. This will help to support
other types of south bound implementations like OpenDaylight.
Change-Id: I403c7c0f110d4ad95d803640508b78c1539d181f
Closes-Bug: 1478812
Author: Maruti <maruti.kamat@hp.com>
Co-Authored-By: Manjunath Patil <mpatil@hp.com>
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
The patch set fixes the problem in the l2gw devstack scripts
where the l2gw_plugin.ini file neither gets copied to /etc/neutron,
nor is supplied while starting the neutron server.
Change-Id: If519e1a5394954d14673302aa8792f27017f60fa
Closes-Bug: 1511614
Armando Migliaccio