Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@deltacloud.apache.org
Date: Wed, 14 Dec 2011 20:05:31 +0000 (UTC)
From: "Michal Fojtik (Resolved) (JIRA)" <jira@apache.org>
To: dev@deltacloud.apache.org
Message-ID: 
 <236698234.12559.1323893131119.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <864439880.11047.1323872370701.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (DTACLOUD-117) Deltacloud does not return realms,
 instances, images available in rhevm provider
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DTACLOUD-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Fojtik resolved DTACLOUD-117.
------------------------------------

    Resolution: Not A Problem
      Assignee: Michal Fojtik  (was: David Lutterkort)

Hi,

This is not a bug. Yesterday I pushed a patch for Deltacloud API which treat RHEV-M data centers as separated entry points (similar to EC2 regions).
The problem, however is that in RHEV-M there is no 'default' data center we can use (in EC2 I think we automatically choose us-west1, if not specified).

To resolve this issue, you need to get UUID of the datacenter you want to speak to. To get this list you can browse "/api/drivers/rhevm?format=xml". The list of available 'providers' should appear here after supplying RHEV-M credentials.
Then you can choose what datacenter you want to speak with to, using:

API_PROVIDER="http://rhev-m.local:xxxx/rhevm-api;UUID-OF-DATACENTER"

If the datacenter is not specified, RHEV-M driver in Deltacloud will use the 'first' datacenter returned from RHEV-M ('default' in this case). Your 'default' datacenter has no clusters/images/etc, so this is the reason why they are blank.

Hope this helps. Also this change is not yet pushed to any RPM and will be part of the  upcoming release of deltacloud 1.0
                
> Deltacloud does not return realms, instances, images available in rhevm provider
> --------------------------------------------------------------------------------
>
>                 Key: DTACLOUD-117
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-117
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>         Environment: Fedora 16, RHEL 6.2, Fedora 15, RHEL 6.1 Firefox 7.0.1
> commit bdab47ae36b20eaa2956f263f744082adafa76d
>            Reporter: Ronelle Landy
>            Assignee: Michal Fojtik
>         Attachments: images.png, instances.png, realms.png
>
>
> Older versions of Deltacloud return realms, images and instances available in rhevm provider. 
> Build of dc from commit bdab47ae36b20eaa2956f263f744082adafa76d  returns no realms, instances or images. Screen shots from Deltacloud GUI attached.
> PS: Output from API does not return realms, images or instances available either. Example:
> >> curl -X GET --user "XXXX:XXXX" "http://server:3002/api/realms?format=xml"
> <?xml version='1.0' encoding='utf-8' ?>
> <realms>
> </realms>
> Affected modules- realms, images, instances

--
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