thockingoog

14 ms·

1. 121.▲
   by thockingoog 12y ago

   Fair usage of resources and security isolation are two VERY different problems. Containers can be VERY good at resource isolation. Security has not really been figured out yet.
2. 122.▲
   by thockingoog 12y ago

   Thanks, I'll peek at it, too.
3. 123.▲
   by thockingoog 12y ago

   Interesting approach. I'm very much looking forward to hashing out the details.
4. 124.▲
   by thockingoog 12y ago

   This runs in a VM. We're not selling bare-metal (and even if we wanted to, Docker doesn't really have a co-tenancy model yet, so you'd have to buy full machines...)
5. 125.▲
   by thockingoog 12y ago

   We're in favor of standardizing the ideas, here.
6. 126.▲
   by thockingoog 12y ago

   (primary author of that python here) We have a number of things we're looking at for agents. One is derived from internal code, but has to clear some legal hurdles to OSS. One is a new codebase, but not quite up to the current spec.
7. 127.▲
   by thockingoog 12y ago

   LMCTFY is a "container" implementation by Google's traditional definition, which is very focused on isolation and less so on namespacing, filesystem, and packaging. We've added namespace support recently, but we do not
8. 128.▲
   by thockingoog 12y ago

   We're certainly still evaluating alternatives, here. Debian is much closer to what we use internally, and we wanted to start with sharing some of the internal ways we work.