There are a lot of on-premise workloads which cannot be moved to someone else's remote cloud (for varying reasons). This is where OpenStack fills in the gap and provides something better than an ad-hoc brew-it-yourself cloud platform. That being said it still requires a good understanding of the requirements as well as a well chosen distribution to match the foreseen use-cases.
It's better to look at each situation, and decide whether the cloud is a good idea or not. Let's stop pretending this is the only good solution.
Anyway, infrastructure in cases like these is really like a public utility. No one says companies are putting their money maker in other's hands because they use public grid electricity (or sewage, or water supply, etc.).
Evernote's money-maker is the sum of those parts.
> No one says companies are putting their money maker in other's hands because they use public grid electricity (or sewage, or water supply, etc.).
Yeah, because that's generally not the product. Those are typically by-products. They happen after the product is produced.
And you can run a dedicated, private client if you want for most services.
A listenable connection to your client is entirely different than handing your entire infrastructure and data to a third-party. I fail to see the merit of putting your whole business in the hands of a potential competitor.
I'm curious as to what really made you hate it. From my vantage point of running openstack in production from Essex to Juno, Openstack Swift after Folsom release was the most reliable part of openstack outside of keystone and glance.
(Nevermind that it was also the easiest to upgrade as well).
Or you can use the ceph stuff, which is also pretty nice.
I narrowly avoided a long term (career-derailing) OpenStack assignment...four days in...oh, this is all based on OpenStack?...transfer approved
There was no CVE mailing list like other projects. We had to scrape their launchpad bug tracker. On top of that none of the package repos we checked (Canonical's, Debian's .. couple of others) would even have package updates for up to three weeks on some of the CVEs. We started building out own CI so we could build and patch ourselves. Then I got pulled from the open stack team onto something that was not a bottomless pit of haemorrhaging money.
I myself am a PTL (project technical lead) in one of the OpenStack projects and although I do understand where you are coming from I wonder what the gist of the experience you had was...
Care to share what experiences you have that made you think 'total dumpster fire'?
I know the software isn't perfect, but then what software is? Also I've seen that the OpenStack 'having a bad time experience' is as much of a cultural change as it is a software change; ie, OSS in general isn't a take and not contribute kind of thing, that's not how it really works/gets better.
Good riddance! Deploying Openstack Swift was a nightmare in my personal experience. A few outages and I decided I'll never work a job supporting it again.
If a recruiter mentions "Openstack" to me what I hear is a shamble mess of a services with components you'll be on-call for which will break in unique ways. Oh and of course you're expected to maintain the entire infrastructure while you do your normal job.
Just move to the cloud already.