Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@deltacloud.apache.org
Date: Fri, 1 Jun 2012 07:49:25 +0000 (UTC)
From: "Jan Provaznik (JIRA)" <jira@apache.org>
To: dev@deltacloud.apache.org
Message-ID: <1427734913.25691.1338536965533.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Created] (DTACLOUD-224) Error abstraction/categorization
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jan Provaznik created DTACLOUD-224:
--------------------------------------

             Summary: Error abstraction/categorization
                 Key: DTACLOUD-224
                 URL: https://issues.apache.org/jira/browse/DTACLOUD-224
             Project: DeltaCloud
          Issue Type: Improvement
            Reporter: Jan Provaznik


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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira