Hi Antanas,

Using ssh drivers and persistent images does not mean that the copy is
not necessary, since the image DS doesn't have to be accesible as a
local filesystem in the virtualization node. On VM shutdown, if the
image is persistent it will be copied back to the datastore to avoid
losing changes.

hih,

-Tino



--
OpenNebula - Flexible Enterprise Cloud Made Simple

--
Constantino Vázquez Blanco, PhD, MSc
Senior Infrastructure Architect at C12G Labs
www.c12g.com | @C12G | es.linkedin.com/in/tinova

--
Confidentiality Warning: The information contained in this e-mail and
any accompanying documents, unless otherwise expressly indicated, is
confidential and privileged, and is intended solely for the person
and/or entity to whom it is addressed (i.e. those identified in the
"To" and "cc" box). They are the property of C12G Labs S.L..
Unauthorized distribution, review, use, disclosure, or copying of this
communication, or any part thereof, is strictly prohibited and may be
unlawful. If you have received this e-mail in error, please notify us
immediately by e-mail at ab...@c12g.com and delete the e-mail and
attachments and any copy from your system. C12G thanks you for your
cooperation.


On 11 June 2014 15:34, Antanas Masevicius <antanas.masevic...@ntt.lt> wrote:
> Hello,
>
> been struggling to resolve situation with persistent images. That is
> images gets copied (during instantiation) after setting DS to ssh, even
> on local storage.
> At first i had only machine with local data storage which look like:
>
> oneadmin@xen-host0:~/datastores/0/42$ onedatastore list
> ID NAME SIZE AVAIL CLUSTER IMAGES TYPE DS TM
> 0 system 110.1G 20% - 0 sys - shared
> 1 default 110.1G 20% - 8 img fs shared
> 2 files 110.1G 20% - 0 fil fs shared
>
> then, i added another xen host for which i have set data storage TM to ssh:
>
> oneadmin@xen-host0:~/datastores/0/42$ onedatastore list
> ID NAME SIZE AVAIL CLUSTER IMAGES TYPE DS TM
> 0 system 110.1G 20% - 0 sys - shared
> 1 default 110.1G 20% - 8 img fs shared
> 2 files 110.1G 20% - 0 fil fs shared
> 100 xen1_ds_syste - - A_cluster 0 sys - ssh
>
> This did not let me deploy image to remote (new) host. Someone suggested
> i have to set image DS to ssh:
>
> oneadmin@xen-host0:~/datastores/0/42$ onedatastore list
> ID NAME SIZE AVAIL CLUSTER IMAGES TYPE DS TM
> 0 system 110.1G 20% - 0 sys - shared
> 1 default 110.1G 20% - 8 img fs ssh
> 2 files 110.1G 20% - 0 fil fs ssh
> 100 xen1_ds_syste - - A_cluster 0 sys - ssh
>
> Now, i was able to instantiate image on remote host. This is fine, but,
> when i tried to instantiate image for local host, it also started to
> copy persistent images on instatiation.
>
> What is practice for such cases? Should i run everything on shared media
> only or maybe there is some other way to achieve this compatibility?
>
> best regards,
> Antanas
>
> --
> Antanas Masevičius
> Technikos direktorius
> UAB "Nacionalinis telekomunikaciju tinklas"
> Tel.  +370 5 2056000
> Tel.  +370 700 00031 (tiesioginis)
> Fax.  +370 700 00034
> el.p: antanas.masevic...@ntt.lt
> www.ntt.lt
> www.spykas.com
>
> _______________________________________________
> 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

Reply via email to