https://www.wplug.org/api.php?action=feedcontributions&feedformat=atom&user=LdaberkoWPLUG - User contributions [en]2026-10-31T12:26:32ZUser contributionsMediaWiki 1.43.9https://www.wplug.org/index.php?title=2024_Server_Migration&diff=50612024 Server Migration2024-10-30T04:15:00Z<p>Ldaberko: </p>
<hr />
<div>This page is to collect information about our current configuration and options for switching to a new server going forward, since CentOS 7 goes end-of-life at 2024-06-30. Please feel free to edit to add missing information or correct errors.<br />
<br />
= Migration Progress =<br />
== Servers ==<br />
There are 3 current servers: <br />
* Linode - The legacy server running CentOS7. Mediawiki was migrated off due to bot hits driving up the load. This was also done to reduce surface attack area of an EOL CentOS.<br />
* Penguin - The current production server running *only* mediawiki.<br />
* Nestling - The current development/staging server. <br />
=== Penguin ===<br />
This server is now serving Mediawiki. It's a virtual server:<br />
* Name: penguin<br />
* OS: Debian 12<br />
* Region: Atlanta<br />
* Plan: Nanode 1GB<br />
* IPv4: 139.144.29.132<br />
* IPv6: 2600:3c02::f03c:94ff:fe10:c62f<br />
=== Nestling ===<br />
Currently doing dev on it. It'll become the staging server once migration is complete.<br />
* Name: nestling<br />
* OS: Debian 11<br />
* Region: Chicago<br />
* Plan: <s>Nanode 1GB</s> Linode 2 GB due to high memory use of Mailman 3.<br />
* IPv4: 172.234.26.233<br />
* IPv6: 2600:3c06::f03c:95ff:fed6:b745<br />
This server was selected to run this OS version and location because it was the only image and location that featured cloud-init which was necessary for automated builds. Once Debian 12 gets that feature or we find something better, we'll migrate again which should be much simpler.<br />
<br />
== Ansible ==<br />
From https://www.ansible.com<br />
<q>Ansible is an open source IT automation engine that automates provisioning, configuration management, application deployment, orchestration, and many other IT processes.</q><br />
I am using ansible to automate most of the setup and migration. Right now it does 99% of the work with some web interface clicking required here and there.<br />
<br />
== Setup Steps ==<br />
=== Completed ===<br />
Here are the steps completed:<br />
* Create or rebuild new linode, with cloud-init that adds admin users and ssh public keys.<br />
* Set hostname, /etc/hosts, disable root ssh login<br />
* Add board group and create board home directory<br />
* apt update<br />
* Install apache, mariadb, php<br />
* Install and run certbot<br />
* Install mediawiki and restore images and sql data<br />
* Mail - mua, postfix, opendkim, SPF, DKIM, DMARC<br />
* Backup mediawiki data and config for future rebuild and migration<br />
* Restore mediawiki data and config<br />
* Add ufw management and set up firewall<br />
* fail2ban complete and added to penguin also<br />
* mail aliases<br />
* established staging.wplug.org subdomain<br />
* mailman3 installation finally successful<br />
* limit outbound mail in postfix so we don't spam people while testing<br />
* ran out of memory on the 1GB plan so bumped it up to 2GB RAM<br />
* added 512MB /swapfile on top of the 512MB swap partition<br />
* mailman 2.1 to 3 migration <br />
* mailman 3 backup and restore<br />
* move django /admin page to a different url<br />
* apache http and www redirect to staging.wplug.org<br />
<br />
=== Working On ===<br />
* Cleaning up Legacy data<br />
<br />
=== To Do ===<br />
* Create a new index page to point to wiki and mailman<br />
* Migrate users and data<br />
* Backup and restore using ansible<br />
<br />
<br />
= Proper Planning =<br />
This section is the preplanning done prior to the migration<br />
== Server selection ==<br />
<br />
[https://www.linode.com/pricing?r=30335eb136f2c5f7fa3429dce9f15bea836f81d3 Linode] has been acquired by Akamai and raised their prices. Could potentially downgrade from the $12/mo (2GB RAM) plan to the $5 (1GB RAM "Nanode") plan depending on distro system requirements. Could also consider dropping paid backup service or using something different.<br />
<br />
Other VPS providers can be considered, not sure if they are any cheaper/better.<br />
<br />
=== Cloud Plans ===<br />
Looking at 1GB and 2GB plans.<br />
{| class="wikitable"<br />
! Vendor !! Plan !! $/Mo !! Memory !! CPU !! Storage !! Transfer<br />
|-<br />
| Linode || Nanode 1GB || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Linode || Linode 2GB || $12 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| DigitalOcean || 1GiB || $6 || 1GiB || 1 || 25GiB || 1TB<br />
|-<br />
| DigitalOcean || 2GiB || $12 || 2GiB || 1 || 50GiB || 2TB<br />
|-<br />
| Hostwinds || || $4.99 || 1GB || 1 || 30GB || 1TB<br />
|-<br />
| Hostwinds || || $9.90 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| Vultr || || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Vultr || || $10 || 2GB || 1 || 55GB || 2TB<br />
|}<br />
All services seem to be similar, with price differences only by a dollar or two.<br />
<br />
== OS selection ==<br />
<br />
CentOS Linux is dead. CentOS Stream is only viable as long as Red Hat/IBM has a business case for it. Can consider other options like pure Debian or Ubuntu LTS.<br />
<br />
=== Service enumeration ===<br />
<br />
Services that are currently running on the WPLUG Linode server. These should include things that are user-facing only, not infrastructure.<br />
<br />
* E-mail (Postfix)<br />
* Mailing lists (Mailman)<br />
* Wiki (MediaWiki)<br />
* Monkeybot IRC bot (infobot)<br />
** While one of the oldest WPLUG services, since [[IRC|freenode]] is essentially dead, there may not be good reason to keep it alive.<br />
* Ticketing system (Trac)<br />
** This is [https://trac.wplug.org/wplug-internet/report/6 virtually unused], likely not worth deploying.<br />
<br />
Infrastructure software which supports the services above.<br />
<br />
* Web server (Apache) - it would be possible to use Nginx instead, but I (Vance) am not familiar with setting it up<br />
* PHP (Apache mod_php) for MediaWiki - could be replaced with PHP-FPM<br />
* Let's Encrypt for TLS certificate (certbot)<br />
* Python for Mailman, Let's Encrypt, and Trac<br />
* Perl for Monkeybot<br />
* MariaDB for MediaWiki - may be [http://www.mediawiki.org/wiki/Compatibility#Database possible] to use SQLite or PostgreSQL instead<br />
* Greylisting daemon (Postgrey)<br />
* Fail2ban<br />
<br />
=== Support lifetime ===<br />
<br />
* CentOS Stream 9 - [https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates 2027-05-31] (limited to RHEL Full Support lifetime)<br />
* Rocky Linux 9 - [https://wiki.rockylinux.org/rocky/version/ 2032-05-31]<br />
* AlmaLinux 9 - [https://wiki.almalinux.org/release-notes/#almalinux-9 2032-05-31]<br />
* Debian 12 "bookworm" - [https://www.debian.org/News/2023/20230610.en.html 2028-06-10 or later]<br />
* Ubuntu 22.04 LTS - [http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Releases 2027-04]<br />
<br />
=== System requirements ===<br />
{| border="1"<br />
!<br />
!CPU<br />
!RAM<br />
!Disk<br />
|-<br />
|[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#system-requirements-reference_installing-RHEL CentOS] / Rocky / Alma 9<br />
|amd64, arm64, ppc64el<br />
|1.5 GB<br />
|10 GB<br />
|-<br />
|[https://www.debian.org/releases/bookworm/amd64/ch03s04.en.html Debian 12]<br />
|amd64, arm64, i386 (686 or higher), ppc64el, mipsel, mips64el<br />
|512 MB<br />
|4 GB<br />
|-<br />
|[https://ubuntu.com/server/docs/installation Ubuntu 22.04]<br />
|1 GHz amd64, arm64, ppc64el<br />
|1 GB<br />
|2.5 GB<br />
|-<br />
|}<br />
<br />
Currently we are using 22 GB of disk, as follows:<br />
594M /boot<br />
35M /etc<br />
11G /home - monkeybot.log is 7.3GB<br />
25M /opt<br />
2.2G /root<br />
4.0K /srv<br />
36K /tmp<br />
2.1G /usr<br />
6.3G /var<br />
<br />
=== Software availability ===<br />
<br />
This table is to track, for the different distros under consideration, whether the software we need is available within its repositories. We want to minimize the number of applications which have to be maintained manually.<br />
<br />
Key:<br />
* B: in distro's base repository<br />
* A: in an additional repository provided by the distro<br />
* T: in a third-party repository<br />
* ~: not available in any known repository<br />
* ?: availability unknown<br />
<br />
{| border="1"<br />
!<br />
!CentOS / Rocky / Alma 9<br />
!Debian 12<br />
!Ubuntu 22.04<br />
|-<br />
|postfix<br />
|B 3.5.9<br />
|B 3.7.5<br />
|B 3.6.4<br />
|-<br />
|mailman<br />
|~<br />
|B 3.3.8<br />
|A (3) 20200530<br />
|-<br />
|postgrey<br />
|T 1.37<sup>EPEL</sup><br />
|B 1.37<br />
|A 1.36<br />
|-<br />
|mediawiki<br />
|~<br />
|B 1.39<br />
|A 1.35<br />
|-<br />
|infobot<br />
|~<br />
|~<br />
|~<br />
|-<br />
|trac<br />
|~<br />
|[https://packages.debian.org/bookworm-backports/trac A 1.6] (backports)<br />
|A 1.5.3<br />
|-<br />
|apache<br />
|B 2.4.53<br />
|B 2.4.57<br />
|B 2.4.52<br />
|-<br />
|nginx<br />
|B 1.20.1 / 1.22.1<br />
|B 1.22.1<br />
|B 1.18.0<br />
|-<br />
|php<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|B 8.1<br />
|-<br />
|php-fpm<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|A 8.1<br />
|-<br />
|python2<br />
|~<br />
|[https://wiki.debian.org/Python/FAQ#Python_2_support ~]<br />
|A 2.7.18<br />
|-<br />
|python3<br />
|B 3.9.16<br />
|B 3.11.2<br />
|B 3.10.4<br />
|-<br />
|perl5<br />
|B 5.32<br />
|B 5.36<br />
|B 5.34<br />
|-<br />
|mariadb<br />
|B 10.5<br />
|B 10.11<br />
|A 10.6<br />
|-<br />
|mysql<br />
|B 8.0<br />
|~<br />
|B 8.0<br />
|-<br />
|sqlite<br />
|B 3.34<br />
|B 3.40<br />
|B 3.37<br />
|-<br />
|fail2ban<br />
|T 1.0.2<sup>EPEL</sup><br />
|B 1.0.2<br />
|A 0.11.2<br />
|-<br />
|certbot<br />
|T 2.6.0<sup>EPEL</sup><br />
|B 2.1.0<br />
|A 1.21.0<br />
|-<br />
|}<br />
<br />
Third-party repositories:<br />
* EPEL - [https://docs.fedoraproject.org/en-US/epel/ Extra Packages for Enterprise Linux]<br />
<br />
== Nice-to-haves ==<br />
<br />
* We have an archive of static web pages from the pre-2007 server "penguin" - it would be nice to make this history available somehow.<br />
<br />
<br />
<br />
<br />
[[Category:Migration]]</div>Ldaberkohttps://www.wplug.org/index.php?title=2024_Server_Migration&diff=50602024 Server Migration2024-10-25T03:50:03Z<p>Ldaberko: /* Server Setup Steps */</p>
<hr />
<div>This page is to collect information about our current configuration and options for switching to a new server going forward, since CentOS 7 goes end-of-life at 2024-06-30. Please feel free to edit to add missing information or correct errors.<br />
<br />
== Server selection ==<br />
<br />
[https://www.linode.com/pricing?r=30335eb136f2c5f7fa3429dce9f15bea836f81d3 Linode] has been acquired by Akamai and raised their prices. Could potentially downgrade from the $12/mo (2GB RAM) plan to the $5 (1GB RAM "Nanode") plan depending on distro system requirements. Could also consider dropping paid backup service or using something different.<br />
<br />
Other VPS providers can be considered, not sure if they are any cheaper/better.<br />
<br />
=== Cloud Plans ===<br />
Looking at 1GB and 2GB plans.<br />
{| class="wikitable"<br />
! Vendor !! Plan !! $/Mo !! Memory !! CPU !! Storage !! Transfer<br />
|-<br />
| Linode || Nanode 1GB || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Linode || Linode 2GB || $12 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| DigitalOcean || 1GiB || $6 || 1GiB || 1 || 25GiB || 1TB<br />
|-<br />
| DigitalOcean || 2GiB || $12 || 2GiB || 1 || 50GiB || 2TB<br />
|-<br />
| Hostwinds || || $4.99 || 1GB || 1 || 30GB || 1TB<br />
|-<br />
| Hostwinds || || $9.90 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| Vultr || || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Vultr || || $10 || 2GB || 1 || 55GB || 2TB<br />
|}<br />
All services seem to be similar, with price differences only by a dollar or two.<br />
<br />
== OS selection ==<br />
<br />
CentOS Linux is dead. CentOS Stream is only viable as long as Red Hat/IBM has a business case for it. Can consider other options like pure Debian or Ubuntu LTS.<br />
<br />
=== Service enumeration ===<br />
<br />
Services that are currently running on the WPLUG Linode server. These should include things that are user-facing only, not infrastructure.<br />
<br />
* E-mail (Postfix)<br />
* Mailing lists (Mailman)<br />
* Wiki (MediaWiki)<br />
* Monkeybot IRC bot (infobot)<br />
** While one of the oldest WPLUG services, since [[IRC|freenode]] is essentially dead, there may not be good reason to keep it alive.<br />
* Ticketing system (Trac)<br />
** This is [https://trac.wplug.org/wplug-internet/report/6 virtually unused], likely not worth deploying.<br />
<br />
Infrastructure software which supports the services above.<br />
<br />
* Web server (Apache) - it would be possible to use Nginx instead, but I (Vance) am not familiar with setting it up<br />
* PHP (Apache mod_php) for MediaWiki - could be replaced with PHP-FPM<br />
* Let's Encrypt for TLS certificate (certbot)<br />
* Python for Mailman, Let's Encrypt, and Trac<br />
* Perl for Monkeybot<br />
* MariaDB for MediaWiki - may be [http://www.mediawiki.org/wiki/Compatibility#Database possible] to use SQLite or PostgreSQL instead<br />
* Greylisting daemon (Postgrey)<br />
* Fail2ban<br />
<br />
=== Support lifetime ===<br />
<br />
* CentOS Stream 9 - [https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates 2027-05-31] (limited to RHEL Full Support lifetime)<br />
* Rocky Linux 9 - [https://wiki.rockylinux.org/rocky/version/ 2032-05-31]<br />
* AlmaLinux 9 - [https://wiki.almalinux.org/release-notes/#almalinux-9 2032-05-31]<br />
* Debian 12 "bookworm" - [https://www.debian.org/News/2023/20230610.en.html 2028-06-10 or later]<br />
* Ubuntu 22.04 LTS - [http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Releases 2027-04]<br />
<br />
=== System requirements ===<br />
{| border="1"<br />
!<br />
!CPU<br />
!RAM<br />
!Disk<br />
|-<br />
|[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#system-requirements-reference_installing-RHEL CentOS] / Rocky / Alma 9<br />
|amd64, arm64, ppc64el<br />
|1.5 GB<br />
|10 GB<br />
|-<br />
|[https://www.debian.org/releases/bookworm/amd64/ch03s04.en.html Debian 12]<br />
|amd64, arm64, i386 (686 or higher), ppc64el, mipsel, mips64el<br />
|512 MB<br />
|4 GB<br />
|-<br />
|[https://ubuntu.com/server/docs/installation Ubuntu 22.04]<br />
|1 GHz amd64, arm64, ppc64el<br />
|1 GB<br />
|2.5 GB<br />
|-<br />
|}<br />
<br />
Currently we are using 22 GB of disk, as follows:<br />
594M /boot<br />
35M /etc<br />
11G /home - monkeybot.log is 7.3GB<br />
25M /opt<br />
2.2G /root<br />
4.0K /srv<br />
36K /tmp<br />
2.1G /usr<br />
6.3G /var<br />
<br />
=== Software availability ===<br />
<br />
This table is to track, for the different distros under consideration, whether the software we need is available within its repositories. We want to minimize the number of applications which have to be maintained manually.<br />
<br />
Key:<br />
* B: in distro's base repository<br />
* A: in an additional repository provided by the distro<br />
* T: in a third-party repository<br />
* ~: not available in any known repository<br />
* ?: availability unknown<br />
<br />
{| border="1"<br />
!<br />
!CentOS / Rocky / Alma 9<br />
!Debian 12<br />
!Ubuntu 22.04<br />
|-<br />
|postfix<br />
|B 3.5.9<br />
|B 3.7.5<br />
|B 3.6.4<br />
|-<br />
|mailman<br />
|~<br />
|B 3.3.8<br />
|A (3) 20200530<br />
|-<br />
|postgrey<br />
|T 1.37<sup>EPEL</sup><br />
|B 1.37<br />
|A 1.36<br />
|-<br />
|mediawiki<br />
|~<br />
|B 1.39<br />
|A 1.35<br />
|-<br />
|infobot<br />
|~<br />
|~<br />
|~<br />
|-<br />
|trac<br />
|~<br />
|[https://packages.debian.org/bookworm-backports/trac A 1.6] (backports)<br />
|A 1.5.3<br />
|-<br />
|apache<br />
|B 2.4.53<br />
|B 2.4.57<br />
|B 2.4.52<br />
|-<br />
|nginx<br />
|B 1.20.1 / 1.22.1<br />
|B 1.22.1<br />
|B 1.18.0<br />
|-<br />
|php<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|B 8.1<br />
|-<br />
|php-fpm<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|A 8.1<br />
|-<br />
|python2<br />
|~<br />
|[https://wiki.debian.org/Python/FAQ#Python_2_support ~]<br />
|A 2.7.18<br />
|-<br />
|python3<br />
|B 3.9.16<br />
|B 3.11.2<br />
|B 3.10.4<br />
|-<br />
|perl5<br />
|B 5.32<br />
|B 5.36<br />
|B 5.34<br />
|-<br />
|mariadb<br />
|B 10.5<br />
|B 10.11<br />
|A 10.6<br />
|-<br />
|mysql<br />
|B 8.0<br />
|~<br />
|B 8.0<br />
|-<br />
|sqlite<br />
|B 3.34<br />
|B 3.40<br />
|B 3.37<br />
|-<br />
|fail2ban<br />
|T 1.0.2<sup>EPEL</sup><br />
|B 1.0.2<br />
|A 0.11.2<br />
|-<br />
|certbot<br />
|T 2.6.0<sup>EPEL</sup><br />
|B 2.1.0<br />
|A 1.21.0<br />
|-<br />
|}<br />
<br />
Third-party repositories:<br />
* EPEL - [https://docs.fedoraproject.org/en-US/epel/ Extra Packages for Enterprise Linux]<br />
<br />
== Nice-to-haves ==<br />
<br />
* We have an archive of static web pages from the pre-2007 server "penguin" - it would be nice to make this history available somehow.<br />
<br />
== Migration Notes ==<br />
New virtual server:<br />
* Name: penguin<br />
* OS: Debian 12<br />
* Region: Atlanta<br />
* Plan: Nanode 1GB<br />
* IPv4: 139.144.29.132<br />
* IPv6: 2600:3c02::f03c:94ff:fe10:c62f<br />
<br />
New staging server:<br />
* Name: nestling<br />
* OS: Debian 11<br />
* Region: Chicago<br />
* Plan: <s>Nanode 1GB</s> Linode 2 GB due to high memory use of Mailman 3.<br />
* IPv4: 172.234.26.233<br />
* IPv6: 2600:3c06::f03c:95ff:fed6:b745<br />
This server was selected to run this OS version and location because it was the only image and location that featured cloud-init which was necessary for automated builds. Once Debian 12 gets that feature, we'll migrate over.<br />
<br />
=== Server Setup Steps ===<br />
I'm setting up ansible to do the server build and configuration entirely. Nesting is the staging server.<br />
Here are the steps completed:<br />
* Create or rebuild new linode, with cloud-init that adds admin users and ssh public keys.<br />
* Set hostname, /etc/hosts, disable root ssh login<br />
* Add board group and create board home directory<br />
* apt update<br />
* Install apache, mariadb, php<br />
* Install and run certbot<br />
* Install mediawiki and restore images and sql data<br />
* Mail - mua, postfix, opendkim, SPF, DKIM, DMARC<br />
* Backup mediawiki data and config for future rebuild and migration<br />
* Restore mediawiki data and config<br />
* Add ufw management and set up firewall<br />
* fail2ban complete and added to penguin also<br />
* mail aliases<br />
* established staging.wplug.org subdomain<br />
* mailman3 installation finally successful<br />
* limit outbound mail in postfix so we don't spam people while testing<br />
* ran out of memory on the 1GB plan so bumped it up to 2GB RAM<br />
* added 512MB /swapfile<br />
* mailman 2.1 to 3 migration <br />
<br />
Currently working on:<br />
* mailman3 - figuring out settings and backup/restore<br />
<br />
Next steps:<br />
* Reconfigure apache to have wiki as front page.<br />
* Rename django admin page, set up a fail2ban for that.<br />
* Figure out where hyperkitty mailman3 index files are being saved to. /opt/mailman/mm?<br />
<br />
<br />
[[Category:Migration]]</div>Ldaberkohttps://www.wplug.org/index.php?title=2024_Server_Migration&diff=50592024 Server Migration2024-10-17T04:50:55Z<p>Ldaberko: /* Migration Notes */</p>
<hr />
<div>This page is to collect information about our current configuration and options for switching to a new server going forward, since CentOS 7 goes end-of-life at 2024-06-30. Please feel free to edit to add missing information or correct errors.<br />
<br />
== Server selection ==<br />
<br />
[https://www.linode.com/pricing?r=30335eb136f2c5f7fa3429dce9f15bea836f81d3 Linode] has been acquired by Akamai and raised their prices. Could potentially downgrade from the $12/mo (2GB RAM) plan to the $5 (1GB RAM "Nanode") plan depending on distro system requirements. Could also consider dropping paid backup service or using something different.<br />
<br />
Other VPS providers can be considered, not sure if they are any cheaper/better.<br />
<br />
=== Cloud Plans ===<br />
Looking at 1GB and 2GB plans.<br />
{| class="wikitable"<br />
! Vendor !! Plan !! $/Mo !! Memory !! CPU !! Storage !! Transfer<br />
|-<br />
| Linode || Nanode 1GB || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Linode || Linode 2GB || $12 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| DigitalOcean || 1GiB || $6 || 1GiB || 1 || 25GiB || 1TB<br />
|-<br />
| DigitalOcean || 2GiB || $12 || 2GiB || 1 || 50GiB || 2TB<br />
|-<br />
| Hostwinds || || $4.99 || 1GB || 1 || 30GB || 1TB<br />
|-<br />
| Hostwinds || || $9.90 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| Vultr || || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Vultr || || $10 || 2GB || 1 || 55GB || 2TB<br />
|}<br />
All services seem to be similar, with price differences only by a dollar or two.<br />
<br />
== OS selection ==<br />
<br />
CentOS Linux is dead. CentOS Stream is only viable as long as Red Hat/IBM has a business case for it. Can consider other options like pure Debian or Ubuntu LTS.<br />
<br />
=== Service enumeration ===<br />
<br />
Services that are currently running on the WPLUG Linode server. These should include things that are user-facing only, not infrastructure.<br />
<br />
* E-mail (Postfix)<br />
* Mailing lists (Mailman)<br />
* Wiki (MediaWiki)<br />
* Monkeybot IRC bot (infobot)<br />
** While one of the oldest WPLUG services, since [[IRC|freenode]] is essentially dead, there may not be good reason to keep it alive.<br />
* Ticketing system (Trac)<br />
** This is [https://trac.wplug.org/wplug-internet/report/6 virtually unused], likely not worth deploying.<br />
<br />
Infrastructure software which supports the services above.<br />
<br />
* Web server (Apache) - it would be possible to use Nginx instead, but I (Vance) am not familiar with setting it up<br />
* PHP (Apache mod_php) for MediaWiki - could be replaced with PHP-FPM<br />
* Let's Encrypt for TLS certificate (certbot)<br />
* Python for Mailman, Let's Encrypt, and Trac<br />
* Perl for Monkeybot<br />
* MariaDB for MediaWiki - may be [http://www.mediawiki.org/wiki/Compatibility#Database possible] to use SQLite or PostgreSQL instead<br />
* Greylisting daemon (Postgrey)<br />
* Fail2ban<br />
<br />
=== Support lifetime ===<br />
<br />
* CentOS Stream 9 - [https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates 2027-05-31] (limited to RHEL Full Support lifetime)<br />
* Rocky Linux 9 - [https://wiki.rockylinux.org/rocky/version/ 2032-05-31]<br />
* AlmaLinux 9 - [https://wiki.almalinux.org/release-notes/#almalinux-9 2032-05-31]<br />
* Debian 12 "bookworm" - [https://www.debian.org/News/2023/20230610.en.html 2028-06-10 or later]<br />
* Ubuntu 22.04 LTS - [http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Releases 2027-04]<br />
<br />
=== System requirements ===<br />
{| border="1"<br />
!<br />
!CPU<br />
!RAM<br />
!Disk<br />
|-<br />
|[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#system-requirements-reference_installing-RHEL CentOS] / Rocky / Alma 9<br />
|amd64, arm64, ppc64el<br />
|1.5 GB<br />
|10 GB<br />
|-<br />
|[https://www.debian.org/releases/bookworm/amd64/ch03s04.en.html Debian 12]<br />
|amd64, arm64, i386 (686 or higher), ppc64el, mipsel, mips64el<br />
|512 MB<br />
|4 GB<br />
|-<br />
|[https://ubuntu.com/server/docs/installation Ubuntu 22.04]<br />
|1 GHz amd64, arm64, ppc64el<br />
|1 GB<br />
|2.5 GB<br />
|-<br />
|}<br />
<br />
Currently we are using 22 GB of disk, as follows:<br />
594M /boot<br />
35M /etc<br />
11G /home - monkeybot.log is 7.3GB<br />
25M /opt<br />
2.2G /root<br />
4.0K /srv<br />
36K /tmp<br />
2.1G /usr<br />
6.3G /var<br />
<br />
=== Software availability ===<br />
<br />
This table is to track, for the different distros under consideration, whether the software we need is available within its repositories. We want to minimize the number of applications which have to be maintained manually.<br />
<br />
Key:<br />
* B: in distro's base repository<br />
* A: in an additional repository provided by the distro<br />
* T: in a third-party repository<br />
* ~: not available in any known repository<br />
* ?: availability unknown<br />
<br />
{| border="1"<br />
!<br />
!CentOS / Rocky / Alma 9<br />
!Debian 12<br />
!Ubuntu 22.04<br />
|-<br />
|postfix<br />
|B 3.5.9<br />
|B 3.7.5<br />
|B 3.6.4<br />
|-<br />
|mailman<br />
|~<br />
|B 3.3.8<br />
|A (3) 20200530<br />
|-<br />
|postgrey<br />
|T 1.37<sup>EPEL</sup><br />
|B 1.37<br />
|A 1.36<br />
|-<br />
|mediawiki<br />
|~<br />
|B 1.39<br />
|A 1.35<br />
|-<br />
|infobot<br />
|~<br />
|~<br />
|~<br />
|-<br />
|trac<br />
|~<br />
|[https://packages.debian.org/bookworm-backports/trac A 1.6] (backports)<br />
|A 1.5.3<br />
|-<br />
|apache<br />
|B 2.4.53<br />
|B 2.4.57<br />
|B 2.4.52<br />
|-<br />
|nginx<br />
|B 1.20.1 / 1.22.1<br />
|B 1.22.1<br />
|B 1.18.0<br />
|-<br />
|php<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|B 8.1<br />
|-<br />
|php-fpm<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|A 8.1<br />
|-<br />
|python2<br />
|~<br />
|[https://wiki.debian.org/Python/FAQ#Python_2_support ~]<br />
|A 2.7.18<br />
|-<br />
|python3<br />
|B 3.9.16<br />
|B 3.11.2<br />
|B 3.10.4<br />
|-<br />
|perl5<br />
|B 5.32<br />
|B 5.36<br />
|B 5.34<br />
|-<br />
|mariadb<br />
|B 10.5<br />
|B 10.11<br />
|A 10.6<br />
|-<br />
|mysql<br />
|B 8.0<br />
|~<br />
|B 8.0<br />
|-<br />
|sqlite<br />
|B 3.34<br />
|B 3.40<br />
|B 3.37<br />
|-<br />
|fail2ban<br />
|T 1.0.2<sup>EPEL</sup><br />
|B 1.0.2<br />
|A 0.11.2<br />
|-<br />
|certbot<br />
|T 2.6.0<sup>EPEL</sup><br />
|B 2.1.0<br />
|A 1.21.0<br />
|-<br />
|}<br />
<br />
Third-party repositories:<br />
* EPEL - [https://docs.fedoraproject.org/en-US/epel/ Extra Packages for Enterprise Linux]<br />
<br />
== Nice-to-haves ==<br />
<br />
* We have an archive of static web pages from the pre-2007 server "penguin" - it would be nice to make this history available somehow.<br />
<br />
== Migration Notes ==<br />
New virtual server:<br />
* Name: penguin<br />
* OS: Debian 12<br />
* Region: Atlanta<br />
* Plan: Nanode 1GB<br />
* IPv4: 139.144.29.132<br />
* IPv6: 2600:3c02::f03c:94ff:fe10:c62f<br />
<br />
New staging server:<br />
* Name: nestling<br />
* OS: Debian 11<br />
* Region: Chicago<br />
* Plan: <s>Nanode 1GB</s> Linode 2 GB due to high memory use of Mailman 3.<br />
* IPv4: 172.234.26.233<br />
* IPv6: 2600:3c06::f03c:95ff:fed6:b745<br />
This server was selected to run this OS version and location because it was the only image and location that featured cloud-init which was necessary for automated builds. Once Debian 12 gets that feature, we'll migrate over.<br />
<br />
=== Server Setup Steps ===<br />
I'm setting up ansible to do the server build and configuration entirely. Nesting is the staging server.<br />
Here are the steps completed:<br />
* Create or rebuild new linode, with cloud-init that adds admin users and ssh public keys.<br />
* Set hostname, /etc/hosts, disable root ssh login<br />
* Add board group and create board home directory<br />
* apt update<br />
* Install apache, mariadb, php<br />
* Install and run certbot<br />
* Install mediawiki and restore images and sql data<br />
* Mail - mua, postfix, opendkim, SPF, DKIM, DMARC<br />
* Backup mediawiki data and config for future rebuild and migration<br />
* Restore mediawiki data and config<br />
* Add ufw management and set up firewall<br />
* fail2ban complete and added to penguin also<br />
* mail aliases<br />
* established staging.wplug.org subdomain<br />
* mailman3 installation finally successful<br />
* limit outbound mail in postfix so we don't spam people while testing<br />
* ran out of memory on the 1GB plan so bumped it up to 2GB RAM<br />
<br />
Currently working on:<br />
* mailman3 - final configuration<br />
<br />
Next steps:<br />
* migrate mailman 2.1 to 3<br />
<br />
[[Category:Migration]]</div>Ldaberkohttps://www.wplug.org/index.php?title=2024_Server_Migration&diff=50582024 Server Migration2024-10-16T15:31:02Z<p>Ldaberko: /* Server Setup Steps */</p>
<hr />
<div>This page is to collect information about our current configuration and options for switching to a new server going forward, since CentOS 7 goes end-of-life at 2024-06-30. Please feel free to edit to add missing information or correct errors.<br />
<br />
== Server selection ==<br />
<br />
[https://www.linode.com/pricing?r=30335eb136f2c5f7fa3429dce9f15bea836f81d3 Linode] has been acquired by Akamai and raised their prices. Could potentially downgrade from the $12/mo (2GB RAM) plan to the $5 (1GB RAM "Nanode") plan depending on distro system requirements. Could also consider dropping paid backup service or using something different.<br />
<br />
Other VPS providers can be considered, not sure if they are any cheaper/better.<br />
<br />
=== Cloud Plans ===<br />
Looking at 1GB and 2GB plans.<br />
{| class="wikitable"<br />
! Vendor !! Plan !! $/Mo !! Memory !! CPU !! Storage !! Transfer<br />
|-<br />
| Linode || Nanode 1GB || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Linode || Linode 2GB || $12 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| DigitalOcean || 1GiB || $6 || 1GiB || 1 || 25GiB || 1TB<br />
|-<br />
| DigitalOcean || 2GiB || $12 || 2GiB || 1 || 50GiB || 2TB<br />
|-<br />
| Hostwinds || || $4.99 || 1GB || 1 || 30GB || 1TB<br />
|-<br />
| Hostwinds || || $9.90 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| Vultr || || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Vultr || || $10 || 2GB || 1 || 55GB || 2TB<br />
|}<br />
All services seem to be similar, with price differences only by a dollar or two.<br />
<br />
== OS selection ==<br />
<br />
CentOS Linux is dead. CentOS Stream is only viable as long as Red Hat/IBM has a business case for it. Can consider other options like pure Debian or Ubuntu LTS.<br />
<br />
=== Service enumeration ===<br />
<br />
Services that are currently running on the WPLUG Linode server. These should include things that are user-facing only, not infrastructure.<br />
<br />
* E-mail (Postfix)<br />
* Mailing lists (Mailman)<br />
* Wiki (MediaWiki)<br />
* Monkeybot IRC bot (infobot)<br />
** While one of the oldest WPLUG services, since [[IRC|freenode]] is essentially dead, there may not be good reason to keep it alive.<br />
* Ticketing system (Trac)<br />
** This is [https://trac.wplug.org/wplug-internet/report/6 virtually unused], likely not worth deploying.<br />
<br />
Infrastructure software which supports the services above.<br />
<br />
* Web server (Apache) - it would be possible to use Nginx instead, but I (Vance) am not familiar with setting it up<br />
* PHP (Apache mod_php) for MediaWiki - could be replaced with PHP-FPM<br />
* Let's Encrypt for TLS certificate (certbot)<br />
* Python for Mailman, Let's Encrypt, and Trac<br />
* Perl for Monkeybot<br />
* MariaDB for MediaWiki - may be [http://www.mediawiki.org/wiki/Compatibility#Database possible] to use SQLite or PostgreSQL instead<br />
* Greylisting daemon (Postgrey)<br />
* Fail2ban<br />
<br />
=== Support lifetime ===<br />
<br />
* CentOS Stream 9 - [https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates 2027-05-31] (limited to RHEL Full Support lifetime)<br />
* Rocky Linux 9 - [https://wiki.rockylinux.org/rocky/version/ 2032-05-31]<br />
* AlmaLinux 9 - [https://wiki.almalinux.org/release-notes/#almalinux-9 2032-05-31]<br />
* Debian 12 "bookworm" - [https://www.debian.org/News/2023/20230610.en.html 2028-06-10 or later]<br />
* Ubuntu 22.04 LTS - [http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Releases 2027-04]<br />
<br />
=== System requirements ===<br />
{| border="1"<br />
!<br />
!CPU<br />
!RAM<br />
!Disk<br />
|-<br />
|[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#system-requirements-reference_installing-RHEL CentOS] / Rocky / Alma 9<br />
|amd64, arm64, ppc64el<br />
|1.5 GB<br />
|10 GB<br />
|-<br />
|[https://www.debian.org/releases/bookworm/amd64/ch03s04.en.html Debian 12]<br />
|amd64, arm64, i386 (686 or higher), ppc64el, mipsel, mips64el<br />
|512 MB<br />
|4 GB<br />
|-<br />
|[https://ubuntu.com/server/docs/installation Ubuntu 22.04]<br />
|1 GHz amd64, arm64, ppc64el<br />
|1 GB<br />
|2.5 GB<br />
|-<br />
|}<br />
<br />
Currently we are using 22 GB of disk, as follows:<br />
594M /boot<br />
35M /etc<br />
11G /home - monkeybot.log is 7.3GB<br />
25M /opt<br />
2.2G /root<br />
4.0K /srv<br />
36K /tmp<br />
2.1G /usr<br />
6.3G /var<br />
<br />
=== Software availability ===<br />
<br />
This table is to track, for the different distros under consideration, whether the software we need is available within its repositories. We want to minimize the number of applications which have to be maintained manually.<br />
<br />
Key:<br />
* B: in distro's base repository<br />
* A: in an additional repository provided by the distro<br />
* T: in a third-party repository<br />
* ~: not available in any known repository<br />
* ?: availability unknown<br />
<br />
{| border="1"<br />
!<br />
!CentOS / Rocky / Alma 9<br />
!Debian 12<br />
!Ubuntu 22.04<br />
|-<br />
|postfix<br />
|B 3.5.9<br />
|B 3.7.5<br />
|B 3.6.4<br />
|-<br />
|mailman<br />
|~<br />
|B 3.3.8<br />
|A (3) 20200530<br />
|-<br />
|postgrey<br />
|T 1.37<sup>EPEL</sup><br />
|B 1.37<br />
|A 1.36<br />
|-<br />
|mediawiki<br />
|~<br />
|B 1.39<br />
|A 1.35<br />
|-<br />
|infobot<br />
|~<br />
|~<br />
|~<br />
|-<br />
|trac<br />
|~<br />
|[https://packages.debian.org/bookworm-backports/trac A 1.6] (backports)<br />
|A 1.5.3<br />
|-<br />
|apache<br />
|B 2.4.53<br />
|B 2.4.57<br />
|B 2.4.52<br />
|-<br />
|nginx<br />
|B 1.20.1 / 1.22.1<br />
|B 1.22.1<br />
|B 1.18.0<br />
|-<br />
|php<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|B 8.1<br />
|-<br />
|php-fpm<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|A 8.1<br />
|-<br />
|python2<br />
|~<br />
|[https://wiki.debian.org/Python/FAQ#Python_2_support ~]<br />
|A 2.7.18<br />
|-<br />
|python3<br />
|B 3.9.16<br />
|B 3.11.2<br />
|B 3.10.4<br />
|-<br />
|perl5<br />
|B 5.32<br />
|B 5.36<br />
|B 5.34<br />
|-<br />
|mariadb<br />
|B 10.5<br />
|B 10.11<br />
|A 10.6<br />
|-<br />
|mysql<br />
|B 8.0<br />
|~<br />
|B 8.0<br />
|-<br />
|sqlite<br />
|B 3.34<br />
|B 3.40<br />
|B 3.37<br />
|-<br />
|fail2ban<br />
|T 1.0.2<sup>EPEL</sup><br />
|B 1.0.2<br />
|A 0.11.2<br />
|-<br />
|certbot<br />
|T 2.6.0<sup>EPEL</sup><br />
|B 2.1.0<br />
|A 1.21.0<br />
|-<br />
|}<br />
<br />
Third-party repositories:<br />
* EPEL - [https://docs.fedoraproject.org/en-US/epel/ Extra Packages for Enterprise Linux]<br />
<br />
== Nice-to-haves ==<br />
<br />
* We have an archive of static web pages from the pre-2007 server "penguin" - it would be nice to make this history available somehow.<br />
<br />
== Migration Notes ==<br />
New virtual server:<br />
* Name: penguin<br />
* OS: Debian 12<br />
* Region: Atlanta<br />
* Plan: Nanode 1GB<br />
* IPv4: 139.144.29.132<br />
* IPv6: 2600:3c02::f03c:94ff:fe10:c62f<br />
<br />
New staging server:<br />
* Name: nestling<br />
* OS: Debian 11<br />
* Region: Chicago<br />
* Plan: Nanode 1GB<br />
* IPv4: 172.234.26.233<br />
* IPv6: 2600:3c06::f03c:95ff:fed6:b745<br />
This server was selected to run this OS version and location because it was the only image and location that featured cloud-init which was necessary for automated builds. Once Debian 12 gets that feature, we'll migrate over.<br />
<br />
=== Server Setup Steps ===<br />
I'm setting up ansible to do the server build and configuration entirely. Nesting is the staging server.<br />
Here are the steps completed:<br />
* Create or rebuild new linode, with cloud-init that adds admin users and ssh public keys.<br />
* Set hostname, /etc/hosts, disable root ssh login<br />
* Add board group and create board home directory<br />
* apt update<br />
* Install apache, mariadb, php<br />
* Install and run certbot<br />
* Install mediawiki and restore images and sql data<br />
* Mail - mua, postfix, opendkim, SPF, DKIM, DMARC<br />
* Backup mediawiki data and config for future rebuild and migration<br />
* Restore mediawiki data and config<br />
* Add ufw management and set up firewall<br />
* fail2ban complete and added to penguin also<br />
* mail aliases<br />
* established staging.wplug.org subdomain<br />
* mailman3 installation finally successful<br />
<br />
Currently working on:<br />
* mailman3 - final configuration<br />
<br />
Next steps:<br />
* migrate mailman 2.1 to 3<br />
<br />
[[Category:Migration]]</div>Ldaberkohttps://www.wplug.org/index.php?title=2024_Server_Migration&diff=50572024 Server Migration2024-10-14T05:30:27Z<p>Ldaberko: /* Server Setup Steps */</p>
<hr />
<div>This page is to collect information about our current configuration and options for switching to a new server going forward, since CentOS 7 goes end-of-life at 2024-06-30. Please feel free to edit to add missing information or correct errors.<br />
<br />
== Server selection ==<br />
<br />
[https://www.linode.com/pricing?r=30335eb136f2c5f7fa3429dce9f15bea836f81d3 Linode] has been acquired by Akamai and raised their prices. Could potentially downgrade from the $12/mo (2GB RAM) plan to the $5 (1GB RAM "Nanode") plan depending on distro system requirements. Could also consider dropping paid backup service or using something different.<br />
<br />
Other VPS providers can be considered, not sure if they are any cheaper/better.<br />
<br />
=== Cloud Plans ===<br />
Looking at 1GB and 2GB plans.<br />
{| class="wikitable"<br />
! Vendor !! Plan !! $/Mo !! Memory !! CPU !! Storage !! Transfer<br />
|-<br />
| Linode || Nanode 1GB || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Linode || Linode 2GB || $12 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| DigitalOcean || 1GiB || $6 || 1GiB || 1 || 25GiB || 1TB<br />
|-<br />
| DigitalOcean || 2GiB || $12 || 2GiB || 1 || 50GiB || 2TB<br />
|-<br />
| Hostwinds || || $4.99 || 1GB || 1 || 30GB || 1TB<br />
|-<br />
| Hostwinds || || $9.90 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| Vultr || || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Vultr || || $10 || 2GB || 1 || 55GB || 2TB<br />
|}<br />
All services seem to be similar, with price differences only by a dollar or two.<br />
<br />
== OS selection ==<br />
<br />
CentOS Linux is dead. CentOS Stream is only viable as long as Red Hat/IBM has a business case for it. Can consider other options like pure Debian or Ubuntu LTS.<br />
<br />
=== Service enumeration ===<br />
<br />
Services that are currently running on the WPLUG Linode server. These should include things that are user-facing only, not infrastructure.<br />
<br />
* E-mail (Postfix)<br />
* Mailing lists (Mailman)<br />
* Wiki (MediaWiki)<br />
* Monkeybot IRC bot (infobot)<br />
** While one of the oldest WPLUG services, since [[IRC|freenode]] is essentially dead, there may not be good reason to keep it alive.<br />
* Ticketing system (Trac)<br />
** This is [https://trac.wplug.org/wplug-internet/report/6 virtually unused], likely not worth deploying.<br />
<br />
Infrastructure software which supports the services above.<br />
<br />
* Web server (Apache) - it would be possible to use Nginx instead, but I (Vance) am not familiar with setting it up<br />
* PHP (Apache mod_php) for MediaWiki - could be replaced with PHP-FPM<br />
* Let's Encrypt for TLS certificate (certbot)<br />
* Python for Mailman, Let's Encrypt, and Trac<br />
* Perl for Monkeybot<br />
* MariaDB for MediaWiki - may be [http://www.mediawiki.org/wiki/Compatibility#Database possible] to use SQLite or PostgreSQL instead<br />
* Greylisting daemon (Postgrey)<br />
* Fail2ban<br />
<br />
=== Support lifetime ===<br />
<br />
* CentOS Stream 9 - [https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates 2027-05-31] (limited to RHEL Full Support lifetime)<br />
* Rocky Linux 9 - [https://wiki.rockylinux.org/rocky/version/ 2032-05-31]<br />
* AlmaLinux 9 - [https://wiki.almalinux.org/release-notes/#almalinux-9 2032-05-31]<br />
* Debian 12 "bookworm" - [https://www.debian.org/News/2023/20230610.en.html 2028-06-10 or later]<br />
* Ubuntu 22.04 LTS - [http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Releases 2027-04]<br />
<br />
=== System requirements ===<br />
{| border="1"<br />
!<br />
!CPU<br />
!RAM<br />
!Disk<br />
|-<br />
|[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#system-requirements-reference_installing-RHEL CentOS] / Rocky / Alma 9<br />
|amd64, arm64, ppc64el<br />
|1.5 GB<br />
|10 GB<br />
|-<br />
|[https://www.debian.org/releases/bookworm/amd64/ch03s04.en.html Debian 12]<br />
|amd64, arm64, i386 (686 or higher), ppc64el, mipsel, mips64el<br />
|512 MB<br />
|4 GB<br />
|-<br />
|[https://ubuntu.com/server/docs/installation Ubuntu 22.04]<br />
|1 GHz amd64, arm64, ppc64el<br />
|1 GB<br />
|2.5 GB<br />
|-<br />
|}<br />
<br />
Currently we are using 22 GB of disk, as follows:<br />
594M /boot<br />
35M /etc<br />
11G /home - monkeybot.log is 7.3GB<br />
25M /opt<br />
2.2G /root<br />
4.0K /srv<br />
36K /tmp<br />
2.1G /usr<br />
6.3G /var<br />
<br />
=== Software availability ===<br />
<br />
This table is to track, for the different distros under consideration, whether the software we need is available within its repositories. We want to minimize the number of applications which have to be maintained manually.<br />
<br />
Key:<br />
* B: in distro's base repository<br />
* A: in an additional repository provided by the distro<br />
* T: in a third-party repository<br />
* ~: not available in any known repository<br />
* ?: availability unknown<br />
<br />
{| border="1"<br />
!<br />
!CentOS / Rocky / Alma 9<br />
!Debian 12<br />
!Ubuntu 22.04<br />
|-<br />
|postfix<br />
|B 3.5.9<br />
|B 3.7.5<br />
|B 3.6.4<br />
|-<br />
|mailman<br />
|~<br />
|B 3.3.8<br />
|A (3) 20200530<br />
|-<br />
|postgrey<br />
|T 1.37<sup>EPEL</sup><br />
|B 1.37<br />
|A 1.36<br />
|-<br />
|mediawiki<br />
|~<br />
|B 1.39<br />
|A 1.35<br />
|-<br />
|infobot<br />
|~<br />
|~<br />
|~<br />
|-<br />
|trac<br />
|~<br />
|[https://packages.debian.org/bookworm-backports/trac A 1.6] (backports)<br />
|A 1.5.3<br />
|-<br />
|apache<br />
|B 2.4.53<br />
|B 2.4.57<br />
|B 2.4.52<br />
|-<br />
|nginx<br />
|B 1.20.1 / 1.22.1<br />
|B 1.22.1<br />
|B 1.18.0<br />
|-<br />
|php<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|B 8.1<br />
|-<br />
|php-fpm<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|A 8.1<br />
|-<br />
|python2<br />
|~<br />
|[https://wiki.debian.org/Python/FAQ#Python_2_support ~]<br />
|A 2.7.18<br />
|-<br />
|python3<br />
|B 3.9.16<br />
|B 3.11.2<br />
|B 3.10.4<br />
|-<br />
|perl5<br />
|B 5.32<br />
|B 5.36<br />
|B 5.34<br />
|-<br />
|mariadb<br />
|B 10.5<br />
|B 10.11<br />
|A 10.6<br />
|-<br />
|mysql<br />
|B 8.0<br />
|~<br />
|B 8.0<br />
|-<br />
|sqlite<br />
|B 3.34<br />
|B 3.40<br />
|B 3.37<br />
|-<br />
|fail2ban<br />
|T 1.0.2<sup>EPEL</sup><br />
|B 1.0.2<br />
|A 0.11.2<br />
|-<br />
|certbot<br />
|T 2.6.0<sup>EPEL</sup><br />
|B 2.1.0<br />
|A 1.21.0<br />
|-<br />
|}<br />
<br />
Third-party repositories:<br />
* EPEL - [https://docs.fedoraproject.org/en-US/epel/ Extra Packages for Enterprise Linux]<br />
<br />
== Nice-to-haves ==<br />
<br />
* We have an archive of static web pages from the pre-2007 server "penguin" - it would be nice to make this history available somehow.<br />
<br />
== Migration Notes ==<br />
New virtual server:<br />
* Name: penguin<br />
* OS: Debian 12<br />
* Region: Atlanta<br />
* Plan: Nanode 1GB<br />
* IPv4: 139.144.29.132<br />
* IPv6: 2600:3c02::f03c:94ff:fe10:c62f<br />
<br />
New staging server:<br />
* Name: nestling<br />
* OS: Debian 11<br />
* Region: Chicago<br />
* Plan: Nanode 1GB<br />
* IPv4: 172.234.26.233<br />
* IPv6: 2600:3c06::f03c:95ff:fed6:b745<br />
This server was selected to run this OS version and location because it was the only image and location that featured cloud-init which was necessary for automated builds. Once Debian 12 gets that feature, we'll migrate over.<br />
<br />
=== Server Setup Steps ===<br />
I'm setting up ansible to do the server build and configuration entirely. Nesting is the staging server.<br />
Here are the steps completed:<br />
* Create or rebuild new linode, with cloud-init that adds admin users and ssh public keys.<br />
* Set hostname, /etc/hosts, disable root ssh login<br />
* Add board group and create board home directory<br />
* apt update<br />
* Install apache, mariadb, php<br />
* Install and run certbot<br />
* Install mediawiki and restore images and sql data<br />
* Mail - mua, postfix, opendkim, SPF, DKIM, DMARC<br />
* Backup mediawiki data and config for future rebuild and migration<br />
* Restore mediawiki data and config<br />
* Add ufw management and set up firewall<br />
* fail2ban complete and added to penguin also<br />
<br />
Currently working on:<br />
* mailman3 - difficulties abound<br />
<br />
Next steps:<br />
* Mail - aliases structure, spam filtering<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
[[Category:Migration]]</div>Ldaberkohttps://www.wplug.org/index.php?title=2024_Server_Migration&diff=50562024 Server Migration2024-10-14T04:21:17Z<p>Ldaberko: /* Server Setup Steps */</p>
<hr />
<div>This page is to collect information about our current configuration and options for switching to a new server going forward, since CentOS 7 goes end-of-life at 2024-06-30. Please feel free to edit to add missing information or correct errors.<br />
<br />
== Server selection ==<br />
<br />
[https://www.linode.com/pricing?r=30335eb136f2c5f7fa3429dce9f15bea836f81d3 Linode] has been acquired by Akamai and raised their prices. Could potentially downgrade from the $12/mo (2GB RAM) plan to the $5 (1GB RAM "Nanode") plan depending on distro system requirements. Could also consider dropping paid backup service or using something different.<br />
<br />
Other VPS providers can be considered, not sure if they are any cheaper/better.<br />
<br />
=== Cloud Plans ===<br />
Looking at 1GB and 2GB plans.<br />
{| class="wikitable"<br />
! Vendor !! Plan !! $/Mo !! Memory !! CPU !! Storage !! Transfer<br />
|-<br />
| Linode || Nanode 1GB || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Linode || Linode 2GB || $12 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| DigitalOcean || 1GiB || $6 || 1GiB || 1 || 25GiB || 1TB<br />
|-<br />
| DigitalOcean || 2GiB || $12 || 2GiB || 1 || 50GiB || 2TB<br />
|-<br />
| Hostwinds || || $4.99 || 1GB || 1 || 30GB || 1TB<br />
|-<br />
| Hostwinds || || $9.90 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| Vultr || || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Vultr || || $10 || 2GB || 1 || 55GB || 2TB<br />
|}<br />
All services seem to be similar, with price differences only by a dollar or two.<br />
<br />
== OS selection ==<br />
<br />
CentOS Linux is dead. CentOS Stream is only viable as long as Red Hat/IBM has a business case for it. Can consider other options like pure Debian or Ubuntu LTS.<br />
<br />
=== Service enumeration ===<br />
<br />
Services that are currently running on the WPLUG Linode server. These should include things that are user-facing only, not infrastructure.<br />
<br />
* E-mail (Postfix)<br />
* Mailing lists (Mailman)<br />
* Wiki (MediaWiki)<br />
* Monkeybot IRC bot (infobot)<br />
** While one of the oldest WPLUG services, since [[IRC|freenode]] is essentially dead, there may not be good reason to keep it alive.<br />
* Ticketing system (Trac)<br />
** This is [https://trac.wplug.org/wplug-internet/report/6 virtually unused], likely not worth deploying.<br />
<br />
Infrastructure software which supports the services above.<br />
<br />
* Web server (Apache) - it would be possible to use Nginx instead, but I (Vance) am not familiar with setting it up<br />
* PHP (Apache mod_php) for MediaWiki - could be replaced with PHP-FPM<br />
* Let's Encrypt for TLS certificate (certbot)<br />
* Python for Mailman, Let's Encrypt, and Trac<br />
* Perl for Monkeybot<br />
* MariaDB for MediaWiki - may be [http://www.mediawiki.org/wiki/Compatibility#Database possible] to use SQLite or PostgreSQL instead<br />
* Greylisting daemon (Postgrey)<br />
* Fail2ban<br />
<br />
=== Support lifetime ===<br />
<br />
* CentOS Stream 9 - [https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates 2027-05-31] (limited to RHEL Full Support lifetime)<br />
* Rocky Linux 9 - [https://wiki.rockylinux.org/rocky/version/ 2032-05-31]<br />
* AlmaLinux 9 - [https://wiki.almalinux.org/release-notes/#almalinux-9 2032-05-31]<br />
* Debian 12 "bookworm" - [https://www.debian.org/News/2023/20230610.en.html 2028-06-10 or later]<br />
* Ubuntu 22.04 LTS - [http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Releases 2027-04]<br />
<br />
=== System requirements ===<br />
{| border="1"<br />
!<br />
!CPU<br />
!RAM<br />
!Disk<br />
|-<br />
|[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#system-requirements-reference_installing-RHEL CentOS] / Rocky / Alma 9<br />
|amd64, arm64, ppc64el<br />
|1.5 GB<br />
|10 GB<br />
|-<br />
|[https://www.debian.org/releases/bookworm/amd64/ch03s04.en.html Debian 12]<br />
|amd64, arm64, i386 (686 or higher), ppc64el, mipsel, mips64el<br />
|512 MB<br />
|4 GB<br />
|-<br />
|[https://ubuntu.com/server/docs/installation Ubuntu 22.04]<br />
|1 GHz amd64, arm64, ppc64el<br />
|1 GB<br />
|2.5 GB<br />
|-<br />
|}<br />
<br />
Currently we are using 22 GB of disk, as follows:<br />
594M /boot<br />
35M /etc<br />
11G /home - monkeybot.log is 7.3GB<br />
25M /opt<br />
2.2G /root<br />
4.0K /srv<br />
36K /tmp<br />
2.1G /usr<br />
6.3G /var<br />
<br />
=== Software availability ===<br />
<br />
This table is to track, for the different distros under consideration, whether the software we need is available within its repositories. We want to minimize the number of applications which have to be maintained manually.<br />
<br />
Key:<br />
* B: in distro's base repository<br />
* A: in an additional repository provided by the distro<br />
* T: in a third-party repository<br />
* ~: not available in any known repository<br />
* ?: availability unknown<br />
<br />
{| border="1"<br />
!<br />
!CentOS / Rocky / Alma 9<br />
!Debian 12<br />
!Ubuntu 22.04<br />
|-<br />
|postfix<br />
|B 3.5.9<br />
|B 3.7.5<br />
|B 3.6.4<br />
|-<br />
|mailman<br />
|~<br />
|B 3.3.8<br />
|A (3) 20200530<br />
|-<br />
|postgrey<br />
|T 1.37<sup>EPEL</sup><br />
|B 1.37<br />
|A 1.36<br />
|-<br />
|mediawiki<br />
|~<br />
|B 1.39<br />
|A 1.35<br />
|-<br />
|infobot<br />
|~<br />
|~<br />
|~<br />
|-<br />
|trac<br />
|~<br />
|[https://packages.debian.org/bookworm-backports/trac A 1.6] (backports)<br />
|A 1.5.3<br />
|-<br />
|apache<br />
|B 2.4.53<br />
|B 2.4.57<br />
|B 2.4.52<br />
|-<br />
|nginx<br />
|B 1.20.1 / 1.22.1<br />
|B 1.22.1<br />
|B 1.18.0<br />
|-<br />
|php<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|B 8.1<br />
|-<br />
|php-fpm<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|A 8.1<br />
|-<br />
|python2<br />
|~<br />
|[https://wiki.debian.org/Python/FAQ#Python_2_support ~]<br />
|A 2.7.18<br />
|-<br />
|python3<br />
|B 3.9.16<br />
|B 3.11.2<br />
|B 3.10.4<br />
|-<br />
|perl5<br />
|B 5.32<br />
|B 5.36<br />
|B 5.34<br />
|-<br />
|mariadb<br />
|B 10.5<br />
|B 10.11<br />
|A 10.6<br />
|-<br />
|mysql<br />
|B 8.0<br />
|~<br />
|B 8.0<br />
|-<br />
|sqlite<br />
|B 3.34<br />
|B 3.40<br />
|B 3.37<br />
|-<br />
|fail2ban<br />
|T 1.0.2<sup>EPEL</sup><br />
|B 1.0.2<br />
|A 0.11.2<br />
|-<br />
|certbot<br />
|T 2.6.0<sup>EPEL</sup><br />
|B 2.1.0<br />
|A 1.21.0<br />
|-<br />
|}<br />
<br />
Third-party repositories:<br />
* EPEL - [https://docs.fedoraproject.org/en-US/epel/ Extra Packages for Enterprise Linux]<br />
<br />
== Nice-to-haves ==<br />
<br />
* We have an archive of static web pages from the pre-2007 server "penguin" - it would be nice to make this history available somehow.<br />
<br />
== Migration Notes ==<br />
New virtual server:<br />
* Name: penguin<br />
* OS: Debian 12<br />
* Region: Atlanta<br />
* Plan: Nanode 1GB<br />
* IPv4: 139.144.29.132<br />
* IPv6: 2600:3c02::f03c:94ff:fe10:c62f<br />
<br />
New staging server:<br />
* Name: nestling<br />
* OS: Debian 11<br />
* Region: Chicago<br />
* Plan: Nanode 1GB<br />
* IPv4: 172.234.26.233<br />
* IPv6: 2600:3c06::f03c:95ff:fed6:b745<br />
This server was selected to run this OS version and location because it was the only image and location that featured cloud-init which was necessary for automated builds. Once Debian 12 gets that feature, we'll migrate over.<br />
<br />
=== Server Setup Steps ===<br />
I'm setting up ansible to do the server build and configuration entirely. Nesting is the staging server.<br />
Here are the steps completed:<br />
* Create or rebuild new linode, with cloud-init that adds admin users and ssh public keys.<br />
* Set hostname, /etc/hosts, disable root ssh login<br />
* Add board group and create board home directory<br />
* apt update<br />
* Install apache, mariadb, php<br />
* Install and run certbot<br />
* Install mediawiki and restore images and sql data<br />
* Mail - mua, postfix, opendkim, SPF, DKIM, DMARC<br />
* Backup mediawiki data and config for future rebuild and migration<br />
* Restore mediawiki data and config<br />
* Add ufw management and set up firewall<br />
<br />
Currently working on:<br />
* fail2ban - in place, working on restoring old rulesets<br />
* mailman3 - difficulties abound<br />
<br />
Next steps:<br />
* Mail - aliases structure, spam filtering<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
[[Category:Migration]]</div>Ldaberkohttps://www.wplug.org/index.php?title=2024_Server_Migration&diff=50552024 Server Migration2024-10-02T01:48:40Z<p>Ldaberko: /* Server Setup Steps */</p>
<hr />
<div>This page is to collect information about our current configuration and options for switching to a new server going forward, since CentOS 7 goes end-of-life at 2024-06-30. Please feel free to edit to add missing information or correct errors.<br />
<br />
== Server selection ==<br />
<br />
[https://www.linode.com/pricing?r=30335eb136f2c5f7fa3429dce9f15bea836f81d3 Linode] has been acquired by Akamai and raised their prices. Could potentially downgrade from the $12/mo (2GB RAM) plan to the $5 (1GB RAM "Nanode") plan depending on distro system requirements. Could also consider dropping paid backup service or using something different.<br />
<br />
Other VPS providers can be considered, not sure if they are any cheaper/better.<br />
<br />
=== Cloud Plans ===<br />
Looking at 1GB and 2GB plans.<br />
{| class="wikitable"<br />
! Vendor !! Plan !! $/Mo !! Memory !! CPU !! Storage !! Transfer<br />
|-<br />
| Linode || Nanode 1GB || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Linode || Linode 2GB || $12 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| DigitalOcean || 1GiB || $6 || 1GiB || 1 || 25GiB || 1TB<br />
|-<br />
| DigitalOcean || 2GiB || $12 || 2GiB || 1 || 50GiB || 2TB<br />
|-<br />
| Hostwinds || || $4.99 || 1GB || 1 || 30GB || 1TB<br />
|-<br />
| Hostwinds || || $9.90 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| Vultr || || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Vultr || || $10 || 2GB || 1 || 55GB || 2TB<br />
|}<br />
All services seem to be similar, with price differences only by a dollar or two.<br />
<br />
== OS selection ==<br />
<br />
CentOS Linux is dead. CentOS Stream is only viable as long as Red Hat/IBM has a business case for it. Can consider other options like pure Debian or Ubuntu LTS.<br />
<br />
=== Service enumeration ===<br />
<br />
Services that are currently running on the WPLUG Linode server. These should include things that are user-facing only, not infrastructure.<br />
<br />
* E-mail (Postfix)<br />
* Mailing lists (Mailman)<br />
* Wiki (MediaWiki)<br />
* Monkeybot IRC bot (infobot)<br />
** While one of the oldest WPLUG services, since [[IRC|freenode]] is essentially dead, there may not be good reason to keep it alive.<br />
* Ticketing system (Trac)<br />
** This is [https://trac.wplug.org/wplug-internet/report/6 virtually unused], likely not worth deploying.<br />
<br />
Infrastructure software which supports the services above.<br />
<br />
* Web server (Apache) - it would be possible to use Nginx instead, but I (Vance) am not familiar with setting it up<br />
* PHP (Apache mod_php) for MediaWiki - could be replaced with PHP-FPM<br />
* Let's Encrypt for TLS certificate (certbot)<br />
* Python for Mailman, Let's Encrypt, and Trac<br />
* Perl for Monkeybot<br />
* MariaDB for MediaWiki - may be [http://www.mediawiki.org/wiki/Compatibility#Database possible] to use SQLite or PostgreSQL instead<br />
* Greylisting daemon (Postgrey)<br />
* Fail2ban<br />
<br />
=== Support lifetime ===<br />
<br />
* CentOS Stream 9 - [https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates 2027-05-31] (limited to RHEL Full Support lifetime)<br />
* Rocky Linux 9 - [https://wiki.rockylinux.org/rocky/version/ 2032-05-31]<br />
* AlmaLinux 9 - [https://wiki.almalinux.org/release-notes/#almalinux-9 2032-05-31]<br />
* Debian 12 "bookworm" - [https://www.debian.org/News/2023/20230610.en.html 2028-06-10 or later]<br />
* Ubuntu 22.04 LTS - [http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Releases 2027-04]<br />
<br />
=== System requirements ===<br />
{| border="1"<br />
!<br />
!CPU<br />
!RAM<br />
!Disk<br />
|-<br />
|[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#system-requirements-reference_installing-RHEL CentOS] / Rocky / Alma 9<br />
|amd64, arm64, ppc64el<br />
|1.5 GB<br />
|10 GB<br />
|-<br />
|[https://www.debian.org/releases/bookworm/amd64/ch03s04.en.html Debian 12]<br />
|amd64, arm64, i386 (686 or higher), ppc64el, mipsel, mips64el<br />
|512 MB<br />
|4 GB<br />
|-<br />
|[https://ubuntu.com/server/docs/installation Ubuntu 22.04]<br />
|1 GHz amd64, arm64, ppc64el<br />
|1 GB<br />
|2.5 GB<br />
|-<br />
|}<br />
<br />
Currently we are using 22 GB of disk, as follows:<br />
594M /boot<br />
35M /etc<br />
11G /home - monkeybot.log is 7.3GB<br />
25M /opt<br />
2.2G /root<br />
4.0K /srv<br />
36K /tmp<br />
2.1G /usr<br />
6.3G /var<br />
<br />
=== Software availability ===<br />
<br />
This table is to track, for the different distros under consideration, whether the software we need is available within its repositories. We want to minimize the number of applications which have to be maintained manually.<br />
<br />
Key:<br />
* B: in distro's base repository<br />
* A: in an additional repository provided by the distro<br />
* T: in a third-party repository<br />
* ~: not available in any known repository<br />
* ?: availability unknown<br />
<br />
{| border="1"<br />
!<br />
!CentOS / Rocky / Alma 9<br />
!Debian 12<br />
!Ubuntu 22.04<br />
|-<br />
|postfix<br />
|B 3.5.9<br />
|B 3.7.5<br />
|B 3.6.4<br />
|-<br />
|mailman<br />
|~<br />
|B 3.3.8<br />
|A (3) 20200530<br />
|-<br />
|postgrey<br />
|T 1.37<sup>EPEL</sup><br />
|B 1.37<br />
|A 1.36<br />
|-<br />
|mediawiki<br />
|~<br />
|B 1.39<br />
|A 1.35<br />
|-<br />
|infobot<br />
|~<br />
|~<br />
|~<br />
|-<br />
|trac<br />
|~<br />
|[https://packages.debian.org/bookworm-backports/trac A 1.6] (backports)<br />
|A 1.5.3<br />
|-<br />
|apache<br />
|B 2.4.53<br />
|B 2.4.57<br />
|B 2.4.52<br />
|-<br />
|nginx<br />
|B 1.20.1 / 1.22.1<br />
|B 1.22.1<br />
|B 1.18.0<br />
|-<br />
|php<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|B 8.1<br />
|-<br />
|php-fpm<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|A 8.1<br />
|-<br />
|python2<br />
|~<br />
|[https://wiki.debian.org/Python/FAQ#Python_2_support ~]<br />
|A 2.7.18<br />
|-<br />
|python3<br />
|B 3.9.16<br />
|B 3.11.2<br />
|B 3.10.4<br />
|-<br />
|perl5<br />
|B 5.32<br />
|B 5.36<br />
|B 5.34<br />
|-<br />
|mariadb<br />
|B 10.5<br />
|B 10.11<br />
|A 10.6<br />
|-<br />
|mysql<br />
|B 8.0<br />
|~<br />
|B 8.0<br />
|-<br />
|sqlite<br />
|B 3.34<br />
|B 3.40<br />
|B 3.37<br />
|-<br />
|fail2ban<br />
|T 1.0.2<sup>EPEL</sup><br />
|B 1.0.2<br />
|A 0.11.2<br />
|-<br />
|certbot<br />
|T 2.6.0<sup>EPEL</sup><br />
|B 2.1.0<br />
|A 1.21.0<br />
|-<br />
|}<br />
<br />
Third-party repositories:<br />
* EPEL - [https://docs.fedoraproject.org/en-US/epel/ Extra Packages for Enterprise Linux]<br />
<br />
== Nice-to-haves ==<br />
<br />
* We have an archive of static web pages from the pre-2007 server "penguin" - it would be nice to make this history available somehow.<br />
<br />
== Migration Notes ==<br />
New virtual server:<br />
* Name: penguin<br />
* OS: Debian 12<br />
* Region: Atlanta<br />
* Plan: Nanode 1GB<br />
* IPv4: 139.144.29.132<br />
* IPv6: 2600:3c02::f03c:94ff:fe10:c62f<br />
<br />
New staging server:<br />
* Name: nestling<br />
* OS: Debian 11<br />
* Region: Chicago<br />
* Plan: Nanode 1GB<br />
* IPv4: 172.234.26.233<br />
* IPv6: 2600:3c06::f03c:95ff:fed6:b745<br />
This server was selected to run this OS version and location because it was the only image and location that featured cloud-init which was necessary for automated builds. Once Debian 12 gets that feature, we'll migrate over.<br />
<br />
=== Server Setup Steps ===<br />
I'm setting up ansible to do the server build and configuration entirely. Nesting is the staging server.<br />
Here are the steps completed:<br />
* Create or rebuild new linode, with cloud-init that adds admin users and ssh public keys.<br />
* Set hostname, /etc/hosts, disable root ssh login<br />
* Add board group and create board home directory<br />
* apt update<br />
* Install apache, mariadb, php<br />
* Install and run certbot<br />
* Install mediawiki and restore images and sql data<br />
* Mail - mua, postfix, opendkim, SPF, DKIM, DMARC<br />
* Backup mediawiki data and config for future rebuild and migration<br />
* Restore mediawiki data and config<br />
* Add ufw management and set up firewall<br />
<br />
Currently working on:<br />
* mailman3<br />
<br />
Next steps:<br />
* fail2ban<br />
* Mail - aliases structure, spam filtering<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
[[Category:Migration]]</div>Ldaberkohttps://www.wplug.org/index.php?title=2024_Server_Migration&diff=50542024 Server Migration2024-09-30T21:20:21Z<p>Ldaberko: /* Server Setup Steps */</p>
<hr />
<div>This page is to collect information about our current configuration and options for switching to a new server going forward, since CentOS 7 goes end-of-life at 2024-06-30. Please feel free to edit to add missing information or correct errors.<br />
<br />
== Server selection ==<br />
<br />
[https://www.linode.com/pricing?r=30335eb136f2c5f7fa3429dce9f15bea836f81d3 Linode] has been acquired by Akamai and raised their prices. Could potentially downgrade from the $12/mo (2GB RAM) plan to the $5 (1GB RAM "Nanode") plan depending on distro system requirements. Could also consider dropping paid backup service or using something different.<br />
<br />
Other VPS providers can be considered, not sure if they are any cheaper/better.<br />
<br />
=== Cloud Plans ===<br />
Looking at 1GB and 2GB plans.<br />
{| class="wikitable"<br />
! Vendor !! Plan !! $/Mo !! Memory !! CPU !! Storage !! Transfer<br />
|-<br />
| Linode || Nanode 1GB || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Linode || Linode 2GB || $12 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| DigitalOcean || 1GiB || $6 || 1GiB || 1 || 25GiB || 1TB<br />
|-<br />
| DigitalOcean || 2GiB || $12 || 2GiB || 1 || 50GiB || 2TB<br />
|-<br />
| Hostwinds || || $4.99 || 1GB || 1 || 30GB || 1TB<br />
|-<br />
| Hostwinds || || $9.90 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| Vultr || || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Vultr || || $10 || 2GB || 1 || 55GB || 2TB<br />
|}<br />
All services seem to be similar, with price differences only by a dollar or two.<br />
<br />
== OS selection ==<br />
<br />
CentOS Linux is dead. CentOS Stream is only viable as long as Red Hat/IBM has a business case for it. Can consider other options like pure Debian or Ubuntu LTS.<br />
<br />
=== Service enumeration ===<br />
<br />
Services that are currently running on the WPLUG Linode server. These should include things that are user-facing only, not infrastructure.<br />
<br />
* E-mail (Postfix)<br />
* Mailing lists (Mailman)<br />
* Wiki (MediaWiki)<br />
* Monkeybot IRC bot (infobot)<br />
** While one of the oldest WPLUG services, since [[IRC|freenode]] is essentially dead, there may not be good reason to keep it alive.<br />
* Ticketing system (Trac)<br />
** This is [https://trac.wplug.org/wplug-internet/report/6 virtually unused], likely not worth deploying.<br />
<br />
Infrastructure software which supports the services above.<br />
<br />
* Web server (Apache) - it would be possible to use Nginx instead, but I (Vance) am not familiar with setting it up<br />
* PHP (Apache mod_php) for MediaWiki - could be replaced with PHP-FPM<br />
* Let's Encrypt for TLS certificate (certbot)<br />
* Python for Mailman, Let's Encrypt, and Trac<br />
* Perl for Monkeybot<br />
* MariaDB for MediaWiki - may be [http://www.mediawiki.org/wiki/Compatibility#Database possible] to use SQLite or PostgreSQL instead<br />
* Greylisting daemon (Postgrey)<br />
* Fail2ban<br />
<br />
=== Support lifetime ===<br />
<br />
* CentOS Stream 9 - [https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates 2027-05-31] (limited to RHEL Full Support lifetime)<br />
* Rocky Linux 9 - [https://wiki.rockylinux.org/rocky/version/ 2032-05-31]<br />
* AlmaLinux 9 - [https://wiki.almalinux.org/release-notes/#almalinux-9 2032-05-31]<br />
* Debian 12 "bookworm" - [https://www.debian.org/News/2023/20230610.en.html 2028-06-10 or later]<br />
* Ubuntu 22.04 LTS - [http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Releases 2027-04]<br />
<br />
=== System requirements ===<br />
{| border="1"<br />
!<br />
!CPU<br />
!RAM<br />
!Disk<br />
|-<br />
|[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#system-requirements-reference_installing-RHEL CentOS] / Rocky / Alma 9<br />
|amd64, arm64, ppc64el<br />
|1.5 GB<br />
|10 GB<br />
|-<br />
|[https://www.debian.org/releases/bookworm/amd64/ch03s04.en.html Debian 12]<br />
|amd64, arm64, i386 (686 or higher), ppc64el, mipsel, mips64el<br />
|512 MB<br />
|4 GB<br />
|-<br />
|[https://ubuntu.com/server/docs/installation Ubuntu 22.04]<br />
|1 GHz amd64, arm64, ppc64el<br />
|1 GB<br />
|2.5 GB<br />
|-<br />
|}<br />
<br />
Currently we are using 22 GB of disk, as follows:<br />
594M /boot<br />
35M /etc<br />
11G /home - monkeybot.log is 7.3GB<br />
25M /opt<br />
2.2G /root<br />
4.0K /srv<br />
36K /tmp<br />
2.1G /usr<br />
6.3G /var<br />
<br />
=== Software availability ===<br />
<br />
This table is to track, for the different distros under consideration, whether the software we need is available within its repositories. We want to minimize the number of applications which have to be maintained manually.<br />
<br />
Key:<br />
* B: in distro's base repository<br />
* A: in an additional repository provided by the distro<br />
* T: in a third-party repository<br />
* ~: not available in any known repository<br />
* ?: availability unknown<br />
<br />
{| border="1"<br />
!<br />
!CentOS / Rocky / Alma 9<br />
!Debian 12<br />
!Ubuntu 22.04<br />
|-<br />
|postfix<br />
|B 3.5.9<br />
|B 3.7.5<br />
|B 3.6.4<br />
|-<br />
|mailman<br />
|~<br />
|B 3.3.8<br />
|A (3) 20200530<br />
|-<br />
|postgrey<br />
|T 1.37<sup>EPEL</sup><br />
|B 1.37<br />
|A 1.36<br />
|-<br />
|mediawiki<br />
|~<br />
|B 1.39<br />
|A 1.35<br />
|-<br />
|infobot<br />
|~<br />
|~<br />
|~<br />
|-<br />
|trac<br />
|~<br />
|[https://packages.debian.org/bookworm-backports/trac A 1.6] (backports)<br />
|A 1.5.3<br />
|-<br />
|apache<br />
|B 2.4.53<br />
|B 2.4.57<br />
|B 2.4.52<br />
|-<br />
|nginx<br />
|B 1.20.1 / 1.22.1<br />
|B 1.22.1<br />
|B 1.18.0<br />
|-<br />
|php<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|B 8.1<br />
|-<br />
|php-fpm<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|A 8.1<br />
|-<br />
|python2<br />
|~<br />
|[https://wiki.debian.org/Python/FAQ#Python_2_support ~]<br />
|A 2.7.18<br />
|-<br />
|python3<br />
|B 3.9.16<br />
|B 3.11.2<br />
|B 3.10.4<br />
|-<br />
|perl5<br />
|B 5.32<br />
|B 5.36<br />
|B 5.34<br />
|-<br />
|mariadb<br />
|B 10.5<br />
|B 10.11<br />
|A 10.6<br />
|-<br />
|mysql<br />
|B 8.0<br />
|~<br />
|B 8.0<br />
|-<br />
|sqlite<br />
|B 3.34<br />
|B 3.40<br />
|B 3.37<br />
|-<br />
|fail2ban<br />
|T 1.0.2<sup>EPEL</sup><br />
|B 1.0.2<br />
|A 0.11.2<br />
|-<br />
|certbot<br />
|T 2.6.0<sup>EPEL</sup><br />
|B 2.1.0<br />
|A 1.21.0<br />
|-<br />
|}<br />
<br />
Third-party repositories:<br />
* EPEL - [https://docs.fedoraproject.org/en-US/epel/ Extra Packages for Enterprise Linux]<br />
<br />
== Nice-to-haves ==<br />
<br />
* We have an archive of static web pages from the pre-2007 server "penguin" - it would be nice to make this history available somehow.<br />
<br />
== Migration Notes ==<br />
New virtual server:<br />
* Name: penguin<br />
* OS: Debian 12<br />
* Region: Atlanta<br />
* Plan: Nanode 1GB<br />
* IPv4: 139.144.29.132<br />
* IPv6: 2600:3c02::f03c:94ff:fe10:c62f<br />
<br />
New staging server:<br />
* Name: nestling<br />
* OS: Debian 11<br />
* Region: Chicago<br />
* Plan: Nanode 1GB<br />
* IPv4: 172.234.26.233<br />
* IPv6: 2600:3c06::f03c:95ff:fed6:b745<br />
This server was selected to run this OS version and location because it was the only image and location that featured cloud-init which was necessary for automated builds. Once Debian 12 gets that feature, we'll migrate over.<br />
<br />
=== Server Setup Steps ===<br />
I'm setting up ansible to do the server build and configuration entirely. Nesting is the staging server.<br />
Here are the steps completed:<br />
* Create or rebuild new linode, with cloud-init that adds admin users and ssh public keys.<br />
* Set hostname, /etc/hosts, disable root ssh login<br />
* Add board group and create board home directory<br />
* apt update<br />
* Install apache, mariadb, php<br />
* Install and run certbot<br />
* Install mediawiki and restore images and sql data<br />
* Mail - mua, postfix, opendkim, SPF, DKIM, DMARC<br />
* Backup mediawiki data and config for future rebuild and migration<br />
* Restore mediawiki data and config<br />
<br />
Currently testing:<br />
* mailman<br />
<br />
Next steps:<br />
* Mail - aliases structure, spam filtering<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
[[Category:Migration]]</div>Ldaberkohttps://www.wplug.org/index.php?title=2024_Server_Migration&diff=50532024 Server Migration2024-09-30T21:02:27Z<p>Ldaberko: /* Server Setup Steps */</p>
<hr />
<div>This page is to collect information about our current configuration and options for switching to a new server going forward, since CentOS 7 goes end-of-life at 2024-06-30. Please feel free to edit to add missing information or correct errors.<br />
<br />
== Server selection ==<br />
<br />
[https://www.linode.com/pricing?r=30335eb136f2c5f7fa3429dce9f15bea836f81d3 Linode] has been acquired by Akamai and raised their prices. Could potentially downgrade from the $12/mo (2GB RAM) plan to the $5 (1GB RAM "Nanode") plan depending on distro system requirements. Could also consider dropping paid backup service or using something different.<br />
<br />
Other VPS providers can be considered, not sure if they are any cheaper/better.<br />
<br />
=== Cloud Plans ===<br />
Looking at 1GB and 2GB plans.<br />
{| class="wikitable"<br />
! Vendor !! Plan !! $/Mo !! Memory !! CPU !! Storage !! Transfer<br />
|-<br />
| Linode || Nanode 1GB || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Linode || Linode 2GB || $12 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| DigitalOcean || 1GiB || $6 || 1GiB || 1 || 25GiB || 1TB<br />
|-<br />
| DigitalOcean || 2GiB || $12 || 2GiB || 1 || 50GiB || 2TB<br />
|-<br />
| Hostwinds || || $4.99 || 1GB || 1 || 30GB || 1TB<br />
|-<br />
| Hostwinds || || $9.90 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| Vultr || || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Vultr || || $10 || 2GB || 1 || 55GB || 2TB<br />
|}<br />
All services seem to be similar, with price differences only by a dollar or two.<br />
<br />
== OS selection ==<br />
<br />
CentOS Linux is dead. CentOS Stream is only viable as long as Red Hat/IBM has a business case for it. Can consider other options like pure Debian or Ubuntu LTS.<br />
<br />
=== Service enumeration ===<br />
<br />
Services that are currently running on the WPLUG Linode server. These should include things that are user-facing only, not infrastructure.<br />
<br />
* E-mail (Postfix)<br />
* Mailing lists (Mailman)<br />
* Wiki (MediaWiki)<br />
* Monkeybot IRC bot (infobot)<br />
** While one of the oldest WPLUG services, since [[IRC|freenode]] is essentially dead, there may not be good reason to keep it alive.<br />
* Ticketing system (Trac)<br />
** This is [https://trac.wplug.org/wplug-internet/report/6 virtually unused], likely not worth deploying.<br />
<br />
Infrastructure software which supports the services above.<br />
<br />
* Web server (Apache) - it would be possible to use Nginx instead, but I (Vance) am not familiar with setting it up<br />
* PHP (Apache mod_php) for MediaWiki - could be replaced with PHP-FPM<br />
* Let's Encrypt for TLS certificate (certbot)<br />
* Python for Mailman, Let's Encrypt, and Trac<br />
* Perl for Monkeybot<br />
* MariaDB for MediaWiki - may be [http://www.mediawiki.org/wiki/Compatibility#Database possible] to use SQLite or PostgreSQL instead<br />
* Greylisting daemon (Postgrey)<br />
* Fail2ban<br />
<br />
=== Support lifetime ===<br />
<br />
* CentOS Stream 9 - [https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates 2027-05-31] (limited to RHEL Full Support lifetime)<br />
* Rocky Linux 9 - [https://wiki.rockylinux.org/rocky/version/ 2032-05-31]<br />
* AlmaLinux 9 - [https://wiki.almalinux.org/release-notes/#almalinux-9 2032-05-31]<br />
* Debian 12 "bookworm" - [https://www.debian.org/News/2023/20230610.en.html 2028-06-10 or later]<br />
* Ubuntu 22.04 LTS - [http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Releases 2027-04]<br />
<br />
=== System requirements ===<br />
{| border="1"<br />
!<br />
!CPU<br />
!RAM<br />
!Disk<br />
|-<br />
|[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#system-requirements-reference_installing-RHEL CentOS] / Rocky / Alma 9<br />
|amd64, arm64, ppc64el<br />
|1.5 GB<br />
|10 GB<br />
|-<br />
|[https://www.debian.org/releases/bookworm/amd64/ch03s04.en.html Debian 12]<br />
|amd64, arm64, i386 (686 or higher), ppc64el, mipsel, mips64el<br />
|512 MB<br />
|4 GB<br />
|-<br />
|[https://ubuntu.com/server/docs/installation Ubuntu 22.04]<br />
|1 GHz amd64, arm64, ppc64el<br />
|1 GB<br />
|2.5 GB<br />
|-<br />
|}<br />
<br />
Currently we are using 22 GB of disk, as follows:<br />
594M /boot<br />
35M /etc<br />
11G /home - monkeybot.log is 7.3GB<br />
25M /opt<br />
2.2G /root<br />
4.0K /srv<br />
36K /tmp<br />
2.1G /usr<br />
6.3G /var<br />
<br />
=== Software availability ===<br />
<br />
This table is to track, for the different distros under consideration, whether the software we need is available within its repositories. We want to minimize the number of applications which have to be maintained manually.<br />
<br />
Key:<br />
* B: in distro's base repository<br />
* A: in an additional repository provided by the distro<br />
* T: in a third-party repository<br />
* ~: not available in any known repository<br />
* ?: availability unknown<br />
<br />
{| border="1"<br />
!<br />
!CentOS / Rocky / Alma 9<br />
!Debian 12<br />
!Ubuntu 22.04<br />
|-<br />
|postfix<br />
|B 3.5.9<br />
|B 3.7.5<br />
|B 3.6.4<br />
|-<br />
|mailman<br />
|~<br />
|B 3.3.8<br />
|A (3) 20200530<br />
|-<br />
|postgrey<br />
|T 1.37<sup>EPEL</sup><br />
|B 1.37<br />
|A 1.36<br />
|-<br />
|mediawiki<br />
|~<br />
|B 1.39<br />
|A 1.35<br />
|-<br />
|infobot<br />
|~<br />
|~<br />
|~<br />
|-<br />
|trac<br />
|~<br />
|[https://packages.debian.org/bookworm-backports/trac A 1.6] (backports)<br />
|A 1.5.3<br />
|-<br />
|apache<br />
|B 2.4.53<br />
|B 2.4.57<br />
|B 2.4.52<br />
|-<br />
|nginx<br />
|B 1.20.1 / 1.22.1<br />
|B 1.22.1<br />
|B 1.18.0<br />
|-<br />
|php<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|B 8.1<br />
|-<br />
|php-fpm<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|A 8.1<br />
|-<br />
|python2<br />
|~<br />
|[https://wiki.debian.org/Python/FAQ#Python_2_support ~]<br />
|A 2.7.18<br />
|-<br />
|python3<br />
|B 3.9.16<br />
|B 3.11.2<br />
|B 3.10.4<br />
|-<br />
|perl5<br />
|B 5.32<br />
|B 5.36<br />
|B 5.34<br />
|-<br />
|mariadb<br />
|B 10.5<br />
|B 10.11<br />
|A 10.6<br />
|-<br />
|mysql<br />
|B 8.0<br />
|~<br />
|B 8.0<br />
|-<br />
|sqlite<br />
|B 3.34<br />
|B 3.40<br />
|B 3.37<br />
|-<br />
|fail2ban<br />
|T 1.0.2<sup>EPEL</sup><br />
|B 1.0.2<br />
|A 0.11.2<br />
|-<br />
|certbot<br />
|T 2.6.0<sup>EPEL</sup><br />
|B 2.1.0<br />
|A 1.21.0<br />
|-<br />
|}<br />
<br />
Third-party repositories:<br />
* EPEL - [https://docs.fedoraproject.org/en-US/epel/ Extra Packages for Enterprise Linux]<br />
<br />
== Nice-to-haves ==<br />
<br />
* We have an archive of static web pages from the pre-2007 server "penguin" - it would be nice to make this history available somehow.<br />
<br />
== Migration Notes ==<br />
New virtual server:<br />
* Name: penguin<br />
* OS: Debian 12<br />
* Region: Atlanta<br />
* Plan: Nanode 1GB<br />
* IPv4: 139.144.29.132<br />
* IPv6: 2600:3c02::f03c:94ff:fe10:c62f<br />
<br />
New staging server:<br />
* Name: nestling<br />
* OS: Debian 11<br />
* Region: Chicago<br />
* Plan: Nanode 1GB<br />
* IPv4: 172.234.26.233<br />
* IPv6: 2600:3c06::f03c:95ff:fed6:b745<br />
This server was selected to run this OS version and location because it was the only image and location that featured cloud-init which was necessary for automated builds. Once Debian 12 gets that feature, we'll migrate over.<br />
<br />
=== Server Setup Steps ===<br />
I'm setting up ansible to do the server build and configuration entirely. Nesting is the staging server.<br />
Here are the steps completed:<br />
* Create or rebuild new linode, with cloud-init that adds admin users and ssh public keys.<br />
* Set hostname, /etc/hosts, disable root ssh login<br />
* Add board group and create board home directory<br />
* apt update<br />
* Install apache, mariadb, php<br />
* Install and run certbot<br />
* Install mediawiki and restore images and sql data<br />
* Mail - mua, postfix, opendkim, SPF, DKIM, DMARC<br />
* Backup mediawiki data and config for future rebuild and migration<br />
* Restore mediawiki data and config<br />
<br />
Currently testing:<br />
<br />
Next steps:<br />
* Mail - aliases structure, spam filtering<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
[[Category:Migration]]</div>Ldaberkohttps://www.wplug.org/index.php?title=2024_Server_Migration&diff=50522024 Server Migration2024-09-26T21:18:58Z<p>Ldaberko: /* Server Setup Steps */</p>
<hr />
<div>This page is to collect information about our current configuration and options for switching to a new server going forward, since CentOS 7 goes end-of-life at 2024-06-30. Please feel free to edit to add missing information or correct errors.<br />
<br />
== Server selection ==<br />
<br />
[https://www.linode.com/pricing?r=30335eb136f2c5f7fa3429dce9f15bea836f81d3 Linode] has been acquired by Akamai and raised their prices. Could potentially downgrade from the $12/mo (2GB RAM) plan to the $5 (1GB RAM "Nanode") plan depending on distro system requirements. Could also consider dropping paid backup service or using something different.<br />
<br />
Other VPS providers can be considered, not sure if they are any cheaper/better.<br />
<br />
=== Cloud Plans ===<br />
Looking at 1GB and 2GB plans.<br />
{| class="wikitable"<br />
! Vendor !! Plan !! $/Mo !! Memory !! CPU !! Storage !! Transfer<br />
|-<br />
| Linode || Nanode 1GB || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Linode || Linode 2GB || $12 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| DigitalOcean || 1GiB || $6 || 1GiB || 1 || 25GiB || 1TB<br />
|-<br />
| DigitalOcean || 2GiB || $12 || 2GiB || 1 || 50GiB || 2TB<br />
|-<br />
| Hostwinds || || $4.99 || 1GB || 1 || 30GB || 1TB<br />
|-<br />
| Hostwinds || || $9.90 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| Vultr || || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Vultr || || $10 || 2GB || 1 || 55GB || 2TB<br />
|}<br />
All services seem to be similar, with price differences only by a dollar or two.<br />
<br />
== OS selection ==<br />
<br />
CentOS Linux is dead. CentOS Stream is only viable as long as Red Hat/IBM has a business case for it. Can consider other options like pure Debian or Ubuntu LTS.<br />
<br />
=== Service enumeration ===<br />
<br />
Services that are currently running on the WPLUG Linode server. These should include things that are user-facing only, not infrastructure.<br />
<br />
* E-mail (Postfix)<br />
* Mailing lists (Mailman)<br />
* Wiki (MediaWiki)<br />
* Monkeybot IRC bot (infobot)<br />
** While one of the oldest WPLUG services, since [[IRC|freenode]] is essentially dead, there may not be good reason to keep it alive.<br />
* Ticketing system (Trac)<br />
** This is [https://trac.wplug.org/wplug-internet/report/6 virtually unused], likely not worth deploying.<br />
<br />
Infrastructure software which supports the services above.<br />
<br />
* Web server (Apache) - it would be possible to use Nginx instead, but I (Vance) am not familiar with setting it up<br />
* PHP (Apache mod_php) for MediaWiki - could be replaced with PHP-FPM<br />
* Let's Encrypt for TLS certificate (certbot)<br />
* Python for Mailman, Let's Encrypt, and Trac<br />
* Perl for Monkeybot<br />
* MariaDB for MediaWiki - may be [http://www.mediawiki.org/wiki/Compatibility#Database possible] to use SQLite or PostgreSQL instead<br />
* Greylisting daemon (Postgrey)<br />
* Fail2ban<br />
<br />
=== Support lifetime ===<br />
<br />
* CentOS Stream 9 - [https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates 2027-05-31] (limited to RHEL Full Support lifetime)<br />
* Rocky Linux 9 - [https://wiki.rockylinux.org/rocky/version/ 2032-05-31]<br />
* AlmaLinux 9 - [https://wiki.almalinux.org/release-notes/#almalinux-9 2032-05-31]<br />
* Debian 12 "bookworm" - [https://www.debian.org/News/2023/20230610.en.html 2028-06-10 or later]<br />
* Ubuntu 22.04 LTS - [http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Releases 2027-04]<br />
<br />
=== System requirements ===<br />
{| border="1"<br />
!<br />
!CPU<br />
!RAM<br />
!Disk<br />
|-<br />
|[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#system-requirements-reference_installing-RHEL CentOS] / Rocky / Alma 9<br />
|amd64, arm64, ppc64el<br />
|1.5 GB<br />
|10 GB<br />
|-<br />
|[https://www.debian.org/releases/bookworm/amd64/ch03s04.en.html Debian 12]<br />
|amd64, arm64, i386 (686 or higher), ppc64el, mipsel, mips64el<br />
|512 MB<br />
|4 GB<br />
|-<br />
|[https://ubuntu.com/server/docs/installation Ubuntu 22.04]<br />
|1 GHz amd64, arm64, ppc64el<br />
|1 GB<br />
|2.5 GB<br />
|-<br />
|}<br />
<br />
Currently we are using 22 GB of disk, as follows:<br />
594M /boot<br />
35M /etc<br />
11G /home - monkeybot.log is 7.3GB<br />
25M /opt<br />
2.2G /root<br />
4.0K /srv<br />
36K /tmp<br />
2.1G /usr<br />
6.3G /var<br />
<br />
=== Software availability ===<br />
<br />
This table is to track, for the different distros under consideration, whether the software we need is available within its repositories. We want to minimize the number of applications which have to be maintained manually.<br />
<br />
Key:<br />
* B: in distro's base repository<br />
* A: in an additional repository provided by the distro<br />
* T: in a third-party repository<br />
* ~: not available in any known repository<br />
* ?: availability unknown<br />
<br />
{| border="1"<br />
!<br />
!CentOS / Rocky / Alma 9<br />
!Debian 12<br />
!Ubuntu 22.04<br />
|-<br />
|postfix<br />
|B 3.5.9<br />
|B 3.7.5<br />
|B 3.6.4<br />
|-<br />
|mailman<br />
|~<br />
|B 3.3.8<br />
|A (3) 20200530<br />
|-<br />
|postgrey<br />
|T 1.37<sup>EPEL</sup><br />
|B 1.37<br />
|A 1.36<br />
|-<br />
|mediawiki<br />
|~<br />
|B 1.39<br />
|A 1.35<br />
|-<br />
|infobot<br />
|~<br />
|~<br />
|~<br />
|-<br />
|trac<br />
|~<br />
|[https://packages.debian.org/bookworm-backports/trac A 1.6] (backports)<br />
|A 1.5.3<br />
|-<br />
|apache<br />
|B 2.4.53<br />
|B 2.4.57<br />
|B 2.4.52<br />
|-<br />
|nginx<br />
|B 1.20.1 / 1.22.1<br />
|B 1.22.1<br />
|B 1.18.0<br />
|-<br />
|php<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|B 8.1<br />
|-<br />
|php-fpm<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|A 8.1<br />
|-<br />
|python2<br />
|~<br />
|[https://wiki.debian.org/Python/FAQ#Python_2_support ~]<br />
|A 2.7.18<br />
|-<br />
|python3<br />
|B 3.9.16<br />
|B 3.11.2<br />
|B 3.10.4<br />
|-<br />
|perl5<br />
|B 5.32<br />
|B 5.36<br />
|B 5.34<br />
|-<br />
|mariadb<br />
|B 10.5<br />
|B 10.11<br />
|A 10.6<br />
|-<br />
|mysql<br />
|B 8.0<br />
|~<br />
|B 8.0<br />
|-<br />
|sqlite<br />
|B 3.34<br />
|B 3.40<br />
|B 3.37<br />
|-<br />
|fail2ban<br />
|T 1.0.2<sup>EPEL</sup><br />
|B 1.0.2<br />
|A 0.11.2<br />
|-<br />
|certbot<br />
|T 2.6.0<sup>EPEL</sup><br />
|B 2.1.0<br />
|A 1.21.0<br />
|-<br />
|}<br />
<br />
Third-party repositories:<br />
* EPEL - [https://docs.fedoraproject.org/en-US/epel/ Extra Packages for Enterprise Linux]<br />
<br />
== Nice-to-haves ==<br />
<br />
* We have an archive of static web pages from the pre-2007 server "penguin" - it would be nice to make this history available somehow.<br />
<br />
== Migration Notes ==<br />
New virtual server:<br />
* Name: penguin<br />
* OS: Debian 12<br />
* Region: Atlanta<br />
* Plan: Nanode 1GB<br />
* IPv4: 139.144.29.132<br />
* IPv6: 2600:3c02::f03c:94ff:fe10:c62f<br />
<br />
New staging server:<br />
* Name: nestling<br />
* OS: Debian 11<br />
* Region: Chicago<br />
* Plan: Nanode 1GB<br />
* IPv4: 172.234.26.233<br />
* IPv6: 2600:3c06::f03c:95ff:fed6:b745<br />
This server was selected to run this OS version and location because it was the only image and location that featured cloud-init which was necessary for automated builds. Once Debian 12 gets that feature, we'll migrate over.<br />
<br />
=== Server Setup Steps ===<br />
I'm setting up ansible to do the server build and configuration entirely. Nesting is the staging server.<br />
Here are the steps completed:<br />
* Create or rebuild new linode, with cloud-init that adds admin users and ssh public keys.<br />
* Set hostname, /etc/hosts, disable root ssh login<br />
* Add board group and create board home directory<br />
* apt update<br />
* Install apache, mariadb, php<br />
* Install and run certbot<br />
* Install mediawiki and restore images and sql data<br />
<br />
Currently testing:<br />
* Mail - mua, postfix, opendkim, SPF, DKIM, DMARC<br />
<br />
Next steps:<br />
* Backup data and config for future rebuild and migration<br />
* Mail - aliases structure, spam filtering<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
[[Category:Migration]]</div>Ldaberkohttps://www.wplug.org/index.php?title=2024_Server_Migration&diff=50512024 Server Migration2024-09-26T20:48:54Z<p>Ldaberko: </p>
<hr />
<div>This page is to collect information about our current configuration and options for switching to a new server going forward, since CentOS 7 goes end-of-life at 2024-06-30. Please feel free to edit to add missing information or correct errors.<br />
<br />
== Server selection ==<br />
<br />
[https://www.linode.com/pricing?r=30335eb136f2c5f7fa3429dce9f15bea836f81d3 Linode] has been acquired by Akamai and raised their prices. Could potentially downgrade from the $12/mo (2GB RAM) plan to the $5 (1GB RAM "Nanode") plan depending on distro system requirements. Could also consider dropping paid backup service or using something different.<br />
<br />
Other VPS providers can be considered, not sure if they are any cheaper/better.<br />
<br />
=== Cloud Plans ===<br />
Looking at 1GB and 2GB plans.<br />
{| class="wikitable"<br />
! Vendor !! Plan !! $/Mo !! Memory !! CPU !! Storage !! Transfer<br />
|-<br />
| Linode || Nanode 1GB || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Linode || Linode 2GB || $12 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| DigitalOcean || 1GiB || $6 || 1GiB || 1 || 25GiB || 1TB<br />
|-<br />
| DigitalOcean || 2GiB || $12 || 2GiB || 1 || 50GiB || 2TB<br />
|-<br />
| Hostwinds || || $4.99 || 1GB || 1 || 30GB || 1TB<br />
|-<br />
| Hostwinds || || $9.90 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| Vultr || || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Vultr || || $10 || 2GB || 1 || 55GB || 2TB<br />
|}<br />
All services seem to be similar, with price differences only by a dollar or two.<br />
<br />
== OS selection ==<br />
<br />
CentOS Linux is dead. CentOS Stream is only viable as long as Red Hat/IBM has a business case for it. Can consider other options like pure Debian or Ubuntu LTS.<br />
<br />
=== Service enumeration ===<br />
<br />
Services that are currently running on the WPLUG Linode server. These should include things that are user-facing only, not infrastructure.<br />
<br />
* E-mail (Postfix)<br />
* Mailing lists (Mailman)<br />
* Wiki (MediaWiki)<br />
* Monkeybot IRC bot (infobot)<br />
** While one of the oldest WPLUG services, since [[IRC|freenode]] is essentially dead, there may not be good reason to keep it alive.<br />
* Ticketing system (Trac)<br />
** This is [https://trac.wplug.org/wplug-internet/report/6 virtually unused], likely not worth deploying.<br />
<br />
Infrastructure software which supports the services above.<br />
<br />
* Web server (Apache) - it would be possible to use Nginx instead, but I (Vance) am not familiar with setting it up<br />
* PHP (Apache mod_php) for MediaWiki - could be replaced with PHP-FPM<br />
* Let's Encrypt for TLS certificate (certbot)<br />
* Python for Mailman, Let's Encrypt, and Trac<br />
* Perl for Monkeybot<br />
* MariaDB for MediaWiki - may be [http://www.mediawiki.org/wiki/Compatibility#Database possible] to use SQLite or PostgreSQL instead<br />
* Greylisting daemon (Postgrey)<br />
* Fail2ban<br />
<br />
=== Support lifetime ===<br />
<br />
* CentOS Stream 9 - [https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates 2027-05-31] (limited to RHEL Full Support lifetime)<br />
* Rocky Linux 9 - [https://wiki.rockylinux.org/rocky/version/ 2032-05-31]<br />
* AlmaLinux 9 - [https://wiki.almalinux.org/release-notes/#almalinux-9 2032-05-31]<br />
* Debian 12 "bookworm" - [https://www.debian.org/News/2023/20230610.en.html 2028-06-10 or later]<br />
* Ubuntu 22.04 LTS - [http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Releases 2027-04]<br />
<br />
=== System requirements ===<br />
{| border="1"<br />
!<br />
!CPU<br />
!RAM<br />
!Disk<br />
|-<br />
|[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#system-requirements-reference_installing-RHEL CentOS] / Rocky / Alma 9<br />
|amd64, arm64, ppc64el<br />
|1.5 GB<br />
|10 GB<br />
|-<br />
|[https://www.debian.org/releases/bookworm/amd64/ch03s04.en.html Debian 12]<br />
|amd64, arm64, i386 (686 or higher), ppc64el, mipsel, mips64el<br />
|512 MB<br />
|4 GB<br />
|-<br />
|[https://ubuntu.com/server/docs/installation Ubuntu 22.04]<br />
|1 GHz amd64, arm64, ppc64el<br />
|1 GB<br />
|2.5 GB<br />
|-<br />
|}<br />
<br />
Currently we are using 22 GB of disk, as follows:<br />
594M /boot<br />
35M /etc<br />
11G /home - monkeybot.log is 7.3GB<br />
25M /opt<br />
2.2G /root<br />
4.0K /srv<br />
36K /tmp<br />
2.1G /usr<br />
6.3G /var<br />
<br />
=== Software availability ===<br />
<br />
This table is to track, for the different distros under consideration, whether the software we need is available within its repositories. We want to minimize the number of applications which have to be maintained manually.<br />
<br />
Key:<br />
* B: in distro's base repository<br />
* A: in an additional repository provided by the distro<br />
* T: in a third-party repository<br />
* ~: not available in any known repository<br />
* ?: availability unknown<br />
<br />
{| border="1"<br />
!<br />
!CentOS / Rocky / Alma 9<br />
!Debian 12<br />
!Ubuntu 22.04<br />
|-<br />
|postfix<br />
|B 3.5.9<br />
|B 3.7.5<br />
|B 3.6.4<br />
|-<br />
|mailman<br />
|~<br />
|B 3.3.8<br />
|A (3) 20200530<br />
|-<br />
|postgrey<br />
|T 1.37<sup>EPEL</sup><br />
|B 1.37<br />
|A 1.36<br />
|-<br />
|mediawiki<br />
|~<br />
|B 1.39<br />
|A 1.35<br />
|-<br />
|infobot<br />
|~<br />
|~<br />
|~<br />
|-<br />
|trac<br />
|~<br />
|[https://packages.debian.org/bookworm-backports/trac A 1.6] (backports)<br />
|A 1.5.3<br />
|-<br />
|apache<br />
|B 2.4.53<br />
|B 2.4.57<br />
|B 2.4.52<br />
|-<br />
|nginx<br />
|B 1.20.1 / 1.22.1<br />
|B 1.22.1<br />
|B 1.18.0<br />
|-<br />
|php<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|B 8.1<br />
|-<br />
|php-fpm<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|A 8.1<br />
|-<br />
|python2<br />
|~<br />
|[https://wiki.debian.org/Python/FAQ#Python_2_support ~]<br />
|A 2.7.18<br />
|-<br />
|python3<br />
|B 3.9.16<br />
|B 3.11.2<br />
|B 3.10.4<br />
|-<br />
|perl5<br />
|B 5.32<br />
|B 5.36<br />
|B 5.34<br />
|-<br />
|mariadb<br />
|B 10.5<br />
|B 10.11<br />
|A 10.6<br />
|-<br />
|mysql<br />
|B 8.0<br />
|~<br />
|B 8.0<br />
|-<br />
|sqlite<br />
|B 3.34<br />
|B 3.40<br />
|B 3.37<br />
|-<br />
|fail2ban<br />
|T 1.0.2<sup>EPEL</sup><br />
|B 1.0.2<br />
|A 0.11.2<br />
|-<br />
|certbot<br />
|T 2.6.0<sup>EPEL</sup><br />
|B 2.1.0<br />
|A 1.21.0<br />
|-<br />
|}<br />
<br />
Third-party repositories:<br />
* EPEL - [https://docs.fedoraproject.org/en-US/epel/ Extra Packages for Enterprise Linux]<br />
<br />
== Nice-to-haves ==<br />
<br />
* We have an archive of static web pages from the pre-2007 server "penguin" - it would be nice to make this history available somehow.<br />
<br />
== Migration Notes ==<br />
New virtual server:<br />
* Name: penguin<br />
* OS: Debian 12<br />
* Region: Atlanta<br />
* Plan: Nanode 1GB<br />
* IPv4: 139.144.29.132<br />
* IPv6: 2600:3c02::f03c:94ff:fe10:c62f<br />
<br />
New staging server:<br />
* Name: nestling<br />
* OS: Debian 11<br />
* Region: Chicago<br />
* Plan: Nanode 1GB<br />
* IPv4: 172.234.26.233<br />
* IPv6: 2600:3c06::f03c:95ff:fed6:b745<br />
This server was selected to run this OS version and location because it was the only image and location that featured cloud-init which was necessary for automated builds. Once Debian 12 gets that feature, we'll migrate over.<br />
<br />
=== Server Setup Steps ===<br />
I'm setting up ansible to do the server build and configuration entirely. Nesting is the staging server.<br />
Here are the steps completed:<br />
* Create or rebuild new linode, with cloud-init that adds admin users and ssh public keys.<br />
* Set hostname, /etc/hosts, disable root ssh login<br />
* Add board group and create board home directory<br />
* apt update<br />
* Install apache, mariadb, php<br />
* Install and run certbot<br />
* Install mediawiki and restore images and sql data<br />
<br />
Currently testing:<br />
* Mail - mua, postfix, opendkim, SPF, DKIM, DMARC<br />
<br />
Next steps:<br />
* Mail - aliases structure, spam filtering<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
[[Category:Migration]]</div>Ldaberkohttps://www.wplug.org/index.php?title=2024_Server_Migration&diff=49282024 Server Migration2024-06-27T16:22:57Z<p>Ldaberko: </p>
<hr />
<div>This page is to collect information about our current configuration and options for switching to a new server going forward, since CentOS 7 goes end-of-life at 2024-06-30. Please feel free to edit to add missing information or correct errors.<br />
<br />
== Server selection ==<br />
<br />
[https://www.linode.com/pricing?r=30335eb136f2c5f7fa3429dce9f15bea836f81d3 Linode] has been acquired by Akamai and raised their prices. Could potentially downgrade from the $12/mo (2GB RAM) plan to the $5 (1GB RAM "Nanode") plan depending on distro system requirements. Could also consider dropping paid backup service or using something different.<br />
<br />
Other VPS providers can be considered, not sure if they are any cheaper/better.<br />
<br />
=== Cloud Plans ===<br />
Looking at 1GB and 2GB plans.<br />
{| class="wikitable"<br />
! Vendor !! Plan !! $/Mo !! Memory !! CPU !! Storage !! Transfer<br />
|-<br />
| Linode || Nanode 1GB || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Linode || Linode 2GB || $12 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| DigitalOcean || 1GiB || $6 || 1GiB || 1 || 25GiB || 1TB<br />
|-<br />
| DigitalOcean || 2GiB || $12 || 2GiB || 1 || 50GiB || 2TB<br />
|-<br />
| Hostwinds || || $4.99 || 1GB || 1 || 30GB || 1TB<br />
|-<br />
| Hostwinds || || $9.90 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| Vultr || || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Vultr || || $10 || 2GB || 1 || 55GB || 2TB<br />
|}<br />
All services seem to be similar, with price differences only by a dollar or two.<br />
<br />
== OS selection ==<br />
<br />
CentOS Linux is dead. CentOS Stream is only viable as long as Red Hat/IBM has a business case for it. Can consider other options like pure Debian or Ubuntu LTS.<br />
<br />
=== Service enumeration ===<br />
<br />
Services that are currently running on the WPLUG Linode server. These should include things that are user-facing only, not infrastructure.<br />
<br />
* E-mail (Postfix)<br />
* Mailing lists (Mailman)<br />
* Wiki (MediaWiki)<br />
* Monkeybot IRC bot (infobot)<br />
** While one of the oldest WPLUG services, since [[IRC|freenode]] is essentially dead, there may not be good reason to keep it alive.<br />
* Ticketing system (Trac)<br />
** This is [https://trac.wplug.org/wplug-internet/report/6 virtually unused], likely not worth deploying.<br />
<br />
Infrastructure software which supports the services above.<br />
<br />
* Web server (Apache) - it would be possible to use Nginx instead, but I (Vance) am not familiar with setting it up<br />
* PHP (Apache mod_php) for MediaWiki - could be replaced with PHP-FPM<br />
* Let's Encrypt for TLS certificate (certbot)<br />
* Python for Mailman, Let's Encrypt, and Trac<br />
* Perl for Monkeybot<br />
* MariaDB for MediaWiki - may be [http://www.mediawiki.org/wiki/Compatibility#Database possible] to use SQLite or PostgreSQL instead<br />
* Greylisting daemon (Postgrey)<br />
* Fail2ban<br />
<br />
=== Support lifetime ===<br />
<br />
* CentOS Stream 9 - [https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates 2027-05-31] (limited to RHEL Full Support lifetime)<br />
* Rocky Linux 9 - [https://wiki.rockylinux.org/rocky/version/ 2032-05-31]<br />
* AlmaLinux 9 - [https://wiki.almalinux.org/release-notes/#almalinux-9 2032-05-31]<br />
* Debian 12 "bookworm" - [https://www.debian.org/News/2023/20230610.en.html 2028-06-10 or later]<br />
* Ubuntu 22.04 LTS - [http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Releases 2027-04]<br />
<br />
=== System requirements ===<br />
{| border="1"<br />
!<br />
!CPU<br />
!RAM<br />
!Disk<br />
|-<br />
|[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#system-requirements-reference_installing-RHEL CentOS] / Rocky / Alma 9<br />
|amd64, arm64, ppc64el<br />
|1.5 GB<br />
|10 GB<br />
|-<br />
|[https://www.debian.org/releases/bookworm/amd64/ch03s04.en.html Debian 12]<br />
|amd64, arm64, i386 (686 or higher), ppc64el, mipsel, mips64el<br />
|512 MB<br />
|4 GB<br />
|-<br />
|[https://ubuntu.com/server/docs/installation Ubuntu 22.04]<br />
|1 GHz amd64, arm64, ppc64el<br />
|1 GB<br />
|2.5 GB<br />
|-<br />
|}<br />
<br />
Currently we are using 22 GB of disk, as follows:<br />
594M /boot<br />
35M /etc<br />
11G /home - monkeybot.log is 7.3GB<br />
25M /opt<br />
2.2G /root<br />
4.0K /srv<br />
36K /tmp<br />
2.1G /usr<br />
6.3G /var<br />
<br />
=== Software availability ===<br />
<br />
This table is to track, for the different distros under consideration, whether the software we need is available within its repositories. We want to minimize the number of applications which have to be maintained manually.<br />
<br />
Key:<br />
* B: in distro's base repository<br />
* A: in an additional repository provided by the distro<br />
* T: in a third-party repository<br />
* ~: not available in any known repository<br />
* ?: availability unknown<br />
<br />
{| border="1"<br />
!<br />
!CentOS / Rocky / Alma 9<br />
!Debian 12<br />
!Ubuntu 22.04<br />
|-<br />
|postfix<br />
|B 3.5.9<br />
|B 3.7.5<br />
|B 3.6.4<br />
|-<br />
|mailman<br />
|~<br />
|B 3.3.8<br />
|A (3) 20200530<br />
|-<br />
|postgrey<br />
|T 1.37<sup>EPEL</sup><br />
|B 1.37<br />
|A 1.36<br />
|-<br />
|mediawiki<br />
|~<br />
|B 1.39<br />
|A 1.35<br />
|-<br />
|infobot<br />
|~<br />
|~<br />
|~<br />
|-<br />
|trac<br />
|~<br />
|[https://packages.debian.org/bookworm-backports/trac A 1.6] (backports)<br />
|A 1.5.3<br />
|-<br />
|apache<br />
|B 2.4.53<br />
|B 2.4.57<br />
|B 2.4.52<br />
|-<br />
|nginx<br />
|B 1.20.1 / 1.22.1<br />
|B 1.22.1<br />
|B 1.18.0<br />
|-<br />
|php<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|B 8.1<br />
|-<br />
|php-fpm<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|A 8.1<br />
|-<br />
|python2<br />
|~<br />
|[https://wiki.debian.org/Python/FAQ#Python_2_support ~]<br />
|A 2.7.18<br />
|-<br />
|python3<br />
|B 3.9.16<br />
|B 3.11.2<br />
|B 3.10.4<br />
|-<br />
|perl5<br />
|B 5.32<br />
|B 5.36<br />
|B 5.34<br />
|-<br />
|mariadb<br />
|B 10.5<br />
|B 10.11<br />
|A 10.6<br />
|-<br />
|mysql<br />
|B 8.0<br />
|~<br />
|B 8.0<br />
|-<br />
|sqlite<br />
|B 3.34<br />
|B 3.40<br />
|B 3.37<br />
|-<br />
|fail2ban<br />
|T 1.0.2<sup>EPEL</sup><br />
|B 1.0.2<br />
|A 0.11.2<br />
|-<br />
|certbot<br />
|T 2.6.0<sup>EPEL</sup><br />
|B 2.1.0<br />
|A 1.21.0<br />
|-<br />
|}<br />
<br />
Third-party repositories:<br />
* EPEL - [https://docs.fedoraproject.org/en-US/epel/ Extra Packages for Enterprise Linux]<br />
<br />
== Nice-to-haves ==<br />
<br />
* We have an archive of static web pages from the pre-2007 server "penguin" - it would be nice to make this history available somehow.<br />
<br />
== Migration Notes ==<br />
New virtual server:<br />
* Name: penguin<br />
* OS: Debian 12<br />
* Region: Atlanta<br />
* Plan: Nanode 1GB<br />
* IPv4: 139.144.29.132<br />
* IPv6: 2600:3c02::f03c:94ff:fe10:c62f<br />
<br />
A and AAAA records added to wplug.org domain setup<br />
<br />
=== Server Setup Steps ===<br />
# apt update<br />
# adduser jdoe<br />
# copy ssh key<br />
# usermod -aG sudo jdoe<br />
<br />
Need to set hostname<br />
<br />
<br />
<br />
<br />
<br />
<br />
[[Category:Migration]]</div>Ldaberkohttps://www.wplug.org/index.php?title=2024_Server_Migration&diff=49272024 Server Migration2024-02-27T04:57:37Z<p>Ldaberko: </p>
<hr />
<div>This page is to collect information about our current configuration and options for switching to a new server going forward, since CentOS 7 goes end-of-life at 2024-06-30. Please feel free to edit to add missing information or correct errors.<br />
<br />
== Server selection ==<br />
<br />
[https://www.linode.com/pricing?r=30335eb136f2c5f7fa3429dce9f15bea836f81d3 Linode] has been acquired by Akamai and raised their prices. Could potentially downgrade from the $12/mo (2GB RAM) plan to the $5 (1GB RAM "Nanode") plan depending on distro system requirements. Could also consider dropping paid backup service or using something different.<br />
<br />
Other VPS providers can be considered, not sure if they are any cheaper/better.<br />
<br />
=== Cloud Plans ===<br />
Looking at 1GB and 2GB plans.<br />
{| class="wikitable"<br />
! Vendor !! Plan !! $/Mo !! Memory !! CPU !! Storage !! Transfer<br />
|-<br />
| Linode || Nanode 1GB || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Linode || Linode 2GB || $12 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| DigitalOcean || 1GiB || $6 || 1GiB || 1 || 25GiB || 1TB<br />
|-<br />
| DigitalOcean || 2GiB || $12 || 2GiB || 1 || 50GiB || 2TB<br />
|-<br />
| Hostwinds || || $4.99 || 1GB || 1 || 30GB || 1TB<br />
|-<br />
| Hostwinds || || $9.90 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| Vultr || || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Vultr || || $10 || 2GB || 1 || 55GB || 2TB<br />
|}<br />
All services seem to be similar, with price differences only by a dollar or two.<br />
<br />
== OS selection ==<br />
<br />
CentOS Linux is dead. CentOS Stream is only viable as long as Red Hat/IBM has a business case for it. Can consider other options like pure Debian or Ubuntu LTS.<br />
<br />
=== Service enumeration ===<br />
<br />
Services that are currently running on the WPLUG Linode server. These should include things that are user-facing only, not infrastructure.<br />
<br />
* E-mail (Postfix)<br />
* Mailing lists (Mailman)<br />
* Wiki (MediaWiki)<br />
* Monkeybot IRC bot (infobot)<br />
** While one of the oldest WPLUG services, since [[IRC|freenode]] is essentially dead, there may not be good reason to keep it alive.<br />
* Ticketing system (Trac)<br />
** This is [https://trac.wplug.org/wplug-internet/report/6 virtually unused], likely not worth deploying.<br />
<br />
Infrastructure software which supports the services above.<br />
<br />
* Web server (Apache) - it would be possible to use Nginx instead, but I (Vance) am not familiar with setting it up<br />
* PHP (Apache mod_php) for MediaWiki - could be replaced with PHP-FPM<br />
* Let's Encrypt for TLS certificate (certbot)<br />
* Python for Mailman, Let's Encrypt, and Trac<br />
* Perl for Monkeybot<br />
* MariaDB for MediaWiki - may be [http://www.mediawiki.org/wiki/Compatibility#Database possible] to use SQLite or PostgreSQL instead<br />
* Greylisting daemon (Postgrey)<br />
* Fail2ban<br />
<br />
=== Support lifetime ===<br />
<br />
* CentOS Stream 9 - [https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates 2027-05-31] (limited to RHEL Full Support lifetime)<br />
* Rocky Linux 9 - [https://wiki.rockylinux.org/rocky/version/ 2032-05-31]<br />
* AlmaLinux 9 - [https://wiki.almalinux.org/release-notes/#almalinux-9 2032-05-31]<br />
* Debian 12 "bookworm" - [https://www.debian.org/News/2023/20230610.en.html 2028-06-10 or later]<br />
* Ubuntu 22.04 LTS - [http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Releases 2027-04]<br />
<br />
=== System requirements ===<br />
{| border="1"<br />
!<br />
!CPU<br />
!RAM<br />
!Disk<br />
|-<br />
|[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#system-requirements-reference_installing-RHEL CentOS] / Rocky / Alma 9<br />
|amd64, arm64, ppc64el<br />
|1.5 GB<br />
|10 GB<br />
|-<br />
|[https://www.debian.org/releases/bookworm/amd64/ch03s04.en.html Debian 12]<br />
|amd64, arm64, i386 (686 or higher), ppc64el, mipsel, mips64el<br />
|512 MB<br />
|4 GB<br />
|-<br />
|[https://ubuntu.com/server/docs/installation Ubuntu 22.04]<br />
|1 GHz amd64, arm64, ppc64el<br />
|1 GB<br />
|2.5 GB<br />
|-<br />
|}<br />
<br />
Currently we are using 22 GB of disk, as follows:<br />
594M /boot<br />
35M /etc<br />
11G /home - monkeybot.log is 7.3GB<br />
25M /opt<br />
2.2G /root<br />
4.0K /srv<br />
36K /tmp<br />
2.1G /usr<br />
6.3G /var<br />
<br />
=== Software availability ===<br />
<br />
This table is to track, for the different distros under consideration, whether the software we need is available within its repositories. We want to minimize the number of applications which have to be maintained manually.<br />
<br />
Key:<br />
* B: in distro's base repository<br />
* A: in an additional repository provided by the distro<br />
* T: in a third-party repository<br />
* ~: not available in any known repository<br />
* ?: availability unknown<br />
<br />
{| border="1"<br />
!<br />
!CentOS / Rocky / Alma 9<br />
!Debian 12<br />
!Ubuntu 22.04<br />
|-<br />
|postfix<br />
|B 3.5.9<br />
|B 3.7.5<br />
|B 3.6.4<br />
|-<br />
|mailman<br />
|~<br />
|B 3.3.8<br />
|A (3) 20200530<br />
|-<br />
|postgrey<br />
|T 1.37<sup>EPEL</sup><br />
|B 1.37<br />
|A 1.36<br />
|-<br />
|mediawiki<br />
|~<br />
|B 1.39<br />
|A 1.35<br />
|-<br />
|infobot<br />
|~<br />
|~<br />
|~<br />
|-<br />
|trac<br />
|~<br />
|[https://packages.debian.org/bookworm-backports/trac A 1.6] (backports)<br />
|A 1.5.3<br />
|-<br />
|apache<br />
|B 2.4.53<br />
|B 2.4.57<br />
|B 2.4.52<br />
|-<br />
|nginx<br />
|B 1.20.1 / 1.22.1<br />
|B 1.22.1<br />
|B 1.18.0<br />
|-<br />
|php<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|B 8.1<br />
|-<br />
|php-fpm<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|A 8.1<br />
|-<br />
|python2<br />
|~<br />
|[https://wiki.debian.org/Python/FAQ#Python_2_support ~]<br />
|A 2.7.18<br />
|-<br />
|python3<br />
|B 3.9.16<br />
|B 3.11.2<br />
|B 3.10.4<br />
|-<br />
|perl5<br />
|B 5.32<br />
|B 5.36<br />
|B 5.34<br />
|-<br />
|mariadb<br />
|B 10.5<br />
|B 10.11<br />
|A 10.6<br />
|-<br />
|mysql<br />
|B 8.0<br />
|~<br />
|B 8.0<br />
|-<br />
|sqlite<br />
|B 3.34<br />
|B 3.40<br />
|B 3.37<br />
|-<br />
|fail2ban<br />
|T 1.0.2<sup>EPEL</sup><br />
|B 1.0.2<br />
|A 0.11.2<br />
|-<br />
|certbot<br />
|T 2.6.0<sup>EPEL</sup><br />
|B 2.1.0<br />
|A 1.21.0<br />
|-<br />
|}<br />
<br />
Third-party repositories:<br />
* EPEL - [https://docs.fedoraproject.org/en-US/epel/ Extra Packages for Enterprise Linux]<br />
<br />
== Nice-to-haves ==<br />
<br />
* We have an archive of static web pages from the pre-2007 server "penguin" - it would be nice to make this history available somehow.<br />
<br />
<br />
[[Category:Migration]]</div>Ldaberkohttps://www.wplug.org/index.php?title=2024_Server_Migration&diff=49262024 Server Migration2024-02-27T04:41:19Z<p>Ldaberko: </p>
<hr />
<div>This page is to collect information about our current configuration and options for switching to a new server going forward, since CentOS 7 goes end-of-life at 2024-06-30. Please feel free to edit to add missing information or correct errors.<br />
<br />
== Server selection ==<br />
<br />
[https://www.linode.com/pricing?r=30335eb136f2c5f7fa3429dce9f15bea836f81d3 Linode] has been acquired by Akamai and raised their prices. Could potentially downgrade from the $12/mo (2GB RAM) plan to the $5 (1GB RAM "Nanode") plan depending on distro system requirements. Could also consider dropping paid backup service or using something different.<br />
<br />
Other VPS providers can be considered, not sure if they are any cheaper/better.<br />
<br />
=== Cloud Plans ===<br />
Looking at 1GB and 2GB plans.<br />
{| class="wikitable"<br />
! Vendor !! Plan !! $/Mo !! Memory !! CPU !! Storage !! Transfer<br />
|-<br />
| Linode || Nanode 1GB || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Linode || Linode 2GB || $12 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| DigitalOcean || 1GiB || $6 || 1GiB || 1 || 25GiB || 1TB<br />
|-<br />
| DigitalOcean || 2GiB || $12 || 2GiB || 1 || 50GiB || 2TB<br />
|-<br />
| Hostwinds || || $4.99 || 1GB || 1 || 30GB || 1TB<br />
|-<br />
| Hostwinds || || $9.90 || 2GB || 1 || 50GB || 2TB<br />
|-<br />
| Vultr || || $5 || 1GB || 1 || 25GB || 1TB<br />
|-<br />
| Vultr || || $10 || 2GB || 1 || 55GB || 2TB<br />
|}<br />
All services seem to be similar, with price differences only by a dollar or two.<br />
<br />
== OS selection ==<br />
<br />
CentOS Linux is dead. CentOS Stream is only viable as long as Red Hat/IBM has a business case for it. Can consider other options like pure Debian or Ubuntu LTS.<br />
<br />
=== Service enumeration ===<br />
<br />
Services that are currently running on the WPLUG Linode server. These should include things that are user-facing only, not infrastructure.<br />
<br />
* E-mail (Postfix)<br />
* Mailing lists (Mailman)<br />
* Wiki (MediaWiki)<br />
* Monkeybot IRC bot (infobot)<br />
** While one of the oldest WPLUG services, since [[IRC|freenode]] is essentially dead, there may not be good reason to keep it alive.<br />
* Ticketing system (Trac)<br />
** This is [https://trac.wplug.org/wplug-internet/report/6 virtually unused], likely not worth deploying.<br />
<br />
Infrastructure software which supports the services above.<br />
<br />
* Web server (Apache) - it would be possible to use Nginx instead, but I (Vance) am not familiar with setting it up<br />
* PHP (Apache mod_php) for MediaWiki - could be replaced with PHP-FPM<br />
* Let's Encrypt for TLS certificate (certbot)<br />
* Python for Mailman, Let's Encrypt, and Trac<br />
* Perl for Monkeybot<br />
* MariaDB for MediaWiki - may be [http://www.mediawiki.org/wiki/Compatibility#Database possible] to use SQLite or PostgreSQL instead<br />
* Greylisting daemon (Postgrey)<br />
* Fail2ban<br />
<br />
=== Support lifetime ===<br />
<br />
* CentOS Stream 9 - [https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates 2027-05-31] (limited to RHEL Full Support lifetime)<br />
* Rocky Linux 9 - [https://wiki.rockylinux.org/rocky/version/ 2032-05-31]<br />
* AlmaLinux 9 - [https://wiki.almalinux.org/release-notes/#almalinux-9 2032-05-31]<br />
* Debian 12 "bookworm" - [https://www.debian.org/News/2023/20230610.en.html 2028-06-10 or later]<br />
* Ubuntu 22.04 LTS - [http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Releases 2027-04]<br />
<br />
=== System requirements ===<br />
{| border="1"<br />
!<br />
!CPU<br />
!RAM<br />
!Disk<br />
|-<br />
|[https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/performing_a_standard_rhel_9_installation/index#system-requirements-reference_installing-RHEL CentOS] / Rocky / Alma 9<br />
|amd64, arm64, ppc64el<br />
|1.5 GB<br />
|10 GB<br />
|-<br />
|[https://www.debian.org/releases/bookworm/amd64/ch03s04.en.html Debian 12]<br />
|amd64, arm64, i386 (686 or higher), ppc64el, mipsel, mips64el<br />
|512 MB<br />
|4 GB<br />
|-<br />
|[https://ubuntu.com/server/docs/installation Ubuntu 22.04]<br />
|1 GHz amd64, arm64, ppc64el<br />
|1 GB<br />
|2.5 GB<br />
|-<br />
|}<br />
<br />
Currently we are using 22 GB of disk, as follows:<br />
594M /boot<br />
35M /etc<br />
11G /home<br />
25M /opt<br />
2.2G /root<br />
4.0K /srv<br />
36K /tmp<br />
2.1G /usr<br />
6.3G /var<br />
<br />
=== Software availability ===<br />
<br />
This table is to track, for the different distros under consideration, whether the software we need is available within its repositories. We want to minimize the number of applications which have to be maintained manually.<br />
<br />
Key:<br />
* B: in distro's base repository<br />
* A: in an additional repository provided by the distro<br />
* T: in a third-party repository<br />
* ~: not available in any known repository<br />
* ?: availability unknown<br />
<br />
{| border="1"<br />
!<br />
!CentOS / Rocky / Alma 9<br />
!Debian 12<br />
!Ubuntu 22.04<br />
|-<br />
|postfix<br />
|B 3.5.9<br />
|B 3.7.5<br />
|B 3.6.4<br />
|-<br />
|mailman<br />
|~<br />
|B 3.3.8<br />
|A (3) 20200530<br />
|-<br />
|postgrey<br />
|T 1.37<sup>EPEL</sup><br />
|B 1.37<br />
|A 1.36<br />
|-<br />
|mediawiki<br />
|~<br />
|B 1.39<br />
|A 1.35<br />
|-<br />
|infobot<br />
|~<br />
|~<br />
|~<br />
|-<br />
|trac<br />
|~<br />
|[https://packages.debian.org/bookworm-backports/trac A 1.6] (backports)<br />
|A 1.5.3<br />
|-<br />
|apache<br />
|B 2.4.53<br />
|B 2.4.57<br />
|B 2.4.52<br />
|-<br />
|nginx<br />
|B 1.20.1 / 1.22.1<br />
|B 1.22.1<br />
|B 1.18.0<br />
|-<br />
|php<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|B 8.1<br />
|-<br />
|php-fpm<br />
|B 8.0 / 8.1<br />
|B 8.2<br />
|A 8.1<br />
|-<br />
|python2<br />
|~<br />
|[https://wiki.debian.org/Python/FAQ#Python_2_support ~]<br />
|A 2.7.18<br />
|-<br />
|python3<br />
|B 3.9.16<br />
|B 3.11.2<br />
|B 3.10.4<br />
|-<br />
|perl5<br />
|B 5.32<br />
|B 5.36<br />
|B 5.34<br />
|-<br />
|mariadb<br />
|B 10.5<br />
|B 10.11<br />
|A 10.6<br />
|-<br />
|mysql<br />
|B 8.0<br />
|~<br />
|B 8.0<br />
|-<br />
|sqlite<br />
|B 3.34<br />
|B 3.40<br />
|B 3.37<br />
|-<br />
|fail2ban<br />
|T 1.0.2<sup>EPEL</sup><br />
|B 1.0.2<br />
|A 0.11.2<br />
|-<br />
|certbot<br />
|T 2.6.0<sup>EPEL</sup><br />
|B 2.1.0<br />
|A 1.21.0<br />
|-<br />
|}<br />
<br />
Third-party repositories:<br />
* EPEL - [https://docs.fedoraproject.org/en-US/epel/ Extra Packages for Enterprise Linux]<br />
<br />
== Nice-to-haves ==<br />
<br />
* We have an archive of static web pages from the pre-2007 server "penguin" - it would be nice to make this history available somehow.<br />
<br />
<br />
[[Category:Migration]]</div>Ldaberkohttps://www.wplug.org/index.php?title=Talk:2024_Server_Migration&diff=4925Talk:2024 Server Migration2024-02-27T03:57:22Z<p>Ldaberko: </p>
<hr />
<div><br />
== From Larry ==<br />
<br />
For service enumeration, I am in favor of removing monkeybot and trac.<br />
<br />
I'm not familiar with nginx so we should stick with Apache.<br />
<br />
I'd prefer to use SQLite if possible. One less service to manage.<br />
<br />
For the support lifetime comparisons, the Rocky and Alma distributions do require point release upgrades to stay current until End of Support, just like Ubuntu. Debian looks like they have new versions on a 2 year cycle with support going one year past the new release so the longest we can use one version of Debian is 3 years on average.<br />
<br />
I would prefer Debian even with the short lifecycle. However I'm not very familiar with any linux as server because I'm used to FreeBSD.<br />
<br />
Cloud service: I'm familiar with Linode and DigitalOcean. Their 2GB $12 offerings are identical. The lower level nanode and droplets differ by $1. I think any of those can handle the workload. It might fall on storage or traffic dictating our choice.<br />
<br />
One thing I'd like to try is to configure the server using Ansible. I think it's a good way to semi-automate future testing and installations.<br />
<br />
--[[User:Ldaberko|Ldaberko]] ([[User talk:Ldaberko|talk]]) 23:23, 15 February 2024 (UTC)<br />
<br />
I'm on board with your comments about monkeybot, trac, and Apache.<br />
<br />
I have no objection in principle to [https://www.mediawiki.org/wiki/Manual:SQLite using SQLite] - I think the limitations listed on that page are not a concern for our use. The instructions linked from that page about converting from MySQL/MariaDB to SQLite are from 2013; not sure if they are still valid or how much trouble it may be to convert. The other potential negative is the extra effort if someone in the future decides to switch back. But I think it's worth testing out.<br />
<br />
About distros, presumably point release upgrades on Rocky and Alma happen with a simple yum or dnf update like they do with "classic" CentOS. My thinking with Debian would be rather than sticking on the stable version for an extended time, to upgrade to the next version when it's available. I am given to understand that such upgrades tend to be smooth on Debian these days, but don't have direct experience.<br />
<br />
FreeBSD would be fine with me, but I don't have experience using it and would need to learn some of the system admin stuff. Presumably the programs involved would be configured the same way, so I could at least be useful there from the start. In a quick search I couldn't find any current info if it's possible to run FreeBSD on Linode or DigitalOcean, can look deeper into this if desired. (The docs about [https://www.digitalocean.com/community/tutorial-series/getting-started-with-freebsd running FreeBSD on DigitalOcean] are from 2015, don't know if it's currently supported. Also, DigitalOcean basically [https://docs.digitalocean.com/support/why-is-smtp-blocked/ forbids running a mail server], which seems to me a no-go.)<br />
<br />
I added [[2024_Server_Migration#System_requirements|info about disk usage]] (currently 22 GB for everything, including the OS) to the base page to allow comparison to [https://www.linode.com/pricing/#compute-shared Linode], [https://www.digitalocean.com/pricing/droplets DigitalOcean], or other plans. Currently web logs are kept for about a month, could maybe reduce usage by tweaking, also we've made no attempt to clean up other stuff.<br />
<br />
Likewise I don't have a problem with Ansible or similar, but don't have any experience with it. I would agree that our current way of doing things is very much "pet," not "cattle."<br />
<br />
--[[User:Vance|Vance]] ([[User talk:Vance|talk]]) 04:26, 24 February 2024 (UTC)<br />
<br />
I was not suggesting to install FreeBSD. I just said I had experience. After all it's a '''LINUX''' user group :-)<br />
<br />
I'll see if I can get an ansible setup for a demo.<br />
<br />
--[[User:Ldaberko|Ldaberko]] ([[User talk:Ldaberko|talk]]) 03:57, 27 February 2024 (UTC)</div>Ldaberkohttps://www.wplug.org/index.php?title=Talk:2024_Server_Migration&diff=4921Talk:2024 Server Migration2024-02-16T00:02:43Z<p>Ldaberko: /* From Larry */</p>
<hr />
<div><br />
== From Larry ==<br />
<br />
For service enumeration, I am in favor of removing monkeybot and trac.<br />
<br />
I'm not familiar with nginx so we should stick with Apache.<br />
<br />
I'd prefer to use SQLite if possible. One less service to manage.<br />
<br />
For the support lifetime comparisons, the Rocky and Alma distributions do require point release upgrades to stay current until End of Support, just like Ubuntu. Debian looks like they have new versions on a 2 year cycle with support going one year past the new release so the longest we can use one version of Debian is 3 years on average.<br />
<br />
I would prefer Debian even with the short lifecycle. However I'm not very familiar with any linux as server because I'm used to FreeBSD.<br />
<br />
Cloud service: I'm familiar with Linode and DigitalOcean. Their 2GB $12 offerings are identical. The lower level nanode and droplets differ by $1. I think any of those can handle the workload. It might fall on storage or traffic dictating our choice.<br />
<br />
One thing I'd like to try is to configure the server using Ansible. I think it's a good way to semi-automate future testing and installations.<br />
<br />
--[[User:Ldaberko|Ldaberko]] ([[User talk:Ldaberko|talk]]) 23:23, 15 February 2024 (UTC)</div>Ldaberkohttps://www.wplug.org/index.php?title=Talk:2024_Server_Migration&diff=4920Talk:2024 Server Migration2024-02-15T23:23:15Z<p>Ldaberko: Created page with " == From Larry == For service enumeration, I am in favor of removing monkeybot and trac. I'm not familiar with nginx so we should stick with Apache. I'd prefer to use SQLit..."</p>
<hr />
<div><br />
== From Larry ==<br />
<br />
For service enumeration, I am in favor of removing monkeybot and trac.<br />
<br />
I'm not familiar with nginx so we should stick with Apache.<br />
<br />
I'd prefer to use SQLite if possible. One less service to manage.<br />
<br />
For the support lifetime comparisons, the Rocky and Alma distributions do require point release upgrades to stay current until End of Support, just like Ubuntu. Debian looks like they have new versions on a 2 year cycle with support going one year past the new release so the longest we can use one version of Debian is 3 years on average.<br />
<br />
I would prefer Debian even with the short lifecycle. However I'm not very familiar with any linux as server because I'm used to FreeBSD.<br />
<br />
--[[User:Ldaberko|Ldaberko]] ([[User talk:Ldaberko|talk]]) 23:23, 15 February 2024 (UTC)</div>Ldaberkohttps://www.wplug.org/index.php?title=Meeting-20070210&diff=648Meeting-200702102007-02-10T01:28:26Z<p>Ldaberko: </p>
<hr />
<div>The first [[InstallFest]] of 2007 will be held on February 10th, 2007 from 10am to 3pm at Carnegie Mellon University, 3305 Newell-Simon Hall. An installfest is an interactive event where you bring your computer to either show off some neat aspect of Linux, or seek help about getting Linux running on your hardware.<br />
<br />
'''Note:''' The [http://pghcodingdojo.org/ Pittsburgh Coding Dojo] will be holding an event called [http://pghcodingdojo.org/index.php/Iteration_0 Iteration Zero] concurrent with the installfest. Follow the link for details.<br />
<br />
= I'd like help with =<br />
If you're going to be installing a particular piece of software and would like help with it, put your name on this list.<br />
* '''Scott Kiesling:'''I've got this old small notebook I got on ebay for $150 I've been playing around with. I'd like to put a minimal distro on it and see what I can get it to do. It has a cdrom but does not boot from it. It is a [http://linux.toshiba-dme.co.jp/linux/eng/spec.php3?model=PAP302U-T Toshiba Portege 3025CT] (mine has 96 Mb). [http://www.gweep.net/~sfoskett/linux/p3010-3.html Here] are the specs, more or less. It has an external CD player but I have not been able to get it to boot off of it. I had been incrementally getting to the point where I can boot, but hadn't quite made it. I've tried a few small distros like [http://www.puppylinux.org Puppy] and [http://www.featherweightlinux.org Featherweight], as well as some disk-based distros (there's an external floppy too), but now that I have just Googled [http://www.gweep.net/~sfoskett/linux/p3010.html this site] I may go with that. I will try to bring the relevant files on a CD. My last attempt had been variations on [http://marc.herbert.free.fr/linux/win2linstall.html this method], which got started booting (using Puppy if I remember correctly) but then got stuck. I hope I can get some help, if not, it will be fun to try. I'll probably have to leave around noon, or bring my kids in.<br />
** I'm not sure how much it may help, another option might be to set up the disk as a boot disk on another computer. I've got a little USB enclosure for 2.5 inch hard disks that works quite well that we could use to initialize the disk and pre-load it with installer software. -- [[User:Pwagstro | Patrick Wagstrom]]<br />
***I'd be happy to try it if you think it will work! -- [[User:Sfaius | Scott Kiesling]]<br />
<br />
* There's a project that maybe a couple people could help. It involves reworking an event signup website using some html, mysql, php (or perl or other language that can speak to mysql or postgres), and emailing out a copy of the information once someone signs up. I'm not stellar at website stuff, but if anyone is willing to help with it, it would be appreciated, and could help make someone very happy who is helping out wplug in a behind the scenes way. [[User:Tdr | Ted]]<br />
<br />
* I'm going to come in and check this installfest out. I've got a Dell Dimension 2400 that I can't install Ubuntu on. It freezes up on the first boot after installation. - [[User:Ldaberko | Larry Daberko]]<br />
<br />
= I can help with =<br />
If you can help out with a particular piece of software that you think other people may be installing, put your name on this list.<br />
* MythTV - [[User:Pwagstro | Patrick Wagstrom]]<br />
* FreeBSD/PHP/Apache/PostgreSQL - [[User:Wmoran | Bill Moran]]<br />
* Mandriva - [[User:Vance | Vance Kochenderfer]]<br />
<br />
* [[Installfest Services]] - [[User:Bseklecki | Brian A. Seklecki]]<br />
<br />
= I'm going to show off =<br />
If you've got a particular setup, peripheral, or application that you're planning on showing off at the installfest, put your name on this list.<br />
* Nintendo Wii Remotes controlling Linux applications - [[User:Pwagstro | Patrick Wagstrom]]<br />
<br />
= Meeting Staff =<br />
If you would like to volunteer to assist with this meeting, please add your name to one or more of the categories below.<br />
* Host: [[User:Wmoran | Bill Moran]]<br />
* Co-Host: [[User:Tdr | Ted Rodgers]]<br />
* Pizza: [[User:Pwagstro | Patrick Wagstrom]]<br />
* Donuts: [[User:Curlynoodle | David Kraus]]<br />
* Setup: [[User:Curlynoodle | David Kraus]], [[User:Pwagstro | Patrick Wagstrom]],[[User:Tdr | Ted Rodgers]]<br />
* Clean Up: [[User:Curlynoodle | David Kraus]], [[User: Vance | Vance Kochenderfer]]</div>Ldaberko