Bug 798020

Summary: Prompted Twice to select a cloud resource cluster during launch of an application
Product: [Retired] CloudForms Cloud Engine Reporter: james labocki <jlabocki>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED EOL QA Contact: Rehana <aeolus-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, deltacloud-maint, hbrock, ssachdev
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
screen20a
none
screen20b none

Description james labocki 2012-02-27 20:47:30 UTC 
Description of problem:

When "new application" is selected in conductor the following workflow takes place. 

1) attachment screen20a - "Application Details" page where the following is specified:
  - Application Name (uniquely identifies your application) 
  - Deployable (I didn't know we were still referring to it as deployable)
  - Cloud Resource Cluster

2) Optional - Configure launch-time parameters for your application:

3) attachment screen20b - "Deploy 'test' to ResourceZoneFinance Cloud Resource Zone page where the following is configurable:
  - Name
  - Cloud Resource Cluster

Having a drop down of cloud resource cluster twice in the same workflow is redundant and confusing. It's also confusing to have Name appear twice. Can we use different term for them if they are in fact different or can we simply remove them if they are redundant?
Comment 1 james labocki 2012-02-27 20:47:57 UTC 
Created attachment 566138 [details]
screen20a
Comment 2 james labocki 2012-02-27 20:48:23 UTC 
Created attachment 566139 [details]
screen20b
Comment 3 Hugh Brock 2012-05-07 15:51:18 UTC 
We'll have to address in the context of UI unification with Katello.