Updated openstack/openstack
Project: openstack/tempest  3e4cc71add90ee62ef00ece8193021a92c9ca140
null
Removes vim headers 3rd round

This is a follow up on:
  Change-Id: I8d09cb41ad633719857973a3ea228cd8dd3a9270

The vim headers in all the files are being removed. We've missed these
files because of delays in the patches.

Change-Id: Ie8097db6c60481749c88991864187ade64f39ecb
Closes-Bug: #1229324
Updated openstack/openstack
Project: openstack/ceilometer  39ead2a4c7153fb904ee47c414192d6dc451256a
null
Fix the py27 failure because of "ephemeral_key_uuid" error

Change-Id: Ic520a1657106a10a595240f84455eec1b79c2de0
Updated openstack/openstack
Project: openstack-dev/devstack  e0ed8ea038299952826b27a16753775472f108d8
null
Generate Tempest service list rather than hard-code it

The list of services that Tempest used to set its 'service_available'
config values was hard-coded. To be plugin-friendly have each
service (project) add its name to the TEMPEST_SERVICES variable
and use that for setting the 'service_avilable' values.

Change-Id: I208efd7fd0798b18ac2e6353ee70b773e84a2683
Updated openstack/openstack
Project: openstack/heat  e533603c05259deb38b56af06b27bae3dcd0a938
null
Fix AWS::StackId pseudo-parameter during stack update

Parameters, including pseudo-parameters, are resolved at the time that
resources are created, which is as soon as they are first accessed (in the
case of a stack update, this means during the validation of the new
template). As a result, by the time we set the AWS::StackId
pseudo-parameter in the process of doing an update it is already too late
for resources in the new stack to resolve them correctly. This was leading
to spurious differences being detected on stack update.

This patch fixes the issue by setting the pseudo-parameter before any
resources in the new stack are created.

Fixes bug 1260282

Change-Id: I908879827d6460ecbef30e9db98ac5597dc323cd