- scale-infra - lists.linuxfests.org

Update from your Tech (online services) team!
by Phil Dibowitz 01 Feb '25

01 Feb '25

Hey all, As you probably saw in Slack, today we completed the lists migration. This includes: * Mailman2 (unsupported) => Mailman3 (supported!) * CentOS Stream 8 (unsupported) => CentOS Stream 9 (supported!) * PHPList 3.5.2 (doesn't work on modern PHP) => PHPList 3.6.14 (supports modern PHP!) * PHP 7.2 (unsupported) => PHP 8.2 (security support) This was part of a lot of work on the part of the team over the last 6-8 months, we only just finally pulled the last trigger today. I want to remind everyone: * For non-email interactions (moderation or tweaking settings is really the only thing here) you'll need to register for an account. It'll auto-associate with all your memberships (assuming you use the same email). * If you have any issues, please let me know, I'll happily sort you out, and attend to any moderation in the interim. I will answering any tags in slack or direct within 24 hours for the next week for sure, and in general until the conference. * The permission model is more sane in MM3, there's not some magical password you have to share (woo!), people are just assigned as owners, moderators, or members. So people can easily be added to share the moderation burden, or removed when they no longer should have access with minimal fuss. This brings us generally to a much better place with our webserver on CentOS Stream 10 and our Lists server on CentOS Stream 9 (mailman3 is not yet ready for 10, but it'll be a simple upgrade when it is). The next project will be moving reg. It's a bit trickier as it still requires python2, so we'll be containerizing it and moving it to CentOS Stream 10 after the conference (obviously this is reg's most critical time, so we won't be touching it until post-conf). Then we'll go about cleaning up all the old code throughout our codebase specific to CentOS 6, 7, and 8. So many thanks to Davide for countless Monday's hacking on all of this. And thanks to Hannah for helping with the migration today. -- Phil Dibowitz phil(a)ipom.com Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind." - Dr. Seuss

1 0

Final (probably) test
by Phil Dibowitz 31 Jan '25

31 Jan '25

Please ignore still. -- Phil Dibowitz phil(a)ipom.com Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind." - Dr. Seuss

1 0

test, please ignore
by Phil Dibowitz 31 Jan '25

31 Jan '25

test -- Phil Dibowitz phil(a)ipom.com Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind." - Dr. Seuss

1 0

test 2, please ignore
by Phil Dibowitz 31 Jan '25

31 Jan '25

test 2, please ignore. -- Phil Dibowitz phil(a)ipom.com Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind." - Dr. Seuss

1 0

test message, please ignore
by Phil Dibowitz 31 Jan '25

31 Jan '25

-- Phil Dibowitz phil(a)ipom.com Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind." - Dr. Seuss

1 0

All lists imported to mailman3 - PLEASE TEST
by Phil Dibowitz 02 Dec '24

02 Dec '24

All lists are imported to mailman3, aka lists2.socallinuxexpo.org. Davide and I will meet in January to do the final migration, which gives everyone one month to test the new setup. A version of this notice will go to -chairs and -infra - but ALL LISTS have been imported, so please work with your various teams to test if you feel necessary. I am not on all the lists, I'm putting it on individual Chairs to pass this along to your teams. Archives, list settings, memberships have all been imported and look good to us. THINGS TO TEST: * Send an email (<list>@lists2.socallinuxexpo.org)! It'll work, and GO TO EVERYONE ON THE NORMAL LIST, so it's worth noting somewhere in the email it's a test and discussions on that thread will not be preserved * Create an account on the webui so you can change your delivery settings * Checkout the archives, see if they fill you with joy * If you have weird requirements for your list - see if they're satisfied by the new setup! Thanks! -- Phil Dibowitz phil(a)ipom.com Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind." - Dr. Seuss

1 0

mailman3 is ready for INITIAL testing
by Phil Dibowitz 25 Nov '24

25 Nov '24

Davide and I spent most of today getting Mailman3 up and running. https://lists2.socallinuxexpo.org/mailman3/ is up with CentOS 9 and Mailman3. All the goodies are - I think - there, including archives. I've made a test list called scale-test you all can subscribe to if you like and start playing around. Various notes: * I have *not* yet tweaked all of it's settings to match our preferences, but I will soon. * I have also not imported existing lists or archives from mailman2, though that is possible. That's why I said 'initial' testing. I want to get a bit more familiar with the knobs and whistles. * The superuser account is in 1Password in the "Tech - online services" vault, which the Infra team and Ilan should have access to. * If you would like to _own_ a list, I can make a list, and assign it to you, but you'll need to register first. Anyone can register, it gives you no special permission though. * You do NOT need to register to join a list. If you later register, you'll then be able to manage your preferences through though the website. * I have *NOT* set up phplist or mailgun, as I'm rather hoping we'll move off of them, but if we decide not to, I'll setup both. * The standard / redirect still goes to an invalid mailman2 URL, I know. Just go to /mailman3 for now. -- Phil Dibowitz phil(a)ipom.com Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind." - Dr. Seuss

