Bug 715101

Summary: [UI]: Remove the EC2 private key and cert questions in Add Provider Account
Product: [Retired] CloudForms Cloud Engine Reporter: Chris Lalancette <clalance>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED CURRENTRELEASE QA Contact: wes hayutin <whayutin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.3.1CC: dajohnso, deltacloud-maint, jguiditt, jprovazn, ssachdev
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-22 14:02:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Chris Lalancette 2011-06-21 21:07:43 UTC
Description of problem:
Since we are no longer building images through the conductor web UI, I believe it is the case that we no longer need to ask the user for their private key and certificate when adding a new provider account for EC2.  Someone should go and verify that I am correct, and if so, remove those fields from the UI.

Comment 1 Jan Provaznik 2011-06-22 13:35:40 UTC
I think aeolus-image CLI fetches these credentials from conductor so it makes sense to keep it. But maybe I'm wrong, CCing Jay who knows if aeolus-image needs it in conductor or not.

Comment 2 Jason Guiditta 2011-06-22 13:48:11 UTC
Yes, the conductor is still the authority for account credentials.  The cli tool retrieves this in xml format via an api call, and passes it along to factory.  If we removed this, there would be nowhere to store the credentials.

Comment 3 Chris Lalancette 2011-06-22 14:02:26 UTC
Ah, OK.  No problem then.  I'll close it out.

Chris Lalancette

Comment 4 wes hayutin 2011-07-11 00:32:34 UTC
removing from tracker

Comment 5 wes hayutin 2011-12-08 13:47:06 UTC
perm close