4 ms·
It's a well-funded solution to a well-funded problem. Producing platforms for enterprise customers is truly, genuinely difficult. There is enormous variation a
by jacques_chester 7y ago
It's a well-funded solution to a well-funded problem.
Producing platforms for enterprise customers is truly, genuinely difficult. There is enormous variation and complexity between and within customers, which cannot be dismissed easily.
Disclosure: I work for VMware, a direct competitor in this space.
- streetcat1 7y agoIs Vmware going to support an operator store like red hat? If yes, is there a way to certify an operator on Vmware 7?
- jacques_chester 7y agoI'm not sure, to be honest. Can you email me? I'll try to figure out who I can connect you to for an answer when I'm back on Monday.
- streetcat1 6y agoSure. will do. Thank you for your reply.
- nickthemagicman 7y agoIm not knowledgable enough in this area, but I don't understand the value in using Openshift's custom setup over established cloud providers setups like AWS or GCP or Azure or even VMWare(who has been in the vm biz wayyy longer than all of these players.)
- freedomben 7y agoThe value prop depends a lot on who you are and what you have. The massive selling point to many enterprises that own their own hardware is that they can run OpenShift on their metal, and augment with public clouds (AWS/GCP/Azure). If you use any of the vendor-specific augmentations (like ALB integration) you can't leave AWS and move to another cloud or your own hardware. OpenShift also adds a lot of rich functionality above the standards K8s setup. It's essentially a bunch of operators that work really well together and add PaaS functionality onto K8s.
- oso2k 7y agoDisclaimer: I work for Red Hat Consulting where my day job is 100% OpenShift. The "custom" parts of OpenShift are things you're going to want anyways. They're also optional (to a point) but obviously Supportability will change depending on customer customization. A Container Registry, something to manage your Ingress (we have HAProxy and Ingress Controller), Metrics & Monitoring of containers, pods, and nodes using Prometheus, Grafana, and AlertManager, a logging stack that sucks in your logs from stdout built on Elasticsearch, Fluentd, and Kibana, supported Middleware, Apache Camel, AMQ, Kafk), Java, OpenJDK, JBoss, Tomcat, Spring Boot, node.js, Quarkus, Python, Ruby, PHP stacks, built-in tooling for CI/CD with Jenkins, Tekton. OpenShift can be run almost anywhere that RHEL8 can. We've started down the path of multi-arch supported Kubernetes too, first with IBM Z and others to come. We run OpenShift on Public Clouds, Private Clouds, VMs and Baremetal.
- pnako 7y agoYou forgot to mention Erlang, MongoDB, Rebol, zsh, PostgreSQL, Haskell, Microsoft .NET Compact Framework 3.9, DB2, Ansible, NetBSD and an elastic scalable automated deployment and analysis stack based on virtualized Visual Basic 6. Any company needs that, and more! I'm glad Red Hat consultants are here to help us make sense of all those technologies.
- nickthemagicman 6y agoEverything you named is common to every cloud provider.....container registry, load balancers, log monitoring, etc It's actually also doable with K8's and Helm. I only have a birds eye view but I can tell so far, it seems like yall are providing the much-needed synergy, organic innovation and turnkey platform insights to those vertically and horizontally aligned paradigm holistically reimagined out of the box future forward dynamic enterprises to both meet market demand and to transform industry mindshare with world class artisinal I.P. I.P.A if you will. Every technology V.P. will get a visible hard-on when they hear about the Open shift product.