Cloud computing and virtualisation

This ‘migratory nerd’ has moved back to OVH for hosting

This site now lives on an Alpine instance via Vultr.com public cloud. No more Azure Storage Blob web hosting (Microsoft) for me. And though it wasn’t a financial decision, I save money!

This is true despite the fact that I am moving my websites (including this one) away from OVHcloud and/or self-hosting, and am making a shift to using Microsoft 365. Some will never believe that nor accept what I have to say about it, but for me it’s the right decision.

While our internal tests (using private data that would need to be replaced with dummy data) of a full config were successful, frustrations with ‘our’ OpenStack hosting provider has led to the conclusion that it’s not a viable cloud alternative for us. In addition, is our finding that this approach involves more effort than if Terraform were a viable option, so if we were to continue with public cloud infrastructure we would prefer services with which we can successfully use Terraform.

I’ve been experimenting with Terraform to manage a number of Public Cloud Infrastructure instances (virtual machines) on OVHcloud. I hit an issue that affects both OVH API and OpenStack API on OVH. For OpenStack on OVH there are ‘Resource Not Found’ issues which seem to be experienced by others as well. For the OVH Terraform provider plugin there are issues with id’s being changed.

In my opinion, Windows is deceptively clear and smooth, but when once one really shines a light on it, one finds significant imperfections. Linux may feel a little less polished, but is more what you see is what you get (or better) — there are imperfections for a power user / developer like me, but those idiosyncrasies are minor compared to the more problematic ones found in Windows.