----- Original Message -----
On 12/03/2012 01:26 PM, Justin Clift wrote:
I would actually go a step further and offer not only templates but deployables as well. I know we can make a trivial deployable from a given template so this would be for showing off more complex stuff: multi-instance deployments, launch-time parameters and provisioning, etc.
We can put them in the Default (or Sample) catalog and have Conductor immediately useful.
Bundling sample deployables will be more difficult because they need to contain specific image IDs in order to be launchable, but I still think it's a good idea to do.
I remember there was some discussion about alternatives to image-specific IDs back when we were discussing templates.aoelusproject.com:
https://lists.fedorahosted.org/pipermail/aeolus-devel/2012-June/010814.html