Red Hat OpenStack Platform vs. Sardina FishOS

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

• 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

• 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

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

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