Overview of the OpenStack Orchestration service platform tests

updated: 2017/02/03

Overview of the OpenStack Orchestration service platform tests

If you have installed the OpenStack Orchestration service (Heat) in your OpenStack environment, Fuel provides the automatic tests to verify its functionality.

The following table describes the details of the Heat tests.

Heat platform tests
Name Description Scenario
Test basic stack operations. The test verifies that the Heat service can create, update, and delete a stack, as well as shows details of the stack and its resources, events, and template.
  1. Create a stack.
  2. Wait for the stack status to change to CREATE_COMPLETE.
  3. Get details of the created stack by its name.
  4. Get the list of resources for the created stack.
  5. Get details of the stack resources.
  6. Get the list of events for the created stack.
  7. Get the details of the stack event.
  8. Update the stack.
  9. Wait for the stack to update.
  10. Get the stack template details.
  11. Get the list of resources for the updated stack.
  12. Delete the stack.
  13. Wait for the stack to delete.
Test the stack autoscaling. The test verifies that the Heat service can scale the stack capacity up and down automatically according to the changes in the configuration. Image with cfntools package should be imported.
  1. Create a flavor.
  2. Create a keypair.
  3. Save the generated private key to a file on the controller node.
  4. Create a security group.
  5. Create a stack.
  6. Wait for the stack status to change to ‘CREATE_COMPLETE’.
  7. Create a floating IP.
  8. Assign the floating IP to the instance of the stack.
  9. Wait for the cloud_init procedure to complete on the instance.
  10. Load CPU of the instance to initiate the stack scaling up.
  11. Wait for the second instance to launch.
  12. Release CPU of the instance to initiate the stack scaling down.
  13. Wait for the second instance to be terminated.
  14. Delete the file with the private key on the controller node.
  15. Delete the stack.
  16. Wait for the stack to delete.
Test the stack rollback functionality. The test verifies that the Heat service can rollback the stack if its creation failed.
  1. Start stack creation with rollback enabled.
  2. Verify that the stack appears with status CREATE_IN_PROGRESS.
  3. Wait for the stack to be deleted as a result of the rollback after the expiration of the timeout defined in the WaitHandle resource of the stack.
  4. Verify that the instance of the stack has been deleted.
Test advanced stack operations. The test verifies that the Heat service can suspend and resume the stack.
  1. Create a stack.
  2. Wait until the stack status changes to CREATE_COMPLETE.
  3. Call the stack suspend action.
  4. Wait until the stack status changes to SUSPEND_COMPLETE.
  5. Call the stack resume action.
  6. Wait until the stack status changes to RESUME_COMPLETE.
  7. Call the stack check action.
  8. Wail until the stack status changes to CHECK_COMPLETE.
  9. Delete the stack.
  10. Wait for the stack to be deleted.
updated: 2017/02/03
Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.

found an error? report a bug questions?

Contents