[one-users] CLVM datastore

[Jaime Melis]

Hi Kapetanakis.

I think you can achieve all those things without hacking code.

* Using block devices directly:

A suggested workflow to work directly with block devices is to create a new
empty persistent image of type datablock and use it inside a VM and install
the OS directly to that image. If you do think the only actions are
"lvcreate" and "mkfs" on the new LV.

http://opennebula.org/documentation:rel3.8:img_guide#create_images

* Attaching a CDROM

That should definitely work. If it's not working then there might be a
problem with the installation or the OpenNebula templates.
I couldn't find out how to do that with templates. Making CDROM images
didn't work since it asked for IDE controller which was not pressent. Can
you elaborate a bit more on the problems you're having with CDROM images?
ISO image do work.

* Passing options to the vm's XML

There is a specific RAW attribute precisely for this:
http://opennebula.org/documentation:rel3.8:template#raw_section

cheers,
Jaime

On Fri, Feb 22, 2013 at 5:22 PM, Kapetanakis Giannis <
bilias at edu.physics.uoc.gr> wrote:

> On 20/02/13 13:44, Jaime Melis wrote:
>
>> Hello Kapetanakis,
>>
>> can you describe the modifications you would make to the deploy script
>> for instance in order to give you a better solution?
>>
>> cheers,
>> Jaime
>>
>
> Maybe I'm wrong and the changes are not needed in kvm driver, but in lvm
> drivers.
>
> The whole idea would be to be able to work directly on block devices
> and not copying file images around. For instance to add a new empty 100GB
> disk on a VM
> you have to create a image for that and then attach it to VM which would
> copy
> the image to a new LV. That is not acceptable. A new LV should be created
> and attached directly.
>
> I guess I would also add an ide controller in order to add cdrom device
> which would be able to use .iso images like libvirt does.
> I couldn't find out how to do that with templates. Making CDROM images
> didn't work since it asked for IDE controller which was not pressent.
>
> I would pass more options in the vm's XML (like apic feature, clock ..
> etc).
> Again I couldn't use template to do that.
>
> These actions seem to me that are controlled by kvm (deploy, attach_disk)
> and not the tm driver.
> Maybe I misunderstood something or didn't read enough.
>
> G
> ps. Also saw the cxm drivers but these are supposed to work on XEN and not
> KVM.
>
>
>
>


-- 
Jaime Melis
Project Engineer
OpenNebula - The Open Source Toolkit for Cloud Computing
www.OpenNebula.org | jmelis at opennebula.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20130228/59a946b6/attachment-0002.htm>