You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@deltacloud.apache.org by "Jan Provaznik (JIRA)" <ji...@apache.org> on 2012/10/10 15:47:03 UTC

[jira] [Commented] (DTACLOUD-224) Error abstraction/categorization

    [ https://issues.apache.org/jira/browse/DTACLOUD-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473226#comment-13473226 ] 

Jan Provaznik commented on DTACLOUD-224:
----------------------------------------

error categories are tracked in separate ticket: https://issues.apache.org/jira/browse/DTACLOUD-309

> So if Deltacloud API will get some smart error categorisation system, that system may not work well for everyone.
Well, the original provider error would be kept, so no information would be lost.
                
> Error abstraction/categorization
> --------------------------------
>
>                 Key: DTACLOUD-224
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-224
>             Project: DeltaCloud
>          Issue Type: Improvement
>            Reporter: Jan Provaznik
>            Assignee: Michal Fojtik
>
> It would be nice to get categorized errors from Deltacloud if something goes wrong instead of just forwarding a provider specific error directly to client. For example if an instance create failed because something was wrong with hw profile, Deltacloud would return HWProfileError exception. The original provider specific exception would be included in some description.
> For the beginning most errors would be in some some generic class, only most common errors would be categorized, especially these which are related to params passed in API calls, for instance creation it would be errors related to image id, realms, hwp...
> Use case for Aeolus is this: if instance create action fails for some reason, we need to decide if the instance should be launched on same provider with different configuration (different realm/hwp...) or if it's better to try launch the instance on another provider account or even provider.
> Deltacloud is the best place where the error abstraction should be done because:
> - Deltacloud is the abstraction layer which should abstract provider-specific behavior
> - each Deltacloud client would have to implement it's own error abstraction

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira