All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Asleson <tasleson@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-scsi@vger.kernel.org
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] [ATTEND] Storage management (API & Library)
Date: Mon, 23 Jan 2012 10:21:39 -0600	[thread overview]
Message-ID: <4F1D8913.1060709@redhat.com> (raw)
In-Reply-To: <1327157825.2748.5.camel@dabdike.int.hansenpartnership.com>

On 01/21/2012 08:57 AM, James Bottomley wrote:
> It's also a bit insular ... the first thing you usually ask in open
> source is what can I steal^Wborrow from other projects and how do I
> recruit others to do the work for me.

The project site is a little sparse on details about what we have looked
at and considered.  Ric Wheeler covered some of this during his
presentation in Prague, but I will place more information on the project
web site.

> The first question is probably: is there anything we can liberate
> from the Oracle storage API fisasco to help with this.

The Oracle storage connect library was evaluated and subsequently
rejected for the following reasons:

1. The Oracle storage connect library is dual licensed, GPL and a
proprietary Oracle license which allows proprietary use.  This allows
hardware vendors the ability to write proprietary plug-ins.  The design
of the library has the library user and plug-in executing in the same
address space.  Based on the information presented on plug-ins
(http://www.gnu.org/licenses/gpl-faq.html#GPLAndPlugins) this design
goes against the requirements of GPL license compliance.  Proprietary
plug-ins could be in compliance if they are implemented to execute in a
separate process.

2. At the time the Oracle storage connect library was being evaluated we
were unable to obtain a plug-in from a few different vendors.  Without
plug-ins the value of any library becomes greatly diminished.

> 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.

Regards,
Tony

  reply	other threads:[~2012-01-23 16:21 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 [this message]
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=4F1D8913.1060709@redhat.com \
    --to=tasleson@redhat.com \
    --cc=James.Bottomley@HansenPartnership.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 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.