Re:Red Hat OpenShift 3 design document
by themgt on Sunday March 29, 2015 @03:10PM
(#9286040)
When CoreOS abandoned btrfs, it made me seriously start to consider the Joyent SDC stack, above all else just because ZFS can answer the storage question in a way that seemingly nothing on Linux will be able to provide in the near future
[ Parent
| on HN ]
I really, really like the Joyent SDC stack... It seems like a really nice solution. Though I wish they had the equivalent of S3 or Azure blob storage. Having to run your own VMs for archive storage seems like a pain, especially relative to the cost/amount of storage you get per VM.
Manta is part of SDC and implements a S3-like API (plus distributed map-reduce data processing).
Right. Ceph is what I've been using for that, and I'm assuming it'll be doable either in Docker or Linux KVM on SDC
Re:Red Hat OpenShift 3 design document
by justincormack on Sunday March 29, 2015 @04:47PM
(#9286413)
ClusterHQ is working on openzfs for containers too, on Linux.
Yep, and we think ZFS on Linux is ready real production use https://clusterhq.com/blog/state-zfs-on-linux/
well, micro services Paas does not care much about the storage: ephemeral storage is good. And you can re deploy the app with a click.
Re:Red Hat OpenShift 3 design document
by smarterclayton on Monday March 30, 2015 @10:40AM
(#9289795)
As part of OpenShift and Kubernetes we're building stack integration for Gluster, Ceph, NFS, iSCSI, and others into the core runtime environment (so you can on-demand provision storage at a cluster level). Micro services may not care much about storage, but everything else does.
https://github.com/GoogleCloudPlatform/kubernetes/blob/maste... captures the first draft of it, but there's a lot more work going on to let you bind storage on demand to Docker containers at a cluster level.