iaas

Every IaaS provider (Google, Amazon, Azure) has added a code hosting service or will do so in the future.

We do not focus on virtual machine images that can be launched on your favorite IaaS.

These are similar changes you would need to make if you were to switch IaaS providers & remove vendor lock-in.

IaaS tooling is really only relevant to people maintaining a private cloud, which is a shrinking piece of the market.

And you're never investing in IT if you are doing IaaS or PaaS: you're just paying a third party for a temporary good.

Having your code hosted here will increase lock-in which is the best way for the IaaS provider to increase margins in the future.

Joyent has a capable basic cloud IaaS offering, but its feature set is strongly oriented toward cloud-native use cases, and it is highly developer-centric.

But in the middle there's an awful lot of mechanism required to run an IaaS and OpenStack is the only serious opensource contender around.

I guess their plan is to focus on software on top of Azure, cause as IaaS it's simply not competitive.

On the short term we'll add documentation how to use the Travis DPL gem to push to the IaaS providers.

Getting this right is hard and I wonder if many IaaS providers will get this right.

Our company manages the IaaS tier of IBM Cloud using OpenStack.

Nitpick: 2 typos in one sentence: "From lightning fast IaaS to innovate container technology" should be "From lightning-fast IaaS to innovative container technology".

And in the end the problem they solve is "running applications", and for some applications that don't strictly require IaaS they are competitors.

I would put it differently: OpenStack is how you do IaaS with long-lived, mutable server instances ("pets").

Kubernetes is how you do IaaS with immutable, disposable application instances ("cattle").