Open Stack

At first thanks for all of your answers.
Lets talk more about my concern. My main issue is availability of two
seperated cloud paradigm namely 1) DC virtualization and Infrastructure
provisioning(According to
http://opennebula.org/eucalyptus-cloudstack-openstack-and-opennebula-a-tale-of-two-cloud-models/
).
Cloud specialists make a connection between old(legacy) applications and DC
virtualization(Like Vcloud and CloudStack) in one side, new application and
infrastructure provisioning cloud(Like AWS and OpenStack) on the other
side. They said that, to leverage the infrastructure when running legacy
applications, you need to use DC virtualization solutions, and to run new
applications(Cloud-Ready Apps), its best to use infrastructure provisioning
clouds. I don't know really why they said things like this?
*Glad if some one explain more about these two types of different cloud
paradigms.*
I have 10 legacy applications that holds my business, according to the
above reference, CloudStack is the best matched CMP to my case. But I hear
everywhere about OpenStack, and its rapid improvement, large community and
so on.... So, I don't know what will be happened if I run legacy
applications on the OpenStack(Infrastructure Provisioning Cloud Solution)?
In other words, what will I miss if I select openStack?
Thanks in advance.

M.H Zabolzadeh.


On Thu, May 29, 2014 at 11:41 PM, Adam Lawson <alawson at aqorn.com> wrote:

> 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.
>
> 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.
>
>
> *Adam Lawson*
> AQORN, Inc.
> 427 North Tatnall Street
> Ste. 58461
> Wilmington, Delaware 19801-2230
> Toll-free: (844) 4-AQORN-NOW
> Direct: +1 (302) 268-6914
>
>
>
> On Thu, May 29, 2014 at 11:52 AM, Tim Bell <Tim.Bell at cern.ch> wrote:
>
>>
>> For those interested in CloudStack's functionality in this area, they
>> provide restart of hypervisors and VMs as described in
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/High+Availability+Developer's+Guide
>>
>> Tim
>>
>> > -----Original Message-----
>> > From: Amrith Kumar [mailto:amrith at tesora.com]
>> > Sent: 29 May 2014 20:39
>> > To: Jay Pipes; openstack at lists.openstack.org; hossein zabolzadeh
>> > Subject: Re: [Openstack] Legacy Application Run on top of OpenStack
>> >
>> > Hi Hossein,
>> >
>> > You can get HA on OpenStack for things like storage just as you would
>> in your
>> > existing data center. Unless you are running some highly available or
>> fault
>> > tolerant hardware in your data center, I believe you will see comparable
>> > reliability in an OpenStack cloud, at least with respect to computing.
>> >
>> > I am interpreting Jay's answer below to say that you can build
>> additional
>> > availability through scale-out paradigms but that may be inconsistent
>> with your
>> > desire to make no change to your applications.
>> >
>> > If what you are looking for is a fault tolerant offering in the
>> OpenStack cloud,
>> > maybe you want to look at something like Stratus (I'm sure someone from
>> > Stratus can respond and tell you more).
>> >
>> > -amrith
>> >
>> > | -----Original Message-----
>> > | From: Jay Pipes [mailto:jaypipes at gmail.com]
>> > | Sent: Thursday, May 29, 2014 1:56 PM
>> > | To: openstack at lists.openstack.org
>> > | Subject: Re: [Openstack] Legacy Application Run on top of OpenStack
>> > |
>> > | On 05/29/2014 05:12 AM, hossein zabolzadeh wrote:
>> > | > Hi there.
>> > | > I am baffling between Cloudstack and Openstack to select. My
>> > | > Datacenter has more than 10 legacy application, which need to be run
>> > | > on top of the best matched CMP(Cloud Management Platform). I am
>> > | > search a lot and I select openStack and CloudStack at the end. But,
>> > | > I can not make a final decision about these two CMPs. I don't want
>> > | > to make any change to my legacy application codebase. So, my exact
>> > concern is:
>> > | > "How legacy applications can be run on OpenStack without any HA and
>> > | > resiliancy problems?" As we know cloud-ready applications are fully
>> > | > awared from underlying infrastucture, but what about non-cloud-ready
>> > | > apps(Legacy Applications)?
>> > | > CloudStack is DC virtualization cloud solution(Vcloud Like Cloud
>> > | > Solution) that handle all of the HA and resiliancy in the
>> > | > infrastructure layer, but the paradigm in openStack is
>> > | > infrastructure provisioning(AWS like cloud), which the HA problems
>> > | > shoud be addressed
>> > | in application layer.
>> > | > So at general, how openStack support legacy applications to run
>> > | > without any HA problems?
>> > | > Thanks in advance.
>> > |
>> > | Hi Hossein,
>> > |
>> > | The short answer is that the idea behind "legacy" applications -- i.e.
>> > | that applications should rely on infrastructure to handle reliability
>> > | of the application in a scale-up-only manner -- is not something that
>> > | the OpenStack platform really encourages.
>> > |
>> > | We encourage scale-out behaviour and application development
>> > | methodologies that give the scaling, reliability, and resiliency
>> > | control to the application deployer to implement as they see fits
>> best their
>> > application.
>> > | It's not a one-size-fits-all world, and as such, there are plenty of
>> > | application architectures and deployment methodologies that are
>> > | supported in cloudy environments; OpenStack doesn't pick or choose
>> one over
>> > another.
>> > |
>> > | Best,
>> > | -jay
>> > |
>> > | _______________________________________________
>> > | Mailing list: http://lists.openstack.org/cgi-
>> > | bin/mailman/listinfo/openstack
>> > | Post to     : openstack at lists.openstack.org
>> > | Unsubscribe : http://lists.openstack.org/cgi-
>> > | bin/mailman/listinfo/openstack
>>
>> _______________________________________________
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to     : openstack at lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140530/c05d9f7e/attachment.html>