<div dir="ltr">Hossein, what are your requirements for these legacy apps? To be able to run or do they require some specific HA components? You can easily run your apps in a VM if they allow that (some simply don't in whicu case your only option is HW) and you can do that with either Cloudstack or Openstack. But what I personally like about Openstack is its modular architecture where you can implement things like a LB between multiple VM's without reaching to your network folks to update the F5 as you would with a non-cloudy ecosystem.<div>
<br></div><div>Is your immediate requirement straight-up 'service availability' or to be highly available? I think Openstack's modular design suits hybrid cloud approaches better than other orchestrators by virtue of its design but that's me talking.</div>
</div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div><font><div style="font-family:arial;font-size:small"><b><i><br>Adam Lawson</i></b></div><div><font><font color="#666666" size="1"><div style="font-family:arial;font-size:small">
AQORN, Inc.</div><div style="font-family:arial;font-size:small">427 North Tatnall Street</div><div style="font-family:arial;font-size:small">Ste. 58461</div><div style="font-family:arial;font-size:small">Wilmington, Delaware 19801-2230</div>
<div style="font-family:arial;font-size:small">Toll-free: (844) 4-AQORN-NOW</div><div style="font-family:arial;font-size:small">Direct: +1 (302) 268-6914</div></font></font></div></font></div><div style="font-family:arial;font-size:small">
<img src="http://www.aqorn.com/images/logo.png" width="96" height="39"><br></div></div></div>
<br><br><div class="gmail_quote">On Thu, May 29, 2014 at 11:52 AM, Tim Bell <span dir="ltr"><<a href="mailto:Tim.Bell@cern.ch" target="_blank">Tim.Bell@cern.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
For those interested in CloudStack's functionality in this area, they provide restart of hypervisors and VMs as described in <a href="https://cwiki.apache.org/confluence/display/CLOUDSTACK/High+Availability+Developer's+Guide" target="_blank">https://cwiki.apache.org/confluence/display/CLOUDSTACK/High+Availability+Developer's+Guide</a><br>
<span class="HOEnZb"><font color="#888888"><br>
Tim<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
> -----Original Message-----<br>
> From: Amrith Kumar [mailto:<a href="mailto:amrith@tesora.com">amrith@tesora.com</a>]<br>
> Sent: 29 May 2014 20:39<br>
> To: Jay Pipes; <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a>; hossein zabolzadeh<br>
> Subject: Re: [Openstack] Legacy Application Run on top of OpenStack<br>
><br>
> Hi Hossein,<br>
><br>
> You can get HA on OpenStack for things like storage just as you would in your<br>
> existing data center. Unless you are running some highly available or fault<br>
> tolerant hardware in your data center, I believe you will see comparable<br>
> reliability in an OpenStack cloud, at least with respect to computing.<br>
><br>
> I am interpreting Jay's answer below to say that you can build additional<br>
> availability through scale-out paradigms but that may be inconsistent with your<br>
> desire to make no change to your applications.<br>
><br>
> If what you are looking for is a fault tolerant offering in the OpenStack cloud,<br>
> maybe you want to look at something like Stratus (I'm sure someone from<br>
> Stratus can respond and tell you more).<br>
><br>
> -amrith<br>
><br>
> | -----Original Message-----<br>
> | From: Jay Pipes [mailto:<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>]<br>
> | Sent: Thursday, May 29, 2014 1:56 PM<br>
> | To: <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
> | Subject: Re: [Openstack] Legacy Application Run on top of OpenStack<br>
> |<br>
> | On 05/29/2014 05:12 AM, hossein zabolzadeh wrote:<br>
> | > Hi there.<br>
> | > I am baffling between Cloudstack and Openstack to select. My<br>
> | > Datacenter has more than 10 legacy application, which need to be run<br>
> | > on top of the best matched CMP(Cloud Management Platform). I am<br>
> | > search a lot and I select openStack and CloudStack at the end. But,<br>
> | > I can not make a final decision about these two CMPs. I don't want<br>
> | > to make any change to my legacy application codebase. So, my exact<br>
> concern is:<br>
> | > "How legacy applications can be run on OpenStack without any HA and<br>
> | > resiliancy problems?" As we know cloud-ready applications are fully<br>
> | > awared from underlying infrastucture, but what about non-cloud-ready<br>
> | > apps(Legacy Applications)?<br>
> | > CloudStack is DC virtualization cloud solution(Vcloud Like Cloud<br>
> | > Solution) that handle all of the HA and resiliancy in the<br>
> | > infrastructure layer, but the paradigm in openStack is<br>
> | > infrastructure provisioning(AWS like cloud), which the HA problems<br>
> | > shoud be addressed<br>
> | in application layer.<br>
> | > So at general, how openStack support legacy applications to run<br>
> | > without any HA problems?<br>
> | > Thanks in advance.<br>
> |<br>
> | Hi Hossein,<br>
> |<br>
> | The short answer is that the idea behind "legacy" applications -- i.e.<br>
> | that applications should rely on infrastructure to handle reliability<br>
> | of the application in a scale-up-only manner -- is not something that<br>
> | the OpenStack platform really encourages.<br>
> |<br>
> | We encourage scale-out behaviour and application development<br>
> | methodologies that give the scaling, reliability, and resiliency<br>
> | control to the application deployer to implement as they see fits best their<br>
> application.<br>
> | It's not a one-size-fits-all world, and as such, there are plenty of<br>
> | application architectures and deployment methodologies that are<br>
> | supported in cloudy environments; OpenStack doesn't pick or choose one over<br>
> another.<br>
> |<br>
> | Best,<br>
> | -jay<br>
> |<br>
> | _______________________________________________<br>
> | Mailing list: <a href="http://lists.openstack.org/cgi-" target="_blank">http://lists.openstack.org/cgi-</a><br>
> | bin/mailman/listinfo/openstack<br>
> | Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
> | Unsubscribe : <a href="http://lists.openstack.org/cgi-" target="_blank">http://lists.openstack.org/cgi-</a><br>
> | bin/mailman/listinfo/openstack<br>
<br>
</div></div><div class="im HOEnZb">_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
</div><div class="HOEnZb"><div class="h5">Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
</div></div></blockquote></div><br></div>