IBM Cloud Foundry is an IBM version of the open-source platform designed for building, testing, deploying, and scaling applications. Enterprises can run Cloud Foundry in a public isolated environment, while natively integrating with other IBM Cloud services, such as AI, Blockchain, and IoT.
$0.07
Per GBH
Red Hat OpenShift
Score 9.3 out of 10
N/A
OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.
IBM Cloud Foundry (CF) is simpler and there is a service model that fits most of our internal services. We are going to Loopback for API and Node.js and we have an easy path to go with Bluemix. It's a very easy way to start if you are moving to the cloud and mainly if you are …
When we evaluated PCF, it was just running application as containers. Managing applications and workloads were not that easy. Ecosystem wise PCF was quite small. Just few resources to create and manage. But Red Hat OpenShift was based on K8s, any k8s capabilities' will able to …
We had some existing apps and were looking for a platform to modernize our app deployments and scale for future growth. Based on Kubernetes, OpenShift offers more flexibility and customization. We could deploy any type of containerized application, not just Cloud Foundry-specifi…
As it is an open-source platform as a service, it is very easy to operate, scale, and deploy regardless of what programming language and framework it's written in. However, it could be improved in terms of scalability. There should be proper documentation for easier and clearer understanding to make the process smooth.
Well suited if you are looking to do containers, if you're looking for an easy way to build a container platform, there's so much in it to easily do that. Right now it's not as great as handling VMs with my aforementioned comments about how it can improve. So I would say it's low point right now it's the VMs, but it looks like they're improving. But the high point is always containerization.
Simplicity - the command line tool provided can get you up and running within minutes.
Resourceful - IBM Cloud Foundry is built on top of the open source Cloud Foundry technology, so any resources you find online about Cloud Foundry generally can be applied.
Feature rich - provides all the necessary features for a cloud based platform, such as auto-scaling, 0 downtime deployment.
One thing is the way how it works with the GitHubs model on an enterprise business, how the hub and spoke topology works. Hub cluster topology works the way how there is a governance model to enforce policies. The R back models, the Red Hat OpenShift virtualization that supports the cube board and developer workspace is one big feature within. So yes, these are all some features I would call out.
So I don't know that this is a specific disadvantage for Red Hat OpenShift. It's a challenge for anything that Kubernetes face is. There's an extremely large learning curve associated with it and once you get to the point where you're comfortable with it, it's really not bad. But beating that learning curve is a challenge. I've done a couple presentations on our implementation of Red Hat OpenShift at various conferences and one of the slides I always have in there is a tweet from years ago that said, "I tried to teach somebody Kubernetes once. Now neither of us knows what it is."
OpenShift is really easy of use through its management console. OpenShift gives a very large flexibility through many inbuilt functionalities, all gathered in the same place (it's a very convenient tool to learn DevOps technics hands on) OpenShift is an ideal integrated development / deployment platform for containers
The virtualization part takes some getting used to it you are coming from a more traditional hypervisor. Customization options are not intuitive to these users. The process should be more clear. Perhaps a guide to Openshift Virtualization for users of RHV, VMware, etc. would ease this transition into the new platform
Redhat openshift is generally reliable and available platform, it ensures high availability for most the situations. in fact the product where we put openshift in a box, we ensure that the availability is also happening at node and network level and also at storage level, so some of the factors that are outside of Openshift realm are also working in HA manner.
Overall, this platform is beneficial. The only downsides we have encountered have been with pods that occasionally hang. This results in resources being dedicated to dead or zombie pods. Over time, these wasted resources occasionally cause us issues, and we have had difficulty monitoring these pods. However, this issue does not overshadow the benefits we get from Openshift.
Every time we need to get support all the Red Hat team move forward looking to solve the problem. Sometimes this was not easy and requires the scalation to product team, and we always get a response. Most of the minor issues were solved with the information from access.redhat.com
I was not involved in the in person training, so i can not answer this question, but the team in my org worked directly with Openshift and able to get the in person training done easily, i did not hear problem or complain in this space, so i hope things happen seamlessly without any issue.
We went thru the training material on RH webesite, i think its very descriptive and the handson lab sesssions are very useful. It would be good to create more short duration videos covering one single aspect of openshift, this wll keep the interest and also it breaks down the complexity to reasonable chunks.
CF is what we initially went with to establish a development pipeline and start our cloud journey, now we are expanding this and although we are now pulling in many other tools and functions around CF, it is not being replaced. It stands out as having a key place working ‘with’ git, Kubernetes, IBM cloud etc, not against or segregated from it.
The Tanzu Platform seemed overly complicated, and the frequent changes to the portfolio as well as the messaging made us uneasy. We also decided it would not be wise to tie our application platform to a specific infrastructure provider, as Tanzu cannot be deployed on anything other than vSphere. SUSE Rancher seemed good overall, but ultimately felt closer to a DIY approach versus the comprehensive package that Red Hat OpenShift provides.
It's easy to understand what are being billed and what's included in each type of subscription. Same with the support (Std or Premium) you know exactly what to expect when you need to use it. The "core" unit approach on the subscription made really simple to scale and carry the workloads from one site to another.
This is a great platform to deployment container applications designed for multiple use cases. Its reasonably scalable platform, that can host multiple instances of applications, which can seamlessly handle the node and pod failure, if they are configured properly. There should be some scalability best practices guide would be very useful
IBM Bluemix is mainly a foundation enabler at this stage, although our business plan does look promising.
The low cost of development on Bluemix for a start-up like us is so helpful......we had no spare cash for this project besides what we could save or borrow at first, and that wasn't much. We are still trying to attract venture capital to cover the main Cordova Coding effort plus the launch "Cash Burn".
Features like push notifications, mobile-back end, and world-beating security help us to sell our SaaS products/services.
The pure (usually!) functionality of IBM products and services is very rewarding to work with.They are so insightful and thoughtful, to say naught of clever!
All of the above. Red Hat OpenShift going into a developer-type setting can be stood up very quickly. There's a very short period to have developers onboard to it and they're able to become productive much faster than a grow your own type solution.