From shashidhar.velagandula at gmail.com Fri Apr 1 06:35:14 2011 From: shashidhar.velagandula at gmail.com (shashidhar v) Date: Fri, 1 Apr 2011 12:05:14 +0530 Subject: [Openstack-operators] failed to run the auth-server deamon for SAIO setup In-Reply-To: <4696C6EF-36BE-4D7D-939F-FD7364A2AAB8@zeroaccess.org> References: <4696C6EF-36BE-4D7D-939F-FD7364A2AAB8@zeroaccess.org> Message-ID: HI Marcelo , Thanks for the reply , 1. W.r.t problem #1 , I have stopped the tomcat service which is using the port 8080 and then started the swift service without any errors . It is using "swauth" auth. mechanisam as you mentioned swift-1.3 develop supports only swauth ,then created the accounts using "recreateaccounts" script of SAIO ,, #!/bin/bash # Replace swauthkey with whatever your super_admin key is (recorded in # /etc/swift/proxy-server.conf). swauth-prep -K swauthkey swauth-add-user -K swauthkey -a test tester testing swauth-add-user -K swauthkey -a test2 tester2 testing2 swauth-add-user -K swauthkey test tester3 testing3 swauth-add-user -K swauthkey -a -r reseller reseller reseller [shashi at shashi samples]$ curl -v -H 'X-Storage-User: test:tester3' -H 'X-Storage-Pass: testing3' http://192.168.62.63:8080/auth/v1.0 * About to connect() to 192.168.62.63 port 8080 * Trying 192.168.62.63... connected * Connected to 192.168.62.63 (192.168.62.63) port 8080 > GET /auth/v1.0 HTTP/1.1 > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > Host: 192.168.62.63:8080 > Accept: */* > X-Storage-User: test:tester3 > X-Storage-Pass: testing3 > < HTTP/1.1 200 OK < X-Storage-Url: http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a < X-Storage-Token: AUTH_tke67d8d3c037649688bd527a7b77cc287 < X-Auth-Token: AUTH_tke67d8d3c037649688bd527a7b77cc287 < Content-Length: 112 < Date: Fri, 01 Apr 2011 04:31:06 GMT Connection #0 to host 192.168.62.63 left intact * Closing connection #0 {"storage": {"default": "local", "local": " http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a "}}[shashi at shashi samples]$ [shashi at shashi samples]$ [shashi at shashi samples]$ curl -v -H 'X-Auth-Token: AUTH_tke67d8d3c037649688bd527a7b77cc287' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a * About to connect() to 192.168.62.63 port 8080 * Trying 192.168.62.63... connected * Connected to 192.168.62.63 (192.168.62.63) port 8080 > GET /v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a HTTP/1.1 > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > Host: 192.168.62.63:8080 > Accept: */* > X-Auth-Token: AUTH_tke67d8d3c037649688bd527a7b77cc287 > < HTTP/1.1 403 Forbidden < Content-Length: 157 < Content-Type: text/html; charset=UTF-8 < Date: Fri, 01 Apr 2011 04:45:35 GMT 403 Forbidden

403 Forbidden

Access was denied to this resource.

Connection #0 to host 192.168.62.63 left intact * Closing connection #0 [shashi at shashi samples]$ [shashi at shashi samples]$ In the above script, the third user is tester3 (non admin) which is not allowed to create containers ? Then what's the role of non-admin users created under swift , what operations they can perform ? Swift supports ACL or not and the containers/objects created by a admin user can be shared with non-admin user for atleast downloading the objects ? 2. In order to check the "devauth" authentication , I have donwloaded the swift-1.2.0.tar.gz in a second test node , what's the command to build the code ,, sudo python setup.py develop or anyother command I need to use ? Whether same SAIO doc can be referred to start the deamons ? Thanks & Regards, shashi On Thu, Mar 31, 2011 at 9:35 PM, Marcelo Martins wrote: > Sent u a reply for the message below a few minutes ago .... Please reply > to btorch-os at zeroaccess.org and the list when u do so.. Thanks > > > Marcelo > > > On Mar 31, 2011, at 4:33 AM, shashidhar v wrote: > > HI, > > I am trying to install and test the Swift tool by following the SAIO > I have set up the repos and downloaded the code as per the steps given in > SAIO > > swift at test3:~/swift$ cd ~/swift/trunk; sudo python setup.py develop > running develop > running egg_info > creating swift.egg-info > writing swift.egg-info/PKG-INFO > writing top-level names to swift.egg-info/top_level.txt > writing dependency_links to swift.egg-info/dependency_links.txt > writing entry points to swift.egg-info/entry_points.txt > writing manifest file 'swift.egg-info/SOURCES.txt' > reading manifest file 'swift.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no files found matching 'ChangeLog' > writing manifest file 'swift.egg-info/SOURCES.txt' > running build_ext > Creating /usr/local/lib/python2.6/dist-packages/swift.egg-link (link to .) > Removing swift 1.3-dev from easy-install.pth file > Adding swift 1.3-dev to easy-install.pth file > Installing st script to /usr/local/bin > Installing swift-account-auditor script to /usr/local/bin > Installing swift-account-audit script to /usr/local/bin > Installing swift-account-reaper script to /usr/local/bin > Installing swift-account-replicator script to /usr/local/bin > Installing swift-account-server script to /usr/local/bin > Installing swift-container-auditor script to /usr/local/bin > Installing swift-container-replicator script to /usr/local/bin > Installing swift-container-server script to /usr/local/bin > Installing swift-container-updater script to /usr/local/bin > Installing swift-drive-audit script to /usr/local/bin > Installing swift-get-nodes script to /usr/local/bin > Installing swift-init script to /usr/local/bin > Installing swift-object-auditor script to /usr/local/bin > Installing swift-object-info script to /usr/local/bin > Installing swift-object-replicator script to /usr/local/bin > Installing swift-object-server script to /usr/local/bin > Installing swift-object-updater script to /usr/local/bin > Installing swift-proxy-server script to /usr/local/bin > Installing swift-ring-builder script to /usr/local/bin > Installing swift-stats-populate script to /usr/local/bin > Installing swift-stats-report script to /usr/local/bin > Installing swift-bench script to /usr/local/bin > Installing swift-log-uploader script to /usr/local/bin > Installing swift-log-stats-collector script to /usr/local/bin > Installing swift-account-stats-logger script to /usr/local/bin > Installing swauth-add-account script to /usr/local/bin > Installing swauth-add-user script to /usr/local/bin > Installing swauth-cleanup-tokens script to /usr/local/bin > Installing swauth-delete-account script to /usr/local/bin > Installing swauth-delete-user script to /usr/local/bin > Installing swauth-list script to /usr/local/bin > Installing swauth-prep script to /usr/local/bin > Installing swauth-set-account-service script to /usr/local/bin > > Installed /home/swift/swift/trunk > Processing dependencies for swift==1.3-dev > Finished processing dependencies for swift==1.3-dev > swift at test3:~/swift/trunk$ > > > swift at test3:~$ startmain > WARNING: Unable to increase file descriptor limit. Running as non-root? > Starting proxy-server...(/etc/swift/proxy-server.conf) > Starting container-server...(/etc/swift/container-server/1.conf) > Starting container-server...(/etc/swift/container-server/2.conf) > Starting container-server...(/etc/swift/container-server/3.conf) > Starting container-server...(/etc/swift/container-server/4.conf) > Starting account-server...(/etc/swift/account-server/1.conf) > Starting account-server...(/etc/swift/account-server/2.conf) > Starting account-server...(/etc/swift/account-server/3.conf) > Starting account-server...(/etc/swift/account-server/4.conf) > Starting object-server...(/etc/swift/object-server/1.conf) > Starting object-server...(/etc/swift/object-server/2.conf) > Starting object-server...(/etc/swift/object-server/3.conf) > Starting object-server...(/etc/swift/object-server/4.conf) > Traceback (most recent call last): > File "/usr/local/bin/swift-proxy-server", line 7, in > execfile(__file__) > File "/home/swift/swift/trunk/bin/swift-proxy-server", line 22, in > > run_wsgi(conf_file, 'proxy-server', default_port=8080, **options) > File "/home/swift/swift/trunk/swift/common/wsgi.py", line 123, in > run_wsgi > sock = get_socket(conf, default_port=kwargs.get('default_port', 8080)) > File "/home/swift/swift/trunk/swift/common/wsgi.py", line 89, in > get_socket > bind_addr) > Exception: Could not bind to 0.0.0.0:8080 after trying for 30 seconds > > WARNING: Unable to increase file descriptor limit. Running as non-root? > Starting auth-server...(/etc/swift/auth-server.conf) > Traceback (most recent call last): > File "/usr/local/bin/swift-auth-server", line 5, in > pkg_resources.run_script('swift==1.3-dev', 'swift-auth-server') > File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 461, in > run_script > self.require(requires)[0].run_script(script_name, ns) > File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 1188, in > run_script > raise ResolutionError("No script named %r" % script_name) > pkg_resources.ResolutionError: No script named 'swift-auth-server' > > swift at test3:~$ > > Kindly help me to resolve the above error > > Thanks & Regards, > shashi > > _______________________________________________ > Openstack-operators mailing list > Openstack-operators at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gholt at rackspace.com Fri Apr 1 13:02:45 2011 From: gholt at rackspace.com (Greg Holt) Date: Fri, 1 Apr 2011 08:02:45 -0500 Subject: [Openstack-operators] failed to run the auth-server deamon for SAIO setup In-Reply-To: References: <4696C6EF-36BE-4D7D-939F-FD7364A2AAB8@zeroaccess.org> Message-ID: <43C2F369-B701-4163-8805-EA6657742D9E@rackspace.com> On Apr 1, 2011, at 1:35 AM, shashidhar v wrote: > In the above script, the third user is tester3 (non admin) which is not allowed to create containers ? Then what's the role of non-admin users created under swift , what operations they can perform ? > > Swift supports ACL or not and the containers/objects created by a admin user can be shared with non-admin user for atleast downloading the objects ? Non-admin users can only perform operations per container based on the container?s X-Container-Read and X-Container-Write ACLs. With an admin account you could create a container for that non-admin user and set X-Container-Read: test:tester3 and X-Container-Write: test:tester3. These may explain more: http://swift.openstack.org/overview_auth.html http://swift.openstack.org/misc.html#module-swift.common.middleware.acl From shashidhar.velagandula at gmail.com Tue Apr 5 10:32:24 2011 From: shashidhar.velagandula at gmail.com (shashidhar v) Date: Tue, 5 Apr 2011 16:02:24 +0530 Subject: [Openstack-operators] failed to run the auth-server deamon for SAIO setup In-Reply-To: <43C2F369-B701-4163-8805-EA6657742D9E@rackspace.com> References: <4696C6EF-36BE-4D7D-939F-FD7364A2AAB8@zeroaccess.org> <43C2F369-B701-4163-8805-EA6657742D9E@rackspace.com> Message-ID: Hi Gholt, I tried to set the container based read and write acl to share the container with non admin user , but it is giving error as access denied [shashi at shashi samples]$ curl -v -H 'X-Storage-User: test:tester' -H 'X-Storage-Pass: testing' http://192.168.62.63:8080/auth/v1.0* About to connect() to 192.168.62.63 port 8080 * Trying 192.168.62.63... connected * Connected to 192.168.62.63 (192.168.62.63) port 8080 > GET /auth/v1.0 HTTP/1.1 > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > Host: 192.168.62.63:8080 > Accept: */* > X-Storage-User: test:tester > X-Storage-Pass: testing > < HTTP/1.1 200 OK < X-Storage-Url: http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a < X-Storage-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525 < X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525 < Content-Length: 112 < Date: Tue, 05 Apr 2011 10:18:31 GMT Connection #0 to host 192.168.62.63 left intact * Closing connection #0 {"storage": {"default": "local", "local": " http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a "}}[shashi at shashi samples]$ [shashi at shashi samples]$ curl -X HEAD -D - -H 'X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a HTTP/1.1 204 No Content X-Account-Object-Count: 0 X-Account-Bytes-Used: 0 X-Account-Container-Count: 1 Content-Length: 0 Date: Tue, 05 Apr 2011 10:20:19 GMT [shashi at shashi samples]$ [shashi at shashi samples]$ curl -X HEAD -D - -H 'X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 HTTP/1.1 204 No Content X-Container-Object-Count: 1 X-Container-Bytes-Used: 29 Content-Length: 0 Date: Tue, 05 Apr 2011 10:20:40 GMT [shashi at shashi samples]$ Initially I have created a container named as "container1" using the admin user "test:tester" and then trying to set read and write acl for the container1 to share it with non-admin user .......... [shashi at shashi samples]$ curl -v -H 'X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525' -H 'X-Container-Read: test:tester3' -H 'X-Container-Write: test:tester3' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 * About to connect() to 192.168.62.63 port 8080 * Trying 192.168.62.63... connected * Connected to 192.168.62.63 (192.168.62.63) port 8080 > GET /v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 HTTP/1.1 > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > Host: 192.168.62.63:8080 > Accept: */* > X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525 > X-Container-Read: test:tester3 > X-Container-Write: test:tester3 > < HTTP/1.1 200 OK < X-Container-Object-Count: 1 < X-Container-Bytes-Used: 29 < Content-Length: 10 < Content-Type: text/plain; charset=utf8 < Date: Tue, 05 Apr 2011 10:11:01 GMT testfile1 * Connection #0 to host 192.168.62.63 left intact * Closing connection #0 [shashi at shashi samples]$ [shashi at shashi samples]$ curl -v -H 'X-Storage-User: test:tester3' -H 'X-Storage-Pass: testing3' http://192.168.62.63:8080/auth/v1.0* About to connect() to 192.168.62.63 port 8080 * Trying 192.168.62.63... connected * Connected to 192.168.62.63 (192.168.62.63) port 8080 > GET /auth/v1.0 HTTP/1.1 > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > Host: 192.168.62.63:8080 > Accept: */* > X-Storage-User: test:tester3 > X-Storage-Pass: testing3 > < HTTP/1.1 200 OK < X-Storage-Url: http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a < X-Storage-Token: AUTH_tk124a8a19ad7e49c5a04710716fd4f126 < X-Auth-Token: AUTH_tk124a8a19ad7e49c5a04710716fd4f126 < Content-Length: 112 < Date: Tue, 05 Apr 2011 10:11:16 GMT Connection #0 to host 192.168.62.63 left intact * Closing connection #0 {"storage": {"default": "local", "local": " http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a "}}[shashi at shashi samples]$ [shashi at shashi samples]$ curl -s -D - -H 'X-Auth-Token: AUTH_tk124a8a19ad7e49c5a04710716fd4f126' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1/testfile1 HTTP/1.1 403 Forbidden Content-Length: 157 Content-Type: text/html; charset=UTF-8 Date: Tue, 05 Apr 2011 10:11:42 GMT 403 Forbidden

403 Forbidden

Access was denied to this resource.

[shashi at shashi samples]$ [shashi at shashi samples]$ Thanks & Regards, shashi On Fri, Apr 1, 2011 at 6:32 PM, Greg Holt wrote: > On Apr 1, 2011, at 1:35 AM, shashidhar v wrote: > > > In the above script, the third user is tester3 (non admin) which is not > allowed to create containers ? Then what's the role of non-admin users > created under swift , what operations they can perform ? > > > > Swift supports ACL or not and the containers/objects created by a admin > user can be shared with non-admin user for atleast downloading the objects ? > > Non-admin users can only perform operations per container based on the > container?s X-Container-Read and X-Container-Write ACLs. With an admin > account you could create a container for that non-admin user and set > X-Container-Read: test:tester3 and X-Container-Write: test:tester3. > > These may explain more: > > http://swift.openstack.org/overview_auth.html > http://swift.openstack.org/misc.html#module-swift.common.middleware.acl > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gholt at rackspace.com Tue Apr 5 12:36:31 2011 From: gholt at rackspace.com (Greg Holt) Date: Tue, 5 Apr 2011 07:36:31 -0500 Subject: [Openstack-operators] failed to run the auth-server deamon for SAIO setup In-Reply-To: References: <4696C6EF-36BE-4D7D-939F-FD7364A2AAB8@zeroaccess.org> <43C2F369-B701-4163-8805-EA6657742D9E@rackspace.com> Message-ID: You have to use the PUT or POST command when trying to set the headers on a container. Try adding -X POST to that curl command: curl -v -X POST -H 'X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525' -H 'X-Container-Read: test:tester3' -H 'X-Container-Write: test:tester3' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 If you GET or the HEAD the container afterwards, you should see the two headers returned to you with the appropriate values. On Apr 5, 2011, at 5:32 AM, shashidhar v wrote: > Hi Gholt, > > I tried to set the container based read and write acl to share the container with non admin user , but it is giving error as access denied > > [shashi at shashi samples]$ curl -v -H 'X-Storage-User: test:tester' -H 'X-Storage-Pass: testing' http://192.168.62.63:8080/auth/v1.0* About to connect() to 192.168.62.63 port 8080 > * Trying 192.168.62.63... connected > * Connected to 192.168.62.63 (192.168.62.63) port 8080 > > GET /auth/v1.0 HTTP/1.1 > > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > > Host: 192.168.62.63:8080 > > Accept: */* > > X-Storage-User: test:tester > > X-Storage-Pass: testing > > > < HTTP/1.1 200 OK > < X-Storage-Url: http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a > < X-Storage-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525 > < X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525 > < Content-Length: 112 > < Date: Tue, 05 Apr 2011 10:18:31 GMT > Connection #0 to host 192.168.62.63 left intact > * Closing connection #0 > {"storage": {"default": "local", "local": "http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a"}}[shashi at shashi samples]$ > > > [shashi at shashi samples]$ curl -X HEAD -D - -H 'X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a > HTTP/1.1 204 No Content > X-Account-Object-Count: 0 > X-Account-Bytes-Used: 0 > X-Account-Container-Count: 1 > Content-Length: 0 > Date: Tue, 05 Apr 2011 10:20:19 GMT > > [shashi at shashi samples]$ > [shashi at shashi samples]$ curl -X HEAD -D - -H 'X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 > HTTP/1.1 204 No Content > X-Container-Object-Count: 1 > X-Container-Bytes-Used: 29 > Content-Length: 0 > Date: Tue, 05 Apr 2011 10:20:40 GMT > > [shashi at shashi samples]$ > > > > Initially I have created a container named as "container1" using the admin user "test:tester" and then trying to set read and write acl for the container1 to share it with non-admin user .......... > > > > [shashi at shashi samples]$ curl -v -H 'X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525' -H 'X-Container-Read: test:tester3' -H 'X-Container-Write: test:tester3' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 > * About to connect() to 192.168.62.63 port 8080 > * Trying 192.168.62.63... connected > * Connected to 192.168.62.63 (192.168.62.63) port 8080 > > GET /v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 HTTP/1.1 > > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > > Host: 192.168.62.63:8080 > > Accept: */* > > X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525 > > X-Container-Read: test:tester3 > > X-Container-Write: test:tester3 > > > < HTTP/1.1 200 OK > < X-Container-Object-Count: 1 > < X-Container-Bytes-Used: 29 > < Content-Length: 10 > < Content-Type: text/plain; charset=utf8 > < Date: Tue, 05 Apr 2011 10:11:01 GMT > testfile1 > * Connection #0 to host 192.168.62.63 left intact > * Closing connection #0 > [shashi at shashi samples]$ > > [shashi at shashi samples]$ curl -v -H 'X-Storage-User: test:tester3' -H 'X-Storage-Pass: testing3' http://192.168.62.63:8080/auth/v1.0* About to connect() to 192.168.62.63 port 8080 > * Trying 192.168.62.63... connected > * Connected to 192.168.62.63 (192.168.62.63) port 8080 > > GET /auth/v1.0 HTTP/1.1 > > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > > Host: 192.168.62.63:8080 > > Accept: */* > > X-Storage-User: test:tester3 > > X-Storage-Pass: testing3 > > > < HTTP/1.1 200 OK > < X-Storage-Url: http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a > < X-Storage-Token: AUTH_tk124a8a19ad7e49c5a04710716fd4f126 > < X-Auth-Token: AUTH_tk124a8a19ad7e49c5a04710716fd4f126 > < Content-Length: 112 > < Date: Tue, 05 Apr 2011 10:11:16 GMT > Connection #0 to host 192.168.62.63 left intact > * Closing connection #0 > {"storage": {"default": "local", "local": "http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a"}}[shashi at shashi samples]$ > > [shashi at shashi samples]$ curl -s -D - -H 'X-Auth-Token: AUTH_tk124a8a19ad7e49c5a04710716fd4f126' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1/testfile1 > HTTP/1.1 403 Forbidden > Content-Length: 157 > Content-Type: text/html; charset=UTF-8 > Date: Tue, 05 Apr 2011 10:11:42 GMT > > > > 403 Forbidden > > >

403 Forbidden

> Access was denied to this resource.

