OpenShift Reviews

OpenShift is being used at a project level. OpenShift makes it easy to host our web application on the cloud. Being on the cloud makes our application more accessible than it was before. The interface is easy to use and understand so there is not too much difficulty on that front. It can also be useful from time to time for testing out prototypes.

We evaluated OpenShift as a docker platform for our company. While not chosen for non-technical reasons, OpenShift was a definite leader in the list of competitors. The intention was to use this platform across the company for development through production. Integration with our CI/CD pipeline was intended. Simply put, OpenShift solved the majority of our continuous development and deployment issues.

OpenShift is a great way to start, especially their free tier. It is excellent for software engineers who want to learn PaaS. I have tested many PaaS system from Heroku, IBM Bluemix, to Azure Microsoft. It is great for solo developers and large enterprises.

Right now, it is being used for a single website that has previously been hosted either personally, in EC2, or on Bluehost over the years. I picked Openshift because it had the capability to scale up, but I don't get charged when use is low, which is the case a majority of the time.

We use OpenShift for quick easy up websites that don't require a lot of ongoing development. We use AWS for our bigger projects that we need more control over. For example, we use OpenShift if a client needs a click-through website without much real functionality, or just a basic website.

I am using it for evaluation purposes to understand the usefulness of this product in terms of its PAAS services. I have been using the public Openshift cloud since it has a lot more cartridges available. I have developed two applications on the Openshift cloud: Kecha and Note. Kecha, is a instant messaging application and Note is a blog-like application developed using Tomcat7, MongoDB, PostgreSQL cartridges.

From developing these applications, I have learned a lot about OpenShift. I really like their devops architecture such as using environment variables per environment for username/passwords, so no need to maintain extra properties files. I like their "hooks" that triggers builds when a code is pushed-in using GIT or you can customize the process how you like using OpenShift marker files. They also have support for Docker integration which makes it more worthwhile to integrate applications using OpenShift now.

We leverage OpenShift in a number of ways. First, we use it to support the Academic institutions by setting up environments for students to access course applications. Second, we use it to host our Sales Automation and quote generation tools. Finally, we leverage it to support development environments and enable developer self-service.
In addition to being a consumer, we also are a consulting company where we advise companies as to the use and implementation of OpenShift and PaaS solutions within there environment. We help them identify which applications are ideal fits and which ones should be avoided. In addition, we have worked with other partner companies to bring their products to the OpenShift environment. ownCloud is one such company where we not only created the instant application to be deployed in the environment, but also developed an on-premise Dropbox alternative for companies concerned about data ownership.

We are currently using OpenShift to host Aerogear's Unified Push Notification server from Red Hat. Aerogear is installed as a plugin which is called a cartridge in OpenShift terminology. One of the dependencies for Aerogear is MySQL. It is also bundled as a cartridge and is selected as part of the Aerogear cartridge install.

RedHat Openshift is used across the whole organization to cover 2 needs. First foster a DevOps culture between developers and the middleware team. Secondly standardize the way applications are implemented based on a limited set of docker images and homogenize all configuration properties through a unified all-in-one property file defining JMS queues, JDBC databases, web-services url etc...

I deployed my applications on openshift.

It was helpful in these ways:
1) very easy to upload
2) Easy manuals are available
3) Easy troubleshooting

It was not only one application but multiple applications. I could deploy the applications with ease and use OpenShift for software as a service. Links were quite responsive and compatible with other SAAS as well. My DB was also always deployed on the cloud.

OpenShift was used to facilitate research and development within the front end development team. It enabled front end developers to quickly create development environments using pre built cartridges without requiring dev ops support.
Previously, developers would have been limited to the languages and tools available to them, which restricted innovation. The speed at which environments can be created has enabled great creativity.

Our team provides infrastructure for hundreds of applications. We implemented OpenShift as a cloud computing platform as a service. It helps our application developers to get a cloud environment where they can build, test, deploy and run applications. It helps app teams from simple application hosting, to building new service offerings, to eventually hosting your own platform. It has improved resource utilization.

We used OpenShift for our internal development purpose, this helped us solve so many manual and human error problems. OpenShift Origin provides you with a platform to deploy and automate your development process as well as to automate your build process. Openshift has variety of product support. It also has integration features with build and CI tools like Jenkins,