14259 Commits

Author SHA1 Message Date
Sławek Kapłoński
6dcdb15dce LinuxBridge agent's QoS driver bw limit for egress traffic
QoS service plugin provides for now bandwidth limit rules for egress traffic
only (from VM point of view). QoS extension driver for Linuxbridge agent now
configures limits in proper way on tap interface so limited is traffic which is
outgoing from VM.
Linuxbridge agent's QoS extension configures egress bandwidth limit and burst
value in exactly same way how openvswitch is doing it with tc.
Old methods in TcCommand class will stay untouched because they can be used
later to implement also ingress bandwidth limits in QoS.

Change-Id: Id2b0463f49df52744e5bc3979a4cfd0ff06f9248
Closes-bug: #1563720
2016-04-18 14:07:07 +00:00
Jenkins
e5b9ba1ea9 Merge "Revert "Add instrumentation devref, Part I"" 2016-04-17 07:49:27 +00:00
Jenkins
59d1673e86 Merge "Add support for building ovs from git sources on stacking" 2016-04-16 15:51:13 +00:00
Jenkins
d9e2a65d6f Merge "Clear DVR MAC on last agent deletion from host" 2016-04-15 23:45:09 +00:00
Jenkins
7a35d352da Merge "Add quota tests in unit tests." 2016-04-15 23:41:18 +00:00
Jenkins
70f8f1bab5 Merge "Reuse to_utf8() and jsonutils.dump_as_bytes()" 2016-04-15 23:40:59 +00:00
Armando Migliaccio
4e3a9c2b9c Be explicit about the APIs tested in the gate
Add an rc hook that declaratively define what extensions
are going to be tested in the gate.

This has two benefits: a) it provides an easy switch to
disable intermittent/experimental APIs; b) it provides a
safeguard against accidental configuration errors that
may trigger the execution of dormant tests.

The 'service_type' extension has been skipped in preparation
of [1].

[1] https://review.openstack.org/#/c/195329/

Change-Id: I03e2394011aa747899b50e6eb64faca68866b388
2016-04-15 13:03:55 -07:00
Jenkins
86b99e3a1c Merge "Move away from invoking api tests explicitly" 2016-04-15 20:00:25 +00:00
Jenkins
3d492f7ea5 Merge "Make gate-hook structure more readable and extensible" 2016-04-15 17:40:59 +00:00
Armando Migliaccio
965e1d18a7 Move away from invoking api tests explicitly
Since adoption of the Tempest plugin framework, this
extra plumbing is no longer necessary in tree.

Related-bug: 1555356

Depends-on: If5f7ea82c45494953452f728fabb7403d0b6e14e
Change-Id: I5377f33c5a7b29f97f00878e048d154378a4fe34
2016-04-15 17:13:59 +00:00
Jenkins
b97cf3850f Merge "Avoid referencing code from master branch" 2016-04-15 14:23:08 +00:00
OpenStack Proposal Bot
22ff1cfeb7 Updated from global requirements
Change-Id: If75e0f0541a3bdcebbf18c34b8491cffbe96ce5b
2016-04-15 01:55:23 +00:00
Jenkins
04aa284151 Merge "Added initial release check list" 2016-04-14 23:24:24 +00:00
Armando Migliaccio
55459e6e79 Make gate-hook structure more readable and extensible
Change-Id: I085b63c1d447d0c4e177a2d0e047d7621ebb9b2a
2016-04-14 13:19:38 -07:00
Jenkins
cc23e358b1 Merge "Use tempest plugin interface" 2016-04-14 18:10:14 +00:00
Carl Baldwin
f9c2b56518 Avoid referencing code from master branch
I clicked on this link while reading the plugin development section in
the effective neutron guide.  I wasn't sure it linked me to the right
thing because it currently links to a blank line.  I figured that it
was just a line off but I wasn't sure because the link is to the
master branch, which can change.

This patch changes master to the short commit id of the commit that
added this link in the first place.  This way, it'll always link to
what it originally linked to.  If contents move around on master by
adding code to the file or refactoring or whatever, it might still
cause some confusion but at least we'll know what it was originally
intended to point to without doubt.

Change-Id: I13a10e10a31b88cb6f030ca644ca20e0bf14012c
2016-04-14 09:45:08 -06:00
Daniel Mellado
c56918027a Use tempest plugin interface
Make use of the Tempest plugin interface instead of copying Neutron
files into Tempest. This will remove the burden to port Neutron
tests onto Tempest master recurrently.

