Hi Seph, OpenNebula chooses the TM based on which hosts needs to stage the image into. This is defined at the time of adding the host to OpenNebula. Your host seems to be correctly defined to use the lvm tm driver, so the chosing of tm_clone.sh boils down to what is defined in $ONE_LOCATION/tm_lvm/tm_lvm.conf.
Hope it helps, please come back if you need further clarifications, -Tino -- Constantino Vázquez Blanco | dsa-research.org/tinova Virtualization Technology Engineer / Researcher OpenNebula Toolkit | opennebula.org On Thu, May 27, 2010 at 7:39 PM, seph <[email protected]> wrote: > Hi all, I'm playing around with opennebula and LVM and having some > trouble fitting the pieces together. I have a handful of test nodes, > and I'd like each of them to use their local lvm pools. (I realize > this makes migration hard). > > I'm not really sure where to begin debugging it. I created a kvm image > using vmbuilder, and a trivial template, and then I created the > VM. But, opennebula is using tm_commands/ssh/tm_clone.sh and not > tm_commands/lvm/tm_clone.sh thus I'm winding up with the wrong thing. > > My oned.conf: > > HOST_MONITORING_INTERVAL = 60 > VM_POLLING_INTERVAL = 60 > PORT=2633 > DEBUG_LEVEL=3 > NETWORK_SIZE = 254 > MAC_PREFIX = "00:03" > IM_MAD = [ name = "im_kvm", executable = "one_im_ssh", arguments = > "im_kvm/im_kvm.conf" ] > VM_MAD = [ name = "vmm_kvm", executable = "one_vmm_kvm", default = > "vmm_kvm/vmm_kvm.conf", type = "kvm" ] > TM_MAD = [ name = "tm_lvm", executable = "one_tm", arguments = > "tm_lvm/tm_lvm.conf" ] > HM_MAD = [ executable = "one_hm" ] > > My VM template: > > NAME = "TEST" > CPU = "1" > MEMORY = "256" > VCPU = "1" > DISK = [ > type = "block", > source = "/home/seph/testvm/tmpp0wEVF.qcow2", > clone = "no", > size = "4096", > target = "sda", > bus = "virtio" ] > > Some onehost info: > > HOST 0 INFORMATION > ID : 0 > NAME : macbook-test2 > STATE : MONITORED > IM_MAD : im_kvm > VM_MAD : vmm_kvm > TM_MAD : tm_lvm > > And some of the oned log from the creation: > (note the "via ssh" in the second line. That's my instrumentation) > > tm_ln.sh: Link (non shared dir, will clone) > tm_clone.sh: macbook-test2:/home/seph/testvm/tmpp0wEVF.qcow2 > macbook-test2:/var/lib/one//14/images/disk.0 (via ssh) > tm_clone.sh: DST: /var/lib/one//14/images/disk.0 > tm_clone.sh: Creating directory /var/lib/one//14/images > tm_clone.sh: Executed "ssh macbook-test2 mkdir -p /var/lib/one//14/images". > tm_clone.sh: Cloning macbook-test2:/home/seph/testvm/tmpp0wEVF.qcow2 > tm_clone.sh: Executed "scp macbook-test2:/home/seph/testvm/tmpp0wEVF.qcow2 > macbook-test2:/var/lib/one//14/images/disk.0". > tm_clone.sh: Executed "ssh macbook-test2 chmod a+w > /var/lib/one//14/images/disk.0". > > I'm not really sure how opennebula chooses which TM tools to use, so I'm > not really sure how to debug this. Pointers? Help? > > seph > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > _______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
