Linux upgrades
I took advantage of the enforced, unplanned outage to update SLES 11 from SP2 to SP3.
All good – the only tiny gotcha was running the MySQL upgrade manually at the end.
Otherwise – looks happy so far.
I took advantage of the enforced, unplanned outage to update SLES 11 from SP2 to SP3.
All good – the only tiny gotcha was running the MySQL upgrade manually at the end.
Otherwise – looks happy so far.
I got bitten by the udev GUIDs when I did the move/upgrade/move back of my on-prem blog server this morning.
What should have been a simple evacuation of some VMs, upgrade the host to Windows Server 2012 R2, move the old VMs back in place – turned into another episode of handcrafting grub entries and checking that everything mounted back up correctly.
I got bit by this before – and I need to drill into the best practices for using SLES 11/udev in a virtual environment.
After an initial set of testing in 2011 – I am back testing the Azure IaaS capabilities for the blog.
Finally it arrived. Unboxed; find all of the bits needed (Micro USB power supply, USB keyboard, 2GB SD card); download the beta bits; boot and it worked.
I’ve not done anything beyond this – just checking the darn thing worked.
I’ve said it before – but hopefully there’s more to blog about again.
Less confidential stuff; lots more around Private Cloud and datacenter transformation.
Back to self hosting.
The blog has moved from home, to hosting at GoDaddy and up to Azure.
All had advantages – all had downsides. It’s the private cloud/public cloud conversation in a nutshell.
Ultimately GoDaddy performance let it down – especially for the database – was unacceptable. Their support was also pretty poor. As always “you get what you pay for” – but the bottlenecks for even simple, near static, WordPress sites were unacceptable.
Azure has a lot going for it – I am still keeping my eye on future features that are currently in beta. Performance was incredible; the process of getting apps updated was a little too cumbersome for me.
Self hosting really requires me to get dirty with the infrastructure and tuning – but the fact that I can lets me drive the performance. I’m also responsible for everything below the app – hardware, storage, network, connectivity, OS, security etc etc.
Recent Comments