Raise VolumeNotFound with correct volume_id

Make sure VolumeNotFound is raised with the correct volume_id
in the SolidFire driver. Some exceptions were wrongfully referring
to an undefined variable named uuid.

Fixes: bug #1182966
Change-Id: Ied101fc9778f51dfb74b39f466c2c13d6e775a40
Bump stable/grizzly next version to 2013.1.5

Change-Id: Idb7cf867801b3ea79b42c0376d5cb712a5f1e2cf
Merge "Raise VolumeNotFound with correct volume_id" into stable/grizzly
Handle GlanceMetadataNotFound Exceptions

Change number I859bb2550267c6a5142e85ec89f1c7ff885588ac
fixed a bug where we weren't copying the bootable properties
of a volume or snapshot on create from snap or volume.

This didn't however handle the case of non-bootable volumes/snaps.

The result is that when the db call to get the image metadata raises
a NotFound exception we don't handle it and crash, causing the create
operation to fail.

This adds a try/except block around the copy volume/snap
glance_metadata get calls and ignores the exception.

Change-Id: Ibad730e7886b082d34717cd01b4ba31941e7594a
Closes-Bug: 1246004
Clear correct device when deleting a ThinLVM snap

The LVM driver tries to wipe a device using dd when
a snapshot is deleted.  For ThinLVM, it is attempting
to wipe the /dev/mapper/cinder--volumes-<vol>-cow device,
which does not exist for ThinLVM.  This causes snapshot
deletion to fail for ThinLVM if volume clearing is on.

When using ThinLVM, only wipe the LV device rather than
attempting to wipe the -cow device.

This bug is only present in stable/grizzly (2013.1.4).
It does not exist in stable/havana or master due to these
changes:
f702fe7 Fix secure delete for thick LVM snapshots
de43923 Don't zero out thin provisioned LV's on delete

Closes-Bug: #1245529
Change-Id: I1d8dd618e51cc99b8947fbe0697a1c765c8251ba
Don't zero out thin provisioned LV's on delete

Thin provisioned LV's don't need secure delete to protect
from data leakage.  Also, zeroing these out kinda defeats
the purpose of using thing provisioning.

This patch add a check for the lvm type and if it's thin simply
returns from the lvm.clear_volume() method.

Conflicts:
	cinder/tests/test_volume.py
	cinder/volume/drivers/lvm.py

Change-Id: Ie6764209018152565295291efc6fbba553698ae6
Closes-Bug: #1240299
(cherry picked from commit de4392314f9b0def8fab65679ec5668aec98fbee)
Pin Sphinx to <1.2

1.2 was just released and has a bug that causes builds to fail with
the error:

  error: 'source_dir' must be a directory name (got `...doc/source`)

See: http://bugs.python.org/issue19570
and: https://bitbucket.org/birkenfeld/sphinx/pull-request/193/builddoc-shouldnt-fail-on-unicode-paths/diff

Change-Id: I0487b4eca8f2755b882689289e3cdf429729b1fb
Fix problem with setting SSL protocol in QPid

looks like we were setting the wrong param

This is patch Id138926f in Grizzly oslo-incubator and it was already
included as part of Id72417d5 for Havana.

Closes-Bug: 1158807
Change-Id: Ie751e5670f612d52eea11db72bab4620de243e89
Hiding postgresql password in connection string

Change-Id: Iafc820d6201acf5b563b62bd9f20a715901f1ab4
Closes-Bug: #1266804
Merge "Handle GlanceMetadataNotFound Exceptions" into stable/grizzly
Pin SQLAlchemy to 0.7.x

0.7.10 has been released and is compatible with 0.7.x. Instead
of pinning to 0.7.9, simply pin to 0.7.x to avoid SQLAlchemy 0.8

Change-Id: Iea57598698b4faf906e82a2974497221d07f4d16
Merge "Fix problem with setting SSL protocol in QPid" into stable/grizzly
Merge "Hiding postgresql password in connection string" into stable/grizzly
Ensure we don't access the net when building docs

(Note, this has not been sent upstream)
Use updated parallel install versions of epel package

Use sqlalchemy >= 0.6.3 WebOb >= 1.0 Routes >= 1.12.3 PasteDeploy >= 1.5.0
and depend on the parallel installable
versions of these packages to satisfy those requirements.

Delve into pkg_resources a little to get it to modify sys.path,
so that our parallel installed egg takes precedence over the
system default module versions.
(cherry picked from commit 7b25747ffc21d0771e864f57ab2088725c8851f0)

Conflicts:
	bin/cinder-manage
remove deprecated assert_unicode sqlalchemy attribute

Removing this enables use with sqlalchemy 0.8.0
The deprecation is described upstream at:
http://docs.sqlalchemy.org/en/latest/changelog/changelog_08.html#change-ad44af79c886d1bb283042deb64f9cbe

Change-Id: I305bfdbcd3c3669c41318ea34115624f729b3909
avoid code path causing qpid exchange leaks

Always assume amqp_rpc_single_reply_queue is True,
so that the problematic code path is ignored.
The issue is discussed at https://pad.lv/1178375