From: Tom Coughlan <coughlan@redhat.com>
To: Hannes Reinecke <hare@suse.de>, tasleson@redhat.com
Cc: Shyam_Iyer@Dell.com, vgoyal@redhat.com, rwheeler@redhat.com,
linux-fsdevel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [LSF/MM TOPIC] linux servers as a storage server - what's missing?
Date: Mon, 09 Jan 2012 07:59:45 -0500 [thread overview]
Message-ID: <1326113987.2580.8.camel@localhost.localdomain> (raw)
In-Reply-To: <4F0ADB0A.9020707@suse.de>
On Mon, 2012-01-09 at 13:18 +0100, Hannes Reinecke wrote:
> On 12/22/2011 09:54 PM, Shyam_Iyer@Dell.com wrote:
> >
> >
> >> -----Original Message-----
> >> From: linux-scsi-owner@vger.kernel.org [mailto:linux-scsi-
> >> owner@vger.kernel.org] On Behalf Of Vivek Goyal
> >> Sent: Thursday, December 22, 2011 10:59 AM
> >> To: Iyer, Shyam
> >> Cc: rwheeler@redhat.com; linux-fsdevel@vger.kernel.org; linux-
> >> scsi@vger.kernel.org
> >> Subject: Re: [LSF/MM TOPIC] linux servers as a storage server - what's
> >> missing?
> >>
> >> On Thu, Dec 22, 2011 at 01:44:16PM +0530, Shyam_Iyer@Dell.com wrote:
> >>
> >> [..]
> >>
> >>> Simple asks -
> >>> 1) Provide a consistent storage and fs management library that
> >> discourages folks to write their own usespace storage library. Include
> >> things like fs formatting(fs profiles), transport configuration(eg:
> >> iscsiadm as a library), thin provisioning watermarks, cluster
> >> management, apis for cgroups etc.
> >> ^^^^^^^^^^^^^^^^
> >> For cgroups, we have libcgroup library. Not many people like to use it
> >> though as cgroup is exported as a filesystem and they prefer to use
> >> normal
> >> libc api to traverse and configure cgroups (Instead of going through
> >> another library). Some examples include libvrit, systemd.
> >>
> >> Thanks
> >> Vivek
> >
> > Well honestly I think that is a libvirt/systemd issue and libvirt also
> > invokes things like iscsiadm, dcb etc as a binary :-/
> >
> > Some one could always use qemu command lines to invoke KVM/XEN but
> > libvirt has saved me one too many days in doing a quick operation
> > without wondering about a qemu commandline.
> >
> > I am also asking for ideas on how to avoid this fragmentation because
> > just like libvirt others are also encouraged to do their own libc
> thing
> > in the absence of a common storage management framework..
> >
> > Does the standard interface for linux end at the user/kernel boundary
> > or the user/libc boundary? If so I feel we would continue to lag
> behind
> > other OSes in features because of the model.
> >
> StorageAPI _again_.
>
> I was under the impression RH had someone working on it.
Yes, Red Hat does. Tony Asleson. libStorageMgmt:
http://sourceforge.net/apps/trac/libstoragemgmt
The current focus is on managing external storage (SMI-S, etc.). This
focus can be expanded over time. Contributions welcome.
> (Actually I was trying to give it a go, but then got buried under
> customer escalations).
>
> So yes, we know there is a shortcoming.
> And yes, we should improve things.
>
> But I feel another discussion about this will only give us more
> insight, but not moving things forward.
>
> What about having a separate session at the storage summit (or even
> at the collab summit) to hammer out the requirements here?
That would be fine, although as you say, we need more than talk.
Tom
next prev parent reply other threads:[~2012-01-09 12:59 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 15:59 [LSF/MM TOPIC] linux servers as a storage server - what's missing? Ric Wheeler
2011-12-22 8:14 ` Shyam_Iyer
2011-12-22 15:58 ` Vivek Goyal
2011-12-22 20:54 ` Shyam_Iyer
2011-12-23 3:06 ` Vivek Goyal
2011-12-23 4:35 ` Shyam_Iyer
2012-01-09 12:18 ` Hannes Reinecke
2012-01-09 12:59 ` Tom Coughlan [this message]
2012-01-10 6:53 ` Ric Wheeler
2012-01-20 8:55 ` Hannes Reinecke
2012-01-19 16:17 ` [LSF/MM TOPIC] linux servers as a storage server - what'smissing? Loke, Chetan
2012-01-19 16:19 ` Ric Wheeler
2012-01-19 16:26 ` Loke, Chetan
2012-01-19 16:29 ` Ric Wheeler
2012-01-19 17:32 ` Loke, Chetan
2012-01-19 17:44 ` Ric Wheeler
2012-01-19 21:30 ` Loke, Chetan
2012-01-19 21:39 ` Ric Wheeler
2012-01-24 17:05 ` Loke, Chetan
2012-01-24 18:13 ` Ric Wheeler
2012-01-26 22:24 ` Dave Chinner
2012-01-26 22:29 ` Ric Wheeler
2012-01-03 19:26 ` [LSF/MM TOPIC][ATTEND] linux servers as a storage server - what's missing? Jeff Layton
2012-01-03 19:32 ` Chuck Lever
2012-01-17 21:16 ` J. Bruce Fields
2012-01-17 21:25 ` Chuck Lever
2012-01-24 21:36 ` J. Bruce Fields
2012-01-24 23:13 ` Ric Wheeler
2012-01-25 19:05 ` Christopher R. Hertel
2012-01-25 20:25 ` Christopher R. Hertel
2012-01-25 21:56 ` Roland Dreier
2012-01-25 22:09 ` Christopher R. Hertel
2012-01-26 21:52 ` Andy Grover
2012-01-26 11:15 ` Bart Van Assche
2012-01-18 17:00 ` [LSF/MM TOPIC] " Roland Dreier
2012-01-18 17:51 ` Ric Wheeler
2012-01-18 18:46 ` Roland Dreier
2012-01-18 18:51 ` Bart Van Assche
2012-01-18 19:00 ` Roland Dreier
2012-01-19 8:16 ` Rolf Eike Beer
2012-01-19 17:50 ` Loke, Chetan
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=1326113987.2580.8.camel@localhost.localdomain \
--to=coughlan@redhat.com \
--cc=Shyam_Iyer@Dell.com \
--cc=hare@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rwheeler@redhat.com \
--cc=tasleson@redhat.com \
--cc=vgoyal@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).