> > > > > [shashi at shashi samples]$ > [shashi at shashi samples]$ > > Thanks & Regards, > shashi > > > > > > On Fri, Apr 1, 2011 at 6:32 PM, Greg Holt wrote: > On Apr 1, 2011, at 1:35 AM, shashidhar v wrote: > > > In the above script, the third user is tester3 (non admin) which is not allowed to create containers ? Then what's the role of non-admin users created under swift , what operations they can perform ? > > > > Swift supports ACL or not and the containers/objects created by a admin user can be shared with non-admin user for atleast downloading the objects ? > > Non-admin users can only perform operations per container based on the container?s X-Container-Read and X-Container-Write ACLs. With an admin account you could create a container for that non-admin user and set X-Container-Read: test:tester3 and X-Container-Write: test:tester3. > > These may explain more: > > http://swift.openstack.org/overview_auth.html > http://swift.openstack.org/misc.html#module-swift.common.middleware.acl > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shashidhar.velagandula at gmail.com Tue Apr 5 14:03:48 2011 From: shashidhar.velagandula at gmail.com (shashidhar v) Date: Tue, 5 Apr 2011 19:33:48 +0530 Subject: [Openstack-operators] failed to run the auth-server deamon for SAIO setup In-Reply-To: References: <4696C6EF-36BE-4D7D-939F-FD7364A2AAB8@zeroaccess.org> <43C2F369-B701-4163-8805-EA6657742D9E@rackspace.com> Message-ID: Hi Gholt , 1) Container based ACL was working fine ,, [shashi at shashi samples]$ curl -X GET -D - -H 'X-Auth-Token:AUTH_tk124a8a19ad7e49c5a04710716fd4f126' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 HTTP/1.1 200 OK X-Container-Object-Count: 1 X-Container-Read: test:tester3 X-Container-Bytes-Used: 29 Content-Length: 10 Content-Type: text/plain; charset=utf8 Date: Tue, 05 Apr 2011 12:57:49 GMT testfile1 [shashi at shashi samples]$ 2) How to create new accounts/users using the admin "reseller" which was created using the script "recreateaccounts" of SAIO swift at test3:~/swift/trunk$ swauth-prep -K reseller Auth subsystem prep failed: 403 Forbidden swift at test3:~/swift/trunk$ swift at test3:~/swift/trunk$ swauth-add-user -U reseller:reseller -K reseller -A http://192.168.62.63:8080/auth/v1.0 reseller user1 user1Account creation failed: 400 Bad Request User creation failed: 400 Bad Request swift at test3:~/swift/trunk$ swauth-add-user -U reseller:reseller -K reseller -A http://192.168.62.63:8080/v1/AUTH_a62419e4-7841-49d1-950f-521443c8a75dreseller user1 password1 Account creation failed: 401 Unauthorized User creation failed: 401 Unauthorized swift at test3:~/swift/trunk$ 3) Is it possible to enforce the storage limit for a non admin account/user in swift , if so how to set that storage limit for a user ? How to distribute the available storage among different users ? Thanks & Regards, shashi On Tue, Apr 5, 2011 at 6:06 PM, Greg Holt wrote: > You have to use the PUT or POST command when trying to set the headers on a > container. Try adding -X POST to that curl command: > > curl -v *-X POST* -H 'X-Auth-Token: > AUTH_tk64b46c28eda84a839b7ba10cc54f3525' -H 'X-Container-Read: test:tester3' > -H 'X-Container-Write: test:tester3' > http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 > > If you GET or the HEAD the container afterwards, you should see the two > headers returned to you with the appropriate values. > > On Apr 5, 2011, at 5:32 AM, shashidhar v wrote: > > Hi Gholt, > > I tried to set the container based read and write acl to share the > container with non admin user , but it is giving error as access denied > > [shashi at shashi samples]$ curl -v -H 'X-Storage-User: test:tester' -H > 'X-Storage-Pass: testing' http://192.168.62.63:8080/auth/v1.0* About to > connect() to 192.168.62.63 port 8080 > * Trying 192.168.62.63... connected > * Connected to 192.168.62.63 (192.168.62.63) port 8080 > > GET /auth/v1.0 HTTP/1.1 > > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 > OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > > Host: 192.168.62.63:8080 > > Accept: */* > > X-Storage-User: test:tester > > X-Storage-Pass: testing > > > < HTTP/1.1 200 OK > < X-Storage-Url: > http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a > < X-Storage-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525 > < X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525 > < Content-Length: 112 > < Date: Tue, 05 Apr 2011 10:18:31 GMT > Connection #0 to host 192.168.62.63 left intact > * Closing connection #0 > {"storage": {"default": "local", "local": " > http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a > "}}[shashi at shashi samples]$ > > > [shashi at shashi samples]$ curl -X HEAD -D - -H 'X-Auth-Token: > AUTH_tk64b46c28eda84a839b7ba10cc54f3525' > http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a > HTTP/1.1 204 No Content > X-Account-Object-Count: 0 > X-Account-Bytes-Used: 0 > X-Account-Container-Count: 1 > Content-Length: 0 > Date: Tue, 05 Apr 2011 10:20:19 GMT > > [shashi at shashi samples]$ > [shashi at shashi samples]$ curl -X HEAD -D - -H 'X-Auth-Token: > AUTH_tk64b46c28eda84a839b7ba10cc54f3525' > http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 > HTTP/1.1 204 No Content > X-Container-Object-Count: 1 > X-Container-Bytes-Used: 29 > Content-Length: 0 > Date: Tue, 05 Apr 2011 10:20:40 GMT > > [shashi at shashi samples]$ > > > > Initially I have created a container named as "container1" using the admin > user "test:tester" and then trying to set read and write acl for the > container1 to share it with non-admin user .......... > > > > [shashi at shashi samples]$ curl -v -H 'X-Auth-Token: > AUTH_tk64b46c28eda84a839b7ba10cc54f3525' -H 'X-Container-Read: test:tester3' > -H 'X-Container-Write: test:tester3' > http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 > * About to connect() to 192.168.62.63 port 8080 > * Trying 192.168.62.63... connected > * Connected to 192.168.62.63 (192.168.62.63) port 8080 > > GET /v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 HTTP/1.1 > > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 > OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > > Host: 192.168.62.63:8080 > > Accept: */* > > X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525 > > X-Container-Read: test:tester3 > > X-Container-Write: test:tester3 > > > < HTTP/1.1 200 OK > < X-Container-Object-Count: 1 > < X-Container-Bytes-Used: 29 > < Content-Length: 10 > < Content-Type: text/plain; charset=utf8 > < Date: Tue, 05 Apr 2011 10:11:01 GMT > testfile1 > * Connection #0 to host 192.168.62.63 left intact > * Closing connection #0 > [shashi at shashi samples]$ > > [shashi at shashi samples]$ curl -v -H 'X-Storage-User: test:tester3' -H > 'X-Storage-Pass: testing3' http://192.168.62.63:8080/auth/v1.0* About to > connect() to 192.168.62.63 port 8080 > * Trying 192.168.62.63... connected > * Connected to 192.168.62.63 (192.168.62.63) port 8080 > > GET /auth/v1.0 HTTP/1.1 > > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 > OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > > Host: 192.168.62.63:8080 > > Accept: */* > > X-Storage-User: test:tester3 > > X-Storage-Pass: testing3 > > > < HTTP/1.1 200 OK > < X-Storage-Url: > http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a > < X-Storage-Token: AUTH_tk124a8a19ad7e49c5a04710716fd4f126 > < X-Auth-Token: AUTH_tk124a8a19ad7e49c5a04710716fd4f126 > < Content-Length: 112 > < Date: Tue, 05 Apr 2011 10:11:16 GMT > Connection #0 to host 192.168.62.63 left intact > * Closing connection #0 > {"storage": {"default": "local", "local": " > http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a > "}}[shashi at shashi samples]$ > > [shashi at shashi samples]$ curl -s -D - -H 'X-Auth-Token: > AUTH_tk124a8a19ad7e49c5a04710716fd4f126' > http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1/testfile1 > HTTP/1.1 403 Forbidden > Content-Length: 157 > Content-Type: text/html; charset=UTF-8 > Date: Tue, 05 Apr 2011 10:11:42 GMT > > > > 403 Forbidden > > >

403 Forbidden

> Access was denied to this resource.

