From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from tasleson.csb (vpn-226-68.phx2.redhat.com [10.3.226.68]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q93EaC0t018258 for ; Wed, 3 Oct 2012 10:36:12 -0400 Message-ID: <506C4D5C.8080103@redhat.com> Date: Wed, 03 Oct 2012 09:36:12 -0500 From: Tony Asleson MIME-Version: 1.0 References: In-Reply-To: Content-Transfer-Encoding: 7bit Subject: Re: [linux-lvm] LVM2APP still under active development? Reply-To: tasleson@redhat.com, LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" To: linux-lvm@redhat.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