linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Hannes Reinecke <hare@suse.de>
Cc: tasleson@redhat.com,
	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 12:42:24 -0500	[thread overview]
Message-ID: <20120125174224.GA12620@infradead.org> (raw)
In-Reply-To: <4F1FFF0F.1030007@suse.de>

On Wed, Jan 25, 2012 at 02:09:35PM +0100, Hannes Reinecke wrote:
> 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.

Wrapping tools from libraries is more of a last resort than a proper
solution.  But if we can't get better APIs that's probably what we
will have to resort to if vendors don't cooperate.


  reply	other threads:[~2012-01-25 17:42 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
2012-01-25 17:42       ` Christoph Hellwig [this message]
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=20120125174224.GA12620@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=hare@suse.de \
    --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 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).