4 ms·
Flocker on CoreOS Linux
- darkr 11y agoCan someone explain the benefits of using flocker (on ec2, using ebs) over using an EBS sidekick-type container with fleet?
- binocarlos 11y agoHi, Flocker provides a neat abstraction to the underlying choice of storage. It has a range of different backends - EBS, OpenStack Cinder, ZFS (experimental), EMC scale.io, EMC Xtrem.io and many more. This means that if you decide to move your application to a different underlying platform - your storage specific application and infrastructure code remains the same and all that changes is a Flocker configuration. We have seen this benefit with a number of folks who need to support multiple infrastructures. Before Flocker - there were multiple code-paths depending on the underlying storage. Using Flocker - the same code-path was used.
- wereHamster 11y agoWhat about google persistent disks?
- ferrantim 11y agoHi, this is Michael, I work at ClusterHQ. We don't support running Flocker with a Google persistent disk backend yet, but would like to. If you add that idea here, it will help us prioritize https://feedback.clusterhq.com/forums/305266-feedback-for-flocker-container-data-volume-manager https://feedback.clusterhq.com/forums/305266-feedback-for-fl...
- tehbeard 11y agoDoesn't appear to support it, but the source is on github and in theory they're just a different google-flavoured ebs.
- ferrantim 11y agoYep, someone would need to write a Flocker storage driver for GPD, that's all. Could be us, could be the community. We have docs on building drivers: https://docs.clusterhq.com/en/1.3.0/gettinginvolved/plugins.html https://docs.clusterhq.com/en/1.3.0/gettinginvolved/plugins....
- binocarlos 11y agoIt's also worth pointing out that using Flocker, you are able to use other orchestration frameworks (such as Marathon). As a disclaimer - I work for ClusterHQ who make Flocker
- superuser2 11y agoWondering if this is really suitable for production databases. Is there support for performant synchronous replication ala the DRBD MySQL HA strategy? It would be awesome to fire up MySQL on a different box seconds later with no data loss.