provisioning

It's not like little kids, learning the language for the first time are provisioning servers and installing from scratch.

Turns out there is a combo of physical servers and cloud-style provisioning/pricing: it's called bare metal clouds.

But at the time, they were a simple hosting provider with no API and no self-provisioning.

If the latter, you're back to the problem of provisioning tons of infrastructure for storing them...

Why not limit service scope to service provisioning, and normalize to a reasonable service-independent solution for high availability consensus and orchestration?

Don't use any kind of provisioning on vagrant just straight bootstrap.sh as honestly I don't like them.

I think it is actually quite undesirable for benchmark performance to be trivially computed from one parameter in machine provisioning.

Combining a rapid-provisioning, paid-hourly, physical hosting solution with strong privacy policies (e.g.

Edit: If you need a standardised provisioning system, start out with Ansible.

Or is he doing something else entirely like developing solutions that enable his company to enter new verticals or automating infrastructure provisioning and monitoring?

Your provisioning script is still point at correct version - 1.

Once you have that, provisioning, testing, failover, scaling and high availability get much easier.

Slower performance than "Thick Provisioning" where the entire allocated space is zeroed on allocation, instead of on write.

What is "Active Directory provisioning"?

Perhaps one that's more similar Thick Provisioning?

--- Copy on Write (COW) sounds like Thin Provisioning.