Red Hat OpenStack Platform vs. Sonatype Platform

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

- Guidance on remediation is very good - Vulnerability detection is very good - Support is very good - Ability to ask PMs/POs open questions at Office Hours every month is very good - Support for languages is lacking (TIOBE Index Top20) - Some features are un-neededly hidden and make the usage more complex then it needs to be

• 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

• Nexus firewall is a great feature enabled for all our proxy repositories which are used to download the third-party opensource packages.
• Nexus IQ is integrated with build stage to analyze the component against evaluation policy. This helps to figure out the application security standards.
• Nexus IQ is also having a feature to scan container images before it uploads to our private repository. This is great feature for container platforms.

• 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

• Support on the end of life lifecycle of known open source components that are going end of life, or already went end of life
• Support for emerging infrastructure as code frameworks
• Support for native/ default retention, archiving and clean up policies for hosted repositories

Sonatype supports more than 200 dev(s). It proves with the repository to store the artifacts. Allows for governance of open source software used by the different teams. It is used by security teams to scan for vulnerabilities in software(s) and in the deployed containers. It helps ensure code quality.

Incentivized

Overall experience is great with the Platform; however, I see some opportunity with upgrading the platform as it is missing with data of historical scans to allow reviewer to get view of trend how the application/product development team is considering fixing the issues.

Incentivized

Extremely good

Sonatype products are great value as I said but a few areas like how products use underlying resources in order to make it further lightweight, is something I would like them to consider.

Monthly touchpoints with Sinisa has been very valuable.

Incentivized

easy to implement and performing the scans via automations as well

Incentivized

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

Incentivized

Out of other products we evaluated before choosing Sonatype, the later looked far more user friendly, easy to understand and work with. This was key for us, as the tool needs to be used by many engineers that don't have security as their main focus. Having a tool that is easy to understand and work with, makes the process of evaluating open source dependencies much easier and appealing for developers.

Incentivized

Great value for money

Everything is very good except a little concern regarding large scale docker usage.

Very good

• 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

• Sonatype's centralized management of artifacts have made it very easy for developers to share code in an efficient manner.
• Sonatype's low false positive rate has made it easier to convince developers to remediate vulnerabilities
• Sonatype's archaic architecture has made it more expensive to manage than it could be.