In my integration adventure of my Xen infrastructure (diskless) with OpenNebula, today I try to use the datastores storage and have some problems.
I can monitor my xen hypervisor and completely create my vm on it, when I create the VM from my template, it does :
- create a new ZFS dataset on my storage server
- set a new zfs quota from template ‘User Input’ attributes
- rsync the master rootfs from storage server to my previously created dataset
- set a new nfs export directive to access the rootfs from the VM
All this works well with the xen deploy script.
So in my mind, I thought I can do this :
When I create a new VM, OpenNebula creates a new dataset in my system datastore, set the quota and nfs settings, rsync the master I choose from images datastore to the dataset previously created in the system datastore. And optionnaly add the correct kernel/initramfs in my os boot line => launch my new vm.
Goal : manage some users quota spacedisk with the frontend
So I create 3 dataset on my zfs pool :
- For my “master” VM
- For my VMs
- For my customs kernels or initramfs
I install the zfs add-on on OpenNebula.
I create image, system datastore, seems OK I have capacity returned
I try to create a new image file : “master-jessie”, I am stuck here !
my “image” is a jessie rootfs, so I choose ‘generic storage datablock’ type and give a NFS path … not really sur for the options… for the path, I try different things and always returns me "Cannot parse image SIZE: "
Can I have explanation on the path attributes ? And on the datastores working ?
Do you think this is possible ? Even partially would appreciate some clues
Sorry if it’s too rough but it is so rough in my mind