deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Provaznik (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-309) RFE: Deltacloud API backend errors/exceptions categorisation system
Date Wed, 10 Oct 2012 13:35:05 GMT


Jan Provaznik commented on DTACLOUD-309:

This request was originally tracked here:
One of use cases for Aeolus is this (most important): 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 another provider.

Bellow is basic kick-off list of errors for which it would be nice to distinguish between.
Feel free to define their exception class names as you prefer. The original error message
from provider would be kept in exception. IOW this would be mostly about finer graining of
BackendError exception class.

Related to instance launching
* wrong image (doesn't exist)
* wrong hardware profile
* not enough resources
* wrong hw profile override value (optional?)
* wrong realm
* wrong provider account - doesn't exist, disabled, wrong credentials
* wrong provider - not accessible
* "temporary" error (if common?) - 

Related to periodic instance checking:
* provider is not accessible
* auth failure (already supported?)
* instance was not found (includes perission error?)

> RFE: Deltacloud API backend errors/exceptions categorisation system
> -------------------------------------------------------------------
>                 Key: DTACLOUD-309
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Michal Fojtik
>            Assignee: Michal Fojtik
>            Priority: Minor
> This JIRA should collection proposed 'Generic Errors'  and the mappings to actual provider
> The comment should contain proposed generic error name (class) and list of exceptions
that this error
> will capture.
> Example:
> **WrongImageID**
> EC2: InvalidAMIID.*
> RHEV-M: Unknown Template

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:

View raw message