Please tag AMIs #111

Closed
blalor opened this Issue Aug 21, 2014 · 4 comments

Comments

Projects
None yet
5 participants
@blalor

blalor commented Aug 21, 2014

Please tag Amazon AMIs with channel, version, timestamp, etc. For example, the current stable release looks like:

    {
      "VirtualizationType": "hvm",
      "Name": "CoreOS-stable-367.1.1-hvm",
      "Hypervisor": "xen",
      "ImageId": "ami-02a2766a",
      "State": "available",
      "BlockDeviceMappings": [
        {
          "DeviceName": "/dev/xvda",
          "Ebs": {
            "DeleteOnTermination": true,
            "SnapshotId": "snap-afd82903",
            "VolumeSize": 8,
            "VolumeType": "standard",
            "Encrypted": false
          }
        },
        {
          "DeviceName": "/dev/xvdb",
          "VirtualName": "ephemeral0"
        }
      ],
      "Architecture": "x86_64",
      "ImageLocation": "595879546273/CoreOS-stable-367.1.1-hvm",
      "RootDeviceType": "ebs",
      "OwnerId": "595879546273",
      "RootDeviceName": "/dev/xvda",
      "Public": true,
      "ImageType": "machine",
      "Description": "CoreOS stable 367.1.1 (HVM)"
    }

It would be helpful to have the following tags:

  • channel: stable
  • version: 367.1.1
  • timestamp: Unix epoch or ISO8601 timestamp of release

This will make it easier to choose the most recent image for a given channel programmatically.

@jimmycuadra

This comment has been minimized.

Show comment
Hide comment
@jimmycuadra

jimmycuadra Dec 1, 2016

Is the code that publishes these AMIs open source? It doesn't seem the CoreOS team has time to do this themselves, but maybe someone in the community could help out.

Is the code that publishes these AMIs open source? It doesn't seem the CoreOS team has time to do this themselves, but maybe someone in the community could help out.

@crawford

This comment has been minimized.

Show comment
Hide comment

@crawford crawford added this to the CoreOS Alpha 1300.0.0 milestone Jan 6, 2017

@crawford crawford modified the milestone: CoreOS Alpha 1300.0.0 Jan 25, 2017

@bgilbert bgilbert self-assigned this Mar 31, 2017

@bgilbert

This comment has been minimized.

Show comment
Hide comment
@bgilbert

bgilbert Apr 11, 2017

Member

coreos/mantle#540 reimplements the AMI publishing process inside plume. The new implementation sets Channel and Version tags, but doesn't record the release timestamp because that isn't known when the AMIs are created. The channel and version number should be sufficient to select the most recent image, but if you need the release timestamp, you can look it up in the releases feed.

The new tags should start appearing in the next alpha release. Thanks for the report!

Member

bgilbert commented Apr 11, 2017

coreos/mantle#540 reimplements the AMI publishing process inside plume. The new implementation sets Channel and Version tags, but doesn't record the release timestamp because that isn't known when the AMIs are created. The channel and version number should be sufficient to select the most recent image, but if you need the release timestamp, you can look it up in the releases feed.

The new tags should start appearing in the next alpha release. Thanks for the report!

@bgilbert bgilbert closed this Apr 11, 2017

@euank

This comment has been minimized.

Show comment
Hide comment
@euank

euank Jun 28, 2017

Member

For anyone following this bug: it turns out tagging AMIs doesn't work like we want it to.

From their docs

You can tag public or shared resources, but the tags you assign are available only to your AWS account and not to the other accounts sharing the resource.

As far as I can tell, there's no way to publish/share tags.

Member

euank commented Jun 28, 2017

For anyone following this bug: it turns out tagging AMIs doesn't work like we want it to.

From their docs

You can tag public or shared resources, but the tags you assign are available only to your AWS account and not to the other accounts sharing the resource.

As far as I can tell, there's no way to publish/share tags.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment