Live data from Hacker News

ClusterHQ is shutting down

clusterhq.com

21–30 of 230 posts

Re: ClusterHQ is shutting down

#21

This 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.

Thanks for posting, Michael, and I hope good things for you in the future.

Do you foresee Flocker living on in opensource form?

Re: ClusterHQ is shutting down

#22

How 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.

> Secondly, failure averse cultures don't actually prevent failures, and they have a tendency to squash innovation.

Celebrating failure and being failure averse have nothing to do with each other other than celebrating failure means you're probably not failure averse (but I would argue you lack empathy for the people you just lost money for and for the people you just lost jobs for).

Re: ClusterHQ is shutting down

#23
post #21

This 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.

Thanks for posting, Michael, and I hope good things for you in the future. Do you foresee Flocker living on in opensource form?

Yes, Flocker will remain open-source and my hope is that the community continues to improve it. Fli too, btw, for creating and managing ZFS snapshots https://github.com/ClusterHQ/fli

Re: ClusterHQ is shutting down

#24

How 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.

Having a culture where failure is okay is different from having a culture where failure is valued. Like the parent commenter said, if failure means you look back at what happened, learn some lessons, do better next time, then that's fine, you've gotten value out of failure. If you say "Hey, I got a failure out of the way," you're playing slots and falling victim to the gambler's fallacy.

> Make New Mistakes. Make glorious, amazing mistakes. Make mistakes nobody’s ever made before.

> Mistakes aren’t a necessary evil. They aren’t evil at all. They are an inevitable consequence of doing something new (and, as such, should be seen as valuable; without them, we’d have no originality).

So, was this mistake glorious, amazing, or new?

Re: ClusterHQ is shutting down

#25

How 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’…

It kind of reeks of entitlement to me. You would never see someone who is barely scraping by at a blue-collar job make a post celebrating getting laid off.

Re: ClusterHQ is shutting down

#26
Maybe "stateful containers" aren't a good idea. The whole point of containers is supposed to be that they can be duplicated and loaded into many machine instances. "Stateful containers" with changing databases inside can't be treated that way.

Re: ClusterHQ is shutting down

#27

We'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 to know what you are doing right now ? I'm planning to deploy a redis cluster on a private cloud and am wondering what to use.

do you use hostpath right now ?

Re: ClusterHQ is shutting down

#28
post #16

Earlier quoted context omitted.

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?

We are using DC/OS (Mesos) and found it to be much more feature rich for what our needs were.

Re: ClusterHQ is shutting down

#29

How 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’…

Well, a few thoughts.

1) It means you tried. Most people don't even get that far because they're too busy being terrified of failure 2) It means a hypotheses has been vetted and deemed not correct/successful, so something was learned. 3) I'm sure some of it is just trying to put a brave face on a shitty situation. If you try something, fail and then jump off a bridge because you're so donwn on yourself over it I'd say that's the wrong approach. No one likes failure, but having a more positive mindset about it is healthier than the alternative.

Re: ClusterHQ is shutting down

#30

We'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 to know what you are doing right now ? I'm planning to deploy a redis cluster on a private cloud and am wondering what to use. do you use hostpath right now ?

We don't put any persistent data into Kube. Everything goes into OpenStack instances (Ubuntu), orchestrated by Chef. We hate it. OpenStack SDN has been flaky, Chef is a pain and doesn't support the latest Ubuntu releases well, none of the devs or technical ops engineers like it.

It's my #1 goal for 2017: figure out persistent volumes for Kube.

Post reply on HN