>>Isn't that good enough?
Yes, perfect like this !
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIER"
Cc: pve-devel@pve.proxmox.com
Envoyé: Samedi 16 Février 2013 09:21:14
Objet: RE: new has_feature for 'create_base'
> vms are grouped by pool (1 pool by customer by
> vms are grouped by pool (1 pool by customer by example), but the template
> need to be available across differents pools.
I will introduce a new permission called VM.Copy, and a new role:
PVETemplateUser ==> VM.Copy
So you can simply assign that role to the template for selected users and
gro
>>But I am not sure what you talk about? What kind of pools/templates do you
>>talk about exactly?
I was talking about pool permissions
http://pve.proxmox.com/wiki/User_Management#Pools
vms are grouped by pool (1 pool by customer by example), but the template need
to be available across differ
> > One other thing that could be great, is to have some "public"
> > templates, available across differents vm pools.
> > Could be usefull to provide generic templates for differents customers.
> > What do you think about this ?
>
> The plan was to simply use VMID 0 for those.
But I am not sure
> One other thing that could be great, is to have some "public" templates,
> available across differents vm pools.
> Could be usefull to provide generic templates for differents customers.
> What do you think about this ?
The plan was to simply use VMID 0 for those.
___
>>Please can you assemble a patch for that?
Yes sure, I'll send it today.
> lvm could be also use template but only copy for now. (maybe clone in the
> futur ?)
>>makes no sense if we can't clone? Or can we clone by creating a qcow2 image
>>on, but what size do we use?
>>dm-thin solves
> mmm, yes, maybe is better to hava a "base" feature. (maybe
> has_feature('template') ?)
Yes, I like has_feature('template') ;-)
> I think we can add it to all storage can be template, except storage we can't
> rename. (iscsi,isciredirect)
Please can you assemble a patch for that?
> lvm cou
mmm, yes, maybe is better to hava a "base" feature. (maybe
has_feature('template') ?)
I think we can add it to all storage can be template, except storage we can't
rename. (iscsi,isciredirect)
lvm could be also use template but only copy for now. (maybe clone in the futur
?)
what do you think
I first thought we can use the 'clone' check, but that results in:
# qm template 200
volume 'local:200/vm-200-disk-1.raw' does not support template/clone
So we need an new feature check like: has_feature('base') ?
___
pve-devel mailing list
pve-devel@p
