Support configurable template repo URL
Establish a feature in the Heat CLI and Horizon clients that allows a configurable URL to be supplied as a repo for templates. It shall be defaulted to a community repository of well known best practices that the OpenStack user community can contribute to. A one-time repo registration command would save the preference in a local settings file like .heat. This would enable deployment of well known templates by a name, rather than specifying an explicit template file. The example below registers an alternate repo rather than the default OpenStack one, and installs a lamp stack with 2 app servers. If you skip the repo registration step, it just uses the community repo.
$ heat-cli repo http://
$ heat-cli install lamp --parameters=
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Angus Salkeld
Related branches
Related bugs
Sprints
Whiteboard
I recognize that the current clo tool is heat-cfn. This blueprint anticipates that we have an OpenStack native tool called heat-cli that uses the new API and DSL that we are working on in this blueprint:
https:/
See also:
https:/
(asalkeld) this could be done with environments.
This could be a neat way to solve this problem:
"
template:
base_url: http://
parameters:
bla: foo
resources:
provider: big_cloud
"
This could also mean that any nested stacks could use relative urls.
2013.06.03 - RB: While I agree with the above, I don't think its the intent of this (or https:/
