7 ms·
I've been giving this some thought because well who doesn't want to glue together cloud-y things. The only version I can see is one that runs on generic nix. i
by Havoc 7y ago
I've been giving this some thought because well who doesn't want to glue together cloud-y things.
The only version I can see is one that runs on generic nix. i.e. Spin up a VM on each cloud (and in house) and run a stack on that which software glues it together. Redundancy of sorts.
...however if that glue actually works I might as well do that with 20 sht tier providers and let the redundancy cover gloss over it. No competitive advantage for cloud providers - and each of the cloud's various competitive advantages are by definition not hybrid-able easily.
Scaling? You're now dealing with multiple cloud's worth of different approaches to scaling. Good luck scaling that hybrid style in a resilient way.
...and all of this is just VMs. Add the 50 other offerings the average cloud has all with different scaling, quirks and the hybrid dream is deader than dead.
- hardwaresofton 7y ago> ...however if that glue actually works I might as well do that with 20 sht tier providers and let the redundancy cover gloss over it. No competitive advantage for cloud providers - and each of the cloud's various competitive advantages are by definition not hybrid-able easily. YES! I might be the only one that wants this, but this is the future I want[0][1][2]. As technology makes it easier and easier to run a cloud compute/service provider, more competition will improve the offerings. I don't know what "shit tier providers" you're referring to, but I'm not convinced of the additional value AWS is delivering when running certain services (I'm thinking postgres) which are already pretty excellent by themselves. In the end you need to hire for AWS expertise (and spend time boning up anyway/reading docs when things go wrong), and for 90% of apps 1 mid-tier postgres instance (not even a highly-available) instance is all you need until you really get traction and can afford to hire someone to look after it. I think the future is going to see the bifurcation of management (making sure it's up/efficient) and hosting (providing hardware), and plummeting prices for both as more people enter the market. The super perplexing thing is that cloud providers jumped on the kubernetes bandwagon so quickly and this is what made this commoditization possible. Pessimistically speaking, this means either they're either about to butcher the cross-cloud usability of kubernetes (i.e. drift between EKS,AKS,etc) or kubernetes was a wolf in sheep's clothing from the start. I've been cautiously watching the Service Catalog[3] feature in Kubernetes because I think it's one of the places where vendors are exerting the most control to see how it goes -- I've brought it up before, but the "Service Catalog" is basically identical to the user Operator (Controller + Custom Resource Definition) pattern, but for some reason it's being treated as different... [0]: https://news.ycombinator.com/item?id=19170073 https://news.ycombinator.com/item?id=19170073 [1]: https://news.ycombinator.com/item?id=18121150 https://news.ycombinator.com/item?id=18121150 [2]: https://news.ycombinator.com/item?id=18015057 https://news.ycombinator.com/item?id=18015057 [3]: https://kubernetes.io/docs/concepts/extend-kubernetes/service-catalog/ https://kubernetes.io/docs/concepts/extend-kubernetes/servic...
- jacques_chester 7y ago> The super perplexing thing is that cloud providers jumped on the kubernetes bandwagon so quickly and this is what made this commoditization possible. My view remains that this was the purpose of Kubernetes: to scorch the earth ahead of ECS. Google had nothing to lose by doing so. > I've brought it up before, but the "Service Catalog" is basically identical to the user Operator (Controller + Custom Resource Definition) pattern, but for some reason it's being treated as different... The Service Catalog is based on the Open Service Broker API, which in turn was extracted from the Cloud Foundry Service Broker API. I hear folks say "it's not declarative", but typically this turns out to mean "it's not a YAML file". The fact is that OSBAPI is literally about telling the platform: hey, I need a service for this app. The brokerage process then works out how that's achieved. One such mechanism is Operators, there are also brokers that can apply Helm charts. The major difference is really about the CRDs as the point of interface. There's a fork or project somewhere which presents OSBAPI as CRDs (ie, YAML submitted to a remote REST endpoint) instead of as CLI commands (ie, JSON submitted to a remote REST endpoint). I feel like that's the best of both worlds. You keep the internal consistency of service discovery, service binding and service injection, plus the thing that really adds value: checking the YAML into revision control. Disclosure: I work for Pivotal. We compete with Red Hat / IBM. We also cooperate with them on OSBAPI and a number of other projects.
- hardwaresofton 7y ago> My view remains that this was the purpose of Kubernetes: to scorch the earth ahead of ECS. Google had nothing to lose by doing so. I agree, but avoided saying it to try to not seem like a crackpot. I'm fairly sure I have a comment to the same tune somewhere in the back of HN somewhere (or maybe somewhere else). Also in the sounds-like-what-a-crackpot-would-say category of thoughts -- I don't trust the CNCF. Similar to how I don't trust the OIN. > The Service Catalog is based on the Open Service Broker API, which in turn was extracted from the Cloud Foundry Service Broker API. I hear folks say "it's not declarative", but typically this turns out to mean "it's not a YAML file". The fact is that OSBAPI is literally about telling the platform: hey, I need a service for this app. The brokerage process then works out how that's achieved. One such mechanism is Operators, there are also brokers that can apply Helm charts. No comment about this, "declarative" is just tacked on onto things as marketing fluff these days. OSBAPI is plenty declarative to me; you're telling it what you want instead of how to provide what you want. > The major difference is really about the CRDs as the point of interface. There's a fork or project somewhere which presents OSBAPI as CRDs (ie, YAML submitted to a remote REST endpoint) instead of as CLI commands (ie, JSON submitted to a remote REST endpoint). I feel like that's the best of both worlds. You keep the internal consistency of service discovery, service binding and service injection, plus the thing that really adds value: checking the YAML into revision control. Though heavily simplified, do I have the difference (written below) correct? API version: 0) User wants cloud provided service X 1) User makes service catalog CLI request (a web request is made to the broker) CRD version: 0) User wants cloud provided service X 1) User creates a CRD 2) Controller sees created CRD and makes web request to the broker If this is right, it seems like a very small difference.
- goatinaboat 7y agoSpin up a VM on each cloud (and in house) and run a stack on that which software glues it together. Redundancy of sorts The thing is that using a cloud as a glorified hypervisor for home-baked VMs doesn’t work economically. Colo or even running a DC is cheaper. Cloud generally only makes financial sense if you are using the managed services. And of course the instant you do that you sacrifice portability to a greater or lesser extent. This is of course deliberate on the part of the cloud providers. It makes sense to pick 2 clouds and go all-in on them using their native and managed services to the maximum. You will need to maintain two parallel skillsets to do this. Completely forget about any layer that promises to abstract it, they are all red herrings if not outright snake oil. Whether that’s IBM consultants, or Terraform.
- namibj 7y agoI might end up using Azure of all for their hourly-priced Infiniband clusters. You can get an hour with ~25 TB ram for ~50$, d you have like 5~10GB/(physical)core. I don't want to use them, but it looks like there might not be any alternatives for only some very few hours on such a cluster.
- yipbub 7y agoWhy are the abstraction layers snake oil?
- goatinaboat 7y agoBecause either a) you are constrained to the lowest common denominators or b) the abstraction is something trivial like syntax and you still need to maintain two codebases (this is the problem with Terraform)
- tilolebo 7y agoAnd you're not even talking about data gravity... Moving data from one provider to another will quickly drive your costs up.
- windexh8er 7y ago