Updated openstack/openstack
Project: openstack/nova  1eb14b64ae5fbdbd863232ad704fc86282c197d6
null
Add Flavor object

This patch adds the Flavor object and associated tests. It looks
mostly like the corresponding DB object, but without a nullable
flavorid attribute (which isn't actually optional). It also
makes a loadable 'projects' field with the associated project IDs
in it to avoid another object/interface for this simple thing.

Related to blueprint compute-manager-objects

Change-Id: Ib50a4efe874d6f19f5fc1178eb253ec8487f3808
Updated openstack/openstack
Project: openstack/tempest  1a149280d6d3b3028476f4b98e5aff8c0e8b1497
null
VPNaas IKE policies tests

testcases (create, update, delete, show, and list) for IKE policies.
part of blueprint: vpnaas-api-test-cases
Change-Id: I82e39edadb8160c92f5a72fbdc7035c3a3efd18d
Updated openstack/openstack
Project: openstack/glance  53fca479eafc9ad1a94ecede0edf9fdb1b749831
null
Unittests added for glance/cmd/cache_manage.py

Related to blueprint glance-cmd+unittests

Unittests for all methods, that manage cache added:
* list_cached
* list_queued
* queue_image
* delete_cached_image
* delete_all_cached_images
* delete_queued_image
* delete_all_queued_images

Unittests for several internal methods added:
catch_error; env; create_options; parse_options; lookup_command

Change-Id: Id07bbecdc9877268a514e3a594699364dcc4618f
Updated openstack/openstack
Project: openstack/cinder  bd75f2e72c59d03cc7222ddb1c71b124c6f75898
null
LVM: Create thin pools of adequate size

Thin pools in LVM are quite different from volume groups or logical
volumes and their differences must be taken into account when providing
thin LVM support in Cinder.

When you create a thin pool, LVM actually creates 4 block devices.  You
can see this after thin pool creation with the following command:

    $ dmsetup ls

    volumes--1-volumes--1--pool       (253:4)
    volumes--1-volumes--1--pool-tpool (253:3)
    volumes--1-volumes--1--pool_tdata (253:2)
    volumes--1-volumes--1--pool_tmeta (253:1)

In the above command, a thin pool named 'volumes-1-pool' was created in
the 'volumes-1' volume group.  Despite this, the 'lvs' command will only
show one logical volume for the thin pool, which can be misleading if
you aren't aware of how thin pools are implemented.

When you create a thin pool, you specify on the command line a size for
the pool.  LVM will interpret this size as the amount of space requested
to store data blocks only.  In order to allow volume sharing and
snapshots, some amount of metadata must be reserved in addition to the
data request.  This amount is calculated by LVM internally and varies
depending on volume size and chunksize.  This is why one cannot simply
allocate 100% of a volume group to a thin pool - there must be some
remaining space for metadata or you will not be able to create volumes
and snapshots that are pool-backed.

This patch allocates 95% of a volume group's free space to the thin
pool.  By doing this, we allow LVM to successfully allocate a region for
metadata.  Additionally, any free space remaining will by dynamically
used by either data or metadata if capacity should become scarce.

The 95/5 split seems like a sane default.  This split can easily (and
probably should) be made user-configurable in the future if the user
expects an abnormal amount of volume sharing.

Change-Id: Id461445780c1574db316ede0c0194736e71640d0
Closes-Bug: #1245909