No edit summary |
No edit summary |
||
Line 58: | Line 58: | ||
| | | | ||
| A partkeepr frontend. Needs older php, 7.1 at max | | A partkeepr frontend. Needs older php, 7.1 at max | ||
|- | |- | ||
| 122 | | 122 | ||
Line 94: | Line 87: | ||
! Done | ! Done | ||
! Remarks | ! Remarks | ||
|- | |||
| 103 | |||
| LXC | |||
| postgresql.vm.nurd.space | |||
| Debian 10 | |||
| Dennis | |||
| New container with Debian 10, will need some work later (newer postgres, auth stuff) | |||
|- | |- | ||
| 133 | | 133 |
Revision as of 20:24, 31 January 2022
Coherence update 2022 | |
---|---|
Name | Coherence update 2022 |
Date | 2022/01/06 |
DateEnd | 2022/01/31 |
Location | Space |
Contact | Melan |
Attendees |
- Date still needs to be determined.
What
We are several versions behind on Proxmox on Coherence, as of writing the current version of Proxmox is 7.1-7 while we are still running 5.4-13(!). This means that we can't make any new LXC containers with newer distributions because they are simply not supported by Proxmox 5. Several attempts to upgrade Coherence have been made in the past, but I hope this time we can actually do it! It would also be nice if we could use this as an opportunity to clear old unused VMs and containers off Coherence.
Upgrading Proxmox path
A upgrade from 5 to 6 is needed, and from there on we can upgrade from 6 to 7. - [1] - [2]
Upgrade stuff (can be done already when backups are possible)
Please make backups first before you upgrade a VM or container
There should be a backup system available on backup-nfs before we start.
Debian containers should be Debian 10 at least before we can upgrade Proxmox, and Ubuntu 18.04 it seems.
Thinking steps required
* Backups - if we mess up, how do we bring things back?
- Need at least 4Tb to do this.
- Redundancy - Can we upgrade some other host and migrate? Would this be a good plan going forwards?
- Probably not required - Proxmox upgrade scripts should check containers before upgrades.
- Upgrades - All VkMs/Containers below need to be ticked off
Backup
A system called `notnotapp` has been setup and has 4x 1TB in raid 5 storage, meaning we have 3TB available for backup with redundancy. Although, roughly 1.8TB has been used for the mp3 share and the user data. Which should leave enough for VMs however, it is advised to remove your backup once the VM has been successfully upgraded to leave enough room.
A update of the user directory and mp3 share has finished at 10 January, rsync should be ran from time to time to keep notnotapp in sync with notapp. There is 966GB left free for VM backups.
Restore
Make sure you don't check unprivileged checkbox if you plan to do NFS inside the container!
List of LXCs/VMs
LXCs/VMs in need of OS upgrade
VMID | type | Name | OS | Done | Remarks |
---|---|---|---|---|---|
102 | LXC | parts.vm.nurd.space | Debian 9 | A partkeepr frontend. Needs older php, 7.1 at max | |
122 | LXC | saml.nurd.space | CentOS 6.6 | - | Zarya |
144 | VM | nurdservices.nurdspace.lan | Debian 9 | - | Critical - but this is a VM, so do is this blocking? |
LXCs/VMs that are upgraded
Some of these have been done previously
VMID | type | Name | OS | Done | Remarks |
---|---|---|---|---|---|
103 | LXC | postgresql.vm.nurd.space | Debian 10 | Dennis | New container with Debian 10, will need some work later (newer postgres, auth stuff) |
133 | LXC | egg.vm.nurd.space | Debian 10 | - | This is now Debian 10, but is a bit wacky. Might be a good idea to rebuild this one from scratch someday. |
101 | LXC | notapp.vm.nurd.space | Debian 10 | - | Critical - this is the main container that provides storage mounts to everywhere (egg, mpd). Update this one early. |
125 | LXC | ipam.vm.nurd.space | Debian 10 | - | Petraea |
140 | LXC | nurdbot.vm.nurd.space | Ubuntu 16.04 LTS | Update to Ubuntu 20.04.3 LTS | Crticial |
100 | LXC | spacesound.vm.nurd.space | Ubuntu 20.04.3 LTS | OK | Used to be VM 105 but now it's LXC 100 |
107 | LXC | nurdbotdev.vm.nurd.space | Ubuntu 20.04 LTS | OK | |
109 | LXC | asterisk | Debian 10 | Previously | |
118 | LXC | gopher | Debian 10 | OK | |
119 | LXC | gallery.nurd.space | Debian 10 | Previously | |
123 | VM | jarvis.vm.nurd.space | Hass OS 6.6 | - | |
124 | LXC | sdr.nurd.space | Ubuntu 20.04 LTS | OK | |
128 | LXC | revproxy01.nurd.space | Debian 10 | Previously | |
131 | LXC | influx.vm.nurd.space | Debian 10 | Previously | |
112 | VM | portal.nurd.space | Debian 10 | OK | CAREFULNEXTTIME: see that the http://pkg.switch.ch/switchaai/debian repo also follows along well!! |
LXCs/VMs that are not running
These can possibly be deleted or archived.
VMID | type | Name | OS | Done | Remarks |
---|---|---|---|---|---|
104 | LXC | status.vm.nurd.space | Debian 10 | Previously | |
106 | VM | jarvis-ng.vm.nurd.space | ? | Deleted | |
108 | VM | docker.vm.nurd.space | ? | Deleted | |
110 | LXC | bridger.lan.nurd.space | ? | Deleted | Petraea - An old routing box for prototyping different network layers. Could be folded. |
111 | LXC | Flunk | ? | - | |
113 | LXC | panopticon.vm.nurd.space | ? | Deleted | Petraea - An old monitoring setup (zabbix). Could be folded. |
114 | LXC | vinculum.vm.nurd.space | Debian 8 | Deleted | Petraea - An old IoT processing system. Could be folded. |
115 | LXC | wopr.vm.nurd.space | ? | Deleted | Gaming VM. Noone knows whose it is so fuck it :p Not used since 2015 |
116 | LXC | music.nurd.space | ? | Deleted | |
117 | LXC | snor.vm.nurd.space | ? | - | |
120 | LXC | mailng.vm.nurd.space | Debian 9 | Deleted | |
121 | LXC | mercator.vm.nurd.space | ? | - | Petraea |
127 | LXC | mail.vm.nurd.space | ? | - | |
135 | LXC | lightsjam.vm.nurd.space | ? | Deleted | backup has been transferred to Petraeas homedir |
137 | LXC | wol-server.vm.nurd.space | Debian 7 | Deleted | Petraea - Some central means of coordinating WoL handling with an API. Could be folded. |
141 | LXC | pretender.dhcp.nurd.space | ? | - | Petraea |
143 | LXC | neural.vm.nurd.space | ? | Deleted | Petraea - an old artistic neural network processor. Could be folded. |