This is needed to protect volumes when creating templates
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
dre Derumier
> Sent: Donnerstag, 29. November 2012 10:39
> To: pve-devel@pve.proxmox.com
> Subject: [pve-devel] pve-storage : volume_lock && volume_unlock
>
> This is needed to protect volumes when creating templates
>
>
ange that in my git.
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre Derumier" , pve-devel@pve.proxmox.com
Envoyé: Lundi 3 Décembre 2012 06:22:43
Objet: RE: [pve-devel] pve-storage : volume_lock && volume_unlock
I think you should not use the term
Hi Alexandre,
Am 03.12.2012 08:53, schrieb Alexandre DERUMIER:
I think you should not use the term 'lock/unlock' here.
Maybe something like:
volume_protect(true/false)
volume_protect seem good. (as snapshot are not really readonly, and rbd already
use protect for the rbd command)
I'll chan
an Priebe - Profihost AG"
À: pve-devel@pve.proxmox.com
Envoyé: Lundi 3 Décembre 2012 09:23:46
Objet: Re: [pve-devel] pve-storage : volume_lock && volume_unlock
Hi Alexandre,
Am 03.12.2012 08:53, schrieb Alexandre DERUMIER:
>>> I think you should not use the term
ve.proxmox.com
> Subject: Re: [pve-devel] pve-storage : volume_lock && volume_unlock
>
> >>It would be cool if we have these git repos public containing new
> >>features / work in progress ideas.
> >>
> >>What about mirroring to github and w
t; Sent: Montag, 03. Dezember 2012 11:15
> To: Stefan Priebe - Profihost AG
> Cc: pve-devel@pve.proxmox.com
> Subject: Re: [pve-devel] pve-storage : volume_lock && volume_unlock
>
> >>It would be cool if we have these git repos public containing new
> >>fe
> Cc: pve-devel@pve.proxmox.com; Stefan Priebe - Profihost AG
> Subject: Re: [pve-devel] pve-storage : volume_lock && volume_unlock
>
> >> Why (beside beeing 'cool')?
>
> I think Stefan want to test without manual patching.
Then it would make sense for
Am 03.12.2012 17:06, schrieb Dietmar Maurer:
Cc: pve-devel@pve.proxmox.com; Stefan Priebe - Profihost AG
Subject: Re: [pve-devel] pve-storage : volume_lock && volume_unlock
Why (beside beeing 'cool')?
I think Stefan want to test without manual patching.
Then it woul
> The idea is to have a repo where we can track all patches. Right now
> someone sends a patch to the mailinglist. Some of them might not be
> included directly. And then after some month it might get lost.
The idea is to get all those ideas into the main repository asap.
I am currently just a li
10 matches
Mail list logo
