From: Hannes Reinecke <hare@suse.de>
To: tasleson@redhat.com
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
lsf-pc@lists.linux-foundation.org, linux-scsi@vger.kernel.org
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] [ATTEND] Storage management (API & Library)
Date: Wed, 25 Jan 2012 14:09:35 +0100 [thread overview]
Message-ID: <4F1FFF0F.1030007@suse.de> (raw)
In-Reply-To: <4F1D8913.1060709@redhat.com>
On 01/23/2012 05:21 PM, Tony Asleson wrote:
> On 01/21/2012 08:57 AM, James Bottomley wrote:
[ .. ]
>> The second might be what would it take to get vendors interested in
>> doing the array plugin glue.
>
> By providing:
> * Permissive license (LGPL)
> * Easy to use out of process plug-in support to allow proprietary
> plug-ins (IPC is abstracted)
> * Language agnostic plug-in support (initial support is C and python)
>
> We are hoping we can get hardware vendors interested in providing their
> own plug-ins. If anyone has additional ideas, we would certainly like
> to discuss them.
>
The various hardware vendors already have the means of managing their
arrays, in most cases also providing a CLI.
I would be hoping we could draft the API support such that we can
use the existing tools, without the need of special plug-ins.
Cheers,
Hannes
next prev parent reply other threads:[~2012-01-25 13:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 17:50 [LSF/MM TOPIC] [ATTEND] Storage management (API & Library) Tony Asleson
2012-01-20 23:28 ` [Lsf-pc] " 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 [this message]
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=4F1FFF0F.1030007@suse.de \
--to=hare@suse.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=tasleson@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 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.