- scale-infra - lists.linuxfests.org

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 04 Mar '24

04 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

Infra Hackathon @ SCALE
by Phil Dibowitz 26 Feb '24

26 Feb '24

Hey all, I was talking to Davide about doing an Infra hackathon at SCALE. We think we could both knock down a lot of the backlog, but also, others interested in helping who maybe would prefer to do it with some guidance could help as well. Things that would be a priority: * Re-syncing upstream cookbooks * Upgrading Chef/Cinc * Porting things to C9 (and cleaning up old support) * Debugging Web instability I was thinking perhaps a few hours on Thursday and Friday afternoon which are a bit quieter. And maybe Ilan can even find us a room! So several questions: * Are people interested in joining us? * Do people have day/time preferences? * Any other thoughts? -- 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

Re: [scale-infra] Mail server slow
by Phil Dibowitz 14 Feb '24

14 Feb '24

Adding -infra (back?) The docs are a lie! Thanks for fixing that, good catch. On 2/14/24 09:48, Ilan Rabinovitch wrote: > I dont actually think this is working. The paths listed in the cron > job were pointing to non-existent files/directories. > > https://github.com/socallinuxexpo/scale-chef/pull/308 > > On Sun, Nov 19, 2023 at 8:17 PM Phil Dibowitz <phil(a)ipom.com> wrote: >> >> https://github.com/socallinuxexpo/scale-chef/pull/303 should do the trick. >> >> >> >> On 11/18/23 10:45, Ilan Rabinovitch wrote: >>> OK. Hopefully we can get to it before Hannah has to send the next set >>> of emails, or maybe you can help her run the commands manually until >>> we get cron jobs set up. >>> >>> Hannah, also please let us know once you've picked a new mailing list too. >>> >>> On Tue, Nov 7, 2023 at 10:17 PM Phil Dibowitz <phil(a)ipom.com> wrote: >>>> >>>> Sorry, new job is really keeping me busy. Plus last weekend and this >>>> weekend are the last two weekends of the Metallica 2023 tour and I'm >>>> doing both. >>>> >>>> I will try to do the cron next week when I get back (I put it on my todo >>>> list app), but if you make a PR before then I won't take any offense. >>>> >>>> >>>> >>>> On 11/7/23 06:00, Ilan Rabinovitch wrote: >>>>> Phil, Let us know if you need a hand with setting up the cron jobs. >>>>> >>>>> Hannah, Let us know if you still want to switch mailing list tooling. >>>>> >>>>> On Sun, Oct 29, 2023 at 5:19 PM Ilan Rabinovitch <ilan(a)linuxfests.org >>>>> <mailto:ilan@linuxfests.org>> wrote: >>>>> >>>>> Running the queue from the CLI resulted in it completing in <5 >>>>> minutes. Definitely worth configuring it in cron when Phil has time. >>>>> >>>>> On Sun, Oct 29, 2023 at 6:06 PM Ilan Rabinovitch >>>>> <ilan(a)linuxfests.org <mailto:ilan@linuxfests.org>> wrote: >>>>> >>>>> Hannah, >>>>> >>>>> You mentioned a few times wanting to switch tools, have you >>>>> identified the new tool you prefer to use? >>>>> >>>>> PHPList by default expects the browser to remain open until the >>>>> send is complete. You can however set up a cronjob to >>>>> automatically process the queue in the background: >>>>> (https://www.phplist.org/manual/books/phplist-manual/page/methods-of-sending… <https://www.phplist.org/manual/books/phplist-manual/page/methods-of-sending…>) >>>>> >>>>> >>>>> Phil, Maybe the infra team can set that up to run per the docs >>>>> above? >>>>> >>>>> /usr/bin/php /var/www/html/lists/admin/index.php -pprocessqueue >>>>> -c/var/www/html/lists/config/config.php >>>>> >>>>> There's also a bunch of phplist settings the define how fast >>>>> mail is sent. >>>>> >>>>> You might what to look at these: >>>>> >>>>> MAX_PROCESS_MESSAGE >>>>> MAILQUEUE_BATCH_SIZE >>>>> MAILQUEUE_BATCH_PERIOD >>>>> MAILQUEUE_THROTTLE >>>>> MAILQUEUE_AUTOTHROTTLE >>>>> >>>>> I imagine they're set to defaults rather than tuned for our >>>>> workloads. >>>>> >>>>> >>>>> >>>>> >>>>> On Sun, Oct 29, 2023 at 4:23 PM Hannah Anderson >>>>> <hsanderson707(a)gmail.com <mailto:hsanderson707@gmail.com>> wrote: >>>>> >>>>> The server definitely does not send unless my laptop is on. >>>>> >>>>> I sent an email three days ago and it is still only at 30% >>>>> complete. It sends a bunch quickly then slows to a halt. >>>>> >>>>> On Sun, Oct 29, 2023, 7:01 AM Ilan Rabinovitch >>>>> <ilan(a)linuxfests.org <mailto:ilan@linuxfests.org>> wrote: >>>>> >>>>> If we're not moving off phplist to another tool we >>>>> might want to try the mailgun plugin for phplist so that >>>>> we get bounce handling. Not sure if it'll speed things >>>>> up to use the API without testing. >>>>> >>>>> https://resources.phplist.com/plugin/mailgun >>>>> <https://resources.phplist.com/plugin/mailgun> >>>>> >>>>> >>>>> On Wed, Oct 11, 2023 at 3:03 PM Ilan Rabinovitch >>>>> <ilan(a)linuxfests.org <mailto:ilan@linuxfests.org>> wrote: >>>>> >>>>> I believe the flow for emails here is phplist -> >>>>> postfix -> mailgun. We use mailgun here because EC2 >>>>> ip addresses had deliverability issues for us in the >>>>> past. Mailgun also handles signing all our emails >>>>> with DKIM, etc which simplifies things for us. Can >>>>> easily change it if we find it problematic. >>>>> >>>>> We're using serverless RDS for this which scales to >>>>> 0 anytime somebody hasn't touched phplist in 5-10 >>>>> minutes. >>>>> This saves us money but means the first attempt to >>>>> access it in a while will be slow. It shouldn't >>>>> impact sending, but we can extend that to an hour or >>>>> two of idle time if we want and see if that helps. >>>>> >>>>> In terms of when the sends were: >>>>> >>>>> Mailgun graph suggests emails were sent on 10/3/23 >>>>> at 6pm ET, 10/4 at 3am ET, and 10/6 at 1pm ET. >>>>> >>>>> Screenshot 2023-10-11 at 9.32.30 PM.png >>>>> >>>>> I configured the mailgun integration >>>>> <https://docs.datadoghq.com/integrations/mailgun/> >>>>> with Datadog so that we can have those stats >>>>> alongside system stats and postfix stats moving >>>>> forward. It wont help for past sends just new email >>>>> moving forward.. >>>>> >>>>> PHP List confirms the timeline above. >>>>> >>>>> Screenshot 2023-10-11 at 9.45.41 PM.png >>>>> Looks like postfix stats are failing to collect due >>>>> to a missing sudo configuration, but I'm not sure >>>>> it'd have anything useful for this investigation. >>>>> Not sure which cookbook/recipe you want that in. We >>>>> probably want it on all hosts, not just >>>>> mailman/phplist boxes, but defer to you. >>>>> >>>>> Oct 11 18:52:18 scale-lists2 sudo[3737505]: dd-agent >>>>> : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=list >>>>> Oct 11 18:52:18 scale-lists2 sudo[3737507]: >>>>> pam_unix(sudo:auth): conversation failed >>>>> Oct 11 18:52:18 scale-lists2 sudo[3737507]: >>>>> pam_unix(sudo:auth): auth could not identify >>>>> password for [dd-agent] >>>>> Oct 11 18:52:20 scale-lists2 sudo[3737507]: dd-agent >>>>> : command not allowed ; TTY=unknown ; PWD=/ ; >>>>> USER=root ; COMMAND=/bin/find >>>>> /var/spool/postfix/active -type f >>>>> >>>>> Looking at system graphs >>>>> <https://app.datadoghq.com/metric/explorer?start=1696194000000&end=169671234…> there's no spikes in memory, cpu or network around that time. >>>>> >>>>> One thing we should figure out outside of perf is >>>>> bounce handling. PHPlist says none of the emails we >>>>> send are bouncing, but mailgun shows over 1K bounces >>>>> per email campaign sent out. I imagine that's not >>>>> helping speed, but also makes us look like spammers. >>>>> >>>>> Screenshot 2023-10-11 at 9.50.24 PM.png >>>>> >>>>> >>>>> Anyways, that's all I can offer before I crash tonight. >>>>> >>>>> Good luck with the investigation. >>>>> >>>>> -Ilan >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Ilan Rabinovitch >>>>> Conference Chair >>>>> Southern California Linux Expo >>>>> 877-831-2569 x11 Voice >>>>> 818-442-1865 Mobile >>>>> ilan(a)linuxfests.org <mailto:ilan@linuxfests.org> Email >>>>> --- >>>>> Ask about sponsorship and speaking opportunities at >>>>> LinuxFests.org's upcoming events: >>>>> * SCALE 21x - March 14-17 2024 >>>>> * DevOpsDay LA - March 15, 2024 >>>>> * Texas Linux Fest - April 12-13, 2024 >>>>> >>>>> >>>>> On Wed, Oct 11, 2023 at 5:49 AM Phil Dibowitz >>>>> <phil(a)ipom.com <mailto:phil@ipom.com>> wrote: >>>>> >>>>> I'll dig into this tomorrow afternoon, thanks >>>>> for reporting. >>>>> >>>>> One thing that would be helpful is to know what >>>>> time you sent emails, >>>>> and what time it appeared to be done processing >>>>> so I could correlate >>>>> with the events you saw. >>>>> >>>>> Thanks! >>>>> >>>>> On 10/10/23 10:20, Hannah Anderson wrote: >>>>> > Hey Phil, >>>>> > >>>>> > I have noticed that the mail server has been >>>>> slow. It took 3 hours to >>>>> > process the last email I sent and did not >>>>> make it to 100% of the list. >>>>> > >>>>> > I thought this was a fluke, but it has >>>>> happened for the last 3 emails >>>>> > now. Any idea what could be wrong? >>>>> > >>>>> > Thanks, >>>>> > Hannah >>>>> > >>>>> > -- >>>>> > Without Wax >>>>> >>>>> -- >>>>> Phil Dibowitz phil(a)ipom.com <mailto:phil@ipom.com> >>>>> Open Source software and tech docs >>>>> Insanity Palace of Metallica >>>>> http://www.phildev.net/ >>>>> <http://www.phildev.net/> http://www.ipom.com/ >>>>> <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 >>>>> >>>>> >>>> >>>> -- >>>> 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 >>>> >>>> >> -- 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

