Bug 806990
Summary: | RFE: need scoping information on top level monitor page | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] CloudForms Cloud Engine | Reporter: | Steve Reichard <sreichar> | ||||
Component: | aeolus-conductor | Assignee: | Angus Thomas <athomas> | ||||
Status: | CLOSED EOL | QA Contact: | Rehana <aeolus-qa-list> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 1.0.0 | CC: | akarol, dajohnso, deltacloud-maint, hbrock, morazi, scollier, ssachdev, sseago | ||||
Target Milestone: | rc | Keywords: | FutureFeature, Triaged | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Enhancement | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2020-03-27 20:11:02 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
I agree. We need this. Even better, we should organize the page by cloud, much like we do on the 'clouds' page. See my comments on Bug 806985 for more details, but essentially, when we redesign the nav/flow, I'd like to see the 'monitor' view and the 'clouds' view merged into one. We should always present zones as "sub-nav" below clouds, and we really shouldn't present the the "parent" and "child" objects on completely separate sides of the nave. the top level under "monitor" (but please change the name!) should be the list of clouds and zones (filtered for user permissions like now). This will also resolve the sort of nav-flow problems as reported in 806985. This is an RFE, moving to 1.1 |
Created attachment 572818 [details] screen shot Description of problem: After adding several zones, if I switch to the Monitor tab, I can not tell which Zone belongs to which cloud. While having the same name Zone in the same cloud, different capitalization is allowed. Look at the screen shot. Can you tell which cloud "Default" is associated with, compared to "default"? Or "bug" and "bugs"? While I like the grouping in the Admin | Clouds page, just prepending the cloud to toe Zone would be quite helpful. As you can see, I've made it a practice to do this myself "ra-dev-usecase" (I've prepended "ra-" to map to my SE zone, again, probably a best practice for now) Version-Release number of selected component (if applicable): early beta6 Red Hat Enterprise Linux Server release 6.2 (Santiago) Linux cf-cloudforms9.cloud.lab.eng.bos.redhat.com 2.6.32-220.7.1.el6.x86_64 #1 SMP Fri Feb 10 15:22:22 EST 2012 x86_64 x86_64 x86_64 GNU/Linux postgresql-8.4.9-1.el6_1.1.x86_64 mongodb-1.8.2-3.el6.x86_64 euca2ools-1.3.1-4.el6_0.noarch ruby-1.8.7.352-6.el6.x86_64 rubygems-1.8.16-1.el6.noarch deltacloud-core-0.5.0-7.el6.noarch rubygem-deltacloud-client-0.5.0-2.el6.noarch package libdeltacloud is not installed hail-0.8-0.3.gf9c5b967.el6.x86_64 puppet-2.6.14-1.el6.noarch aeolus-configure-2.5.2-1.el6.noarch iwhd-1.5-2.el6.x86_64 imagefactory-1.0.0rc10-1.el6.noarch aeolus-conductor-daemons-0.8.3-1.el6.noarch aeolus-conductor-0.8.3-1.el6.noarch How reproducible: easily Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: