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
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
This change adds a (currently unused) database function
stack_get_root_id to find the root stack ID for any stack.
Scheduler hints are moved to using Stack.root_stack_id() in this change.
Remaining uses of Stack.root_stack() will switch to using
Stack.root_stack_id() later in the series.
Change-Id: I9914b0df5af119edea6346db0d7c62124fbb1313
Partial-Bug: #1455589
Most validation errors are in fact the user's problem, but in the case of
an AssertionError that's a real problem with Heat. We should return 500
status codes and log the tracebacks, not wrap the in validation exceptions.
Change-Id: I71d91a5413d7f026b332014487583b7f2762b322
Circular references cause practically every bit of data that Heat uses to
remain in memory until the completion of an operation, and even then to
only be freed once the loop is detected by the garbage collector. By
breaking all of the loops using weak references, we can ensure that things
will get freed when they are no longer referenced without the need to wait
for garbage collection (which should also take a lot less time). This
change removes the loops from Resource and Function objects back to the
Stack.
Change-Id: Ibf80e95e69a2f27ed29754a2e0f1125e8eed0775
Closes-Bug: #1454873
There are some improvement of error message and tests
related of bug/1451713.
Change-Id: I78b609c8f1c8d04835f4a9dbadae51e2013fa753
Related-Bug: #1451713
Add a new constraint for CIDR format validation.
Implemented: blueprint enhance-property-constraints
Change-Id: Ica70147b713992c8523b92b12db0172a2966719c
This fix adds schema regeneration before props are validated
for TemplateResource during stack-update.
Change-Id: Ia79a25083489f48ed7332fbbd089a0090452cdc4
Closes-Bug: #1452983
Closes-Bug: #1453923
The event and notifications do not look the stack up in
the DB so we can rely on the in memory status.
Change-Id: Iceb9bf6fa86f7f5ada7d3a8672788f09a48b1f43
Partial-Bug: #1450314
This is the only thread that gets started without an explicit reference to
the stack. This prevents us from using a weakref in the resource, as it
will cause the Stack's reference count to hit 0 before the thread is run.
Now we explicitly pass a reference to the stack.
Change-Id: Ie51be7b54d97ef184e401e395a7e7e3a26ce003b
Related-Bug: #1454873
This will allow Resources to hold weak references to Stacks (so as to avoid
circular references) without causing the Stack object to be prematurely
deleted.
Change-Id: Ia76da7bc51042fb3598ef2a660d6fbf78137a37b
Related-Bug: #1454873
In order to eliminate circular references, we need to define the Stack as
the top of any reference hierarchy. This means we can't hold a reference to
a Resource directly without also holding a reference to its Stack.
Change-Id: I7430b109bbe1c5d6d64be9b8c778b394e9cff269
Related-Bug: #1454873
Use unittest2.assertWarnsRegex() for making sure we generate the
required warnings.
Use WarningsCapture to not print the other repeated warns to the
console.
Change-Id: I7223f8956394208eaf2eb8a1d651ba1425128bc9
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
Docs still tells that Heat is configured by default on
devstack. Need to fix it.
Change-Id: I186415f3422f3865aa3fbf4fe83ef13ea73c7eed
Closes-bug: #1450422
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
Thomas Spatzier