Can we ban techcrunch please? http://googlecloudplatform.blogspot.com/2014/11/google-cloud...
(We changed the URL from http://techcrunch.com/2014/11/04/google-launches-managed-ser...)
51–60 of 69 posts
Can we ban techcrunch please? http://googlecloudplatform.blogspot.com/2014/11/google-cloud...
(We changed the URL from http://techcrunch.com/2014/11/04/google-launches-managed-ser...)
Earlier quoted context omitted.
GCE doesn't support nested virtualization. But if you are running Kubernetes on bare metal, there is no reason you couldn't map in /dev/kvm and have k8s run VMs for you. I haven't done it though :)
Ok, I've done VMs inside docker already which has been fine, was hoping GCE would let me do it on Google's systems.
Can someone explain the difference between Apache Mesos, Apache Spark, and Kubernetes. As someone reading just announcements, and having never experimented with any of these tools, they sound like they promise the same capabilities. Is it just that they are different open source projects aiming for the same goal ... or are their goals different?
Apache Mesos is based on Twitter's expertise in deploying their cluster, Kubernetes on Google's. They do things in different ways. Spark seems to be in the same area as Hadoop, so not relevant to the conversation.
More info/docs here: https://cloud.google.com/container-engine/ I'm on the Kubernetes/GKE team and happy to answer any questions you all might have. We also all hang out on IRC at #google-containers on freenode.
Some google-managed base images would be helpful. The last time I checked, some of the major public docker images were still shellshock-vulnerable. Pre-installed GCE tools would be helpful. Perhaps automated environment variables about region, etc.
See https://gist.github.com/voltagex/582473e3b86ee5ae4438 - I ran some tests on the three most popular (?) official base images.
Earlier quoted context omitted.
Ok, I've done VMs inside docker already which has been fine, was hoping GCE would let me do it on Google's systems.
As someone who doesn't know, why would you want to run VMs inside of a docker container? Wouldn't this have tremendous overhead relative to just running the hypervisor?
It's advantageous for me, because I can say "hey check out this software" and they just have to run a single docker command, compared to installing Go, apt-getting a bunch of packages, fetching our repo, compiling, etc.
More info/docs here: https://cloud.google.com/container-engine/ I'm on the Kubernetes/GKE team and happy to answer any questions you all might have. We also all hang out on IRC at #google-containers on freenode.
Docker has pulled off some really impressive biz dev. I can't think of too many other things that Azure, Google Cloud, and AWS all support.
More info/docs here: https://cloud.google.com/container-engine/ I'm on the Kubernetes/GKE team and happy to answer any questions you all might have. We also all hang out on IRC at #google-containers on freenode.
Some google-managed base images would be helpful. The last time I checked, some of the major public docker images were still shellshock-vulnerable. Pre-installed GCE tools would be helpful. Perhaps automated environment variables about region, etc.