<div dir="ltr"><div style="font-family:arial,sans-serif;font-size:13px"><b>My short list of requirement is:<br></b></div><div style="font-family:arial,sans-serif;font-size:13px">- Legacy Stateful Application on my VMs</div>
<div style="font-family:arial,sans-serif;font-size:13px">- No time to change the application code base(to convert them as stateless apps which are work better on openstack)</div><div style="font-family:arial,sans-serif;font-size:13px">
- Completely opensource solution(HA in openstack need "stratus allways on cloud" solution or something like that, which are not opensource)</div><div style="font-family:arial,sans-serif;font-size:13px">- High amount of code stability</div>
<div style="font-family:arial,sans-serif;font-size:13px">- Enterprise proven solution</div><div style="font-family:arial,sans-serif;font-size:13px">- Better siute for private cloud instead of public</div><div style="font-family:arial,sans-serif;font-size:13px">
- High amount of HA, fault tolerance, resiliency in underlying layers</div><div style="font-family:arial,sans-serif;font-size:13px"><b>By the aim of these requirement description, what about the decision between OpenStack & CloudStack?</b></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 5, 2014 at 10:29 PM, hossein zabolzadeh <span dir="ltr"><<a href="mailto:zabolzadeh@gmail.com" target="_blank">zabolzadeh@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks Paul for your responce.<div>But, My case was not a few server in small server room. I have been talked about a huge datacenter with more than 1000 server, SAN storage devices, complex physical networks and so on, with high amount of change in IT needs.</div>
<div>Yes you right. Sorry for my miss-typping. My mean was "I don't want <b>public</b> cloud". In other words "I don't want to deliver <b>public</b> cloud". I want to use private cloud on my datacenter. But becasue of my in-ability to change my legacy application codebase, the datacenter virtualization is better matched to my requirements, instead of infrastructure provisioning cloud solution(e.g. OpenStack), which focused more on new future applications(stateless apps). I need high availability, fault-tolerance, resiliancy and so on, all in my infrastrructure level, not on the application itself. And now, what is the best matched one for me to select???</div>
<div>Thanks in advance.</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 5, 2014 at 10:13 PM, CARVER, PAUL <span dir="ltr"><<a href="mailto:pc2929@att.com" target="_blank">pc2929@att.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>hossein zabolzadeh wrote:<br>
>I want to fully virtualize my datacenter. I don't want cloud. I don't want to deliver<br>
>public cloud. I have several legacy appliacation that I want to run all of them on<br>
>virtualized environment. I want to leverage the virtualization technology to improve<br>
>my datacenter consolidation, ease of meintenace, ease of management with<br>
>increase in capacity.<br>
<br>
<br>
</div>If you don’t want cloud and don’t need cloud then don’t look at CloudStack or OpenStack. There’s no need to be buzzword compliant. Just use ESXi (with or without vCenter), or use KVM or Xen directly. After you’ve virtualized your infrastructure either one of two things will happen:<br>
<br>
1) You’ll realize that you really did want cloud, but now you’ll understand why and you won’t just be doing it for buzzword’s sake<br>
<br>
or<br>
<br>
2) You’ll be perfectly happy because you were actually right that all you wanted was to virtualize a few servers. You’re done and you didn’t make yourself miserable by implementing something you really didn’t want or need<br>
<br>
Not everybody needs a cloud platform. Certainly not everybody needs to build their own cloud platform internal to their company. If you’re IT needs are big enough and rapidly changing enough to actually need cloud then you wouldn’t be posting to an OpenStack mailing list that “I don’t want cloud” unless of course you don’t actually know your IT needs well enough. And if you don’t know your IT needs well enough to understand on a technical basis why you need OpenStack (or CloudStack or vCloud or etc) then you need to go back and figure out your own IT needs before proceeding further.<br>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>