Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-users@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of mpatton@inforelay.com
 designates 50.56.211.18 as permitted sender)
Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes
To: cloudstack-users@incubator.apache.org
Subject: Re: Storage failure in not handled well in CS
References: <506B4AA7.5040400@nfinausa.com> <506C42E5.4030101@nfinausa.com>
Date: Wed, 03 Oct 2012 11:44:23 -0400
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Matthew Patton" <mpatton@inforelay.com>
Organization: InfoRelay
Message-ID: <op.wll0n9i9mtfvvt@mpatton-pc.iad2.cloud.inforelay.net>
In-Reply-To: <506C42E5.4030101@nfinausa.com>
User-Agent: Opera Mail/11.62 (Win32)

On Wed, 03 Oct 2012 09:51:33 -0400, Nik Martin <nik.martin@nfinausa.com>  
wrote:

> Bump?  This is a serious issue that I need to get resolved.  An entire  
> cloud going down while one SAN is being repaired is a bad thing.

Don't get too upset - it's par for the course for products written by  
Citrix programmers. Citrix XenServer (the hypervisor) also has a similar,  
fatal flaw. If the first IP of a multi-IP SAN array is unreachable (eg. a  
bad port, or controller failure), it won't reconnect using any of the  
other IP. It will just mark it dead and you literally have to DELETE the  
volume object and redefine it.

The only hypervisor that isn't complete sh*t is ESX. So far I haven't  
found a cloud environment that wasn't riddled with incredibly naive  
assumptions.

-- 
Cloud Services Architect, Senior System Administrator
InfoRelay Online Systems (www.inforelay.com)