Bug 1042233

Summary: [RFE][heat]: Support configurable template repo URL
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/heat/+spec/hot-repo
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:40:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 21:28:28 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/hot-repo.

Description:

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://repos.example.org/
$ heat-cli install lamp --parameters="AppServers=2"

Specification URL (additional information):

None