Bug 883064

Created attachment 656847 [details]
Screenshot.png

Description of problem:

Currently, when launching an application to a Cloud Resource Zone, conductor will display all Cloud Resource Clusters for the user to select.  This can be confusing to a user.  For example, I may be attempting to launch an application into a RHEV resource zone (private cloud environment), but conductor displays resource clusters intended for other resource zones (e.g. vSphere, ec2 etc...).


Version-Release number of selected component (if applicable):
 * aeolus-conductor-0.13.24-1.el6cf.noarch

How reproducible:


Steps to Reproduce:
1. Create multiple Cloud Environments: Public, Private
2. Create multiple Cloud Resource Zones (one for each provider): RHEV, vSphere, ec2-us-east-1, ec2-us-east-2 etc...
3. Create multiple resource clusters (one for each provider type): RHEV, vSphere, ec2
4. From the monitor tab, attempt to launch a new application into the RHEV resource zone
  
Actual results:

Observe that the dropdown-list ' Cloud Resource Cluster ' displays *all* resource clusters, not just those associated with the Private Cloud Environment, or the RHEV Resource Zone.

Expected results:

When launching an application, Conductor should only offer Cloud Resource Clusters that apply for the target Cloud Resource Zone.  In other words, ec2 clusters (intended for a different zone or cloud environement), should not display when launching into a private cloud env (or RHEV resource zone).

Additional info:

> 12:10:27  jlaska: ping athomas 
> 12:10:42  jlaska: Hey Angus, morazi suggested you might be a good person to help clarify cloud resource clusters
> 12:10:43  athomas: pong
> 12:10:48  athomas: eesh
> 12:11:03  athomas: I'll get him back for that. ;-)
> 12:11:12  athomas: I can try..
> 12:11:16  athomas: What's up?
> 12:11:24  jlaska: haha
> 12:11:32  jlaska: I'm perplexed at how they are used
> 12:11:43  jlaska: and this may be a result of how we've setup our CloudForms instance ...
> 12:11:44  jlaska: http://file.rdu.redhat.com/jlaska/screenshots/Screenshot.png
> 12:11:56  jlaska: err, one sec ... lemme update screenshot
> 12:12:24  athomas: They are an additional layer in the provider selection process..
> 12:12:52  jlaska: what's confusing is that I'm attempting to launch an application into my RHEV cloud resource zone ...
> 12:12:58  athomas: So, we exclude providers which don't have the right images, or which are over quota etc..
> 12:13:04  jlaska: and it's allowing me to select all clusters, regardless of provider/zone
> 12:13:18  athomas: Ah
> 12:13:21  athomas: Yes
> 12:13:35  jlaska: I would have expected it to limit the clusters available to the cloud I'm launching in (or to the zone)
> 12:13:44  jlaska: but I'm wrong, and not sure why 
> 12:13:55  athomas: Currently, there is a single, global list of clusters
> 12:13:59  athomas: So, you see them all
> 12:14:02  jlaska: yeah
> 12:14:28  athomas: Even though several may make little sense, in the context of the current cloud environment.
> 12:14:40  athomas: That's a UI bug/glaring missing feature
> 12:15:10  athomas: I was talking to sseago about this a recently
> 12:15:14  jlaska: yeah it's weird that it let's me launch to a my zone (RHEV), but select ec2 or vsphere clusters
> 12:15:24  jlaska: good, I'm not entirely crazy then!
> 12:15:30  athomas: I'm currently scoping tasks for the next dev sprint
> 12:15:36  jlaska: s/let's/lets/
> 12:15:43  athomas: I'll add this, since it is obviously wrong.
> 12:15:59  jlaska: what's correct behavior?  Should the clusters be associated with a cloud or a resource zone?
> 12:16:59  athomas: I think that the UI should only invite you to filter on the clusters which contain some part of the provider accounts which are scoped into the current cloud 
>                    environment
> 12:17:19  jlaska: gotcha, that makes sense
> 12:17:44  jlaska: and clusters aren't currently associated with a cloud environment, so I guess that adjustment would be needed
> 12:17:50  jlaska: (as you said, just a flat list of clusters currently)
> 12:18:16  athomas: So, if the only available provider accounts, in the current cloud environment, are RHEV, you should on;y see the option to select the resource clusters which 
>                    contiain some part of at least one of those RHEN providers
> 12:18:31  jlaska: that's good ... thanks for explaining!