I’ve been bitten multiple times with the SLES service pack upgrade routine – with Red Carpet Enterprise (ouch – that’s a long time ago) and all of the various permutations of update tooling since.
Happy to say that SLES 12 SP1 to SLES 12 SP3 was zero fuss, fast and efficient. Less than five minutes per server on Azure and around 30 seconds of planned outage.
Good job SUSE team!
Since I wrote this post (a long, long time ago) – Office 365 now adds support for creating a trusted connector between your Linux/postfix environment and Office 365.
Much, much easier than before.
So as a reminder for me next time:
SASL for username/password
- Postfix main.cf settings
- Set up Office 365 connector and trusted IP end point
This is a reminder for myself mainly.
The update servers for SLES 11 SP3 on Azure changed – and there is a pretty well managed process to change the update repos.
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.
The process and change control for the build/rebuild is pretty straight-forward now.
Updated the main archive server from Windows Server 2008 R2 to Windows Server 2012 Release Candidate. Looks great – some nice features – and it seems to be faster than the previous version.
Also this blog is hosted as a SUSE Linux web server running on top of Hyper-V on top of Windows Server 2012 RC. Performance is solid. No issues to date.
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.