-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
pkg/rhcos/ami: Update name filter to "redhat-coreos-*" #572
pkg/rhcos/ami: Update name filter to "redhat-coreos-*" #572
Conversation
The OS folks have a new pipeline for publishing these AMIs, and they're setting these new names. Current output: $ curl -sL https://rhcos-release-browser-coreos.int.open.paas.redhat.com/storage/releases/maipo/47.33/meta.json | jq .amis [ { "name": "us-east-1", "hvm": "ami-0fd0205c3c81d0412" } ] $ AWS_DEFAULT_REGION=us-east-1 aws ec2 describe-images --image-ids ami-0fd0205c3c81d0412 --output json { "Images": [ { "VirtualizationType": "hvm", "Description": "Red Hat CoreOS \"maipo\" (OpenShift) 47.33", "Tags": [ { "Value": "redhat-coreos-maipo-47.33-hvm", "Key": "Name" } ], "Hypervisor": "xen", "EnaSupport": true, "SriovNetSupport": "simple", "ImageId": "ami-0fd0205c3c81d0412", "State": "available", "BlockDeviceMappings": [ { "DeviceName": "/dev/xvda", "Ebs": { "Encrypted": false, "DeleteOnTermination": true, "VolumeType": "gp2", "VolumeSize": 8, "SnapshotId": "snap-08318a8024617da0b" } }, { "DeviceName": "/dev/xvdb", "VirtualName": "ephemeral0" } ], "Architecture": "x86_64", "ImageLocation": "531415883065/redhat-coreos-maipo-47.33-hvm", "RootDeviceType": "ebs", "OwnerId": "531415883065", "RootDeviceName": "/dev/xvda", "CreationDate": "2018-10-30T15:27:07.000Z", "Public": false, "ImageType": "machine", "Name": "redhat-coreos-maipo-47.33-hvm" } ] } For the previous pipeline, see the output in d01ac5d (pkg/rhcos: Default to the most-recent AMI, 2018-09-19, openshift#290).
089283f
to
8c0d7b6
Compare
Why don't we get the AMI information from the release metadata in #554 ? |
It seems like |
Right, though we are discussing changing that. |
(Also I meant #554 - edited my first comment too) |
Because this is a one-line change that gets us working while we work out how to use the JSON metadata ;). This AWS-scraping approach will also continue to work in regions beyond us-east-1, while the |
which is currently blocked on getting access to the new AMIs from the CI account. |
That's because it's only that region right now. |
Can we fix that (again)? @coverprice has been pushing openshift-dev users into us-east-2 and us-west-1 regions where we have higher resource quotas. |
CI access to the new pipeline's AMIs is in flight with this just built. |
$ AWS_PROFILE=ci AWS_DEFAULT_REGION=us-east-1 aws ec2 describe-images --filter 'Name=name,Values=redhat-coreos-*' --query 'sort_by(Images, &CreationDate)[-1]' --output json
{
"VirtualizationType": "hvm",
"Description": "Red Hat CoreOS \"maipo\" (OpenShift) 47.14",
"Hypervisor": "xen",
"EnaSupport": true,
"SriovNetSupport": "simple",
"ImageId": "ami-0c353b2d94b0a6247",
"State": "available",
"BlockDeviceMappings": [
{
"DeviceName": "/dev/xvda",
"Ebs": {
"Encrypted": false,
"DeleteOnTermination": true,
"VolumeType": "gp2",
"VolumeSize": 8,
"SnapshotId": "snap-058e45208e113a230"
}
},
{
"DeviceName": "/dev/xvdb",
"VirtualName": "ephemeral0"
}
],
"Architecture": "x86_64",
"ImageLocation": "531415883065/redhat-coreos-maipo-47.14-hvm",
"RootDeviceType": "ebs",
"OwnerId": "531415883065",
"RootDeviceName": "/dev/xvda",
"CreationDate": "2018-10-26T20:15:56.000Z",
"Public": false,
"ImageType": "machine",
"Name": "redhat-coreos-maipo-47.14-hvm"
} /retest |
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, wking The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The OS folks have a new pipeline for publishing these AMIs, and they're setting these new names. Current output:
For the previous pipeline, see the output in d01ac5d (#290).
CC @abhinavdahiya, @crawford, @cgwalters.