4 ms·

Have you looked at Joyent's Triton service? They claim they can run containers securely on bare metal, since the underlying kernel is Illumos (but it can run Li

Have you looked at Joyent's Triton service? They claim they can run containers securely on bare metal, since the underlying kernel is Illumos (but it can run Linux binaries and thus Docker containers). So the trade-off between isolation and efficient resource usage would disappear. On the one hand, they don't have all the same higher-level services as AWS, like ELB, let alone managed database services. On the other hand, I don't think I'd sleep well running anything based on EBS ever again, since EBS is so notorious for cascading failures.

duggan 11y ago
To my recollection, EBS has only suffered one such major failure, some time in 2011 (I was working for Engine Yard at the time). It hasn't factored strongly into my decision making since, other than that since AWS weathered it, they're likely now well prepared against it. AWS is a known quantity to me, Joyent is unfortunately not. I have a lot of time for Bryan Cantrill though, so I'm sure they're doing good stuff - I just don't have the extra cognitive cycles to handle a whole new base layer on top of all the scheduler / container stuff right now.
pradeepchhetri 11y ago
I got the chance to play with Joyent's Triton Elastic Container Service. Yes, the trade-off between resource isolation and efficient usage would disappear since they use SmartOS zones rather than Linux namespaces or cgroups to provide strong isolation between containers. They have forked Mesos[1] and added capability to run Triton containers as Mesos tasks[2]. Some of the questions which need to be explored: - Whether they provide some kind of built-in service discovery. - Whether all existing Mesos frameworks will support Triton based Mesos deployment since many frameworks make use of different networking modes, docker storage engine. [1]: https://github.com/joyent/mesos https://github.com/joyent/mesos [2]: https://www.joyent.com/blog/mesos-by-the-pound https://www.joyent.com/blog/mesos-by-the-pound

duggan 11y ago

To my recollection, EBS has only suffered one such major failure, some time in 2011 (I was working for Engine Yard at the time). It hasn't factored strongly into my decision making since, other than that since AWS weathered it, they're likely now well prepared against it. AWS is a known quantity to me, Joyent is unfortunately not. I have a lot of time for Bryan Cantrill though, so I'm sure they're doing good stuff - I just don't have the extra cognitive cycles to handle a whole new base layer on top of all the scheduler / container stuff right now.

pradeepchhetri 11y ago

I got the chance to play with Joyent's Triton Elastic Container Service. Yes, the trade-off between resource isolation and efficient usage would disappear since they use SmartOS zones rather than Linux namespaces or cgroups to provide strong isolation between containers. They have forked Mesos[1] and added capability to run Triton containers as Mesos tasks[2]. Some of the questions which need to be explored: - Whether they provide some kind of built-in service discovery. - Whether all existing Mesos frameworks will support Triton based Mesos deployment since many frameworks make use of different networking modes, docker storage engine. [1]: https://github.com/joyent/mesos https://github.com/joyent/mesos [2]: https://www.joyent.com/blog/mesos-by-the-pound https://www.joyent.com/blog/mesos-by-the-pound