> > > > > [shashi at shashi samples]$ > [shashi at shashi samples]$ > > Thanks & Regards, > shashi > > > > > > On Fri, Apr 1, 2011 at 6:32 PM, Greg Holt wrote: > >> On Apr 1, 2011, at 1:35 AM, shashidhar v wrote: >> >> > In the above script, the third user is tester3 (non admin) which is not >> allowed to create containers ? Then what's the role of non-admin users >> created under swift , what operations they can perform ? >> > >> > Swift supports ACL or not and the containers/objects created by a admin >> user can be shared with non-admin user for atleast downloading the objects ? >> >> Non-admin users can only perform operations per container based on the >> container?s X-Container-Read and X-Container-Write ACLs. With an admin >> account you could create a container for that non-admin user and set >> X-Container-Read: test:tester3 and X-Container-Write: test:tester3. >> >> These may explain more: >> >> http://swift.openstack.org/overview_auth.html >> http://swift.openstack.org/misc.html#module-swift.common.middleware.acl >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gholt at rackspace.com Tue Apr 5 19:48:14 2011 From: gholt at rackspace.com (Greg Holt) Date: Tue, 5 Apr 2011 14:48:14 -0500 Subject: [Openstack-operators] failed to run the auth-server deamon for SAIO setup In-Reply-To: References: <4696C6EF-36BE-4D7D-939F-FD7364A2AAB8@zeroaccess.org> <43C2F369-B701-4163-8805-EA6657742D9E@rackspace.com> Message-ID: On Apr 5, 2011, at 9:03 AM, shashidhar v wrote: > 2) How to create new accounts/users using the admin "reseller" which was created using the script "recreateaccounts" of SAIO > > swift at test3:~/swift/trunk$ swauth-add-user -U reseller:reseller -K reseller -A http://192.168.62.63:8080/auth/v1.0 reseller user1 user1 This one was closest. The -A ADMIN_URL should be -A http://192.168.62.63:8080/auth/ I often forget too, but if you run swauth-add-user with no options it has an example for a reminder. > 3) Is it possible to enforce the storage limit for a non admin account/user in swift , if so how to set that storage limit for a user ? How to distribute the available storage among different users ? Swift currently does not have quota support (limiting how much space a user can use). It's on the list, but not yet on a specific roadmap. Here at Rackspace we just make sure to mount new hard drives faster than folks can upload. :) -------------- next part -------------- An HTML attachment was scrubbed... URL: From shashidhar.velagandula at gmail.com Wed Apr 6 06:53:34 2011 From: shashidhar.velagandula at gmail.com (shashidhar v) Date: Wed, 6 Apr 2011 12:23:34 +0530 Subject: [Openstack-operators] Swift - usage of JAVA apis bindings from rackspace ?? Message-ID: Hi, I am trying to build the "rackspace-java-cloudfiles" package (JAVA apis) and run the unit tests ... but getting the errors [shashi at shashi rackspace-java-cloudfiles-1fb920d]$ cat src/test/resources/cloudfiles.properties # user properties username=tester password=testing account=test # Auth Info, including two headers that can change for different auth services #auth_url=http://test1:8080/auth/v1 auth_token_name=X-Auth-Token auth_url= http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a auth_user_header=tester auth_pass_header=testing auth_user_header=X-Storage-User auth_pass_header=X-Storage-Pass # cloudfs properties version=v1 connection_timeout=15000 [shashi at shashi rackspace-java-cloudfiles-1fb920d]$ ant test Buildfile: build.xml init: [echo] ------------------------------------------------- [echo] Building Cloudfiles [echo] ------------------------------------------------- compile: [echo] Compiling the source [jar] Building jar: /home/shashi/Desktop/rackspace-java-cloudfiles-1fb920d/dist/java-cloudfiles.jar compile-test: [echo] Compiling the test source [copy] Copying 1 file to /home/shashi/Desktop/rackspace-java-cloudfiles-1fb920d/classes [jar] Building jar: /home/shashi/Desktop/rackspace-java-cloudfiles-1fb920d/dist/java-cloudfiles-test.jar test: [junit] Running com.rackspacecloud.client.cloudfiles.FilesClientTestCase [junit] Testsuite: com.rackspacecloud.client.cloudfiles.FilesClientTestCase [junit] Tests run: 44, Failures: 42, Errors: 0, Time elapsed: 1.606 sec [junit] Tests run: 44, Failures: 42, Errors: 0, Time elapsed: 1.606 sec [junit] [junit] ------------- Standard Error ----------------- [junit] java.lang.IllegalStateException: Target host must not be null, or set in parameters. [junit] at org.apache.http.impl.client.DefaultRequestDirector.determineRoute(DefaultRequestDirector.java:651) [junit] at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:353) [junit] at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641) [junit] at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:576) [junit] at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:554) [junit] at com.rackspacecloud.client.cloudfiles.FilesClient.login(FilesClient.java:278) [junit] at com.rackspacecloud.client.cloudfiles.FilesClientTestCase.testUnicodeContainer(FilesClientTestCase.java:1401) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at java.lang.reflect.Method.invoke(Method.java:597) [junit] at junit.framework.TestCase.runTest(TestCase.java:164) [junit] at junit.framework.TestCase.runBare(TestCase.java:130) [junit] at junit.framework.TestResult$1.protect(TestResult.java:106) [junit] at junit.framework.TestResult.runProtected(TestResult.java:124) [junit] at junit.framework.TestResult.run(TestResult.java:109) [junit] at junit.framework.TestCase.run(TestCase.java:120) [junit] at junit.framework.TestSuite.runTest(TestSuite.java:230) [junit] at junit.framework.TestSuite.run(TestSuite.java:225) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:421) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask.java:1245) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:814) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1657) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:765) [junit] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) [junit] at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at java.lang.reflect.Method.invoke(Method.java:597) [junit] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105) [junit] at org.apache.tools.ant.Task.perform(Task.java:348) [junit] at org.apache.tools.ant.Target.execute(Target.java:357) [junit] at org.apache.tools.ant.Target.performTasks(Target.java:385) [junit] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329) [junit] at org.apache.tools.ant.Project.executeTarget(Project.java:1298) [junit] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) [junit] at org.apache.tools.ant.Project.executeTargets(Project.java:1181) [junit] at org.apache.tools.ant.Main.runBuild(Main.java:698) [junit] at org.apache.tools.ant.Main.startAnt(Main.java:199) [junit] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) [junit] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) [junit] java.lang.IllegalStateException: Target host must not be null, or set in parameters. [junit] at org.apache.http.impl.client.DefaultRequestDirector.determineRoute(DefaultRequestDirector.java:651) [junit] at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:353) [junit] at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641) [junit] at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:576) [junit] at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:554) [junit] at com.rackspacecloud.client.cloudfiles.FilesClient.login(FilesClient.java:278) [junit] at com.rackspacecloud.client.cloudfiles.FilesClientTestCase.testUnicode(FilesClientTestCase.java:1432) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at java.lang.reflect.Method.invoke(Method.java:597) [junit] at junit.framework.TestCase.runTest(TestCase.java:164) [junit] at junit.framework.TestCase.runBare(TestCase.java:130) [junit] at junit.framework.TestResult$1.protect(TestResult.java:106) [junit] at junit.framework.TestResult.runProtected(TestResult.java:124) [junit] at junit.framework.TestResult.run(TestResult.java:109) [junit] at junit.framework.TestCase.run(TestCase.java:120) [junit] at junit.framework.TestSuite.runTest(TestSuite.java:230) [junit] at junit.framework.TestSuite.run(TestSuite.java:225) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:421) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask.java:1245) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:814) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1657) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:765) [junit] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) [junit] at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at java.lang.reflect.Method.invoke(Method.java:597) [junit] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105) [junit] at org.apache.tools.ant.Task.perform(Task.java:348) [junit] at org.apache.tools.ant.Target.execute(Target.java:357) [junit] at org.apache.tools.ant.Target.performTasks(Target.java:385) [junit] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329) [junit] at org.apache.tools.ant.Project.executeTarget(Project.java:1298) [junit] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) [junit] at org.apache.tools.ant.Project.executeTargets(Project.java:1181) [junit] at org.apache.tools.ant.Main.runBuild(Main.java:698) [junit] at org.apache.tools.ant.Main.startAnt(Main.java:199) [junit] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) [junit] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) [junit] ------------- ---------------- --------------- [junit] Testcase: testLogin(com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] null [junit] junit.framework.AssertionFailedError [junit] at com.rackspacecloud.client.cloudfiles.FilesClientTestCase.testLogin(FilesClientTestCase.java:68) [junit] [junit] [junit] Testcase: testAccountInfo(com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] null [junit] junit.framework.AssertionFailedError [junit] at com.rackspacecloud.client.cloudfiles.FilesClientTestCase.testAccountInfo(FilesClientTestCase.java:92) [junit] [junit] [junit] Testcase: testMultipleFilesNotThere(com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] null =============== ======= ===== [junit] [junit] Testcase: testFilesObjectPath(com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] null [junit] junit.framework.AssertionFailedError [junit] at com.rackspacecloud.client.cloudfiles.FilesClientTestCase.testFilesObjectPath(FilesClientTestCase.java:1783) [junit] [junit] [junit] Testcase: testURLs(com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] null [junit] junit.framework.AssertionFailedError [junit] at com.rackspacecloud.client.cloudfiles.FilesClientTestCase.testURLs(FilesClientTestCase.java:1826) [junit] [junit] [junit] Test com.rackspacecloud.client.cloudfiles.FilesClientTestCase FAILED BUILD SUCCESSFUL Total time: 5 seconds [shashi at shashi rackspace-java-cloudfiles-1fb920d]$ I was not clear about the properties to be set for running the "unit tests" of rackspace cloud files - java apis package , kindly help me for usage of java apis w.r.t swift Thanks & Regards, shashi -------------- next part -------------- An HTML attachment was scrubbed... URL: From gholt at rackspace.com Wed Apr 6 12:38:46 2011 From: gholt at rackspace.com (Greg Holt) Date: Wed, 6 Apr 2011 07:38:46 -0500 Subject: [Openstack-operators] Swift - usage of JAVA apis bindings from rackspace ?? In-Reply-To: References: Message-ID: <9F3F24EB-446F-444C-80E2-834384F11931@rackspace.com> On Apr 6, 2011, at 1:53 AM, shashidhar v wrote: > I am trying to build the "rackspace-java-cloudfiles" package (JAVA apis) and run the unit tests ... but getting the errors Ah, you're outside my knowledge area as I haven't used those bindings myself for quite a while, and then only briefly, and then it was with Rackspace Cloud Files not Swift. If I get some time I'll see if I can figure it out and get back to you. From shashidhar.velagandula at gmail.com Wed Apr 6 14:06:06 2011 From: shashidhar.velagandula at gmail.com (shashidhar v) Date: Wed, 6 Apr 2011 19:36:06 +0530 Subject: [Openstack-operators] talking to swift with cyberduck - failed to build the cyberduck source ?? Message-ID: Hi , I was trying to build the cyberduck to interface with the swift , I followed the steps from doc http://swift.openstack.org/howto_cyberduck.html upto step 5 I did as per the doc ,,,, but step 6 failed to build it ... step 4 : I have used the auth_url as http://192.168.62.63:8080/auth/v1.0in the file " lib/cloudfiles.properties" step 5: updated the "source/ch/cyberduck/core/Protocol.java" file public boolean isHostnameConfigurable() { return true; } step 6: trying to build the cyberduck ,,,, since I am using windows , I used the command "ant dll" C:\Users\Admin\Desktop\shashi\cyberduck-src-3.8.1\3.8.1>ant dll Buildfile: C:\Users\Admin\Desktop\shashi\cyberduck-src-3.8.1\3.8.1\build.xml [taskdef] Could not load definitions from resource net/sf/antcontrib/antcontri b.properties. It could not be found. revision: [echo] Calculating revision... [echo] _REVISION_=exported [echo] Build number 11 version: BUILD FAILED C:\Users\Admin\Desktop\shashi\cyberduck-src-3.8.1\3.8.1\build-windows.xml:60: Pr oblem: failed to create task or type propertyregex Cause: The name is undefined. Action: Check the spelling. Action: Check that any custom tasks/types have been declared. Action: Check that any / declarations have taken place. Total time: 0 seconds Kindly help me to resolve the error Thanks & Regards, shashi -------------- next part -------------- An HTML attachment was scrubbed... URL: From btorch-os at zeroaccess.org Mon Apr 11 15:28:13 2011 From: btorch-os at zeroaccess.org (Marcelo Martins) Date: Mon, 11 Apr 2011 10:28:13 -0500 Subject: [Openstack-operators] Swift - usage of JAVA apis bindings from rackspace ?? In-Reply-To: References: Message-ID: Shashidhar, PS -> had to remove your original post in the email due to a 40KB message body limitation on the list. I'm don't think the java-cloudfiles API currently works with openstack- swift authentication system. I tried to use the latest version 1.8.1 and also 1.8.0 but was encountering other problems that was prohibiting me from even reaching my openstack-swift SAIO system. So I decided to give it a try on an older version I already had installed (1.5.3 ... I know it's old) ... Problem #1 : Using SSL with java sucks .. I didn't feel like troubleshooting java keytool, so I changed my SAIO setup to no longer use SSL in my proxy-server. Problem #2: Had to hack two files in order to make authentication work FILE #1 = src/main/java/com/rackspacecloud/client/cloudfiles/ FilesClient.java -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 377-openstack/src/main/java/com/rackspacecloud/client/cloudfiles/ FilesClient.java --- rackspace-java-cloudfiles-0ce9377/src/main/java/com/rackspacecloud/ client/cloudfiles/FilesClient.java 2010-02-08 17:46:42.000000000 -0600 +++ rackspace-java-cloudfiles-0ce9377-openstack/src/main/java/com/ rackspacecloud/client/cloudfiles/FilesClient.java 2011-04-09 21:36:32.110095891 -0500 @@ -115,8 +115,10 @@ this.username = username; this.password = password; this.account = account; + if (account != null && account.length() > 0) { - this.authenticationURL = FilesUtil.getProperty("auth_url")+VERSION+"/"+account +FilesUtil.getProperty("auth_url_post"); + this.authenticationURL = FilesUtil.getProperty("auth_url"); + this.username = account+":"+username; } else { this.authenticationURL = FilesUtil.getProperty("auth_url"); @@ -192,7 +194,7 @@ { this.account = account; if (account != null && account.length() > 0) { - this.authenticationURL = FilesUtil.getProperty("auth_url")+VERSION+"/"+account +FilesUtil.getProperty("auth_url_post"); + this.authenticationURL = FilesUtil.getProperty("auth_url"); } else { this.authenticationURL = FilesUtil.getProperty("auth_url"); -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- FILE #2 = src/main/java/com/rackspacecloud/client/cloudfiles/ FilesResponse.java -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- e9377-openstack/src/main/java/com/rackspacecloud/client/cloudfiles/ FilesResponse.java --- rackspace-java-cloudfiles-0ce9377/src/main/java/com/rackspacecloud/ client/cloudfiles/FilesResponse.java 2010-02-08 17:46:42.000000000 -0600 +++ rackspace-java-cloudfiles-0ce9377-openstack/src/main/java/com/ rackspacecloud/client/cloudfiles/FilesResponse.java 2011-04-09 20:56:22.826095729 -0500 @@ -51,7 +51,8 @@ if (getStatusCode() == HttpStatus.SC_UNAUTHORIZED ) return false; - if (getStatusCode() == HttpStatus.SC_NO_CONTENT) + /* Marcelo if (getStatusCode() == HttpStatus.SC_NO_CONTENT) */ + if (getStatusCode() == HttpStatus.SC_OK) return true; return false; -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Once I was done with modifying the files I compiled it with "ant compile" Then I created my "cloudfiles.properties" file ---------------------------------------------------------------------------------------------- version=v1 connection_timeout=5000 # Auth info auth_url=http://MY_IP_ADDRR:8080/auth/v1.0 auth_token_name=X-Auth-Token #auth_user_header=X-Auth-User #auth_pass_header=X-Auth-Key ---------------------------------------------------------------------------------------------- Then I tested the java api using the run_cli.sh btorch at stone:~/src/rackspace-java-cloudfiles-0ce9377-openstack$ bash run_cli.sh Username: marcelo Password: XXXXXXXXXX Account (return if using Mosso directly): external Logged in! Type 'help' for assistance external: get The account has 3 containers glance images test external: head Account information: Number of Containers: 3 Total Account Size: 1938161664 external: head glance Information for glance Object Count: 2 Total Size: 1,938,161,664 bytes .... Then I ran the test unit... I also expected any CDN test units to fail since openstack-swift does not have CDN: btorch at stone:~/src/rackspace-java-cloudfiles-0ce9377-openstack$ ant test Buildfile: build.xml init: [echo] ------------------------------------------------- [echo] Building Cloudfiles [echo] ------------------------------------------------- compile: [echo] Compiling the source compile-test: [echo] Compiling the test source [javac] Compiling 2 source files to /home/btorch/src/rackspace- java-cloudfiles-0ce9377-openstack/classes [copy] Copying 2 files to /home/btorch/src/rackspace-java- cloudfiles-0ce9377-openstack/classes [jar] Building jar: /home/btorch/src/rackspace-java- cloudfiles-0ce9377-openstack/dist/java-cloudfiles-test.jar test: [junit] Running com.rackspacecloud.client.cloudfiles.FilesClientTestCase [junit] Testsuite: com.rackspacecloud.client.cloudfiles.FilesClientTestCase [junit] Tests run: 38, Failures: 8, Errors: 0, Time elapsed: 30.824 sec [junit] Tests run: 38, Failures: 8, Errors: 0, Time elapsed: 30.824 sec [junit] [junit] Testcase: testConstructor (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] expected:<...> but was: [junit] junit.framework.ComparisonFailure: expected:<...> but was: [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase.testConstructor(FilesClientTestCase.java:49) [junit] [junit] [junit] Testcase: testNoArgConstructor (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] expected:<...> but was: [junit] junit.framework.ComparisonFailure: expected:<...> but was: [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase.testNoArgConstructor(FilesClientTestCase.java:59) [junit] [junit] [junit] [junit] Testcase: testCDNContainerList (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase.testCDNContainerList(FilesClientTestCase.java:1242) [junit] [junit] [junit] Testcase: testCDNContainerListLimitMarker (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase .testCDNContainerListLimitMarker(FilesClientTestCase.java:1268) [junit] [junit] [junit] Testcase: testCDNContainerFullListing (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase .testCDNContainerFullListing(FilesClientTestCase.java:1293) [junit] [junit] [junit] Testcase: testCDNContainerFullListingAll (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase .testCDNContainerFullListingAll(FilesClientTestCase.java:1307) [junit] [junit] [junit] Testcase: testCDNApi (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles.FilesClientTestCase.testCDNApi(FilesClientTestCase.java: 1366) [junit] [junit] [junit] Testcase: testURLs (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] null [junit] junit.framework.AssertionFailedError [junit] at com .rackspacecloud .client .cloudfiles.FilesClientTestCase.testURLs(FilesClientTestCase.java:1526) [junit] [junit] [junit] Test com.rackspacecloud.client.cloudfiles.FilesClientTestCase FAILED BUILD SUCCESSFUL Total time: 34 seconds ----- I'm not sure why the newer versions of the java-cloudfiles API were failing, perhaps I was doing something wrong! I hope this helps a bit or perhaps sends you to the right track. If I have an update about java-cloudfiles and openstack-swift compatibility I'll let you know. Marcelo Martins Openstack-swift btorch-os at zeroaccess.org ?Knowledge is the wings on which our aspirations take flight and soar. When it comes to surfing and life if you know what to do you can do it. If you desire anything become educated about it and succeed. ? > > Thanks & Regards, > shashi > _______________________________________________ > Openstack-operators mailing list > Openstack-operators at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack- > operators -------------- next part -------------- An HTML attachment was scrubbed... URL: From jinzishuai at gmail.com Sun Apr 24 20:23:31 2011 From: jinzishuai at gmail.com (Shi Jin) Date: Sun, 24 Apr 2011 14:23:31 -0600 Subject: [Openstack-operators] nova-objectstore not working (http 500 error) on RHEL-6 Message-ID: Hi there, I am having trouble connecting to nova-objectstore running on RHEL-6, which runs perfectly fine on a Ubuntu installation. I got the following using S3_Curl * About to connect() to 192.168.2.4 port 3333 (#0) * Trying 192.168.2.4... connected * Connected to 192.168.2.4 (192.168.2.4) port 3333 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/ 3.12.6.2 zlib/1.2.3 libidn/1.18 libssh2/1.2.2 > Host: 192.168.2.4:3333 > Accept: */* > Date: Sun, 24 Apr 2011 20:11:47 +0000 > Authorization: AWS 5ffcff0a-f879-41b7-b4c0-5f5f9e26856b:IRT:6/nldG738bkYk3bpKZt42hKFRr8= > < HTTP/1.1 500 Internal Server Error < Content-Type: text/plain < Content-Length: 1106 < Date: Sun, 24 Apr 2011 20:11:47 GMT < Connection: close < Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/eventlet/wsgi.py", line 336, in handle_one_response result = self.application(self.environ, start_response) File "/usr/lib/python2.6/site-packages/webob/dec.py", line 159, in __call__ return resp(environ, start_response) File "/usr/lib/python2.6/site-packages/routes/middleware.py", line 131, in __call__ response = self.app(environ, start_response) File "/usr/lib/python2.6/site-packages/webob/dec.py", line 159, in __call__ return resp(environ, start_response) File "/usr/lib/python2.6/site-packages/nova/objectstore/s3server.py", line 72, in controller=lambda *a, **kw: RootHandler(self)(*a, **kw)) File "/usr/lib/python2.6/site-packages/webob/dec.py", line 147, in __call__ resp = self.call_func(req, *args, **self.kwargs) File "/usr/lib/python2.6/site-packages/webob/dec.py", line 208, in call_func return self.func(req, *args, **kwargs) File "/usr/lib/python2.6/site-packages/nova/objectstore/s3server.py", line 128, in __call__ del params['action'] KeyError: 'action' * Closing connection #0 I cannot find anything useful from the log file either. [root at openstack-controller nova]# cat nova-objectstore.log 2011-04-24 14:09:20,197 DEBUG routes.middleware [-] Initialized with method overriding = True, and path info altering = True from (pid=26724) __init__ /usr/lib/python2.6/site-packages/routes/middleware.py:41 2011-04-24 14:09:20,197 AUDIT nova [-] Starting /usr/bin/nova-objectstore on 192.168.2.4:3333 2011-04-24 14:11:35,121 DEBUG routes.middleware [-] Matched GET / from (pid=26724) __call__ /usr/lib/python2.6/site-packages/routes/middleware.py:100 2011-04-24 14:11:35,121 DEBUG routes.middleware [-] Route path: '/', defaults: {'controller': at 0x127fc08>} from (pid=26724) __call__ /usr/lib/python2.6/site-packages/routes/middleware.py:102 2011-04-24 14:11:35,122 DEBUG routes.middleware [-] Match dict: {'controller': at 0x127fc08>} from (pid=26724) __call__ /usr/lib/python2.6/site-packages/routes/middleware.py:103 2011-04-24 14:11:47,175 DEBUG routes.middleware [-] Matched GET / from (pid=26724) __call__ /usr/lib/python2.6/site-packages/routes/middleware.py:100 2011-04-24 14:11:47,175 DEBUG routes.middleware [-] Route path: '/', defaults: {'controller': at 0x127fc08>} from (pid=26724) __call__ /usr/lib/python2.6/site-packages/routes/middleware.py:102 2011-04-24 14:11:47,175 DEBUG routes.middleware [-] Match dict: {'controller': at 0x127fc08>} from (pid=26724) __call__ /usr/lib/python2.6/site-packages/routes/middleware.py:103 BTW, The service of nova-objectstore runs fine and listens to the 3333 port. Has anyone had any experience with the rpm package for RHEL-6 installed following this documentation: http://docs.openstack.org/trunk/openstack-compute-admin/content/installing-openstack-compute-on-rhel6.html ? Thanks a lot. Shi -- Shi Jin, Ph.D. -------------- next part -------------- An HTML attachment was scrubbed... URL: From shashidhar.velagandula at gmail.com Tue Apr 26 13:22:16 2011 From: shashidhar.velagandula at gmail.com (shashidhar v) Date: Tue, 26 Apr 2011 18:52:16 +0530 Subject: [Openstack-operators] cyberduck interface to swift ?? Message-ID: Hi, I have deployed swift-1.4 dev(SAIO) service running on a test node , able to create the accounts and do upload/download of files using the "st" tool by following doc of SAIO Test node swift service is enabled with SSL using self signed certs. and uses swauth authentication And, then I have installed the Cyberduck-Installer-4.0.2.exe on windows xp and windows vista machines , but when I open connection to swift service running on test node it throws error as login failed swift at test3:~$ swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0 -U system:root -K testpass stat Account: AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f Containers: 0 Objects: 0 Bytes: 0 Accept-Ranges: bytes swift at test3:~$ swift at test3:~$ swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0 -U system:root -K testpass list swift at test3:~$ swift at test3:~$ curl -k -v -H 'X-Storage-User: system:root' -H 'X-Storage-Pass: testpass' https://192.168.62.63:8080/auth/v1.0 * About to connect() to 192.168.62.63 port 8080 (#0) * Trying 192.168.62.63... connected * Connected to 192.168.62.63 (192.168.62.63) port 8080 (#0) * successfully set certificate verify locations: * CAfile: none CApath: /etc/ssl/certs * SSLv3, TLS handshake, Client hello (1): * SSLv3, TLS handshake, Server hello (2): * SSLv3, TLS handshake, CERT (11): * SSLv3, TLS handshake, Server finished (14): * SSLv3, TLS handshake, Client key exchange (16): * SSLv3, TLS change cipher, Client hello (1): * SSLv3, TLS handshake, Finished (20): * SSLv3, TLS change cipher, Client hello (1): * SSLv3, TLS handshake, Finished (20): * SSL connection using AES256-SHA * Server certificate: * subject: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in * start date: 2011-04-25 05:45:12 GMT * expire date: 2011-05-25 05:45:12 GMT * common name: swift (does not match '192.168.62.63') * issuer: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in * SSL certificate verify result: self signed certificate (18), continuing anyway. > GET /auth/v1.0 HTTP/1.1 > User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15 > Host: 192.168.62.63:8080 > Accept: */* > X-Storage-User: system:root > X-Storage-Pass: testpass > < HTTP/1.1 200 OK < X-Storage-Url: https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f < X-Storage-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 < X-Auth-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 < Content-Length: 117 < Date: Tue, 26 Apr 2011 12:48:39 GMT < * Connection #0 to host 192.168.62.63 left intact * Closing connection #0 * SSLv3, TLS alert, Client hello (1): {"storage": {"default": "local", "local": " https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f "}}swift at test3:~$ swift at test3:~$ Using st tool I am able upload/download the files but using cyberduck interface , login itself is failed Kindly help me to resolve this login error , any doc. which describes about cyberduck interface to swift will be helpful I have checked the related doc. present under http://swift.openstack.org/howto_cyberduck.html but it describes about source build of cyberduck not the binary version Is it possible to specify "http" protocol instead of "https" using cyerduck to contact swift service ? kindly help me Thanks & Regards, shashi -------------- next part -------------- An HTML attachment was scrubbed... URL: From jinzishuai at gmail.com Tue Apr 26 18:17:54 2011 From: jinzishuai at gmail.com (Shi Jin) Date: Tue, 26 Apr 2011 12:17:54 -0600 Subject: [Openstack-operators] cyberduck interface to swift ?? In-Reply-To: References: Message-ID: I was able to login to swift using https, just have to confirm continue when cyberduck prompts about the SSL self signed certificate. I am also curious about having cyberduck to connect to S3 with plain http instead of https. Shi On Tue, Apr 26, 2011 at 7:22 AM, shashidhar v < shashidhar.velagandula at gmail.com> wrote: > Hi, > > I have deployed swift-1.4 dev(SAIO) service running on a test node , able > to create the accounts and do upload/download of files using the "st" tool > by following doc of SAIO > Test node swift service is enabled with SSL using self signed certs. and > uses swauth authentication > > And, then I have installed the Cyberduck-Installer-4.0.2.exe on windows xp > and windows vista machines , but when I open connection to swift service > running on test node it throws error as login failed > > swift at test3:~$ swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0-U system:root -K testpass stat > Account: AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f > Containers: 0 > Objects: 0 > Bytes: 0 > Accept-Ranges: bytes > swift at test3:~$ > swift at test3:~$ > swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0 -U system:root > -K testpass list > swift at test3:~$ > swift at test3:~$ curl -k -v -H 'X-Storage-User: system:root' -H > 'X-Storage-Pass: testpass' https://192.168.62.63:8080/auth/v1.0 > * About to connect() to 192.168.62.63 port 8080 (#0) > * Trying 192.168.62.63... connected > * Connected to 192.168.62.63 (192.168.62.63) port 8080 (#0) > * successfully set certificate verify locations: > * CAfile: none > CApath: /etc/ssl/certs > * SSLv3, TLS handshake, Client hello (1): > * SSLv3, TLS handshake, Server hello (2): > * SSLv3, TLS handshake, CERT (11): > * SSLv3, TLS handshake, Server finished (14): > * SSLv3, TLS handshake, Client key exchange (16): > * SSLv3, TLS change cipher, Client hello (1): > * SSLv3, TLS handshake, Finished (20): > * SSLv3, TLS change cipher, Client hello (1): > * SSLv3, TLS handshake, Finished (20): > * SSL connection using AES256-SHA > * Server certificate: > * subject: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; > CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in > * start date: 2011-04-25 05:45:12 GMT > * expire date: 2011-05-25 05:45:12 GMT > * common name: swift (does not match '192.168.62.63') > * issuer: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; > CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in > * SSL certificate verify result: self signed certificate (18), > continuing anyway. > > GET /auth/v1.0 HTTP/1.1 > > User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k > zlib/1.2.3.3 libidn/1.15 > > Host: 192.168.62.63:8080 > > Accept: */* > > X-Storage-User: system:root > > X-Storage-Pass: testpass > > > < HTTP/1.1 200 OK > < X-Storage-Url: > https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f > < X-Storage-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 > < X-Auth-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 > < Content-Length: 117 > < Date: Tue, 26 Apr 2011 12:48:39 GMT > < > * Connection #0 to host 192.168.62.63 left intact > * Closing connection #0 > * SSLv3, TLS alert, Client hello (1): > {"storage": {"default": "local", "local": " > https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f > "}}swift at test3:~$ > swift at test3:~$ > > > Using st tool I am able upload/download the files but using cyberduck > interface , login itself is failed > > Kindly help me to resolve this login error , any doc. which describes > about cyberduck interface to swift will be helpful > > I have checked the related doc. present under > http://swift.openstack.org/howto_cyberduck.html but it describes about > source build of cyberduck not the binary version > > Is it possible to specify "http" protocol instead of "https" using > cyerduck to contact swift service ? > kindly help me > > Thanks & Regards, > shashi > > > _______________________________________________ > Openstack-operators mailing list > Openstack-operators at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > -- Shi Jin, Ph.D. -------------- next part -------------- An HTML attachment was scrubbed... URL: From btorch-os at zeroaccess.org Sun Apr 10 02:55:42 2011 From: btorch-os at zeroaccess.org (Marcelo Martins) Date: Sun, 10 Apr 2011 02:55:42 -0000 Subject: [Openstack-operators] *****SPAM***** Re: Swift - usage of JAVA apis bindings from rackspace ?? In-Reply-To: References: Message-ID: <078F41C1-0386-40CE-B75A-F846C9D8CB69@zeroaccess.org> Shashidhar, I'm don't think the java-cloudfiles API currently works with openstack- swift authentication system. I tried to use the latest version 1.8.1 and also 1.8.0 but was encountering other problems that was prohibiting me from even reaching my openstack-swift SAIO system. So I decided to give it a try on an older version I already had installed (1.5.3 ... I know it's old) ... Problem #1 : Using SSL with java sucks .. I didn't feel like troubleshooting java keytool, so I changed my SAIO setup to no longer use SSL in my proxy-server. Problem #2: Had to hack two files in order to make authentication work FILE #1 = src/main/java/com/rackspacecloud/client/cloudfiles/ FilesClient.java -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 377-openstack/src/main/java/com/rackspacecloud/client/cloudfiles/ FilesClient.java --- rackspace-java-cloudfiles-0ce9377/src/main/java/com/rackspacecloud/ client/cloudfiles/FilesClient.java 2010-02-08 17:46:42.000000000 -0600 +++ rackspace-java-cloudfiles-0ce9377-openstack/src/main/java/com/ rackspacecloud/client/cloudfiles/FilesClient.java 2011-04-09 21:36:32.110095891 -0500 @@ -115,8 +115,10 @@ this.username = username; this.password = password; this.account = account; + if (account != null && account.length() > 0) { - this.authenticationURL = FilesUtil.getProperty("auth_url")+VERSION+"/"+account +FilesUtil.getProperty("auth_url_post"); + this.authenticationURL = FilesUtil.getProperty("auth_url"); + this.username = account+":"+username; } else { this.authenticationURL = FilesUtil.getProperty("auth_url"); @@ -192,7 +194,7 @@ { this.account = account; if (account != null && account.length() > 0) { - this.authenticationURL = FilesUtil.getProperty("auth_url")+VERSION+"/"+account +FilesUtil.getProperty("auth_url_post"); + this.authenticationURL = FilesUtil.getProperty("auth_url"); } else { this.authenticationURL = FilesUtil.getProperty("auth_url"); -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- FILE #2 = src/main/java/com/rackspacecloud/client/cloudfiles/ FilesResponse.java -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- e9377-openstack/src/main/java/com/rackspacecloud/client/cloudfiles/ FilesResponse.java --- rackspace-java-cloudfiles-0ce9377/src/main/java/com/rackspacecloud/ client/cloudfiles/FilesResponse.java 2010-02-08 17:46:42.000000000 -0600 +++ rackspace-java-cloudfiles-0ce9377-openstack/src/main/java/com/ rackspacecloud/client/cloudfiles/FilesResponse.java 2011-04-09 20:56:22.826095729 -0500 @@ -51,7 +51,8 @@ if (getStatusCode() == HttpStatus.SC_UNAUTHORIZED ) return false; - if (getStatusCode() == HttpStatus.SC_NO_CONTENT) + /* Marcelo if (getStatusCode() == HttpStatus.SC_NO_CONTENT) */ + if (getStatusCode() == HttpStatus.SC_OK) return true; return false; -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Once I was done with modifying the files I compiled it with "ant compile" Then I created my "cloudfiles.properties" file ---------------------------------------------------------------------------------------------- version=v1 connection_timeout=5000 # Auth info auth_url=http://MY_IP_ADDRR:8080/auth/v1.0 auth_token_name=X-Auth-Token #auth_user_header=X-Auth-User #auth_pass_header=X-Auth-Key ---------------------------------------------------------------------------------------------- Then I tested the java api using the run_cli.sh btorch at stone:~/src/rackspace-java-cloudfiles-0ce9377-openstack$ bash run_cli.sh Username: marcelo Password: XXXXXXXXXX Account (return if using Mosso directly): external Logged in! Type 'help' for assistance external: get The account has 3 containers glance images test external: head Account information: Number of Containers: 3 Total Account Size: 1938161664 external: head glance Information for glance Object Count: 2 Total Size: 1,938,161,664 bytes .... Then I ran the test unit... I also expected any CDN test units to fail since openstack-swift does not have CDN: btorch at stone:~/src/rackspace-java-cloudfiles-0ce9377-openstack$ ant test Buildfile: build.xml init: [echo] ------------------------------------------------- [echo] Building Cloudfiles [echo] ------------------------------------------------- compile: [echo] Compiling the source compile-test: [echo] Compiling the test source [javac] Compiling 2 source files to /home/btorch/src/rackspace- java-cloudfiles-0ce9377-openstack/classes [copy] Copying 2 files to /home/btorch/src/rackspace-java- cloudfiles-0ce9377-openstack/classes [jar] Building jar: /home/btorch/src/rackspace-java- cloudfiles-0ce9377-openstack/dist/java-cloudfiles-test.jar test: [junit] Running com.rackspacecloud.client.cloudfiles.FilesClientTestCase [junit] Testsuite: com.rackspacecloud.client.cloudfiles.FilesClientTestCase [junit] Tests run: 38, Failures: 8, Errors: 0, Time elapsed: 30.824 sec [junit] Tests run: 38, Failures: 8, Errors: 0, Time elapsed: 30.824 sec [junit] [junit] Testcase: testConstructor (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] expected:<...> but was: [junit] junit.framework.ComparisonFailure: expected:<...> but was: [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase.testConstructor(FilesClientTestCase.java:49) [junit] [junit] [junit] Testcase: testNoArgConstructor (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] expected:<...> but was: [junit] junit.framework.ComparisonFailure: expected:<...> but was: [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase.testNoArgConstructor(FilesClientTestCase.java:59) [junit] [junit] [junit] [junit] Testcase: testCDNContainerList (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase.testCDNContainerList(FilesClientTestCase.java:1242) [junit] [junit] [junit] Testcase: testCDNContainerListLimitMarker (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase .testCDNContainerListLimitMarker(FilesClientTestCase.java:1268) [junit] [junit] [junit] Testcase: testCDNContainerFullListing (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase .testCDNContainerFullListing(FilesClientTestCase.java:1293) [junit] [junit] [junit] Testcase: testCDNContainerFullListingAll (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase .testCDNContainerFullListingAll(FilesClientTestCase.java:1307) [junit] [junit] [junit] Testcase: testCDNApi (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles.FilesClientTestCase.testCDNApi(FilesClientTestCase.java: 1366) [junit] [junit] [junit] Testcase: testURLs (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] null [junit] junit.framework.AssertionFailedError [junit] at com .rackspacecloud .client .cloudfiles.FilesClientTestCase.testURLs(FilesClientTestCase.java:1526) [junit] [junit] [junit] Test com.rackspacecloud.client.cloudfiles.FilesClientTestCase FAILED BUILD SUCCESSFUL Total time: 34 seconds ----- btorch at stone:~/src/rackspace-java-cloudfiles-0ce9377-openstack$ ant test-report Buildfile: build.xml init: [echo] ------------------------------------------------- [echo] Building Cloudfiles [echo] ------------------------------------------------- compile: [echo] Compiling the source [jar] Building jar: /home/btorch/src/rackspace-java- cloudfiles-0ce9377-openstack/dist/java-cloudfiles.jar compile-test: [echo] Compiling the test source test-report: [mkdir] Created dir: /home/btorch/src/rackspace-java- cloudfiles-0ce9377-openstack/testreport [junit] Test com.rackspacecloud.client.cloudfiles.FilesClientTestCase FAILED [junitreport] Processing /home/btorch/src/rackspace-java- cloudfiles-0ce9377-openstack/testreport/TESTS-TestSuites.xml to /tmp/ null971541946 [junitreport] Loading stylesheet jar:file:/usr/share/ant/lib/ant- junit.jar!/org/apache/tools/ant/taskdefs/optional/junit/xsl/junit- frames.xsl [junitreport] Transform time: 1172ms [junitreport] Deleting: /tmp/null971541946 BUILD SUCCESSFUL Total time: 32 seconds I'm not sure why the newer versions of the java-cloudfiles API were failing, perhaps I was doing something wrong! I hope this helps a bit or perhaps sends you to the right track. If I have an update about java-cloudfiles and openstack-swift compatibility I'll let you know. - Marcelo ?Knowledge is the wings on which our aspirations take flight and soar. When it comes to surfing and life if you know what to do you can do it. If you desire anything become educated about it and succeed. ? On Apr 6, 2011, at 1:53 AM, shashidhar v wrote: > > Hi, > > I am trying to build the "rackspace-java-cloudfiles" package (JAVA > apis) and run the unit tests ... but getting the errors > > > > [shashi at shashi rackspace-java-cloudfiles-1fb920d]$ cat src/test/ > resources/cloudfiles.properties > > # user properties > username=tester > password=testing > account=test > > # Auth Info, including two headers that can change for different > auth services > #auth_url=http://test1:8080/auth/v1 > > auth_token_name=X-Auth-Token > auth_url=http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a > auth_user_header=tester > auth_pass_header=testing > auth_user_header=X-Storage-User > auth_pass_header=X-Storage-Pass > > # cloudfs properties > version=v1 > connection_timeout=15000 > > > > > > > [shashi at shashi rackspace-java-cloudfiles-1fb920d]$ ant test > Buildfile: build.xml > > init: > [echo] ------------------------------------------------- > [echo] Building Cloudfiles > [echo] ------------------------------------------------- > > compile: > [echo] Compiling the source > [jar] Building jar: /home/shashi/Desktop/rackspace-java- > cloudfiles-1fb920d/dist/java-cloudfiles.jar > > compile-test: > [echo] Compiling the test source > [copy] Copying 1 file to /home/shashi/Desktop/rackspace-java- > cloudfiles-1fb920d/classes > [jar] Building jar: /home/shashi/Desktop/rackspace-java- > cloudfiles-1fb920d/dist/java-cloudfiles-test.jar > > test: > [junit] Running > com.rackspacecloud.client.cloudfiles.FilesClientTestCase > [junit] Testsuite: > com.rackspacecloud.client.cloudfiles.FilesClientTestCase > [junit] Tests run: 44, Failures: 42, Errors: 0, Time elapsed: > 1.606 sec > [junit] Tests run: 44, Failures: 42, Errors: 0, Time elapsed: > 1.606 sec > [junit] > [junit] ------------- Standard Error ----------------- > [junit] java.lang.IllegalStateException: Target host must not be > null, or set in parameters. > [junit] at > org > .apache > .http > .impl > .client > .DefaultRequestDirector.determineRoute(DefaultRequestDirector.java: > 651) > [junit] at > org > .apache > .http > .impl > .client.DefaultRequestDirector.execute(DefaultRequestDirector.java: > 353) > [junit] at > org > .apache > .http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java: > 641) > [junit] at > org > .apache > .http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java: > 576) > [junit] at > org > .apache > .http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java: > 554) > [junit] at > com > .rackspacecloud.client.cloudfiles.FilesClient.login(FilesClient.java: > 278) > [junit] at > com > .rackspacecloud > .client > .cloudfiles > .FilesClientTestCase.testUnicodeContainer(FilesClientTestCase.java: > 1401) > [junit] at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [junit] at > sun > .reflect > .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [junit] at > sun > .reflect > .DelegatingMethodAccessorImpl > .invoke(DelegatingMethodAccessorImpl.java:25) > [junit] at java.lang.reflect.Method.invoke(Method.java:597) > [junit] at junit.framework.TestCase.runTest(TestCase.java:164) > [junit] at junit.framework.TestCase.runBare(TestCase.java:130) > [junit] at junit.framework.TestResult > $1.protect(TestResult.java:106) > [junit] at > junit.framework.TestResult.runProtected(TestResult.java:124) > [junit] at junit.framework.TestResult.run(TestResult.java:109) > [junit] at junit.framework.TestCase.run(TestCase.java:120) > [junit] at junit.framework.TestSuite.runTest(TestSuite.java: > 230) > [junit] at junit.framework.TestSuite.run(TestSuite.java:225) > [junit] at > org > .apache > .tools > .ant > .taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:421) > [junit] at > org > .apache > .tools > .ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask.java: > 1245) > [junit] at > org > .apache > .tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java: > 814) > [junit] at > org > .apache > .tools > .ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java: > 1657) > [junit] at > org > .apache > .tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java: > 765) > [junit] at > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) > [junit] at > sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > [junit] at > sun > .reflect > .DelegatingMethodAccessorImpl > .invoke(DelegatingMethodAccessorImpl.java:25) > [junit] at java.lang.reflect.Method.invoke(Method.java:597) > [junit] at > org > .apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java: > 105) > [junit] at org.apache.tools.ant.Task.perform(Task.java:348) > [junit] at org.apache.tools.ant.Target.execute(Target.java: > 357) > [junit] at > org.apache.tools.ant.Target.performTasks(Target.java:385) > [junit] at > org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329) > [junit] at > org.apache.tools.ant.Project.executeTarget(Project.java:1298) > [junit] at > org > .apache > .tools > .ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) > [junit] at > org.apache.tools.ant.Project.executeTargets(Project.java:1181) > [junit] at org.apache.tools.ant.Main.runBuild(Main.java:698) > [junit] at org.apache.tools.ant.Main.startAnt(Main.java:199) > [junit] at > org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) > [junit] at > org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) > [junit] java.lang.IllegalStateException: Target host must not be > null, or set in parameters. > [junit] at > org > .apache > .http > .impl > .client > .DefaultRequestDirector.determineRoute(DefaultRequestDirector.java: > 651) > [junit] at > org > .apache > .http > .impl > .client.DefaultRequestDirector.execute(DefaultRequestDirector.java: > 353) > [junit] at > org > .apache > .http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java: > 641) > [junit] at > org > .apache > .http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java: > 576) > [junit] at > org > .apache > .http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java: > 554) > [junit] at > com > .rackspacecloud.client.cloudfiles.FilesClient.login(FilesClient.java: > 278) > [junit] at > com > .rackspacecloud > .client > .cloudfiles.FilesClientTestCase.testUnicode(FilesClientTestCase.java: > 1432) > [junit] at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [junit] at > sun > .reflect > .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [junit] at > sun > .reflect > .DelegatingMethodAccessorImpl > .invoke(DelegatingMethodAccessorImpl.java:25) > [junit] at java.lang.reflect.Method.invoke(Method.java:597) > [junit] at junit.framework.TestCase.runTest(TestCase.java:164) > [junit] at junit.framework.TestCase.runBare(TestCase.java:130) > [junit] at junit.framework.TestResult > $1.protect(TestResult.java:106) > [junit] at > junit.framework.TestResult.runProtected(TestResult.java:124) > [junit] at junit.framework.TestResult.run(TestResult.java:109) > [junit] at junit.framework.TestCase.run(TestCase.java:120) > [junit] at junit.framework.TestSuite.runTest(TestSuite.java: > 230) > [junit] at junit.framework.TestSuite.run(TestSuite.java:225) > [junit] at > org > .apache > .tools > .ant > .taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:421) > [junit] at > org > .apache > .tools > .ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask.java: > 1245) > [junit] at > org > .apache > .tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java: > 814) > [junit] at > org > .apache > .tools > .ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java: > 1657) > [junit] at > org > .apache > .tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java: > 765) > [junit] at > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) > [junit] at > sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > [junit] at > sun > .reflect > .DelegatingMethodAccessorImpl > .invoke(DelegatingMethodAccessorImpl.java:25) > [junit] at java.lang.reflect.Method.invoke(Method.java:597) > [junit] at > org > .apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java: > 105) > [junit] at org.apache.tools.ant.Task.perform(Task.java:348) > [junit] at org.apache.tools.ant.Target.execute(Target.java: > 357) > [junit] at > org.apache.tools.ant.Target.performTasks(Target.java:385) > [junit] at > org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329) > [junit] at > org.apache.tools.ant.Project.executeTarget(Project.java:1298) > [junit] at > org > .apache > .tools > .ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) > [junit] at > org.apache.tools.ant.Project.executeTargets(Project.java:1181) > [junit] at org.apache.tools.ant.Main.runBuild(Main.java:698) > [junit] at org.apache.tools.ant.Main.startAnt(Main.java:199) > [junit] at > org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) > [junit] at > org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) > [junit] ------------- ---------------- --------------- > [junit] Testcase: > testLogin > (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): > FAILED > [junit] null > [junit] junit.framework.AssertionFailedError > [junit] at > com > .rackspacecloud > .client > .cloudfiles.FilesClientTestCase.testLogin(FilesClientTestCase.java:68) > [junit] > [junit] > [junit] Testcase: > testAccountInfo > (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): > FAILED > [junit] null > [junit] junit.framework.AssertionFailedError > [junit] at > com > .rackspacecloud > .client > .cloudfiles > .FilesClientTestCase.testAccountInfo(FilesClientTestCase.java:92) > [junit] > [junit] > [junit] Testcase: > testMultipleFilesNotThere > (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): > FAILED > [junit] null > > =============== > ======= > ===== > > > [junit] > [junit] Testcase: > testFilesObjectPath > (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED > [junit] null > [junit] junit.framework.AssertionFailedError > [junit] at > com > .rackspacecloud > .client > .cloudfiles > .FilesClientTestCase.testFilesObjectPath(FilesClientTestCase.java: > 1783) > [junit] > [junit] > [junit] Testcase: > testURLs > (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): > FAILED > [junit] null > [junit] junit.framework.AssertionFailedError > [junit] at > com > .rackspacecloud > .client > .cloudfiles.FilesClientTestCase.testURLs(FilesClientTestCase.java: > 1826) > [junit] > [junit] > [junit] Test > com.rackspacecloud.client.cloudfiles.FilesClientTestCase FAILED > > BUILD SUCCESSFUL > Total time: 5 seconds > [shashi at shashi rackspace-java-cloudfiles-1fb920d]$ > > > I was not clear about the properties to be set for running the "unit > tests" of rackspace cloud files - java apis package , kindly help me > for usage of java apis w.r.t swift > > > Thanks & Regards, > shashi > _______________________________________________ > Openstack-operators mailing list > Openstack-operators at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack- > operators -------------- next part -------------- An HTML attachment was scrubbed... URL: From jrussell at thesba.com Tue Apr 26 16:02:12 2011 From: jrussell at thesba.com (Justin J. Russell) Date: Tue, 26 Apr 2011 09:02:12 -0700 Subject: [Openstack-operators] cyberduck interface to swift ?? In-Reply-To: References: Message-ID: <401C063992AB5C47B4AF4D8F2FC6C3090175A3F392FE@NTSEXCHA1CMB2.NTS.PHX1> I was able to connect to our own implementation of Swift using the following settings: Server: storage.webcontrolcenter.com Port: 11000 Username: AccountName:UserName Path: /auth The username is your account name + ":" + your username. For example, if your account name is "Account1" and your username is "User1" then your username in Cyberduck is Account1:User1. I hope this helps. Thank you, Justin J. Russell | Vice President of Product Development of Technology Services [cid:image001.png at 01CC03F0.9FF6AE80] From: openstack-operators-bounces at lists.openstack.org [mailto:openstack-operators-bounces at lists.openstack.org] On Behalf Of shashidhar v Sent: Tuesday, April 26, 2011 6:22 AM To: openstack-operators at lists.openstack.org; Greg Holt Subject: [Openstack-operators] cyberduck interface to swift ?? Hi, I have deployed swift-1.4 dev(SAIO) service running on a test node , able to create the accounts and do upload/download of files using the "st" tool by following doc of SAIO Test node swift service is enabled with SSL using self signed certs. and uses swauth authentication And, then I have installed the Cyberduck-Installer-4.0.2.exe on windows xp and windows vista machines , but when I open connection to swift service running on test node it throws error as login failed swift at test3:~$ swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0 -U system:root -K testpass stat Account: AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f Containers: 0 Objects: 0 Bytes: 0 Accept-Ranges: bytes swift at test3:~$ swift at test3:~$ swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0 -U system:root -K testpass list swift at test3:~$ swift at test3:~$ curl -k -v -H 'X-Storage-User: system:root' -H 'X-Storage-Pass: testpass' https://192.168.62.63:8080/auth/v1.0 * About to connect() to 192.168.62.63 port 8080 (#0) * Trying 192.168.62.63... connected * Connected to 192.168.62.63 (192.168.62.63) port 8080 (#0) * successfully set certificate verify locations: * CAfile: none CApath: /etc/ssl/certs * SSLv3, TLS handshake, Client hello (1): * SSLv3, TLS handshake, Server hello (2): * SSLv3, TLS handshake, CERT (11): * SSLv3, TLS handshake, Server finished (14): * SSLv3, TLS handshake, Client key exchange (16): * SSLv3, TLS change cipher, Client hello (1): * SSLv3, TLS handshake, Finished (20): * SSLv3, TLS change cipher, Client hello (1): * SSLv3, TLS handshake, Finished (20): * SSL connection using AES256-SHA * Server certificate: * subject: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in * start date: 2011-04-25 05:45:12 GMT * expire date: 2011-05-25 05:45:12 GMT * common name: swift (does not match '192.168.62.63') * issuer: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in * SSL certificate verify result: self signed certificate (18), continuing anyway. > GET /auth/v1.0 HTTP/1.1 > User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15 > Host: 192.168.62.63:8080 > Accept: */* > X-Storage-User: system:root > X-Storage-Pass: testpass > < HTTP/1.1 200 OK < X-Storage-Url: https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f < X-Storage-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 < X-Auth-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 < Content-Length: 117 < Date: Tue, 26 Apr 2011 12:48:39 GMT < * Connection #0 to host 192.168.62.63 left intact * Closing connection #0 * SSLv3, TLS alert, Client hello (1): {"storage": {"default": "local", "local": "https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f"}}swift at test3:~$ swift at test3:~$ Using st tool I am able upload/download the files but using cyberduck interface , login itself is failed Kindly help me to resolve this login error , any doc. which describes about cyberduck interface to swift will be helpful I have checked the related doc. present under http://swift.openstack.org/howto_cyberduck.html but it describes about source build of cyberduck not the binary version Is it possible to specify "http" protocol instead of "https" using cyerduck to contact swift service ? kindly help me Thanks & Regards, shashi ________________________________ Notice: This communication, including attachments, may contain information that is confidential. It constitutes non-public information intended to be conveyed only to the designated recipient(s). If the reader or recipient of this communication is not the intended recipient, an employee or agent of the intended recipient who is responsible for delivering it to the intended recipient, or if you believe that you have received this communication in error, please notify the sender immediately by return e-mail and promptly delete this e-mail, including attachments without reading or saving them in any manner. The unauthorized use, dissemination, distribution, or reproduction of this e-mail, including attachments, is prohibited and may be unlawful. If you have received this email in error, please notify us immediately by e-mail or telephone and delete the e-mail and the attachments (if any). -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 13536 bytes Desc: image001.png URL: From shashidhar.velagandula at gmail.com Wed Apr 27 05:10:12 2011 From: shashidhar.velagandula at gmail.com (shashidhar v) Date: Wed, 27 Apr 2011 10:40:12 +0530 Subject: [Openstack-operators] Openstack-operators Digest, Vol 6, Issue 10 In-Reply-To: References: Message-ID: Hi, I tried similar way , but no luck ... login failed server : IP address login : system:root since I am using swauth - I used path as /auth/v1.0 ( even I tried path - "/auth" also ) You can check the attached scrennshots which shows the swift login using cyberduck swift logs : /var/log/syslog Apr 27 09:29:04 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/03/59/04 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29% 20%28Windows%20XP/5.1%29%20%28x86%29 - - - - txd48e8456-2803-4235-9fb1-1c2b443e33b3 - 0.0005 Apr 27 09:29:13 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/03/59/13 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx781d965e-edea-4853-992f-a84afdf1aefb - 0.0005 Apr 27 09:29:53 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/03/59/53 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx709aa787-0391-40a2-928f-9f16f642f5ee - 0.0005 Apr 27 09:32:42 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/04/02/42 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx28acc218-2c08-40e3-be5e-610b79607c64 - 0.0006 Apr 27 09:34:16 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/04/04/16 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx8e389e6c-a99a-4345-98be-99ad3c79e129 - 0.0005 There were no logs w.r.t cyberduck , how to enable the logs in cyberduck( debug mode ) ? There were no error messages except the login failed ,,, Kindly help to resolve this Thanks & Regards, shashi On Wed, Apr 27, 2011 at 12:32 AM, < openstack-operators-request at lists.openstack.org> wrote: > Send Openstack-operators mailing list submissions to > openstack-operators at lists.openstack.org > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > or, via email, send a message with subject or body 'help' to > openstack-operators-request at lists.openstack.org > > You can reach the person managing the list at > openstack-operators-owner at lists.openstack.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Openstack-operators digest..." > > > Today's Topics: > > 1. Re: cyberduck interface to swift ?? (Justin J. Russell) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 26 Apr 2011 09:02:12 -0700 > From: "Justin J. Russell" > To: shashidhar v , > "openstack-operators at lists.openstack.org" > , Greg Holt > > Subject: Re: [Openstack-operators] cyberduck interface to swift ?? > Message-ID: > <401C063992AB5C47B4AF4D8F2FC6C3090175A3F392FE at NTSEXCHA1CMB2.NTS.PHX1 > > > Content-Type: text/plain; charset="us-ascii" > > I was able to connect to our own implementation of Swift using the > following settings: > > Server: storage.webcontrolcenter.com > Port: 11000 > Username: AccountName:UserName > Path: /auth > > The username is your account name + ":" + your username. For example, if > your account name is "Account1" and your username is "User1" then your > username in Cyberduck is Account1:User1. > > I hope this helps. > > Thank you, > > Justin J. Russell | Vice President of Product Development of Technology > Services > > [cid:image001.png at 01CC03F0.9FF6AE80] > > From: openstack-operators-bounces at lists.openstack.org [mailto: > openstack-operators-bounces at lists.openstack.org] On Behalf Of shashidhar v > Sent: Tuesday, April 26, 2011 6:22 AM > To: openstack-operators at lists.openstack.org; Greg Holt > Subject: [Openstack-operators] cyberduck interface to swift ?? > > Hi, > > I have deployed swift-1.4 dev(SAIO) service running on a test node , able > to create the accounts and do upload/download of files using the "st" tool > by following doc of SAIO > Test node swift service is enabled with SSL using self signed certs. and > uses swauth authentication > > And, then I have installed the Cyberduck-Installer-4.0.2.exe on windows xp > and windows vista machines , but when I open connection to swift service > running on test node it throws error as login failed > > swift at test3:~$ swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0-U system:root -K testpass stat > Account: AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f > Containers: 0 > Objects: 0 > Bytes: 0 > Accept-Ranges: bytes > swift at test3:~$ > swift at test3:~$ > swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0 -U system:root > -K testpass list > swift at test3:~$ > swift at test3:~$ curl -k -v -H 'X-Storage-User: system:root' -H > 'X-Storage-Pass: testpass' https://192.168.62.63:8080/auth/v1.0 > * About to connect() to 192.168.62.63 port 8080 (#0) > * Trying 192.168.62.63... connected > * Connected to 192.168.62.63 (192.168.62.63) port 8080 (#0) > * successfully set certificate verify locations: > * CAfile: none > CApath: /etc/ssl/certs > * SSLv3, TLS handshake, Client hello (1): > * SSLv3, TLS handshake, Server hello (2): > * SSLv3, TLS handshake, CERT (11): > * SSLv3, TLS handshake, Server finished (14): > * SSLv3, TLS handshake, Client key exchange (16): > * SSLv3, TLS change cipher, Client hello (1): > * SSLv3, TLS handshake, Finished (20): > * SSLv3, TLS change cipher, Client hello (1): > * SSLv3, TLS handshake, Finished (20): > * SSL connection using AES256-SHA > * Server certificate: > * subject: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; > CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in shashidharv at ctsf.cdac.org.in> > * start date: 2011-04-25 05:45:12 GMT > * expire date: 2011-05-25 05:45:12 GMT > * common name: swift (does not match '192.168.62.63') > * issuer: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; > CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in shashidharv at ctsf.cdac.org.in> > * SSL certificate verify result: self signed certificate (18), > continuing anyway. > > GET /auth/v1.0 HTTP/1.1 > > User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k > zlib/1.2.3.3 libidn/1.15 > > Host: 192.168.62.63:8080 > > Accept: */* > > X-Storage-User: system:root > > X-Storage-Pass: testpass > > > < HTTP/1.1 200 OK > < X-Storage-Url: > https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f > < X-Storage-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 > < X-Auth-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 > < Content-Length: 117 > < Date: Tue, 26 Apr 2011 12:48:39 GMT > < > * Connection #0 to host 192.168.62.63 left intact > * Closing connection #0 > * SSLv3, TLS alert, Client hello (1): > {"storage": {"default": "local", "local": " > https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f > "}}swift at test3:~$ > swift at test3:~$ > > > Using st tool I am able upload/download the files but using cyberduck > interface , login itself is failed > > Kindly help me to resolve this login error , any doc. which describes > about cyberduck interface to swift will be helpful < > http://cyberduck.ch/windows/Cyberduck-Installer-4.0.2.exe> > I have checked the related doc. present under > http://swift.openstack.org/howto_cyberduck.html but it describes about > source build of cyberduck not the binary version > > Is it possible to specify "http" protocol instead of "https" using > cyerduck to contact swift service ? > kindly help me > > Thanks & Regards, > shashi > > ________________________________ > Notice: This communication, including attachments, may contain information > that is confidential. It constitutes non-public information intended to be > conveyed only to the designated recipient(s). If the reader or recipient of > this communication is not the intended recipient, an employee or agent of > the intended recipient who is responsible for delivering it to the intended > recipient, or if you believe that you have received this communication in > error, please notify the sender immediately by return e-mail and promptly > delete this e-mail, including attachments without reading or saving them in > any manner. The unauthorized use, dissemination, distribution, or > reproduction of this e-mail, including attachments, is prohibited and may be > unlawful. If you have received this email in error, please notify us > immediately by e-mail or telephone and delete the e-mail and the attachments > (if any). > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.openstack.org/pipermail/openstack-operators/attachments/20110426/0d9d7598/attachment.html > > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: image001.png > Type: image/png > Size: 13536 bytes > Desc: image001.png > URL: < > http://lists.openstack.org/pipermail/openstack-operators/attachments/20110426/0d9d7598/attachment.png > > > > ------------------------------ > > _______________________________________________ > Openstack-operators mailing list > Openstack-operators at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > End of Openstack-operators Digest, Vol 6, Issue 10 > ************************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shashidhar.velagandula at gmail.com Wed Apr 27 05:01:58 2011 From: shashidhar.velagandula at gmail.com (shashidhar v) Date: Wed, 27 Apr 2011 10:31:58 +0530 Subject: [Openstack-operators] cyberduck interface to swift ?? In-Reply-To: <401C063992AB5C47B4AF4D8F2FC6C3090175A3F392FE@NTSEXCHA1CMB2.NTS.PHX1> References: <401C063992AB5C47B4AF4D8F2FC6C3090175A3F392FE@NTSEXCHA1CMB2.NTS.PHX1> Message-ID: Hi, I tried similar way , but no luck ... login failed since I am using swauth - I used path as /auth/v1.0 ( even I tried path - "/auth" also ) You can check the attached scrennshots which shows the swift login using cyberduck swift logs : /var/log/syslog Apr 27 09:29:04 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/03/59/04 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - txd48e8456-2803-4235-9fb1-1c2b443e33b3 - 0.0005 Apr 27 09:29:13 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/03/59/13 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx781d965e-edea-4853-992f-a84afdf1aefb - 0.0005 Apr 27 09:29:53 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/03/59/53 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx709aa787-0391-40a2-928f-9f16f642f5ee - 0.0005 Apr 27 09:32:42 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/04/02/42 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx28acc218-2c08-40e3-be5e-610b79607c64 - 0.0006 Apr 27 09:34:16 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/04/04/16 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx8e389e6c-a99a-4345-98be-99ad3c79e129 - 0.0005 There were no logs w.r.t cyberduck , how to enable the logs in cyberduck( debug mode ) ? There were no error messages except the login failed ,,, Kindly help to resolve this Thanks & Regards, shashi On Tue, Apr 26, 2011 at 9:32 PM, Justin J. Russell wrote: > I was able to connect to our own implementation of Swift using the > following settings: > > > > Server: storage.webcontrolcenter.com > > Port: 11000 > > Username: AccountName:UserName > > Path: /auth > > > > The username is your account name + ?:? + your username. For example, if > your account name is ?Account1? and your username is ?User1? then your > username in Cyberduck is Account1:User1. > > > > I hope this helps. > > > > Thank you, > > > > Justin J. Russell *|* Vice President of Product Development of Technology > Services > > > > [image: Description: Description: Description: thesbalogo] > > > > *From:* openstack-operators-bounces at lists.openstack.org [mailto: > openstack-operators-bounces at lists.openstack.org] *On Behalf Of *shashidhar > v > *Sent:* Tuesday, April 26, 2011 6:22 AM > *To:* openstack-operators at lists.openstack.org; Greg Holt > *Subject:* [Openstack-operators] cyberduck interface to swift ?? > > > > Hi, > > I have deployed swift-1.4 dev(SAIO) service running on a test node , able > to create the accounts and do upload/download of files using the "st" tool > by following doc of SAIO > Test node swift service is enabled with SSL using self signed certs. and > uses swauth authentication > > And, then I have installed the Cyberduck-Installer-4.0.2.exe on windows xp > and windows vista machines , but when I open connection to swift service > running on test node it throws error as login failed > > swift at test3:~$ swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0-U system:root -K testpass stat > Account: AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f > Containers: 0 > Objects: 0 > Bytes: 0 > Accept-Ranges: bytes > swift at test3:~$ > swift at test3:~$ > swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0 -U system:root > -K testpass list > swift at test3:~$ > swift at test3:~$ curl -k -v -H 'X-Storage-User: system:root' -H > 'X-Storage-Pass: testpass' https://192.168.62.63:8080/auth/v1.0 > * About to connect() to 192.168.62.63 port 8080 (#0) > * Trying 192.168.62.63... connected > * Connected to 192.168.62.63 (192.168.62.63) port 8080 (#0) > * successfully set certificate verify locations: > * CAfile: none > CApath: /etc/ssl/certs > * SSLv3, TLS handshake, Client hello (1): > * SSLv3, TLS handshake, Server hello (2): > * SSLv3, TLS handshake, CERT (11): > * SSLv3, TLS handshake, Server finished (14): > * SSLv3, TLS handshake, Client key exchange (16): > * SSLv3, TLS change cipher, Client hello (1): > * SSLv3, TLS handshake, Finished (20): > * SSLv3, TLS change cipher, Client hello (1): > * SSLv3, TLS handshake, Finished (20): > * SSL connection using AES256-SHA > * Server certificate: > * subject: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; > CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in > * start date: 2011-04-25 05:45:12 GMT > * expire date: 2011-05-25 05:45:12 GMT > * common name: swift (does not match '192.168.62.63') > * issuer: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; > CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in > * SSL certificate verify result: self signed certificate (18), > continuing anyway. > > GET /auth/v1.0 HTTP/1.1 > > User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k > zlib/1.2.3.3 libidn/1.15 > > Host: 192.168.62.63:8080 > > Accept: */* > > X-Storage-User: system:root > > X-Storage-Pass: testpass > > > < HTTP/1.1 200 OK > < X-Storage-Url: > https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f > < X-Storage-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 > < X-Auth-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 > < Content-Length: 117 > < Date: Tue, 26 Apr 2011 12:48:39 GMT > < > * Connection #0 to host 192.168.62.63 left intact > * Closing connection #0 > * SSLv3, TLS alert, Client hello (1): > {"storage": {"default": "local", "local": " > https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f > "}}swift at test3:~$ > swift at test3:~$ > > > Using st tool I am able upload/download the files but using cyberduck > interface , login itself is failed > > Kindly help me to resolve this login error , any doc. which describes > about cyberduck interface to swift will be helpful > > I have checked the related doc. present under > http://swift.openstack.org/howto_cyberduck.html but it describes about > source build of cyberduck not the binary version > > Is it possible to specify "http" protocol instead of "https" using > cyerduck to contact swift service ? > kindly help me > > Thanks & Regards, > shashi > > ------------------------------ > Notice: This communication, including attachments, may contain information > that is confidential. It constitutes non-public information intended to be > conveyed only to the designated recipient(s). If the reader or recipient of > this communication is not the intended recipient, an employee or agent of > the intended recipient who is responsible for delivering it to the intended > recipient, or if you believe that you have received this communication in > error, please notify the sender immediately by return e-mail and promptly > delete this e-mail, including attachments without reading or saving them in > any manner. The unauthorized use, dissemination, distribution, or > reproduction of this e-mail, including attachments, is prohibited and may be > unlawful. If you have received this email in error, please notify us > immediately by e-mail or telephone and delete the e-mail and the attachments > (if any). > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: swift1.JPG Type: image/jpeg Size: 133530 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: swift2.JPG Type: image/jpeg Size: 118924 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: swift3.JPG Type: image/jpeg Size: 118924 bytes Desc: not available URL: From topper at toppingdesign.com Wed Apr 27 19:13:51 2011 From: topper at toppingdesign.com (Topping Bowers) Date: Wed, 27 Apr 2011 15:13:51 -0400 Subject: [Openstack-operators] 1.2 to 1.3 upgrade Message-ID: Hey All, hope this finds you well. We are trying to upgrade from 1.2 to 1.3 swift object store. Looking at the swift code - I see the new indexes getting created on new container databases, but I do not see it getting added to existing 1.2 databases. Also, in general, I don't see anything in the release notes about upgrading. Any hints, clues, or how-tos anyone knows? Thanks so much, -- Topper Bowers topper at toppingdesign.com http://croonmytune.com http://blog.toppingdesign.com From shashidhar.velagandula at gmail.com Fri Apr 1 06:35:14 2011 From: shashidhar.velagandula at gmail.com (shashidhar v) Date: Fri, 1 Apr 2011 12:05:14 +0530 Subject: [Openstack-operators] failed to run the auth-server deamon for SAIO setup In-Reply-To: <4696C6EF-36BE-4D7D-939F-FD7364A2AAB8@zeroaccess.org> References: <4696C6EF-36BE-4D7D-939F-FD7364A2AAB8@zeroaccess.org> Message-ID: HI Marcelo , Thanks for the reply , 1. W.r.t problem #1 , I have stopped the tomcat service which is using the port 8080 and then started the swift service without any errors . It is using "swauth" auth. mechanisam as you mentioned swift-1.3 develop supports only swauth ,then created the accounts using "recreateaccounts" script of SAIO ,, #!/bin/bash # Replace swauthkey with whatever your super_admin key is (recorded in # /etc/swift/proxy-server.conf). swauth-prep -K swauthkey swauth-add-user -K swauthkey -a test tester testing swauth-add-user -K swauthkey -a test2 tester2 testing2 swauth-add-user -K swauthkey test tester3 testing3 swauth-add-user -K swauthkey -a -r reseller reseller reseller [shashi at shashi samples]$ curl -v -H 'X-Storage-User: test:tester3' -H 'X-Storage-Pass: testing3' http://192.168.62.63:8080/auth/v1.0 * About to connect() to 192.168.62.63 port 8080 * Trying 192.168.62.63... connected * Connected to 192.168.62.63 (192.168.62.63) port 8080 > GET /auth/v1.0 HTTP/1.1 > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > Host: 192.168.62.63:8080 > Accept: */* > X-Storage-User: test:tester3 > X-Storage-Pass: testing3 > < HTTP/1.1 200 OK < X-Storage-Url: http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a < X-Storage-Token: AUTH_tke67d8d3c037649688bd527a7b77cc287 < X-Auth-Token: AUTH_tke67d8d3c037649688bd527a7b77cc287 < Content-Length: 112 < Date: Fri, 01 Apr 2011 04:31:06 GMT Connection #0 to host 192.168.62.63 left intact * Closing connection #0 {"storage": {"default": "local", "local": " http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a "}}[shashi at shashi samples]$ [shashi at shashi samples]$ [shashi at shashi samples]$ curl -v -H 'X-Auth-Token: AUTH_tke67d8d3c037649688bd527a7b77cc287' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a * About to connect() to 192.168.62.63 port 8080 * Trying 192.168.62.63... connected * Connected to 192.168.62.63 (192.168.62.63) port 8080 > GET /v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a HTTP/1.1 > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > Host: 192.168.62.63:8080 > Accept: */* > X-Auth-Token: AUTH_tke67d8d3c037649688bd527a7b77cc287 > < HTTP/1.1 403 Forbidden < Content-Length: 157 < Content-Type: text/html; charset=UTF-8 < Date: Fri, 01 Apr 2011 04:45:35 GMT 403 Forbidden

