Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IBM closing DAL05, SJC01 and WDC01 data centers 4 April 2024 #3279

Closed
richardlau opened this issue Apr 4, 2023 · 12 comments
Closed

IBM closing DAL05, SJC01 and WDC01 data centers 4 April 2024 #3279

richardlau opened this issue Apr 4, 2023 · 12 comments

Comments

@richardlau
Copy link
Member

richardlau commented Apr 4, 2023

IBM has sent out this notifcation. We have a year (see "Key Milestones") to identify the servers affected and move them to another IBM data center.

Thank you for your business and trust in IBM as your valued business partner and cloud provider. We’re committed to your success and prioritizing your experience within our data center infrastructure.

We have made significant investments in our new IBM Cloud data centers and Multi-zone Regions (MZRs) designed to deliver a more resilient architecture with higher levels of network throughput and redundancy with our latest generation cloud technologies.

As part of this modernization strategy, we have made the decision to consolidate select data centers and help our customers shift operations to our newer and higher-capacity facilities, including the decision to close the following data center on April 04, 2024

• DAL05
• SJC01
• WDC01

This means you will need to migrate your workloads to one of our newer IBM Cloud data centers before this date – but don’t worry we can help ensure you pay the same or a lower price that you pay today for the same or a better configuration!

For our valued IBM Cloud® platform customers:

We recognize transferring data centers can be complex and costly, so we are offering:
• Two months free on replacement servers or services in our new data centers (Promo Code: DCMIGRATE2023) or Four months free when you optimize your IT infrastructure by migrating from Bare Metal to VSI or VPC (Promo Code: UPGRADE2VSI2023).
• The same or a lower price with a same or better configuration.
• Migration assistance. This includes a free architectural consultation with guidance on recommended configurations to help you transition and maximize solution performance. We have the support of a third-party partner available to help with your data migration at no charge. Additionally, we may be able to help with other migration requirements, depending on your needs

