Hi Carsten, Yes, it is necessary if you want to be able to use the image name's in the template, like
DISK = [ IMAGE = "Ubuntu Lucic" ] Otherwise, you are forcing the users to use images by their IMAGE_ID, which is an internal ID that can change at any time, e.g., you define templates for your IMAGE "Ubuntu" and a VM that uses "Ubuntu", but the VM template has be modified if you delete and register again some time later that IMAGE) Regards, Carlos Martín, Cloud Technology Engineer/Researcher DSA Research Group: web http://dsa-research.org and blog http://blog.dsa-research.org OpenNebula Open Source Toolkit for Cloud Computing: http://www.OpenNebula.org On 29 September 2010 07:20, <carsten.friedr...@csiro.au> wrote: > Trying to insert a second image with the same name into the image > repository creates an error on the database layer. Since images are already > uniquely defined by their id, and it is not unlikely that different users > may choose the same name for an image, e g. “Ubuntu Lucid”, I’m not sure > this restriction is doing more good than harm (by confusing users through > hard to interpret error messages). Is it really necessary? > > > > Carsten > > > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > >
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
