Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@deltacloud.apache.org
Date: Thu, 27 Sep 2012 20:10:07 +1100 (NCT)
From: "Michal Fojtik (JIRA)" <jira@apache.org>
To: dev@deltacloud.apache.org
Message-ID: <1702465519.132880.1348737007813.JavaMail.jiratomcat@arcas>
In-Reply-To: <403585227.132844.1348735447685.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (DTACLOUD-330) Openstack driver - Deltacloud
 requires credentials for any request
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Michal Fojtik commented on DTACLOUD-330:
----------------------------------------

Another possible solution for Conductor could be:

* GET /api/drivers

Then parse the response and check if the requested driver is included in list of driver. This collection does not require authentication, so it should always return 200.

I'll send a patch for the 401 exception. 
                
> Openstack driver - Deltacloud requires credentials for any request
> ------------------------------------------------------------------
>
>                 Key: DTACLOUD-330
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-330
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>         Environment: deltalcoud-core from master branch (last commit 97db199f908eb9fcd7780d904e7161fb7c60bac5)
>            Reporter: Jan Provaznik
>            Assignee: Michal Fojtik
>
> Conductor keeps providers and provider accounts separately. This means that at first step a user adds a provider (ec2, rhevm, openstack), then he can add multiple accounts for this provider.
> When adding a provider, Conductor checks if the provider is valid by doing dc connect with nil credentials:
> DeltaCloud.new(nil, nil, url)
> The problem is that this call always fails for Openstack driver with 
> Deltacloud::ExceptionHandler::BackendError - Unhandled exception or status code (Must supply a :username):
> 	/usr/local/share/gems/gems/openstack-1.0.6/lib/openstack/connection.rb:74:in `initialize'
> 	/usr/local/share/gems/gems/openstack-1.0.6/lib/openstack/connection.rb:60:in `new'
> 	/usr/local/share/gems/gems/openstack-1.0.6/lib/openstack/connection.rb:60:in `create'
> 	/home/jprovazn/devel/deltacloud/server/lib/deltacloud/drivers/openstack/openstack_driver.rb:357:in `block in new_client'
> 	/home/jprovazn/devel/deltacloud/server/lib/deltacloud/drivers/exceptions.rb:199:in `call'
> 	/home/jprovazn/devel/deltacloud/server/lib/deltacloud/drivers/exceptions.rb:199:in `safely'
> 	/home/jprovazn/devel/deltacloud/server/lib/deltacloud/drivers/openstack/openstack_driver.rb:352:in `new_client'
> 	/home/jprovazn/devel/deltacloud/server/lib/deltacloud/drivers/openstack/openstack_driver.rb:47:in `supported_collections'
> 	/home/jprovazn/devel/deltacloud/server/lib/deltacloud/server.rb:52:in `block in <class:API>'
> From what I know DC requries openstack credentials to be able to connect to openstack api and check if some bucket is supported or not.
> Is it possible to offer some unauthenticated connection which can be used just to check that a provider is accessible?

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