4 ms·

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 di

by jnoller 11y ago

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/docs/faq/ https://getcarina.com/docs/faq/ has more

whalesalad 11y ago
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 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 (on more than one node, and in more than one zone) and Ronco™ set it and forget it. Everything else is just noise. I love the ideas behind Kubernetes and Fleet/CoreOS (and this) but everyone is SO excited about these low level technologies that have yet to be composed into beautiful experiences. A tweet from Kelsey Hightower sums it up perfectly: It's going to be nearly impossible for people to evaluate and chose a container management platform during the gold rush. https://twitter.com/kelseyhightower/status/659182022410305536 https://twitter.com/kelseyhightower/status/65918202241030553...
- jnoller 11y ago
  I actually completely agree, and that's where I want to head with Carina. That user experience is the end-game.
- tbronchain 11y ago
  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. [1]: http://hypernetes.com http://hypernetes.com
- nevalau 11y ago
  Totally agreed with this and that was also our vision when we started to create Kontena (https://github.com/kontena/kontena https://github.com/kontena/kontena)

by jnoller 11y ago

whalesalad 11y ago

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 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 (on more than one node, and in more than one zone) and Ronco™ set it and forget it. Everything else is just noise. I love the ideas behind Kubernetes and Fleet/CoreOS (and this) but everyone is SO excited about these low level technologies that have yet to be composed into beautiful experiences. A tweet from Kelsey Hightower sums it up perfectly: It's going to be nearly impossible for people to evaluate and chose a container management platform during the gold rush. https://twitter.com/kelseyhightower/status/659182022410305536 https://twitter.com/kelseyhightower/status/65918202241030553...

jnoller 11y ago
I actually completely agree, and that's where I want to head with Carina. That user experience is the end-game.
tbronchain 11y ago
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. [1]: http://hypernetes.com http://hypernetes.com
nevalau 11y ago
Totally agreed with this and that was also our vision when we started to create Kontena (https://github.com/kontena/kontena https://github.com/kontena/kontena)