SLES 16 upgrade time rolls around, and there were so many changes between versions, it was a good move to do a clean installation and move the content.
The summary list (as a reminder for next time).
backup the old server
deploy a new SLES 16 server, using PAYG license
install all of the dependencies (apache2, php8, php8 modules, mariadb, python, certbot)
drop the data disks (/wwwroot) from the old server, attach to the new server, check mount
change ownership and permissions for the new server
SELinux permissions (this bit me hard!)
switch DNS A records
check http is working
get certificates
check https is working
tweaks (php config, apache logging, daemon starts, cron jobs, and general tidying)
The biggest gotcha was old friends from SLES 8 days were gone, so having to re-learn and update skills for a modern Linux and re-learn SELinux.
Today I asked about the current state of “digital pen and paper”, as I’ve been eyeing the Moleskine Smart Writing System for a while.
Copilot, knowing some of the history fed to it, recommended:
My view
Given your background in technology leadership, meetings, workshops, architecture discussions, and note-taking, the Moleskine is attractive if your goal is:
“I want to write naturally in meetings and have an automatic digital copy.”
It’s less attractive if your goal is:
“I want a searchable knowledge-management system.”
Next I asked about the use of OneNote, and Obsidian, in a Microsoft centric workflow; with paper planner and note taking.
What I would do in your shoes:
Daily planning
Leuchtturm1917 Daily Planner or Moleskine Daily Planner Keep calendar, priorities, and tasks on paper.
Meetings
Surface Pro + Slim Pen + OneNote
Long-term knowledge
OneNote notebooks:
Leadership
Staff
Projects
Personal Development
Capture
Use Microsoft Lens on your phone to scan any important planner pages into OneNote.
This approach avoids the biggest weakness of smart notebooks:
They create digital copies of pages, but they do not organise knowledge nearly as well as OneNote.
The new v6 and v7 family Azure hardware is now broadly available, with plenty of capacity in the various regions.
The biggest changes are to network and storage drivers, moving to use the Microsoft MANA interface for network fabric, and a switch from SCSI to NVMe for disk.
Unlike previous SKU updates, e.g. v3 to v5, this family update requires some planning, especially on the Linux side.
There is a great PowerShell script to assist with the switch, which automates much of the roll forward, and provides a roll back as well.
In testing I found that two additional checks made this work flawlessly:
Ensure the latest Azure VM tools are are installed (azure-vm-utils)
Ensure the nvme drivers are installed (modprobe, dracut.conf)
Usual disclaimers before doing this – ensure you have a backup of your Linux VM before this work, you could be left with a somewhat broken VM. The rollback script works well.
I am really pleased with the solar panel/battery installation.
It’s not quite perfect – but we are banking enough power to only get billed during the dark, dark months.
One body of work over the coming months is to analyse a few years worth of data, and see if additional battery capacity would help this at all, and most critically whether it would give any return on investment.
During the summer we are generating during the day, filling the batteries, selling to the grid for credits, and then running off battery over night.
A decade ago I bought three Microsoft Surface Precision mice. I love the tactile feeling, and wired or bluetooth operation.
The last of these died over the weekend. A sad day. These mice are no longer made, used versions sell for hundreds on Amazon and eBay. My replacement was a Logitech MX Master 3S – which is performing well.
This website, and others I maintain, use CloudFlare as the free front-end to safeguard against brute force and DDOS attacks. For several of these sites the geo-fencing is set to US only.
Last time round the certs failed to renew. Some troubleshooting, and the secondary challenge from the Let’s Encrypt ACME client was getting firewall denied at the Cloudflare side.
There is no allow-list of IPs, nor a single ASN to allow.
Recent Comments