From: Tony Asleson <tasleson@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM2APP still under active development?
Date: Wed, 03 Oct 2012 09:36:12 -0500 [thread overview]
Message-ID: <506C4D5C.8080103@redhat.com> (raw)
In-Reply-To: <CAMwsLt6D7c6YDHFHiBufNGDtVG+_soqo1OK9Kg4pV7L1WuPhMA@mail.gmail.com>
On 10/02/2012 04:42 AM, Bram Klein Gunnewiek wrote:
> Hello,
>
> I'm developing an in-house application that needs to control LVM
> set-ups. I was looking at the lvm2app API but its missing a couple of
> features I need (snapshots, resizing logical volumes (API is defined
> but not implemented), ...). I can't find any road-map or document
> with plans for the API (only the v1 document at
> http://fedoraproject.org/wiki/LVM/liblvm ).
>
> Is the API still under active development, and are new features
> added?
The API is getting some attention. Current plan is to add feature
parity python bindings to API (patches pending) and then add features to
the API. Some of the initial planned improvements include:
- PV (create/resize/remove/enumerate & query)
- VG (activate/deactivate)
- LV (Ability to enumerate information directly without enumerating VGs
first)
- Dry run feature, the ability to do multiple changes while checking
for errors and examine the end resulting end configuration before
applying changes
The long term goal is to achieve feature parity with the command line.
> I rather use a stable API instead of wrapping around CLI commands,
> but mixing the two to use the functionality the API is missing
> doesn't seem a smart option to me.
We agree.
Regards,
Tony
prev parent reply other threads:[~2012-10-03 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 9:42 [linux-lvm] LVM2APP still under active development? Bram Klein Gunnewiek
2012-10-03 14:36 ` Tony Asleson [this message]
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=506C4D5C.8080103@redhat.com \
--to=tasleson@redhat.com \
--cc=linux-lvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).