[FOLIO-2679] AWS instance type provisioning failures Created: 07/Jul/20  Updated: 21/Jul/20  Resolved: 21/Jul/20

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

Type: Bug Priority: P3
Reporter: John Malconian Assignee: John Malconian
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: DevOps: sprint 92
Development Team: FOLIO DevOps

 Description   

AWS has a t2.2xlarge capacity issue in us-east-1 that is impacting the project's ability to provision new ec2 instances of this type. t2.2xlarge is what we typically use to build a standalone, full FOLIO stack - folio-snapshot, folio-testing, etc. Switching over to m5.2xlarge seems to work. Perhaps t3.2xlarge instances will work as well. Assess cost impact of switching from t2.2xlarge to one of these instance types and update build pipelines if applicable.

CC: Peter Murray



 Comments   
Comment by Peter Murray [ 07/Jul/20 ]

Hey John: I've been buying short-term (less than 12 month) RIs for the hosted reference environments. I can look for m5 RIs to cover these. I presume the plan is to move these standalone, full-FOLIO-stacks for hosted reference environments into a Kubernetes cluster at some point, which is why I've been buying the short-term RIs.

Comment by John Malconian [ 07/Jul/20 ]

I've reconfigured the daily folio-snapshot and folio-testing-backend builds to use the m5.2xlarge instance type as well as the PR build pipeline for platform-complete.

Comment by John Malconian [ 21/Jul/20 ]

All reference builds that use t2.2xlarge have been changed to m5.2xlarge in the us-east-1 region going forward.

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