Hello,
I am migrating KVM VMs from Archipel orchestrator, which includes importing mutiple VM disk images into Opennebula 5.2 datastore.
I am using CLI oneimage create
command.
When I execute command it returns right away, but when I do it mutiple times for mutiple images I notice that images are getting queued - is it intentional or there is some configuration piece missing in my setup?
(4 Opennebula nodes, NFS image store)
Versions of the related components and OS (frontend, hypervisors, VMs):
Opennebula 5.2
Steps to reproduce:
Try to import multiple qcow2 images via “oneimage create”. Say
oneimage create --name "os-1" --type OS --description "os1" --path=/var/tmp/vms2/vm/drives/xxx/os1.qcow2 --driver qcow2 -d imgfsds oneimage create --name "bkp1" --type DATABLOCK --description "bkp1" --path=/var/tmp/vms2/vm/drives/xxx/bkp1.qcow2 -d imgfsds --driver qcow2
Current results:
Watch staging DIR for file import progress, you will see that until 1st image file finished copying, next image file will not start.
Expected results:
Image files should be imported in parallel independently from each other, in as many threads as many oneimage create
processes are executed.