Updated openstack/openstack
Project: openstack/horizon  015aff26307ca619abc569404f82c6338239e628
null
Heat Stack update view/form

2 Part view for updating Heat Templates. The first page allows you to
select a new template for your stack. The second allows you to set new
template parameters for your stack. Like the launch stack workflow, this
is not a horizon workflow, but two separate forms.

Implements: blueprint heat-stack-update

Change-Id: I2854e9e4bb578be5187ef962808b93f11ac6b1f1
Updated openstack/openstack
Project: openstack/tempest  51aa0920460eda6cffc378076d56b9bd150d56b1
null
Stop running CONF getattr during import

This commit fixes 2 cases where a getattr was being run during test
file import which causes errors to be printed if a config file isn't
present.

Change-Id: I44a7750860c0a024997db5dd9ff3fa5b7332993a
Updated openstack/openstack
Project: openstack/cinder  41b244def5cfd1fe15fb1a4a6e345ce27e5b79cd
null
Add user defined extra capabilities

Provide a mechanism that will allow sys admins who are managing cinder
installations with multiple backends to assign key/value pairs to
backends. The key/value pairs can be used by the capabilities scheduler
to select between backends when requests specify volume types.

For example a sysadmin could specify the key 'service_level' with the
values 'high', 'medium' and 'low' for different backends. The sys admin
specifies the 'service_level' for each backend in cinder.conf as a json
string, for example:

extra_capabilities='{"service_level"="high"}'

or

extra_capabilities='{"service_level"="medium"}'

DocImpact
Implements: blueprint admin-defined-capabilities
Change-Id: I1ee9dcb22b3f097c3f3b2a70b0cb672930407cc9