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

Michal Fojtik commented on DTACLOUD-127:
----------------------------------------

Hi,

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: https://issues.apache.org/jira/browse/DTACLOUD-127
>             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 known)
> This causes failure of the valid_credentials? method but offers no more 
> information.
> This is related to this BZ in aeolus-conductor: 
> https://bugzilla.redhat.com/show_bug.cgi?id=753880

--
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

        

Reply via email to