From: Chris Murphy <lists@colorremedies.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: Moviuro <moviuro@gmail.com>, Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-progs and btrfs(8) inconsistencies
Date: Sat, 6 Feb 2016 14:35:23 -0700 [thread overview]
Message-ID: <CAJCQCtSKxYNhJVfixWbM8mgcGF4XL=TtEuZ6=Dx_n2F+HRWUMw@mail.gmail.com> (raw)
In-Reply-To: <56B412FC.8060007@oracle.com>
On Thu, Feb 4, 2016 at 8:11 PM, Anand Jain <anand.jain@oracle.com> wrote:
>
>
> If you look critically we have been using UI/CLI as API,
> IMO these two class of interfaces be distinct clearly.
>
> Btrfs needs library functions/APIs which is callable in
> popular scripting language like python.
I'm not sure what this is using to get btrfs info, it's written in c.
https://github.com/storaged-project/storaged/tree/master/modules/btrfs
This is python and has a btrfs backed that depends on user space
tools, the comments pretty clearly express the challenges with using
user space tools as a primary means to interface with Btrfs volumes.
http://sourceforge.net/p/storagemanager/code/ci/devel/tree/ssmlib/backends/btrfs.py
Red Hat's installer, Anaconda, has split out its storage configuration
module into python-blivet to enable a bunch of storage work to be done
in Python, including a lot of Btrfs functionality. Some of this just
got too complicated I guess for blivet, and has been split out into
libblockdev, which includes plugin apis, and there happens to be one
for Btrfs. But I have no idea where it goes from there.
https://github.com/rhinstaller/libblockdev
https://github.com/rhinstaller/libblockdev/blob/master/src/lib/plugin_apis/btrfs.api
So yeah, people are trying to do this.
--
Chris Murphy
next prev parent reply other threads:[~2016-02-06 21:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 21:54 btrfs-progs and btrfs(8) inconsistencies Moviuro
2016-02-04 1:33 ` Qu Wenruo
2016-02-04 8:57 ` Moviuro
2016-02-04 9:15 ` Qu Wenruo
2016-02-04 10:14 ` Martin Steigerwald
2016-02-04 12:04 ` Moviuro
2016-02-04 12:53 ` Austin S. Hemmelgarn
2016-02-04 19:40 ` Chris Murphy
2016-02-04 20:19 ` Austin S. Hemmelgarn
2016-02-04 20:40 ` Moviuro
2016-02-05 13:04 ` Austin S. Hemmelgarn
2016-02-04 17:17 ` Goffredo Baroncelli
2016-02-04 19:48 ` Hugo Mills
2016-02-04 20:10 ` Chris Murphy
2016-02-04 18:22 ` Chris Murphy
2016-02-05 3:11 ` Anand Jain
2016-02-05 12:59 ` Austin S. Hemmelgarn
2016-02-06 21:35 ` Chris Murphy [this message]
2016-02-07 10:07 ` Qu Wenruo
2016-02-07 20:26 ` Goffredo Baroncelli
2016-03-08 16:02 ` David Sterba
2016-03-09 10:02 ` Moviuro
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='CAJCQCtSKxYNhJVfixWbM8mgcGF4XL=TtEuZ6=Dx_n2F+HRWUMw@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=moviuro@gmail.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.