It uses neutron/tests/tempest/ as new top folder for all Tempest
tests. It follows the model of Heat [1].

[1]: https://github.com/openstack/heat/tree/master/heat_integrationtests

Partially implements bp external-plugin-interface

Change-Id: Ia233aa162746845f6ae08a8157dcd242dcd58eab
2016-04-14 15:19:14 +02:00
Ha Van Tu
2b2e5b65c5 Change wrong word "propogated" to "propagated"
This patch fixes typo "propogated" to correct word "propagated" in
Neutron plugin and Neutron managers Mechanism driver.

Change-Id: I837e2ad9d93d4b84b20ede764283dbf793bb3870
2016-04-14 11:31:43 +07:00
Jenkins
81c61a9939 Merge "Add ALLOCATING state to routers" 2016-04-13 23:36:51 +00:00
Jenkins
2a305c5630 Merge "Always call ipam driver on subnet update" 2016-04-13 18:43:12 +00:00
Jenkins
b98f2134b2 Merge "Add an option for WSGI pool size" 2016-04-13 17:16:40 +00:00
Jakub Libosvar
7d5b1f8ddd Skip l2_ovs_agent functional tests
Let's skip the flaky tests until we find the root cause. The debugging
will happen with another patch that unblocks these tests so we still
have reproducer.

Change-Id: Icad4c1fb7a7ef9d6f5c34f48deb46ae286cb536b
Related-Bug: 1567668
2016-04-13 12:45:19 +00:00
Ihar Hrachyshka
f2f7a097eb Added initial release check list
The document is hopefully a good start and will eventually collect
enough information and tips for next release managers to run the
nervous process more smoothly.

Change-Id: Iaa14d818ae13e7cfa5ad061a2ae9d87a1f0fd331
2016-04-13 12:16:01 +02:00
Jenkins
6f17fdb3af Merge "Only load timestamp service plugin in timestamp tests" 2016-04-13 09:50:57 +00:00
Jenkins
b357b22898 Merge "Skip firewall blink test for ovs-fw" 2016-04-13 09:43:00 +00:00
Jenkins
d1a3767d26 Merge "Updated from global requirements" 2016-04-13 09:39:33 +00:00
Jenkins
99ceee29e5 Merge "Get rid of unnecessary _ha_routers_present check" 2016-04-13 09:13:53 +00:00
Jenkins
1574167b96 Merge "Revert "Add 169.254.169.254 when enable force_metadata"" 2016-04-13 08:32:02 +00:00
Jenkins
ce20b3c3b0 Merge "Cleanup override of compare_type from oslo_db" 2016-04-13 07:52:30 +00:00
Jakub Libosvar
c3f6bf5297 Skip firewall blink test for ovs-fw
We need to start using bundles first for ofctl operations.

Change-Id: Ia67c97bfa0fe03ca976be2330c9a66a85f988ceb
Related-Bug: 1569621
2016-04-13 07:52:10 +00:00
OpenStack Proposal Bot
8e983aad03 Updated from global requirements
Change-Id: I0524752926e5fd084ffee073def311bc2bb25667
2016-04-13 03:42:01 +00:00
Henry Gessau
61e76a34f3 Revert "Add 169.254.169.254 when enable force_metadata"
This reverts commit 45bec12cfc27578597cd197334979d0aee73a2cf.

Closes-bug: #1569507

Change-Id: Ie605f3b848a35b5db545c69038249155477d71e0
2016-04-13 00:49:18 +00:00
Assaf Muller
2397fd0d5c Fix broken Tempest conf options in API tests
Tempest commit ed6e586b9f8f0ada10af7711f297afa01b2b7754
changed configuration options defined in Tempest from
tenant to project. Currently we use Tempest from PyPI,
and since there hasn't yet been a Tempest release with
the change that breaks us, we're still safe, however the
next release will break us, so let's be ready for it.

Long term I think the correct thing to do would be to
define new options used exclusively in the Neutron tree.

Change-Id: I054b94a43d900e42872a9cb28d33a3ed45e14779
2016-04-12 16:47:21 -04:00
Jenkins
153f535d55 Merge "Refactor IPAM ip allocation method" 2016-04-12 20:37:05 +00:00
Jenkins
7fe5d1597a Merge "Add RECLONE support for ovs" 2016-04-12 14:14:49 +00:00
Mike Bayer
9d573387f1 Add an option for WSGI pool size
Neutron currently hardcodes the number of
greenlets used to process requests in a process to 1000.
As detailed in
http://lists.openstack.org/pipermail/openstack-dev/2015-December/082717.html

