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
Remove unnecessary using self.properties.get for more
clear code. Using properties.get(prop, default) causes
next issues:
1. properties.get(prop) if prop not in properties_schema
will return None instead of expected KeyError.
2. properties.get(prop, default) returns "default" value
if current properties is not presented in properties_schema.
So using self.properties.get() makes sense only when we plan
to use this property with default option in another resource,
which has not it in property schema.
This patch replaces this methods in resources/openstack folder.
Change-Id: I523eb3feacb0cb7a16a928a92896ce56188e376f
Heat stack_resource has similar check for actions, but currently it does
not raise error if actions are different. OS::Heat::Stack resource is
similar on stack_resource so it has same issue, when resources require
some time to change state/action and it should not be so strict.
Change-Id: I20c2d3f8900b7393b1f551384805a35d5ef6497d
Closes-Bug: #1454589
The call to ignore_not_found() in the SwiftSignal resource was missing
an argument.
Change-Id: Id65af72ed30e76ab3620248807ef05c31e1e8565
Closes-Bug: 1452412
If we get repeat signals that cause no concrete actions
this can cause large quantities of senseless events that
suppress useful events.
Change-Id: I79374d27648319f241f36ab041784fab37823ddb
Closes-bug: #1445361
Adds `min_adjustment_step` property to ScalingPolicy
resource. It represents the minimum number of resources
that are added or removed when AutoScaling group scales
up or down. This can be used only when specifying value
`percent_change_in_capacity` for `adjustment_type` property.
Change-Id: Ia8976e52047ab47245566487ce1872a8890bcff2
Closes-Bug: #1447913
We can't call child_template() from a validate in ResourceGroup
as it accesses nested(). So move the validation to validate_nested_stack()
so we can control the test template used for validation.
Unfortunately coverage for this got removed during recent test rework
and it looks like the interface has got broken.
Co-Authored-by: Angus Salkeld <asalkeld@mirantis.com>
Change-Id: Ibea738a343847736b041cc49a2c486fa71e562d9
Closes-Bug: #1446861
generate_template and resource_schema methods of service.py
raises wrong type of exceptions after catching them.
Also resource validation failure should not raise stack
validation exception.
Change-Id: I44b8d37db7d2687cee2a7b675dd062b3af3ee167
Closes-Bug: #1447194
NUMBER in properties can be integer or float, some properties are
just integer type, correct those codes with correct type.
Change-Id: Id36203bb8e497559b811c825e2dc060f925d7a37
Clarify that latest HOT is required for path based get_attr
calls using 'outputs' and 'outputs_list'.
Change-Id: I44de426a61726d27616f6dd8a38e676fb2a6fbcc
Closes-Bug: #1444286
Currently we only create the deployment if the actions list includes
CREATE, but its valid to create e.g DELETE only deployments, which
curently won't work. So determine whether to create the deployment
on the resource_id instead of via the action, which resolves this problem.
Change-Id: Ia563f4130c31baa4dcee3be3786ea3c49b6bad98
Closes-Bug: #1444087
This improve doc notes about deprecated objects
and adds option 'version' to all objects with
support_status parameter.
blueprint deprecating-improvements
Change-Id: I82f9f4514142a3a66c872722b265fee365eb5de2
It is defined within the properties as rolling_updates.
This patch is to make it more obvious to users that UpdatePolicy
is not supported.
Change-Id: I8162d27036843d0b9282cd8f4aa4d2eb93afba19
Closes-bug: 1423426
With this change 'refs' attribute of the ResourceGroup resource will
support indexing.
Change-Id: I7715897091a55ed333e4b07bd1ad38bd4d8aa019
Closes-Bug: #1434586
All resources, which have handle_signal, check condition
if action in DELETE or SUSPEND state. Move this check to
Resource class.
Change-Id: Ifa9e97c19cc35c4b2aa40dbed37296d9d4a38d5b
This change removes the required bit for the actions field of the
configs property in the OS::Heat::SoftwareComponent resource. This
avoids confusion, as this field has a default value.
Change-Id: I1c5ee40a194b5670668dd7d60846e509d587ecc3
Closes-Bug: #1436002
When we moved parameters from the stack table to the template table
we did it in a "flexible" way, but this led to some difficult to
diagnose problems. So this patch totally removes "env" as an argument
to the Stack class to make absolutely sure that we are doing this
correctly. I came across these bugs when rebasing decouple-nested.
- env was not getting passed into instance group make_templates()
- template deepcopy was not working correctly (causing some problems
when deleting backup stacks)
Change-Id: I85cfb01c68ff5a44e2ff4f6e446870efb7205933
This change adds config options so that operators can choose the default
transports for server software_config_transport and deployment
signal_transport. With properly set config values, templates should
have no need for setting these options at all, making templates more
portable across clouds.
The defaults currently are the cfn transports but consideration could be
made in the future to switch to swift.
Downstream deployment tools (puppet etc) would have enough information
to set the best heat.conf values, with something like the following
logic:
- if there is an object-store endpoint, set for *TEMP_URL*
- if there is no cloudformation endpoint, set for *HEAT*
- else set for *CFN*
Change-Id: I5f3d41db35e380486051cee432a7190b3c51fa00
Related-Blueprint: software-config-swift-signal
This patch closes a bug related to the 'rolling_updates' property of a
Heat AutoScalingResourceGroup resource. Currently the 'rolling_updates'
property is a map will all keys having default values assigned. This
means the 'rolling_updates' property as a whole has a default value
ready to be used.
Closes-Bug: 1343873
Change-Id: Icb8dcf44ab16c0547fd1b8edcce650a6892900f2
Allow empty 'config' for software deployment resources.
The use case would be for custom agents where the config
is already baked into the image, so these agents would
still want to:
read input_values to feed into the baked-in config
signal heat that deployment is complete, including output values
Change-Id: I87807065bf5821bcff23810d7e58c34eaa991f19
Closes-Bug: #1407387
Move the resources which inherit from 'Resource'
to engine/resources, such as stack_resource,
stack_user and signal_responder, and move
non-resources to engine/, such as iso_8601.py module.
Change-Id: Ic26c34cc8d34ca03ce674dc8c6ac32c10885b75f
Implements: blueprint reorganize-resources-code-structure
Always update remote_stack even though properties didn't change,
and let the let the individual resources in it decide if they
need updating
Closes-Bug: #1428979
Change-Id: Id0898683b86e3a72e539f2432f521c7ee70afe26
Thomas Spatzier