From: Mike Christie <michaelc@cs.wisc.edu>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: qemu-devel@nongnu.org, "Michael Tokarev" <mjt@tls.msk.ru>,
"Hannes Reinecke" <hare@suse.de>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] QEMU desired libiscsi.so clashes with libiscsi.so from iscsi-initiator-utils
Date: Tue, 06 Mar 2012 20:30:51 -0600 [thread overview]
Message-ID: <4F56C85B.8070302@cs.wisc.edu> (raw)
In-Reply-To: <CAN05THQcNc83-coom5K_reatykkjoa6foqE_ahBcnMcA6JDgDQ@mail.gmail.com>
On 03/06/2012 07:51 PM, ronnie sahlberg wrote:
> Hi Mike,
>
> Thanks!
>
> That would be great if you rename it to something less generic and
> specific to libiscsi-utils.
> That means I can continue using libiscsi as the name for my
> multiplatform library.
>
> By the way, if the only user today and in the future of the library
> in libiscsi-utils is anaconda,
The only current user that I know of is anaconda, but I have been
working on making a more generic lib that others can use. I think Qlogic
was going to use it too, but I have been trying to advise them not to
since it was not upstream.
For anaconda we need to be able to find targets/disks and setup the
install on them. We want to then set things up so the OS uses those
disks and whatever driver (software iscsi or one of the offload drivers
or iser) they selected for root/boot and the other partitions.
In general, I just want to have a way to login, discover, and manage
targets and HBAs using the software iscsi or iser driver or one of the
offload cards we support. So something like IMA. I wanted to keep it
close to IMA so other vendors can use it for a plugin if needed.
If your lib can or would like to do stuff like that, I would be very
very very happy :)
next prev parent reply other threads:[~2012-03-07 2:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 13:24 [Qemu-devel] QEMU desired libiscsi.so clashes with libiscsi.so from iscsi-initiator-utils Daniel P. Berrange
2012-03-03 6:43 ` ronnie sahlberg
2012-03-03 11:15 ` Andreas Färber
2012-03-03 11:54 ` Michael Tokarev
2012-03-06 10:07 ` Daniel P. Berrange
2012-03-06 10:38 ` Michael Tokarev
2012-03-06 11:06 ` ronnie sahlberg
2012-03-06 11:15 ` Daniel P. Berrange
2012-03-06 14:10 ` Michael Tokarev
2012-03-06 12:19 ` Hannes Reinecke
2012-03-06 19:58 ` Mike Christie
2012-03-06 20:13 ` Mike Christie
2012-03-07 1:51 ` ronnie sahlberg
2012-03-07 2:30 ` Mike Christie [this message]
2012-03-06 10:02 ` Daniel P. Berrange
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=4F56C85B.8070302@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=afaerber@suse.de \
--cc=hare@suse.de \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.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).