Add a number of basic tests for Heat
Heat mostly seats on the APIs from the underlying components but a few high level functionalities should be tested to make sure the Heat's internals are doing fine:
1. successful deployment of a composite template
- also ensures status reporting is working
- also ensures cloudwatch is working
2. successful deletion of composite applications
3. cli tools basic functionalities
Blueprint information
- Status:
- Complete
- Approver:
- David Kranz
- Priority:
- High
- Drafter:
- Giulio Fidente
- Direction:
- Approved
- Assignee:
- Steve Baker
- Definition:
- Approved
- Series goal:
- Proposed for havana
- Implementation:
-
Implemented
- Milestone target:
-
havana-2
- Started by
- Giulio Fidente
- Completed by
- Giulio Fidente
Related branches
Related bugs
Sprints
Whiteboard
note that some good work has been done already by steve baker for this: https:/
Gerrit topic: https:/
Addressed by: https:/
A Heat client which does basic stack operations.
Addressed by: https:/
Initial heat orchestration tests.
Addressed by: https:/
Heat test to launch a heat-cfntools based instance.
Addressed by: https:/
Default to m1.little for heat test flavor
Addressed by: https:/
Avoid potential race condition in list_stacks assert.
Addressed by: https:/
Heat test ssh to the server.
Addressed by: https:/
Clear keypairs on teardown.
Addressed by: https:/
Use build_timeout & build_interval from heat config.
Addressed by: https:/
Always include credentials for heat stack create.
Addressed by: https:/
Implement update_stack client method.
Addressed by: https:/
Orchestration tests to use own credentials.
Addressed by: https:/
Create stack in class setup, rather than instance.
Addressed by: https:/
Autoscaling test.
Addressed by: https:/
Orchestration tests to use admin user, demo tenant.
Addressed by: https:/
Configure a heat security group for testing ssh.
