4 ms·
My bet is on Redhat's project atomic, which uses Kubernetes under the hood and will eventually support Mesos for scheduling (via kubernetes).
by SEJeff 12y ago
My bet is on Redhat's project atomic, which uses Kubernetes under the hood and will eventually support Mesos for scheduling (via kubernetes).
- chuhnk 12y agoI think what Redhat is doing with Atomic and OpenShift is really great. They are building some awesome stuff around Kubernetes however I feel like that is going to be entirely geared towards the enterprise space. Much like OpenStack it's very complicated and the barrier to entry is still quite high. When I looked at the docs I immediately had to go look at reference info for all this new terminology they had introduced. They'd basically ignored what had come out of industry usage and naming. But in saying that, I do hope they cause massive shifts in the enterprise game. I have quite a bit of experience in the microservice and cluster management space and have started to prototype something much more accessible to the masses. I'll know within the space of 6-8 weeks whether it's actually going to work or not but nonetheless we need people who understand and use these technologies on a day to day basis in the general tech space.
- jacques_chester 12y agoThe next generation of OpenShift is largely hypothetical at the moment. Cloud Foundry already has a container-based PaaS and it's only getting better. And it's not tied to a single vendor. Disclaimer: I'm biased as hell, I work on CF for my dayjob.
- SEJeff 12y agoNo I've got no interest in OpenShift and wasn't referring to it, I was referring to Project Atomic[1] and the RHEL/Fedora/CentOS Atomic Host. [1] http://www.projectatomic.io/ http://www.projectatomic.io/
- jacques_chester 12y agoGranted, but I was replying to chuhnk's comment, which mentioned both OpenShift and Atomic.
- fatherlinnux 12y agoThe current version of OpenShift (2.X) is essentially Linux container based (selinux, cgroups, kernel namespaces). OpenShift 2.X has been running in production for years now (openshift.com). The reason something like Docker wasn't used is because nothing existed, so Red Hat had to invent something. From an app perspective it's fairly good for what it does.
- jacques_chester 12y agoThanks for the correction, I was wrong. I do note that Warden uses a lot of the same primitives (as do several projects building on the facilities that arose or were repurposed for Linux-VServer, OpenVZ, LXC etc etc).
- SEJeff 12y agoThe exact same could be said for CoreOS :) I'd love to see what you're doing if you're open to sharing.
- chuhnk 12y agohttp://myodc.io/ http://myodc.io/ Building a microservices ecosystem. Starting with one click Cluster as a Service with Kubernetes on multiple cloud platforms. Then leveraging that to offer a microservices platform which gets you started extremely quickly much like Heroku but with the idea of deploying multiple services that coordinate to create something much larger.
- qooleot 12y agoJust a single data point, but I went to a Redhat talk and their demos had several failing bugs. They also clicked around a lot, and said things like 'well, you now created an ip block, then designated an ip from the pool, but to make that actually work you need to...'. I'm not so sure Redhat will make things simple enough and "just work" for non-corporate clients.