Bug 747645

Summary: add realm ui can be confusing
Product: [Retired] CloudForms Cloud Engine Reporter: Dave Johnson <dajohnso>
Component: DocumentationAssignee: Dan Macpherson <dmacpher>
Status: CLOSED CURRENTRELEASE QA Contact: wes hayutin <whayutin>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, dajohnso, deltacloud-maint, dgao, dmacpher, lbrindle, slinaber, ssachdev
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 773369 (view as bug list) Environment:
Last Closed: 2012-08-30 17:13:39 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:    
Bug Blocks: 773369    

Description Dave Johnson 2011-10-20 15:27:51 UTC 
Description of problem:
==============================
It seems like our use of terminology on this process is overlapping which makes it confusing.  

I go to a provider and create a new realm which gives me a option to map to a realm or map to a provider.  

In terms of rhevm, I create a new realm and map that to a rhevm cluster which the conductor ui calls a realm.  

Not sure if what is needed is specific terminology based on the provider the realm is for like changing 'add mapping to realm' to 'add mapping to rhevm cluster'.  

Its also not clear when you map to a realm(cluster) or map to a provider and if you need just one or the other or both.
Comment 1 Ken Keiter 2011-12-16 16:50:46 UTC 
Talking to sseago, it looks like the best way to fix this is to modify the doc to address this issue for now, and fix it in a future release.
Comment 2 Steve Linabery 2012-01-10 22:02:52 UTC 
Blindly setting this to ON_QA in the belief that a fix is included in the latest aeolus packages.
Comment 3 wes hayutin 2012-01-11 15:48:31 UTC 
want/need athomas to ack moving this to a doc issue
Comment 4 wes hayutin 2012-01-11 16:50:59 UTC 
Angus acked on the doc solution..

moving this bug to documents ce-sprint-next, and cloning a bug to cf-1.1.0
Comment 5 Dave Johnson 2012-01-11 18:35:09 UTC 
Please include the information/error documented in bug 767382 which is directly related to this.
Comment 6 wes hayutin 2012-01-12 16:32:44 UTC 
adding to ce-sprint
Comment 7 wes hayutin 2012-01-12 16:39:30 UTC 
removing ce-sprint-next tracker
Comment 10 Dave Johnson 2012-02-07 20:27:11 UTC 
good 2 go