Re: [duracloud-dev] Duracloud with Openstack Swift Error

[Bill Branan]

Hi Onur,

As a starting point, since the error you're reporting is clearly a login failure, have you verified that you can connect to your OpenStack swift installation with the credentials you are using? Perhaps a stand-alone client like CyberDuck (http://cyberduck.ch/) could be of assistance there. You could also write a simple app using JClouds (http://www.jclouds.org/), just to verify that you're able to connect.

Bill

On Fri, Apr 19, 2013 at 4:53 AM, <onur.hali...@gmail.com> wrote:

Hi, I am trying to implement Duracloud with Openstack Swift.

I updated the authURL of sdscstorageprovider so that he points on my openstack. But I still can’t deploy the DuraCloud because it fails to connect to Openstack Swift.

Can you help me?

Error in the shell after running the commande : sudo java –jar target/app-config-2.0.3-driver.jar init-properties

09:32:25.590 [main] DEBUG o.a.c.httpclient.HttpConnection - Open connection to localhost:8080
09:32:25.591 [main] DEBUG httpclient.wire.header - >> "POST /durastore/init HTTP/1.1[\r][\n]"
09:32:25.591 [main] DEBUG o.a.c.httpclient.HttpMethodBase - Adding Host request header
09:32:25.591 [main] DEBUG httpclient.wire.header - >> "Content-Length: 408[\r][\n]"
09:32:25.591 [main] DEBUG httpclient.wire.header - >> "Authorization: Basic cm9vdDpycHc=[\r][\n]"
09:32:25.591 [main] DEBUG httpclient.wire.header - >> "User-Agent: Jakarta Commons-HttpClient/3.1[\r][\n]"
09:32:25.591 [main] DEBUG httpclient.wire.header - >> "Host: localhost:8080[\r][\n]"
09:32:25.591 [main] DEBUG httpclient.wire.header - >> "Content-Type: text/xml[\r][\n]"
09:32:25.591 [main] DEBUG httpclient.wire.header - >> "[\r][\n]"
09:32:25.591 [main] DEBUG httpclient.wire.content - >> "<?xml version="1.0" encoding="UTF-8"?>[\r][\n]"
09:32:25.592 [main] DEBUG httpclient.wire.content - >> "<storageProviderAccounts>[\r][\n]"
09:32:25.592 [main] DEBUG httpclient.wire.content - >> "  <storageAcct ownerId="0" isPrimary="1">[\r][\n]"
09:32:25.592 [main] DEBUG httpclient.wire.content - >> "    <id>0</id>[\r][\n]"
09:32:25.592 [main] DEBUG httpclient.wire.content - >> "    <storageProviderType>OPENSTACK</storageProviderType>[\r][\n]"
09:32:25.592 [main] DEBUG httpclient.wire.content - >> "    <storageProviderCredential>[\r][\n]"
09:32:25.592 [main] DEBUG httpclient.wire.content - >> "      <username>62:96:93:-100:-2:72:-87:-76:</username>[\r][\n]"
09:32:25.592 [main] DEBUG httpclient.wire.content - >> "      <password>62:96:93:-100:-2:72:-87:-76:</password>[\r][\n]"
09:32:25.592 [main] DEBUG httpclient.wire.content - >> "    </storageProviderCredential>[\r][\n]"
09:32:25.592 [main] DEBUG httpclient.wire.content - >> "  </storageAcct>[\r][\n]"
09:32:25.592 [main] DEBUG httpclient.wire.content - >> "</storageProviderAccounts>[\r][\n]"
09:32:25.592 [main] DEBUG httpclient.wire.content - >> "[\r][\n]"
09:32:25.593 [main] DEBUG o.a.c.h.m.EntityEnclosingMethod - Request body sent
09:32:26.068 [main] DEBUG httpclient.wire.header - << "HTTP/1.1 500 Internal Error Servlet[\r][\n]"
09:32:26.068 [main] DEBUG httpclient.wire.header - << "HTTP/1.1 500 Internal Error Servlet [\r][\n]"
09:32:26.068 [main] DEBUG httpclient.wire.header - << "Server: Apache-Coyote/1.1[\r][\n]"
09:32:26.068 [main] DEBUG httpclient.wire.header - << "Content-Type: text/plain[\r][\n]"
09:32:26.068 [main] DEBUG httpclient.wire.header - << "Transfer-Encoding: chunked[\r][\n]"
09:32:26.068 [main] DEBUG httpclient.wire.header - << "Date: Fri, 19 Apr 2013 07:32:26 GMT[\r][\n]"
09:32:26.068 [main] DEBUG httpclient.wire.header - << "Connection: close[\r][\n]"
09:32:26.068 [main] DEBUG httpclient.wire.header - << "[\r][\n]"
09:32:26.069 [main] DEBUG o.d.common.web.RestHttpHelper - RESPONSE CODE: '500'
RESPONSE HEADERS:
  [Server|Apache-Coyote/1.1]
  [Content-Type|text/plain]
  [Transfer-Encoding|chunked]
  [Date|Fri, 19 Apr 2013 07:32:26 GMT]
  [Connection|close]

