Bug 1710981 - m4 instances are old (2015), OpenShift should default to m5 instances for IPI and UPI installs on AWS
Summary: m4 instances are old (2015), OpenShift should default to m5 instances for IPI...
Keywords:
Status: NEW
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.3.0
Assignee: Abhinav Dahiya
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-16 17:15 UTC by Mike Fiedler
Modified: 2019-09-05 20:18 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-16 21:18:10 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3314661 None None None 2019-09-05 20:18:42 UTC

Comment 6 W. Trevor King 2019-05-23 19:40:19 UTC
Seems like AWS isn't yet ready for us to default to m5 in us-east-1 or ap-southeast-2:

  $ AWS_PROFILE=ci aws --region us-east-1 ec2 describe-reserved-instances-offerings --instance-tenancy default --instance-type m5.large --product-description 'Linux/UNIX' --filters Name=scope,Values='Availability Zone' | jq -r '[.ReservedInstancesOfferings[].AvailabilityZone] | sort | unique[]'
  us-east-1a
  us-east-1b
  us-east-1c
  us-east-1d
  us-east-1f

^ missing us-east-1e.

  $ AWS_PROFILE=ci aws --region ap-southeast-2 ec2 describe-reserved-instances-offerings --instance-tenancy default --instance-type m5.large --product-description 'Linux/UNIX' --filters Name=scope,Values='Availability Zone' | jq -r '[.ReservedInstancesOfferings[].AvailabilityZone] | sort | unique[]'
  ap-southeast-2b
  ap-southeast-2c

^ missing ap-southeast-2a.  As far as the CI account has access (e.g. not to us-gov-east-1, etc.), the other regions have m5 in all their zones.  More on per-zone availability in bug 1713157.

Comment 7 Eric Paris 2019-07-08 19:36:38 UTC
There were 2 issues with m5 that made us (consciously) choose to stick with m4.
1. They have a lower EBS attach limit per node (m5 is 28, m4 is ~40)
2. Kube originally at least had trouble always getting the name of the device inside the instance correct.


While (1) seems like it can easily overcome by getting more nodes it actually costs more. Since you have to pay for CPU/memory for the infrastructure pieces (kernel, kubelet, crio, sdn, etc) per node.

If (2) was solved we probably can switch the default after the issues in comment #6 are resolved...


Note You need to log in before you can comment on or make changes to this bug.