Your action needed:
• Identify impacted servers/services. Contact us through your IBM Cloud Portal (https://cloud.ibm.com/login) or reach out to the Customer Success team via live chat (https://www.ibm.com/cloud/data-centers?focusArea=WCP%20-%20Cloud%20services%20-%20all%20other&contactmodule) or by phone: (US) 866-597-9687; (EMEA) +31 20 308 0540; (APAC) +65 6622 2231.
• Migrate your workloads currently running in the impacted data centers/PODs.
• Free migration assistance is available through our partner Wan-clouds (https://www.wanclouds.net/ibm-request).
• Cancel your servers after migration. After you complete the migration to your new servers, make sure to cancel your existing servers / services. Existing services will continue to be invoiced until cancelled.

Key Milestones:
Between now and the final reclaim date, there are several key milestones to be aware of:
• April 03, 2023: Official Announcements for all impacted customers in DAL05, SJC01, WDC01 data centers
• April 03, 2023: No New Account provisioning in impacted data centers.
• August 14, 2023: Last date to provision services in impacted data centers.
• January 23, 2024: Network maintenance Dallas (DAL05): 10: AM US Eastern Time (14:00 GMT).
• January 24, 2024: Network maintenance San Jose (SJC01): 10: AM US Eastern Time (14:00 GMT).
• January 23, 2024: Network maintenance Washington DC (WDC01): 10: AM US Eastern Time (14:00 GMT).
• April 03, 2024: Last date to migrate before consolidation of DAL05, SJC01 and WDC01 data centers begins.
• April 04, 2024: DAL05, SJC01 and WDC01 data centers are closed; no longer available or supported.

Refs: https://cloud.ibm.com/docs/get-support?topic=get-support-dc-closure (public notification)
Refs: https://cloud.ibm.com/notifications?query=153216466&bss_account=699fe437d5f54fc6bff4a803ee1c059d (requires access to our IBM Cloud community account)

@targos
Copy link
Member

targos commented Apr 4, 2023

The build email alias has been sent this from IBM.

Are you sure about that? I can't find this in my emails.

@richardlau
Copy link
Member Author

The build email alias has been sent this from IBM.

Are you sure about that? I can't find this in my emails.

Ah sorry, you're right. IBM Cloud has individual accounts attached to the community account, so this went to my own email.

@richardlau
Copy link
Member Author

This is the same notification in IBM Cloud, if you have access to the account:
https://cloud.ibm.com/notifications?query=153216466&bss_account=699fe437d5f54fc6bff4a803ee1c059d

(If you're in build-infra and don't have access to the account, @mhdawson and I should be able to get you added.)

@targos
Copy link
Member

targos commented Apr 4, 2023

I don't have an IBM Cloud account yet. Last time I tried to create one it didn't work.

@richardlau
Copy link
Member Author

• DAL05
• SJC01
• WDC01

https://cloud.ibm.com/docs/overview?topic=overview-locations contains mappings of the codes to the names used in the IBM Cloud web ui, e.g.
• DAL05➡️Dallas 05
• SJC01➡️San Jose 01
• WDC01➡️Washington DC 01

@richardlau
Copy link
Member Author

https://cloud.ibm.com/docs/get-support?topic=get-support-dc-closure is a publicly accessible link announcing the closures, along with recommendations as to data centers to move to.

@richardlau
Copy link
Member Author

richardlau commented Apr 4, 2023

We have sixteen servers in our IBM Cloud account. Of those, the affected servers are in San Jose 1 where we have five servers (we have no servers in Dallas 1 nor Washington 1).

Device name Last known status Device type Location Public IP
nodejs-data2.softlayer.com Running Virtual Server San Jose 1 50.97.245.4
release-ibm-rhel8-x64-2.nodejs.cloud Running Virtual Server San Jose 1 50.97.245.10
test-ibm-ubuntu1804-x64-2.softlayer.com Running Virtual Server San Jose 1 50.97.245.9
test-softlayer-centos7-x64-1.softlayer.com Running Virtual Server San Jose 1 50.23.85.250
test-softlayer-ubuntu1404-x64-1.softlayer.com Running Virtual Server San Jose 1 50.97.245.5

of those

  • test-softlayer-ubuntu1404-x64-1.softlayer.com isn't needed anymore.
  • nodejs-data2.softlayer.com is the benchmarking data machine, which is now only used as an intermediate server for transferring data between the benchmark machine and the www server (for coverage.nodejs.org). This is another reason towards decommissioning coverage.nodejs.org and the related supporting infrastructure.
  • release-ibm-rhel8-x64-2.nodejs.cloud is actually one of three RHEL 8 x64 release machines we have (one other is in San Jose 4, which isn't being closed, and the other hosted in Digital Ocean). I'm least worried about this one.

@richardlau
Copy link
Member Author

richardlau commented Apr 5, 2023

@targos
Copy link
Member

targos commented Apr 19, 2023

I don't have an IBM Cloud account yet. Last time I tried to create one it didn't work.

Still not working...

CleanShot 2023-04-19 at 21 41 26@2x

Copy link

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.

@github-actions github-actions bot added the stale label Feb 14, 2024
@richardlau richardlau removed the stale label Feb 14, 2024
richardlau added a commit to richardlau/build that referenced this issue Mar 18, 2024
Remove test-softlayer-ubuntu1404-x64-1 which is in an IBM data center
(SJC1) that is closing.

Replace with test-ibm-ubuntu2204-x64-1.

Refs: nodejs#3279
@richardlau
Copy link
Member Author

richardlau commented Mar 18, 2024

Device name Last known status Device type Location Public IP Migration
nodejs-data2.softlayer.com Reclaiming Virtual Server San Jose 1 50.97.245.4 N/A (no longer required)
release-ibm-rhel8-x64-2.nodejs.cloud Reclaiming Virtual Server San Jose 1 50.97.245.10 Migrated: #3662
test-ibm-ubuntu1804-x64-2.softlayer.com Reclaiming Virtual Server San Jose 1 50.97.245.9 Replace with ubuntu2204 (cannot create new Ubuntu 18.04 servers): #3655
test-softlayer-centos7-x64-1.softlayer.com Reclaiming Virtual Server San Jose 1 50.23.85.250 Replace with rhel9: #3663
test-softlayer-ubuntu1404-x64-1.softlayer.com Reclaiming Virtual Server San Jose 1 50.97.245.5 Replace with ubuntu2204: #3654

richardlau added a commit that referenced this issue Mar 19, 2024
Remove test-softlayer-ubuntu1404-x64-1 which is in an IBM data center
(SJC1) that is closing.

Replace with test-ibm-ubuntu2204-x64-1.

Refs: #3279
richardlau added a commit to richardlau/build that referenced this issue Mar 19, 2024
Remove test-ibm-ubuntu1804-x64-2 which is in an IBM data center (SJC1)
that is closing.

Replace with test-ibm-ubuntu2204-x64-2.

Refs: nodejs#3279
richardlau added a commit that referenced this issue Mar 21, 2024
Remove test-ibm-ubuntu1804-x64-2 which is in an IBM data center (SJC1)
that is closing.

Replace with test-ibm-ubuntu2204-x64-2.

Refs: #3279
richardlau added a commit to richardlau/build that referenced this issue Mar 26, 2024
Replace the release-ibm-rhel8-x64-2 hosted in SJC1 to a new server
(hosted at DAL13).

Refs: nodejs#3279
richardlau added a commit that referenced this issue Mar 27, 2024
Replace the release-ibm-rhel8-x64-2 hosted in SJC1 to a new server
(hosted at DAL13).

Refs: #3279
@richardlau
Copy link
Member Author

I've cancelled all the servers at SJC01 -- the last two are in "Reclaiming" state and should be gone in a day or two.
image

Replacement server details in #3279 (comment).

richardlau added a commit that referenced this issue Mar 29, 2024
Replace test-centos7-x64-1 which was hosted on IBM Cloud at SJC1
(which is closing) with a new IBM Cloud hosted server running RHEL 9.

Refs: #3279
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants