linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@debian.org>
To: Anant Narayanan <anant@kix.in>
Cc: parted-devel@lists.alioth.debian.org, linux-lvm@redhat.com
Subject: Re: [parted-devel] Re: [linux-lvm] Proposal for the libLVM project
Date: Fri, 10 Nov 2006 10:21:48 -0200	[thread overview]
Message-ID: <87hcx7o5k3.fsf@neumann.lab.ossystems.com.br> (raw)
In-Reply-To: <20061109211804.GL30653@agk.surrey.redhat.com> (Alasdair G. Kergon's message of "Thu, 9 Nov 2006 21:18:04 +0000")

[ I've removed linux-lvm from cc list but leave parted-devel since
it still on topic]

Alasdair G Kergon <agk@redhat.com> writes:

> Thanks for getting in touch.
>
> The only library supported for external applications at present is
> liblvm2cmd and this is basically a wrapper around the command line.
> This was a deliberate decision to force people to use the only stable interface
> we have, namely the command line.

Right. Is this library being still maintained?

> The end result should be:
>
>   a new lvm library API exists which is designed to be maintainable as the
> tools develop and not cause compatibility problems or inhibit anticipated
> future developments;
>
>   the tools directory uses only the published API;
>
>   everything available in the API is available directly through the lvm
> command line - there must be no 'hidden' features;

I completely agree with you here.

>   no internal structures are exposed through the library API so we retain
> complete freedom to change internal implementations and data structures.

Indeed.

> The first job is to sketch out possible interfaces for some examples
> like that - 'create a PV', 'create/extend a VG' - based on what the tools
> do today.

Indeed. How do you wish to coordenate this? Should we propose those to
mailing list? Or should us use something like a wiki?

> Further, if there are things that parted wants that are not available
> through the command line today, then put those on the table ASAP and
> we should try to get them implemented through the command line (in parallel
> with work on designing a library).

I don't think so. On parted side we'll probably write another layer
that will be used to "connect" the libparted on external libraries. It
won't be done just for lvm but also for other filesystems like
ext[34], and other's will come later.

-- 
        O T A V I O    S A L V A D O R
---------------------------------------------
 E-mail: otavio@debian.org      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
 you the whole house."

  reply	other threads:[~2006-11-10 12:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10  8:02 [linux-lvm] Proposal for the libLVM project Anant Narayanan
2006-11-09 21:18 ` Alasdair G Kergon
2006-11-10 12:21   ` Otavio Salvador [this message]
2006-11-10 23:02     ` [parted-devel] " Alasdair G Kergon

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=87hcx7o5k3.fsf@neumann.lab.ossystems.com.br \
    --to=otavio@debian.org \
    --cc=anant@kix.in \
    --cc=linux-lvm@redhat.com \
    --cc=parted-devel@lists.alioth.debian.org \
    /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).