make neutron-ns-metadata-proxy configurable

Introduced a new configuration parameter for DHCP and L3 agent
to be able to set the path of the metadata socket to be used
by neutron-ns-metadata-proxy when started inside the DHCP or L3
agent. Also moved the configuration parameter of the
neutron-ns-metadata-proxy to the CLI parameters.

fixes bug #1202628

Change-Id: I3b1aa72b4e06c00f7fed152f0ee03d52b6bbc279
remove binaries under bin

bp: remove-bin-directory

There are some binaries which are expected to run in branch, so
we have to keep them there now.

Change-Id: I5134d975cbd69f929a325ab80a6d19ce1f122656
Syslog support for neutron metadata proxy

When neutron metadata proxy reads the cli args
which are propagated from its parent processes
(l3-agent and dhcp-agent), if log-dir and log-file
are not defined in the context, it will also
double-check whether syslog is enabled and
its facility in the user-defined configuration
files (/etc/neutron).
As a result, the log behavior of each neutron
component becomes consistent.
File log is the default logging function. The syslog
is enabled when use_syslog is explicitly defined and
file log options are all disabled.

Fixes: bug #1184500
Change-Id: I7804fa8794071d21513e068d084607691215522f
Fix typos and code style check

In neutron/api/extensions.py, there are some typos, no needed blank
lines and docstrings can be improved (according to HACKING.rst).

Closes-Bug: #1213541

Change-Id: I01087d133e1b2a7e69f0bcc2ae359a3a2042b1dc
Add ext-gw-mode support to ML2

Closes-Bug: #1212772

ML2 doesn't support ext-gw-mode, resulting in L3 agents not
setting-up NAT rules in neutron routers (currently, l3 agents
will assume enable_snat=false if plugin doesn't provide this
parameter as described in bug 1212868)

This patchset adds the support of ext-gw-mode to ML2 plugin.

In order to support ext-gw-mode alembic migration (as well as
other potential migrations on plugin dbs), folsom_initial
migration script is fixed to include ML2 plugin. Otherwise
databases won't be set-up during migration script (but at
plugin startup by sqlalchemy), resulting in migration failures.

Change-Id: I95ec18e0a4f0e5b661f3a5d679c434f18f100fa6
Add missing ForeignKeyConstraint to Cisco providernet migration

Change-Id: Ieb6126fe80f71a5c44434861d65b6a1c97957eed
Closes-Bug: #1214497
Imported Translations from Transifex

Change-Id: I9112615ea4700ea15f85fdb3ef82812dac4df14b
Use subnet id instead of wrong built-in id()

In _validate_subnet(), built-in id() is used as param for exceptions,
this patch fixes it via using proper subnet id.

Closes-Bug: #1213930

Change-Id: I9a88f4dc7b771047f4061fb94ba65f0515afa745
Remove calls to policy.check and policy.enforce from plugin code

Completes blueprint make-authz-orthogonal

This patch removes a few explicit policy checks recently added to
the plumgrid and cisco plugins.
They are not necessary as the same checks are already performed
by the policy engine.

Change-Id: Ie99f5fa6ad4a9568b050827bc479a62dd40e18ac
Adding VPC support to the Cisco plugin

Adding VPC(Virtual Port Channel) support to the Cisco plugin.

Change-Id: I898e4355d05f6f43593deb2d977dfc1e55fb2fc8
Implements: Blueprint cisco-plugin-vpc-support
Merge "remove binaries under bin"
Merge "Add ext-gw-mode support to ML2"
Fix auth_url in metadata_agent.ini

Closes-Bug: #1214921

The value of auth_url is incorrect, some operators may not change
that value and problem will occur. According to keystone, 35357 is
the port number which the public admin listens on, 5000 should be
used for neutron instead.

Change-Id: I0b35f25c1845d02f8b9b3cd8c759920d52003c0c
Merge "Add missing ForeignKeyConstraint to Cisco providernet migration"
Merge "make neutron-ns-metadata-proxy configurable"
Disallow non-admin to specify binding:profile

Change-Id: Iefa4b251f3b0a373fb9b2b7d576e14d58afece59
Fixes-Bug: #1214873
Merge "Use subnet id instead of wrong built-in id()"
Merge "Syslog support for neutron metadata proxy"
Merge "Fix typos and code style check"
Merge "Fix auth_url in metadata_agent.ini"