Updated openstack/openstack
Project: openstack/neutron  60b43cedbe9f5aa031d4f2452398a7cc81d07cac
null
Add X-Tenant-ID to metadata request

Previously, one could update a port's device_id to be that of
another tenant's instance_id and then be able to retrieve that
instance's metadata. In order to prevent this X-Tenant-ID is now
passed in the metadata request to nova and nova then checks that
X-Tenant-ID also matches the tenant_id for the instance against it's
database to ensure it's not being spoofed.

DocImpact - When upgrading OpenStack nova and neturon, neutron
            should be updated first (and neutron-metadata-agent
            restarted before nova is upgraded) in order to minimize
            downtime. This is because there is also a patch to nova
            which has checks X-Tenant-ID against it's database
            therefore neutron-metadata-agent needs to pass that
            before nova is upgraded for metadata to work.

Change-Id: I2b8fa2f561a7f2914608e68133abf15efa95015a
Closes-Bug: #1235450
Updated openstack/openstack
Project: openstack-dev/devstack  732e3d489ef4cdd3fba1b095201468f59fd1f0d0
null
Workaround Cinder "wishlist" bug 1255593 for multi-backend volume_clear

Cinder currently only applies the volume_clear setting from the DEFAULT
section of cinder.conf if you're using a single backend.

The Cinder team has determined this is a 'wishlist' item to propagate
volume_clear to each backend, but it does impact usability and
performance.

To improve the performance of running Tempest with multi-backends in the
gate, workaround the bug in devstack.

Related-Bug: #1255593

Change-Id: Ia0ff5422f53eeda9a3ac4336eefec3b9bdea6da2