Reviews (1-14 of 14)
2. Learning platform to cloud technologies / Computer Science / DevOps (e.g. kubernetes, minishift).
3. An experimenting / testing platform to test new services, functions, features.
4. As a showcasing platform, where staging working prototypes are presented to clients.
- Easy to use interface.
- Free 1GB access on signup.
- It is considerably fast.
- When there is a failure while uploading a project it may take time to understand where the problem is coming from.
- SSL certification knowledge is required before deploying web projects.
- Difficult to check and understand logs.
- Built on top of Kubernetes giving it a solid base to work with.
- Extensive API support allowing developers to extend the platform as needed.
- Built for security. For instance, containers are expected to run as a non-root user inside the container. If this is not the case, OpenShift complains and requires an explicit override to allow the container to run.
- There is a bit of a learning curve. Especially for how OpenShift expects code to be developed.
- Not for small deployments. OpenShift runs on Kubernetes and with that comes a fairly hefty server count requirement.
- LocalHost using Minishift, having your own PaaS locally
- Fast Build times
- Node Support
- .Net Support
- Runs on CoreOS
- Vertical Scaling
- Horizontal Scaling
- No Credit Card Needed
- Free Tier
- There is a steep earning curve
- More tutorials
- Openshift has an intuitive easy-to-use web interface as well as an OC client if you need to automate (oc stand for Openshift client).
- Openshift concepts are clear and well defined (pod, route, probe etc...).
- Fast, stable with an integrated monitoring tool that covers most the needs.
- I would like to use another CI tool instead of Jenkins.
- It would be useful to have a tool to apply global changes on all applications across all tenants at once.
- An integrated statistical module keeping historical data would be interesting.
Can't beat the price to get started with a low traffic website, and still be ready for a burst of traffic.
- No work seems to be required in order to scale up.
- Free service when use is low.
- I love the ability to login with SSH!
- Data storage seems a bit costly in comparison with the other services, but maybe I am just cheap.
- Quick setup complete with pre-configured gears.
- Easy to manage modules and gears.
- Comes with a git repo.
- If my site doesn't get much traffic it goes offline sometimes, so I had to set up a service to ping my site frequently.
- Sometimes my site just goes offline randomly and I have to go restart my app.
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.
- OpenShift is really designed well particularly from a developers perspective. I think as a developer myself I just want to pick my target app-server runtime and choose the cartridges I need using OpenShift and I can just deploy. If you are a newbie or want to try it out you can use the OpenShift public cloud and start from there.
- OpenShift Integration with Git makes it a attractive point. You can also use OpenShift marker files to control when to build and when to deploy after each check-in makes it convenient to customize the build and deploy behavior per environment.
- OpenShift and Docker integration makes it a very appealing choice.
- I would like to see a public cloud using OpenShift and Docker integration. I am not aware if this is already available now.
- I would like to see a tool that can help with extracting log files from the remote server like it being available on a Samba shared folder. And other applications that want to scan for keywords in the application log can check if there have been any errors or exceptions thrown by the application.
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.
- Ability to rapidly create application hosting environments
- Security-first mindset with SELinux and limited ports open by default
- Rich ecosystem of tools, frameworks, and languages. While most PaaS environments are just now moving to a Polyglot platform, OpenShift has been doing it from day one.
- Improved monitoring of the stack. Difficult to see how the different layers can be impacted and correlate events.
- OpenShift + Docker deployment strategies - ability to move application workloads between different deployments such as developer environments, other cloud providers.
- More commercial supported applications similar to Drupal, Wordpress, EnterpriseDB, MongoDB, AppDynamics, etc.
- Cartridge Architecture - The ability to install existing cartridges from the community as well as ones you create makes it really easy to get a PaaS up and running quickly
- Source Control - OpenShift provides the ability to control changes to your software thru a Git repository. This allows you to effectively manage your software.
- RedHat Console - RedHat provides some nice Ruby based tools that allow you to interact with your server. You can tail logs, restart the server, ssh in and change JBoss configuration settings for example.
- Auto Scaling - There is the ability to auto scale an application. However, you have to decide on this up front. There doesn't seem to be a way to change this after the application is created.
- Upgrading Cartridges - You can upgrade cartridges thru the source code repository provided. However, it would be nice if you could just select a new version in the UI.
- Free Version - If you have an application running in the free pricing model and have not accessed it in over 24 hours, the application goes into a pending status. The first request after the 24 hour period will fail while your application starts up. The pricing model is really inexpensive so this really is not a big deal however.
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.
2) When the number of people involved is not more than 100 (provided you are using a free version).
3) Also, there is a minimum number of applications we can keep active at one time. So if you have to keep multiple applications on at a time it is not possible [to use] free Open Shift.
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.
- Pre built cartridges, giving a huge range of software ready to go. Reduces the amount of time required to get up and running.
- Integration with GIT was an advantage, cloning the repo and making changes was straight forward.
- Speed, creating an environment in minutes, ready to deploy.
- Swapping between different Openshift accounts wasn't as intuitive as I would have imagined, although I doubt that the tool is primarily aimed towards front end developers.
- Application Scaling: Auto scaling feature helps application teams to get the resources on the fly without wait time ( provisioning time).
- Single platform supports multiple technologies, web cartridges and add on cartridges which helps application teams to avoid unnecessary time spent on installing and procuring software.
- Friendly URL, clients can select the alias name as required.
- Gear movement from one district to another.
- Storage accessibility for auto scaled gears.
- Gear distribution across different data centers.
- Can be implemented on a bare metal environment
- Can be managed by a development team without IT involvements
- Auto DNS registration
- Include more Product Support (Cartridges)
- Should include more GUI based management
- Should help to port the application across the platform
OpenShift Scorecard Summary
Feature Scorecard Summary
OpenShift Technical Details