Oh that explains a lot. I keep answering you, LOL. Lets get you on the list, ffs.

As I mentioned to you once off list and a few times you wouldn't have seen onlist, the site has been tested on newer versions of MySQL so I'm not worried.

A 10-minute outage doesn't seem like a huge deal to me, given our site traffic. It also doesn't seem to matter much to me if its 2/24 or 3/1. However I've been hoping to find a time when Philip will be around in case there's some weird unexpected incompatibility.

As it stands my plan was to hit him up when I get back from the DMV this afternoon and then spend 10 minutes finding the button, hit it, and then poke around when it was done.

I'm not super familiar with RDS, but I figure I can hit the 'migrate' button.

If the 10 minutes bothers you and you'd rather do the clone-and-cut-over process, let me know and I can hand it off to you. I'm not even sure where to update the DB info in the PHP and stuff.

On 2/24/23 01:35, Ilan Rabinovitch wrote:

(as a non-list member I dont get replies if you're not replying to me as well)

the upgrade will resulted in a 10 minute outage for reg.

The way to work around it is clone the DB and cut over seems to be spin up a new cluster thats upgraded, cut over, kill old cluster.

On Fri, Feb 24, 2023 at 4:31 AM Ilan Rabinovitch <ilan@linuxfests.org mailto:ilan@linuxfests.org> wrote:

We really dont want the website down during  or leading up to SCALE.

Let me know if I need to grab this.

---------- Forwarded message ---------
From: *Amazon Web Services, Inc.* <no-reply-aws@amazon.com
<mailto:no-reply-aws@amazon.com>>
Date: Fri, Feb 24, 2023 at 4:29 AM
Subject: Amazon Aurora MySQL 1 (with MySQL 5.6 compatibility) will
reach end of life on February 28, 2023 [AWS Account: 355993445259]
[US-EAST-1]
To: <ilan@linuxfests.org <mailto:ilan@linuxfests.org>>


Hello,

You are receiving this message because you have one or more Amazon
Aurora MySQL clusters running a version of Aurora MySQL 1 (with
MySQL 5.6 compatibility) in the US-EAST-1 Region.

Amazon Aurora MySQL 1 (with MySQL 5.6 compatibility) will reach end
of life on February 28, 2023. We are providing you with a one week
notice so you have sufficient time to upgrade your database
cluster(s). You can find additional information needed to plan your
upgrade including a detailed timeline with milestones in the
'Preparing for Amazon Aurora MySQL-Compatible Edition version 1 end
of life' documentation [1].

Clusters that are running these deprecated engine versions after
March 1, 2023 will be upgraded on your behalf within a maintenance
window after March 1, 2023. The major version upgrade will start
within your maintenance window and typically finish within that
timeframe. Depending on the cluster and the database activity at the
time, the upgrade process may extend beyond the maintenance window.
For more information, please refer to the Amazon RDS maintenance
window [2].

The clusters we identified as affected are listed in your 'Affected
resources' tab of your AWS Health Dashboard. You may also find
clusters affected by this deprecation notice by utilizing the
'Finding clusters affected by this end-of-life process' guide [3].

Should you have any questions or concerns, the AWS Support Team is
available on re:Post [4] and via Premium Support [5].

[1]
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL56.EOL.html <https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL56.EOL.html>
[2]
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html#Concepts.DBMaintenance <https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html#Concepts.DBMaintenance>
[3]
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL56.EOL.html#find-cluster <https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL56.EOL.html#find-cluster>
[4] https://repost.aws/ <https://repost.aws/>
[5] https://aws.amazon.com/support <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://phd.aws.amazon.com/phd/home?region=us-east-1#/event-log?eventID=arn:aws:health:us-east-1::event/RDS/AWS_RDS_OPERATIONAL_NOTIFICATION/AWS_RDS_OPERATIONAL_NOTIFICATION_a6c3c27c8fa9a17b4966661b72fa8534d37f3090b2ca1b5040c2ff611f27a90f&amp;eventTab=details <https://phd.aws.amazon.com/phd/home?region=us-east-1#/event-log?eventID=arn:aws:health:us-east-1::event/RDS/AWS_RDS_OPERATIONAL_NOTIFICATION/AWS_RDS_OPERATIONAL_NOTIFICATION_a6c3c27c8fa9a17b4966661b72fa8534d37f3090b2ca1b5040c2ff611f27a90f&amp;eventTab=details>

---

scale-infra mailing list scale-infra@lists.linuxfests.org https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-infra

I've added you to the list because JFC.

Right. But to do a cutover you have to put either the cluster or the site in read-only mode, or take it down, then clone, then modify PHP, etc.

Either way you're talking a few minutes outage on either end, which doesn't seem much better to me than a single 10-minute outage.

I did just look through the migration process. It requires setting a new master password for the cluster. I'll make one up and put it in my own Bitwarden, but we REALLY need to get that sorted. If you can give me a budget, I can sort that out.

Phillip just confirmed he's around this afternoon, so here's my notice I plan to do an in-place-migration probably around 2:30 or 3pm when I get back from the DMV.

On 2/24/23 11:25, Ilan Rabinovitch wrote:

You have to modify the cluster. Take an outage. Then it comes back. Generally I'd agree 10 min is easy enough but  with two weeks to the show the site sees constant traffic

On Fri, Feb 24, 2023, 2:23 PM Phil Dibowitz <phil@ipom.com mailto:phil@ipom.com> wrote:

Oh that explains a lot. I keep answering you, LOL. Lets get you on the
list, ffs.

As I mentioned to you once off list and a few times you wouldn't have
seen onlist, the site has been tested on newer versions of MySQL so I'm
not worried.

A 10-minute outage doesn't seem like a huge deal to me, given our site
traffic. It also doesn't seem to matter much to me if its 2/24 or 3/1.
However I've been hoping to find a time when Philip will be around in
case there's some weird unexpected incompatibility.

As it stands my plan was to hit him up when I get back from the DMV
this
afternoon and then spend 10 minutes finding the button, hit it, and
then
poke around when it was done.

I'm not super familiar with RDS, but I figure I can hit the 'migrate'
button.

If the 10 minutes bothers you and you'd rather do the
clone-and-cut-over
process, let me know and I can hand it off to you. I'm not even sure
where to update the DB info in the PHP and stuff.


On 2/24/23 01:35, Ilan Rabinovitch wrote:
 > (as a non-list member I dont get replies if you're not replying
to me as
 > well)
 >
 > the upgrade will resulted in a 10 minute outage for reg.
 >
 > The way to work around it is clone the DB and cut over seems to
be spin
 > up a new cluster thats upgraded, cut over, kill old cluster.
 >
 > On Fri, Feb 24, 2023 at 4:31 AM Ilan Rabinovitch
<ilan@linuxfests.org <mailto:ilan@linuxfests.org>
 > <mailto:ilan@linuxfests.org <mailto:ilan@linuxfests.org>>> wrote:
 >
 >
 >
 >     We really dont want the website down during  or leading up to
SCALE.
 >
 >     Let me know if I need to grab this.
 >
 >     ---------- Forwarded message ---------
 >     From: *Amazon Web Services, Inc.* <no-reply-aws@amazon.com
<mailto:no-reply-aws@amazon.com>
 >     <mailto:no-reply-aws@amazon.com
<mailto:no-reply-aws@amazon.com>>>
 >     Date: Fri, Feb 24, 2023 at 4:29 AM
 >     Subject: Amazon Aurora MySQL 1 (with MySQL 5.6 compatibility)
will
 >     reach end of life on February 28, 2023 [AWS Account:
355993445259]
 >     [US-EAST-1]
 >     To: <ilan@linuxfests.org <mailto:ilan@linuxfests.org>
<mailto:ilan@linuxfests.org <mailto:ilan@linuxfests.org>>>
 >
 >
 >     Hello,
 >
 >     You are receiving this message because you have one or more
Amazon
 >     Aurora MySQL clusters running a version of Aurora MySQL 1 (with
 >     MySQL 5.6 compatibility) in the US-EAST-1 Region.
 >
 >     Amazon Aurora MySQL 1 (with MySQL 5.6 compatibility) will
reach end
 >     of life on February 28, 2023. We are providing you with a one
week
 >     notice so you have sufficient time to upgrade your database
 >     cluster(s). You can find additional information needed to
plan your
 >     upgrade including a detailed timeline with milestones in the
 >     'Preparing for Amazon Aurora MySQL-Compatible Edition version
1 end
 >     of life' documentation [1].
 >
 >     Clusters that are running these deprecated engine versions after
 >     March 1, 2023 will be upgraded on your behalf within a
maintenance
 >     window after March 1, 2023. The major version upgrade will start
 >     within your maintenance window and typically finish within that
 >     timeframe. Depending on the cluster and the database activity
at the
 >     time, the upgrade process may extend beyond the maintenance
window.
 >     For more information, please refer to the Amazon RDS maintenance
 >     window [2].
 >
 >     The clusters we identified as affected are listed in your
'Affected
 >     resources' tab of your AWS Health Dashboard. You may also find
 >     clusters affected by this deprecation notice by utilizing the
 >     'Finding clusters affected by this end-of-life process' guide
[3].
 >
 >     Should you have any questions or concerns, the AWS Support
Team is
 >     available on re:Post [4] and via Premium Support [5].
 >
 >     [1]
 >
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL56.EOL.html <https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL56.EOL.html> <https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL56.EOL.html <https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL56.EOL.html>>
 >     [2]
 >
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html#Concepts.DBMaintenance <https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html#Concepts.DBMaintenance> <https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html#Concepts.DBMaintenance <https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html#Concepts.DBMaintenance>>
 >     [3]
 >
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL56.EOL.html#find-cluster <https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL56.EOL.html#find-cluster> <https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL56.EOL.html#find-cluster <https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL56.EOL.html#find-cluster>>
 >     [4] https://repost.aws/ <https://repost.aws/>
<https://repost.aws/ <https://repost.aws/>>
 >     [5] https://aws.amazon.com/support
<https://aws.amazon.com/support> <https://aws.amazon.com/support
<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://phd.aws.amazon.com/phd/home?region=us-east-1#/event-log?eventID=arn:aws:health:us-east-1::event/RDS/AWS_RDS_OPERATIONAL_NOTIFICATION/AWS_RDS_OPERATIONAL_NOTIFICATION_a6c3c27c8fa9a17b4966661b72fa8534d37f3090b2ca1b5040c2ff611f27a90f&amp;eventTab=details <https://phd.aws.amazon.com/phd/home?region=us-east-1#/event-log?eventID=arn:aws:health:us-east-1::event/RDS/AWS_RDS_OPERATIONAL_NOTIFICATION/AWS_RDS_OPERATIONAL_NOTIFICATION_a6c3c27c8fa9a17b4966661b72fa8534d37f3090b2ca1b5040c2ff611f27a90f&amp;eventTab=details> <https://phd.aws.amazon.com/phd/home?region=us-east-1#/event-log?eventID=arn:aws:health:us-east-1::event/RDS/AWS_RDS_OPERATIONAL_NOTIFICATION/AWS_RDS_OPERATIONAL_NOTIFICATION_a6c3c27c8fa9a17b4966661b72fa8534d37f3090b2ca1b5040c2ff611f27a90f&amp;eventTab=details <https://phd.aws.amazon.com/phd/home?region=us-east-1#/event-log?eventID=arn:aws:health:us-east-1::event/RDS/AWS_RDS_OPERATIONAL_NOTIFICATION/AWS_RDS_OPERATIONAL_NOTIFICATION_a6c3c27c8fa9a17b4966661b72fa8534d37f3090b2ca1b5040c2ff611f27a90f&amp;eventTab=details>>
 >
 >
 > _______________________________________________
 > scale-infra mailing list
 > scale-infra@lists.linuxfests.org
<mailto:scale-infra@lists.linuxfests.org>
 > https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-infra
<https://lists.linuxfests.org/cgi-bin/mailman/listinfo/scale-infra>

-- 
Phil Dibowitz phil@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