ovsdb-client monitor attempts to connect to ovs via the
ovsdb_connection if it is set. Since it is set by default, we need
to ensure that OVS is listening on the socket before calling
ovsdb-client monitor.
Closes-Bug: #1669893
Depends-On: Ibde5417d005265d27e939ca29788c21f73b38980
Change-Id: Ia34b9d599b522dd12ef088100c2b68a75a78d797
Nova Ocata and Newton have protection against bridge
creation races in os-vif[1] so we no longer need
to special-case this port type in the Linux Bridge
loop going forward in Pike.
1. Ib0266086e0caffecf3f9f2a8291369cfa155f386
Related-Bug: #1617447
Change-Id: I2a23d0cbc4c4d0db6e9f48d91ca03b5007f91a84
Sadly, Nate is no longer with the team. Also Doug left us a while ago.
However we may like to blame others for all faults, it's time to free
those two from responsibility for the code.
Also, new infra liaisons were added.
Change-Id: Ief906ef64922acb4d3e7370c3d1e3ed75fe92a04
In an effort to simplify the codebase, this eliminates
all of the custom code in the ML2 delete_network
method and leverages registry callbacks for network
events.
The only purpose of the remaining inheritance of the
method is to leave the transaction guard on.
Partial-Bug: #1666424
Change-Id: Ib7d1c2081654dda82b5e015c71d20f378f3308f7
With pbr 2.0 and Sphinx 1.5, the setting for treat sphinx warnings as
errors is setting warning-is-error in build_sphinx section. Migrate
the setting from the old warnerrors one.
Change-Id: Ic4f2dd097137e4fa12acbdbfa47ea078d1b6d105
Nova V2.1 API has been available since Kilo, and the API is CURRENT.
Neutron is using Nova API via novaclient and the used Nova API is
V2.1 on the gate as the default Nova endpoint. So this patch doesn't
change the used Nova API actually, but current novaclient skips checking
expected API version in a response from Nova API.
This patch will be helpful to avoid an issue when enabling this check
on novaclient side.
NOTE: Cinder is using Nova v2.1 API with the similar patch as
Iadd3363265be6c5a8ed46704a712da6c15e2b046
Change-Id: Ie3a10f7078f4213da77be522e3866f82b5e8683c
The conntrack clearing code was belligerenty killing connections
without a conntrack zone specifier when it couldn't get the zone
for a given device. This means it would kill all connections based
on an IP address match, which meant hitting innocent bystanders
in other tenant networks with overlapping IP addresses.
This bad fallback was being triggered every time because it was
using the wrong identifier for a port to look up the zone.
This patch fixes the port lookup and adjusts the fallback behavior
to never clear conntrack entries if we can't find the conntrack
zone for a port.
This triggered the bug below (in the cases I root-caused) by
killing a metadata connection right in the middle of retrieving
a key.
Closes-Bug: #1668958
Change-Id: Ia4ee9b3305e89c958ac927980d80119c53ea519b
nova_metadata_ip option name is a bit confusing as it accepts an ip but
also a dns name (which is required when https protocol is used).
This change deprecates nova_metadata_ip option in favor of
nova_metadata_host option and updates option help to highlight that we
can use an ip or a dns name.
DocImpact
Closes-Bug: #1585699
Change-Id: Ia6c2471c7b4f3e924941222133edbb90151757a5
This will help root cause the Cirros image complaining
about a lack of keys when they are visibly present in the
Nova API logs.
Related-Bug: #1668958
Change-Id: I606c56f73be147e7f3281dfc73b874e404c39675
Since pbr already landed and the old version of hacking seems not
work very well with pbr>=2, we should update it to match global
requirement.
Partial-Bug: #1668848
Change-Id: Ie0a2cef329e2820ffe60c512a4870c0c3053574a
Switch to registry.receives decorator in
neutron.services.l3_router.service_providers.driver_controller.
Change-Id: I96b32365ef15c5e7c1f54cf58f1451e978f6bd91
Partial-Bug: #1668262
This change updates has_registry_receivers implementation in order to
call super.__new__ without args, kwargs parameters if super.__new__ is
object.__new__ (which forbids args, kwargs parameters). Without this fix
decorated class instantiation with positional or/and keyword arguments
fail.
Change-Id: I25880f6142f294fdde9db7f453d5e649c79029d0