Bug 744065 - [RFE]Can't add provider to existing realm in the Administer - Cloud Provider - Realms path
Summary: [RFE]Can't add provider to existing realm in the Administer - Cloud Provider ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
Assignee: Angus Thomas
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-06 21:15 UTC by Steve Reichard
Modified: 2020-03-27 19:34 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:34:30 UTC


Attachments (Terms of Use)

Description Steve Reichard 2011-10-06 21:15:31 UTC
Description of problem:

Added a new provider account then want to add this provider to my existing global realm.   Click on the Realm 'tab'.  There was no listing on existing realms.  Attempted to say it was a new realm - but it said it already existed.

I could add by going to Content - Realms - choose existing realm and added provider mapping.  Seems like I should be able to do this while working in the provider.

Version-Release number of selected component (if applicable):


[root@cf-cloudforms2 nodes]# /pub/scripts/post_install_configuration_scripts/cf-versions
Red Hat Enterprise Linux Server release 6.1 (Santiago)
Linux cf-cloudforms2.cloud.lab.eng.bos.redhat.com 2.6.32-131.12.1.el6.x86_64 #1 SMP Sun Jul 31 16:44:56 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
postgresql-8.4.7-2.el6.x86_64
mongodb-1.8.0-6.el6.x86_64
euca2ools-1.3.1-4.el6_0.noarch
package gsoap is not installed
ruby-1.8.7.299-7.el6_1.1.x86_64
rubygems-1.8.10-1.el6.noarch
deltacloud-core-0.5.0-0.2.1317167702git.el6.noarch
rubygem-deltacloud-client-0.4.0-3.el6.noarch
package libdeltacloud is not installed
hail-0.8-0.2.gf9c5b967.el6_0.x86_64
puppet-2.6.6-1.el6_0.noarch
aeolus-configure-2.0.2-4.20111005095819gitaf7e59a.el6.noarch
package condor is not installed
iwhd-0.98.15.z3-2.el6.x86_64
imagefactory-0.7.0-1.el6.noarch
aeolus-conductor-daemons-0.4.0-0.20111005200518gitf9deb7f.el6.noarch
aeolus-conductor-0.4.0-0.20111005200518gitf9deb7f.el6.noarch
[root@cf-cloudforms2 nodes]# 


How reproducible:

easliy

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 wes hayutin 2011-10-07 12:07:17 UTC
Angus, can you please comment here.. its been our understanding.. one provider per realm

Comment 3 wes hayutin 2011-10-11 14:40:43 UTC
recreated.. but I dont think this is supported..
The realms do not behave like hwp, and its one provider per realm.  So if you already have a realm created, you can not add another provider to it.

ack from Angus..

<athomas> weshay_hm You are correct. Realms are a subdivision within a provider
<athomas> weshay_hm What that bug is describing is much more like a pool
<weshay_hm> athomas, ya.. or a hwp
<athomas> weshay_hm Yup

Comment 4 Scott Seago 2011-10-11 14:50:06 UTC
There seems to be some confusion here. There are back-end realms that are subdivisions within a provider. However, the conductor/front-end realms (which are the ones the end user actually sees) are mapped across providers.

So, in fact, the realms the user sees can span across providers and provider realms. If you can't edit an existing front end realm, that would be a real bug.

Comment 5 Scott Seago 2011-10-11 15:20:40 UTC
Re-reading, the request here is to add UI to manage realm mappings from the Provider/ProviderRealm side. Right now we can only do that from the Conductor/global side. It's a valid concern, but probably not something that we'll be able to do in the short term.

Comment 6 wes hayutin 2011-10-11 17:20:41 UTC
moving this back to assigned.

adding this as a future feature.


Note You need to log in before you can comment on or make changes to this bug.