Jump to: navigation, search

Difference between revisions of "Blueprint-add-basic-heat-tests"

(Created page with "* '''Launchpad Entry''': TempestSpec:add-basic-heat-tests * '''Created''': 18 May 2013 * '''Contributors''': == Summary == Heat is an orchestration Openstack components help...")
 
Line 6: Line 6:
  
 
Heat is an orchestration Openstack components help you to mange complex service deployment and horizontal scaling.
 
Heat is an orchestration Openstack components help you to mange complex service deployment and horizontal scaling.
Unlike the other OpenStack competent it has relative simple OpenStack API, but relative verbose language(HOT).
+
Unlike the other OpenStack competent it has relative simple OpenStack API, but relative verbose language([https://wiki.openstack.org/wiki/Heat/DSL HOT]).
Heat also provides minimal Amazon CouldFormation compatibility.
+
Heat also provides basic Amazon Could Formation compatibility.
  
 
== User stories ==
 
== User stories ==
  
 
We have multi-tier enterprise web application "stack" and our internal resource are usually not enough to provide low latency services in the rush hours.
 
We have multi-tier enterprise web application "stack" and our internal resource are usually not enough to provide low latency services in the rush hours.
We would like to ensure our "scaling out to the cloud" solution is working in reliable way, and we are considering moving our complete application stack
+
We would like to ensure our "scaling out to the cloud" solution is working in a reliable way and we are considering moving our complete application stack
 
"into the cloud".
 
"into the cloud".
  
Line 21: Line 21:
 
== Design ==
 
== Design ==
  
 +
Gate time tests:
 +
* Full API coverage including the negative tests.
 +
* Basic API access CLI coverage as with the other CLI client
 +
* scenario: Build a stack with networking elements.
  
 
+
Most likely periodic tests:
 
+
* Periodically built heat cloudwatch compatible images, they should be published for example on the static.openstack.org.
== Implementation ==
+
  The heat project contains special reporting components which must be part of the could image.
 
+
  [https://wiki.openstack.org/wiki/Heat/ApplicationDeployment Application deployment]
 
+
  [https://github.com/openstack/heat-cfntools heat-cfntools]
 
+
  [https://github.com/openstack/heat-templates Heat templates] Includes oz image build templates
 +
  [https://github.com/stackforge/tripleo-image-elements/tree/master/elements/heat-cfntools diskimage-builder elements]
 +
*  CloudWatch / ceilometer aided HA and auto scaling tests.
  
 
=== Additional Notes ===
 
=== Additional Notes ===
  
 +
Heat has a horizon plugin called 'thermal': https://github.com/steveb/heat-horizon
  
 
== Unresolved issues ==
 
== Unresolved issues ==

Revision as of 14:32, 4 July 2013

  • Launchpad Entry: TempestSpec:add-basic-heat-tests
  • Created: 18 May 2013
  • Contributors:

Summary

Heat is an orchestration Openstack components help you to mange complex service deployment and horizontal scaling. Unlike the other OpenStack competent it has relative simple OpenStack API, but relative verbose language(HOT). Heat also provides basic Amazon Could Formation compatibility.

User stories

We have multi-tier enterprise web application "stack" and our internal resource are usually not enough to provide low latency services in the rush hours. We would like to ensure our "scaling out to the cloud" solution is working in a reliable way and we are considering moving our complete application stack "into the cloud".

Assumptions

Ensure complex application stacks successfully deploy-able into an OpenStack environment.

Design

Gate time tests:

  • Full API coverage including the negative tests.
  • Basic API access CLI coverage as with the other CLI client
  • scenario: Build a stack with networking elements.

Most likely periodic tests:

  • Periodically built heat cloudwatch compatible images, they should be published for example on the static.openstack.org.
 The heat project contains special reporting components which must be part of the could image. 
 Application deployment
 heat-cfntools
 Heat templates Includes oz image build templates
 diskimage-builder elements
  • CloudWatch / ceilometer aided HA and auto scaling tests.

Additional Notes

Heat has a horizon plugin called 'thermal': https://github.com/steveb/heat-horizon

Unresolved issues

  • What needs to be a periodic tests and what fits into the gate check/verify time.

BoF agenda and discussion