From: Andy Grover <agrover@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Tony Asleson <tasleson@redhat.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: Thu, 26 Jan 2012 12:53:16 -0800 [thread overview]
Message-ID: <4F21BD3C.8050809@redhat.com> (raw)
In-Reply-To: <20120125174411.GB12620@infradead.org>
On 01/25/2012 09:44 AM, Christoph Hellwig wrote:
> There's another project which is creating a very ad-hoc storage
> management abstraction, the nova-volume code in openstack. Right now
> it supports iSCSI with a few vendor-specific extensions for management,
> RBD and sheepdog, but it looks like the numbers of vendors that want
> to be supported is growing.
>
> See https://github.com/openstack/nova/blob/master/nova/volume/driver.py
> and other files in that directory for the little bits that exist at the
> moment.
<two minutes prior>
On 01/25/2012 09:42 AM, Christoph Hellwig wrote:
> 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.
Nova is wrapping cmdline tools, and all the vendors interested so far
are foss/cloudy.
This definitely shows others see a need for an API, but if we really
want big storage vendor buy-in, then a better (C?/sockets?) API and
working with non-foss code seems key.
Also, Nova code executes on the target machine, whereas libstoragemgmt
is running on the mgmt node and the plugins are responsible for
communication with the target node. (just wanted to point out another
difference.)
-- Andy
next prev parent reply other threads:[~2012-01-26 20:53 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
2012-01-25 17:44 ` Christoph Hellwig
2012-01-26 20:53 ` Andy Grover [this message]
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=4F21BD3C.8050809@redhat.com \
--to=agrover@redhat.com \
--cc=hch@infradead.org \
--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).