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.
The JIRA for the external storage support is here https://issues.apache.org/jira/browse/MESOS-4355 Thanks, Guangya On Fri, May 13, 2016 at 2:16 AM, Wong, Steven <[email protected]> wrote: > 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 > ScaleIO) would be used to hold the database. > > slide deck: > http://www.slideshare.net/EMCCODE/emc-world-2016-code04-extending-mesos-for-storage-and-external-resources > > > > Video of demo: > https://www.youtube.com/watch?v=DL64mdYv5Lg&list=PLbssOJyyvHuWiBQAg9EFWH570timj2fxt&index=1 > > > > Note that the demo is using a very recent version of the DC/OS Marathon UI > > Steve Wong > > Developer Advocate > > EMC{code} – the open source advocacy group within EMC > > [image: emccode small] > > *CODE OPEN, DEPLOY EVERYWHERE* > > https://github.com/emccode > > *blog.emccode.com <http://blog.emccode.com>* > > > > @cantbewong > > > > *From:* [email protected] [mailto:[email protected]] > > *Sent:* Thursday, May 12, 2016 2:59 AM > *To:* [email protected] > *Subject:* Deploying MySQL and WordPress Docker Containers through > Marathon > > > > > > Hi , > > > > In case we are killing one of the instances running through Marathon UI. > It is able to bring up another replacing it. > > > > So, would like to know is it a replication of the previous instance which > was killed or it’s a new one. > > > > For example, if we are running a MySQL application through Marathon UI > and try on of its instance to kill. Will the information saved in the > database will be remain in the new one replacing it. > > > > > > Thanks > > > > > > > > > > > ------------------------------ > > > This message is for the designated recipient only and may contain > privileged, proprietary, or otherwise confidential information. If you have > received it in error, please notify the sender immediately and delete the > original. Any other use of the e-mail by you is prohibited. Where allowed > by local law, electronic communications with Accenture and its affiliates, > including e-mail and instant messaging (including content), may be scanned > by our systems for the purposes of information security and assessment of > internal compliance with Accenture policy. > > ______________________________________________________________________________________ > > www.accenture.com >
