Antsle Forum
Welcome to our Antsle community! This forum is to connect all Antsle users to post experiences, make user-generated content available for the entire community and more.
Please note: This forum is about discussing one specific issue at a time. No generalizations. No judgments. Please check the Forum Rules before posting. If you have specific questions about your Antsle and expect a response from our team directly, please continue to use the appropriate channels (email: [email protected]) so every inquiry is tracked.
Advice before beginning AntsleOS 0.5.0 to Whatever-is-Current Upgrade
Quote from tpearson on June 20, 2020, 11:27 amI have one of the original 32GB RAM / 2x500G SSD / 2X 2TB HDD Antsles...
It's running AntsleOS 0.5.0 and AntMan 0.11.1d
I'd like to ask you experts for some advice (or a reference to a guide that applies to updating something this out of date all the way to current versions of the OS and AntMan). Anything special I need to consider when things are this far out of date? (more info below these two long listings that follow)
Here's a df -h of the base file system:
root@myantsle:~ # df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 0 10M 0% /dev
/dev/sdc3 16G 5.3G 9.6G 36% /
tmpfs 3.2G 748K 3.2G 1% /run
shm 16G 0 16G 0% /dev/shm
cgroup_root 10M 0 10M 0% /sys/fs/cgroup
/dev/sdc2 127M 35M 92M 28% /boot
antlets 320G 128K 320G 1% /antlets
antlets/_aosupd-workspace 333G 13G 320G 4% /antlets/_aosupd-workspace
antlets/_templates 320G 128K 320G 1% /antlets/_templates
antlets/_templates/CentOS-7 321G 618M 320G 1% /antlets/_templates/CentOS-7
antlets/_templates/CentOS-7.1.lxc 321G 239M 320G 1% /antlets/_templates/CentOS-7.1.lxc
antlets/_templates/Debian8.5.lxc 321G 235M 320G 1% /antlets/_templates/Debian8.5.lxc
antlets/_templates/FreeBSD 321G 497M 320G 1% /antlets/_templates/FreeBSD
antlets/_templates/Server_2016_Std.kvm 333G 13G 320G 4% /antlets/_templates/Server_2016_Std.kvm
antlets/_templates/Ubuntu-18.04.kvm 322G 1.1G 320G 1% /antlets/_templates/Ubuntu-18.04.kvm
antlets/_templates/Ubuntu-18.04.lxc 321G 243M 320G 1% /antlets/_templates/Ubuntu-18.04.lxc
antlets/_templates/Win2016 326G 5.8G 320G 2% /antlets/_templates/Win2016
antlets/_templates/debian 321G 245M 320G 1% /antlets/_templates/debian
antlets/_tmp 320G 128K 320G 1% /antlets/_tmp
antlets/dc-2016 346G 26G 320G 8% /antlets/dc-2016
antlets/mx 322G 1.3G 320G 1% /antlets/mx
antlets/plex 351G 31G 320G 9% /antlets/plex
antlets/unifi 328G 7.6G 320G 3% /antlets/unifi
antlets/www 322G 1.5G 320G 1% /antlets/www
antlets/zimbra 329G 8.8G 320G 3% /antlets/zimbra
hdd 1.8T 113G 1.7T 7% /hdd
hdd/dc-2016 1.7T 0 1.7T 0% /hdd/dc-2016
hdd/plex 1.7T 0 1.7T 0% /hdd/plex
antlets/_docker 321G 5.9M 320G 1% /var/lib/docker... and here's the ZFS environment:
root@myantsle:~ # zfs list
NAME USED AVAIL REFER MOUNTPOINT
antlets 114G 320G 24K /antlets
antlets/_aosupd-workspace 12.1G 320G 12.1G /antlets/_aosupd-workspace
antlets/_docker 970M 320G 5.84M /var/lib/docker
antlets/_docker/0275dca03bc7ce1eacda472f40975f8355c55e8b99244ecbced422172c60ad77 24.2M 320G 514M legacy
antlets/_docker/046b55d78350dc454aa0f9555d8d346428ca1d49b6d6b93f79106ab35132849c 162K 320G 338M legacy
antlets/_docker/07301623a48236c6e07c0ade7405339a865e6d46faec3b011d4dc013c29b3552 28.3M 320G 472M legacy
antlets/_docker/1b94b6a8e166166131f844ee0f1299436fb6130020fd2c3d4fefa3a0b5535e0c 75.6M 320G 155M legacy
antlets/_docker/47840e0b10b4a149403f3ad263da9c62ea2abc47e672b27faf9d2ea35b67d49f 188K 320G 444M legacy
antlets/_docker/4aeef21616c57f7dee0ca9a2c4b8ee571b757b8eed556b048fe56a50b956ee1b 1.65M 320G 369M legacy
antlets/_docker/4b5b4674a714f5cb1bb8acb8de4842cab883097fff7682a7c735c12ea3978941 186K 320G 444M legacy
antlets/_docker/4d043782834d8863111b54fbce3ca5c5edcdc42d4d896c44d8d4300b50575d61 42K 320G 498M legacy
antlets/_docker/4d043782834d8863111b54fbce3ca5c5edcdc42d4d896c44d8d4300b50575d61-init 70K 320G 498M legacy
antlets/_docker/512944fbb6c9a93458580c00474c78884aa2dede955dff2dba5a9107d48d43bc 73.1M 320G 73.1M legacy
antlets/_docker/5a2119e7d49f96b4f9ab35fa515bb130b78e36ee67ad3003728d3623f6235158 291M 320G 444M legacy
antlets/_docker/62c6586f6da2f2a8d719bd87268a4e63dfe77d8734d124165ecb280e44e4064e 23.7M 320G 498M legacy
antlets/_docker/6dc28607450158b7e0473599604d4969ee7a67b0406e2edfbb765c12b1e8d6fb 184K 320G 338M legacy
antlets/_docker/8645b4022b2c98bacb0807f40e3928fc6b817958802ca0153ecc16a033c4bc7c 177M 320G 338M legacy
antlets/_docker/984db98cf1a3c7d398dbf5c27344588a2c91ff43c33c95208193499397d8e531 6.31M 320G 375M legacy
antlets/_docker/9ab2ecbecadbd180f05daa48e0c6160e3b5f0cd98bc4895cbccdad7e7bc4d616 45.8M 320G 519M legacy
antlets/_docker/a0077754b763c40f0384e113900925d7df6c4a4c6f2f4fa6a44b706bb4baaba1 1.79M 320G 474M legacy
antlets/_docker/a63e71443e9a2cda52029df0c933aaf4d0853613f0cc271cb445987e0552a8ca 26.2M 320G 98.2M legacy
antlets/_docker/aabcd09aefc3de4093b5a88b9bd8dcf4a067d7360fa2c6e27e85e4cbdbf52067 62.3M 320G 62.3M legacy
antlets/_docker/c31b72537b8bb48445b7949efa63b507e0b52c1ebdc9c4abc60fd452333d7383 29.2M 320G 367M legacy
antlets/_docker/cc13ce33ee8514dd0eaf31aeef3ca615ec3ec8b1ab0e77d166eb3fccf953b297 14.3M 320G 75.6M legacy
antlets/_docker/cdb805943e7fbd9a9ee0237b6fafc3ec9a74c535ba862666b6e7bab18f015d3d 65.4M 320G 162M legacy
antlets/_docker/d8493111c9dcbee698c51ac220e91c1dbc689e485ae38d6977c1d2336c6f2885 82.5K 320G 375M legacy
antlets/_docker/e1caa92b6d73c7252c5b3ed585fb9251e8037f44f05023489881b37611f0772e 5.49M 320G 80.4M legacy
antlets/_docker/e1f8700b07301edf5094ac6022cf208a04088b413c7bbac40a96eec316fb843f 104K 320G 514M legacy
antlets/_docker/e25642d8f00c8722a0f7412186a842c7cec5a6b83bc947ee756d82efa2f9421c 56.5K 320G 498M legacy
antlets/_docker/ead4d4e4e220e8b7528b6f06dbf1e1bc4988ba349db8040d255e4262ff8d7dd7 11.5M 320G 485M legacy
antlets/_templates 26.4G 320G 23K /antlets/_templates
antlets/_templates/CentOS-7 617M 320G 617M /antlets/_templates/CentOS-7
antlets/_templates/CentOS-7.1.lxc 377M 320G 239M /antlets/_templates/CentOS-7.1.lxc
antlets/_templates/Debian8.5.lxc 234M 320G 234M /antlets/_templates/Debian8.5.lxc
antlets/_templates/FreeBSD 993M 320G 496M /antlets/_templates/FreeBSD
antlets/_templates/Server_2016_Std.kvm 12.4G 320G 12.4G /antlets/_templates/Server_2016_Std.kvm
antlets/_templates/Ubuntu-18.04.kvm 1.08G 320G 1.08G /antlets/_templates/Ubuntu-18.04.kvm
antlets/_templates/Ubuntu-18.04.lxc 243M 320G 243M /antlets/_templates/Ubuntu-18.04.lxc
antlets/_templates/Win2016 10.2G 320G 5.71G /antlets/_templates/Win2016
antlets/_templates/debian 244M 320G 244M /antlets/_templates/debian
antlets/_tmp 91K 320G 91K /antlets/_tmp
antlets/dc-2016 25.8G 320G 25.5G /antlets/dc-2016
antlets/mx 1.20G 320G 1.21G /antlets/mx
antlets/plex 30.1G 320G 30.1G /antlets/plex
antlets/unifi 7.28G 320G 7.52G /antlets/unifi
antlets/www 1.43G 320G 1.44G /antlets/www
antlets/zimbra 8.66G 320G 8.75G /antlets/zimbra
hdd 112G 1.65T 112G /hdd
hdd/dc-2016 19K 1.65T 19K /hdd/dc-2016
hdd/plex 24K 1.65T 24K /hdd/plexI've shut down each antlet, taken a snapshot of each, and done a zfs send antlets/machine-name@snapshot-name | gzip > /hdd/backup-file-name.gz and copied those off the Antsle to separate storage for emergency use. I've also copied the entire /etc/libvirt directory structure off the Antsle to a backup location on another machine.
Any other tips or tricks before I "take the plunge"? Is it as simple as shutting down the antlets and doing "upgrade-edgelinux"? (remember I'm at AntsleOS 0.5.0) Does AntMan get updated in this process or do I "upgrade-antman" afterward? (or before?)
Thanks all! I look forward to getting access to all the new stuff!
Tim Pearson
I have one of the original 32GB RAM / 2x500G SSD / 2X 2TB HDD Antsles...
It's running AntsleOS 0.5.0 and AntMan 0.11.1d
I'd like to ask you experts for some advice (or a reference to a guide that applies to updating something this out of date all the way to current versions of the OS and AntMan). Anything special I need to consider when things are this far out of date? (more info below these two long listings that follow)
Here's a df -h of the base file system:
root@myantsle:~ # df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 0 10M 0% /dev
/dev/sdc3 16G 5.3G 9.6G 36% /
tmpfs 3.2G 748K 3.2G 1% /run
shm 16G 0 16G 0% /dev/shm
cgroup_root 10M 0 10M 0% /sys/fs/cgroup
/dev/sdc2 127M 35M 92M 28% /boot
antlets 320G 128K 320G 1% /antlets
antlets/_aosupd-workspace 333G 13G 320G 4% /antlets/_aosupd-workspace
antlets/_templates 320G 128K 320G 1% /antlets/_templates
antlets/_templates/CentOS-7 321G 618M 320G 1% /antlets/_templates/CentOS-7
antlets/_templates/CentOS-7.1.lxc 321G 239M 320G 1% /antlets/_templates/CentOS-7.1.lxc
antlets/_templates/Debian8.5.lxc 321G 235M 320G 1% /antlets/_templates/Debian8.5.lxc
antlets/_templates/FreeBSD 321G 497M 320G 1% /antlets/_templates/FreeBSD
antlets/_templates/Server_2016_Std.kvm 333G 13G 320G 4% /antlets/_templates/Server_2016_Std.kvm
antlets/_templates/Ubuntu-18.04.kvm 322G 1.1G 320G 1% /antlets/_templates/Ubuntu-18.04.kvm
antlets/_templates/Ubuntu-18.04.lxc 321G 243M 320G 1% /antlets/_templates/Ubuntu-18.04.lxc
antlets/_templates/Win2016 326G 5.8G 320G 2% /antlets/_templates/Win2016
antlets/_templates/debian 321G 245M 320G 1% /antlets/_templates/debian
antlets/_tmp 320G 128K 320G 1% /antlets/_tmp
antlets/dc-2016 346G 26G 320G 8% /antlets/dc-2016
antlets/mx 322G 1.3G 320G 1% /antlets/mx
antlets/plex 351G 31G 320G 9% /antlets/plex
antlets/unifi 328G 7.6G 320G 3% /antlets/unifi
antlets/www 322G 1.5G 320G 1% /antlets/www
antlets/zimbra 329G 8.8G 320G 3% /antlets/zimbra
hdd 1.8T 113G 1.7T 7% /hdd
hdd/dc-2016 1.7T 0 1.7T 0% /hdd/dc-2016
hdd/plex 1.7T 0 1.7T 0% /hdd/plex
antlets/_docker 321G 5.9M 320G 1% /var/lib/docker
... and here's the ZFS environment:
root@myantsle:~ # zfs list
NAME USED AVAIL REFER MOUNTPOINT
antlets 114G 320G 24K /antlets
antlets/_aosupd-workspace 12.1G 320G 12.1G /antlets/_aosupd-workspace
antlets/_docker 970M 320G 5.84M /var/lib/docker
antlets/_docker/0275dca03bc7ce1eacda472f40975f8355c55e8b99244ecbced422172c60ad77 24.2M 320G 514M legacy
antlets/_docker/046b55d78350dc454aa0f9555d8d346428ca1d49b6d6b93f79106ab35132849c 162K 320G 338M legacy
antlets/_docker/07301623a48236c6e07c0ade7405339a865e6d46faec3b011d4dc013c29b3552 28.3M 320G 472M legacy
antlets/_docker/1b94b6a8e166166131f844ee0f1299436fb6130020fd2c3d4fefa3a0b5535e0c 75.6M 320G 155M legacy
antlets/_docker/47840e0b10b4a149403f3ad263da9c62ea2abc47e672b27faf9d2ea35b67d49f 188K 320G 444M legacy
antlets/_docker/4aeef21616c57f7dee0ca9a2c4b8ee571b757b8eed556b048fe56a50b956ee1b 1.65M 320G 369M legacy
antlets/_docker/4b5b4674a714f5cb1bb8acb8de4842cab883097fff7682a7c735c12ea3978941 186K 320G 444M legacy
antlets/_docker/4d043782834d8863111b54fbce3ca5c5edcdc42d4d896c44d8d4300b50575d61 42K 320G 498M legacy
antlets/_docker/4d043782834d8863111b54fbce3ca5c5edcdc42d4d896c44d8d4300b50575d61-init 70K 320G 498M legacy
antlets/_docker/512944fbb6c9a93458580c00474c78884aa2dede955dff2dba5a9107d48d43bc 73.1M 320G 73.1M legacy
antlets/_docker/5a2119e7d49f96b4f9ab35fa515bb130b78e36ee67ad3003728d3623f6235158 291M 320G 444M legacy
antlets/_docker/62c6586f6da2f2a8d719bd87268a4e63dfe77d8734d124165ecb280e44e4064e 23.7M 320G 498M legacy
antlets/_docker/6dc28607450158b7e0473599604d4969ee7a67b0406e2edfbb765c12b1e8d6fb 184K 320G 338M legacy
antlets/_docker/8645b4022b2c98bacb0807f40e3928fc6b817958802ca0153ecc16a033c4bc7c 177M 320G 338M legacy
antlets/_docker/984db98cf1a3c7d398dbf5c27344588a2c91ff43c33c95208193499397d8e531 6.31M 320G 375M legacy
antlets/_docker/9ab2ecbecadbd180f05daa48e0c6160e3b5f0cd98bc4895cbccdad7e7bc4d616 45.8M 320G 519M legacy
antlets/_docker/a0077754b763c40f0384e113900925d7df6c4a4c6f2f4fa6a44b706bb4baaba1 1.79M 320G 474M legacy
antlets/_docker/a63e71443e9a2cda52029df0c933aaf4d0853613f0cc271cb445987e0552a8ca 26.2M 320G 98.2M legacy
antlets/_docker/aabcd09aefc3de4093b5a88b9bd8dcf4a067d7360fa2c6e27e85e4cbdbf52067 62.3M 320G 62.3M legacy
antlets/_docker/c31b72537b8bb48445b7949efa63b507e0b52c1ebdc9c4abc60fd452333d7383 29.2M 320G 367M legacy
antlets/_docker/cc13ce33ee8514dd0eaf31aeef3ca615ec3ec8b1ab0e77d166eb3fccf953b297 14.3M 320G 75.6M legacy
antlets/_docker/cdb805943e7fbd9a9ee0237b6fafc3ec9a74c535ba862666b6e7bab18f015d3d 65.4M 320G 162M legacy
antlets/_docker/d8493111c9dcbee698c51ac220e91c1dbc689e485ae38d6977c1d2336c6f2885 82.5K 320G 375M legacy
antlets/_docker/e1caa92b6d73c7252c5b3ed585fb9251e8037f44f05023489881b37611f0772e 5.49M 320G 80.4M legacy
antlets/_docker/e1f8700b07301edf5094ac6022cf208a04088b413c7bbac40a96eec316fb843f 104K 320G 514M legacy
antlets/_docker/e25642d8f00c8722a0f7412186a842c7cec5a6b83bc947ee756d82efa2f9421c 56.5K 320G 498M legacy
antlets/_docker/ead4d4e4e220e8b7528b6f06dbf1e1bc4988ba349db8040d255e4262ff8d7dd7 11.5M 320G 485M legacy
antlets/_templates 26.4G 320G 23K /antlets/_templates
antlets/_templates/CentOS-7 617M 320G 617M /antlets/_templates/CentOS-7
antlets/_templates/CentOS-7.1.lxc 377M 320G 239M /antlets/_templates/CentOS-7.1.lxc
antlets/_templates/Debian8.5.lxc 234M 320G 234M /antlets/_templates/Debian8.5.lxc
antlets/_templates/FreeBSD 993M 320G 496M /antlets/_templates/FreeBSD
antlets/_templates/Server_2016_Std.kvm 12.4G 320G 12.4G /antlets/_templates/Server_2016_Std.kvm
antlets/_templates/Ubuntu-18.04.kvm 1.08G 320G 1.08G /antlets/_templates/Ubuntu-18.04.kvm
antlets/_templates/Ubuntu-18.04.lxc 243M 320G 243M /antlets/_templates/Ubuntu-18.04.lxc
antlets/_templates/Win2016 10.2G 320G 5.71G /antlets/_templates/Win2016
antlets/_templates/debian 244M 320G 244M /antlets/_templates/debian
antlets/_tmp 91K 320G 91K /antlets/_tmp
antlets/dc-2016 25.8G 320G 25.5G /antlets/dc-2016
antlets/mx 1.20G 320G 1.21G /antlets/mx
antlets/plex 30.1G 320G 30.1G /antlets/plex
antlets/unifi 7.28G 320G 7.52G /antlets/unifi
antlets/www 1.43G 320G 1.44G /antlets/www
antlets/zimbra 8.66G 320G 8.75G /antlets/zimbra
hdd 112G 1.65T 112G /hdd
hdd/dc-2016 19K 1.65T 19K /hdd/dc-2016
hdd/plex 24K 1.65T 24K /hdd/plex
I've shut down each antlet, taken a snapshot of each, and done a zfs send antlets/machine-name@snapshot-name | gzip > /hdd/backup-file-name.gz and copied those off the Antsle to separate storage for emergency use. I've also copied the entire /etc/libvirt directory structure off the Antsle to a backup location on another machine.
Any other tips or tricks before I "take the plunge"? Is it as simple as shutting down the antlets and doing "upgrade-edgelinux"? (remember I'm at AntsleOS 0.5.0) Does AntMan get updated in this process or do I "upgrade-antman" afterward? (or before?)
Thanks all! I look forward to getting access to all the new stuff!
Tim Pearson
Quote from Daniel Scott on June 22, 2020, 10:17 amHi Tim-
I have some "generic" advice in the form of this doc article that talks about the upgrade. As you can see, it requires a fresh OS install.
I'm pretty sure that you'll want to first upgrade-antman and THEN back up all those antlets - one of the recent upgrades in the last few months was to allow antlets to be backed up from the older Gentoo based environment and run on the new CentOS based OS.
Hi Tim-
I have some "generic" advice in the form of this doc article that talks about the upgrade. As you can see, it requires a fresh OS install.
I'm pretty sure that you'll want to first upgrade-antman and THEN back up all those antlets - one of the recent upgrades in the last few months was to allow antlets to be backed up from the older Gentoo based environment and run on the new CentOS based OS.
Quote from tpearson on June 25, 2020, 1:37 pm... and AntsleOS 0.5.0 is "Gentoo" under the covers, so the upgrade-antman should succeed... correct?
Does the backup process in the latest antman also backup common system settings? Network config etc...? OR will I need to record and re-create after the fresh install?
Thanks for the help!
Tim
... and AntsleOS 0.5.0 is "Gentoo" under the covers, so the upgrade-antman should succeed... correct?
Does the backup process in the latest antman also backup common system settings? Network config etc...? OR will I need to record and re-create after the fresh install?
Thanks for the help!
Tim