multiple cloud applications implementing well-known standards such as AWS
CloudFormation and TOSCA.
-Currently the developers are focusing on AWS CloudFormations but are watching
+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.
print ' heat jeos_create <distro> <arch> <instancetype>'
print ' instance type can be:'
print ' gold builds a base image where userdata is used to initialize the instance'
- print ' cfntools builds a base image where AWS CloudFormations tools are present'
+ print ' cfntools builds a base image where AWS CloudFormation tools are present'
sys.exit(1)
distro = arguments.pop(0)
"""
Heat API Server. This implements an approximation of the Amazon
-CloudFormations API and translates it into a native representation. It then
+CloudFormation API and translates it into a native representation. It then
calls the heat-engine via REST to implement them.
"""
1. Create image with application ready to go
2. Use cloud-init to run a startup script passed as userdata to the nova
server create
-3. Use the CloudFormations instance helper scripts
+3. Use the CloudFormation instance helper scripts
This directory contains files required for choice #3.
installs packages, and starts services
cfn-signal - Waits for an application to be ready before continuing, ie:
supporting the WaitCondition feature
-cfn-hup - Handle updates from the UpdateStack CloudFormations API call
+cfn-hup - Handle updates from the UpdateStack CloudFormation API call
# under the License.
"""
-Implements cfn-hup CloudFormations functionality
+Implements cfn-hup CloudFormation functionality
"""
# under the License.
"""
-Implements cfn-init CloudFormations functionality
+Implements cfn-init CloudFormation functionality
Resource metadata currently implemented:
* config/packages
# under the License.
"""
-Implements cfn-signal CloudFormations functionality
+Implements cfn-signal CloudFormation functionality
"""