this can cause requests to wait within one process
for available database connection while other processes
remain available.

By adding a wsgi_default_pool_size option functionally
identical to that of Nova, we can lower the number of
greenlets per process to be more in line with a typical
max database connection pool size.

DocImpact: a previously unused configuration value
           wsgi_default_pool_size is now used to affect
           the number of greenlets used by the server. The
           default number of greenlets also changes from 1000
           to 100.
Change-Id: I94cd2f9262e0f330cf006b40bb3c0071086e5d71
2016-04-12 10:14:15 -04:00
Miguel Angel Ajo
2390064efa Add support for building ovs from git sources on stacking
This eases the deployment of a devstack machine with the latest
Open vSwitch bits, adding this to local.conf provides a fully
featured ovs-ct firewall setup:

  enable_plugin neutron git://git.openstack.org/openstack/neutron

  Q_BUILD_OVS_FROM_GIT=True

  [[post-config|/$Q_PLUGIN_CONF_FILE]]
  [securitygroup]
  firewall_driver = openvswitch

Change-Id: Ia7ad1658b95d7404384c7cae833008a57e3e5af1
2016-04-12 15:59:44 +02:00
Jenkins
eb70f85d3c Merge "Fix Windows IPDevice.device_has_ip racefulness" 2016-04-12 12:33:57 +00:00
Jenkins
c4448bd70c Merge "Remove Openflow Agent(OFAgent) mechanism driver" 2016-04-12 11:15:32 +00:00
Jenkins
64e9796306 Merge "Notify resource_versions from agents only when needed" 2016-04-12 11:15:10 +00:00
Jenkins
4440297a2f Merge "Add 169.254.169.254 when enable force_metadata" 2016-04-12 10:49:46 +00:00
Ann Kamyshnikova
ab67d954f0 Cleanup override of compare_type from oslo_db
As compare_type in oslo_db already contains proper comparison for
Variant override in Neutron is not needed anymore.

Change-Id: Ifae67816ebb16372e6faca8f442f3153b171c1d9
2016-04-12 12:07:23 +03:00
Jenkins
655c7cabb6 Merge "Deprecate 'ovs_use_veth' and 'veth_mtu' options" 2016-04-12 06:54:33 +00:00
Oleg Bondarev
e532ee3fcc Notify resource_versions from agents only when needed
resource_versions were included into agent state reports recently to
support rolling upgrades (commit 97a272a892fcf488949eeec4959156618caccae8)
The downside is that it brought additional processing when handling state
reports on server side: update of local resources versions cache and
more seriously rpc casts to all other servers to do the same.
All this led to a visible performance degradation at scale with hundreds
of agents constantly sending reports. Under load (rally test) agents
may start "blinking" which makes cluster very unstable.

In fact there is no need to send and update resource_versions in each state
report. I see two cases when it should be done:
 1) agent was restarted (after it was upgraded);
 2) agent revived - which means that server was not receiving or being able
    to process state reports for some time (agent_down_time). During that
    time agent might be upgraded and restarted.

So this patch makes agents include resource_versions info only on startup.
After agent revival server itself will update version_manager with
resource_versions taken from agent DB record - this is to avoid
version_manager being outdated.

Closes-Bug: #1567497
Change-Id: I47a9869801f4e8f8af2a656749166b6fb49bcd3b
2016-04-12 05:18:35 +00:00
fumihiko kakuma
2d09f50c98 Remove Openflow Agent(OFAgent) mechanism driver
The OFAgent driver and its agent are removed in the Newton cycle.
This adds to remove them in the release note.

Change-Id: I5dbcd38b0ccc156a6c1cbac4d7fa7f9d297ec466
Partial-Bug: #1521477
2016-04-12 14:10:34 +09:00
Jenkins
0c88a3085c Merge "milestone-review-dash detect current milestone" 2016-04-12 05:06:32 +00:00
Jenkins
5621e166c9 Merge "Fullstack connectivity: test interface scenario added." 2016-04-12 05:06:22 +00:00
Jenkins
06e400d78c Merge "RPC: remove unused parameter" 2016-04-12 05:06:11 +00:00
Jenkins
a7a2fa18b8 Merge "Define context.roles with base class" 2016-04-12 04:55:52 +00:00
Jenkins
5e5563b283 Merge "Use new DB context when checking if agent is online during rescheduling" 2016-04-12 04:55:33 +00:00