Open everpeace opened 10 years ago
so in standalone/, vagrant up would show mesos and docker-mesos?
Ex:
Same strategy for multinode/.
What's your view on this @everpeace
What I've image is that,
In standalone, $ vagrant up --provider=docker
pulls mesosphere/mesos
image from Docker hub and run it and provision mesos-master/slave with cookbook-mesos, and installs marathon and chronos.
In multinode, most part is the same except that we might need some network configurations between docker containers.
Docker can spin up containers more quickly than virtualbox and aws. And vagrant supports docker provider.
We could utilize mesosphere's container mesosphere/mesos
I would like to keep using [cookbook-mesos] to provision
mesos-{master|slave}
.