We override the method get_reference_id() for
scaling policy by calling the supper method, remove it.
Change-Id: Ia205ffebc4c9260445336127ad0bf0f38cf6508f
Adds property 'domain' for keystone role
resource:
1. the default value of the property is 'default'
2. the property is non-updatalbe
Change-Id: I829921dc35e2754eb6c6ccc293423c755806b0df
Closes-Bug: #1684558
It's been possible to set tags for the Mistral workflows, this
change adds a 'tags' property to the resource to make that possible
from Heat.
Change-Id: I231b3619eca86214ecbf33b05651c1b08cfddf96
Related-Bug: #1715389
We started to use keyston esession with mistal client plugin
since pike, but it seems the patch to translate keystoneauth
exceptions to mistal api exceptions did not get to
python-mistalclient==3.1.2.
Change-Id: I198cdbb8ee02623f2f5fb03a784135ce6f94a046
Closes-Bug: #1714679
Removing the uwsgi config files on stop breaks upgrades when using
uwsgi, so let's not do that. Keeping the file deletes in cleanup
makes sense and those calls remain.
Change-Id: I603754c3f5ed5d2f143cf789df96018ec99ad692
This isn't actually used and is a leftover from a thing we did
seven years ago that survives today through copy-pasta.
Change-Id: I7fed29322e00fa72b949692e01d821faa3f718ba
tl;dr : without this Pike and Queens have the same version causing
packaging issues.
https://docs.openstack.org/developer/pbr/#version
Because projects don't push a tag before milestone 1 (queens-1
here), downstream packages are still building packages by using the
version from Pike and it causes problems to distros because they
can't test the upgrades from Pike to Queens.
Bumping the semver will allow us to test packages upgrades.
Note: When your version is X.Y.Z, api-break will bump X, and feature
will bump Y. In this patch, we bump X because this is the way you
bump tags over releases.
Change-Id: I3036486835b4605be3e3891fc5be971fcd834199
Sem-Ver: api-break
Cinder returns the volume infos with key 'readonly',
not 'read_only', so parse live data with correct key
'readonly' for volume resource.
Change-Id: If19db3129f23a6cb9d19e6744c4ffc4522166426
Closes-Bug: #1712041
In I462ce7161497306483286b78416f9037ac80d6fa we changed to use the
frozen_defintion properties for delete. However, When deleting a
resource from backup stack, where the resource is in INIT_COMPLETE,
setting the _stored_properties_data(_properties_data) to {} when
loading the resource from the db, results in error, when resources
access properties in handle_delete.
Change-Id: If76372c7ef9aee258efb1bfbc724d8637bc6a32c
Closes-Bug: #1709682
eliminate [ec2authtoken] section, if auth_uri is specified in
'clients_keystone' section
Change-Id: Ie11139a5d9a176037f1c9f50a62ff6dbd1b20b8f
Closes-Bug: #1705664