cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-5662) XenServer can't discover iSCSI targets with different credentials
Date Sun, 05 Jan 2014 04:14:50 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862488#comment-13862488
] 

ASF subversion and git services commented on CLOUDSTACK-5662:
-------------------------------------------------------------

Commit 811b0856d512df163f29eb07e3f95d0ac80ed6fa in branch refs/heads/4.3 from [~mike-tutkowski]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=811b085 ]

CLOUDSTACK-5662: XenServer can't discover iSCSI targets with different credentials

VAGs


> XenServer can't discover iSCSI targets with different credentials
> -----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5662
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5662
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.3.0
>         Environment: XenServer 6.1
>            Reporter: Mike Tutkowski
>            Assignee: Mike Tutkowski
>             Fix For: 4.3.0
>
>
> If you discover an iSCSI target using CHAP credentials, say, x and later want to discover
another iSCSI target using CHAP credentials, says, y, the second iSCSI target cannot be discovered
because XenServer only tries to discover iSCSI targets using CHAP credentials x (which are
the first CHAP credentials XenServer encountered for the portal in question).
> This is a problem for a multi-tenant storage system and I have seen this issue when using
the SolidFire plug-in.
> The SolidFire plug-in needs to be changed to stop using CHAP with XenServer and instead
use its Volume Access Group feature (which maps host IQNs to volumes).
> This will also require changes in CloudStack itself.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message