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

141–150 of 230 posts

Re: ClusterHQ is shutting down

#141

Post by matt_wulfeck »

> Mark Davis (CEO) explains this opportunity as, “Imagine if you were the 10th engineer at VMware. That’s the kind of experience you’re going to have with us at ClusterHQ.”

That was from a clusterHQ recruiter's email that I received just a week ago. I thought it was weird to sell a position in that way.

I don't find it unreasonable that a recruiter was hiring people while the company is closing down (what do they know?) I'm reminded it's always important to ask for specific financial information when hopping on to a startup. What's your revenue? Expenses? How long is your runway?

My condolences to anyone who had hope, time, and effort invested in clusterHQ stock options.

Re: ClusterHQ is shutting down

#142

Post by gtirloni »

tlb wrote: post #88
gtirloni wrote: post #76

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.

Many -- probably most -- ultimately very successful companies had near-death experiences. They aren't usually written about. Apple's near-death in 1997 is well documented. Tesla's is described in Ashlee Vance's biography of Musk. http://foundersatwork.com/ has firsthand stories about some others. They would have become full-death experiences if the CEO had said, "Hey everybody, we're near death, just FYI". So in the…

Maybe you have been seeing things through SV pink colored glasses for too long.

Companies everywhere are shutting down daily with proper warnings to customers, employees and users. It's not uncommon for companies to give several months (or even a year) of warning that they are winding down operations, won't be accepting new users, will honor contracts, etc. And they are doing the right thing.

Every time there's a post here about how people should keep at least 3 months of salary in case things go south, the general feeling is that whoever is living paycheck to paycheck must be stupid. However, when it's a CEO that couldn't do proper planning and screwed the lives of employees and users alike.. oh, sure, let's give the guy a break.

EDIT: Let me anticipate the argument here that if anyone's "lives" were screwed then it's their problem that they didn't understand the risks properly.

Re: ClusterHQ is shutting down

#143

Post by objectivefs »

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…

If you have access to an object store, you can get persistent file system storage for your containers using ObjectiveFS[0]. You can run it either on the hosts or inside the containers depending on your goal.

[0]: https://objectivefs.com

Re: ClusterHQ is shutting down

#144

Post by tazjin »

contingencies wrote: post #82
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…

Look at the list of PV types for Kube What I see is a lot of complex network filesystems, vendor-specific solutions and gateway protocols to expensive SAN solutions, which are already chalk and cheese in terms of features and performance. Arguably one of the best features of unix-style systems is support for arbitrary mount points, filesystem drivers and (network or local) blockstores. Storage is, essentially, a well…

> Storage is, essentially, a well-solved problem at the OS level. The fact that this option is marked "single node testing only – local storage is not supported in any way and WILL NOT WORK in a multi-node cluster" raises eyebrows.

Just to clarify this a bit: Persistent volumes as an API _resource_ in Kubernetes are independent of which node a container requesting them is scheduled on, which is why it makes little sense to have a host-independent host volume.

If you have your storage sorted out on the hosts you can use a "simple" volume to mount it correctly [1]. Scheduling can also be restricted to the correct nodes with that storage by using node selectors / labels.

1: http://kubernetes.io/docs/user-guide/volumes/#hostpath

Re: ClusterHQ is shutting down

#145

Post by shaybery »

ferrantim wrote: post #10

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.

1. What about the Flocker open source project? 2. Do you have plans to continue and maintain only the Flocker project?

Re: ClusterHQ is shutting down

#146

Post by bogomipz »

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…

I'm in a similar boat. Does Kubernetes have a persistent local storage API story on the horizon?

The one thing I have found on Mesos that I really liked are persisted volume resources:

http://mesos.apache.org/documentation/latest/persistent-volu...

I was hoping K8 has something similar but it didn't the last time that I looked.

Edit: I just looked at your 1st link. I see the PV docs, none of those fit my use case(local) unfortunately.

Re: ClusterHQ is shutting down

#147

Post by twblalock »

Benjamin_Dobell wrote: post #140
twblalock wrote: post #131

Earlier quoted context omitted.

> The relationship is wrong if you feel indebted to your investors and like they deserve thanks. They are partners in the business. Plus, they knew the risks. There is no reason to feel sorry for early-stage investors who lose money unless some kind of fraud was perpetrated on them.

Do you feel sorry for an athlete who hurts themselves? Do you feel sorry for wife of a stuntman who dies in an accident? Do you feel sorry for those with a gambling addiction? I can understand why you wouldn't at all feel sorry for an investor to the same extent as my examples above; presumably the investor hasn't ruined their life. However, my point is knowing the risks doesn't preclude someone from receiving empath…

> I can understand why you wouldn't at all feel sorry for an investor to the same extent as my examples above; presumably the investor hasn't ruined their life. However, my point is knowing the risks doesn't preclude someone from receiving empathy/sympathy.

I was not writing about a general case of risktaking: I was writing specifically about investors.

If I had been writing about athletes, stuntmen, gamblers, or any other kind of people, I would have written something that took into account the different contexts in which such people take risks.

I really don't see what you are trying to accomplish by changing the focus from a specific case to a general case.

Re: ClusterHQ is shutting down

#148

Post by bogomipz »

luka-birsa wrote: post #92
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…

Same here. Running ~100 app servers in K8S and the rest (databases & legacy apps) as regular GCE instances with PD drives. But long term going K8S-only is instrumental for us to prevent vendor lock-in. I really hope that storage for K8S happens this year in a form that is simpler than Gluster/Ceph/etc and preferably integrated. Right now we're using NFS and it's ok for the simple applications but I right now I wouldn…

Any idea how does GCE handles PD drives underneath your K8? Is it network-attacched storage? Are those NVMe drives I wonder?

Re: ClusterHQ is shutting down

#149

Post by bkanber »

Johnny555 wrote: post #32

It seems a little odd to do this 3 days before Christmas. Holiday depression is already a real problem, and making people unemployed a few days before the holiday sounds like a bad thing. And it's a terrible time to be job hunting. Why not hold on a few more weeks, let employees enjoy the holidays and announce in mid-January when employees can actually talk to hiring managers and get some good job prospects instead o…

They shut down because they couldn't secure series B funding. It's likely that they couldn't both make next payroll and also deal with severance and shutdown costs. Hard to hold on for a few more weeks if you can't actually pay anyone.

Re: ClusterHQ is shutting down

#150

Post by bogomipz »

geertj wrote: post #49
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…

> The options just aren't good enough. I'd be curious to understand your storage requirements as a production Kubernetes user. What would you like to see for performance, cost and RPO/RTO?

local NAND flash?
Post reply on HN