Bug 754561

Summary: Chapter 17. Scheduling to Amazon EC2 Comments
Product: Red Hat Enterprise MRG Reporter: Robert Rati <rrati>
Component: Grid_User_GuideAssignee: Alison Young <alyoung>
Status: CLOSED CURRENTRELEASE QA Contact: Jeff Needle <jneedle>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.0CC: eerlands, jneedle, lbrindle, matt
Target Milestone: 2.1   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-26 19:21:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Deadline: 2011-11-18   

Description Robert Rati 2011-11-16 20:40:15 UTC 
Description of problem:
From Erik:
*) Might want to actually work this text into the intro section for CH 17: "In EC2 basic, you generate an AMI in EC2 that does a specific task.  It is the responsibility of whatever is in that AMI to shutdown the AMI instance when said task is complete.  That is how condor knows the grid universe job "completed", by the ami shutting down.  condor actually has no knowledge of what is going on inside the ami."

*) In the EC2-e doc, maybe a bit more explanation should be added to distinguish the three kinds of keys floating around:  AWS access/secret keys, AWS instance keypair, and the grid-specific rsa private/public key that lives in ".ec2" on the AMI, etc.  (particularly difference between AWS instance keypair and ".ec2" keypair you generate for ec2e).


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: