Go to file
Tomas Sedovic 4679fb01c6 Allow templates specified from local filesystem
Fixes #47

Passing a template file (as opposed to a URL) to the CLI:

      ./heat -d create wordpress \
        --template-file=../templates/WordPress_Single_Instance.template

caused a 'URI too long' error. The reason was that we were passing the entire
template contents to the Heat API server inside the URL params.

This makes sure that templates are passed around inside HTTP body rather than
the URL.
2012-04-02 18:01:18 +02:00
2012-03-28 11:41:19 +11:00
2012-03-14 09:25:54 +11:00
2012-03-28 12:50:49 -04:00
2012-03-14 09:25:54 +11:00

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 CloudFormations but are watching the development of the TOSCA specification.

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

Quick Start

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

Install Heat by running:

sudo python setup.py install

Setup Heat:

source ~/.openstack/keystonerc heat jeos_create F16 x86_64 nova keypair-add --pub ~/.ssh/id_rsa.pub my_key

Heat must be registered as a Keystone service. As root run:

# source keystonerc # ./tools/heat-keystone-service

try: shell1:

heat-api

shell2:

sudo heat-engine

shell3:

heat create my_stack --template-url=https://raw.github.com/heat-api/heat/master/templates/WordPress_Single_Instance.template

References

Description
OpenStack Orchestration (Heat)
Readme 215 MiB
Languages
Python 99.5%
Shell 0.5%