Difference between revisions of "Heat/Environments"
< Heat
(Created page with "== What is an Environment? == I see an Environment as a container for anything that affects the behaviour of the Template. # So parameters can be written into an environment...") |
|||
Line 17: | Line 17: | ||
'''Example''' | '''Example''' | ||
− | Parameters | + | Options: |
+ | #Parameters and other global options | ||
InstanceType: m1.xlarge | InstanceType: m1.xlarge | ||
DBUsername: angus | DBUsername: angus | ||
Line 27: | Line 28: | ||
api_key: 012345abcdef67890 | api_key: 012345abcdef67890 | ||
Resources: | Resources: | ||
+ | # resource scoped options | ||
DatabaseServer: | DatabaseServer: | ||
Provider: RACKSPACE | Provider: RACKSPACE |
Revision as of 00:40, 24 May 2013
What is an Environment?
I see an Environment as a container for anything that affects the behaviour of the Template.
- So parameters can be written into an environment file or automatically inserted if you pass them on the cli.
- You define any non-default Providers in the Environment
- You can define any extra/non-keystone credetials in the Environment
Template | Static archetectural design of your application |
Environment | Specific details that affect the instantiation of the Template |
Stack | Template + Environment |
Example
Options: #Parameters and other global options InstanceType: m1.xlarge DBUsername: angus DBPassword: verybadpass KeyName: heat_key Credentials: rax_angus: username: myusername api_key: 012345abcdef67890 Resources: # resource scoped options DatabaseServer: Provider: RACKSPACE Credentials: rax_angus WebServer: Provider: RACKSPACE Credentials: rax_angus