openstack
/
heat
Code Issues Proposed changes
OpenStack Orchestration (Heat)
794 Commits 9 Branches 49 Tags 209 MiB
Python 99.3%
Shell 0.7%
Go to file
Jeff Peeler 8ba6c8ffe8 Split functional test into standalone and utility class 
This allows functional tests to be written for each individual template.
See the test_Wordpress_Single_Instance for an example, but the basic
form to follow is:

import util

def test_template():
    func_utils = util.FuncUtils()

    func_utils.create_stack(template, 'F17')
    func_utils.check_cfntools()
    func_utils.wait_for_provisioning()
    func_utils.check_user_data(template)

    ssh = func_utils.get_ssh_client()

    # test stuff here

    func_utils.cleanup()

Functional test changes:
Changed jeos creation to use new tool.
Added distribution to heat stack creation.
Improved IP parsing from glance.
Improve SSH connection exception handling.
Changed cfntools SHA check to match installed copy instead of locally.
Fixed stack parsing to check correct file and handle user-data injection.

Clean up run_tests a little to make it clear default execution is on host.
Add a short option for unit test running only (may be important due to not
wanting to run functional tests locally).

Also added paramiko to test-requires.

Change-Id: Ib2ae1be32801cb0ee3d1937c4f82ab9f574b4591
Signed-off-by: Jeff Peeler <jpeeler@redhat.com>
 		2012-08-23 13:31:42 -04:00
bin heat cli : Workaround inconsistent boto return type 2012-08-16 13:02:09 +01:00
contrib Add unit test framework nose and associated helper scripts 2012-04-13 17:10:30 -04:00
docs Update Getting started to match change to heat-jeos 2012-08-14 09:07:44 -07:00
etc heat API : move aws common files from api/v1 to api/aws 2012-08-21 11:54:18 +01:00
heat Split functional test into standalone and utility class 2012-08-23 13:31:42 -04:00
templates heat template : Align two Openshift template varieties 2012-08-16 19:06:06 +01:00
tools Split functional test into standalone and utility class 2012-08-23 13:31:42 -04:00
.gitignore Align with project standards. 2012-05-21 16:48:34 -07:00
.gitreview Switch .gitreview to use OpenStack 2012-07-04 13:27:45 +01:00
HACKING.rst Directives to not use variable names that conflict with pdb 2012-03-20 07:16:16 -04:00
LICENSE Initial commit (basics copied from glance) 2012-03-13 21:48:07 +11:00
MANIFEST.in Log all startup operations to /var/log/heat-startup.log 2012-08-03 16:43:59 -07:00
README.rst renaming CloudFormations to CloudFormation 2012-04-13 15:01:41 -04:00
babel.cfg Add setup.py and friends 2012-03-14 09:25:54 +11:00
install.sh Don't use uuidgen in install.sh 2012-07-27 14:37:17 +02:00
openstack-common.conf Import openstack.common.rpc 2012-07-17 08:27:19 -07:00
pylintrc Directives to not use variable names that conflict with pdb 2012-03-20 07:16:16 -04:00
run_tests.sh Split functional test into standalone and utility class 2012-08-23 13:31:42 -04:00
setup.cfg Align with project standards. 2012-05-21 16:48:34 -07:00
setup.py Update openstack-common in prep for pulling in common.rpc 2012-07-13 16:17:36 -07:00
tox.ini Lock to pep 1.1 2012-06-15 08:44:23 -07:00
uninstall.sh Add uninstall script for Heat 2012-06-23 22:41:30 -04:00

README.rst

HEAT

This is an OpenStack style project that provides a REST API to orchestrate multiple cloud applications implementing well-known standards such as AWS CloudFormation and TOSCA.

Currently the developers are focusing on AWS CloudFormation but are watching the development of the TOSCA specification.

Why heat? It makes the clouds rise and keeps them there.

Getting Started -----------

If you'd like to run from the master branch, you can clone the git repo:

git clone git@github.com:heat-api/heat.git

Follow the steps: https://github.com/heat-api/heat/wiki/HeatGettingStarted

References

Related projects