Apache CloudStack vs. Red Hat OpenStack Platform

Whether our clients are VPS hosting providers or operate private cloud infrastructure for their internal enterprise requirements, CloudStack provides solutions in an easy to implement and operate way that is simple to provide training for. The learning curve for our customesr adopting CloudStack for the management of their cloud infrastructure is shallow, enabling our clients to come up to speed quickly without having to outsource their administrative functions any longer than necessary

Best suited for - any organization where you have people who already have expertise on OpenStack, Linux & IP networking. Otherwise, the maintenance & operations will be difficult. When the number of deployed VMs reaches its capacity, it becomes very difficult to manage Red Hat OpenStack because there are no in-built fault management & performance management tools available within Red Hat OpenStack. Not suited for - Organizations where people have a culture of working on automated GUI-based tools. Here VMware wins over Red Hat OpenStack. Also where you have mission-critical applications where downtime cannot be tolerated.

Incentivized

• Low-cost solution
• Open-source
• Engaged community
• Solid documentation
• Is a very reliable tool for orchestration with good usability

Incentivized

• Scaling of application components (VMs).
• Managing the networking between virtual machines.
• Management of VNFs & the underlying infrastructure.
• Availability & uptime of VMs because of features like VM migration & evacuation.

Incentivized

• Sometimes you can find undocumented bugs that can compromise the entire infrastructure.
• [If] you don't have an official support channel, you have try to find out the source of the problem by yourself.
• Volume size limitation. Other players allow you to create volumes up to 64TB while ACS allows only 2TB volumes

• User management really needs improvement - when compared to AWS or GCP.
• Security of the overall platform needs to be improved.
• The whole architecture needs to be modular which is not. Ex - Upgrading any particular component (nova, neutron, cinder) should be possible without upgrading the whole Red Hat OpenStack version.
• The creation of HEAT templates for complex applications is still a challenge & has a dependency on external tools.
• Stack creation still requires parameters modification at controllers & compute because of the complex nova-scheduler algorithm.

Incentivized

The University, my first large implementation, had a big issue with 149 small data centers spread on São Paulo State, this data centers costs to university were very high, the consolidation idea in two data centers were awesome, but were worried with the management, so we adopted ACS to management of all 576 physical hosts. Now a days the university is delivering IaaS for all staff, students, teachers and researchers, they are using these resources to delivery services to their clients and have a great results in research area

Only because of low cost & zero licensing of Red Hat OpenStack

Incentivized

• Low-cost solution (free and open-source)
• More than 2000 users using it simultaneously
• Stable and reliable
• Up and running since 2012

Incentivized

• Saved CAPEX for sure (I can't quote a figure).
• Saved Opex also - because a large support community is already available.
• Increased complexity of system setup though.

Incentivized