lewq

15 ms·

151.
by lewq 11y ago
We are working on block device backends which integrate Flocker with OpenStack, EBS and more, as well as ZFS on local storage. Doing a tarball based export-import backend would be an interesting Flocker backend ;) With regards large volumes
152.
by lewq 11y ago
We're super excited about bringing portable volumes to lots of different orchestration frameworks, including Kubernetes. Any questions, we'll be hanging out here, so ask away ;)
153.
Data migration with Kubernetes and Flocker(clusterhq.com)
49 points by lewq 11y ago|19 comments
154.
by lewq 11y ago
For those who weren't at container camp in SF last week, the rest of the videos are also available here: https://www.youtube.com/playlist?list=PLcHZXHMeDzxUhStxW31Ct... I was going to do the demo that Ben does here but
155.
Docker Swarm with portable volumes and network [video](clusterhq.com)
26 points by lewq 11y ago|4 comments
156.
by lewq 12y ago
It's a work in progress but we hope to have something to show for it soon. :)
157.
by lewq 12y ago
Yup, it works now.
158.
Weave on socketplane acquisition(weaveblog.com)
14 points by lewq 12y ago|0 comments
159.
by lewq 12y ago
Yup, and also here's one with sound. :) https://vimeo.com/118119440 (recorded in the sauna room of an Austrian log cabin thanks to crate.io!)
160.
by lewq 12y ago
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 woul
161.
by lewq 12y ago
Thanks Solomon! Great to be working with you and lots of other nice folks in the ecosystem. :)
162.
by lewq 12y ago
Hey, Luke here, CTO at ClusterHQ. As well as being proud of this company milestone, I can't wait to get powerstrip ( https://github.com/clusterhq/powerstrip ) and flocker ( https://github.com/clusterh
163.
by lewq 12y ago
Yes, we are also glad to be involved in making "batteries included but removeable" really happen :)
164.
by lewq 12y ago
Definitely! We have https://github.com/ClusterHQ/powerstrip#additional-adapter-i... and https://github.com/ClusterHQ/powerstrip/issues/8 for ideas... please add more!
165.
by lewq 12y ago
We're working on moving to a static site generator :) That said one emergency mod_rewrite rule later and we fixed the issue - which was that the HN link went to the link without the trailing slash which was hitting the database! :&#x27
166.
by lewq 12y ago
Hey Michael! Powerstrip can be used to prototype extending anything which speaks the Docker API. So in theory it could be used in front of swarm, as well as behind it. I'm also interested in finding a way to prototype extensions to the
167.
by lewq 12y ago
And huge thanks to Alexis for proposing the meeting in the first place and inviting me along. ;)
168.
by lewq 12y ago
The current thinking from the meeting (correct me if I'm wrong) is that Docker extensions are late-bound named Docker containers; each extension defines a set of "drivers", which have privileged communication to the Docker da
169.
by lewq 12y ago
Luke here, the author of this post. I just wanted to say that Solomon did a great job pulling this meeting together, and that this meeting is an example of a pattern that Docker is using to get community feedback in gradually increasing cir
170.
by lewq 12y ago
We are working on solving this specific problem with Flocker at https://github.com/clusterhq/flocker/ - see http://docs.clusterhq.com/en/latest/introduction.html for a description of how
171.
by lewq 12y ago
Hey, Luke from ClusterHQ here. We're excited about being able to deploy applications described in fig files across multiple hosts, and even across multiple clouds, critically - including portable data volumes, and then being able to mo
172.
Using Weave and Docker for Spark Cluster with Visi(weaveblog.com)
13 points by lewq 12y ago|0 comments
173.
Is ZFS a suitable replacement for other Linux filesystems?(clusterhq.com)
70 points by lewq 12y ago|84 comments
174.
by lewq 12y ago
That's correct - at ClusterHQ (makers of Flocker) we are focusing on using ZFS for volumes. ZFS itself is a copy-on-write filesystem, but we're using snapshots so that we can do send/recv between hosts, as opposed to using sn
175.
by lewq 12y ago
Heya. Luke here, CTO at ClusterHQ. Happy to answer any questions about Flocker or more generally about Docker and storage!
176.
by lewq 12y ago
In HybridCluster we did I/O based load balancing. IOW, the primary metric used to decide when to juggle a container onto a less loaded machine was the aggregate disk busy % on the ZFS pool. This kept disk-bound workloads nice and fast
177.
by lewq 12y ago
Hey otterley, thanks for your comment! The homogeneous server recommendation is based on experience running tens of thousands of containers (mixed application and database containers) in production. In that case, when you have lots more con
178.
by lewq 12y ago
Hey, it's Luke here. I'm one of the founders of ClusterHQ and the author of this post. Happy to answer any questions or discuss any comments here. :)
179.
First European OpenZFS conference in Paris(meetup.com)
1 points by lewq 12y ago|0 comments
180.
Start Programming, It’s Not Too Late(hybridcluster.com)
4 points by lewq 13y ago|0 comments

More ›