Snippet Resource
1. Snippet
...
resources:
snippet1:
type: OS::HEAT::Snippet
properties:
inputs:{...}
outputs: [...] # defaults: stdout, stderr, exit
snippet: ... # snippet running in heat engine
2. Definition
inputs: key value pairs,
ouputs: name list, the values can be accessed via get_attr,
snippet: a runable script.
inputs key pairs will be set to environment,
stdout should be in json format to output,
exit code is an embedded output
The system will capture the output of the snippet and set it in attributes for get_attr
Blueprint information
- Status:
- Complete
- Approver:
- Zane Bitter
- Priority:
- Undefined
- Drafter:
- JunJie Nan
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Zane Bitter
Related branches
Related bugs
Sprints
Whiteboard
(zaneb) What exactly do you mean by "snippet running in heat engine"?
(nanjj) A snippet for example, a python script is invoked in heat engine.
If you do actually mean running inside heat-engine, not on a Nova server, then -2. Heat is not a compute service; we have Nova for that.