[pve-devel] qemu-server : add new qm import_disk feature
aderumier at odiso.com
Thu Jan 19 16:27:13 CET 2017
>>well... you can't have your cake and eat it too? or in other words,
>>nothing in life is free..
Well, to have a real example, I have a customer which have migrated around 50 vmware vms with exactly your steps,
and he said me that's easy really to slow/long will all this steps.
Just to compare , openstack have a single line command import
glance image-create --name "NAME" \
--is-public IS_PUBLIC \
--disk-format DISK_FORMAT \
--container-format CONTAINER_FORMAT \
@cc Stefan && Timo from profihost, as they also try to implement disk image upload last year
----- Mail original -----
De: "Fabian Grünbichler" <f.gruenbichler at proxmox.com>
À: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Jeudi 19 Janvier 2017 11:21:55
Objet: Re: [pve-devel] qemu-server : add new qm import_disk feature
On Thu, Jan 19, 2017 at 10:24:17AM +0100, Alexandre DERUMIER wrote:
> The problem with 1),
> it's that users don't have always local file storage space.
> (for example, they have only small local disk and disks are on a san, or they have big lvmthin storage but no space for files)
> My students/customers generaly export image on usb drive or network share,
the directory storage does not have to be local (e.g., a CIFS or NFS
share mounted locally works just fine) - "local" is just the default PVE
> and don't known nothing about directory structure (/images/vmid/vm-ID-whatever)
> and don't want to define a storage for this in proxmox configuration.
well... you can't have your cake and eat it too? or in other words,
nothing in life is free..
if you add your mounted USB drive / network share / .. as directory
storage, it will even add the directory structure and you just need to
move the disk image..
alternatively, but I would only recommend this temporary while
importing, you can use a symlink instead of moving/copying the disk
image. then you neither need to add a new (temporary) storage, nor do
you need to copy (with all the space and time requirements). a simply
"ln -s" (again, with the right target name and location!) followed by
"qm rescan -vmid ID" is enough. after using move disk, don't forget to
remove the symlink to prevent accidents. (removing the unused source
disk in PVE should only remove the symlink, but I would not rely on
> I'm more to implement root permission only and add some regex for paths. (CLI only is enough)
if you mean a whitelist regex of acceptable paths, I don't really see
the advantage compared to the existing whitelist of "put it on a
storage with an accepted name". adding a blacklist does not help at all?
pve-devel mailing list
pve-devel at pve.proxmox.com
More information about the pve-devel