From: Mike Christie <michaelc@cs.wisc.edu>
To: lsf10-pc@lists.linuxfoundation.org, linux-scsi@vger.kernel.org
Subject: Re: [LSF/VM TOPIC] Generic SAN Management via Oracle VM Storage Connect Plugin.
Date: Wed, 31 Mar 2010 20:52:32 -0500 [thread overview]
Message-ID: <4BB3FC60.1050405@cs.wisc.edu> (raw)
In-Reply-To: <20100401010539.GF28680@mail.oracle.com>
On 03/31/2010 08:05 PM, Joel Becker wrote:
> [ I was asked to Cc: linux-scsi, so here it is ]
>
>
> [Topic]
> Generic SAN Management via Oracle VM Storage Connect Plugin.
>
> [Abstract]
> Managing storage in the SAN often requires using a different tool for
> each vendor in the environment. Oracle has defined a plugin interface
> for SAN management, the (sorry about the mouthful) Oracle VM Storage
> Connect Plugin. The important part is that many of our storage partners
> have agreed to not only help, but actively author plugins for their
> storage hardware.
>
> While initiated for the Oracle VM product, I've written a standalone
> application that uses the plugin, giving a unified view of storage that
> can be managed from one place. The program will be open source, of
> course. I'm looking for input from storage folks at LFS on what
> I can do to make this even more useful to general SAN management.
>
Sounds interesting. I have been trying to just get initiator tools and
libs that work with all hbas. We have a common iscsi tool for iscsi
initiators and was hoping fcoeadmin could be made more generic to work
for all fcoe and fc drivers (there is work to make a the linux hbaapi
lib work for all drivers too).
Is your interface based on anything like SMI-S, or something new? It
will work on the initiator and targets, right? Will it work on switches?
next prev parent reply other threads:[~2010-04-01 1:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 1:05 [LSF/VM TOPIC] Generic SAN Management via Oracle VM Storage Connect Plugin Joel Becker
2010-04-01 1:52 ` Mike Christie [this message]
2010-05-13 21:56 ` Joel Becker
2010-06-02 1:18 ` FUJITA Tomonori
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=4BB3FC60.1050405@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf10-pc@lists.linuxfoundation.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.