Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

ClusterHQ is shutting down

clusterhq.com

Post reply on HN
Print view View original

71–80 of 230 posts

Re: ClusterHQ is shutting down

#71

Post by dsp1234 »

calgaryeng wrote: post #63

- December 22, 2016: ClusterF *ed - December 15, 2016: Reflecting on a Year of Change and What’s to Come in 2017 ("All in all, 2016 was full of tests and triumphs and I can promise that 2017 will also be a big year for the company.") I'll be the first to admit I don't know anything about this company, but that's an interesting change of heart.

For reference, here is the post from 12/15 where the statement, " I can promise that 2017 will also be a big year for the company" was made by the CTO. Having the CTO make that statement, knowing that the company was shutting down, seems odd. Which implies it was not an orderly shutdown.

https://clusterhq.com/2016/12/15/container-predictions/

Re: ClusterHQ is shutting down

#72

Post by seanp2k2 »

tw04 wrote: post #60
chrissnell wrote: post #15

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…

>NFS? No way. Not performant. Really? https://www.spec.org/sfs2008/results/res2011q4/sfs2008-20111... And those are nothing compared to modern systems.

I've had many problems with NFS, but they were not performance related. Mostly FS hangs with some program waiting for IO that never comes.

Re: ClusterHQ is shutting down

#73

Post by Declanomous »

gkoberger wrote: post #65
jcoffland wrote: post #61

This is why it's a really bad idea to rely on PaaS/SaaS for your next project. When the company tanks (or cancels the product, changes the API, raises it's prices, etc.) you're screwed. Hope no one out there was heavily commited to FlockerHub. What we really need is better business models for supporting Open-Source.

Counter argument: if you don't rely on PaaS/SaaS, it'll take you 3-4x to launch. So, rely on them, but be ready to switch. A few bad things like this shouldn't take away from how services enable rapid development and iteration of ideas.

>Be ready to switch.

This why I include a weekly back up of our data from any of the PaaS/SaaS providers we use. Make sure you know exactly what is in the data you are backing up as well. You might find that data you really need isn't included in the backup/export files. There are a few sites where I have to take screen shots of configurations or rules to make sure I have all the data I need to switch over to a new process with minimal disruption.

I trust other people, but I don't want to endanger my organization by inextricably tying it's survival to that of another organization.

Re: ClusterHQ is shutting down

#74

Post by Nacraile »

BinaryIdiot wrote: post #43
Nacraile wrote: post #31

Earlier quoted context omitted.

> Failure is failure. It's not awesome. Why would you relish it? You're beating on a straw man. Nobody (very few people?) thinks the failure itself is good in and of itself. The mentality is to observe that even if a business endeavour ends in financial failure, that outcome is just one effect of a long process that had many effects, and that many of the other effects of the process were highly beneficial. Sure, some…

> You're beating on a straw man. How so? If you're stating that you're going to greatly enjoy your failure, how is that not making failure seem good? Can you greatly enjoy something that you don't consider awesome (greatly being the keyword)? Seems like we could split hairs over this in a variety of different ways. On the other hand the rest of your post discusses the value created out of a failed company which wasn'…

> On the other hand the rest of your post discusses the value created out of a failed company which wasn't related to the context of my post.

"not relevant"? The entire point of my response was to point out that the fundamental flaw in your argument is that you are ignoring the wider effects of the business process, while the "failure is success" mentality is all about taking into consideration those same wider effects.

> If you're stating that you're going to greatly enjoy your failure, how is that not making failure seem good? Can you greatly enjoy something that you don't consider awesome.

You don't enjoy the failure, but you can still enjoy the process that happens to lead to the failure, and the net outcome can still be positive. Once again: the mentality you're attempting to criticise is all about accounting for the entire process and all of its outcomes, and not narrow-mindedly focusing on just the financial outcome for the business.

> I think we're going to be arguing in straw man circles

