On 2025-10-24 08:40, Mike Horwath wrote:
On Thu, Oct 23, 2025 at 05:50:22PM -0500, Richard Laager via mice-discuss wrote:
MICE is running Ubuntu 22.04, which has BIRD 2.0.8. In a few months, we can upgrade to 26.04 when it comes out, which will have at least BIRD 2.17.1 (which is the current release right now).
why not just do-release-upgrade to 24.04 and snag the newerver version that way?
As a general rule, I don't upgrade* production systems in place. To upgrade, I build a new VM, configure it (using Ansible), test, then cut over. This allows for more testing before going live, preserves the option to revert to the old VM as it was, generally reduces the downtime of the upgrade, forces/proves you have everything in Ansible, etc. It is more work, though. But not a lot more work, when it's VMs and configurations in Ansible. In this specific case, upgrading to 24.04 is also more heavy handed and more work than we need. We just need newer BIRD. As it turns out (Barry from IXP Manager pointed this out), the BIRD team has repositories for Ubuntu (and Debian) with newer versions available: https://pkg.labs.nic.cz/doc/?project=bird So I just used that. That was super easy, and it also means we can stay current on BIRD on an ongoing basis. * I'm using the word "upgrade" to indicate moving to a new distro, as opposed to "update" to indicate applying security patches. I imagine full devops would be to rebuild the whole thing (probably using containers) every time, even for patches. -- Richard