Re:Large-scale cluster management at Google with Borg
by dcsommer on Thursday May 07, 2015 @01:02PM
(#9506546)
Does Kubernetes use chroot jails like Borg, or has it advanced to LXC containers? Nowadays LXC isolation seems strictly preferable.
[ Parent
| on HN ]
Re:Large-scale cluster management at Google with Borg
by wffurr on Thursday May 07, 2015 @01:34PM
(#9506800)
Borg also uses cgroups, just like LXC.
From the paper: "We use a Linux chroot jail as the primary security isolation mechanism between multiple tasks on the same machine… all Borg tasks run inside a Linux cgroup-based resource container."
Re:Large-scale cluster management at Google with Borg
by samkone on Thursday May 07, 2015 @02:01PM
(#9507000)
Remember that Borg is an old thing. At the time they probably started out with chroot jails, because cgroups weren't ready yet. But Kubernetes, Mesos use docker and cgroups(Mesos).
Re:Large-scale cluster management at Google with Borg
by KaiserPro on Thursday May 07, 2015 @03:50PM
(#9507789)
Cgroups have been around for a long time. Wikipedia says 8 years.
I think was in RHEL 6.2 possibly even 6.0
Re:Large-scale cluster management at Google with Borg
by powera on Thursday May 07, 2015 @02:06PM
(#9507045)
cgroups were largely written by members of the Borg team.
Re:Large-scale cluster management at Google with Borg
by jbeda on Thursday May 07, 2015 @01:17PM
(#9506665)
Kubernetes uses Docker (or now rkt) to do the actual containing. The focus is on scheduling and managing lots of containers.
You may run O(10) containers on a single machine. When you run O(10k)+ containers in a cluster you need new tools to manage things.
Re:Large-scale cluster management at Google with Borg
by jhspaybar on Thursday May 07, 2015 @01:05PM
(#9506573)
LXC uses chroot + other things. chroot is essentially the foundation of any containerization tool.
Re:Large-scale cluster management at Google with Borg
by zobzu on Thursday May 07, 2015 @01:10PM
(#9506613)
Not really- chroot provides no isolation, namespaces do.
choot is the visible portion (changes root.. ie changes /mnt/blah/bleh to /) but not "the foundation"
Things can in fact work isolated without chroot, too. Its just convenient.