Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Fri, 10 Jul 2015 15:05:11 +0000 (UTC)
From: "Daan Hoogland (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12687524.1389042237000.155433.1436540711741@Atlassian.JIRA>
In-Reply-To: <JIRA.12687524.1389042237000@Atlassian.JIRA>
References: <JIRA.12687524.1389042237000@Atlassian.JIRA>
 <JIRA.12687524.1389042237318@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-5807) Problem with shared datastore in
 VMware cluster with only one host
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daan Hoogland updated CLOUDSTACK-5807:
--------------------------------------
    Fix Version/s:     (was: 4.4.4)
                   Future

> Problem with shared datastore in VMware cluster with only one host
> ------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5807
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5807
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>    Affects Versions: 4.3.0
>         Environment: ESX 5.1
>            Reporter: Mike Tutkowski
>            Assignee: Likitha Shetty
>             Fix For: Future
>
>
> I created a volume on a SAN and connected my one and only ESX host in the cluster to it via CHAP. The iSCSI target was detected and I was able to create a datastore with it (manually through vSphere Client).
> The problem is that the VMware server resource detects this new datastore and automatically introduces it to CloudStack as host-based primary storage.
> This is a problem because it should really be cluster-based primary storage.
> If I were to add another ESX host to this cluster, I don't think it could access this primary storage as it is currently configured in CloudStack.
> The logic to detect if a datastore on an ESX host is local must be somewhat flawed.
> I believe if I had two or more hosts in my cluster and performed this datastore operation that it would not have detected this as host-based primary storage and I would have been able to manually add the datastore to CloudStack as cluster-based primary storage.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)