1 0

Fwd: [REMINDER] Amazon Aurora MySQL 2 (with MySQL 5.7 compatibility) will reach end of Standard Support on October 31, 2024 [AWS Account: 355993445259] [US-EAST-1]
by Ilan Rabinovitch 11 Oct '24

11 Oct '24

not sure if this impacts us. ---------- Forwarded message --------- From: 'Amazon Web Services, Inc.' via aws-linuxfests <aws(a)linuxfests.org> Date: Wed, Jul 31, 2024 at 12:44 PM Subject: [REMINDER] Amazon Aurora MySQL 2 (with MySQL 5.7 compatibility) will reach end of Standard Support on October 31, 2024 [AWS Account: 355993445259] [US-EAST-1] To: <aws(a)linuxfests.org> Hello, [AWS Health may periodically trigger reminder notifications about this communication if resources remain unresolved.] You are receiving this message because you have one or more Amazon Aurora MySQL clusters running a version of Aurora MySQL 2 (with MySQL 5.7 compatibility) on a provisioned instance in the US-EAST-1 Region. If you are running Amazon Aurora MySQL 2 (with MySQL 5.7 compatibility) in an Aurora Serverless v1 cluster, this communication does not apply to you. Amazon Aurora MySQL 2 (with MySQL 5.7 compatibility) will reach end of standard support on October 31, 2024. We are providing you with a periodic reminder, following up from our previous notice, so you have sufficient time to upgrade your database cluster(s). Please note that upgrading between major versions requires more extensive planning and testing than for a minor version and the process can take substantial time. We recommend that you upgrade your databases to the latest patch of the default minor version of Amazon Aurora MySQL 3, at your earliest convenience before October 31, 2024. For how to do the upgrades please consult our documentation [1]. Upgrades may be performed using in-place upgrade [2], snapshot and restore [3], or a high availability blue-green upgrade technique which can be fully managed using Amazon RDS Blue/Green Deployments [4]. The amount of downtime your system will experience depends on the upgrade technique chosen, as well as properties of your schema. Major version upgrades will require downtime and might require manual intervention and application changes. We will send you updates and reminders before the standard support deadline. You can find the latest information needed to plan your upgrade in our 'User Guide for Aurora' [5]. The affected clusters are listed in the 'Affected resources' tab of your AWS Health Dashboard. You can also find clusters which are affected by this deprecation notice by referring to the following user guide [6]. Amazon Aurora MySQL provides you with one year of free extended support over community MySQL 5.7, that reached end of life on October 31, 2023. If you need more time to complete the upgrades, you can use Amazon RDS Extended Support [7] for Aurora MySQL 2. RDS Extended Support [8] for Aurora is a paid service [9] that will provide up to 28 additional months of support for Aurora MySQL 2 until the end of extended support in February 2027. After October 31, 2024 all your databases continue running Aurora MySQL 2 will be automatically enrolled in RDS Extended Support. Charges for RDS Extended Support will start accruing from December 1, 2024. RDS Extended Support will only be offered for Aurora MySQL minor versions 2.11 and 2.12. If you plan to use Amazon Aurora MySQL 2 beyond end of standard support, please plan to be running your database(s) on one of these minor versions before October 31, 2024. If your databases are not running Aurora MySQL minor versions 2.11 or 2.12 by October 31, 2024 they will be upgraded before being enrolled into RDS Extended Support. This upgrade will occur during your maintenance window and can not be turned off. Should you have any questions or concerns, the AWS Support Team is available on AWS re:Post [10] and via AWS Support. [11] [1] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Up… [2] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Up… [3] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-restore… [4] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deploymen… [5] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL57… [6] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL57… [7] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/extended-suppo… [8] https://aws.amazon.com/blogs/database/introducing-amazon-rds-extended-suppo… [9] https://aws.amazon.com/rds/aurora/pricing/#Amazon_RDS_Extended_Support_costs [10] https://repost.aws/ [11] https://aws.amazon.com/support Sincerely, Amazon Web Services Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210 --- Reference: https://health.aws.amazon.com/health/home?region=us-east-1#/event-log?event…

2 4

Fwd: [REMINDER] Amazon Aurora MySQL 2 (with MySQL 5.7 compatibility) will reach end of Standard Support on October 31, 2024 [AWS Account: 355993445259] [US-EAST-1]
by Ilan Rabinovitch 30 Apr '24

30 Apr '24

