deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dave johnson (Commented) (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-126) RHEV-M: We need to skip 'default' cluster when no 'realm_id' is specified in create_instance
Date Fri, 13 Jan 2012 18:10:39 GMT


dave johnson commented on DTACLOUD-126:

I forgot to mention, in my case, the data center only had one cluster underneath it so maybe
when that scenario is hit, just use the single cluster under the data center

> RHEV-M: We need to skip 'default' cluster when no 'realm_id' is specified in create_instance
> --------------------------------------------------------------------------------------------
>                 Key: DTACLOUD-126
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>            Reporter: Michal Fojtik
>            Assignee: Michal Fojtik
>            Priority: Blocker
> When there is no realm_id provided upon creating a new instance, by default Deltacloud
will choose the first 'realm' returned by 'realms' call.
> In RHEV-M it usually means that the 'default' cluster is being returned, which is wrong
in most cases, since this cluster is being used for
> holding the 'Blank' template, thus cannot be removed. This cluster usually don't have
'storage domain' assigned and deploying an instance
> there lead to error.
> The solution could to to 'skip' default realm and try to use next realm in row (if there
is next realm). If there is just 'default' realm, we should
> choose this realm and additionally give client decent error :-)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message