Coherence update 2022: Difference between revisions

From NURDspace
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Event
{{Event
|Name=Coherence update day 2022
|Name=Coherence update 2022
|Date=2022/01/06
|DateEnd=2022/01/31
|Location=Space
|Location=Space
|Contact=Melan
}}
}}
* Date to still be determined.
* Date still needs to be determined.


= What =
= 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.  
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.
- [https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0]
- [https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0]


== Upgrade stuff (can be done already when backups are possible) ==
== Upgrade stuff (can be done already when backups are possible) ==
Line 14: Line 22:


Debian containers should be Debian 10 at least before we can upgrade Proxmox, and Ubuntu 18.04 it seems.
Debian containers should be Debian 10 at least before we can upgrade Proxmox, and Ubuntu 18.04 it seems.
== Thinking steps required ==
<del>* Backups - if we mess up, how do we bring things back?
- Need at least 4Tb to do this.</del>
* 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.


== List of LXCs/VMs ==
== List of LXCs/VMs ==
<span id="lxcsvms-in-need-of-os-upgrade"></span>
<span id="lxcsvms-in-need-wos-upgrade"></span>
=== LXCs/VMs in need of OS upgrade ===
=== LXCs/VMs in need of OS upgrade ===


Line 32: Line 53:
| Debian 9
| Debian 9
| -
| -
|
| Petraea - a junky attempt at trying to come up with a common deployment standard for Nurdspace, and some mechanism of applying security standards. Could be folded.
|-
|-
| 101
| 101
Line 39: Line 60:
| Debian 9
| Debian 9
| -
| -
| Critical  
| Critical - this is the main container that provides storage mounts to everywhere (egg, mpd). Update this one early.
|-
|-
| 102
| 102
Line 46: Line 67:
| Debian 9
| Debian 9
| -
| -
|
| A partkeepr frontend. Zarya?
|-
|-
| 103
| 103
Line 89: Line 110:
| -
| -
| Crticial
| Crticial
|-
| 142
| LXC
| arbiter.vm.nurd.space
| Debian 10
| -
| Prev notes said “move to docker”, can be delete?
|-
|-
| 144
| 144
Line 109: Line 123:
=== LXCs/VMs that are upgraded ===
=== LXCs/VMs that are upgraded ===


Some of these have been tdone previously
Some of these have been done previously


{| class="wikitable"
{| class="wikitable"
Line 184: Line 198:


<span id="lxcsvms-that-are-not-running"></span>
<span id="lxcsvms-that-are-not-running"></span>
=== LXCs/VMs that are not running ===
=== LXCs/VMs that are not running ===


Line 222: Line 237:
| ?
| ?
| -
| -
|
| Petraea - An old routing box for prototyping different network layers. Could be folded.
|-
|-
| 111
| 111
Line 236: Line 251:
| ?
| ?
| -
| -
|
| Petraea - An old monitoring setup (zabbix). Could be folded.
|-
|-
| 114
| 114
Line 243: Line 258:
| Debian 8
| Debian 8
| -
| -
|
| Petraea - An old IoT processing system. Could be folded.
|-
|-
| 115
| 115
Line 250: Line 265:
| ?
| ?
| -
| -
|
| Gaming VM. Zarya?
|-
|-
| 116
| 116
Line 278: Line 293:
| ?
| ?
| -
| -
|
| Petraea
|-
|-
| 127
| 127
Line 299: Line 314:
| Debian 7
| Debian 7
| -
| -
|
| Petraea - Some central means of coordinating WoL handling with an API. Could be folded.
|-
|-
| 141
| 141
Line 306: Line 321:
| ?
| ?
| -
| -
|
| Petraea
|-
|-
| 143
| 143
Line 313: Line 328:
| ?
| ?
| -
| -
|
| Petraea - an old artistic neural network processor. Could be folded.
|}
|}

Revision as of 21:52, 10 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.

List of LXCs/VMs

LXCs/VMs in need of OS upgrade

VMID type Name OS Done Remarks
100 LXC rollout.vm.nurd.space Debian 9 - Petraea - a junky attempt at trying to come up with a common deployment standard for Nurdspace, and some mechanism of applying security standards. Could be folded.
101 LXC notapp.vm.nurd.space Debian 9 - Critical - this is the main container that provides storage mounts to everywhere (egg, mpd). Update this one early.
102 LXC parts.vm.nurd.space Debian 9 - A partkeepr frontend. Zarya?
103 LXC postgresql.vm.nurd.space Debian 9 - Is seriously broken :< needs fixing (plz save the db)
112 VM portal.nurd.space Debian 8 - Zarya
122 LXC saml.nurd.space CentOS 6.6 - Zarya
125 LXC ipam.nurd.space Debian 7 - Buzz
133 LXC egg.vm.nurd.space Debian 9 - Critical
140 LXC nurdbot.vm.nurd.space Ubuntu 16.04 LTS - Crticial
144 VM nurdservices.nurdspace.lan Debian 9 - Critical

LXCs/VMs that are upgraded

Some of these have been done previously

VMID type Name OS Done Remarks
105 VM spacesound.vm.nurd.space Ubuntu 20.04.3 LTS OK
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

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 ? -
108 VM docker.vm.nurd.space ? -
110 LXC bridger.lan.nurd.space ? - Petraea - An old routing box for prototyping different network layers. Could be folded.
111 LXC Flunk ? -
113 LXC panopticon.vm.nurd.space ? - Petraea - An old monitoring setup (zabbix). Could be folded.
114 LXC vinculum.vm.nurd.space Debian 8 - Petraea - An old IoT processing system. Could be folded.
115 LXC wopr.vm.nurd.space ? - Gaming VM. Zarya?
116 LXC music.nurd.space ? -
117 LXC snor.vm.nurd.space ? -
120 LXC mailng.vm.nurd.space Debian 9 -
121 LXC mercator.vm.nurd.space ? - Petraea
127 LXC mail.vm.nurd.space ? -
135 LXC lightsjam.vm.nurd.space ? -
137 LXC wol-server.vm.nurd.space Debian 7 - 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 ? - Petraea - an old artistic neural network processor. Could be folded.