Bug 782553

Summary: [RFE] Add support for EC2 Instance Resource Tagging
Product: Red Hat Enterprise MRG Reporter: Timothy St. Clair <tstclair>
Component: condorAssignee: Timothy St. Clair <tstclair>
Status: CLOSED ERRATA QA Contact: Luigi Toscano <ltoscano>
Severity: medium Docs Contact:
Priority: low    
Version: 2.1CC: ltoscano, matt, mkudlej, rrati, tstclair
Target Milestone: 2.3Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: condor-7.8.2-0.1 Doc Type: Enhancement
Doc Text:
C: Desire to add resource tagging for condor ec2 jobs. C: Users could not perform queries against various resources. C: Add support to allow tagging to ec2 jobs. R: During job submission users can now tag their resources and run queries against those tags.
Story Points: ---
Clone Of:
: 805358 (view as bug list) Environment:
Last Closed: 2013-03-06 18:40:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 805358    

Description Timothy St. Clair 2012-01-17 17:03:03 UTC
Description of problem:

http://aws.typepad.com/aws/2010/09/new-amazon-ec2-feature-resource-tagging.html

Comment 1 Luigi Toscano 2012-03-07 18:36:29 UTC
How can this feature be exploited/how will it be visible from the user point-of-view?

Comment 2 Timothy St. Clair 2012-03-07 21:22:47 UTC
Upstream ticket references the submit changes, the result is visible in the instance runs.  

---------------------------------------------

ec2_tag_<name> commands in condor_submit. Optional. Allows ec2_tag_foo=bar to assign tag foo the value bar.

ec2_tag_names command in condor_submit. Optional. Allows ec2_tag_names=fOo to specify case of tag name, above fOo=bar. Tag names are case sensitive, attribute names are not.

Default tag named "Name" to Cmd's value (the execute condor_submit command), for integration with AWS Console.

Note: Tags are garbage collected by AWS when they are no longer referenced. Thus no cleanup step in the gridmanager or gahp.

---------------------------------------------

Comment 4 Timothy St. Clair 2012-03-19 18:58:18 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
C: Desire to add resource tagging for condor ec2 jobs.
C: Users could not perform queries against various resources.
C: Add support to allow tagging to ec2 jobs.
R: During job submission users can now tag their resources and run queries against those tags.

Comment 7 Luigi Toscano 2012-12-20 19:48:31 UTC
Tags are correctly assigned; both type of parameters (ec2_tag_<name> and ec2_tag_names) are working as described in #2.

Verified on latest RHEL 5.x/6.x, i386/x86_64 (submitters).
condor-7.8.8-0.1

Comment 10 errata-xmlrpc 2013-03-06 18:40:55 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0564.html