633f4c9f00
Since function.dep_attrs() returns logical resource names (rather than actual objects), we can just as easily use the StackDefinition to calculate it instead of the Stack and Resource objects. In the legacy path, we must ensure we use the StackDefinition from the *new* stack to determine which attributes to include in the NodeData, since that's what we're going to be using it for. In the convergence path the current stack definition already contains the new template. Also, update the *new* stack's definition with the NodeData obtained from completed resources (in addition to the existing stack's), so that that data may be used in calculating the dep_attrs for future resources. This is required when get_attr functions are nested in the template. Change-Id: I23efcc091eae53470f7f9cb3ca21e09f00f43808 Partially-Implements: blueprint stack-definition
Heat integration tests
These tests can be run as a tempest plugin against any heat-enabled OpenStack cloud, however defaults match running against a recent DevStack.
To run the tests against DevStack, do the following:
# Define DEST
export DEST=/opt/stack
# create test resources and write tempest config
$DEST/heat/heat_integrationtests/prepare_test_env.sh $DEST/heat/heat_integrationtests/prepare_test_network.sh
# run tempest selecting only these tests
cd $DEST/tempest tempest run --regex heat_integrationtests
If custom configuration is required, edit the [heat_plugin] section of
$DEST/tempest/etc/tempest.conf