incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcus Sorensen <>
Subject Re: 4.2 storage plug-in changes and CHAP
Date Tue, 26 Feb 2013 03:22:37 GMT
Should be fine, it would be up to the person writing the storage plugin to
define the parameters for that storage.
On Feb 25, 2013 8:19 PM, "Mike Tutkowski" <>

> Hi,
> I know Edison has been hard at work on the storage_refactor branch.  I was
> wondering, it looks like CloudStack does not support CHAP directly today.
>  By "directly," I mean even with, say, XenServer and an iSCSI target, you
> cannot enter CHAP credentials via the GUI or API.  If you need to use CHAP,
> you must set up your config from the hypervisor and then come into
> CloudStack and create your Primary Storage based on that pre-existent
> storage config.
> Edison's changes should allow Primary Storage to be based on a plug-in
> rather than a pre-existent storage config.  That's awesome and very helpful
> for my company.  What I would like to know, though, is if CHAP will be
> supported in this 4.2 storage plug-in environment.  My company's iSCSI
> targets all require CHAP credentials to access them.
> Thanks!
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e:
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<>
> *™*

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