[one-users] Image Manager and Transfer Manager drivers

[Ruben S. Montero]

Hi,

Basically you have to storage areas:

* The image repository, where your base images are kept. Any operation
to copy or move an image from there are through the Image driver. This
is for: 1) Resitering a new image (CP) 2) Creating an empty image
(MKFS) 3) Copy back a persistent image or a saved_as one (MV)  and 4)
delete an image (RM)

* The storage at the hosts and the VM_DIR (can be local or in a shared
FS). Transfer operations to/from that directories are handle with the
TM. TM move is then used to move the images from the host to the
VM_DIR at the front-end.

Cheers

Ruben

On Wed, Nov 9, 2011 at 3:08 PM, Humberto N. Castejon Martinez
<humcasma at gmail.com> wrote:
> Hi,
>
> I have two questions regarding some of the commands in these two sets of
> drivers.
> When is the IM's mkfs command used and when the TM's mkimage command ?
> When (for what) is the   IM's mv command used? (I understand the TM's mv
> command is used to move the image used by a running VM back to the
> repository, right?)
> Thanks.
> Cheers,
> Humberto
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>

-- 
Ruben S. Montero, PhD
Project co-Lead and Chief Architect
OpenNebula - The Open Source Toolkit for Data Center Virtualization
www.OpenNebula.org | rsmontero at opennebula.org | @OpenNebula