Re: 32-->36?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This is reasonable. My suggestion would be

1. keep the original installation, create a snapshot of current configs and installed packages.
2. If possible, use a new server, or use a VM, to install F36.
3. Import the package and configs, fix everything that don't work
4. When most obvious problems are fixed, gradually move production to F36. (For example, night-time traffic go to F36, etc.) 5. After a while gradually move all production traffic to F36, keeping F32 intact (and update relevant databases with a script from F36) . If something breaks, immediately redirect traffic to F32.
6. When you are absolutely sure that everything's okay, move F36 there.


On 7/31/22 9:55 PM, Tom Horsley wrote:
On Sun, 31 Jul 2022 09:46:39 -0400
Go Canes wrote:

If you use a VM for the test-run
you could use snapshots

I always install a new fedora on a VM then after I like it, rsync
the VM to a disk partition, fix a few UUIDs and such in various
config files, then boot to it using the grub "configfile" option.
(Works with BIOS installs, probably more difficult with EFI).

I get to do the initial install and configure without taking the
system down by using a VM.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

Attachment: OpenPGP_0xEE978FA44869B163.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux