[pve-devel] lxc : disk file names, should'nt we use same pattern than qemu ?

Alexandre DERUMIER aderumier at odiso.com
Thu Jul 30 13:03:49 CEST 2015


>>But multi-volume container is a bit too much for me, and it is 
>>unclear to me why we need it? 

to use different storages with different speed for example. (CT with ssd + hdd)

>>Honestly, the plan was to support lxc.mount.entry, so that the user 
>>can mount additional data (nfs, bind mounts). 

in the case of rbd for example, we need to mount/unmount rbd at start/stop, so we need to define them in volid (storeid:volid)



----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "aderumier" <aderumier at odiso.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Jeudi 30 Juillet 2015 12:36:04
Objet: Re: [pve-devel] lxc : disk file names, should'nt we use same pattern than qemu ?

> >>Besides, I am quite unsure it we want to add support for multiple disks 
> >>at this stage. This makes things like backup/restore much more complex. 
> 
> Ok, right. Maybe later when all features will be implemented ? 

Honestly, the plan was to support lxc.mount.entry, so that the user 
can mount additional data (nfs, bind mounts). 

But multi-volume container is a bit too much for me, and it is 
unclear to me why we need it? 


More information about the pve-devel mailing list