web to Centos8
by Ilan Rabinovitch 12 Feb '24

12 Feb '24

Hi, I took a stab at updating the cookbooks we use for the website to use centos8. Motivation was getting a new version of php so we can use some drupal plugins that dont support php5.4, but i think this was on the backlog already for a while. https://github.com/socallinuxexpo/scale-chef/pull/283 To test this out, I spun up scale-web2 with a clone of the production scale-drupal database, and then pointed my host file at it for www.socallinuxexpo.org: I then tested the following: - chef runs complete end to end - Backing up / restoring static assets (see backup scripts in /usr/local/bin or in the scale-drupal cookbook) - browsing legacy static website (eg https://socallinuxexpo.org/past/2002/ https://socallinuxexpo.org/past/2003/) - Registering as a speaker, confirming that I got the email and that my account worked. - publishing the submitted talk - creating sponsors/exhibitors/blog post/events/etc Pending things: - Centos8 seems to default to using php-fpm instead of mod_php. Not opposed but it's different. Seems to work fine, but I've not load tested it or anything. - drush (https://www.drush.org/) packages no longer seemed to be present in centos or epel. remi seems to have it but the drush docs suggest we should be installing this in our drupal code base via composer instead of as a package. I dont have strong opinions, but we should figure out the right path before merging. Cheers, Ilan

