Hi,
I got it running. A foolish mistake. I mentioned the swift endpoint as
http, where as proxy was running https :O
--
Shashank Sahni
On Thu, Nov 22, 2012 at 12:27 PM, Shashank Sahni shredde...@gmail.comwrote:
Hi,
I'm following the steps mentioned in the official object storage
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 shredde...@gmail.com
Hi,
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
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 shredde...@gmail.com 於 2012/11/20 下午6:40 寫道：
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: '
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
5 matches
Mail list logo
