I'm biased, working for Piston Cloud Computing (www.pistoncloud.com). Please check out Piston, and I'd really like to hear about your experiences evaluating other cloud solutions, and what you eventually choose.
-- Noel Burton-Krahn Sr. Distributed Systems Engineer Piston Cloud Computing On Fri, Jun 6, 2014 at 1:58 AM, Erik Weber <terbol...@gmail.com> wrote: > What do you need a cmp for at all? > > What are your technical requirements? Hypervisor? Do you expect the cmp to > configure the network hardware or storage? > 6. juni 2014 08:00 skrev "hossein zabolzadeh" <zabolza...@gmail.com> > følgende: > >> >> *My short list of requirement is:* >> - Legacy Stateful Application on my VMs >> - No time to change the application code base(to convert them as >> stateless apps which are work better on openstack) >> - Completely opensource solution(HA in openstack need "stratus allways on >> cloud" solution or something like that, which are not opensource) >> - High amount of code stability >> - Enterprise proven solution >> - Better siute for private cloud instead of public >> - High amount of HA, fault tolerance, resiliency in underlying layers >> *By the aim of these requirement description, what about the decision >> between OpenStack & CloudStack?* >> >> >> On Thu, Jun 5, 2014 at 10:29 PM, hossein zabolzadeh <zabolza...@gmail.com >> > wrote: >> >>> Thanks Paul for your responce. >>> 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. >>> Yes you right. Sorry for my miss-typping. My mean was "I don't want >>> *public* cloud". In other words "I don't want to deliver *public* >>> 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??? >>> Thanks in advance. >>> >>> >>> On Thu, Jun 5, 2014 at 10:13 PM, CARVER, PAUL <pc2...@att.com> wrote: >>> >>>> hossein zabolzadeh wrote: >>>> >I want to fully virtualize my datacenter. I don't want cloud. I don't >>>> want to deliver >>>> >public cloud. I have several legacy appliacation that I want to run >>>> all of them on >>>> >virtualized environment. I want to leverage the virtualization >>>> technology to improve >>>> >my datacenter consolidation, ease of meintenace, ease of management >>>> with >>>> >increase in capacity. >>>> >>>> >>>> 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: >>>> >>>> 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 >>>> >>>> or >>>> >>>> 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 >>>> >>>> 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. >>>> >>> >>> >> >> _______________________________________________ >> Mailing list: >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> Post to : openstack@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@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@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
