4 ms·
It doesn't have to be an abstraction; it could have been an API standard for IaaS providers, with OpenStack itself serving as a reference implementation of said
by derefr 10y ago
It doesn't have to be an abstraction; it could have been an API standard for IaaS providers, with OpenStack itself serving as a reference implementation of said API. No higher-level concepts like containers; just saying things like "the VM lifecycle controllers in AWS, Google Cloud, Azure, DO, Linode, Rackspace, some random company's private cloud, etc., should all 'speak Nova', so that any Nova client can control VM lifecycles on any of them." Such providers could expose extra features with their own proprietary APIs (think e.g. the features exposed to the Gmail users through the web-app vs. through IMAP) but the standard protocol would at least be there for everything.
Not that asking AWS+GCP+Azure to commoditize themselves in such a way makes much economic sense, but that's the proposition.
- jacques_chester 10y agoIt'd be nice, but I don't think they will. Cloud Foundry gets around this by using BOSH for deployment; it essentially creates the kind of layer you're describing.