Guys,
Here is beauty version https://dcos.io/docs/1.7/overview/roadmap/
Regards,
Sam
Sent from my iPhone
> On May 13, 2016, at 3:35 PM, Guangya Liu wrote:
>
> Just FYI, the dc/os does have near term roadmap to enable support for
> "external volume storage":
>
Just FYI, the dc/os does have near term roadmap to enable support for
"external volume storage":
https://github.com/dcos/dcos-docs/blob/master/1.7/overview/roadmap.md#pluggable-external-volumes
, once this was enabled in open source dc/os, you can use this feature to
manage your stateful services.
There was a presentation given on this last week at the EMC World conference,
demonstrating migration of a MySQL server across cluster nodes, with persistent
storage on an external volume. For this use case, a cloud volume (such as AWS
EBS), or a networked attached storage volume (such as
The MySQL service automatically clusters with a single primary and any number
of replicas. If a replica fails, Marathon will replace it, and the new instance
will automatically bootstrap itself with a copy of the DB and join the cluster.
If the primary should fail, one of the replicas will be
You can do it either way actually. The default case is for it to bring up
a fresh instance of MySQL, since the sandbox the application starts in is
clean. Mesosphere had a recent blog post about using persistent storage in
Marathon (
5 matches
Mail list logo