09:32:26.069 [main] DEBUG httpclient.wire.content - << "3"
09:32:26.069 [main] DEBUG httpclient.wire.content - << "c"
09:32:26.069 [main] DEBUG httpclient.wire.content - << "[\r]"
09:32:26.069 [main] DEBUG httpclient.wire.content - << "[\n]"
09:32:26.069 [main] DEBUG httpclient.wire.content - << "Could not connect to OPENSTACK due to error: Login to OPENSTACK failed"
09:32:26.069 [main] DEBUG httpclient.wire.content - << "[\r]"
09:32:26.069 [main] DEBUG httpclient.wire.content - << "[\n]"
09:32:26.069 [main] DEBUG httpclient.wire.content - << "0"
09:32:26.069 [main] DEBUG httpclient.wire.content - << "[\r]"
09:32:26.069 [main] DEBUG httpclient.wire.content - << "[\n]"
09:32:26.069 [main] DEBUG httpclient.wire.content - << "[\r]"
09:32:26.069 [main] DEBUG httpclient.wire.content - << "[\n]"
09:32:26.070 [main] DEBUG httpclient.wire.header - << "[\r][\n]"
09:32:26.070 [main] DEBUG o.a.c.httpclient.HttpMethodBase - Should close connection in response to directive: close
09:32:26.070 [main] DEBUG o.a.c.httpclient.HttpConnection - Releasing connection back to connection manager.
09:32:26.070 [main] ERROR o.d.appconfig.ApplicationInitializer - error initializing durastore (500)
Could not connect to OPENSTACK due to error: Login to OPENSTACK failed
Exception in thread "main" org.duracloud.common.error.DuraCloudRuntimeException: error initializing durastore (500)
Could not connect to OPENSTACK due to error: Login to OPENSTACK failed

Error message in catalina.out

INFO           2013/04/19 09:32:25 [http-8080-2] (StorageProviderFactoryImpl.java:78) [initializeStorageProviders()] - Caching storage providers on init is enabled: building storage provider cache...
ERROR          2013/04/19 09:32:26 [http-8080-2] (InitRest.java:94) [responseBad()] - Error while initializing DuraStore: Could not connect to OPENSTACK due to error: Login to OPENSTACK failed

 

My init.properties

###
# defines where duradmin, durastore, duraservice are deployed
###
app.*.host=localhost
app.*.port=8080
app.durastore.context=durastore
app.duraservice.context=duraservice
app.duradmin.context=duradmin
# app.duraboss.context=duraboss

durastore.storage-acct.0.owner-id=0
durastore.storage-acct.0.is-primary=true
durastore.storage-acct.0.id=0
durastore.storage-acct.0.provider-type=OPENSTACK
durastore.storage-acct.0.username=OpenstackUsername
durastore.storage-acct.0.password=OpenstackPassword

