Red Hat OpenShift Reviews

The pod solution and the on-demand solution are well suited, although I have feelings of loss regarding not using VMware.

It is promising though. The project we are on is large scale so further information would be far more pertinent when fully deployed I think.

Right now the major point is cost effectiveness. The improvements I am expecting will be better presented when in full production.

For some reason there have been some DNS issues. At this time I am not convinced it is OpenShift though. I will have to circle back to this one.

We have just bought the solution and started using it recently.

There have been some DNS issues.

We did not yet encounter any issues with scalability but I am looking forward to our first "go day."

This isn't really an issue. I haven't really called upon support yet. Red Hat reps have been really quick to respond on other issues though.

We were using VMware which is more expensive for no good reason. Thank you OpenShift.

Linux in general is a different flavor. Nothing out of the unexpected. Though, as in all things, there is room for improvement. One solid BIN would be nice.

In the installation of ORIGIN, using the playbook and Ansible install in the Docker, there are fixed points which would make the install easier.

Save money and get OpenShift. Literally.

We evaluated VMware, but then I am biased. I will always choose Red Hat as I know all too well what it does as opposed to other solutions. I am not knocking other solutions, but Red Hat wins in the long run.

Do your homework. Take the time to analyze what you really want and need. I am not saying this is the absolute answer to all your questions as that would be unreasonable and naive. I personally believe that at least 75% of cases probably should be directed at Red Hat in general.

OpenShift is a primary tool in my daily work and in the project I have been working on in recent years – TV streaming services used widely in the U.S. and outside. OpenShift is used for intensive DevOps and running pieces of the project adhering to the microservices architecture. The project's architecture includes physical servers in tens of datacenters. OpenShift plays a central role in developing, testing, and running specific software.

Our small team developed and rolled out everything to production in a short time, mostly thanks to OpenShift. It saves time. Using it, I just work on integrating services without worrying about containers and whatever is needed for them. OpenShift is a tool that does a lot of work for you. You just need to invest some time learning it.

OpenShift helps by doing a lot of work for us. I love to automate everything and OpenShift was been born to do so. It takes care of the network layer itself and I don't need to dive into it; I can work on a top level. Our project has numerous services designed to run in Docker containers, and we have run almost all pieces of our TV services in OpenShift.

I think that OpenShift has too many commands for running services from the CLI, and the configuration files are a little complicated. This scares newbies from learning it. I hope that the OpenShift developers will improve this "dark side" of OpenShift.

OpenShift has been running for the past three years, since the project started. We were developing the project's architecture, trying different solutions. In the end, we chose OpenShift as a well-known and intensively developed software, with many really useful features.

Migrate to microservices.

Has helped us with faster deployment time, zero downtime.

• Scaling
• Fast deployment
• Zero downtime when releasing a new version
• Auto-recreate pod if pod fails
• Fast rollback, with one click, to previous version

It could use auto-scaling based on criteria such as transaction volume, queue backlog, etc. Currently, it is limited to CPU and memory. 

Credential not hidden, so people on the same group can view it.

Java and WildFly.

OpenShift is great for flexibility, agility, and speed of delivery. We use WildFly as an application server. We have not started to use OpenShift mainly, yet.

• WildFly, because it standardizes infrastructure.
• The git repository and docker. Git is essential for source code and Docker for infrastructure.

It would be great if it supported Bitbucket repositories too.

Migration of old and custom APIs and development environments, for both internal and client-facing use. This migration has been going on for two and half years now. It is a rather large endeavour. I would estimate we have another six to nine months ahead.

No longer do I have to pay VMware large amounts of money to only run in-house solutions. (I give a particular heartfelt thank you for that).

This is an easy question to answer: the virtualization of my APIs. 

There have been some issues with security, in particular, that we had to address. At times they make it “clunky." I am quite confident these parameters will appear in the next releases. They have been reported as bugs and are actually in process. Despite this, the competition is rapidly losing ground.

• Continuous integration between different technologies

• Single Sign-On

• Security enhanced

• Easy deployment and follow-up of entire pipeline process

We connected Jenkins as the main build operator with API calls to the OpenShift Pipeline. It is amazing the amount of time saved. You can see the logs of pipeline process on Jenkins and follow it in real-time or by notifications if something goes wrong. We used Slack for build notifications as well.

• Build

• Deployment

• Product delivery

These areas would save time for the entire team.

We have used this solution for one year so far. We have been following all the improvements on the tool since the launch.

There were only deployment problems on my end, but I did have to reconstruct pipelines.

There were no stability issues.

There were no scalability issues, but only some Docker issues.

Customer service is perfect.

Not available.

I started using another technology, whose name I don't recall. The goal of OpenShift is to make things easier by connecting all tools in one switch.

The first installations were tricky. There were some bugs and workarounds, but it was never hard.

Newer versions were smoother and the problems no longer exist.

The first implementation was done on my own, where I was learning, testing, and exploring. All the documentation is updated on their website.

The ROI is in terms of productivity and saving time. I can't measure how much money I saved by using this technology, but know for sure that the money was well invested.

Go for it. Red Hat is professional on solutions.

I tried Rancher and other similar technologies, but their goals weren't the same as mine.

Try using OpenShift Origin (free version) for a instance. It is pretty stable and has new nice features. The code is on GitHub, so you can always suggest improvements and bug fixes.

The OpenShift environment will be used by medical applications. This environment is still in the development/QA phase.

Not yet.

The scaling and uptime of the applications.

Needs work on volume handling (although this is already better with GlusterFS). Security (SSSD) would also be an improvement.

Not at this moment (still running in dev/QA phase).

Not at this moment (still running in dev/QA phase).

Five stars out of five, all issues were solved in an acceptable timeframe.

This was my first installation. It was not straightforward due to internal limitations, not the product.

I rate it a six out of 10. There are still some issues with it. I have several cases at Red Hat that need to be resolved.

Do a test to try the solution.

The ability to persist data, the security model, the web console, the installation - all of those features make using the product easier.

We develop software for customers that runs on OpenShift, so developing on a standard product like OpenShift supports our customers' need for cloud based container solutions.

The security model is hard to understand and use. Debugging errors can be hard as well.

We have been using the solution for two years.

The product seems to be mature enough to use for production application deployments without stability issues.

The product is able to meet most scalability goals.

The technical support is generally good and there are ample materials available on the web to help find answers to issues.

We have not switched from another product. We also support other cloud offerings like Kubernetes.

The installation is better now than early on and can be complicated to set up if you are not familiar with Red Hat Linux and Docker.

For trials and prototypes, the open source version of OpenShift will suffice for most users and is compatible with the licensed version of OpenShift.

We evaluated Cloud Foundry but decided upon a Docker container based platform like OpenShift.

Start small, try the open source OpenShift Origin first, then develop a sample application to get accustomed to the platform.