Difference between revisions of "Heat/Vocabulary"
< Heat
Adrian Otto (talk | contribs) |
Adrian Otto (talk | contribs) |
||
Line 1: | Line 1: | ||
+ | |||
This is a comparison of the equivalent vocabulary for describing the primitives used during orchestration. The first column references [[Heat/DSL|This DSL]]. | This is a comparison of the equivalent vocabulary for describing the primitives used during orchestration. The first column references [[Heat/DSL|This DSL]]. | ||
− | + | See also: [[Heat/Vision]] | |
''This is work in progress. Experts please amend as appropriate, and more comments at right or underneath.'' | ''This is work in progress. Experts please amend as appropriate, and more comments at right or underneath.'' | ||
Line 8: | Line 9: | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
− | ! [[Heat/DSL|This DSL]] !! CFN !! TOSCA !! CAMP !! - !! Comments | + | ! [[Heat/DSL|This DSL]] !! CFN !! [https://www.oasis-open.org/committees/download.php/48397/TOSCA-v1.0-wd15.zip TOSCA] !! [http://docs.oasis-open.org/camp/camp-spec/v1.1/csd02/camp-spec-v1.1-csd02.pdf CAMP] !! - !! Comments |
|- | |- | ||
− | | [[Heat/DSL# | + | | [[Heat/DSL#Component|Component]] || juju charm; puppet, chef roles || node (component) || Application Component, Platform Component || || Maybe a AWS::CloudFormation::Init section at a stretch? '''Answer''': no. |
|- | |- | ||
− | | [[Heat/DSL#Deployment|Deployment]] || stack || service, topology || | + | | [[Heat/DSL#Heat_Blueprint|Blueprint]] || template || service/topology template || Assembly Template || || |
+ | |- | ||
+ | | [[Heat/DSL#Deployment|Deployment]] || stack || service, topology || Assembly || || | ||
+ | |- | ||
+ | | [[Heat/DSL#Static_Resources_and_Deployment_Resources|Static Resource]] || more properties/metadata || artifact (component) || Application Component Template || || | ||
|- | |- | ||
| [[Heat/DSL#Static_Resources_and_Deployment_Resources|Deployment Resource]] || resource || artifact || Application Component || || Mostly the same | | [[Heat/DSL#Static_Resources_and_Deployment_Resources|Deployment Resource]] || resource || artifact || Application Component || || Mostly the same | ||
|- | |- | ||
− | | [[Heat/DSL#Options_and_Inputs| | + | | [[Heat/DSL#Options_and_Inputs|Options]] || Parameter declarations || parameters || || || |
|- | |- | ||
− | | [[Heat/DSL#Options_and_Inputs| | + | | [[Heat/DSL#Options_and_Inputs|Inputs]] || Parameters || properties || Parameters || || CAMP Parameters = WIP |
|- | |- | ||
| [[Heat/DSL#Options_and_Inputs|Constraints]] || Parameter constraints || || || || | | [[Heat/DSL#Options_and_Inputs|Constraints]] || Parameter constraints || || || || | ||
|- | |- | ||
− | | [[Heat/DSL# | + | | [[Heat/DSL#Providers|Provider]] || (none) || (out of scope, related to requirements and capabilities) || (out of scope, related to requirements and capabilities) || || Resource Plugin exposed so the user can choose the plugin they want? '''Answer''': An abstraction for implementation details. |
|- | |- | ||
− | + | | [[Heat/DSL#Environment|Environment]] || (none) || (out of scope, handled by requirements) || (out of scope, related to requirements and capabilities) || || An Environment may span multiple providers in multiple clouds | |
− | + | ||
− | | [[Heat/DSL#Environment|Environment]] || (none) || (out of scope, handled by requirements) || (out of scope, related to requirements and capabilities) || || | ||
− | |||
− | |||
|} | |} |
Revision as of 06:53, 17 April 2013
This is a comparison of the equivalent vocabulary for describing the primitives used during orchestration. The first column references This DSL.
See also: Heat/Vision
This is work in progress. Experts please amend as appropriate, and more comments at right or underneath.
This DSL | CFN | TOSCA | CAMP | - | Comments |
---|---|---|---|---|---|
Component | juju charm; puppet, chef roles | node (component) | Application Component, Platform Component | Maybe a AWS::CloudFormation::Init section at a stretch? Answer: no. | |
Blueprint | template | service/topology template | Assembly Template | ||
Deployment | stack | service, topology | Assembly | ||
Static Resource | more properties/metadata | artifact (component) | Application Component Template | ||
Deployment Resource | resource | artifact | Application Component | Mostly the same | |
Options | Parameter declarations | parameters | |||
Inputs | Parameters | properties | Parameters | CAMP Parameters = WIP | |
Constraints | Parameter constraints | ||||
Provider | (none) | (out of scope, related to requirements and capabilities) | (out of scope, related to requirements and capabilities) | Resource Plugin exposed so the user can choose the plugin they want? Answer: An abstraction for implementation details. | |
Environment | (none) | (out of scope, handled by requirements) | (out of scope, related to requirements and capabilities) | An Environment may span multiple providers in multiple clouds |