###
# defines duraservice elements
###
duraservice.primary-instance.host=localhost
duraservice.primary-instance.services-admin-port=8089
duraservice.primary-instance.services-admin-context=org.duracloud.services.admin_2.3.0
duraservice.user-storage.host=localhost
duraservice.user-storage.port=8080
duraservice.user-storage.context=durastore
duraservice.user-storage.msg-broker-url=tcp://localhost:61617
duraservice.service-storage.host=dcprod.duracloud.org
#duraservice.service-storage.host=localhost

# duraservice.service-storage.port=Openstack port ?
duraservice.service-storage.port=9999
duraservice.service-storage.context=durastore
duraservice.service-storage.username=MyUsername
duraservice.service-storage.password=MyPassword
duraservice.service-storage.space-id=duracloud-2.3.0-service-repository
duraservice.service-storage.service-xml-id=duracloud-2.3.0-service-repository.xml

###
# defines where durastore and duraservice are deployed, for duradmin
###
duradmin.durastore-host=localhost
duradmin.durastore-port=8080
duradmin.durastore-context=durastore
duradmin.duraservice-host=localhost
duradmin.duraservice-port=8080
duradmin.duraservice-context=duraservice


###
# defines new users
###
security.user.0.username=MyUsername
security.user.0.password=MyUsername
security.user.0.email=x...@mail.com
security.user.0.enabled=true
security.user.0.acct-non-expired=true
security.user.0.cred-non-expired=true
security.user.0.acct-non-locked=true
security.user.0.grants.0=ROLE_USER
security.user.0.grants.1=ROLE_ADMIN

Thank you very much for your support.

 

Best regards.

Onur Erdogan

--
You received this message because you are subscribed to the Google Groups "DuraCloud Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to duracloud-de...@googlegroups.com.
To post to this group, send email to duracl...@googlegroups.com.
Visit this group at http://groups.google.com/group/duracloud-dev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[onur.hali...@gmail.com]

Hi Bill,

Apparently cyberduck is not compatible with keystone for the identification.

I'm wondering if Duracloud was compatible with keystone ?

Thank you very much for your support.

 

Best regards.

Onur Erdogan

security.user.0.email=xxx@mail.com

security.user.0.enabled=true
security.user.0.acct-non-expired=true
security.user.0.cred-non-expired=true
security.user.0.acct-non-locked=true
security.user.0.grants.0=ROLE_USER
security.user.0.grants.1=ROLE_ADMIN

[Bill Branan]

Hi Onur,

We currently test DuraCloud against two OpenStack implementations: Rackspace CloudFiles and SDSC Cloud. It is mentioned here: http://www.rackspace.com/knowledge_center/article/syncing-private-cloud-swift-containers-to-rackspace-cloud-files that Rackspace does not use Keystone for authentication. I can't say for sure what SDSC uses, but I know that it does work with cyberduck (https://cloud.sdsc.edu/hp/cyberduck.php). So according to your findings, SDSC is likely not using Keystone either. That being the case, we haven't attempted to connect DuraCloud to OpenStack using Keystone authentication. My guess is that it would not work out of the box. 

You are welcome to experiment with the code to see if you are able to get authentication to work. If you are, we'd be very interested to see what changes are necessary to support a Keystone auth system in front of OpenStack. 

Bill

--

[Bikramjit Singh]

Sorry for posting in this thread after long time, but were you able to make it working? I am trying to connect duracloud to my swift storage and its failing with invalidtoken error.

security.user.0.email=x...@mail.com

security.user.0.enabled=true
security.user.0.acct-non-expired=true
security.user.0.cred-non-expired=true
security.user.0.acct-non-locked=true
security.user.0.grants.0=ROLE_USER
security.user.0.grants.1=ROLE_ADMIN