From: Tony Asleson <tasleson@redhat.com>
To: lsf-pc@lists.linux-foundation.org, linux-scsi@vger.kernel.org
Subject: [LSF/MM TOPIC] [ATTEND] Storage management (API & Library)
Date: Fri, 20 Jan 2012 11:50:57 -0600 [thread overview]
Message-ID: <4F19A981.4080502@redhat.com> (raw)
I would like to give a brief background on the storage management API
and library that I have been working on** and discuss the design and
implementation challenges that I have encountered thus far.
Most notable is the same topic Shyam Iyer brought up about proprietary
plug-in support (http://marc.info/?l=linux-scsi&m=132454179114038&w=2).
This very feature has influenced libStorageMgmt heavily and has raised a
number of discussions on design and licensing.
Discussion topics
* Scope (What a storage library should/should not do)
* Role (library position in management stack)
* Features (specific: must have to would be nice)
* Usage scenarios which highlight needed features
* Licensing (most appropriate open source license)
* Proprietary plug-in support
** http://sourceforge.net/apps/trac/libstoragemgmt
Regards,
Tony Asleson
next reply other threads:[~2012-01-20 17:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 17:50 Tony Asleson [this message]
2012-01-20 23:28 ` [Lsf-pc] [LSF/MM TOPIC] [ATTEND] Storage management (API & Library) Dan Williams
2012-01-23 14:47 ` Tony Asleson
2012-01-21 14:57 ` James Bottomley
2012-01-23 16:21 ` Tony Asleson
2012-01-24 16:52 ` James Bottomley
2012-01-24 18:11 ` Ric Wheeler
2012-01-24 18:44 ` James Bottomley
2012-01-25 13:09 ` Hannes Reinecke
2012-01-25 17:42 ` Christoph Hellwig
2012-01-25 17:44 ` Christoph Hellwig
2012-01-26 20:53 ` Andy Grover
2012-01-26 20:56 ` Christoph Hellwig
2012-01-26 21:12 ` FUJITA Tomonori
2012-01-31 16:38 ` Christoph Hellwig
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=4F19A981.4080502@redhat.com \
--to=tasleson@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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).