I appreciate the honest tone of this announcement without any "incredible journey" nonsense.
ClusterHQ is shutting down
11–20 of 230 posts
Re: ClusterHQ is shutting down
#12That's a shame. I've always had great interactions with the ClusterHQ team. Michael, Mohit and Carissa have always been incredibly friendly when I've run into them at Dockercon. Unfortunately my engineering team was never able to fully integrate flocker into our production environment as we relied heavily on custom storage driver actions. Wish you folks all the best in your next projects.
Re: ClusterHQ is shutting down
#13Wow this surprising. I wonder what the reason for shutdown is? Flocker looked like a really cool product but was pretty involved setup wise when I was evaluating it. What are best options now for bare-metal? Ceph? NFS?
"What are best options now for bare-metal?"
Writing it yourself in raw x86 ASM.
Re: ClusterHQ is shutting down
#14Or maybe the technology wasn't correct for what most people are trying to do with Docker these days. Flocker never felt like it quite fit in the ecosystem along with Mesos, Kubernetes, etc. Great efforts guys, the tech is cool, but technology will continue to evolve and if you bought into something completely that doesn't fit nicely with the movement, you will get left behind. Edit: not sure why the downvotes, I was…
Since when is Flocker competing with those platforms? It's designed to work with them. http://kubernetes.io/docs/user-guide/volumes/#flocker
I never said it was competing. I said it didn't seem to fit nicely. I run several very large clusters, and we evaluated Flocker and it didn't fit nicely into ecosystem. It felt very "bolted on".
Re: ClusterHQ is shutting down
#15We've been running Kubernetes (500+ containers) in production for over a year now. I believe (and hope) that 2017 will be the year that persistent data storage will be solved. We are ready to move our data out of OpenStack and have our data services (Elasticsearch, Cassandra, MySQL, MongoDB) join the rest of our apps on Kube-orchestrated infrastructure.
But, we're not there yet. The options just aren't good enough. Look at the list of PV types for Kube [1]. You have technologies like Fibre Channel that are simply too expensive when compared with local storage on a Linux server. There's iSCSI, which is mostly the same story. Ceph is great for object storage but not performant enough for busy databases. GCE and AWS volumes are not applicable to our private cloud [2]. Cinder, to me, has the stench of OpenStack. Maybe it's better now? NFS? No way. Not performant.
I'm looking forward to seeing what shakes out in the next few months. It's just really hard to beat local storage right now.
[1] http://kubernetes.io/docs/user-guide/persistent-volumes/#typ...
[2] Beyond a certain size, it becomes more cost-effective to host your own Kubernetes cluster on managed or colocated hardware.
Re: ClusterHQ is shutting down
#16Earlier quoted context omitted.
Since when is Flocker competing with those platforms? It's designed to work with them. http://kubernetes.io/docs/user-guide/volumes/#flocker
I never said it was competing. I said it didn't seem to fit nicely. I run several very large clusters, and we evaluated Flocker and it didn't fit nicely into ecosystem. It felt very "bolted on".
I see, sorry for misunderstanding. What did you move to for persistent volumes?
Re: ClusterHQ is shutting down
#17This is Michael from ClusterHQ. Just wanted to say thanks to everyone in the community who helped make the last 2 and a half years a great experience. Sad that it's ending now, but excited for what's to come.
Michael, I appreciate this. I'm sure ClusterHQ was at times brutally hard work and you and team have worked hard on making things happen. I'm sorry it didn't work out and hopefully the future will be brighter with new lights.
Re: ClusterHQ is shutting down
#18How many people were employed at ClusterHQ? Honestly I never even heard of the company but I had heard of some of the open source projects. Maybe I'm just out of the loop. Also any information as to lessons learned, etc? Basically why it failed? Looking at the marketing material I didn't see anything really remarkable about it (nothing that stood out as a "oh this is why I would give them money") so I'm curious. > I’…
[deleted]
Re: ClusterHQ is shutting down
#19We've been running Kubernetes (500+ containers) in production for over a year now. I believe (and hope) that 2017 will be the year that persistent data storage will be solved. We are ready to move our data out of OpenStack and have our data services (Elasticsearch, Cassandra, MySQL, MongoDB) join the rest of our apps on Kube-orchestrated infrastructure. But, we're not there yet. The options just aren't good enough. L…
Curious if you've tried gluster at all. Using Kubernetes also and about to cross the threshold of stateful data - performance is important but not critical since we're using it in a fairly low volume, low throughput way, but it will grow over time and we want to future-proof it a bit. gluster seemed like the best-case fit for us but have done no empirical testing yet.
Re: ClusterHQ is shutting down
#20How many people were employed at ClusterHQ? Honestly I never even heard of the company but I had heard of some of the open source projects. Maybe I'm just out of the loop. Also any information as to lessons learned, etc? Basically why it failed? Looking at the marketing material I didn't see anything really remarkable about it (nothing that stood out as a "oh this is why I would give them money") so I'm curious. > I’…
Ed Catmull, Pixar cofounder and inventor of the Z-buffer, has a great take on mistakes and failure in his book Creativity, Inc. Here's a pretty decent summary:
https://www.brainpickings.org/2014/05/02/creativity-inc-ed-c...
Essentially, we're going to fail. It happens. Might as well get it out of the way.
Secondly, failure averse cultures don't actually prevent failures, and they have a tendency to squash innovation.