Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of mohammad.adnan.ashraf@gmail.com
 designates 209.85.217.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CD1DEBCA.411FE%chiradeep.vittal@citrix.com>
References: 
 <CAD3_Sqg26icc0=Vskg9SSbWFDFeByw3yBU7LrJv5twfUi6XYAw@mail.gmail.com>
	<CD1DEBCA.411FE%chiradeep.vittal@citrix.com>
Date: Thu, 17 Jan 2013 23:16:12 -0600
Message-ID: 
 <CAD3_SqiesvhL-Fn1ZphSUi-2uk0Csmv_9TTS8OPnynnJoPXbZA@mail.gmail.com>
Subject: Re: JVM level cluster deployments
From: Adnan Ashraf <mohammad.adnan.ashraf@gmail.com>
To: cloudstack-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=e89a8f22c4afbd2c6b04d38935e9

--e89a8f22c4afbd2c6b04d38935e9
Content-Type: text/plain; charset=ISO-8859-1

Thanks for the feedback. so how does CloudStack provide HA/failover
guarantees? (not just the apache CloudStack but also the Citrix enterprise
CloudPlatform and cloudPortal/CPBM)?

A service provider using CloudStack would expect nothing breaks from two
angle: user's perspective and back-end provisioning services. During
provisioning of a VPC (which has many atomic steps) or in the middle of VM
creation process, the application dies (for whatever reason). This case
could easily result in half-baked (bad data) situation and abandoned
workflows loosing the provisioning process.

What workarounds or maybe persistent state based retries or logic is in
place for this situation?

Adnan


On Thu, Jan 17, 2013 at 7:56 PM, Chiradeep Vittal <
Chiradeep.Vittal@citrix.com> wrote:

> As far as I know no one deploys in this manner.
>
> On 1/17/13 6:30 AM, "Adnan Ashraf" <mohammad.adnan.ashraf@gmail.com>
> wrote:
>
> >Hi,
> >
> >I would appreciate if anyone can provide feedback on following questions:
> >
> >Roughly what is the number of cloudStack deployments that are in JVM
> >(tomcat or other server) cluster mode where all session objects, http
> >sessions, beans etc are seamlessly failed over to the other node in case
> >one of the node in the cluster deployment goes out of service and the user
> >sessions carry as if nothing happened in the background.
> >
> >What percent of customers choose not to deploy cloudstack in a cluster
> >mode
> >and why?
> >
> >What is the largest known cluster size in deployment today?
> >
> >thanks
> >
> >regards,
> >Adnan
>
>

--e89a8f22c4afbd2c6b04d38935e9--