Re: [one-users] Local storage on the node (lvm, etc)
Hi, As far as I understand the documentation, it looks like all storage options for OpenNebula are shared - ceph, iSCSI, nfs, cLVM. No, you can also use filesystem DS in combination with ssh TM for exemple. However, configuring the storage locally on the node would allow for better performance (especially if using SSDs), even though the VM then would not be fault tolerant (node goes down, so does the storage for the VM). On the other hand it would still be possible to migrate the VM, assuming the original node is up (by copying the data to the new node). I customized the TM (see http://blog.opennebula.org/?p=4002 ), so that image is copied from remote storage (could be ssh or nfs) to the local LVM. I still plan to publish these patch, even if they are based on 3.6, so I'll probably first update them so that they work on 4.x. Is there a way to configure OpenNebula to use local logical volumes as a datastore? Create the lv on the node, boot the VM, if nned be create the lv on another node, migrate the VM. If you join OpenNebulaConf in Berlin, I'll give a talk about it Thursday afternoon (http://opennebulaconf.com/schedule/), I'll be happy to discuss it with you. In a nutshell, you can basically use filesystem DS with a customized version of ssh TM which creates LV on the flight. Maxence -- Maxence Dunnewind maxence.dunnew...@inria.fr Engineer - System administrator on BonFIRE, Eco2Clouds and Grid5000 projects Centre de recherche INRIA Rennes - Bretagne Atlantique, France Equipe Myriads, bureau E206, niveau vert, tel +33 2 99 84 25 76 signature.asc Description: Digital signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Strange behaviour of DEFAULT_DEVICE_PREFIX and TARGET when using Xen in HVM mode
hi, You are right, TARGET cannot be set in the image template, but you can set the DEV_PREFIX, that should be enough to achieve a working deployment file. I investigate more on the subject, finally the conclusion is that Xen in HVM mode can't handle more than 4 devices, that's why it worked with xvdc or xvdd. I tried to upgrade to Xen4 on squeeze to try with devops modules, but because of some stupid packaging decision, I can't make it work as expected. The last decision has been to move to paravirt on Xen3/lenny, which works correctly, I don't have this issue anymore. Thanks for your help, Maxence -- Maxence Dunnewind System Engineer on Bonfire Research Center INRIA Rennes - Bretagne Atlantique, France Team Myriads, Office E219, tel +33 2 99 84 25 76 signature.asc Description: Digital signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Strange behaviour of DEFAULT_DEVICE_PREFIX and TARGET when using Xen in HVM mode
Hi Tino, Not sure why that is the case. To use /dev/xvd* devices in Xen, domU's need to load the xen paravirtualization kernel modules. Maybe loading these drivers as explained in [1] helps? I tried loading these modules without result, the datablock still does not appear. Anyway, if I change the deployment.0 to replace xvde by xvdc, so it looks like : === name = 'one-1956-2' #O CPU_CREDITS = 256 memory = '256' kernel = '/usr/lib/xen-default/boot/hvmloader' disk = [ 'tap:aio:/srv/cloud/one/var/1956/images/disk.0,xvda,w', 'tap:aio:/srv/cloud/one/var/1956/images/disk.1,xvdc,w', 'tap:aio:/srv/cloud/one/var/1956/images/disk.2,xvdb,r', ] vif = [ ' mac=02:00:83:fe:cc:a3,ip=131.254.204.163,bridge=eth0', ] builder='hvm' device_model='/usr/lib/xen-default/bin/qemu-dm' vfb = [ 'type=vnc' ] Then it works, the disk is correctly detected ( as /dev/sdc ). I tried many values, works for xvdc xvdd, does not work for xvde and above (always shown as sdc). Maxence -- Maxence Dunnewind System Engineer on Bonfire Research Center INRIA Rennes - Bretagne Atlantique, France Team Myriads, Office E219, tel +33 2 99 84 25 76 signature.asc Description: Digital signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Strange behaviour of DEFAULT_DEVICE_PREFIX and TARGET when using Xen in HVM mode
Le Thu, Sep 01, 2011 at 04:40:37PM +0200, Tino Vazquez a écrit : Hi, So then, if you set the DEV_PREFIX to xvd, everything should work as expected, right? I mean, you would end up with a deployment file like the one you just modified. no, because it's a blockdevice, the value will be xvde. Take into account that you can set TARGET in the image template, and also force it in the DISK section of the VM template. it would work if I was using templates, but all my datablocks are created using OCCI. Regards, -- Maxence Dunnewind System Engineer on Bonfire Research Center INRIA Rennes - Bretagne Atlantique, France Team Myriads, Office E219, tel +33 2 99 84 25 76 signature.asc Description: Digital signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Strange behaviour of DEFAULT_DEVICE_PREFIX and TARGET when using Xen in HVM mode
And what about the image template (oneimage show image_id)? You can set the TARGET there. Hmm, I may be wrong, but I can only see the DEV_PREFIX, and I guess occi_templates are only for instances, not for compute ressources (datablock), so I don't know any way to hardcode TARGET for all computes (which is not a good idea because it won't work with more than one DB). Maxence -- Maxence Dunnewind System Engineer on Bonfire Research Center INRIA Rennes - Bretagne Atlantique, France Team Myriads, Office E219, tel +33 2 99 84 25 76 signature.asc Description: Digital signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Strange behaviour of DEFAULT_DEVICE_PREFIX and TARGET when using Xen in HVM mode
Hi, Could you please send us the resulting deployment file? You may find it in $ONE_LOCATION/var/vid. deployment file contains : == name = 'one-1858' #O CPU_CREDITS = 256 memory = '256' kernel = '/usr/lib/xen-default/boot/hvmloader' disk = [ 'tap:aio:/srv/cloud/one/var/1858/images/disk.0,xvda,w', 'tap:aio:/srv/cloud/one/var/1858/images/disk.1,sde,w', 'tap:aio:/srv/cloud/one/var/1858/images/disk.2,xvdb,r', ] vif = [ ' mac=02:00:83:fe:cc:97,ip=131.254.204.151,bridge=eth0', ] builder='hvm' device_model='/usr/lib/xen-default/bin/qemu-dm' = Regards, Maxence -- Maxence Dunnewind System Engineer on Bonfire Research Center INRIA Rennes - Bretagne Atlantique, France Team Myriads, Office E219, tel +33 2 99 84 25 76 signature.asc Description: Digital signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Strange behaviour of DEFAULT_DEVICE_PREFIX and TARGET when using Xen in HVM mode
Hi, I'm trying to use DATABLOCK on our installation and have some issues. First, a little bit of context : * Workers : - Xen 3.2, caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 - Debian Lenny, kernel 2.6.26-2, xen version, x86_64 * ONE : - ONE 2.0.1 - Centos 5.5, kernel 2.6.18-194 I use Xen in HVM mode, so my instances' template looks like : CPU= 1 MEMORY = 256 OS = [ kernel = /usr/lib/xen-default/boot/hvmloader ] RAW =[type =xen,data=builder='hvm'] RAW =[type=xen,data=device_model='/usr/lib/xen-default/bin/qemu-dm'] Now the strange things : If I create a system image with DEV_PREFIX=sd, it own't boot. If I create it with DEV_PREFIX=xvd, it will boot correctly but will be seen as /dev/sda (and context will be /dev/sdb). With datablocks, it much more funny, the only combination which seems to work is : - DEV_PREFIX=xvd for the system image - DEV_PREFIX=sd for the datablock image With this combination, resulting onevm show looks like : [snip] CPU=1 DISK=[ CLONE=YES, DISK_ID=0, IMAGE=BonFIRE Debian Squeeze v2, IMAGE_ID=165, READONLY=NO, SAVE=NO, SOURCE=/srv/cloud/one/var/images/58cad9fd025f8135a4ef176a0f7721826a0aea8e, TARGET=xvda, TYPE=DISK ] DISK=[ CLONE=YES, DISK_ID=1, IMAGE=bd18, IMAGE_ID=283, READONLY=NO, SAVE=NO, SOURCE=/srv/cloud/one/var/images/ec02c9e15e297d51c94ef9640909bee7345eb529, TARGET=sde, TYPE=DISK ] [snip] So the system disk has xvda as target, but will finally appear as /dev/sda. Context will appear as /dev/sdb, and the datablock which has target=sdE will appear as /dev/sdc ... any other combination does not work for me (if TARGET=sda for system disk, instance does not boot, if TARGET=xvdX for datablock, the instance boots but the corresponding device never appears). Any hints ? Maxence -- Maxence Dunnewind System Engineer on Bonfire Research Center INRIA Rennes - Bretagne Atlantique, France Team Myriads, Office E219, tel +33 2 99 84 25 76 signature.asc Description: Digital signature ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
