6.5 HP StoreAll OS User Guide

9. Stat (display information for) the container from the client side after extending the Object
Store.
Sample command
curl -i https://10.21.12.25:8888/v1/AUTH_7b9a902423a582c9eda266dcf3ad69744037ce77e61f526b0739578e87695f32
-I -H "X-Auth-Token: eb733772d0e741b2abdc137ec080213a" --cacert /root/cert.crt
Sample output
HTTP/1.1 204 No Content
Content-Length: 0
Accept-Ranges: bytes
X-Timestamp: 1385681580.82235
X-Account-Bytes-Used: 0
X-Account-Container-Count: 0
Content-Type: text/plain; charset=utf-8
X-Account-Object-Count: 0
Date: Fri, 29 Nov 2013 00:42:59 GMT
Generating a token with HTTPS enabled
Here is an example of how to generate a token when you have HTTPS enabled. You can see
–cacert option and https:// in the url, and you can also see that all the endpoints having an https
connection.
Sample command
curl -X POST https://15.213.70.153:5000/v2.0/tokens -H "Content-Type: application/json" --cacert
/root/SSL/test.crt -d ' {"auth": {"tenantName": "IbrixSwGroup", "passwordCredentials": {"username": "local_user1",
"password": "mypassword"}}}'
Sample output
{"access": {"token": {"expires": "2013-09-05T18:03:31Z", "id": "e8ea182b240c4e2da9fa0e7f8727208a", "tenant":
{"enabled": true, "id": "7b9a902423a582c9eda266dcf3ad69744037ce77e61f526b0739578e87695f32", "name":
"IbrixSwGroup"}}, "serviceCatalog": [{"endpoints": [{"adminURL": "https://15.213.70.159:8888/", "region":
"RegionOne", "internalURL":
"https://15.213.70.159:8888/v1/AUTH_7b9a902423a582c9eda266dcf3ad69744037ce77e61f526b0739578e87695f32", "id":
"973feb3a155b4a908e0332c12e9e21c4", "publicURL":
"https://15.213.70.159:8888/v1/AUTH_7b9a902423a582c9eda266dcf3ad69744037ce77e61f526b0739578e87695f32"}],
"endpoints_links": [], "type": "object-store", "name": "swift"}], "user": {"username": "local_user1",
"roles_links": [], "id": "8309b779f86a463a97881ed753b060c97b9a902423a582c9eda266dcf3ad6974", "roles": [{"name":
"admin"}], "name": "local_user1"}, "metadata": {"is_admin": true, "roles":
["7b9a902423a582c9eda266dcf3ad69744037ce77e61f526b0739578e87695f32"]}}}
Object service monitoring
The Object Store service monitoring feature provides monitoring of Object Store services and
allows automatic restart in case of failure.
NOTE:
• If Object Store services monitoring is manually disabled on all nodes and a Fusion Manager
failover occurs, then Object Store services monitoring is restarted automatically on the active
node and the failed node.
If Object Store services monitoring is manually disabled and a segment failover occurs, then
the monitoring services are migrated to the new segment server but only the rsync service is
started on the backup node. The rest of the Object Store services must be manually re-enabled
on the cluster.
Monitoring service health
Use this command to view the service health of a single node or on all nodes. The service health
includes a matrix of services that are being monitored and the nodes on which they are running.
Services will be identified as UP, DOWN, or DEGRADED.
To list the health of the Object Store services on all hosts in compact mode:
ibrix_objectstoremonitor -l
Managing and monitoring Object Store 169