Let Me Contain That For You!

This proposal has been accepted as a session.


One Line Summary

Redesign of container management and its use at Google.


We’ll demonstrate a redesign of container management solution built for use at Google. The talk highlights our design motivation and some of the differences from existing container management solutions. We cover some lessons learnt during re-design that help us adapt to what we believe are the workloads of tomorrow:

- Larger machine (more cores and memory) which leads to more containers. This requires a level of concurrency and scalability that doesn’t exist today.
- Higher utilization of machines, being able to pack containers more tightly in order to use every last bit of resources available.
- Priority bands for containers: Having different guarantees for containers of different priorities (e.g.: paying customers vs. free customers, latency sensitive vs. batch)
- Hierarchical containment: There’s an increasing demand to run containers inside containers to manage resources allocated to a user by higher-level allocators e.g.: A container-based PaaS/IaaS letting users create subcontainers per db query type, nominate sacrificial loads, etc.

We hope that this talk would help guide the kernel and userspace containers support for future resource isolation needs.


cgroups, userspace container management

Presentation Materials



  • Rohit Jnagal

    Google Inc


    Rohit Jnagal is the lead for container management tools at Google. Rohit has been working on resource isolation and shared-load machine performance at Google since 2009.

    Before Google, Rohit worked on a distributed virtual machine monitor at 3Leaf Systems, HPUX memory management at Hewlett Packard, and Veritas Volume Manager for Linux at Veritas (now Symantec).

    Rohit has been virtualizing bits of system software for more than 12 years.


Leave a private comment to organizers about this proposal