Red Hat OpenShift Reviews

The use of creating environments (Development, Staging, and Production) using easy to use PaaS dashboard, and through the use of RHC.

It has a simple yet powerful way of managing environments, without many governance issues.

The product has helped kick off applications for developers at speed. New joiners can just start using the platform, without bothering to set up an application stack and/or server stack on their local laptop.

It has also helped us ship products at ease, using the Docker and Kubernetes platform, which forms the basis of RedHat OpenShift 3.

Scaling has a few defects, such as not scaling up at threshold values. This needs improvement. Also, require little more integration perspective, such as Service Desk integration and Source Code/CI integration.

I rated the solution as an eight out of 10 for two reasons:

1. Autoscaling issues. It does not increase in a seamless manner. Sometimes, CPU utilization/Memory utilization exceeds and the application just hangs or gets into HeapSpace or OutOfMemory error.
2. Sizing. Maintaining the number of pods at scale.

I've used this solution since 2013. Over almost four years, the product has evolved from a basic PaaS to a full-fledged PaaS and Private Cloud solution (with OpenShift 3)

Yes, as specified in areas for improvement answer.

It's good. Community support is also good. Easy to deal with.

Yes, we used IBM SoftLayer and we were not happy with it. Another solution that we are using is AWS, and we are pretty happy with it.

The initial setup was straightforward; not complex.

Pricing is good in comparison with AWS. The enterprise pricing is also competitive and is specifically fine-tuned to the type of environments we have.

IBM SoftLayer.

It's a solid solution if you are looking for a perfect enterprise-level PaaS. AWS is a better solution if you are looking for IaaS.

We're using this solution for newly developed applications in house development applications. I'm an infrastructure architect and we are customers of Open Shift. 

I think the most valuable feature this solution provides is the possibility to have support throughout the whole platform, including logging, monitoring, op features, and the like. It's a simple solution. 

I'd like to see support for more than one server, a mobile user registry. With that, you could divide it more granulary for development and render for testing and using different IDs.

I've been using this solution for six months. 

This is a stable solution. I think we're going to stick with it. 

This is a scalable solution, we have around 40 users. 

We previously used IBM WebSphere.

The initial setup is straightforward, it took around three to four days. We used the support and four or five of our engineering personnel for deployment. 

The licensing costs are quite cheap compared to other similar solutions. 

We were running many of our products on OpenShift.

We had to discontinue this solution due to many limitations.

Has a better UI and is good as a CICD solution.

Some of the features are platform-specific, so if it is ported to other cloud solutions it requires a lot of changes.

I am using OpenShift as a container platform to host various applications in a containerized environment.

It has really helped me a lot in debugging the issues.

The most valuable thing about it is the support available. 

Installation and setup are a bit tedious, especially in a proxy environment.