deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michal Fojtik (Commented) (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-127) Add better error handling on valid_credentials? request
Date Thu, 19 Jan 2012 12:49:39 GMT


Michal Fojtik commented on DTACLOUD-127:


So in order to get this fixed we need to do following in Deltacloud API:

1. Remove 'begin' .. 'rescue' from 'valid_credentials?' in *all* drivers. We need to use 'safely'..'end'
block to catch all exceptions. This method should still return 'true' if credentials are valid
and 'false' if not.

2. We need to add 'valid_provider?' to Ruby Client. This will not affect driver/server core.
This method in client should fetch the content of "/api/drivers/DRIVER" (where DRIVER is the
current driver) and parse the response. This response should include list of all available
providers defined for current driver (works for EC2 and RHEV-M). The method should then check
if the argument given to 'valid_provider?' is valid API_PROVIDER value. 
> Add better error handling on valid_credentials? request
> -------------------------------------------------------
>                 Key: DTACLOUD-127
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Martyn Taylor
>            Assignee: Michal Fojtik
> In order to determine why a particular valid_credentials? request (using the ruby client)
has failed.  There should be sufficient error/exceptions.  
> Example:
> thin server (localhost:3002) [deltacloud-mock][22098]:
> Aws::AwsError:ec2-eu-west-1 temporarily unavailable: (getaddrinfo: Name or service not
> This causes failure of the valid_credentials? method but offers no more information.
> This is related to this BZ in aeolus-conductor: 

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