Fog Update 1.4.4
-
Hello, I’m running old version of FOG 1.4.4 with a node also on 1.4.4.
Both of these run on proxmox 6.2.9 debian strech containers.I’d like to update to a newer version of fog, which one is the most stable at the moment?
I also have around 30 Images, should I keep a copy of my config and just reinstall a newer version of fog on top of it ? -
How many workstations running the FOG client do you have?
There may be more value in spinning up a new server than an in place upgrade. As for what OS, any of the big three. I’m going to list them in my preferred order, but I’m a rhel guy. Centos 8, Debian 10, or Ubuntu 20.04.
-
@Kamiii said in Fog Update 1.4.4:
Both of these run on proxmox 6.2.9 debian strech containers
That means you want to update to Debian Buster (10) as well? While we try to cover a lot of the changes between dist-upgrades I can’t promise you this will go without glitch. You definitely want to use FOG 1.5.9 (latest official release) and not one of the earlier ones that had more issues with dist-upgrades.
As George said you might be way faster setting up new containers and importing the database, copying image files than doing the update.
-
@george1421
Hello, at the moment none of the workstation run FOG client, I just took over the IT position and the previous IT guy never updated FOG…
As for the images, how do I copy them over to a new fog node? -
@Kamiii said:
As for the images, how do I copy them over to a new fog node?
Take a full copy of everything in
/images/(preserving access rights). You might want to check in/opt/fog/.fogsettingsto see if the default location/images/has actually been used.Other than that you want to read through this as well: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG
-
@Kamiii said in Fog Update 1.4.4:
As for the images, how do I copy them over to a new fog node?
When you setup a new FOG server make sure you place the /images on its own partition. If you use Centos to install the default will be to place the root partition on 50GB and then give /home the remainder of the disk. For FOG I would select custom configuration and then select auto create partitions. Then rename /home to /images sections and then set that configuration. This will keep you from accidentally filling up the partition with imaging and killing your OS and database. The other option if creating in a VM pick the minimum size of disk required by your OS and then install the OS. Once the OS is installed create a second disk for your images and then mount that new disk over the /images mount point, THEN install FOG. This will then keep your disk images on a different disk and away from your OS disk.
