Fix typo in resource tracker audit message

Resolves bug 1092418.

Change-Id: Ia51f1ee78bc612743095759fef6067c93fbcd222
Fix addition of CPU features when running against legacy libvirt

When running against an libvirt < 0.9.10 which lacks support for the
'host-model' CPU type, we must fake it by copying the host CPU
model and features. Unfortunately the code was forgetting to
append the new features to the CPU object feature list

Bug: 1099527
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
(cherry picked from commit 82b55c97d10a55e6a825261397816f6a7ad00fd7)

Change-Id: Ib5e6a173f1ae7d421435af45bf327f5b36c94dd0
Call plug_vifs() for all instances in init_host

Remove the assumption that we are using the "flat" networking model
and there is a single bridge interface for all instances on a given
compute node.  Instead simply call plug_vifs() for each instance in
init_host.

Fixes bug 1083784

Change-Id: I4b367deb6851c06c80a4bdf0bd806cf5e867bb0a
(cherry picked from commit 77e38b7cfc2206ef4ac528d3c9faaa09adbf7f58)
Makes sure compute doesn't crash on failed resume.

If the call to the driver to resume an instance raises an exception,
then nova-compute fails to start properly. This can happen during
recovery, for example, where an instance has been deleted so the
backing files are gone but the database is restored to a state
where it exists.

This patch fixes the issue by catching the exception and setting
the instance to error.

Fixes bug 1100430

Change-Id: Ie31f39fcd43174c29bf7a5cb1b6fa29e4c723f97
(cherry picked from commit 3b4016184f83c71158d41db9a26e6043d9ae1506)
Add NFS to the libvirt volume driver list

Fixes bug 1087252

Change-Id: I01511d4ef7763cbe622b10ee340342eb692afcdd
(cherry picked from commit f6c394cce473f58da704bc1c5230c57ca80f299d)
Merge "Fix addition of CPU features when running against legacy libvirt" into stable/folsom
Merge "Fix typo in resource tracker audit message" into stable/folsom
Merge "Call plug_vifs() for all instances in init_host" into stable/folsom
Merge "Add NFS to the libvirt volume driver list" into stable/folsom
Ensure that Quantum uses configured fixed IP

Fixes bug 1094897

The fix ensures that the fixed IP address specified by the user
is correctly passed to Quantum. That is, when the Quantum port
is created it is created with the specified IP address.

Change-Id: I8191ac2497037e2592b0679962e4606cd24d7844
Merge "Makes sure compute doesn't crash on failed resume." into stable/folsom