Updated openstack/openstack
Project: openstack/nova  8430bff8be259f5b9f48e04ba53df00e4611f3c4
null
VMware ESX: Boot from volume must not relocate vol

ESX does not support relocate API. Moreover when working with ESX the boot
from volume logic need not perform relocation since the volume's datastore
is always visible to the ESX host.

The fix is to ignore relocation when working with ESX.

Change-Id: I227cf2ea5b6f681150ede0bf6257eb238f1452d2
Closes-bug: #1244918
Updated openstack/openstack
Project: openstack/horizon  41a9bba503f82776387d02a065f6bf3f7cc3705c
null
Hidden checkboxes in Availability Zones table

Even if no action column in table Availability Zones, there
still has checkboxes column.

Change-Id: I5d352cf0482308976e36b61bf0a591d9815621c9
Closes-Bug:#1292329
Updated openstack/openstack
Project: openstack/cinder  61a794038b78e4a3c79ec1174c5d12ae685647fd
null
get volumes with limit and filters does not work

The /volumes and /volumes/detail REST APIs support filtering. Currently,
all filtering is done after the volumes are retrieved from the database
in the API.get_all function in /cinder/volume/api.py. Therefore, the usage
combination of filters and limit will only work if all volumes matching
the filters are in the page of data being retrieved from the database.

For example, assume that all of the volumes with a name of "foo" would be
retrieved from the database starting at index 100 and that you query for
all volumes with a name of "foo" while specifying a limit of 50.  In this
case, the query would yield 0 results since the filter did not match any of
the first 50 entries retrieved from the database.

This patch removes all filtering from the volume API layer and moves it
into the DB layer.

Test cases were added to verify filtering at the DB level.

Change-Id: Ia084e1f4cf59ea39bf8a0a36686146a315168cbb
Closes-bug: 1287813