[FOLIO-3572] Replace bare metal server at Equinix used by CI to build Vagrant boxes Created: 04/Sep/22  Updated: 29/Nov/22  Resolved: 29/Nov/22

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: Peter Murray Assignee: John Malconian
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: DevOps Sprint 154
Development Team: FOLIO DevOps
RCA Group: TBD

 Description   

The email below came to the project's AWS infrastructure email address. As I understand it use, the continuous integration infrastructure this server builds the Vagrant snapshot boxes that are used by developers. The "FOLIO-ansible" page has a few more details. This is something John Malconian used to manage, and if the process isn't migrated to new infrastructure, then the developers using this capability will fall behind.

I can provide an account on Equinix to facilitate the move. The FOLIO Project currently budgets about $390 per month for this facility, so if any changes are going to cost more than that, we will need to notify the appropriate people.

From: support@equinixmetal.com
Date: Aug 31, 2022, 10:28 AM -0400
To: folio-aws@openlibraryfoundation.org
Subject: Equinix Metal Legacy Facility Closure Notice

We hope this finds you well. As part of our ongoing efforts to improve the quality of our offerings and provide the best user experience, we plan to close our remaining legacy facilities this year in favor of our go-forward Equinix-based environments. These closures will take place a 90 days from now, on November 30th, 2022:

  • Americas: DFW2, EWR1, SJC1;
  • EMEA: AMS1;
  • Asia-Pacific: NRT1.
    Hint: if you have Equinix Metal infrastructure in a facility with a three-letter airport code (such as EWR1), it is in a legacy facility and will be closing. If it is a two-letter code (such as NY5), it is a go-forward Equinix facility and will remain. You can read more about our metro approach , which aggregates facilities within a metropolitan area and will mitigate the need for migrations in the future.
    1. What We’re Doing To Help

While closing physical facilities is never easy, we are committed to helping make this process as seamless as possible. Here are some key points we want you to know about:

1. Each legacy facility is part of a Metro footprint that includes new Equinix IBXs.
2. In all cases, you’ll be able to deploy infrastructure in the same Metro if desired.
3. We have substantial current generation hardware available to support migrations.
4. Our Customer Success team is here to help you plan and execute your migration.

    1. Reserved & Gen1 Hardware

If you have gear under contract in a legacy facility, we’ll work with you to migrate your current contract or provide you with a new agreement. Unfortunately, Gen1 hardware is not available in our go-forward Equinix IBXs, but we can arrange for both select Gen2 and Gen3 infrastructure to meet your needs.

    1. What’s Next?

Please, take a moment to review your hardware. If you need assistance, contact us as soon as possible to begin planning for this move. The November 30th date is considered a hard deadline, and we want to work with you well in advance to ensure a successful transition. Any exceptions need prior coordination and arrangement to avoid service interruption.

We appreciate your partnership and value your business. Thank you for working with us to complete this important project in a mutually-agreeable manner!

Sincerely,
Jeremy Brooks
Senior Director, Customer Success



 Comments   
Comment by Peter Murray [ 04/Sep/22 ]

Hi Taras Spashchenko: This is a new issue for the Kitfox team backlog.

Comment by John Malconian [ 29/Nov/22 ]

The old c1.small.x86 on-demand instance running in Amsterdam has been decommissioned and replaced with a c3.small.x86 instance running in Dallas. The system is running Ubuntu Jammy. Account credentials are the same as the previous instance. Instance has been added to Jenkins and the Automation/folio-blackbox job has been tested and successfully runs.

Generated at Thu Feb 08 23:29:07 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.