Red Hat OpenShiftの評判・口コミ 全9件

What do you dislike?

Nothing so far. It seems hard to learn but it doesn't.

What do you like best?

Good way to host Java applications in the cloud. I used Openshift to host my JSF application with a little API and it was able to do these things very well.

Recommendations to others considering the product

Good tools. It supports a lot of languages and it can solve many problems of cloud host.

What do you dislike?

Alguna configuraciﾃｳn desde el IDE para conectar con la plataforma

What do you like best?

La facilidad de despliegues de aplicativos en mﾃｺltiples tecnologﾃｭas

What do you dislike?

The platform itself is kind of complicated to understand.

What do you like best?

I love how organized the platform is....

Recommendations to others considering the product

N/A

What do you dislike?

Openshift clusters don't have clear logs upon failure and require going deep into the structure of your docker files without much clarity. Some better automated logging on the web interface would go a long way to improving the software as a whole.

What do you like best?

Ease of uploading is definitely a huge plus. By creating an Openshift cluster on one VM you can locally create images and immediately have them accessible and scalable in a matching web-based UI.

Recommendations to others considering the product

I recommend that anyone planning to use Openshift acquaint themselves with the Docker and Kubernetes documentation and be sure that they have experience creating Docker images of course. I think it is a great secure combination of these two open-source softwares from Red-Hat. Additionality I think the UI adds value in the right ways though it could have more information and data for administrators and users to understand errors. Overall, Openshift is a successful software stack for companies that require certified software and want to move to containerization. It is easy to use with repositories and it's secrets and volumes are easy to adapt to and get to know how to use. With limited knowledge of the documentation you can get several containers up and running and scaling within 20 to 30 minutes. Internal documentation is of course key for getting to know the software better in it's use at your company.