Upstream Aeolus is looking to provide reference XML templates, as a foundation people can then build on top of. ie. an Apache HTTPd template, a PostgreSQL template, and others ( further details here: https://lists.fedorahosted.org/pipermail/aeolus-devel/2012-August/012276.html ) For this to work, we'd probably need to add an optional uuid field to the ImageFactory TDL. Something like this (concept version only): <template> <name>apache_httpd</name> <description>Apache httpd server</description> <uuid>00000000-0000-0000-0000-000000000001</uuid> <!-- other normal template stuff here --> </template> ImageFactory would also need to be updated to use the UUID, instead of generating a new one.
For productised CloudForms, this doesn't need to go into 1.1. For upstream though, we probably want this (or something equivalent after discussion) reasonably soon so we can build on top of it.
Justin, Beyond simply allowing this field to exist in TDL, and carrying the reference around in all the resulting objects we create, is there anything tangible that the Factory needs to do with it?
Closing as ancient and unlikely to be worked on.