Adds logic to the update_port_postcommit method of the
Big Switch ML2 driver to detect when afailure to update
the port via REST was caused by the backend being out-of-sync
with neutron.
This was accomplished by checking for the NXNETWORK message
which indicates that a port request referenced a network that
does not exist on the backend. This only occurs when they are
out-of-sync so the driver will then trigger a full topology sync.
The same logic exists in the port creation method shared with
the Big Switch plugin. However, the Big Switch ML2 driver does
not send port requests to the controller unless the port binding
host ID is set, which doesn't occur until a port update after
binding in the ML2 scenario. Therefore, the logic has to be repeated
in the ML2 driver port update operation.
Closes-Bug: #1331335
Change-Id: Id6488fbdea2c8c22a34e775977d94389c8da74f8
Some test cases instantiate RPC clients in setUp() before calling to
super(). After we port to oslo.messaging, we'll initialize RPC layer in
BaseTestCase, so we should make sure we call there before proceeding
with clients in subclasses.
blueprint oslo-messaging
Change-Id: I6fdcba0ba690c75d1a472b3ad050c21f5f53a1d0
BaseTestCase already cleans up all mocks via .stopall(), so there is no
need to do it in each test case.
Change-Id: I7165ea9682a3dce3a76e90e309b763c939729d84
In oslo.messaging port, we'll need to make sure no RPC clients or
servers or notifiers are created before RPC layer is initialized using
n_rpc.init(). This means that there should be no global objects that
create those objects on __init__.
There should also be no such class attributes because in that case
import will itself instantiate the object, probably before RPC layer is
ready.
blueprint oslo-messaging
Change-Id: Ia8a9fd39777c75e4253f5518c2de6be551cc365b
After oslo.messaging port is done, we'll need to initialize RPC layer
from all RPC agents. We'll put initialization into init() function, so
the first step for migration is to make agents use it.
The function is renamed to be explicit about the fact that we don't just
parse configuration by calling it, but also do other common
initializations, like setting RPC layer.
blueprint oslo-messaging
Change-Id: I71c62f270ac7a1ff1426a3f49a32133b65580e35
systemd is notified only when Neutron is started with multiple api
workers. This patch adds systemd.notify_once() call when starting
Neutron server with api_workers=0
Change-Id: I95581dc5dffde6168c68d9f04cf8bdfcdb773ba8
Closes-Bug: #1330532
Some plugins miss short symbolic name in setup.cfg, specifically Nuage
and Metaplugin.
Change-Id: I0198ae98654bbdddf8f2ba8dd3b80d0d447d6341
Closes-Bug: 1324487
Total connections was mapped to none of the counters
of haproxy. Active connections was mapped to active request
counter(qcur)) of haproxy which in low load situations
always remains zero.
Patch maps connections API counters to haproxy session counters
and fixes unit test accordingly.
Change-Id: I0ef4f76a75340232eb11a9b95453769ecd89d13a
Closes-Bug: #1319361
This class will be used to create proper self.target with appropriate
API version once we migrate to oslo.messaging.
blueprint oslo-messaging
Change-Id: I1fb5eb0aaac0d115fd84630e58b333e695ad4f5f
Recently (https://review.openstack.org/#/c/92453), the
functionality of dhcp_lease_duration was changed to support
infinite lease times.
However, this change failed to update the associated help text
with the option declaration. This patch simply updates the text
so that the new functionality can be understood by the user.
Change-Id: Id9dbe11599c55b447387df4a2d6639b7e8dba6ce
This change adds 'ip rule add', 'ip rule delete' and extends the IpRoute
class to support more ip commands
Change-Id: I8ba2f2d2ee896d9f4a378570be1524077d5b663c
Partially-Implements: blueprint neutron-ovs-dvr