Open Stack

Hi,

I'm following the steps mentioned in the official object storage
documentation.

http://docs.openstack.org/folsom/openstack-object-storage/admin/content/verify-swift-installation.html

I followed the steps as it is and all the services are up and running with
no traces of any error in /var/log/syslog. Note that, I'm trying to run
swift proxy and storage service on the same node. Keystone is on a separate
server. I've already configured glance successfully, hence I believe
keystone is successfully up. As I mentioned previously, keystone is even
responding to swift because if I enter wrong password it returns
'authentication failed'.

Any thoughts?

--
Shashank Sahni



On Wed, Nov 21, 2012 at 2:02 PM, Kuo Hugo <tonytkdk at gmail.com> wrote:

> Hi ,
> For keystone 2.0 auth
> the request should provide a json format which includes username / tenant
> / password .
>
> In your curl test , you provide two headers to auth 2.0 .
>
> Please have a look at officail document to get the right API call.
>
>
> 2012/11/21 Shashank Sahni <shredder12 at gmail.com>
>
>> Hi,
>>
>> Thanks for the response. I went head to verify using curl and ran.
>>
>> $ curl -k -v -H 'X-Storage-User: admin:admin' -H 'X-Storage-Pass: xxxx'
>> http://10.2.4.115:5000/v2.0
>>
>> Here is the output. I don't see the token or storage-url anywhere. Note
>> that, 10.2.4.115 is the keystone server.
>>
>> * About to connect() to 10.2.4.115 port 5000 (#0)
>> *   Trying 10.2.4.115... connected
>> > GET /v2.0 HTTP/1.1
>> > User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0
>> OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
>> > Host: 10.2.4.115:5000
>> > Accept: */*
>> > X-Storage-User: admin:admin
>> > X-Storage-Pass: xxxxx
>> >
>> < HTTP/1.1 200 OK
>> < Vary: X-Auth-Token
>> < Content-Type: application/json
>> < Date: Wed, 21 Nov 2012 05:46:25 GMT
>> < Transfer-Encoding: chunked
>> <
>> * Connection #0 to host 10.2.4.115 left intact
>> * Closing connection #0
>> {"version": {"status": "beta", "updated": "2011-11-19T00:00:00Z",
>> "media-types": [{"base": "application/json", "type":
>> "application/vnd.openstack.identity-v2.0+json"}, {"base":
>> "application/xml", "type": "application/vnd.openstack.identity-v2.0+xml"}],
>> "id": "v2.0", "links": [{"href": "http://10.2.4.115:5000/v2.0/", "rel":
>> "self"}, {"href": "
>> http://docs.openstack.org/api/openstack-identity-service/2.0/content/",
>> "type": "text/html", "rel": "describedby"}, {"href": "
>> http://docs.openstack.org/api/openstack-identity-service/2.0/identity-dev-guide-2.0.pdf",
>> "type": "application/pdf", "rel": "describedby"}]}}
>>
>> --
>> Shashank Sahni
>>
>>
>>
>>
>> On Wed, Nov 21, 2012 at 12:48 AM, Hugo <tonytkdk at gmail.com> wrote:
>>
>>> In my suggestion, using curl for verifying keystone first. And then
>>> using curl to access swift proxy with the returned token and
>>> service-endpoint from previous keystone operation.
>>>
>>> It must give u more clear clues.
>>>
>>>
>>>
>>> 從我的 iPhone 傳送
>>>
>>> Shashank Sahni <shredder12 at gmail.com> 於 2012/11/20 下午6:40 寫道：
>>>
>>> Hi,
>>>
>>> I'm trying to install Swift 1.7.4 on Ubuntu 12.04. The installation is
>>> multi-node with keystone and swift(proxy+storage) running on separate
>>> systems. Keystone is up and running perfectly fine. Swift user and service
>>> endpoints are created correctly to point to the swift_node. Swift is
>>> configured and all its services are up. But during swift installation
>>> verification, the following commands hangs with no output.
>>>
>>> swift -V 2 -A http://keystone_server:5000/v2.0<http://localhost:5000/v2.0>-U admin:admin -K admin_pass stat
>>>
>>> I'm sure its able to contact the keystone server. This is because if I
>>> change admin_pass, it throws authentication failure error. It probably
>>> fails in the next step which I'm unaware of.
>>>
>>> Here is my proxy-server.conf file.
>>>
>>> [DEFAULT]
>>> # Enter these next two values if using SSL certifications
>>> cert_file = /etc/swift/cert.crt
>>> key_file = /etc/swift/cert.key
>>> bind_port = 8888
>>> user = swift
>>>
>>> [pipeline:main]
>>> #pipeline = healthcheck cache swift3 authtoken keystone proxy-server
>>> pipeline = healthcheck cache swift3 authtoken keystone proxy-server
>>>
>>> [app:proxy-server]
>>> use = egg:swift#proxy
>>> allow_account_management = true
>>> account_autocreate = true
>>>
>>> [filter:swift3]
>>> use=egg:swift3#swift3
>>>
>>> [filter:keystone]
>>> paste.filter_factory = keystone.middleware.swift_auth:filter_factory
>>> operator_roles = Member,admin, swiftoperator
>>>
>>> [filter:authtoken]
>>> paste.filter_factory = keystone.middleware.auth_token:filter_factory
>>> # Delaying the auth decision is required to support token-less
>>> # usage for anonymous referrers ('.r:*').
>>> delay_auth_decision = 10
>>> service_port = 5000
>>> service_host = keystone_server
>>> auth_port = 35357
>>> auth_host = keystone_server
>>> auth_protocol = http
>>> auth_uri = http://keystone_server:5000/
>>> auth_token = XXXX
>>> admin_token = XXXX
>>> admin_tenant_name = service
>>> admin_user = swift
>>> admin_password = XXXX
>>> signing_dir = /etc/swift
>>>
>>> [filter:cache]
>>> use = egg:swift#memcache
>>> set log_name = cache
>>>
>>> [filter:catch_errors]
>>> use = egg:swift#catch_errors
>>>
>>> [filter:healthcheck]
>>> use = egg:swift#healthcheck
>>>
>>> Any suggestion?
>>>
>>> --
>>> Shashank Sahni
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to     : openstack at lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>
>
> --
> +Hugo Kuo+
> tonytkdk at gmail.com
> + <tonytkdk at gmail.com>886 935004793
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121122/105f1f94/attachment.html>