We're really pleased to have got a powerstrip adapter ready for flocker! Storage and networking are two important pieces of the Docker jigsaw and this means that you can compose both storage (flocker) and networking (weave, calico, socketplane) into the SAME container using the vanilla docker client.
Because it uses the vanilla docker client, it means that orchestration frameworks (mesos, k8s, fleet, swarm) will also be able to trigger the adapters.
Please note - powerstrip adapters are NOT designed to be used for production and are just a way to prototype docker extensions and experiment with composability of extensions in the Docker ecosystem :)
As I understand Flocker creates ZFS snapshots which are replicated between the nodes. Is this happening continuously and to all nodes? It's not really clear from the post.
Hey geku! We are not currently doing continuous replication between nodes, although we are working on a cloud block device backend which would allow synchronous replication using the underlying cloud block service.
In particular this would enable stateful failover... is that what you had in mind?
Flocker doesn't continuously replicate data at this point, but it is something we've considered adding. Today, replication happens only when you migrate the data volume. This blog gives a good step-by-step of what happens when a migration occurs: https://clusterhq.com/blog/deploying-multi-node-elasticsearc...
Do checkout the demo [1] I and Luke did earlier, using Powerstrip adapters for Weave and Flocker. It shows how a database container can be moved from one machine to another, keeping it's data and IP address!
8 comments
[ 4.7 ms ] story [ 25.7 ms ] threadBecause it uses the vanilla docker client, it means that orchestration frameworks (mesos, k8s, fleet, swarm) will also be able to trigger the adapters.
Please note - powerstrip adapters are NOT designed to be used for production and are just a way to prototype docker extensions and experiment with composability of extensions in the Docker ecosystem :)
In particular this would enable stateful failover... is that what you had in mind?
[1]: https://www.youtube.com/watch?v=8vVKtmd0ENw