403 Forbidden

Access was denied to this resource.

Connection #0 to host 192.168.62.63 left intact * Closing connection #0 [shashi at shashi samples]$ [shashi at shashi samples]$ In the above script, the third user is tester3 (non admin) which is not allowed to create containers ? Then what's the role of non-admin users created under swift , what operations they can perform ? Swift supports ACL or not and the containers/objects created by a admin user can be shared with non-admin user for atleast downloading the objects ? 2. In order to check the "devauth" authentication , I have donwloaded the swift-1.2.0.tar.gz in a second test node , what's the command to build the code ,, sudo python setup.py develop or anyother command I need to use ? Whether same SAIO doc can be referred to start the deamons ? Thanks & Regards, shashi On Thu, Mar 31, 2011 at 9:35 PM, Marcelo Martins wrote: > Sent u a reply for the message below a few minutes ago .... Please reply > to btorch-os at zeroaccess.org and the list when u do so.. Thanks > > > Marcelo > > > On Mar 31, 2011, at 4:33 AM, shashidhar v wrote: > > HI, > > I am trying to install and test the Swift tool by following the SAIO > I have set up the repos and downloaded the code as per the steps given in > SAIO > > swift at test3:~/swift$ cd ~/swift/trunk; sudo python setup.py develop > running develop > running egg_info > creating swift.egg-info > writing swift.egg-info/PKG-INFO > writing top-level names to swift.egg-info/top_level.txt > writing dependency_links to swift.egg-info/dependency_links.txt > writing entry points to swift.egg-info/entry_points.txt > writing manifest file 'swift.egg-info/SOURCES.txt' > reading manifest file 'swift.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no files found matching 'ChangeLog' > writing manifest file 'swift.egg-info/SOURCES.txt' > running build_ext > Creating /usr/local/lib/python2.6/dist-packages/swift.egg-link (link to .) > Removing swift 1.3-dev from easy-install.pth file > Adding swift 1.3-dev to easy-install.pth file > Installing st script to /usr/local/bin > Installing swift-account-auditor script to /usr/local/bin > Installing swift-account-audit script to /usr/local/bin > Installing swift-account-reaper script to /usr/local/bin > Installing swift-account-replicator script to /usr/local/bin > Installing swift-account-server script to /usr/local/bin > Installing swift-container-auditor script to /usr/local/bin > Installing swift-container-replicator script to /usr/local/bin > Installing swift-container-server script to /usr/local/bin > Installing swift-container-updater script to /usr/local/bin > Installing swift-drive-audit script to /usr/local/bin > Installing swift-get-nodes script to /usr/local/bin > Installing swift-init script to /usr/local/bin > Installing swift-object-auditor script to /usr/local/bin > Installing swift-object-info script to /usr/local/bin > Installing swift-object-replicator script to /usr/local/bin > Installing swift-object-server script to /usr/local/bin > Installing swift-object-updater script to /usr/local/bin > Installing swift-proxy-server script to /usr/local/bin > Installing swift-ring-builder script to /usr/local/bin > Installing swift-stats-populate script to /usr/local/bin > Installing swift-stats-report script to /usr/local/bin > Installing swift-bench script to /usr/local/bin > Installing swift-log-uploader script to /usr/local/bin > Installing swift-log-stats-collector script to /usr/local/bin > Installing swift-account-stats-logger script to /usr/local/bin > Installing swauth-add-account script to /usr/local/bin > Installing swauth-add-user script to /usr/local/bin > Installing swauth-cleanup-tokens script to /usr/local/bin > Installing swauth-delete-account script to /usr/local/bin > Installing swauth-delete-user script to /usr/local/bin > Installing swauth-list script to /usr/local/bin > Installing swauth-prep script to /usr/local/bin > Installing swauth-set-account-service script to /usr/local/bin > > Installed /home/swift/swift/trunk > Processing dependencies for swift==1.3-dev > Finished processing dependencies for swift==1.3-dev > swift at test3:~/swift/trunk$ > > > swift at test3:~$ startmain > WARNING: Unable to increase file descriptor limit. Running as non-root? > Starting proxy-server...(/etc/swift/proxy-server.conf) > Starting container-server...(/etc/swift/container-server/1.conf) > Starting container-server...(/etc/swift/container-server/2.conf) > Starting container-server...(/etc/swift/container-server/3.conf) > Starting container-server...(/etc/swift/container-server/4.conf) > Starting account-server...(/etc/swift/account-server/1.conf) > Starting account-server...(/etc/swift/account-server/2.conf) > Starting account-server...(/etc/swift/account-server/3.conf) > Starting account-server...(/etc/swift/account-server/4.conf) > Starting object-server...(/etc/swift/object-server/1.conf) > Starting object-server...(/etc/swift/object-server/2.conf) > Starting object-server...(/etc/swift/object-server/3.conf) > Starting object-server...(/etc/swift/object-server/4.conf) > Traceback (most recent call last): > File "/usr/local/bin/swift-proxy-server", line 7, in > execfile(__file__) > File "/home/swift/swift/trunk/bin/swift-proxy-server", line 22, in > > run_wsgi(conf_file, 'proxy-server', default_port=8080, **options) > File "/home/swift/swift/trunk/swift/common/wsgi.py", line 123, in > run_wsgi > sock = get_socket(conf, default_port=kwargs.get('default_port', 8080)) > File "/home/swift/swift/trunk/swift/common/wsgi.py", line 89, in > get_socket > bind_addr) > Exception: Could not bind to 0.0.0.0:8080 after trying for 30 seconds > > WARNING: Unable to increase file descriptor limit. Running as non-root? > Starting auth-server...(/etc/swift/auth-server.conf) > Traceback (most recent call last): > File "/usr/local/bin/swift-auth-server", line 5, in > pkg_resources.run_script('swift==1.3-dev', 'swift-auth-server') > File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 461, in > run_script > self.require(requires)[0].run_script(script_name, ns) > File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 1188, in > run_script > raise ResolutionError("No script named %r" % script_name) > pkg_resources.ResolutionError: No script named 'swift-auth-server' > > swift at test3:~$ > > Kindly help me to resolve the above error > > Thanks & Regards, > shashi > > _______________________________________________ > Openstack-operators mailing list > Openstack-operators at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gholt at rackspace.com Fri Apr 1 13:02:45 2011 From: gholt at rackspace.com (Greg Holt) Date: Fri, 1 Apr 2011 08:02:45 -0500 Subject: [Openstack-operators] failed to run the auth-server deamon for SAIO setup In-Reply-To: References: <4696C6EF-36BE-4D7D-939F-FD7364A2AAB8@zeroaccess.org> Message-ID: <43C2F369-B701-4163-8805-EA6657742D9E@rackspace.com> On Apr 1, 2011, at 1:35 AM, shashidhar v wrote: > In the above script, the third user is tester3 (non admin) which is not allowed to create containers ? Then what's the role of non-admin users created under swift , what operations they can perform ? > > Swift supports ACL or not and the containers/objects created by a admin user can be shared with non-admin user for atleast downloading the objects ? Non-admin users can only perform operations per container based on the container?s X-Container-Read and X-Container-Write ACLs. With an admin account you could create a container for that non-admin user and set X-Container-Read: test:tester3 and X-Container-Write: test:tester3. These may explain more: http://swift.openstack.org/overview_auth.html http://swift.openstack.org/misc.html#module-swift.common.middleware.acl From shashidhar.velagandula at gmail.com Tue Apr 5 10:32:24 2011 From: shashidhar.velagandula at gmail.com (shashidhar v) Date: Tue, 5 Apr 2011 16:02:24 +0530 Subject: [Openstack-operators] failed to run the auth-server deamon for SAIO setup In-Reply-To: <43C2F369-B701-4163-8805-EA6657742D9E@rackspace.com> References: <4696C6EF-36BE-4D7D-939F-FD7364A2AAB8@zeroaccess.org> <43C2F369-B701-4163-8805-EA6657742D9E@rackspace.com> Message-ID: Hi Gholt, I tried to set the container based read and write acl to share the container with non admin user , but it is giving error as access denied [shashi at shashi samples]$ curl -v -H 'X-Storage-User: test:tester' -H 'X-Storage-Pass: testing' http://192.168.62.63:8080/auth/v1.0* About to connect() to 192.168.62.63 port 8080 * Trying 192.168.62.63... connected * Connected to 192.168.62.63 (192.168.62.63) port 8080 > GET /auth/v1.0 HTTP/1.1 > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > Host: 192.168.62.63:8080 > Accept: */* > X-Storage-User: test:tester > X-Storage-Pass: testing > < HTTP/1.1 200 OK < X-Storage-Url: http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a < X-Storage-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525 < X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525 < Content-Length: 112 < Date: Tue, 05 Apr 2011 10:18:31 GMT Connection #0 to host 192.168.62.63 left intact * Closing connection #0 {"storage": {"default": "local", "local": " http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a "}}[shashi at shashi samples]$ [shashi at shashi samples]$ curl -X HEAD -D - -H 'X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a HTTP/1.1 204 No Content X-Account-Object-Count: 0 X-Account-Bytes-Used: 0 X-Account-Container-Count: 1 Content-Length: 0 Date: Tue, 05 Apr 2011 10:20:19 GMT [shashi at shashi samples]$ [shashi at shashi samples]$ curl -X HEAD -D - -H 'X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 HTTP/1.1 204 No Content X-Container-Object-Count: 1 X-Container-Bytes-Used: 29 Content-Length: 0 Date: Tue, 05 Apr 2011 10:20:40 GMT [shashi at shashi samples]$ Initially I have created a container named as "container1" using the admin user "test:tester" and then trying to set read and write acl for the container1 to share it with non-admin user .......... [shashi at shashi samples]$ curl -v -H 'X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525' -H 'X-Container-Read: test:tester3' -H 'X-Container-Write: test:tester3' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 * About to connect() to 192.168.62.63 port 8080 * Trying 192.168.62.63... connected * Connected to 192.168.62.63 (192.168.62.63) port 8080 > GET /v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 HTTP/1.1 > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > Host: 192.168.62.63:8080 > Accept: */* > X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525 > X-Container-Read: test:tester3 > X-Container-Write: test:tester3 > < HTTP/1.1 200 OK < X-Container-Object-Count: 1 < X-Container-Bytes-Used: 29 < Content-Length: 10 < Content-Type: text/plain; charset=utf8 < Date: Tue, 05 Apr 2011 10:11:01 GMT testfile1 * Connection #0 to host 192.168.62.63 left intact * Closing connection #0 [shashi at shashi samples]$ [shashi at shashi samples]$ curl -v -H 'X-Storage-User: test:tester3' -H 'X-Storage-Pass: testing3' http://192.168.62.63:8080/auth/v1.0* About to connect() to 192.168.62.63 port 8080 * Trying 192.168.62.63... connected * Connected to 192.168.62.63 (192.168.62.63) port 8080 > GET /auth/v1.0 HTTP/1.1 > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > Host: 192.168.62.63:8080 > Accept: */* > X-Storage-User: test:tester3 > X-Storage-Pass: testing3 > < HTTP/1.1 200 OK < X-Storage-Url: http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a < X-Storage-Token: AUTH_tk124a8a19ad7e49c5a04710716fd4f126 < X-Auth-Token: AUTH_tk124a8a19ad7e49c5a04710716fd4f126 < Content-Length: 112 < Date: Tue, 05 Apr 2011 10:11:16 GMT Connection #0 to host 192.168.62.63 left intact * Closing connection #0 {"storage": {"default": "local", "local": " http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a "}}[shashi at shashi samples]$ [shashi at shashi samples]$ curl -s -D - -H 'X-Auth-Token: AUTH_tk124a8a19ad7e49c5a04710716fd4f126' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1/testfile1 HTTP/1.1 403 Forbidden Content-Length: 157 Content-Type: text/html; charset=UTF-8 Date: Tue, 05 Apr 2011 10:11:42 GMT 403 Forbidden

