Bug 782552 – Use idempotent EC2 RunInstances

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 782552 - Use idempotent EC2 RunInstances

Summary:	Use idempotent EC2 RunInstances

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise MRG
Classification:	Red Hat
Component:	condor (Show other bugs)
Sub Component:
Version:	2.1
Hardware:	All All

Priority	low Severity medium
Target Milestone:	2.3
Target Release:	---
Assigned To:	Timothy St. Clair
QA Contact:	Luigi Toscano
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	750078 876873
	Show dependency tree / graph

Reported:	2012-01-17 11:59 EST by Timothy St. Clair
Modified:	2013-03-06 13:40 EST (History)
CC List:	5 users (show)

See Also:
Fixed In Version:	condor-7.8.2-0.1
Doc Type:	Enhancement
Doc Text:	C: Desire to add support for idempotent EC2 RunInstances. C: Performing an idempotent operation more than once yields the same result as applying it just once. C: Added support inside of the ec2 protocol to add idempotent support when calling RunInstances. R: The ec2_gahp now supports idempotent RunInstances.
Story Points:	---
Clone Of:
Clones:	876873 (view as bug list)
Environment:
Last Closed:	2013-03-06 13:40:51 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Condor	2600	None	None	None	Never
Red Hat Product Errata	RHSA-2013:0564	normal	SHIPPED_LIVE	Low: Red Hat Enterprise MRG Grid 2.3 security update	2013-03-06 18:37:09 EST

Groups: None (edit)

Description Timothy St. Clair 2012-01-17 11:59:33 EST

Add support for http://aws.typepad.com/aws/2010/09/new-amazon-ec2-feature-idempotent-instance-creation.html

Comment 1 Luigi Toscano 2012-03-07 13:34:45 EST

Just to recap: from a user point of view, does this bug bring only a change in a way keypairs are handled? (no more or not only self-generated keypairs, but specify an existing one from the keypairs stored amazon servers)
According to the original report, I see that the old behavior will stay too; will we support both?

Comment 2 Timothy St. Clair 2012-03-07 16:18:02 EST

We support both methods, but idepotent instances is tangential to comment #1.

Comment 4 Timothy St. Clair 2012-03-19 14:46:32 EDT

    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 support for idempotent EC2 RunInstances.
C: Performing an idempotent operation more than once yields the same result as applying it just once.
C: Added support inside of the ec2 protocol to add idempotent support when calling RunInstances.
R: The ec2_gahp now supports idempotent RunInstances.

Comment 5 Luigi Toscano 2012-04-03 07:54:27 EDT

After going through the bug again, I think I'm missing something: according to the condor ticket, the keypair is used as client token so that the requests to the same running AMI can be idempotent. What happen when the same key is used for different jobs/AMI instances?

Comment 6 Timothy St. Clair 2012-04-03 09:15:57 EDT

This has nothing to do with keys.  The client token is a unique identifier which is generated in the gridmanager.  

--------------------------------------------------------------
ClientToken
Unique, case-sensitive identifier you provide to ensure idempotency of the request. For more information, go to How to Ensure Idempotency in the Amazon Elastic Compute Cloud User Guide.

Type: String

Default: None

Constraints: Maximum 64 ASCII characters

see also: 
http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/Run_Instance_Idempotency.html
--------------------------------------------------------------

Comment 7 Luigi Toscano 2012-04-03 13:03:12 EDT

Information about the new possible way of handling keypairs, which are reported in the upstream condor ticket referenced by this bug, has been moved to a separated bug:
https://bugzilla.redhat.com/show_bug.cgi?id=809551

Comment 11 Luigi Toscano 2013-02-10 19:39:23 EST

Running/control/shutdown of EC2 instances is executed as before.

Verified on RHEL5.9/6.4 beta, either condor-7.8.8-0.1 or condor-7.8.8-0.4.1.

Comment 13 errata-xmlrpc 2013-03-06 13:40:51 EST

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

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