The /var/lib/heat-cfntools directory should be owned by the
heat-cfntools package for whichever distro it is included.
This avoids the problem of heat writing to directories owned
by cloud-init.
For the moment, the part handler will continue to write to
/var/lib/cloud/data to be removed at a later date.
Change-Id: I70b714c70ed146d4f6807850d6e7264c6a4624cd
Fixes: Bug #1105806
Use the new AWS::StackId pseudo parameter to refer to the stack for
cfn-hup etc, otherwise the stack lookup by name will fail - using
the AWS::StackId parameter means we'll refer to the stack via the
full ARN and the CFN API will be able to lookup the nested stack.
ref bug 1131666
Change-Id: Ieac738df766ae1f1039e743d465cd080b2090473
Re-resolve the template static data before creating the resource,
or we resolve the wrong value for the AWS::StackId pseudo parameter
which is updated after the parser.Stack gets stored.
ref bug 1131666
Change-Id: I68e87366d379356fd7f2685367300abe5594d6f6
We need to compare the runtime resolved resource snippet, since that
is what we get back from self.parsed_template. If we don't do this,
then we get a false positive when a Ref to a parameter which gets
updated (e.g AWS::StackId) is used in the resource properties.
ref bug 1131666
Change-Id: Ib488c43b9eca998a7a82b7571097f5bb69ef946c
We need to set the ARN provided via the AWS::StackId pseudo parameter
when the stack is stored, and also whenever a parser.Stack object is
created
ref bug 1131666
Change-Id: Ic8dc5ab2b25c85c51f2f685fe69bb2447a1e3615
Adds support for the AWS::StackId pseudo parameter, which will
allow us to to reference the stack ARN in the template, e.g so that
stacks can query their resource metadata via ARN not stack name,
which will solve the problem with nested resource being unable
to query their metadata.
ref bug 1131666
Change-Id: Ib7b1d380fa8766b6d0c968bd66270da8ce8245c4
We want to ensure the LB instance has fully launched before declaring
this resource created, otherwise the resource will not be functional
and attempts to modify config via metadata updates will fail
Change-Id: I879c21302f1c3a75a567d959fc2e398c7bfc3f65
The resources import is shadowed by a variable declaration in
validate template, which is confusing, so add a prefix to
differentiate the variable from the import
bug 1133434
Change-Id: Ia7c451c3a2588ddff114da9897b3bcf58e68cf0c
Reinstate the resources import removed by 06f4f85, without this
we fail to create any resources (GenericResource is created for
all resources due to no resource plugins being imported).
bug 1133434
Change-Id: I2b24d58dee83a426deee09f8a9a121f503534de4
The point of this change?
- You have another instances' ip in your metadata and if it
gets restarted you want cfn-hup to see the new ip.
How is it achieved?
- poll for the metadata so you can see these changes (cfn-hup)
- when ever an alarm action is run we make sure the metadata is refreshed.
bug #1131024
Change-Id: I0798c4da9689b126c3c98cafa63138ff2c484ea9
These can be used to ensure uniqueness of names when creating resources in
OpenStack services.
Change-Id: Ifb048fd8ec676b7fd6a15c5d4a39bfc98f0aeca9
Signed-off-by: Zane Bitter <zbitter@redhat.com>
This wrapper was there to allow oslo-config changes through the gate
while keystoneclient hadn't been updated.
Change-Id: I3d48673af58ae379e8e4d2c7fb4b4d81f3ed67dd
Don't crash if quantumclient is not available; just don't register the
resource types that require it.
Change-Id: I9dacc5397327ef7ec784f808227582ee9bd037df
Signed-off-by: Zane Bitter <zbitter@redhat.com>
Create User/AccessKey resources correctly in the LB nested template
so we can create a cfn-credentials file which will allow cfn-hup
to access the CFN API
fixes bug 1131663
Change-Id: I11b6640dbc5689de8f6103f4c1e841f42acbba54
The deletion calls _get_user() that calls FnGetRefId for each
resource. But since this is the delete most resources have been
deleted.
bug #1131534
Change-Id: I08ffd27d1d05214b1a8cf86744e7d4f91d7e1558
Do not tag development releases "dev", as it conflicts with our common
versioning code. Fixes bug 1131622.
Change-Id: I33ab25de1d1509c79d11f1919239798663b0cd22
The ec2token middleware currently dumps the whole request into the
request context when using AWS Auth, when all we really want are
the credentials (accesskey/signature)
fixes bug 1072917
Change-Id: I8fb0d4d7ada29d7d19c702a7da1251384166c246
run_tests.sh parses tox.ini, which has been changed removing the
pep8 version, so remove this test and specify the version in
test-requires. This allows the pep tests to run via run_tests.sh
again, a subsequent patch can reinstate the version check based
on the test-requires version
fixes bug 1131251
Change-Id: Ib24f588cbe81ded768376c138d9d89f5bb311185