4 43

Fwd: [Action Required] Upgrade Amazon Aurora Serverless v1 by December 31, 2024 [AWS Account: 355993445259] [US-EAST-1]
by Ilan Rabinovitch 28 Dec '23

28 Dec '23

looks like we have to migrate all our RDS instances. ---------- Forwarded message --------- From: 'Amazon Web Services, Inc.' via aws-linuxfests <aws(a)linuxfests.org> Date: Thu, Dec 28, 2023 at 1:42 AM Subject: [Action Required] Upgrade Amazon Aurora Serverless v1 by December 31, 2024 [AWS Account: 355993445259] [US-EAST-1] To: <aws(a)linuxfests.org> Hello, We are reaching out to let you know that as of December 31, 2024, Amazon Aurora will no longer support Serverless version 1 (v1). As per the Aurora Version Policy [1], we are providing 12 months notice to give you time to upgrade your database cluster(s). Aurora supports two versions of Serverless. We are only announcing the end of support for Serverless v1. Aurora Serverless v2 continues to be supported. We recommend that you proactively upgrade your databases running Amazon Aurora Serverless v1 to Amazon Aurora Serverless v2 at your convenience before December 31, 2024. Starting on or after 12:00 PM PST on December 31, 2024, if your Amazon Aurora Serverless v1 cluster has not been upgraded, Amazon Aurora will automatically upgrade your Amazon Aurora Serverless v1 cluster to Amazon Aurora Serverless v2 during your next scheduled cluster maintenance window. If your Aurora Serverless v1 cluster is running an engine version that is not available for Aurora Serverless v2, it will be upgraded to an engine version compatible with Aurora Serverless v2. How to determine which clusters are running Aurora Serverless v1? You can find information about the DB cluster on the AWS RDS console. Aurora Serverless v1 DB clusters show Serverless for Role in the Summary section of the cluster detail page [2]. Also a list of your affected clusters can be found in the 'Affected resources' tab of your AWS Health Dashboard. How to Upgrade to Aurora Serverless v2? You can upgrade your database cluster from Aurora Serverless v1 to Aurora Serverless v2 using the AWS SDK or CLI [3] by following these steps: * Convert your Aurora Serverless v1 database cluster to a provisioned cluster * Upgrade the provisioned cluster to the version that is supported with Aurora Serverless v2 * Add a Aurora Serverless v2 reader to the upgraded provisioned cluster and failover to it. Refer to our Aurora Serverless documentation [3] and also the blog on upgrading from Serverless v1 to Serverless v2 [4]. Please be aware of the following timeline: - From now through to December 31, 2024 - You can initiate upgrades of Amazon Aurora Serverless v1 to Amazon Aurora Serverless v2 at any time. - Starting September 1, 2024, you will no longer be able to create new Aurora Serverless v1 clusters or instances with either the AWS Console or the CLI. - Starting December 31, 2024, Amazon Aurora will upgrade your Aurora Serverless v1 cluster during your next maintenance window to Aurora Serverless v2. If you have any questions or concerns, please reach out to AWS Premium Support [5]. [1] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Version… [2] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverl… [3] https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverl… [4] https://aws.amazon.com/blogs/database/upgrade-from-amazon-aurora-serverless… [5] 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

Recovered: [Synthetics] Check on www.socallinuxexpo.org redirects to current SCALE year
by Datadog Alerting 24 Dec '23

24 Dec '23

[Recovered] [Synthetics] Check on www.socallinuxexpo.org redirects to current SCALE year @bala@socallinuxexpo.org @ilan@linuxfests.org @phil@ipom.com @slack-SCALE-infra @slack-infra @scale-infra@lists.linuxfests.org This alert was raised by account LinuxFests. View Test Run in Datadog: https://app.datadoghq.com/synthetics/details/mmg-4xw-gd4?resultId=235868048… View Test: https://app.datadoghq.com/synthetics/details/mmg-4xw-gd4 To manage your Datadog subscription, click here: https://app.datadoghq.com/account/preferences ©2023 Datadog Inc, 620 8th Ave, NYC

1 0

2026

2025

2024

2023

2022

scale-infra