[one-users] ONE 3.6: Problem with LVM datastore
Dietrich, Stefan
stefan.dietrich at desy.de
Fri Jul 13 02:21:54 PDT 2012
Hello Jaime,
I followed your steps, but they are not working for me.
I put the raw image in /scratch/execnode.img and created a template for
it with the PATH attribute. I did this on host01, my front end with oned
running etc.
I registered the image and ONE created a LV on host03, one of my LVM
host, see logs below.
But the image was not dumped with dd into the LV and therefore the
virtual machine came up without a disk.
I had a look into the LVM datastore scripts and the DUMP is not executed
on the CP event. They should work without problems with just LVM and not
CLVM.
Regards,
Stefan
Fri Jul 13 11:03:41 2012 [ImM][I]: Copying /scratch/execnode.img to
repository for image 45
Fri Jul 13 11:03:42 2012 [ImG][D]: Message received: LOG I 45 cp:
Copying local image /scratch/execnode.img to the image repository
Fri Jul 13 11:03:42 2012 [ImM][I]: cp: Copying local
image /scratch/brid-node.img to the image repository
Fri Jul 13 11:03:42 2012 [ImG][D]: Message received: LOG I 45 ExitCode:
0
Fri Jul 13 11:03:42 2012 [ImM][I]: ExitCode: 0
Fri Jul 13 11:03:42 2012 [ImG][D]: Message received: CP SUCCESS 45
host03.desy.de:vg_cloud.lv-one-45
Fri Jul 13 11:03:42 2012 [ImM][I]: Image copied and ready to use.
On Fr, 2012-07-13 at 10:59 +0200, Jaime Melis wrote:
> 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
--
Stefan Dietrich <stefan.dietrich at desy.de>
More information about the Users
mailing list