From: Andy Grover <agrover@redhat.com>
To: lvm-devel@redhat.com
Subject: master - python-lvm: Make second lv.snapshot() argument optional
Date: Sat, 15 Dec 2012 18:27:01 -0800 [thread overview]
Message-ID: <50CD3175.5070803@redhat.com> (raw)
In-Reply-To: <50CCECF7.8000809@redhat.com>
On 12/15/2012 01:34 PM, Zdenek Kabelac wrote:
> Dne 14.12.2012 23:11, Andy Grover napsal(a):
>> If no size is given, size defaults to 0, which in lvm_lv_snapshot will
>> allocate extents equal to the original LV be allocated for the new
>> snapshot.
>>
>
>
> Possibly not the ideal solution here.
>
> 1) we have some clash with command line 'API'
> user creates snapshot of thin volume
> - without giving size he get thin volume snaphost.
> lvcreate -s
> - with size specified he gets 'old' snapshot
> (snapshot outside of the pool)
> lvcreate -s -l|-L
Makes sense. So should we do the same for the Python API -- size = None
-> thin snap, size = >=0 -> 'old' snap with the given size? OR might we
even be OK with just supporting 'new' snaps, and get rid of the size
parameter altogether?
Regards -- Andy
next prev parent reply other threads:[~2012-12-16 2:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 22:11 master - python-lvm: Make second lv.snapshot() argument optional Andy Grover
2012-12-15 21:34 ` Zdenek Kabelac
2012-12-16 2:27 ` Andy Grover [this message]
2012-12-16 18:58 ` Zdenek Kabelac
2012-12-17 14:51 ` Tony Asleson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50CD3175.5070803@redhat.com \
--to=agrover@redhat.com \
--cc=lvm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.