403 Forbidden

Access was denied to this resource.

[shashi at shashi samples]$ [shashi at shashi samples]$ Thanks & Regards, shashi On Fri, Apr 1, 2011 at 6:32 PM, Greg Holt wrote: > On Apr 1, 2011, at 1:35 AM, shashidhar v wrote: > > > In the above script, the third user is tester3 (non admin) which is not > allowed to create containers ? Then what's the role of non-admin users > created under swift , what operations they can perform ? > > > > Swift supports ACL or not and the containers/objects created by a admin > user can be shared with non-admin user for atleast downloading the objects ? > > Non-admin users can only perform operations per container based on the > container?s X-Container-Read and X-Container-Write ACLs. With an admin > account you could create a container for that non-admin user and set > X-Container-Read: test:tester3 and X-Container-Write: test:tester3. > > These may explain more: > > http://swift.openstack.org/overview_auth.html > http://swift.openstack.org/misc.html#module-swift.common.middleware.acl > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gholt at rackspace.com Tue Apr 5 12:36:31 2011 From: gholt at rackspace.com (Greg Holt) Date: Tue, 5 Apr 2011 07:36:31 -0500 Subject: [Openstack-operators] failed to run the auth-server deamon for SAIO setup In-Reply-To: References: <4696C6EF-36BE-4D7D-939F-FD7364A2AAB8@zeroaccess.org> <43C2F369-B701-4163-8805-EA6657742D9E@rackspace.com> Message-ID: You have to use the PUT or POST command when trying to set the headers on a container. Try adding -X POST to that curl command: curl -v -X POST -H 'X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525' -H 'X-Container-Read: test:tester3' -H 'X-Container-Write: test:tester3' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 If you GET or the HEAD the container afterwards, you should see the two headers returned to you with the appropriate values. On Apr 5, 2011, at 5:32 AM, shashidhar v wrote: > Hi Gholt, > > I tried to set the container based read and write acl to share the container with non admin user , but it is giving error as access denied > > [shashi at shashi samples]$ curl -v -H 'X-Storage-User: test:tester' -H 'X-Storage-Pass: testing' http://192.168.62.63:8080/auth/v1.0* About to connect() to 192.168.62.63 port 8080 > * Trying 192.168.62.63... connected > * Connected to 192.168.62.63 (192.168.62.63) port 8080 > > GET /auth/v1.0 HTTP/1.1 > > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > > Host: 192.168.62.63:8080 > > Accept: */* > > X-Storage-User: test:tester > > X-Storage-Pass: testing > > > < HTTP/1.1 200 OK > < X-Storage-Url: http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a > < X-Storage-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525 > < X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525 > < Content-Length: 112 > < Date: Tue, 05 Apr 2011 10:18:31 GMT > Connection #0 to host 192.168.62.63 left intact > * Closing connection #0 > {"storage": {"default": "local", "local": "http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a"}}[shashi at shashi samples]$ > > > [shashi at shashi samples]$ curl -X HEAD -D - -H 'X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a > HTTP/1.1 204 No Content > X-Account-Object-Count: 0 > X-Account-Bytes-Used: 0 > X-Account-Container-Count: 1 > Content-Length: 0 > Date: Tue, 05 Apr 2011 10:20:19 GMT > > [shashi at shashi samples]$ > [shashi at shashi samples]$ curl -X HEAD -D - -H 'X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 > HTTP/1.1 204 No Content > X-Container-Object-Count: 1 > X-Container-Bytes-Used: 29 > Content-Length: 0 > Date: Tue, 05 Apr 2011 10:20:40 GMT > > [shashi at shashi samples]$ > > > > Initially I have created a container named as "container1" using the admin user "test:tester" and then trying to set read and write acl for the container1 to share it with non-admin user .......... > > > > [shashi at shashi samples]$ curl -v -H 'X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525' -H 'X-Container-Read: test:tester3' -H 'X-Container-Write: test:tester3' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 > * About to connect() to 192.168.62.63 port 8080 > * Trying 192.168.62.63... connected > * Connected to 192.168.62.63 (192.168.62.63) port 8080 > > GET /v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 HTTP/1.1 > > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > > Host: 192.168.62.63:8080 > > Accept: */* > > X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525 > > X-Container-Read: test:tester3 > > X-Container-Write: test:tester3 > > > < HTTP/1.1 200 OK > < X-Container-Object-Count: 1 > < X-Container-Bytes-Used: 29 > < Content-Length: 10 > < Content-Type: text/plain; charset=utf8 > < Date: Tue, 05 Apr 2011 10:11:01 GMT > testfile1 > * Connection #0 to host 192.168.62.63 left intact > * Closing connection #0 > [shashi at shashi samples]$ > > [shashi at shashi samples]$ curl -v -H 'X-Storage-User: test:tester3' -H 'X-Storage-Pass: testing3' http://192.168.62.63:8080/auth/v1.0* About to connect() to 192.168.62.63 port 8080 > * Trying 192.168.62.63... connected > * Connected to 192.168.62.63 (192.168.62.63) port 8080 > > GET /auth/v1.0 HTTP/1.1 > > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > > Host: 192.168.62.63:8080 > > Accept: */* > > X-Storage-User: test:tester3 > > X-Storage-Pass: testing3 > > > < HTTP/1.1 200 OK > < X-Storage-Url: http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a > < X-Storage-Token: AUTH_tk124a8a19ad7e49c5a04710716fd4f126 > < X-Auth-Token: AUTH_tk124a8a19ad7e49c5a04710716fd4f126 > < Content-Length: 112 > < Date: Tue, 05 Apr 2011 10:11:16 GMT > Connection #0 to host 192.168.62.63 left intact > * Closing connection #0 > {"storage": {"default": "local", "local": "http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a"}}[shashi at shashi samples]$ > > [shashi at shashi samples]$ curl -s -D - -H 'X-Auth-Token: AUTH_tk124a8a19ad7e49c5a04710716fd4f126' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1/testfile1 > HTTP/1.1 403 Forbidden > Content-Length: 157 > Content-Type: text/html; charset=UTF-8 > Date: Tue, 05 Apr 2011 10:11:42 GMT > > > > 403 Forbidden > > >

403 Forbidden

> Access was denied to this resource.

> > > > > [shashi at shashi samples]$ > [shashi at shashi samples]$ > > Thanks & Regards, > shashi > > > > > > On Fri, Apr 1, 2011 at 6:32 PM, Greg Holt wrote: > On Apr 1, 2011, at 1:35 AM, shashidhar v wrote: > > > In the above script, the third user is tester3 (non admin) which is not allowed to create containers ? Then what's the role of non-admin users created under swift , what operations they can perform ? > > > > Swift supports ACL or not and the containers/objects created by a admin user can be shared with non-admin user for atleast downloading the objects ? > > Non-admin users can only perform operations per container based on the container?s X-Container-Read and X-Container-Write ACLs. With an admin account you could create a container for that non-admin user and set X-Container-Read: test:tester3 and X-Container-Write: test:tester3. > > These may explain more: > > http://swift.openstack.org/overview_auth.html > http://swift.openstack.org/misc.html#module-swift.common.middleware.acl > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shashidhar.velagandula at gmail.com Tue Apr 5 14:03:48 2011 From: shashidhar.velagandula at gmail.com (shashidhar v) Date: Tue, 5 Apr 2011 19:33:48 +0530 Subject: [Openstack-operators] failed to run the auth-server deamon for SAIO setup In-Reply-To: References: <4696C6EF-36BE-4D7D-939F-FD7364A2AAB8@zeroaccess.org> <43C2F369-B701-4163-8805-EA6657742D9E@rackspace.com> Message-ID: Hi Gholt , 1) Container based ACL was working fine ,, [shashi at shashi samples]$ curl -X GET -D - -H 'X-Auth-Token:AUTH_tk124a8a19ad7e49c5a04710716fd4f126' http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 HTTP/1.1 200 OK X-Container-Object-Count: 1 X-Container-Read: test:tester3 X-Container-Bytes-Used: 29 Content-Length: 10 Content-Type: text/plain; charset=utf8 Date: Tue, 05 Apr 2011 12:57:49 GMT testfile1 [shashi at shashi samples]$ 2) How to create new accounts/users using the admin "reseller" which was created using the script "recreateaccounts" of SAIO swift at test3:~/swift/trunk$ swauth-prep -K reseller Auth subsystem prep failed: 403 Forbidden swift at test3:~/swift/trunk$ swift at test3:~/swift/trunk$ swauth-add-user -U reseller:reseller -K reseller -A http://192.168.62.63:8080/auth/v1.0 reseller user1 user1Account creation failed: 400 Bad Request User creation failed: 400 Bad Request swift at test3:~/swift/trunk$ swauth-add-user -U reseller:reseller -K reseller -A http://192.168.62.63:8080/v1/AUTH_a62419e4-7841-49d1-950f-521443c8a75dreseller user1 password1 Account creation failed: 401 Unauthorized User creation failed: 401 Unauthorized swift at test3:~/swift/trunk$ 3) Is it possible to enforce the storage limit for a non admin account/user in swift , if so how to set that storage limit for a user ? How to distribute the available storage among different users ? Thanks & Regards, shashi On Tue, Apr 5, 2011 at 6:06 PM, Greg Holt wrote: > You have to use the PUT or POST command when trying to set the headers on a > container. Try adding -X POST to that curl command: > > curl -v *-X POST* -H 'X-Auth-Token: > AUTH_tk64b46c28eda84a839b7ba10cc54f3525' -H 'X-Container-Read: test:tester3' > -H 'X-Container-Write: test:tester3' > http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 > > If you GET or the HEAD the container afterwards, you should see the two > headers returned to you with the appropriate values. > > On Apr 5, 2011, at 5:32 AM, shashidhar v wrote: > > Hi Gholt, > > I tried to set the container based read and write acl to share the > container with non admin user , but it is giving error as access denied > > [shashi at shashi samples]$ curl -v -H 'X-Storage-User: test:tester' -H > 'X-Storage-Pass: testing' http://192.168.62.63:8080/auth/v1.0* About to > connect() to 192.168.62.63 port 8080 > * Trying 192.168.62.63... connected > * Connected to 192.168.62.63 (192.168.62.63) port 8080 > > GET /auth/v1.0 HTTP/1.1 > > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 > OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > > Host: 192.168.62.63:8080 > > Accept: */* > > X-Storage-User: test:tester > > X-Storage-Pass: testing > > > < HTTP/1.1 200 OK > < X-Storage-Url: > http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a > < X-Storage-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525 > < X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525 > < Content-Length: 112 > < Date: Tue, 05 Apr 2011 10:18:31 GMT > Connection #0 to host 192.168.62.63 left intact > * Closing connection #0 > {"storage": {"default": "local", "local": " > http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a > "}}[shashi at shashi samples]$ > > > [shashi at shashi samples]$ curl -X HEAD -D - -H 'X-Auth-Token: > AUTH_tk64b46c28eda84a839b7ba10cc54f3525' > http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a > HTTP/1.1 204 No Content > X-Account-Object-Count: 0 > X-Account-Bytes-Used: 0 > X-Account-Container-Count: 1 > Content-Length: 0 > Date: Tue, 05 Apr 2011 10:20:19 GMT > > [shashi at shashi samples]$ > [shashi at shashi samples]$ curl -X HEAD -D - -H 'X-Auth-Token: > AUTH_tk64b46c28eda84a839b7ba10cc54f3525' > http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 > HTTP/1.1 204 No Content > X-Container-Object-Count: 1 > X-Container-Bytes-Used: 29 > Content-Length: 0 > Date: Tue, 05 Apr 2011 10:20:40 GMT > > [shashi at shashi samples]$ > > > > Initially I have created a container named as "container1" using the admin > user "test:tester" and then trying to set read and write acl for the > container1 to share it with non-admin user .......... > > > > [shashi at shashi samples]$ curl -v -H 'X-Auth-Token: > AUTH_tk64b46c28eda84a839b7ba10cc54f3525' -H 'X-Container-Read: test:tester3' > -H 'X-Container-Write: test:tester3' > http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 > * About to connect() to 192.168.62.63 port 8080 > * Trying 192.168.62.63... connected > * Connected to 192.168.62.63 (192.168.62.63) port 8080 > > GET /v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1 HTTP/1.1 > > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 > OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > > Host: 192.168.62.63:8080 > > Accept: */* > > X-Auth-Token: AUTH_tk64b46c28eda84a839b7ba10cc54f3525 > > X-Container-Read: test:tester3 > > X-Container-Write: test:tester3 > > > < HTTP/1.1 200 OK > < X-Container-Object-Count: 1 > < X-Container-Bytes-Used: 29 > < Content-Length: 10 > < Content-Type: text/plain; charset=utf8 > < Date: Tue, 05 Apr 2011 10:11:01 GMT > testfile1 > * Connection #0 to host 192.168.62.63 left intact > * Closing connection #0 > [shashi at shashi samples]$ > > [shashi at shashi samples]$ curl -v -H 'X-Storage-User: test:tester3' -H > 'X-Storage-Pass: testing3' http://192.168.62.63:8080/auth/v1.0* About to > connect() to 192.168.62.63 port 8080 > * Trying 192.168.62.63... connected > * Connected to 192.168.62.63 (192.168.62.63) port 8080 > > GET /auth/v1.0 HTTP/1.1 > > User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 > OpenSSL/0.9.7a zlib/1.2.3 libidn/0.6.14 > > Host: 192.168.62.63:8080 > > Accept: */* > > X-Storage-User: test:tester3 > > X-Storage-Pass: testing3 > > > < HTTP/1.1 200 OK > < X-Storage-Url: > http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a > < X-Storage-Token: AUTH_tk124a8a19ad7e49c5a04710716fd4f126 > < X-Auth-Token: AUTH_tk124a8a19ad7e49c5a04710716fd4f126 > < Content-Length: 112 > < Date: Tue, 05 Apr 2011 10:11:16 GMT > Connection #0 to host 192.168.62.63 left intact > * Closing connection #0 > {"storage": {"default": "local", "local": " > http://127.0.0.1:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a > "}}[shashi at shashi samples]$ > > [shashi at shashi samples]$ curl -s -D - -H 'X-Auth-Token: > AUTH_tk124a8a19ad7e49c5a04710716fd4f126' > http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a/container1/testfile1 > HTTP/1.1 403 Forbidden > Content-Length: 157 > Content-Type: text/html; charset=UTF-8 > Date: Tue, 05 Apr 2011 10:11:42 GMT > > > > 403 Forbidden > > >

