heat/templates
Steve Baker a5510ea245 Implement the AWS::S3::Bucket resource type.
An attempt was made to make created bucket names readable and unique.
Names are of the format heat-<resource name>-<random hex>. eg:
heat-S3Bucket-b420d12d02e5d6e46f13

Only the swift v2 auth is currently supported, which means swift will need to
use keystone for auth. This may be a valid assumption for any environment that
is running Heat.

When DeletionPolicy is Delete then an attempt is made to delete the container,
but the stack will still be deleted if container delete fails.

Run the template S3_Single_Instance.template to give it a try.

Functional tests will be coming in a later change.

Change-Id: Ifa2c3c4fcbdb00a44f8c6b347a61f8e1735e8328
2012-09-11 16:00:17 +12:00
..
2012-07-06 08:50:53 +00:00

-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
- The gold templates:                                                         -
- The gold images contain no cfntools                                         -
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------

WordPress_Single_Instance_gold.template
 - Creates a gold image wordpress single instance - not working

-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
- The cfntools templates:                                                     -
- The CFNTOOLS images contain analogs of AWS cfn tools for full orchestration -
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------

*******************************************************************************
* INSECURE TEMPLATES                                                          *
* The following templates do not properly secure the mysql server and allow   *
* any user to connect to the wordpress database.                              *
*******************************************************************************

WordPress_2_Instances.template
 - Creates a two instance wordpress/mysql server
   Note: There is an instance for mysql and instance for wordpress

WordPress_2_Instances_With_EBS.template
 - Creates a two instance wordpress/mysql server with persistent volume
   Note: There is an instance for mysql and instance for wordpress

WordPress_Composed_Instances.template
 - Creates a two instance wordpress/mysql server.
 - The MySQL server is loaded as a nested template from the URL of the latest
   MySQL_Single_Instance template on GitHub.
   Note: There is an instance for mysql and instance for wordpress

MySQL_Single_Instance.template
 - Creates a single instance MySQL server, for use in template composition

*******************************************************************************
* SECURE TEMPLATES                                                            *
* These templates either are single vm or use EIP and security groups to      *
* secure the servers                                                          *
*******************************************************************************

WordPress_Single_Instance.template
 - Creates a single instance wordpress/mysql server

WordPress_Single_Instance_With_EBS.template
 - Creates a single instance wordpress/mysql server with EBS Volume

WordPress_Single_Instance_With_EIP.template
 - Creates a single instance wordpress/mysql server with EIP with full security

WordPress_Single_Instance_With_EBS_EIP.template
 - Creates a single instance wordpress/mysql server with EIP with full security
   and EBS Volume

WordPress_Single_Instance_deb.template
 - Creates a single instance wordpress/mysql server, ubuntu based template

WordPress_Single_Instance_puppet.template
 - Creates a single instance wordpress/mysql server
 - Uses the Puppet client to install server roles

WordPress_Single_Instance_With_HA.template
 - Creates a single instance wordpress/mysql server
 - Includes configuration to use heat HA features

PuppetMaster_Single_Instance.template
 - Sample template to bring up a Puppet Master instance

WordPress_2_Instances_With_EBS_EIP.template
 - Creates a two instance wordpress/mysql server with persistent volume
 - EIP with full security
   Note: There is an instance for mysql and instance for wordpress

Rails_Single_Instance.template
- Create a Ruby on Rails stack

-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
- Other templates:                                                            -
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------

getting_started.template
 - Skeleton example template

-------------------------------------------------------------------------------
- END OF TEMPLATES                                                            -
-------------------------------------------------------------------------------