---------- Forwarded message --------- From: 'Amazon Web Services, Inc.' via aws-linuxfests <aws(a)linuxfests.org> Date: Mon, Apr 29, 2024 at 4:41 PM Subject: [REMINDER] Amazon Aurora MySQL 2 (with MySQL 5.7 compatibility) will reach end of Standard Support on October 31, 2024 [AWS Account: 355993445259] [US-EAST-1] To: <aws(a)linuxfests.org> Hello, You are receiving this message because you have one or more Amazon Aurora MySQL clusters running a version of Aurora MySQL 2 (with MySQL 5.7 compatibility) on a provisioned instance in the US-EAST-1 Region. If you are running Amazon Aurora MySQL 2 (with MySQL 5.7 compatibility) in an Aurora Serverless v1 cluster, this communication does not apply to you. Amazon Aurora MySQL 2 (with MySQL 5.7 compatibility) will reach end of standard support on October 31, 2024. We are providing you with a 6-month reminder, following up from our previous 12-month notice, so you have sufficient time to upgrade your database cluster(s). Please note that upgrading between major versions requires more extensive planning and testing than for a minor version and the process can take substantial time. We recommend that you upgrade your databases to the latest patch of the default minor version of Amazon Aurora MySQL 3 (currently Aurora MySQL 3.04) or higher, at your earliest convenience before October 31, 2024. For how to do the upgrades please consult our documentation [1]. Upgrades may be performed using in-place upgrade [2], snapshot and restore [3], or a high availability blue-green upgrade technique which can be fully managed using Amazon RDS Blue/Green Deployments [4]. The amount of downtime your system will experience depends on the upgrade technique chosen, as well as properties of your schema. Major version upgrades will require downtime and might require manual intervention and application changes. We will send you updates and reminders before the standard support deadline. You can find the latest information needed to plan your upgrade in our 'User Guide for Aurora' [5]. The affected clusters are listed in the 'Affected resources' tab of your AWS Health Dashboard. You can also find clusters which are affected by this deprecation notice by referring to the following user guide [6]. Amazon Aurora MySQL provides you with one year of free extended support over community MySQL 5.7, that reached end of life on October 31, 2023. If you need more time to complete the upgrades, you can use Amazon RDS Extended Support [7] for Aurora MySQL 2. RDS Extended Support [8] for Aurora is a paid service [9] that will provide up to 28 additional months of support for Aurora MySQL 2 until the end of extended support in February 2027. After October 31, 2024 all your databases continue running Aurora MySQL 2 will be automatically enrolled in RDS Extended Support. Charges for RDS Extended Support will start accruing from December 1, 2024. RDS Extended Support will only be offered for Aurora MySQL minor versions 2.11 and 2.12. If you plan to use Amazon Aurora MySQL 2 beyond end of standard support, please plan to be running your database(s) on one of these minor versions before October 31, 2024. If your databases are not running Aurora MySQL minor versions 2.11 or 2.12 by October 31, 2024 they will be upgraded before being enrolled into RDS Extended Support. This upgrade will occur during your maintenance window and cannot be turned off. Should you have any questions or concerns, the AWS Support Team is available on AWS re:Post [10] and via AWS Support. [11] [1] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Up… [2] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Up… [3] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-restore… [4] https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deploymen… [5] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL57… [6] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL57… [7] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/extended-suppo… [8] https://aws.amazon.com/blogs/database/introducing-amazon-rds-extended-suppo… [9] https://aws.amazon.com/rds/aurora/pricing/#Amazon_RDS_Extended_Support_costs [10] https://repost.aws/ [11] https://aws.amazon.com/support Sincerely, Amazon Web Services Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210 --- Reference: https://health.aws.amazon.com/health/home?region=us-east-1#/event-log?event…

2 1

Fwd: [Action may be required] CentOS Linux 7 end of life notification [AWS Account: 355993445259] [US-EAST-1]
by Ilan Rabinovitch 05 Mar '24

05 Mar '24

I believe the only Centos 7 instance remaining is SCALEreg. ---------- Forwarded message --------- From: 'Amazon Web Services, Inc.' via aws-linuxfests <aws(a)linuxfests.org> Date: Mon, Mar 4, 2024 at 12:13 PM Subject: [Action may be required] CentOS Linux 7 end of life notification [AWS Account: 355993445259] [US-EAST-1] To: <aws(a)linuxfests.org> Hello, Your account has been identified as having started an instance or continuing to run CentOS Linux 7 instance(s) over the last 6 months. CentOS 7 will not receive any updates after June 30, 2024 [1]. A list of your affected instance(s) can be found under the "Affected resources" tab of your AWS Health Dashboard. It is important to take action by migrating to another Operating System before CentOS 7 reaches end of life. To understand more about the alternatives available to you to migrate your CentOS workloads on AWS, please refer to this page [2]. For any questions, please reach out to AWS Support [3]. [1] https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-an… [2] https://aws.amazon.com/linux/commercial-linux/centos/ [3] https://aws.amazon.com/support Sincerely, Amazon Web Services Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210 --- Reference: https://health.aws.amazon.com/health/home?region=us-east-1#/event-log?event…

1 0

2026

2025

2024

2023

2022

scale-infra