Batcave moving to rhel10

Greetings everyone.

As you may know, I have been working on migrating machines in our
infrastructure from rhel9 to rhel10. Lots and lots of progress has
been made.

Today I am here to talk about batcave. :slight_smile:

This is our ansible control host along with a number of other things.

I have installed a new rhel10 batcave02 instance and I hope it’s
ready to swap in for batcave01. It’s unfortunately not super easy
to test everything because batcave02 does not have the network
acls that batcave01 has (ie, it cannot talk to other vlans).
While we could adjust this, I don’t think it’s really worth
waiting on.

So, this thursday (day after tomorrow), I would like to swap
over to it.

This would start around 17UTC and hopefully not last too long.

The rough plan is:

  • Kick everyone off batcave01/stop services on it.
  • rsync all data from /home/ /root/ /srv over to 02.
  • take 01 down completely.
  • rename 02 to 01, change it’s ip to 01, etc.
  • bring it up as the new 01

Note that we will be moving from:
ansible-core-2.14.18-3.el9.x86_64
to
ansible-core-2.16.16-2.el10.noarch

I’ve done what testing I could against hosts 02 can reach and
it all seems reasonable, but I am sure there could be some
playbooks that need adjustment.

If this time doesn’t work for you or you have other concerns,
please do share them.

Thanks!

5 Likes