[one-users] ONE 3.6: Problem with LVM datastore

[Jaime Melis]

Hello Stefan,

Yes, there was a major change in the SOURCE attribute between the versions
you mention. The current LVM drivers don't support SOURCE the way you are
using them, since the expect a specific format for the SOURCE and your
example "/dev/vg_cloud/execnode" doesn't work since it doesn't match that
format.

The correct way to use them is:
1) You have a local file in your frontend that holds the image, let's say
ubuntu.img
2) you register an image "oneimage create ubuntu.one -d <lvm_ds_id>".
Inside ubuntu.one you'll have PATH=/path/to/ubuntu.img (and NOT source)
3) after the image create is performed you can use it as a regular image
(use it inside the template as IMAGE_ID = ...)

This means that all the LVs you already have in your host can't be used
unless they've been created by the "oneimage create". If this is a major
problem and a drawback, let us know and we can think about how to support
your preeexisting images defined with your own SOURCE and not with PATH, by
changing the tm/iscsi drivers.

cheers,
Jaime

On Fri, Jul 13, 2012 at 9:57 AM, Dietrich, Stefan
<stefan.dietrich at desy.de>wrote:

> Hello,
>
> I upgraded my installation from ONE 3.2 -> 3.6 with running virtual
> machines without trouble, but I am facing some problems with the new LVM
> datastore. I have some hosts with LVM (no CLVM!) and the volume group
> vg_cloud.
>
> Creating the datastore works without problems. The image is already on
> the host in a logical volume. I can register the image with the SOURCE
> attribute pointing to the path: /dev/vg_cloud/execnode
>
> If I try to instantiate the image, ONE creates a wrong path to clone the
> image:
> Fri Jul 13 09:36:21 2012 [TM][D]: Message received: LOG I 861 Command
> execution fail: /var/lib/one/remotes/tm/lvm/clone host01:/dev/vg_cloud
> /execnode host03:/var/lib/one//datastores/0/861/disk.0 861 104
>
> Fri Jul 13 09:36:21 2012 [TM][D]: Message received: LOG E 861 clone:
> Command "    set -e
>
> Fri Jul 13 09:36:21 2012 [TM][D]: Message received: LOG I 861 mkdir
> -p /var/lib/one/datastores/0/861
>
> Fri Jul 13 09:36:21 2012 [TM][D]: Message received: LOG I 861 sudo
> lvcreate -s -L512 -n /dev/vg_cloud/execnode-861-0 /dev//dev/vg_clou
> d/execnode//dev/vg_cloud/execnode
>
> Fri Jul 13 09:36:21 2012 [TM][D]: Message received: LOG I 861 ln -s
> "/dev//dev/vg_cloud/execnode//dev/vg_cloud/execnode-861-0" "/
> var/lib/one/datastores/0/861/disk.0"" failed:
> "/dev//dev/vg_cloud/execnode//dev/vg_cloud/execnode": Invalid path for
> Logical Vo
> lume
>
> Fri Jul 13 09:36:21 2012 [TM][D]: Message received: LOG I 861 The origin
> name should include the volume group.
>
> Fri Jul 13 09:36:21 2012 [TM][D]: Message received: LOG I 861 Run
> `lvcreate --help' for more information.
>
> Fri Jul 13 09:36:21 2012 [TM][D]: Message received: LOG E 861 Error
> cloning /dev//dev/vg_cloud/execnode//dev/vg_cloud/execnode to
>  /dev//dev/vg_cloud/execnode//dev/vg_cloud/execnode-861-0
>
> Fri Jul 13 09:36:21 2012 [TM][D]: Message received: LOG I 861 ExitCode:
> 3
>
> Fri Jul 13 09:36:21 2012 [TM][D]: Message received: TRANSFER FAILURE 861
> Error cloning /dev//dev/vg_cloud/execnode//dev/vg_cloud/execnode
> to /dev//dev/vg_cloud/execnode//dev/vg_cloud/execnode-861-0
>
> I created the datastore with the following configfile:
> NAME = LVMHOST
> DS_MAD = lvm
> TM_MAD = lvm
> VG_NAME = vg_cloud
> HOST = host03
>
> I tried to create the datastore with the DISK_TYPE attribute, but this
> did not help.
>
> Image with the source attribute:
> SOURCE      = "/dev/vg_cloud/execnode"
>
> I am at the moment stuck at this point, in the old installation this
> worked without problems.
>
> Regards,
> Stefan
>
> --
> Stefan Dietrich <stefan.dietrich at desy.de>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>



-- 
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/20120713/91ece394/attachment-0003.htm>