[one-users] VMWare Server 2.0 and non-persistent images to minimize copy when deploying

[Tino Vazquez]

Hi Manish,

You can avoid the copy of the image if you:

 1) Use the dummy TM drivers
 1) Stop using the image catalog, and input the SOURCE of the disks
with the following format

       [DATASTORE] relative/path/to/disk

The path is relative wrt the DATASTORE.

hope it helps,

-Tino

--
Constantino Vázquez Blanco, MSc
OpenNebula Major Contributor
www.OpenNebula.org | @tinova79



On Wed, Feb 23, 2011 at 1:39 PM, Manish Sapariya <manish at gslab.com> wrote:
> Hi,
> We have are using OpenNebula 1.4 using following kind of setup.
> The non-persistent disk that I used in OpenNebula 1.4 is not
> working in 2.0.
>
> The reason it worked with 1.4 is that it copied the directory as
> it is without looking into the directory. My .vmx file was modified
> to had a link to non-persistent disk and hence the solution was working.
>
> 2.0 specifically copies the vmdk file and then creates a deployment
> file. And hence my 1.4 solution is not working with 2.0.
>
> My question is, can I tell opennebula to use specific image on
> hypervisor, instead of making a copy of vmdk and using that as the
> instance disk.
>
> Thanks and Regards,
> Manish
>
> On 9/27/2010 5:02 PM, Manish Sapariya wrote:
>
> Hi All,
> I thought somebody will find this useful and hence
> sharing it here.
>
> We are using opennebula based setup to test our
> collaboration product. We have home grown test framework
> which can run clients on different machines to execute
> test scenarios. Things were fine until we had only few
> users in our test. However as I added more users in test,
> the VMs deploying started taking too long because of the
> image copying. My frontend is on FC8, with big SATA disk.
> The datastore is expored using CIFS. The VMWare Hypervisors
> mount the datastore using CIFS to run the VMs.
>
> To minimize the copy of the whole disk on deploy, we
> followed solution detailed in 1, which is briefly mentioned
> as below.
>
> - Create your base image, call it basevm.
> - Modify the disk settings to non-persistent.
> - Now create another VM, clone1 , using the disk of
>   basevm.
>   - Set the new disk as non-persistent.
> - Create the vm template pointing to clone1. Note that
>   both the basevm and clone1 images should be in your
>   exported datastore path.
> - Deploy as many VMs as you like, with just few MBs of
>   data to copied.
>
> Hope this helps somebody.
>
> 1. http://communities.vmware.com/thread/15339
>
>
> --
> Thanks and Regards,
> Manish
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>