deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Provaznik (JIRA)" <>
Subject [jira] [Created] (DTACLOUD-330) Openstack driver - Deltacloud requires credentials for any request
Date Thu, 27 Sep 2012 08:44:07 GMT
Jan Provaznik created DTACLOUD-330:

             Summary: Openstack driver - Deltacloud requires credentials for any request
                 Key: DTACLOUD-330
             Project: DeltaCloud
          Issue Type: Bug
          Components: Server
         Environment: deltalcoud-core from master branch (last commit 97db199f908eb9fcd7780d904e7161fb7c60bac5)
            Reporter: Jan Provaznik

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
When adding a provider, Conductor checks if the provider is valid by doing dc connect with
nil credentials:, 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'
`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/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:

View raw message