From Fedora Project Wiki

Revision as of 19:49, 19 July 2012 by Sdake (talk | contribs) (Created page with "{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To rea...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.
Set a Page Watch
Make sure you click watch on your new page so that you are notified of changes to it by others, including the Feature Wrangler
All sections of this template are required for review by FESCo. If any sections are empty it will not be reviewed



Heat

Summary

Heat provides an AWS CloudFormation API for OpenStack. The CloudFormation API allows the orchestration of cloud applications using file or web based templates.

Owner

  • Email: <sdake@redhat.com>

Current status

  • Targeted release: Fedora 18
  • Last updated: July 19, 2012
  • Percentage of completion: 90%


Detailed Description

Heat provides orchestration of composite cloud applications using the CloudFormation API and templates for OpenStack. Heat has requested OpenStack incubation and is currently an OpenStack related project.

Benefit to Fedora

Heat provides a standardized method for OpenStack users to launch multiple applications in an OpenStack cloud from a template file describing the cloud application.

Scope

The feature is currently going through package review. the Heat implementation is high quality and secure, but still needs much work before it will be acceptable for incubation by the OpenStack community.

How To Test

1. Install and configure Folsom OpenStack on the system. 2. To test the feature, the Heat community recommends running through the Getting Started Guide.we recommend running the quickstart guide. 3. The getting started guide explains the expected results of the feature. [Getting Started Guide|https://github.com/heat-api/heat/blob/master/docs/GettingStarted.rst#readme]

User Experience

The user will notice an AWS CloudFormation API available via the heat CLI command.

Dependencies

We depend on a functional OpenStack implementation, but currently work well with Essex. We will also work well with Folsom when it becomes more stable.

Contingency Plan

The feature could be removed entirely as a contingency plan.

Documentation

  • All documentation is in the Heat project's [1].

Release Notes

  • Heat was added to provide an AWS CloudFormation API for OpenStack.

Comments and Discussion