| Summary: | Provide Unique Names for Cloud Resource Cluster | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | james labocki <jlabocki> | ||||||||
| Component: | aeolus-conductor | Assignee: | Tomas Hrcka <thrcka> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | pushpesh sharma <psharma> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 1.0.0 | CC: | akarol, bbandari, cpelland, dajohnso, deltacloud-maint, hbrock, matt.wagner, slinaber, ssachdev, sseago, thrcka, whayutin | ||||||||
| Target Milestone: | rc | Keywords: | Triaged | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-05-15 22:38:57 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Bug Depends On: | 803586 | ||||||||||
| Bug Blocks: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
james labocki
2012-02-21 18:56:37 UTC
Agreed.. Under Cloud Resource Providers... rename Cloud Resource Clusters -> Available Cloud Resource Clusters What is shown here is all of the available backend clusters/realms/avail zones From what I understand, in Administer -> Catalog Change "Cloud Resource Clusters" to "Cloud Resource Profiles" When "Cloud Resource Profiles" is selected show "Cloud Resource Profiles" Button in "Cloud Resource Profiles" should be labelled "New Cloud Resource Profile" When "New Cloud Resource Profile" button is selected the following screen should allow a profile to be created and then mapped to a provider or cluster. Also, the "Cloud Resource Cluster Mapping" label when viewing the "Cloud Resource Profile" should read "Cloud Resource Profile Mapping". Sorry if this is confusing. Also, when launching and instance change "Cloud Resource Cluster" to "Cloud Resource Profile" - it can be found at /conductor/deployments/launch_new?pool_id=X Angus will come up with a string that will hopefully fix this... Fundamentally, the user experience is confusing because the same term, "Cloud Resource Cluster", is used to refer to both front end and back end realms, which are related, but different objects. Solution to this is to continue using "Cloud Resource Clusters" to refer to front end, user-defined realms, and to refer to back end realms as "Provider Realms" at all points in the UI. Because this was identified as a blocker, I stole this task and sent a patch to the list: http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-March/009536.html Tomas, feel free to steal this back from me if you find fault in my patch. fixed in master git commit ec767b62823a57b9acdb3fdddd15a5f09c1ca416 This is not fixed in beta4 and I suspect is causing bug 803586 in beta 5, can't move to verified just yet, need to wait for it to be fixed. Adding depends on assigning to Pushpesh As Angus Thomas suggested that Provider realms should be renamed to "Provider Cloud Resource Cluster" and Front and user realms as "cloud Resource Cluster". But I found some things still confusing:- 1. In "Provider Cloud Resource Cluster" section the there is a reference to "Provider Realm Name" in the table that lists "Provider Cloud Resource Cluster". 2.If i choose any "Provider Relam" then there is more reference to "Realm" instead of "Cluster". Since this can be only treated as partial fix.So changing the state to assigned. Actually, "Provider Realm" is the proper name for the providewr realms. "Cloud resource cluster" is only for front end realms. See Comment #5 from Angus -- but what is reported in 1) and 2) above is correct If as per the comment 5 "Provider Realm" will be used throughout the UI then "Provider Cloud Resource Cluster" tab in Cloud Resource Provider section should be renamed to "Provider Realms". My Point is if "Realms" is used in the back-end(Provider) then there should not be any instance where if is refereed as "Cluster" even for sake of clarity it is prefixed with "Provider". ex:- "Provider Cloud Resource Cluster" should be renamed to "Provider Realms" Marking this bug to assigned again. patch is on the list It appears that this is pushed. master: ec767b62823a57b9acdb3fdddd15a5f09c1ca416 1.0-product: 73ec93c7971c3889ce9e9a754a2a08b18e86e04a Moving to MODIFIED. This may be further along the process but I don't know that for a fact. I didn't find any fix in beta6 release,or any comments that justify my last comment#13 will not be considered as valid fix.I am again rephrasing my idea for the fix: If as per the comment 5 "Provider Realm" will be used throughout the UI then "Provider Cloud Resource Cluster" tab in Cloud Resource Provider section should be renamed to "Provider Realms". PFA for the snapshot of the problem. Created attachment 576679 [details]
problem snapshot
Yes this was moved to MODIFIED and ON_QA by mistake yesterday. I just acked the patch yesterday, so it should be moved to MODIFIED when the patch gets pushed. Moving to POST. git commit 4244f63d12ec69508b4b810559b29ccfb3bdafad Putting this back to ON_QA since 4244f6 has been in the build since v0.8.8-1 and I don't think ET will flip this back on its own. Created attachment 578032 [details]
front end
Created attachment 578033 [details]
back end
front end and back end realms look sane
1. front end = Cloud Resource Cluster
2. back end = Provider Realm
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2012-0583.html |