incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Tutkowski <mike.tutkow...@solidfire.com>
Subject Re: Where to supply CHAP info when using iSCSI in CloudStack
Date Thu, 21 Feb 2013 19:14:46 GMT
>From this mail archive URL, it appears CHAP cannot be used from the GUI:

http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201206.mbox/%3CCAAvCx3hhB+p6tNq1tAAQ_ej3d7e913Ss1maBwzYH=tFLYqFzoA@mail.gmail.com%3E

I wonder if anyone knows if CHAP can be used from the CloudStack API and
the GUI just doesn't support it?

Thanks!


On Wed, Feb 20, 2013 at 3:26 PM, Mike Tutkowski <
mike.tutkowski@solidfire.com> wrote:

> Hi everyone,
>
> I have been able to successfully set up iSCSI Primary Storage in
> CloudStack for a XenServer cluster that does not use CHAP info to access
> the volume (LUN).  I am now trying to do the same with a volume that does
> require CHAP info.
>
> I don't see anywhere in the GUI to provide this.  Is this supported in the
> GUI and API (in CloudStack in general)?
>
> The url field I provide to the createStoragePool API command is the
> following:
>
> iscsi://10.5.1.50/iqn.2010-01.com.solidfire:e1cx.csvolume1.24/0
>
>
> Not sure if I would add on to this path to supply CHAP info?
>
>
> Thanks!
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play>
> *™*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message