[
https://issues.apache.org/jira/browse/DTACLOUD-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ronelle Landy closed DTACLOUD-57.
---------------------------------
Resolution: Fixed
Closing this issue. As per comments from JIRA reporter:
"No, that is no longer a issue, DC has been showing cluster name for some time
now
API also recognizes two clusters in one datacenter:
curl -X GET --user 'uname:password' "http://server:3001/api/realms?format=xml"
<?xml version='1.0' encoding='utf-8' ?>
<realms>
<realm
href='http://server:3001/api/realms/d21bab08-4086-11e1-922a-5cf3fc1c861c'
id='d21bab08-4086-11e1-922a-5cf3fc1c861c'>
<name>cluster3</name>
<state>AVAILABLE</state>
</realm>
<realm
href='http://sever:3001/api/realms/bdce3f96-4070-11e1-9f90-5cf3fc1c861c'
id='bdce3f96-4070-11e1-9f90-5cf3fc1c861c'>
<name>NewCluster</name>
<state>AVAILABLE</state>
</realm>
</realms>
> rhevm realms confusing
> ----------------------
>
> Key: DTACLOUD-57
> URL: https://issues.apache.org/jira/browse/DTACLOUD-57
> Project: DeltaCloud
> Issue Type: Bug
> Environment: Aeolus-conductor configured for rhevm provider
> [root@hp-dl2x170g6-01 ~]# rpm -qa | egrep 'aeolus|deltacloud' | sort
> aeolus-all-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-conductor-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-conductor-daemons-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-conductor-doc-0.3.0-0.el6.20110711131044git5bc7abf.noarch
> aeolus-configure-2.0.1-0.el6.20110708134115gitab1e6dc.noarch
> condor-deltacloud-gahp-7.6.0-5dcloud.el6.x86_64
> deltacloud-core-0.3.9999-1308927004.el6.noarch
> libdeltacloud-0.9-1.el6.x86_64
> rubygem-aeolus-cli-0.0.1-1.el6.20110711131044git5bc7abf.noarch
> rubygem-deltacloud-client-0.3.1-1.el6.noarch
> [root@hp-dl2x170g6-01 ~]#
> Reporter: dave johnson
> Assignee: Michal Fojtik
> Attachments: actual.png, rhevm.png
>
>
> When you have a single datacenter with multiple clusters underneath it, the
> datacenter name is listed multiple times within deltacloud core (& conductor)
> for each cluster. We need to maybe append the datacenter name with each
> '-clusterName'.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira