[one-users] one2 : save tag does not seem to work
olivier.sallou at irisa.fr
Tue Oct 26 08:56:42 PDT 2010
in system-wide installation, the "save" of the image on frontend is done
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 directory
on an external file system (nfs or attached disk), but wouldn't it be
easier to be able to specify the location of saved data?
Le 10/26/10 3:18 PM, Javier Fontan a écrit :
> Adding to that "stop" does not mean kill-the-vm. It will susped a VM
> and save its state/image in the frontend so it can be resumed in any
> other host. That's why it retrieves the image back to the frontend.
> On Tue, Oct 26, 2010 at 2:29 PM, Tino Vazquez<tinova at fdi.ucm.es> wrote:
>> 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 image when using the Image Catalog, either
>> make it persistent or, if you want to save it as another image, use
>> the save_as functionality.
>> Best regards,
>> Constantino Vázquez Blanco | dsa-research.org/tinova
>> Virtualization Technology Engineer / Researcher
>> OpenNebula Toolkit | opennebula.org
>> On Tue, Oct 26, 2010 at 1:23 PM, Olivier Sallou<olivier.sallou at irisa.fr> wrote:
>>> I have a template with:
>>> DISK = [
>>> image = "sampleraw2",
>>> save = "no"
>>> and when I do "onevm stop", one still tries to save the vm on the frontend.
>>> (I also tried with save=no instead of save="no").
>>> Should I create a bug for this or is there something wrong in my template?
>>> Users mailing list
>>> Users at lists.opennebula.org
>> Users mailing list
>> Users at lists.opennebula.org
More information about the Users