Dear Olivier,
When using the Image Catalog, and not the old method of specifying the
full image path in the source attribute, the values of disk attributes
save and clone are overridden by the Image Catalog inferring them
from the image properties (persistency, save_as).
If you want to save the
ok, so it is rather an issue with documentation not really clear at
http://www.opennebula.org/documentation:rel2.0:img_template.
Page should specify that image template override vm template for disk
related data.
In my case, I do not want to save the VM, and I do not specify any tag
to do so
Hi Rich,
I've put a note in the VM template definition section to warn about
the attributes that will be ignored when using the Image Catalog.
A template validator is totally within our roadmap, we will provide
that in future releases for sure.
Thanks and regards,
-Tino
--
Constantino Vázquez
Good deal!
rw2
On 10/26/10 9:02 AM, Tino Vazquez wrote:
Hi Rich,
I've put a note in the VM template definition section to warn about
the attributes that will be ignored when using the Image Catalog.
A template validator is totally within our roadmap, we will provide
that in future releases
in system-wide installation, the save of the image on frontend is done
in /var/lib/one.
This directory is not configurable in oned.conf. This can be an issue
with disk size when many VMs are saved. Required storage can be huge.
An option of course is to copy the content then to mount this
An easier way to do that is to symlink your storage path to that dir.
On Tue, Oct 26, 2010 at 5:56 PM, Olivier Sallou olivier.sal...@irisa.fr wrote:
in system-wide installation, the save of the image on frontend is done in
/var/lib/one.
This directory is not configurable in oned.conf. This
