4 ms·
No solution for persistent/statefull applications, which is a real disapointment, seeing as this is where I see orchestration systems currently breaking new gro
by fidget 11y ago
No solution for persistent/statefull applications, which is a real disapointment, seeing as this is where I see orchestration systems currently breaking new ground and coming up with interesting solutions. The contraint systems also doesn't look too impressive; can I do the equiq of Marathon's GROUP_BY contraint (i.e. AZ GROUP_BY 2 -> ensure I have instances running on >=2 machines w/ different AZ values)?
Also no maintenance primitives, but that's just me being in love with Mesos.
- maximegarcia 11y agoThat's always my first question. Let's have a pgsql "job", or a set of mongodb instance in cluster, backed by Docker. How do we orchestrate the data side ? Do we need to have special nodes where the data live in and set constraints for that ?
- binocarlos 11y agoI work for ClusterHQ and we make a tool called Flocker which aims to solve this problem.
- filearts 11y agoWhen the Hashicorp folk have a few minutes to breathe at their conf, I really hope that they could address the question of stateful apps. I imagine that users of Nomad also have persistent state to deal with and there must be a pattern that has emerged to solve this already?