This has been deprecated for years and is incompatible with deploying
multiple heat-engine processes. Let's at least not turn it on by default.
Change-Id: Iabddbd65be9000a30a5714b26658ea6acea0e103
This change relocates the extraroute resource from the contrib area into
the main resource tree, marking it as unsupported.
Change-Id: I6a51c9bdfb39d61adac48e5bcdf76f04a94e70a1
Heat could not create samples with Ceilometer, because ceilometer client has
change some key words in CREATION_ATTRIBUTES which is using by create sample.
Change-Id: I8e8dc80ae1b666ae74e2b2c2b757e7f468c25de2
Closes-Bug: #1455421
When a resource that has a support status different than SUPPORTED is
registered, the heat engine prints the message associated with its
SupportStatus object as a warning. This change avoids an engine crash
that occurs when a resource's SupportStatus does not define a message.
Change-Id: Id86bf93baade5b4fb0a71a80275b20d70710f2f4
If hooks of resource breakpoint are invalid, should
raise error message to user, and then user will know
what happen and why no pause on updation/creation.
Change-Id: I53822ed96fafdd373d20c45cacb5e33ba0306292
Closes-Bug: #1452636
Rename the StructuredDeployments resource to StructuredDeploymentGroup
to avoid awkward situations when talking about the plural form of the
StructuredDeployment resource. This has been agreed at the Vancouver
summit.
The existing 'StructuredDeployments' resource is kept for backwards
compatibility, but with a deprecated status and corresponding
deprecation message.
Closes-Bug: #1458008
Change-Id: I5d274acf17f222c493d10ded50f87e05a075b424
Rename the SoftwareDeployments resource to SoftwareDeploymentGroup to
avoid awkward situations when talking about the plural form of the
SoftwareDeployment resource. This has been agreed at the Vancouver
summit.
The existing 'SoftwareDeployments' resource is kept for backwards
compatibility, but with a deprecated status and corresponding
deprecation message.
Change-Id: Iae38b4afcb924ba626eccadfd68712e708be2bff
Partial-Bug: #1458008
from handle_delete to check_delete_complete, pass initial number of
Swift objects in the container instead (or None)
Change-Id: Idad1c4bee325f5483a598cd596fe04f4d0bb8cea
Partial-Bug: #1393268
The heat gate is broken due to other libraries pinning
on pbr<1.0
Stevedore extension loading currently has verify_requirements=True.
This change removes this to use the default of False. Loading extensions
is likely the wrong place to be enforcing requirements versions of
libraries that heat depends on, so lets not do it.
This is likely to also improve heat robustness for deployments with
inconsistent dependencies, not just this current heat breakage.
Change-Id: Ifee37e00412e824eead9ba1435ea5a328ff3df58
Closes-Bug: #1458399
When executing stack snapshot heat do not release stack lock
some undefined amount of time because it needs to prepare
some data for stack snapshot. It leads to situation when stack
snapshot is complete(from user perspective) but nobody can do any
operations with stack. So the fix executes snapshot saving to DB
right before stack becomes complete.
Change-Id: Id011142498fee49fee9ec1437fc0816b25780e48
Closes-bug: #1456672
If unencrypted data exists in the database, there will be no
'encrypted_param_names' key in the environment. Check for this key
before referencing it.
Change-Id: Ie8c593818a64d150e815487e1449a52173f1ab5d
Closes-Bug: #1456700
Zane Bitter