[deleted]
AFAIK this is how Heroku works. Your app is running via lxc on a host next to a billion other ones.
Carina – High-Performance, Instant-On Docker Containers
11–20 of 37 posts
Re: Carina – High-Performance, Instant-On Docker Containers
#12How does this compare to Joyent Triton?
Re: Carina – High-Performance, Instant-On Docker Containers
#13Earlier quoted context omitted.
Exactly - we really struggled with this. A node (for example, when doing a Docker info when having $SWARM hosts) implies to the user physical isolation. As a distributed systems nerd, I pushed for "anything that doesn't make a contract it's on a different machine". Segment, slice, pod, chunk, block - something other than implying the isolation and therefore fault tolerance of the overall system. https://getcarina.com…
This level abstraction seems unnecessary. We need to just let-go of the concept of physical or virtual hosts. A machine should boot and join a cluster, advertising its capabilities (ssd drives, gpu's, enhanced networking, it's availability zone or region, etc...) and you should never need to think about that stuff, period. I don't care how many devices/segments/nodes/slices/dynos/widgets are in my cluster. I care tha…
I actually completely agree, and that's where I want to head with Carina. That user experience is the end-game.
Re: Carina – High-Performance, Instant-On Docker Containers
#14I'm surprised and a bit disappointed that this new platform still exposes users to the idea of a container host. In Carina lingo, you have to create a "cluster" and choose the number of "segments" in it.
Joyent's Triton avoids this completely: Their whole data centre is a Docker "host", and you never have to care about it. The way it should be.
(I'm not paid by Joyent, nor am I a customer -- I just like what they've done to push the model forward.)
Re: Carina – High-Performance, Instant-On Docker Containers
#15I'm surprised and a bit disappointed that this new platform still exposes users to the idea of a container host. In Carina lingo, you have to create a "cluster" and choose the number of "segments" in it. Joyent's Triton avoids this completely: Their whole data centre is a Docker "host", and you never have to care about it. The way it should be. (I'm not paid by Joyent, nor am I a customer -- I just like what they've…
This is honestly fantastic feedback and spot-on for the level of abstraction I want (and will) aim for. This is an early Beta, so things like this are top of mind.
Re: Carina – High-Performance, Instant-On Docker Containers
#16I'm surprised and a bit disappointed that this new platform still exposes users to the idea of a container host. In Carina lingo, you have to create a "cluster" and choose the number of "segments" in it. Joyent's Triton avoids this completely: Their whole data centre is a Docker "host", and you never have to care about it. The way it should be. (I'm not paid by Joyent, nor am I a customer -- I just like what they've…
This is honestly fantastic feedback and spot-on for the level of abstraction I want (and will) aim for. This is an early Beta, so things like this are top of mind.
Cool!
Re: Carina – High-Performance, Instant-On Docker Containers
#17Earlier quoted context omitted.
Exactly - we really struggled with this. A node (for example, when doing a Docker info when having $SWARM hosts) implies to the user physical isolation. As a distributed systems nerd, I pushed for "anything that doesn't make a contract it's on a different machine". Segment, slice, pod, chunk, block - something other than implying the isolation and therefore fault tolerance of the overall system. https://getcarina.com…
This level abstraction seems unnecessary. We need to just let-go of the concept of physical or virtual hosts. A machine should boot and join a cluster, advertising its capabilities (ssd drives, gpu's, enhanced networking, it's availability zone or region, etc...) and you should never need to think about that stuff, period. I don't care how many devices/segments/nodes/slices/dynos/widgets are in my cluster. I care tha…
Absolutely agree with that. We released yesterday a project called Hypernetes[1], which has been designed to solve the "I care that I have X GB of total memory and Y cpu's. I want to check a box to make an app or service highly available" problem.
Re: Carina – High-Performance, Instant-On Docker Containers
#18How does this compare to Joyent Triton?
Poorly.
Re: Carina – High-Performance, Instant-On Docker Containers
#19I'm surprised and a bit disappointed that this new platform still exposes users to the idea of a container host. In Carina lingo, you have to create a "cluster" and choose the number of "segments" in it. Joyent's Triton avoids this completely: Their whole data centre is a Docker "host", and you never have to care about it. The way it should be. (I'm not paid by Joyent, nor am I a customer -- I just like what they've…
Your assessment is accurate, unfortunately Triton does not address the issue of data locality, which is a pretty big problem unless you're already building your storage backend to be Smart Data Center aware.
To that extent, I'm not sure that tossing out the idea of hosts is great yet.
Re: Carina – High-Performance, Instant-On Docker Containers
#20I'm surprised and a bit disappointed that this new platform still exposes users to the idea of a container host. In Carina lingo, you have to create a "cluster" and choose the number of "segments" in it. Joyent's Triton avoids this completely: Their whole data centre is a Docker "host", and you never have to care about it. The way it should be. (I'm not paid by Joyent, nor am I a customer -- I just like what they've…
Your assessment is accurate, unfortunately Triton does not address the issue of data locality, which is a pretty big problem unless you're already building your storage backend to be Smart Data Center aware.