Adds --addn-hosts to the dnsmasq arg list

When using multi_host=True and update_dns_entries=True, dns records from
other compute hosts were not able to be resolved.  The --addn-host arg was
constructed but not appended to the cmd list.

Change-Id: I9cafb59256e92bdad0df3e9166e0afd079ae0c09
Fixes: bug #1170529
(cherry picked from commit 3922da72b2569976f25183c476cedcc17d32fa13)
Fix EC2 instance bdm response

Make the bdm response respect Amazon EC2 spec:
 * use ec2 volume id instead of uuid
 * use volume attach_status instead of status

References:
http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-ItemType-EbsInstanceBlockDeviceMappingResponseType.html

Resolves bug 1165973.

Change-Id: Ib68397b79f63e01e92ed4bebbc245ba5e0a3ad11
(cherry picked from commit f48a2e1a68cca1ef147279b2ddf713635f494bc0)
Do not test foreign keys with SQLite version < 3.7

Fixes bug 1158828

Even though SQLAlchemy is documented to support foreign keys (with
the pragma set) on SQLite >= 3.6.19, we're seeing consistent problems
with that support on RHEL 6.4 with SQLite 3.6.20.  It works fine on
Fedora and Ubuntu with SQLite 3.7.x.

To work around these problems, if we're using SQLite, test the SQLite
version inside the test that requires foreign key support,
and skip the test if it's < 3.7

Change-Id: I1c26f29371376b271a4e384ea7b5d2009651acc1
Remove insecure default for signing_dir option.

The sample api-paste.ini file included an insecure value for the
signing_dir option for the keystone authtoken middleware.  Comment out
the option so that we just rely on the default behavior by default.

Fix bug 1174608.

Change-Id: I6189788953d789c34456bbe150b8ed6ce6f68403
(cherry picked from commit 58d6879b1caaa750c39c8e452a0634c24ffef2ce)
Merge "Do not test foreign keys with SQLite version < 3.7" into stable/grizzly
Bump stable/grizzly next version to 2013.1.2

Change-Id: I130528ae946e8888d35c25e468b4ea6ac29db0cf
Merge "Fix EC2 instance bdm response" into stable/grizzly
Merge "Adds --addn-hosts to the dnsmasq arg list" into stable/grizzly
fix non reporting of failures with floating IP assignment

It seems that commit essex-1-1003-g9728ae5
inadvertently removed a 'raise', thus hiding
all processutils.ProcessExecutionError exceptions
apart from the one indicating "Interface not found".

Fixes bug: 1178658
Change-Id: I2bcf8c3a19ebebc81a38ce6bf7b54065d62834c0
(cherry picked from commit 175584f0afef308e1021bb4daf49cbf222a61a40)