Fix MeteringLabel model to not clear router's tenant id on deletion

foreign_keys parameter of orm.relationship should point to local columns.
Currently for MeteringLabel it points to Router.tenant_id column which causes
routers tenant_id clearing on label deletion.

Closes-Bug: #1249188
(cherry picked from commit d1220a3c22fccc1d86eaafeebe7ef9c074d4fcb9)
Change-Id: Iccc0daf4f6edd537fd7f9e4b2fc4be094543ca5d
Add fwaas_driver.ini to setup.cfg

Change-Id: Ie8157c0df343fb1009e7bc5b3ed2f2d4b0d0afec
Closes-Bug: 1258585
(cherry picked from commit daf0d68f9fc1f878ae29061dc43c19fd3e4950ef)
Fix unable to add allow all IPv4/6 security group rule

Previously, if one tried to add a rule to allow all ingress ipv4 neutron
would respond that the rule was already part of the security group.
This happened as the filter for querying existing rules uses a wildcard for
remote_group_id thus returning a false match. This patch addresses
this issue.

Change-Id: I0320013a3869d25fb424995354721929465d2848
Closes-bug: #1252806
(cherry picked from commit 9335ffd7c3eaad0d66d7d19e7760ae12476a5ea2)
Fix argument mismatch failure for neutron-check-nvp-config

Use sys.argv directly.

Fix bug #1243888

Change-Id: I9cb6ca841d004baf72dd68e44be673c361c2ed05
(cherry picked from commit e3e4a3fa2dac7a03169d095267ec492653524325)
Bump stable/havana next version to 2013.2.2

Change-Id: I3a7170180717bd62fce4cbc2c3a9107187f89fb1
NVP: propagate net-gw update to backend

When a network gateway's name is updated, propagate the
update to the backend.

Closes-Bug: #1261334
Change-Id: Icaae84e7f5373946e8c82e0e519528409925dd9d
Merge "Fix unable to add allow all IPv4/6 security group rule" into stable/havana
Merge "NVP: propagate net-gw update to backend" into stable/havana
Merge "Add fwaas_driver.ini to setup.cfg" into stable/havana
Reduce the severity of dhcp related log traces

Due to timing issues, when the agent synchronizes
with the server wrt the representation of server's
and agent's networks, networks may have already
been deleted from the db. In such circumstances,
it is more appropriate to emit warnings rather than
full-blown exceptions as the agent handles these
circumstances just fine.

Close-bug: 1251874

(cherry picked from commit f1b9ac5a542a3125d757094fccda80c80c6dd420)

Conflicts:

        neutron/agent/dhcp_agent.py

Change-Id: I4b118b6087c7f42226f0d4265d2176c028d99f22
Catch PortNotFound exception during get_dhcp_port

Close-bug: 1252437

Change-Id: I3a7954b869b4f5b909c806f8e47180e1ba6ba374
(cherry picked from commit cbe91fda7b416717a23cf7b29adf8201a8c14822)
Change default eswitchd port to avoid conflict

Previous default for eswitch/daemon_endpoint would set a TCP port (5001)
which is in the range of the well known ports.
Change to unreserved port (60001) will avoid that conflict.

Change-Id: I711c4659f497e44a6041ec9958835c1f2f4174a7
Closes-Bug: #1245885
(cherry picked from commit cd542a7f1f2ea21d3694e70b8e6a6db0efbd3a01)
Fix check_nvp_config erroneous complaint

Add the missing ingredient to the boolean test. This is
not a straight cherry-pick from a trunk fix, as the
utility tool has been renamed in Icehouse.

Closes-bug: #1265353

Change-Id: I9eb8fc1f85b16fbae83930fa9723db1fd25eeb5d
Merge "Catch PortNotFound exception during get_dhcp_port" into stable/havana
Send DHCP notifications regardless of agent status

The Neutron service, when under load, may not be able to process
agent heartbeats in a timely fashion.  This can result in
agents being erroneously considered inactive.  Previously, DHCP
notifications for which active agents could not be found were
silently dropped.  This change ensures that notifications for
a given network are sent to agents even if those agents do not
appear to be active.

Additionally, if no enabled dhcp agents can be found for a given
network, an error will be logged.  Raising an exception might be
preferable, but has such a large testing impact that it will be
submitted as a separate patch if deemed necessary.

Closes-bug: #1192381
(cherry picked from commit 522f9f94681de5903422cfde11b93f5c0e71e532)

Change-Id: Id3e639d9cf3d16708fd66a4baebd3fbeeed3dde8
NVP plugin:fix connectivity to fip from internal nw

The current set of NAT rules configured in the NVP logical router
prevents instances on an internal network from establishing TCP
connections with a floating IP associate with an internal port
on the same Neutron network.

This patch add a SNAT rule to ensure connections coming from the
internal network always appear to the port associate with the
floating IP as coming from the external network.

Change-Id: I12da12ee136c61fddb04f2b216382b51d751a02c
Closes-Bug: 1221419
(cherry picked from commit ed2e32b03123ae8e7555b997152c1d8d941494f2)
Add binding:host_id when creating port for probe

When probe is created it needs to have correct bindings otherwise port
is marked as dead.

Change-Id: If542b715756ccfed548ec89a97742fda2ad9b454
Partial-Bug: #1262785
Merge "Fix MeteringLabel model to not clear router's tenant id on deletion" into stable/havana
Merge "Send DHCP notifications regardless of agent status" into stable/havana
Avoid loading policy when processing rpc requests

When Neutron server is restarted in the environment where multiple agents
are sending rpc requests to Neutron, it causes loading of policy.json
before API extensions are loaded. That causes different policy check
failures later on.
This patch avoids loading policy when creating a Context in rpc layer.

Change-Id: I66212baa937ec1457e0d284b5445de5243a8931f
Partial-Bug: 1254555