Live data from Hacker News

Microsoft, RedHat, IBM, Docker, Mesosphere, CoreOS and SaltStack join Kubernetes

googlecloudplatform.blogspot.com

11–20 of 56 posts

Re: Microsoft, RedHat, IBM, Docker, Mesosphere, CoreOS and SaltStack join Kubernetes

#11
post #9

Earlier quoted context omitted.

Not really. Even in an absolute sense, linux-vserver is/was contemporary with zones. Yes, in the sense that partitioning technology isn't new. zones and jails are comparable to vserver/openvz/lxc. vpars, lpars, and ldoms have analogues on mainframes. Various hypervisor technologies (xen, kvm, vmkernel) are also not unique to solaris, and were done on Linux. What Docker offers that none of these do not is that it's co…

Having never used Docker, if it is containerization for applications, how is it different from Application WPARs or App-V?

It's analogous to App-V or an Application LPAR, if such a thing existed, but these are both good examples.

My complaint to the previous poster is mostly that it differs in the same way that an Application WPAR differs from a WPAR. Yes, they're the same base. No, they're not the same thing.

Re: Microsoft, RedHat, IBM, Docker, Mesosphere, CoreOS and SaltStack join Kubernetes

#14
post #5

The cool thing that is that we have a number of companies contributing significant technologies to the open source ecosystem that build a stack of software that gets us closer to running distributed systems in a reasonable reproducible manner: - Google is bringing kubernetes (k8s) which represents their experience in deploying cluster wide applications - CoreOS is bringing etcd to the table for the cluster wide decis…

- Mesosphere is bringing Kubernetes on Mesos, which will give you a top-to-bottom stack that approximates Google's Omega/Borg at scale.

http://mesosphere.io/2014/07/10/mesosphere-announces-kuberne...

Re: Microsoft, RedHat, IBM, Docker, Mesosphere, CoreOS and SaltStack join Kubernetes

#15
post #12

crickets from VMWare/EMC. Docker/containers will eat their lunch if they don't jump in and get involved.

If KVM didn't eat their lunch already, why would Docker be different?

Because it's a new paradigm, not just a competing virtual-machine implementation.

Re: Microsoft, RedHat, IBM, Docker, Mesosphere, CoreOS and SaltStack join Kubernetes

#16
post #15
post #12

Earlier quoted context omitted.

If KVM didn't eat their lunch already, why would Docker be different?

Because it's a new paradigm, not just a competing virtual-machine implementation.

It's not a paradigm which even remotely threatens VMware's use case, though.

Re: Microsoft, RedHat, IBM, Docker, Mesosphere, CoreOS and SaltStack join Kubernetes

#18
post #12

crickets from VMWare/EMC. Docker/containers will eat their lunch if they don't jump in and get involved.

If KVM didn't eat their lunch already, why would Docker be different?

lxc is lighter weight. just like 5% page size saves millions in bandwidth. 5% cpu overhead saves in electricity and hardware costs. Assuming all other things being equal (I know they aren't - but security, tooling, and management can be improved) vmware has inherent overhead of the hypervisor that's not an issue with lxc.

Re: Microsoft, RedHat, IBM, Docker, Mesosphere, CoreOS and SaltStack join Kubernetes

#20
post #19

Interesting. No Canonical/Ubuntu.

They're Python-fans, I believe. EDIT: This used to be their recommended way of making apps: http://arstechnica.com/information-technology/2009/08/quickl...

They use go to build juju.
Post reply on HN