If you continue to insist on equivocating between financial failure of the business (an individual outcome) and the holistic outcome of the entire process, yes. Well, I won't bother to continue responding, but that's beside the point.

Re: ClusterHQ is shutting down

#75

Post by X-Istence »

chrissnell wrote: post #15

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…

Ceph RBD is plenty fast for having a database on... was able to get better performance than fibre channel or NFS to a NetApp using Ceph, ran some nice large Oracle instances on VM's on top of OpenStack backed by Ceph RBD.

Re: ClusterHQ is shutting down

#76

Post by gtirloni »

Oh the immediate shutdowns! After going through the immediate Nebula shutdown, I'm glad we weren't depending on ClusterHQ.

Same question I had for Nebula: you had no idea that a month ago you'd have to shutdown, right?

I've started to follow these ex-CEOs so we avoid their next companies. This kind of shutdown is just terrible.

Re: ClusterHQ is shutting down

#77

Post by vacri »

BinaryIdiot wrote: post #43
Nacraile wrote: post #31

Earlier quoted context omitted.

> Failure is failure. It's not awesome. Why would you relish it? You're beating on a straw man. Nobody (very few people?) thinks the failure itself is good in and of itself. The mentality is to observe that even if a business endeavour ends in financial failure, that outcome is just one effect of a long process that had many effects, and that many of the other effects of the process were highly beneficial. Sure, some…

> You're beating on a straw man. How so? If you're stating that you're going to greatly enjoy your failure, how is that not making failure seem good? Can you greatly enjoy something that you don't consider awesome (greatly being the keyword)? Seems like we could split hairs over this in a variety of different ways. On the other hand the rest of your post discusses the value created out of a failed company which wasn'…

> If you're stating that you're going to greatly enjoy your failure

'Relish' in this context doesn't mean 'greatly enjoy', as in entertainment. It means simply 'to significantly value', as in valuing the learning opportunity, but not necessarily the event itself.

Re: ClusterHQ is shutting down

#78

Post by mathattack »

dsp1234 wrote: post #71
calgaryeng wrote: post #63

- December 22, 2016: ClusterF *ed - December 15, 2016: Reflecting on a Year of Change and What’s to Come in 2017 ("All in all, 2016 was full of tests and triumphs and I can promise that 2017 will also be a big year for the company.") I'll be the first to admit I don't know anything about this company, but that's an interesting change of heart.

For reference, here is the post from 12/15 where the statement, " I can promise that 2017 will also be a big year for the company" was made by the CTO. Having the CTO make that statement, knowing that the company was shutting down, seems odd. Which implies it was not an orderly shutdown. https://clusterhq.com/2016/12/15/container-predictions/

And that the CTO wasn't kept in the loop.

Re: ClusterHQ is shutting down

#79

Post by kureikain »

tw04 wrote: post #60
chrissnell wrote: post #15

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…

>NFS? No way. Not performant. Really? https://www.spec.org/sfs2008/results/res2011q4/sfs2008-20111... And those are nothing compared to modern systems.

I have lots of issue to get NFS works on some particular db as well. Such as RethinkDB and InfluxDB...

Re: ClusterHQ is shutting down

#80

Post by karthikb »

jcoffland wrote: post #70
gkoberger wrote: post #65

Earlier quoted context omitted.

Counter argument: if you don't rely on PaaS/SaaS, it'll take you 3-4x to launch. So, rely on them, but be ready to switch. A few bad things like this shouldn't take away from how services enable rapid development and iteration of ideas.

Why would it take you 3-4x longer to launch? Running your own servers in the cloud is not that hard. You can actually save time by not being restricted by the PaaS. I.e. if you have special needs, and you will, you can go in and hack the software.

If you don't have special needs, then you as a small team or company are taking on a burden that is large enough in scope for an entire company to focus on. It's why most startups just use GMail instead rolling their own. Sure it's easy to set up an email server, but now it's one more thing to think about.
Post reply on HN