403 Forbidden

> Access was denied to this resource.

> > > > > [shashi at shashi samples]$ > [shashi at shashi samples]$ > > Thanks & Regards, > shashi > > > > > > On Fri, Apr 1, 2011 at 6:32 PM, Greg Holt wrote: > >> On Apr 1, 2011, at 1:35 AM, shashidhar v wrote: >> >> > In the above script, the third user is tester3 (non admin) which is not >> allowed to create containers ? Then what's the role of non-admin users >> created under swift , what operations they can perform ? >> > >> > Swift supports ACL or not and the containers/objects created by a admin >> user can be shared with non-admin user for atleast downloading the objects ? >> >> Non-admin users can only perform operations per container based on the >> container?s X-Container-Read and X-Container-Write ACLs. With an admin >> account you could create a container for that non-admin user and set >> X-Container-Read: test:tester3 and X-Container-Write: test:tester3. >> >> These may explain more: >> >> http://swift.openstack.org/overview_auth.html >> http://swift.openstack.org/misc.html#module-swift.common.middleware.acl >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gholt at rackspace.com Tue Apr 5 19:48:14 2011 From: gholt at rackspace.com (Greg Holt) Date: Tue, 5 Apr 2011 14:48:14 -0500 Subject: [Openstack-operators] failed to run the auth-server deamon for SAIO setup In-Reply-To: References: <4696C6EF-36BE-4D7D-939F-FD7364A2AAB8@zeroaccess.org> <43C2F369-B701-4163-8805-EA6657742D9E@rackspace.com> Message-ID: On Apr 5, 2011, at 9:03 AM, shashidhar v wrote: > 2) How to create new accounts/users using the admin "reseller" which was created using the script "recreateaccounts" of SAIO > > swift at test3:~/swift/trunk$ swauth-add-user -U reseller:reseller -K reseller -A http://192.168.62.63:8080/auth/v1.0 reseller user1 user1 This one was closest. The -A ADMIN_URL should be -A http://192.168.62.63:8080/auth/ I often forget too, but if you run swauth-add-user with no options it has an example for a reminder. > 3) Is it possible to enforce the storage limit for a non admin account/user in swift , if so how to set that storage limit for a user ? How to distribute the available storage among different users ? Swift currently does not have quota support (limiting how much space a user can use). It's on the list, but not yet on a specific roadmap. Here at Rackspace we just make sure to mount new hard drives faster than folks can upload. :) -------------- next part -------------- An HTML attachment was scrubbed... URL: From shashidhar.velagandula at gmail.com Wed Apr 6 06:53:34 2011 From: shashidhar.velagandula at gmail.com (shashidhar v) Date: Wed, 6 Apr 2011 12:23:34 +0530 Subject: [Openstack-operators] Swift - usage of JAVA apis bindings from rackspace ?? Message-ID: Hi, I am trying to build the "rackspace-java-cloudfiles" package (JAVA apis) and run the unit tests ... but getting the errors [shashi at shashi rackspace-java-cloudfiles-1fb920d]$ cat src/test/resources/cloudfiles.properties # user properties username=tester password=testing account=test # Auth Info, including two headers that can change for different auth services #auth_url=http://test1:8080/auth/v1 auth_token_name=X-Auth-Token auth_url= http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a auth_user_header=tester auth_pass_header=testing auth_user_header=X-Storage-User auth_pass_header=X-Storage-Pass # cloudfs properties version=v1 connection_timeout=15000 [shashi at shashi rackspace-java-cloudfiles-1fb920d]$ ant test Buildfile: build.xml init: [echo] ------------------------------------------------- [echo] Building Cloudfiles [echo] ------------------------------------------------- compile: [echo] Compiling the source [jar] Building jar: /home/shashi/Desktop/rackspace-java-cloudfiles-1fb920d/dist/java-cloudfiles.jar compile-test: [echo] Compiling the test source [copy] Copying 1 file to /home/shashi/Desktop/rackspace-java-cloudfiles-1fb920d/classes [jar] Building jar: /home/shashi/Desktop/rackspace-java-cloudfiles-1fb920d/dist/java-cloudfiles-test.jar test: [junit] Running com.rackspacecloud.client.cloudfiles.FilesClientTestCase [junit] Testsuite: com.rackspacecloud.client.cloudfiles.FilesClientTestCase [junit] Tests run: 44, Failures: 42, Errors: 0, Time elapsed: 1.606 sec [junit] Tests run: 44, Failures: 42, Errors: 0, Time elapsed: 1.606 sec [junit] [junit] ------------- Standard Error ----------------- [junit] java.lang.IllegalStateException: Target host must not be null, or set in parameters. [junit] at org.apache.http.impl.client.DefaultRequestDirector.determineRoute(DefaultRequestDirector.java:651) [junit] at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:353) [junit] at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641) [junit] at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:576) [junit] at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:554) [junit] at com.rackspacecloud.client.cloudfiles.FilesClient.login(FilesClient.java:278) [junit] at com.rackspacecloud.client.cloudfiles.FilesClientTestCase.testUnicodeContainer(FilesClientTestCase.java:1401) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at java.lang.reflect.Method.invoke(Method.java:597) [junit] at junit.framework.TestCase.runTest(TestCase.java:164) [junit] at junit.framework.TestCase.runBare(TestCase.java:130) [junit] at junit.framework.TestResult$1.protect(TestResult.java:106) [junit] at junit.framework.TestResult.runProtected(TestResult.java:124) [junit] at junit.framework.TestResult.run(TestResult.java:109) [junit] at junit.framework.TestCase.run(TestCase.java:120) [junit] at junit.framework.TestSuite.runTest(TestSuite.java:230) [junit] at junit.framework.TestSuite.run(TestSuite.java:225) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:421) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask.java:1245) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:814) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1657) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:765) [junit] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) [junit] at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at java.lang.reflect.Method.invoke(Method.java:597) [junit] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105) [junit] at org.apache.tools.ant.Task.perform(Task.java:348) [junit] at org.apache.tools.ant.Target.execute(Target.java:357) [junit] at org.apache.tools.ant.Target.performTasks(Target.java:385) [junit] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329) [junit] at org.apache.tools.ant.Project.executeTarget(Project.java:1298) [junit] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) [junit] at org.apache.tools.ant.Project.executeTargets(Project.java:1181) [junit] at org.apache.tools.ant.Main.runBuild(Main.java:698) [junit] at org.apache.tools.ant.Main.startAnt(Main.java:199) [junit] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) [junit] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) [junit] java.lang.IllegalStateException: Target host must not be null, or set in parameters. [junit] at org.apache.http.impl.client.DefaultRequestDirector.determineRoute(DefaultRequestDirector.java:651) [junit] at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:353) [junit] at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641) [junit] at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:576) [junit] at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:554) [junit] at com.rackspacecloud.client.cloudfiles.FilesClient.login(FilesClient.java:278) [junit] at com.rackspacecloud.client.cloudfiles.FilesClientTestCase.testUnicode(FilesClientTestCase.java:1432) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at java.lang.reflect.Method.invoke(Method.java:597) [junit] at junit.framework.TestCase.runTest(TestCase.java:164) [junit] at junit.framework.TestCase.runBare(TestCase.java:130) [junit] at junit.framework.TestResult$1.protect(TestResult.java:106) [junit] at junit.framework.TestResult.runProtected(TestResult.java:124) [junit] at junit.framework.TestResult.run(TestResult.java:109) [junit] at junit.framework.TestCase.run(TestCase.java:120) [junit] at junit.framework.TestSuite.runTest(TestSuite.java:230) [junit] at junit.framework.TestSuite.run(TestSuite.java:225) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:421) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask.java:1245) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:814) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1657) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:765) [junit] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) [junit] at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at java.lang.reflect.Method.invoke(Method.java:597) [junit] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105) [junit] at org.apache.tools.ant.Task.perform(Task.java:348) [junit] at org.apache.tools.ant.Target.execute(Target.java:357) [junit] at org.apache.tools.ant.Target.performTasks(Target.java:385) [junit] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329) [junit] at org.apache.tools.ant.Project.executeTarget(Project.java:1298) [junit] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) [junit] at org.apache.tools.ant.Project.executeTargets(Project.java:1181) [junit] at org.apache.tools.ant.Main.runBuild(Main.java:698) [junit] at org.apache.tools.ant.Main.startAnt(Main.java:199) [junit] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) [junit] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) [junit] ------------- ---------------- --------------- [junit] Testcase: testLogin(com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] null [junit] junit.framework.AssertionFailedError [junit] at com.rackspacecloud.client.cloudfiles.FilesClientTestCase.testLogin(FilesClientTestCase.java:68) [junit] [junit] [junit] Testcase: testAccountInfo(com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] null [junit] junit.framework.AssertionFailedError [junit] at com.rackspacecloud.client.cloudfiles.FilesClientTestCase.testAccountInfo(FilesClientTestCase.java:92) [junit] [junit] [junit] Testcase: testMultipleFilesNotThere(com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] null =============== ======= ===== [junit] [junit] Testcase: testFilesObjectPath(com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] null [junit] junit.framework.AssertionFailedError [junit] at com.rackspacecloud.client.cloudfiles.FilesClientTestCase.testFilesObjectPath(FilesClientTestCase.java:1783) [junit] [junit] [junit] Testcase: testURLs(com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] null [junit] junit.framework.AssertionFailedError [junit] at com.rackspacecloud.client.cloudfiles.FilesClientTestCase.testURLs(FilesClientTestCase.java:1826) [junit] [junit] [junit] Test com.rackspacecloud.client.cloudfiles.FilesClientTestCase FAILED BUILD SUCCESSFUL Total time: 5 seconds [shashi at shashi rackspace-java-cloudfiles-1fb920d]$ I was not clear about the properties to be set for running the "unit tests" of rackspace cloud files - java apis package , kindly help me for usage of java apis w.r.t swift Thanks & Regards, shashi -------------- next part -------------- An HTML attachment was scrubbed... URL: From gholt at rackspace.com Wed Apr 6 12:38:46 2011 From: gholt at rackspace.com (Greg Holt) Date: Wed, 6 Apr 2011 07:38:46 -0500 Subject: [Openstack-operators] Swift - usage of JAVA apis bindings from rackspace ?? In-Reply-To: References: Message-ID: <9F3F24EB-446F-444C-80E2-834384F11931@rackspace.com> On Apr 6, 2011, at 1:53 AM, shashidhar v wrote: > I am trying to build the "rackspace-java-cloudfiles" package (JAVA apis) and run the unit tests ... but getting the errors Ah, you're outside my knowledge area as I haven't used those bindings myself for quite a while, and then only briefly, and then it was with Rackspace Cloud Files not Swift. If I get some time I'll see if I can figure it out and get back to you. From shashidhar.velagandula at gmail.com Wed Apr 6 14:06:06 2011 From: shashidhar.velagandula at gmail.com (shashidhar v) Date: Wed, 6 Apr 2011 19:36:06 +0530 Subject: [Openstack-operators] talking to swift with cyberduck - failed to build the cyberduck source ?? Message-ID: Hi , I was trying to build the cyberduck to interface with the swift , I followed the steps from doc http://swift.openstack.org/howto_cyberduck.html upto step 5 I did as per the doc ,,,, but step 6 failed to build it ... step 4 : I have used the auth_url as http://192.168.62.63:8080/auth/v1.0in the file " lib/cloudfiles.properties" step 5: updated the "source/ch/cyberduck/core/Protocol.java" file public boolean isHostnameConfigurable() { return true; } step 6: trying to build the cyberduck ,,,, since I am using windows , I used the command "ant dll" C:\Users\Admin\Desktop\shashi\cyberduck-src-3.8.1\3.8.1>ant dll Buildfile: C:\Users\Admin\Desktop\shashi\cyberduck-src-3.8.1\3.8.1\build.xml [taskdef] Could not load definitions from resource net/sf/antcontrib/antcontri b.properties. It could not be found. revision: [echo] Calculating revision... [echo] _REVISION_=exported [echo] Build number 11 version: BUILD FAILED C:\Users\Admin\Desktop\shashi\cyberduck-src-3.8.1\3.8.1\build-windows.xml:60: Pr oblem: failed to create task or type propertyregex Cause: The name is undefined. Action: Check the spelling. Action: Check that any custom tasks/types have been declared. Action: Check that any / declarations have taken place. Total time: 0 seconds Kindly help me to resolve the error Thanks & Regards, shashi -------------- next part -------------- An HTML attachment was scrubbed... URL: From btorch-os at zeroaccess.org Mon Apr 11 15:28:13 2011 From: btorch-os at zeroaccess.org (Marcelo Martins) Date: Mon, 11 Apr 2011 10:28:13 -0500 Subject: [Openstack-operators] Swift - usage of JAVA apis bindings from rackspace ?? In-Reply-To: References: Message-ID: Shashidhar, PS -> had to remove your original post in the email due to a 40KB message body limitation on the list. I'm don't think the java-cloudfiles API currently works with openstack- swift authentication system. I tried to use the latest version 1.8.1 and also 1.8.0 but was encountering other problems that was prohibiting me from even reaching my openstack-swift SAIO system. So I decided to give it a try on an older version I already had installed (1.5.3 ... I know it's old) ... Problem #1 : Using SSL with java sucks .. I didn't feel like troubleshooting java keytool, so I changed my SAIO setup to no longer use SSL in my proxy-server. Problem #2: Had to hack two files in order to make authentication work FILE #1 = src/main/java/com/rackspacecloud/client/cloudfiles/ FilesClient.java -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 377-openstack/src/main/java/com/rackspacecloud/client/cloudfiles/ FilesClient.java --- rackspace-java-cloudfiles-0ce9377/src/main/java/com/rackspacecloud/ client/cloudfiles/FilesClient.java 2010-02-08 17:46:42.000000000 -0600 +++ rackspace-java-cloudfiles-0ce9377-openstack/src/main/java/com/ rackspacecloud/client/cloudfiles/FilesClient.java 2011-04-09 21:36:32.110095891 -0500 @@ -115,8 +115,10 @@ this.username = username; this.password = password; this.account = account; + if (account != null && account.length() > 0) { - this.authenticationURL = FilesUtil.getProperty("auth_url")+VERSION+"/"+account +FilesUtil.getProperty("auth_url_post"); + this.authenticationURL = FilesUtil.getProperty("auth_url"); + this.username = account+":"+username; } else { this.authenticationURL = FilesUtil.getProperty("auth_url"); @@ -192,7 +194,7 @@ { this.account = account; if (account != null && account.length() > 0) { - this.authenticationURL = FilesUtil.getProperty("auth_url")+VERSION+"/"+account +FilesUtil.getProperty("auth_url_post"); + this.authenticationURL = FilesUtil.getProperty("auth_url"); } else { this.authenticationURL = FilesUtil.getProperty("auth_url"); -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- FILE #2 = src/main/java/com/rackspacecloud/client/cloudfiles/ FilesResponse.java -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- e9377-openstack/src/main/java/com/rackspacecloud/client/cloudfiles/ FilesResponse.java --- rackspace-java-cloudfiles-0ce9377/src/main/java/com/rackspacecloud/ client/cloudfiles/FilesResponse.java 2010-02-08 17:46:42.000000000 -0600 +++ rackspace-java-cloudfiles-0ce9377-openstack/src/main/java/com/ rackspacecloud/client/cloudfiles/FilesResponse.java 2011-04-09 20:56:22.826095729 -0500 @@ -51,7 +51,8 @@ if (getStatusCode() == HttpStatus.SC_UNAUTHORIZED ) return false; - if (getStatusCode() == HttpStatus.SC_NO_CONTENT) + /* Marcelo if (getStatusCode() == HttpStatus.SC_NO_CONTENT) */ + if (getStatusCode() == HttpStatus.SC_OK) return true; return false; -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Once I was done with modifying the files I compiled it with "ant compile" Then I created my "cloudfiles.properties" file ---------------------------------------------------------------------------------------------- version=v1 connection_timeout=5000 # Auth info auth_url=http://MY_IP_ADDRR:8080/auth/v1.0 auth_token_name=X-Auth-Token #auth_user_header=X-Auth-User #auth_pass_header=X-Auth-Key ---------------------------------------------------------------------------------------------- Then I tested the java api using the run_cli.sh btorch at stone:~/src/rackspace-java-cloudfiles-0ce9377-openstack$ bash run_cli.sh Username: marcelo Password: XXXXXXXXXX Account (return if using Mosso directly): external Logged in! Type 'help' for assistance external: get The account has 3 containers glance images test external: head Account information: Number of Containers: 3 Total Account Size: 1938161664 external: head glance Information for glance Object Count: 2 Total Size: 1,938,161,664 bytes .... Then I ran the test unit... I also expected any CDN test units to fail since openstack-swift does not have CDN: btorch at stone:~/src/rackspace-java-cloudfiles-0ce9377-openstack$ ant test Buildfile: build.xml init: [echo] ------------------------------------------------- [echo] Building Cloudfiles [echo] ------------------------------------------------- compile: [echo] Compiling the source compile-test: [echo] Compiling the test source [javac] Compiling 2 source files to /home/btorch/src/rackspace- java-cloudfiles-0ce9377-openstack/classes [copy] Copying 2 files to /home/btorch/src/rackspace-java- cloudfiles-0ce9377-openstack/classes [jar] Building jar: /home/btorch/src/rackspace-java- cloudfiles-0ce9377-openstack/dist/java-cloudfiles-test.jar test: [junit] Running com.rackspacecloud.client.cloudfiles.FilesClientTestCase [junit] Testsuite: com.rackspacecloud.client.cloudfiles.FilesClientTestCase [junit] Tests run: 38, Failures: 8, Errors: 0, Time elapsed: 30.824 sec [junit] Tests run: 38, Failures: 8, Errors: 0, Time elapsed: 30.824 sec [junit] [junit] Testcase: testConstructor (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] expected:<...> but was: [junit] junit.framework.ComparisonFailure: expected:<...> but was: [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase.testConstructor(FilesClientTestCase.java:49) [junit] [junit] [junit] Testcase: testNoArgConstructor (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] expected:<...> but was: [junit] junit.framework.ComparisonFailure: expected:<...> but was: [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase.testNoArgConstructor(FilesClientTestCase.java:59) [junit] [junit] [junit] [junit] Testcase: testCDNContainerList (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase.testCDNContainerList(FilesClientTestCase.java:1242) [junit] [junit] [junit] Testcase: testCDNContainerListLimitMarker (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase .testCDNContainerListLimitMarker(FilesClientTestCase.java:1268) [junit] [junit] [junit] Testcase: testCDNContainerFullListing (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase .testCDNContainerFullListing(FilesClientTestCase.java:1293) [junit] [junit] [junit] Testcase: testCDNContainerFullListingAll (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase .testCDNContainerFullListingAll(FilesClientTestCase.java:1307) [junit] [junit] [junit] Testcase: testCDNApi (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles.FilesClientTestCase.testCDNApi(FilesClientTestCase.java: 1366) [junit] [junit] [junit] Testcase: testURLs (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] null [junit] junit.framework.AssertionFailedError [junit] at com .rackspacecloud .client .cloudfiles.FilesClientTestCase.testURLs(FilesClientTestCase.java:1526) [junit] [junit] [junit] Test com.rackspacecloud.client.cloudfiles.FilesClientTestCase FAILED BUILD SUCCESSFUL Total time: 34 seconds ----- I'm not sure why the newer versions of the java-cloudfiles API were failing, perhaps I was doing something wrong! I hope this helps a bit or perhaps sends you to the right track. If I have an update about java-cloudfiles and openstack-swift compatibility I'll let you know. Marcelo Martins Openstack-swift btorch-os at zeroaccess.org ?Knowledge is the wings on which our aspirations take flight and soar. When it comes to surfing and life if you know what to do you can do it. If you desire anything become educated about it and succeed. ? > > Thanks & Regards, > shashi > _______________________________________________ > Openstack-operators mailing list > Openstack-operators at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack- > operators -------------- next part -------------- An HTML attachment was scrubbed... URL: From jinzishuai at gmail.com Sun Apr 24 20:23:31 2011 From: jinzishuai at gmail.com (Shi Jin) Date: Sun, 24 Apr 2011 14:23:31 -0600 Subject: [Openstack-operators] nova-objectstore not working (http 500 error) on RHEL-6 Message-ID: Hi there, I am having trouble connecting to nova-objectstore running on RHEL-6, which runs perfectly fine on a Ubuntu installation. I got the following using S3_Curl * About to connect() to 192.168.2.4 port 3333 (#0) * Trying 192.168.2.4... connected * Connected to 192.168.2.4 (192.168.2.4) port 3333 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/ 3.12.6.2 zlib/1.2.3 libidn/1.18 libssh2/1.2.2 > Host: 192.168.2.4:3333 > Accept: */* > Date: Sun, 24 Apr 2011 20:11:47 +0000 > Authorization: AWS 5ffcff0a-f879-41b7-b4c0-5f5f9e26856b:IRT:6/nldG738bkYk3bpKZt42hKFRr8= > < HTTP/1.1 500 Internal Server Error < Content-Type: text/plain < Content-Length: 1106 < Date: Sun, 24 Apr 2011 20:11:47 GMT < Connection: close < Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/eventlet/wsgi.py", line 336, in handle_one_response result = self.application(self.environ, start_response) File "/usr/lib/python2.6/site-packages/webob/dec.py", line 159, in __call__ return resp(environ, start_response) File "/usr/lib/python2.6/site-packages/routes/middleware.py", line 131, in __call__ response = self.app(environ, start_response) File "/usr/lib/python2.6/site-packages/webob/dec.py", line 159, in __call__ return resp(environ, start_response) File "/usr/lib/python2.6/site-packages/nova/objectstore/s3server.py", line 72, in controller=lambda *a, **kw: RootHandler(self)(*a, **kw)) File "/usr/lib/python2.6/site-packages/webob/dec.py", line 147, in __call__ resp = self.call_func(req, *args, **self.kwargs) File "/usr/lib/python2.6/site-packages/webob/dec.py", line 208, in call_func return self.func(req, *args, **kwargs) File "/usr/lib/python2.6/site-packages/nova/objectstore/s3server.py", line 128, in __call__ del params['action'] KeyError: 'action' * Closing connection #0 I cannot find anything useful from the log file either. [root at openstack-controller nova]# cat nova-objectstore.log 2011-04-24 14:09:20,197 DEBUG routes.middleware [-] Initialized with method overriding = True, and path info altering = True from (pid=26724) __init__ /usr/lib/python2.6/site-packages/routes/middleware.py:41 2011-04-24 14:09:20,197 AUDIT nova [-] Starting /usr/bin/nova-objectstore on 192.168.2.4:3333 2011-04-24 14:11:35,121 DEBUG routes.middleware [-] Matched GET / from (pid=26724) __call__ /usr/lib/python2.6/site-packages/routes/middleware.py:100 2011-04-24 14:11:35,121 DEBUG routes.middleware [-] Route path: '/', defaults: {'controller': at 0x127fc08>} from (pid=26724) __call__ /usr/lib/python2.6/site-packages/routes/middleware.py:102 2011-04-24 14:11:35,122 DEBUG routes.middleware [-] Match dict: {'controller': at 0x127fc08>} from (pid=26724) __call__ /usr/lib/python2.6/site-packages/routes/middleware.py:103 2011-04-24 14:11:47,175 DEBUG routes.middleware [-] Matched GET / from (pid=26724) __call__ /usr/lib/python2.6/site-packages/routes/middleware.py:100 2011-04-24 14:11:47,175 DEBUG routes.middleware [-] Route path: '/', defaults: {'controller': at 0x127fc08>} from (pid=26724) __call__ /usr/lib/python2.6/site-packages/routes/middleware.py:102 2011-04-24 14:11:47,175 DEBUG routes.middleware [-] Match dict: {'controller': at 0x127fc08>} from (pid=26724) __call__ /usr/lib/python2.6/site-packages/routes/middleware.py:103 BTW, The service of nova-objectstore runs fine and listens to the 3333 port. Has anyone had any experience with the rpm package for RHEL-6 installed following this documentation: http://docs.openstack.org/trunk/openstack-compute-admin/content/installing-openstack-compute-on-rhel6.html ? Thanks a lot. Shi -- Shi Jin, Ph.D. -------------- next part -------------- An HTML attachment was scrubbed... URL: From shashidhar.velagandula at gmail.com Tue Apr 26 13:22:16 2011 From: shashidhar.velagandula at gmail.com (shashidhar v) Date: Tue, 26 Apr 2011 18:52:16 +0530 Subject: [Openstack-operators] cyberduck interface to swift ?? Message-ID: Hi, I have deployed swift-1.4 dev(SAIO) service running on a test node , able to create the accounts and do upload/download of files using the "st" tool by following doc of SAIO Test node swift service is enabled with SSL using self signed certs. and uses swauth authentication And, then I have installed the Cyberduck-Installer-4.0.2.exe on windows xp and windows vista machines , but when I open connection to swift service running on test node it throws error as login failed swift at test3:~$ swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0 -U system:root -K testpass stat Account: AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f Containers: 0 Objects: 0 Bytes: 0 Accept-Ranges: bytes swift at test3:~$ swift at test3:~$ swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0 -U system:root -K testpass list swift at test3:~$ swift at test3:~$ curl -k -v -H 'X-Storage-User: system:root' -H 'X-Storage-Pass: testpass' https://192.168.62.63:8080/auth/v1.0 * About to connect() to 192.168.62.63 port 8080 (#0) * Trying 192.168.62.63... connected * Connected to 192.168.62.63 (192.168.62.63) port 8080 (#0) * successfully set certificate verify locations: * CAfile: none CApath: /etc/ssl/certs * SSLv3, TLS handshake, Client hello (1): * SSLv3, TLS handshake, Server hello (2): * SSLv3, TLS handshake, CERT (11): * SSLv3, TLS handshake, Server finished (14): * SSLv3, TLS handshake, Client key exchange (16): * SSLv3, TLS change cipher, Client hello (1): * SSLv3, TLS handshake, Finished (20): * SSLv3, TLS change cipher, Client hello (1): * SSLv3, TLS handshake, Finished (20): * SSL connection using AES256-SHA * Server certificate: * subject: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in * start date: 2011-04-25 05:45:12 GMT * expire date: 2011-05-25 05:45:12 GMT * common name: swift (does not match '192.168.62.63') * issuer: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in * SSL certificate verify result: self signed certificate (18), continuing anyway. > GET /auth/v1.0 HTTP/1.1 > User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15 > Host: 192.168.62.63:8080 > Accept: */* > X-Storage-User: system:root > X-Storage-Pass: testpass > < HTTP/1.1 200 OK < X-Storage-Url: https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f < X-Storage-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 < X-Auth-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 < Content-Length: 117 < Date: Tue, 26 Apr 2011 12:48:39 GMT < * Connection #0 to host 192.168.62.63 left intact * Closing connection #0 * SSLv3, TLS alert, Client hello (1): {"storage": {"default": "local", "local": " https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f "}}swift at test3:~$ swift at test3:~$ Using st tool I am able upload/download the files but using cyberduck interface , login itself is failed Kindly help me to resolve this login error , any doc. which describes about cyberduck interface to swift will be helpful I have checked the related doc. present under http://swift.openstack.org/howto_cyberduck.html but it describes about source build of cyberduck not the binary version Is it possible to specify "http" protocol instead of "https" using cyerduck to contact swift service ? kindly help me Thanks & Regards, shashi -------------- next part -------------- An HTML attachment was scrubbed... URL: From jinzishuai at gmail.com Tue Apr 26 18:17:54 2011 From: jinzishuai at gmail.com (Shi Jin) Date: Tue, 26 Apr 2011 12:17:54 -0600 Subject: [Openstack-operators] cyberduck interface to swift ?? In-Reply-To: References: Message-ID: I was able to login to swift using https, just have to confirm continue when cyberduck prompts about the SSL self signed certificate. I am also curious about having cyberduck to connect to S3 with plain http instead of https. Shi On Tue, Apr 26, 2011 at 7:22 AM, shashidhar v < shashidhar.velagandula at gmail.com> wrote: > Hi, > > I have deployed swift-1.4 dev(SAIO) service running on a test node , able > to create the accounts and do upload/download of files using the "st" tool > by following doc of SAIO > Test node swift service is enabled with SSL using self signed certs. and > uses swauth authentication > > And, then I have installed the Cyberduck-Installer-4.0.2.exe on windows xp > and windows vista machines , but when I open connection to swift service > running on test node it throws error as login failed > > swift at test3:~$ swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0-U system:root -K testpass stat > Account: AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f > Containers: 0 > Objects: 0 > Bytes: 0 > Accept-Ranges: bytes > swift at test3:~$ > swift at test3:~$ > swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0 -U system:root > -K testpass list > swift at test3:~$ > swift at test3:~$ curl -k -v -H 'X-Storage-User: system:root' -H > 'X-Storage-Pass: testpass' https://192.168.62.63:8080/auth/v1.0 > * About to connect() to 192.168.62.63 port 8080 (#0) > * Trying 192.168.62.63... connected > * Connected to 192.168.62.63 (192.168.62.63) port 8080 (#0) > * successfully set certificate verify locations: > * CAfile: none > CApath: /etc/ssl/certs > * SSLv3, TLS handshake, Client hello (1): > * SSLv3, TLS handshake, Server hello (2): > * SSLv3, TLS handshake, CERT (11): > * SSLv3, TLS handshake, Server finished (14): > * SSLv3, TLS handshake, Client key exchange (16): > * SSLv3, TLS change cipher, Client hello (1): > * SSLv3, TLS handshake, Finished (20): > * SSLv3, TLS change cipher, Client hello (1): > * SSLv3, TLS handshake, Finished (20): > * SSL connection using AES256-SHA > * Server certificate: > * subject: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; > CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in > * start date: 2011-04-25 05:45:12 GMT > * expire date: 2011-05-25 05:45:12 GMT > * common name: swift (does not match '192.168.62.63') > * issuer: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; > CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in > * SSL certificate verify result: self signed certificate (18), > continuing anyway. > > GET /auth/v1.0 HTTP/1.1 > > User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k > zlib/1.2.3.3 libidn/1.15 > > Host: 192.168.62.63:8080 > > Accept: */* > > X-Storage-User: system:root > > X-Storage-Pass: testpass > > > < HTTP/1.1 200 OK > < X-Storage-Url: > https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f > < X-Storage-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 > < X-Auth-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 > < Content-Length: 117 > < Date: Tue, 26 Apr 2011 12:48:39 GMT > < > * Connection #0 to host 192.168.62.63 left intact > * Closing connection #0 > * SSLv3, TLS alert, Client hello (1): > {"storage": {"default": "local", "local": " > https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f > "}}swift at test3:~$ > swift at test3:~$ > > > Using st tool I am able upload/download the files but using cyberduck > interface , login itself is failed > > Kindly help me to resolve this login error , any doc. which describes > about cyberduck interface to swift will be helpful > > I have checked the related doc. present under > http://swift.openstack.org/howto_cyberduck.html but it describes about > source build of cyberduck not the binary version > > Is it possible to specify "http" protocol instead of "https" using > cyerduck to contact swift service ? > kindly help me > > Thanks & Regards, > shashi > > > _______________________________________________ > Openstack-operators mailing list > Openstack-operators at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > -- Shi Jin, Ph.D. -------------- next part -------------- An HTML attachment was scrubbed... URL: From btorch-os at zeroaccess.org Sun Apr 10 02:55:42 2011 From: btorch-os at zeroaccess.org (Marcelo Martins) Date: Sun, 10 Apr 2011 02:55:42 -0000 Subject: [Openstack-operators] *****SPAM***** Re: Swift - usage of JAVA apis bindings from rackspace ?? In-Reply-To: References: Message-ID: <078F41C1-0386-40CE-B75A-F846C9D8CB69@zeroaccess.org> Shashidhar, I'm don't think the java-cloudfiles API currently works with openstack- swift authentication system. I tried to use the latest version 1.8.1 and also 1.8.0 but was encountering other problems that was prohibiting me from even reaching my openstack-swift SAIO system. So I decided to give it a try on an older version I already had installed (1.5.3 ... I know it's old) ... Problem #1 : Using SSL with java sucks .. I didn't feel like troubleshooting java keytool, so I changed my SAIO setup to no longer use SSL in my proxy-server. Problem #2: Had to hack two files in order to make authentication work FILE #1 = src/main/java/com/rackspacecloud/client/cloudfiles/ FilesClient.java -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 377-openstack/src/main/java/com/rackspacecloud/client/cloudfiles/ FilesClient.java --- rackspace-java-cloudfiles-0ce9377/src/main/java/com/rackspacecloud/ client/cloudfiles/FilesClient.java 2010-02-08 17:46:42.000000000 -0600 +++ rackspace-java-cloudfiles-0ce9377-openstack/src/main/java/com/ rackspacecloud/client/cloudfiles/FilesClient.java 2011-04-09 21:36:32.110095891 -0500 @@ -115,8 +115,10 @@ this.username = username; this.password = password; this.account = account; + if (account != null && account.length() > 0) { - this.authenticationURL = FilesUtil.getProperty("auth_url")+VERSION+"/"+account +FilesUtil.getProperty("auth_url_post"); + this.authenticationURL = FilesUtil.getProperty("auth_url"); + this.username = account+":"+username; } else { this.authenticationURL = FilesUtil.getProperty("auth_url"); @@ -192,7 +194,7 @@ { this.account = account; if (account != null && account.length() > 0) { - this.authenticationURL = FilesUtil.getProperty("auth_url")+VERSION+"/"+account +FilesUtil.getProperty("auth_url_post"); + this.authenticationURL = FilesUtil.getProperty("auth_url"); } else { this.authenticationURL = FilesUtil.getProperty("auth_url"); -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- FILE #2 = src/main/java/com/rackspacecloud/client/cloudfiles/ FilesResponse.java -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- e9377-openstack/src/main/java/com/rackspacecloud/client/cloudfiles/ FilesResponse.java --- rackspace-java-cloudfiles-0ce9377/src/main/java/com/rackspacecloud/ client/cloudfiles/FilesResponse.java 2010-02-08 17:46:42.000000000 -0600 +++ rackspace-java-cloudfiles-0ce9377-openstack/src/main/java/com/ rackspacecloud/client/cloudfiles/FilesResponse.java 2011-04-09 20:56:22.826095729 -0500 @@ -51,7 +51,8 @@ if (getStatusCode() == HttpStatus.SC_UNAUTHORIZED ) return false; - if (getStatusCode() == HttpStatus.SC_NO_CONTENT) + /* Marcelo if (getStatusCode() == HttpStatus.SC_NO_CONTENT) */ + if (getStatusCode() == HttpStatus.SC_OK) return true; return false; -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Once I was done with modifying the files I compiled it with "ant compile" Then I created my "cloudfiles.properties" file ---------------------------------------------------------------------------------------------- version=v1 connection_timeout=5000 # Auth info auth_url=http://MY_IP_ADDRR:8080/auth/v1.0 auth_token_name=X-Auth-Token #auth_user_header=X-Auth-User #auth_pass_header=X-Auth-Key ---------------------------------------------------------------------------------------------- Then I tested the java api using the run_cli.sh btorch at stone:~/src/rackspace-java-cloudfiles-0ce9377-openstack$ bash run_cli.sh Username: marcelo Password: XXXXXXXXXX Account (return if using Mosso directly): external Logged in! Type 'help' for assistance external: get The account has 3 containers glance images test external: head Account information: Number of Containers: 3 Total Account Size: 1938161664 external: head glance Information for glance Object Count: 2 Total Size: 1,938,161,664 bytes .... Then I ran the test unit... I also expected any CDN test units to fail since openstack-swift does not have CDN: btorch at stone:~/src/rackspace-java-cloudfiles-0ce9377-openstack$ ant test Buildfile: build.xml init: [echo] ------------------------------------------------- [echo] Building Cloudfiles [echo] ------------------------------------------------- compile: [echo] Compiling the source compile-test: [echo] Compiling the test source [javac] Compiling 2 source files to /home/btorch/src/rackspace- java-cloudfiles-0ce9377-openstack/classes [copy] Copying 2 files to /home/btorch/src/rackspace-java- cloudfiles-0ce9377-openstack/classes [jar] Building jar: /home/btorch/src/rackspace-java- cloudfiles-0ce9377-openstack/dist/java-cloudfiles-test.jar test: [junit] Running com.rackspacecloud.client.cloudfiles.FilesClientTestCase [junit] Testsuite: com.rackspacecloud.client.cloudfiles.FilesClientTestCase [junit] Tests run: 38, Failures: 8, Errors: 0, Time elapsed: 30.824 sec [junit] Tests run: 38, Failures: 8, Errors: 0, Time elapsed: 30.824 sec [junit] [junit] Testcase: testConstructor (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] expected:<...> but was: [junit] junit.framework.ComparisonFailure: expected:<...> but was: [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase.testConstructor(FilesClientTestCase.java:49) [junit] [junit] [junit] Testcase: testNoArgConstructor (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] expected:<...> but was: [junit] junit.framework.ComparisonFailure: expected:<...> but was: [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase.testNoArgConstructor(FilesClientTestCase.java:59) [junit] [junit] [junit] [junit] Testcase: testCDNContainerList (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase.testCDNContainerList(FilesClientTestCase.java:1242) [junit] [junit] [junit] Testcase: testCDNContainerListLimitMarker (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase .testCDNContainerListLimitMarker(FilesClientTestCase.java:1268) [junit] [junit] [junit] Testcase: testCDNContainerFullListing (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase .testCDNContainerFullListing(FilesClientTestCase.java:1293) [junit] [junit] [junit] Testcase: testCDNContainerFullListingAll (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles .FilesClientTestCase .testCDNContainerFullListingAll(FilesClientTestCase.java:1307) [junit] [junit] [junit] Testcase: testCDNApi (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] host parameter is null [junit] junit.framework.AssertionFailedError: host parameter is null [junit] at com .rackspacecloud .client .cloudfiles.FilesClientTestCase.testCDNApi(FilesClientTestCase.java: 1366) [junit] [junit] [junit] Testcase: testURLs (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED [junit] null [junit] junit.framework.AssertionFailedError [junit] at com .rackspacecloud .client .cloudfiles.FilesClientTestCase.testURLs(FilesClientTestCase.java:1526) [junit] [junit] [junit] Test com.rackspacecloud.client.cloudfiles.FilesClientTestCase FAILED BUILD SUCCESSFUL Total time: 34 seconds ----- btorch at stone:~/src/rackspace-java-cloudfiles-0ce9377-openstack$ ant test-report Buildfile: build.xml init: [echo] ------------------------------------------------- [echo] Building Cloudfiles [echo] ------------------------------------------------- compile: [echo] Compiling the source [jar] Building jar: /home/btorch/src/rackspace-java- cloudfiles-0ce9377-openstack/dist/java-cloudfiles.jar compile-test: [echo] Compiling the test source test-report: [mkdir] Created dir: /home/btorch/src/rackspace-java- cloudfiles-0ce9377-openstack/testreport [junit] Test com.rackspacecloud.client.cloudfiles.FilesClientTestCase FAILED [junitreport] Processing /home/btorch/src/rackspace-java- cloudfiles-0ce9377-openstack/testreport/TESTS-TestSuites.xml to /tmp/ null971541946 [junitreport] Loading stylesheet jar:file:/usr/share/ant/lib/ant- junit.jar!/org/apache/tools/ant/taskdefs/optional/junit/xsl/junit- frames.xsl [junitreport] Transform time: 1172ms [junitreport] Deleting: /tmp/null971541946 BUILD SUCCESSFUL Total time: 32 seconds I'm not sure why the newer versions of the java-cloudfiles API were failing, perhaps I was doing something wrong! I hope this helps a bit or perhaps sends you to the right track. If I have an update about java-cloudfiles and openstack-swift compatibility I'll let you know. - Marcelo ?Knowledge is the wings on which our aspirations take flight and soar. When it comes to surfing and life if you know what to do you can do it. If you desire anything become educated about it and succeed. ? On Apr 6, 2011, at 1:53 AM, shashidhar v wrote: > > Hi, > > I am trying to build the "rackspace-java-cloudfiles" package (JAVA > apis) and run the unit tests ... but getting the errors > > > > [shashi at shashi rackspace-java-cloudfiles-1fb920d]$ cat src/test/ > resources/cloudfiles.properties > > # user properties > username=tester > password=testing > account=test > > # Auth Info, including two headers that can change for different > auth services > #auth_url=http://test1:8080/auth/v1 > > auth_token_name=X-Auth-Token > auth_url=http://192.168.62.63:8080/v1/AUTH_74ac0809-6c3f-4a0b-a6c8-6a664477b32a > auth_user_header=tester > auth_pass_header=testing > auth_user_header=X-Storage-User > auth_pass_header=X-Storage-Pass > > # cloudfs properties > version=v1 > connection_timeout=15000 > > > > > > > [shashi at shashi rackspace-java-cloudfiles-1fb920d]$ ant test > Buildfile: build.xml > > init: > [echo] ------------------------------------------------- > [echo] Building Cloudfiles > [echo] ------------------------------------------------- > > compile: > [echo] Compiling the source > [jar] Building jar: /home/shashi/Desktop/rackspace-java- > cloudfiles-1fb920d/dist/java-cloudfiles.jar > > compile-test: > [echo] Compiling the test source > [copy] Copying 1 file to /home/shashi/Desktop/rackspace-java- > cloudfiles-1fb920d/classes > [jar] Building jar: /home/shashi/Desktop/rackspace-java- > cloudfiles-1fb920d/dist/java-cloudfiles-test.jar > > test: > [junit] Running > com.rackspacecloud.client.cloudfiles.FilesClientTestCase > [junit] Testsuite: > com.rackspacecloud.client.cloudfiles.FilesClientTestCase > [junit] Tests run: 44, Failures: 42, Errors: 0, Time elapsed: > 1.606 sec > [junit] Tests run: 44, Failures: 42, Errors: 0, Time elapsed: > 1.606 sec > [junit] > [junit] ------------- Standard Error ----------------- > [junit] java.lang.IllegalStateException: Target host must not be > null, or set in parameters. > [junit] at > org > .apache > .http > .impl > .client > .DefaultRequestDirector.determineRoute(DefaultRequestDirector.java: > 651) > [junit] at > org > .apache > .http > .impl > .client.DefaultRequestDirector.execute(DefaultRequestDirector.java: > 353) > [junit] at > org > .apache > .http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java: > 641) > [junit] at > org > .apache > .http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java: > 576) > [junit] at > org > .apache > .http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java: > 554) > [junit] at > com > .rackspacecloud.client.cloudfiles.FilesClient.login(FilesClient.java: > 278) > [junit] at > com > .rackspacecloud > .client > .cloudfiles > .FilesClientTestCase.testUnicodeContainer(FilesClientTestCase.java: > 1401) > [junit] at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [junit] at > sun > .reflect > .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [junit] at > sun > .reflect > .DelegatingMethodAccessorImpl > .invoke(DelegatingMethodAccessorImpl.java:25) > [junit] at java.lang.reflect.Method.invoke(Method.java:597) > [junit] at junit.framework.TestCase.runTest(TestCase.java:164) > [junit] at junit.framework.TestCase.runBare(TestCase.java:130) > [junit] at junit.framework.TestResult > $1.protect(TestResult.java:106) > [junit] at > junit.framework.TestResult.runProtected(TestResult.java:124) > [junit] at junit.framework.TestResult.run(TestResult.java:109) > [junit] at junit.framework.TestCase.run(TestCase.java:120) > [junit] at junit.framework.TestSuite.runTest(TestSuite.java: > 230) > [junit] at junit.framework.TestSuite.run(TestSuite.java:225) > [junit] at > org > .apache > .tools > .ant > .taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:421) > [junit] at > org > .apache > .tools > .ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask.java: > 1245) > [junit] at > org > .apache > .tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java: > 814) > [junit] at > org > .apache > .tools > .ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java: > 1657) > [junit] at > org > .apache > .tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java: > 765) > [junit] at > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) > [junit] at > sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > [junit] at > sun > .reflect > .DelegatingMethodAccessorImpl > .invoke(DelegatingMethodAccessorImpl.java:25) > [junit] at java.lang.reflect.Method.invoke(Method.java:597) > [junit] at > org > .apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java: > 105) > [junit] at org.apache.tools.ant.Task.perform(Task.java:348) > [junit] at org.apache.tools.ant.Target.execute(Target.java: > 357) > [junit] at > org.apache.tools.ant.Target.performTasks(Target.java:385) > [junit] at > org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329) > [junit] at > org.apache.tools.ant.Project.executeTarget(Project.java:1298) > [junit] at > org > .apache > .tools > .ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) > [junit] at > org.apache.tools.ant.Project.executeTargets(Project.java:1181) > [junit] at org.apache.tools.ant.Main.runBuild(Main.java:698) > [junit] at org.apache.tools.ant.Main.startAnt(Main.java:199) > [junit] at > org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) > [junit] at > org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) > [junit] java.lang.IllegalStateException: Target host must not be > null, or set in parameters. > [junit] at > org > .apache > .http > .impl > .client > .DefaultRequestDirector.determineRoute(DefaultRequestDirector.java: > 651) > [junit] at > org > .apache > .http > .impl > .client.DefaultRequestDirector.execute(DefaultRequestDirector.java: > 353) > [junit] at > org > .apache > .http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java: > 641) > [junit] at > org > .apache > .http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java: > 576) > [junit] at > org > .apache > .http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java: > 554) > [junit] at > com > .rackspacecloud.client.cloudfiles.FilesClient.login(FilesClient.java: > 278) > [junit] at > com > .rackspacecloud > .client > .cloudfiles.FilesClientTestCase.testUnicode(FilesClientTestCase.java: > 1432) > [junit] at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [junit] at > sun > .reflect > .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [junit] at > sun > .reflect > .DelegatingMethodAccessorImpl > .invoke(DelegatingMethodAccessorImpl.java:25) > [junit] at java.lang.reflect.Method.invoke(Method.java:597) > [junit] at junit.framework.TestCase.runTest(TestCase.java:164) > [junit] at junit.framework.TestCase.runBare(TestCase.java:130) > [junit] at junit.framework.TestResult > $1.protect(TestResult.java:106) > [junit] at > junit.framework.TestResult.runProtected(TestResult.java:124) > [junit] at junit.framework.TestResult.run(TestResult.java:109) > [junit] at junit.framework.TestCase.run(TestCase.java:120) > [junit] at junit.framework.TestSuite.runTest(TestSuite.java: > 230) > [junit] at junit.framework.TestSuite.run(TestSuite.java:225) > [junit] at > org > .apache > .tools > .ant > .taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:421) > [junit] at > org > .apache > .tools > .ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask.java: > 1245) > [junit] at > org > .apache > .tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java: > 814) > [junit] at > org > .apache > .tools > .ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java: > 1657) > [junit] at > org > .apache > .tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java: > 765) > [junit] at > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) > [junit] at > sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > [junit] at > sun > .reflect > .DelegatingMethodAccessorImpl > .invoke(DelegatingMethodAccessorImpl.java:25) > [junit] at java.lang.reflect.Method.invoke(Method.java:597) > [junit] at > org > .apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java: > 105) > [junit] at org.apache.tools.ant.Task.perform(Task.java:348) > [junit] at org.apache.tools.ant.Target.execute(Target.java: > 357) > [junit] at > org.apache.tools.ant.Target.performTasks(Target.java:385) > [junit] at > org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329) > [junit] at > org.apache.tools.ant.Project.executeTarget(Project.java:1298) > [junit] at > org > .apache > .tools > .ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) > [junit] at > org.apache.tools.ant.Project.executeTargets(Project.java:1181) > [junit] at org.apache.tools.ant.Main.runBuild(Main.java:698) > [junit] at org.apache.tools.ant.Main.startAnt(Main.java:199) > [junit] at > org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) > [junit] at > org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) > [junit] ------------- ---------------- --------------- > [junit] Testcase: > testLogin > (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): > FAILED > [junit] null > [junit] junit.framework.AssertionFailedError > [junit] at > com > .rackspacecloud > .client > .cloudfiles.FilesClientTestCase.testLogin(FilesClientTestCase.java:68) > [junit] > [junit] > [junit] Testcase: > testAccountInfo > (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): > FAILED > [junit] null > [junit] junit.framework.AssertionFailedError > [junit] at > com > .rackspacecloud > .client > .cloudfiles > .FilesClientTestCase.testAccountInfo(FilesClientTestCase.java:92) > [junit] > [junit] > [junit] Testcase: > testMultipleFilesNotThere > (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): > FAILED > [junit] null > > =============== > ======= > ===== > > > [junit] > [junit] Testcase: > testFilesObjectPath > (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): FAILED > [junit] null > [junit] junit.framework.AssertionFailedError > [junit] at > com > .rackspacecloud > .client > .cloudfiles > .FilesClientTestCase.testFilesObjectPath(FilesClientTestCase.java: > 1783) > [junit] > [junit] > [junit] Testcase: > testURLs > (com.rackspacecloud.client.cloudfiles.FilesClientTestCase): > FAILED > [junit] null > [junit] junit.framework.AssertionFailedError > [junit] at > com > .rackspacecloud > .client > .cloudfiles.FilesClientTestCase.testURLs(FilesClientTestCase.java: > 1826) > [junit] > [junit] > [junit] Test > com.rackspacecloud.client.cloudfiles.FilesClientTestCase FAILED > > BUILD SUCCESSFUL > Total time: 5 seconds > [shashi at shashi rackspace-java-cloudfiles-1fb920d]$ > > > I was not clear about the properties to be set for running the "unit > tests" of rackspace cloud files - java apis package , kindly help me > for usage of java apis w.r.t swift > > > Thanks & Regards, > shashi > _______________________________________________ > Openstack-operators mailing list > Openstack-operators at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack- > operators -------------- next part -------------- An HTML attachment was scrubbed... URL: From jrussell at thesba.com Tue Apr 26 16:02:12 2011 From: jrussell at thesba.com (Justin J. Russell) Date: Tue, 26 Apr 2011 09:02:12 -0700 Subject: [Openstack-operators] cyberduck interface to swift ?? In-Reply-To: References: Message-ID: <401C063992AB5C47B4AF4D8F2FC6C3090175A3F392FE@NTSEXCHA1CMB2.NTS.PHX1> I was able to connect to our own implementation of Swift using the following settings: Server: storage.webcontrolcenter.com Port: 11000 Username: AccountName:UserName Path: /auth The username is your account name + ":" + your username. For example, if your account name is "Account1" and your username is "User1" then your username in Cyberduck is Account1:User1. I hope this helps. Thank you, Justin J. Russell | Vice President of Product Development of Technology Services [cid:image001.png at 01CC03F0.9FF6AE80] From: openstack-operators-bounces at lists.openstack.org [mailto:openstack-operators-bounces at lists.openstack.org] On Behalf Of shashidhar v Sent: Tuesday, April 26, 2011 6:22 AM To: openstack-operators at lists.openstack.org; Greg Holt Subject: [Openstack-operators] cyberduck interface to swift ?? Hi, I have deployed swift-1.4 dev(SAIO) service running on a test node , able to create the accounts and do upload/download of files using the "st" tool by following doc of SAIO Test node swift service is enabled with SSL using self signed certs. and uses swauth authentication And, then I have installed the Cyberduck-Installer-4.0.2.exe on windows xp and windows vista machines , but when I open connection to swift service running on test node it throws error as login failed swift at test3:~$ swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0 -U system:root -K testpass stat Account: AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f Containers: 0 Objects: 0 Bytes: 0 Accept-Ranges: bytes swift at test3:~$ swift at test3:~$ swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0 -U system:root -K testpass list swift at test3:~$ swift at test3:~$ curl -k -v -H 'X-Storage-User: system:root' -H 'X-Storage-Pass: testpass' https://192.168.62.63:8080/auth/v1.0 * About to connect() to 192.168.62.63 port 8080 (#0) * Trying 192.168.62.63... connected * Connected to 192.168.62.63 (192.168.62.63) port 8080 (#0) * successfully set certificate verify locations: * CAfile: none CApath: /etc/ssl/certs * SSLv3, TLS handshake, Client hello (1): * SSLv3, TLS handshake, Server hello (2): * SSLv3, TLS handshake, CERT (11): * SSLv3, TLS handshake, Server finished (14): * SSLv3, TLS handshake, Client key exchange (16): * SSLv3, TLS change cipher, Client hello (1): * SSLv3, TLS handshake, Finished (20): * SSLv3, TLS change cipher, Client hello (1): * SSLv3, TLS handshake, Finished (20): * SSL connection using AES256-SHA * Server certificate: * subject: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in * start date: 2011-04-25 05:45:12 GMT * expire date: 2011-05-25 05:45:12 GMT * common name: swift (does not match '192.168.62.63') * issuer: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in * SSL certificate verify result: self signed certificate (18), continuing anyway. > GET /auth/v1.0 HTTP/1.1 > User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15 > Host: 192.168.62.63:8080 > Accept: */* > X-Storage-User: system:root > X-Storage-Pass: testpass > < HTTP/1.1 200 OK < X-Storage-Url: https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f < X-Storage-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 < X-Auth-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 < Content-Length: 117 < Date: Tue, 26 Apr 2011 12:48:39 GMT < * Connection #0 to host 192.168.62.63 left intact * Closing connection #0 * SSLv3, TLS alert, Client hello (1): {"storage": {"default": "local", "local": "https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f"}}swift at test3:~$ swift at test3:~$ Using st tool I am able upload/download the files but using cyberduck interface , login itself is failed Kindly help me to resolve this login error , any doc. which describes about cyberduck interface to swift will be helpful I have checked the related doc. present under http://swift.openstack.org/howto_cyberduck.html but it describes about source build of cyberduck not the binary version Is it possible to specify "http" protocol instead of "https" using cyerduck to contact swift service ? kindly help me Thanks & Regards, shashi ________________________________ Notice: This communication, including attachments, may contain information that is confidential. It constitutes non-public information intended to be conveyed only to the designated recipient(s). If the reader or recipient of this communication is not the intended recipient, an employee or agent of the intended recipient who is responsible for delivering it to the intended recipient, or if you believe that you have received this communication in error, please notify the sender immediately by return e-mail and promptly delete this e-mail, including attachments without reading or saving them in any manner. The unauthorized use, dissemination, distribution, or reproduction of this e-mail, including attachments, is prohibited and may be unlawful. If you have received this email in error, please notify us immediately by e-mail or telephone and delete the e-mail and the attachments (if any). -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 13536 bytes Desc: image001.png URL: From shashidhar.velagandula at gmail.com Wed Apr 27 05:10:12 2011 From: shashidhar.velagandula at gmail.com (shashidhar v) Date: Wed, 27 Apr 2011 10:40:12 +0530 Subject: [Openstack-operators] Openstack-operators Digest, Vol 6, Issue 10 In-Reply-To: References: Message-ID: Hi, I tried similar way , but no luck ... login failed server : IP address login : system:root since I am using swauth - I used path as /auth/v1.0 ( even I tried path - "/auth" also ) You can check the attached scrennshots which shows the swift login using cyberduck swift logs : /var/log/syslog Apr 27 09:29:04 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/03/59/04 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29% 20%28Windows%20XP/5.1%29%20%28x86%29 - - - - txd48e8456-2803-4235-9fb1-1c2b443e33b3 - 0.0005 Apr 27 09:29:13 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/03/59/13 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx781d965e-edea-4853-992f-a84afdf1aefb - 0.0005 Apr 27 09:29:53 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/03/59/53 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx709aa787-0391-40a2-928f-9f16f642f5ee - 0.0005 Apr 27 09:32:42 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/04/02/42 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx28acc218-2c08-40e3-be5e-610b79607c64 - 0.0006 Apr 27 09:34:16 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/04/04/16 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx8e389e6c-a99a-4345-98be-99ad3c79e129 - 0.0005 There were no logs w.r.t cyberduck , how to enable the logs in cyberduck( debug mode ) ? There were no error messages except the login failed ,,, Kindly help to resolve this Thanks & Regards, shashi On Wed, Apr 27, 2011 at 12:32 AM, < openstack-operators-request at lists.openstack.org> wrote: > Send Openstack-operators mailing list submissions to > openstack-operators at lists.openstack.org > > To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > or, via email, send a message with subject or body 'help' to > openstack-operators-request at lists.openstack.org > > You can reach the person managing the list at > openstack-operators-owner at lists.openstack.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Openstack-operators digest..." > > > Today's Topics: > > 1. Re: cyberduck interface to swift ?? (Justin J. Russell) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 26 Apr 2011 09:02:12 -0700 > From: "Justin J. Russell" > To: shashidhar v , > "openstack-operators at lists.openstack.org" > , Greg Holt > > Subject: Re: [Openstack-operators] cyberduck interface to swift ?? > Message-ID: > <401C063992AB5C47B4AF4D8F2FC6C3090175A3F392FE at NTSEXCHA1CMB2.NTS.PHX1 > > > Content-Type: text/plain; charset="us-ascii" > > I was able to connect to our own implementation of Swift using the > following settings: > > Server: storage.webcontrolcenter.com > Port: 11000 > Username: AccountName:UserName > Path: /auth > > The username is your account name + ":" + your username. For example, if > your account name is "Account1" and your username is "User1" then your > username in Cyberduck is Account1:User1. > > I hope this helps. > > Thank you, > > Justin J. Russell | Vice President of Product Development of Technology > Services > > [cid:image001.png at 01CC03F0.9FF6AE80] > > From: openstack-operators-bounces at lists.openstack.org [mailto: > openstack-operators-bounces at lists.openstack.org] On Behalf Of shashidhar v > Sent: Tuesday, April 26, 2011 6:22 AM > To: openstack-operators at lists.openstack.org; Greg Holt > Subject: [Openstack-operators] cyberduck interface to swift ?? > > Hi, > > I have deployed swift-1.4 dev(SAIO) service running on a test node , able > to create the accounts and do upload/download of files using the "st" tool > by following doc of SAIO > Test node swift service is enabled with SSL using self signed certs. and > uses swauth authentication > > And, then I have installed the Cyberduck-Installer-4.0.2.exe on windows xp > and windows vista machines , but when I open connection to swift service > running on test node it throws error as login failed > > swift at test3:~$ swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0-U system:root -K testpass stat > Account: AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f > Containers: 0 > Objects: 0 > Bytes: 0 > Accept-Ranges: bytes > swift at test3:~$ > swift at test3:~$ > swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0 -U system:root > -K testpass list > swift at test3:~$ > swift at test3:~$ curl -k -v -H 'X-Storage-User: system:root' -H > 'X-Storage-Pass: testpass' https://192.168.62.63:8080/auth/v1.0 > * About to connect() to 192.168.62.63 port 8080 (#0) > * Trying 192.168.62.63... connected > * Connected to 192.168.62.63 (192.168.62.63) port 8080 (#0) > * successfully set certificate verify locations: > * CAfile: none > CApath: /etc/ssl/certs > * SSLv3, TLS handshake, Client hello (1): > * SSLv3, TLS handshake, Server hello (2): > * SSLv3, TLS handshake, CERT (11): > * SSLv3, TLS handshake, Server finished (14): > * SSLv3, TLS handshake, Client key exchange (16): > * SSLv3, TLS change cipher, Client hello (1): > * SSLv3, TLS handshake, Finished (20): > * SSLv3, TLS change cipher, Client hello (1): > * SSLv3, TLS handshake, Finished (20): > * SSL connection using AES256-SHA > * Server certificate: > * subject: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; > CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in shashidharv at ctsf.cdac.org.in> > * start date: 2011-04-25 05:45:12 GMT > * expire date: 2011-05-25 05:45:12 GMT > * common name: swift (does not match '192.168.62.63') > * issuer: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; > CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in shashidharv at ctsf.cdac.org.in> > * SSL certificate verify result: self signed certificate (18), > continuing anyway. > > GET /auth/v1.0 HTTP/1.1 > > User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k > zlib/1.2.3.3 libidn/1.15 > > Host: 192.168.62.63:8080 > > Accept: */* > > X-Storage-User: system:root > > X-Storage-Pass: testpass > > > < HTTP/1.1 200 OK > < X-Storage-Url: > https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f > < X-Storage-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 > < X-Auth-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 > < Content-Length: 117 > < Date: Tue, 26 Apr 2011 12:48:39 GMT > < > * Connection #0 to host 192.168.62.63 left intact > * Closing connection #0 > * SSLv3, TLS alert, Client hello (1): > {"storage": {"default": "local", "local": " > https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f > "}}swift at test3:~$ > swift at test3:~$ > > > Using st tool I am able upload/download the files but using cyberduck > interface , login itself is failed > > Kindly help me to resolve this login error , any doc. which describes > about cyberduck interface to swift will be helpful < > http://cyberduck.ch/windows/Cyberduck-Installer-4.0.2.exe> > I have checked the related doc. present under > http://swift.openstack.org/howto_cyberduck.html but it describes about > source build of cyberduck not the binary version > > Is it possible to specify "http" protocol instead of "https" using > cyerduck to contact swift service ? > kindly help me > > Thanks & Regards, > shashi > > ________________________________ > Notice: This communication, including attachments, may contain information > that is confidential. It constitutes non-public information intended to be > conveyed only to the designated recipient(s). If the reader or recipient of > this communication is not the intended recipient, an employee or agent of > the intended recipient who is responsible for delivering it to the intended > recipient, or if you believe that you have received this communication in > error, please notify the sender immediately by return e-mail and promptly > delete this e-mail, including attachments without reading or saving them in > any manner. The unauthorized use, dissemination, distribution, or > reproduction of this e-mail, including attachments, is prohibited and may be > unlawful. If you have received this email in error, please notify us > immediately by e-mail or telephone and delete the e-mail and the attachments > (if any). > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.openstack.org/pipermail/openstack-operators/attachments/20110426/0d9d7598/attachment.html > > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: image001.png > Type: image/png > Size: 13536 bytes > Desc: image001.png > URL: < > http://lists.openstack.org/pipermail/openstack-operators/attachments/20110426/0d9d7598/attachment.png > > > > ------------------------------ > > _______________________________________________ > Openstack-operators mailing list > Openstack-operators at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > End of Openstack-operators Digest, Vol 6, Issue 10 > ************************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shashidhar.velagandula at gmail.com Wed Apr 27 05:01:58 2011 From: shashidhar.velagandula at gmail.com (shashidhar v) Date: Wed, 27 Apr 2011 10:31:58 +0530 Subject: [Openstack-operators] cyberduck interface to swift ?? In-Reply-To: <401C063992AB5C47B4AF4D8F2FC6C3090175A3F392FE@NTSEXCHA1CMB2.NTS.PHX1> References: <401C063992AB5C47B4AF4D8F2FC6C3090175A3F392FE@NTSEXCHA1CMB2.NTS.PHX1> Message-ID: Hi, I tried similar way , but no luck ... login failed since I am using swauth - I used path as /auth/v1.0 ( even I tried path - "/auth" also ) You can check the attached scrennshots which shows the swift login using cyberduck swift logs : /var/log/syslog Apr 27 09:29:04 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/03/59/04 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - txd48e8456-2803-4235-9fb1-1c2b443e33b3 - 0.0005 Apr 27 09:29:13 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/03/59/13 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx781d965e-edea-4853-992f-a84afdf1aefb - 0.0005 Apr 27 09:29:53 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/03/59/53 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx709aa787-0391-40a2-928f-9f16f642f5ee - 0.0005 Apr 27 09:32:42 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/04/02/42 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx28acc218-2c08-40e3-be5e-610b79607c64 - 0.0006 Apr 27 09:34:16 test3 proxy-server 192.168.x.x 192.168.x.x 27/Apr/2011/04/04/16 GET /v1.0 HTTP/1.0 412 - Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx8e389e6c-a99a-4345-98be-99ad3c79e129 - 0.0005 There were no logs w.r.t cyberduck , how to enable the logs in cyberduck( debug mode ) ? There were no error messages except the login failed ,,, Kindly help to resolve this Thanks & Regards, shashi On Tue, Apr 26, 2011 at 9:32 PM, Justin J. Russell wrote: > I was able to connect to our own implementation of Swift using the > following settings: > > > > Server: storage.webcontrolcenter.com > > Port: 11000 > > Username: AccountName:UserName > > Path: /auth > > > > The username is your account name + ?:? + your username. For example, if > your account name is ?Account1? and your username is ?User1? then your > username in Cyberduck is Account1:User1. > > > > I hope this helps. > > > > Thank you, > > > > Justin J. Russell *|* Vice President of Product Development of Technology > Services > > > > [image: Description: Description: Description: thesbalogo] > > > > *From:* openstack-operators-bounces at lists.openstack.org [mailto: > openstack-operators-bounces at lists.openstack.org] *On Behalf Of *shashidhar > v > *Sent:* Tuesday, April 26, 2011 6:22 AM > *To:* openstack-operators at lists.openstack.org; Greg Holt > *Subject:* [Openstack-operators] cyberduck interface to swift ?? > > > > Hi, > > I have deployed swift-1.4 dev(SAIO) service running on a test node , able > to create the accounts and do upload/download of files using the "st" tool > by following doc of SAIO > Test node swift service is enabled with SSL using self signed certs. and > uses swauth authentication > > And, then I have installed the Cyberduck-Installer-4.0.2.exe on windows xp > and windows vista machines , but when I open connection to swift service > running on test node it throws error as login failed > > swift at test3:~$ swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0-U system:root -K testpass stat > Account: AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f > Containers: 0 > Objects: 0 > Bytes: 0 > Accept-Ranges: bytes > swift at test3:~$ > swift at test3:~$ > swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0 -U system:root > -K testpass list > swift at test3:~$ > swift at test3:~$ curl -k -v -H 'X-Storage-User: system:root' -H > 'X-Storage-Pass: testpass' https://192.168.62.63:8080/auth/v1.0 > * About to connect() to 192.168.62.63 port 8080 (#0) > * Trying 192.168.62.63... connected > * Connected to 192.168.62.63 (192.168.62.63) port 8080 (#0) > * successfully set certificate verify locations: > * CAfile: none > CApath: /etc/ssl/certs > * SSLv3, TLS handshake, Client hello (1): > * SSLv3, TLS handshake, Server hello (2): > * SSLv3, TLS handshake, CERT (11): > * SSLv3, TLS handshake, Server finished (14): > * SSLv3, TLS handshake, Client key exchange (16): > * SSLv3, TLS change cipher, Client hello (1): > * SSLv3, TLS handshake, Finished (20): > * SSLv3, TLS change cipher, Client hello (1): > * SSLv3, TLS handshake, Finished (20): > * SSL connection using AES256-SHA > * Server certificate: > * subject: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; > CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in > * start date: 2011-04-25 05:45:12 GMT > * expire date: 2011-05-25 05:45:12 GMT > * common name: swift (does not match '192.168.62.63') > * issuer: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; > CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in > * SSL certificate verify result: self signed certificate (18), > continuing anyway. > > GET /auth/v1.0 HTTP/1.1 > > User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k > zlib/1.2.3.3 libidn/1.15 > > Host: 192.168.62.63:8080 > > Accept: */* > > X-Storage-User: system:root > > X-Storage-Pass: testpass > > > < HTTP/1.1 200 OK > < X-Storage-Url: > https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f > < X-Storage-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 > < X-Auth-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22 > < Content-Length: 117 > < Date: Tue, 26 Apr 2011 12:48:39 GMT > < > * Connection #0 to host 192.168.62.63 left intact > * Closing connection #0 > * SSLv3, TLS alert, Client hello (1): > {"storage": {"default": "local", "local": " > https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f > "}}swift at test3:~$ > swift at test3:~$ > > > Using st tool I am able upload/download the files but using cyberduck > interface , login itself is failed > > Kindly help me to resolve this login error , any doc. which describes > about cyberduck interface to swift will be helpful > > I have checked the related doc. present under > http://swift.openstack.org/howto_cyberduck.html but it describes about > source build of cyberduck not the binary version > > Is it possible to specify "http" protocol instead of "https" using > cyerduck to contact swift service ? > kindly help me > > Thanks & Regards, > shashi > > ------------------------------ > Notice: This communication, including attachments, may contain information > that is confidential. It constitutes non-public information intended to be > conveyed only to the designated recipient(s). If the reader or recipient of > this communication is not the intended recipient, an employee or agent of > the intended recipient who is responsible for delivering it to the intended > recipient, or if you believe that you have received this communication in > error, please notify the sender immediately by return e-mail and promptly > delete this e-mail, including attachments without reading or saving them in > any manner. The unauthorized use, dissemination, distribution, or > reproduction of this e-mail, including attachments, is prohibited and may be > unlawful. If you have received this email in error, please notify us > immediately by e-mail or telephone and delete the e-mail and the attachments > (if any). > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: swift1.JPG Type: image/jpeg Size: 133530 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: swift2.JPG Type: image/jpeg Size: 118924 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: swift3.JPG Type: image/jpeg Size: 118924 bytes Desc: not available URL: From topper at toppingdesign.com Wed Apr 27 19:13:51 2011 From: topper at toppingdesign.com (Topping Bowers) Date: Wed, 27 Apr 2011 15:13:51 -0400 Subject: [Openstack-operators] 1.2 to 1.3 upgrade Message-ID: Hey All, hope this finds you well. We are trying to upgrade from 1.2 to 1.3 swift object store. Looking at the swift code - I see the new indexes getting created on new container databases, but I do not see it getting added to existing 1.2 databases. Also, in general, I don't see anything in the release notes about upgrading. Any hints, clues, or how-tos anyone knows? Thanks so much, -- Topper Bowers topper at toppingdesign.com http://croonmytune.com http://blog.toppingdesign.com