Notify creation or deletion of dhcp port for security group

fixes bug 1103840

Change-Id: I8031bc607a874871a8081575bce1526b3453aff6
Load quota resources dynamically

Fixes bug 1149287

Change-Id: Ie02c7091f326c39f92e6a906c19e937e50227658
Imported Translations from Transifex

Change-Id: Iadf0974ffdada18d175698d73bf69ab16e4682da
isolated network metadata does not work with nvp plugin

This patch removes the not self.conf.enable_metadata_network
check before adding METADATA_DEFAULT_IP to ip_cidrs. This result
of this is that the dhcp agent interface will have
169.254.169.254/16 on it even if the network is
enable_metadata_network=True which doesn't matter and happens anyway if one
sets enable_meta_network=False. This change only effects the nvp plugin
as this is the only one that uses the enable_metadata_network flag.

Change-Id: Ifb3b28daed9e3bfc61bb0d8a48c40d027d0e2a51
add ns-metadata-proxy rootwrap filters to dhcp.filters

bug 1150628

now that dhcp-agent also uses ns-metadata-proxy, we need to make sure
those rootwrap filters are installed in scenarios where dhcp-agent is
installed by l3-agent is not.

Change-Id: I141b2291aceb93d650258ff1df1ef0122ce8da90
Show default configuration Quotas

Fixes bug 1144076

The patch set shows the defualt quotas that exist in
the configuration file. This is if the DB_QUOTA_DRIVER
is not configured. In this case the user is required
to update the configuration file and restart the service.

Change-Id: I5517c0215e8cfa71453ee38c34d8249e74346fdf
Merge "Notify creation or deletion of dhcp port for security group"
Merge "Show default configuration Quotas"
Merge "isolated network metadata does not work with nvp plugin"
NVP plugin: configure metadata network only if overlapping IPs are enabled

Bug 1152144

This patch also add a warning emitted in the logs at startup if the
configuration is not correct.

Change-Id: Idbf10c64f068a71ef1ed9c29a6a0c4e736bb975d
Lock tables for update on allocation/deletion

Allocating, creating and deleting port might happen
in parallel and we need to make sure we don't
assign same IP to multiple different requests.

Added treatment for vlan tags and tunnel ID's

Fixes: bug #1110807

Change-Id: Idbb04d3ce6eacd308b05536f1942a35a0792199e
Create quantum client for each api request in metadata agent

Fixes bug 1148017

Change-Id: I6f9263f01d17dcc44a4deb42cdaa348164ac4819
Imported Translations from Transifex

Change-Id: I434136d9dab5344b72eec2e7e319b756c88bc80e
Enable handling the report_state RPC call in Brocade Plugin

Fixes: bug #1150294

Change-Id: I4f641af48140a108e7c707446cda52509d567c8d
Merge "add ns-metadata-proxy rootwrap filters to dhcp.filters"
Merge "Create quantum client for each api request in metadata agent"
Allow probe-create to specify device_owner.

The device owner of the probe port can be
specified by the --device-owner option.

There are two values for device-owner option,
network or compute.

The probe port will be created with the network
as the device owner by default.

Fixes: bug #1102726

Change-Id: I72d62e2fe7b8f7a5eb4411bc9052efa82fb4fdf5
Merge "Allow probe-create to specify device_owner."
Wrap quota controller with resource.Resource

Fixes bug 1116137

Currently the format of error message returned by quota extension was
different with quantum other resource. Other resource will return as
json(eg, '{"QuantumError": "error message"}'). But quota extension only
return messages without any format.
'quantum.api.v2.resource.Resource' provider error messages processing.
So wrap quota controller with it.

By the way, fix some small stuff:
* Use specific exception 'QuotaTenantNotFound' instead of generic exception.
* Correct error message.
* Use attribute mapping checking the request body.

Change-Id: I71261198aa79e9ed8e0ae672de32552abdbf45c1
Merge "Enable handling the report_state RPC call in Brocade Plugin"