Bug 1041258 - [RFE][nova]: Implement EC2 API for Tags
Summary: [RFE][nova]: Implement EC2 API for Tags
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/nova...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 14:06 UTC by RHOS Integration
Modified: 2015-03-19 16:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 16:59:02 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 14:06:15 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/ec2-tags-api.

Description:

The EC2 API allows end users to 'tag' resources with arbitrary key-value pairs.  This facility is also used by internal AWS tools such as autoscaling and cloudformation to group resources spawned by them.  The openstack EC2 API implementation does not offer the tags related API calls DescribeTags, CreateTags, DeleteTags or the ability to filter resource searches by tags ("filter": [{ "tag:key": "value"}]} and {"filter": [{"tag-key": "value"}]}.

The difficulty I see is that tags can be applied to many resource types, including ones handled by Quantum and Glance and so on.  It is not clear to me if reusing the instance-metadata table (and creating a 'security-group-metadata and so on tables) is the best way, or if this should be done with a new table 'tags' that stores all tags and a reference to the resource.

Specification URL (additional information):

http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-CreateTags.html


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