Fix auth issue in get_instance_host

_get_instance_host was attempting to use the
admin username and password with the user's
tenant, which leads to 401 auth errors from
Keystone when attempting to determine the
instance host from nova.

This patch reads the admin tenant from the same
place as the username and password and uses that
instead. It also removes the keystone call that
was used to determine the tenant_id from the name,
since that is no longer needed.

DocImpact grizzly

Change-Id: If7ab8df24f8a727b458a780af8909e4cc6e1d0eb
Fixes: bug 1202462
Wrap delete operations for subnet in a transaction

Fixes #5
Merge pull request #13 from tomoe/stable/grizzly-issue-5

Wrap delete operations for subnet in a transaction
Wrap delete operations for router in a transaction

Fixes: GH #8
Fixes: LP bug 1184518
Merge pull request #14 from tomoe/stable/grizzly-issue-8

Wrap delete operations for router in a transaction
Wrap a midonet port deletion under transaction

Fixes #6
Fixes: LP bug 1184497
Merge pull request #15 from tomoe/stable/grizzly-issue-6

Wrap a midonet port deletion under transaction
Update changelog

Update the version with bug fixes for the rc2 and rc3.

Signed-off-by: Ryu Ishimoto <ryu@midokura.com>
Add quantum-plugin-midonet-custom package.

Add a separate Debian package for midonet plugin that installs
midonet plugin code and config.

Signed-off-by: Ryu Ishimoto <ryu@midokura.com>
Clean up Cisco plugin config parameters

Change-Id: I3095f6aa0aa182592bd939ec59bac1820f15676f
Fixes: bug 1201537
Merge "Clean up Cisco plugin config parameters" into stable/grizzly
Merge "Fix auth issue in get_instance_host" into stable/grizzly
Prevent possible server list damage in BigSwitch plugin

The old failover logic for the BigSwitch plugin modified a
list of controllers as it tested them. If the code for one
thread unexpectedly raised an exception or died, the global
server list could lose a server permanently.
This patch addresses that by flagging servers as failed instead
so the global server list is never modified.

Fixes: bug #1200022

(cherry picked from commit 3732f022778a7c4a47c58029ae77e32a0a4a6ee9)

Conflicts:

	quantum/plugins/bigswitch/plugin.py

Change-Id: Id2dcb820ef9f62fd03e3215bff3345e56c78afe2
Check if dhcp port exist in adding router interface

Fix: #11
Signed-off-by: Rossella Sblendido <rossella@midokura.com>
Checking if not subnet_id in add router interface

Change-Id: I7711eff6e3a3ba80f53dbf4c02eef6543d7610ce
Signed-off-by: Rossella Sblendido <rossella@midokura.com>
Corrected Pep8 warnings

Change-Id: I0f89426c786dae83891687f9b3dd0b795dd1f896
Signed-off-by: Rossella Sblendido
Merge pull request #21 from midokura/rossella/issue11

Rossella/issue11
Clean up the veth and ns created by the dchp agent

Override disable() in DhcpDriverNoOp, since we are not using
any external process for handling the dhcp and the superclass
method checks if a process is active. If it's not active
the clean up is not triggered

Delete the namespace in the interface driver unplug()

Signed-off-by: Rossella Sblendido <rossella@midokura.com>

Change-Id: I51f199b9714375c1753d5c616e60857e07542fb4
Merge pull request #20 from midokura/rossella/issue18

Rossella/issue18
Fix DHCP agent to work with latest dnsmasq

The latest dnsmasq no longer accepts hostnames which begin with a number. This
affects Fedora 19 right now, and will mean Fedora 19 will not work with Neutron
DHCP. dnsmasq should work with hostnames beginning with a number (RFC 1123 says
this is valid), but until this is fixed, many users will be left unable to use
Fedora 19 with Neutron.

This patch adds a "host-" prefix to each hostname entry generated by the DHCP
agent. This fixes the issue in Neutron.

Fixes bug 1204125

Change-Id: I0e29ec033969c3fb958ed3a12b8962b73b0e3d94
(cherry picked from commit acebf769a41a9a55cdc6789bf4962ea64cf87773)