On 04/12/2012, at 2:54 PM, Jiří Stránský wrote:
<snip>
This seems like a similar issue as including default image templates
and deployables [1].
Might be nice to include default templates, deployables and admin account when you are
setting up Aeolus for development or evaluation, but not for production.
Yeah, similar kind of thing, but the password issue is more
serious. :)
It's not unusual when deploying software "to production" to have a
checklist of steps to follow before "it's ready".
i.e. putting in appropriate values for the environment, removing
default things that don't need to be there, etc.
Unlike the password thing, if someone misses a step and doesn't
remove default templates... it's not likely to be a big deal. The
default templates would probably show up in Conductor for people,
so someone would realise at some point "oh, they should have been
removed" and file a ticket with their appropriate support group.
+ Justin
--
Aeolus Cloud Evangelist
http://www.aeolusproject.org