HP StoreAll Storage - Manual (Page 204)

Using the HTTP StoreAll REST API object mode
This section walks you through using the major components of object mode. You will be shown
how to:
•
Create a container.
•
Set permissions for the container.
•
Upload and create objects for the container.
•
View the contents of the container.
•
Download contents from the container.
It is assumed you have already created an HTTP StoreAll REST API share in object mode. See
“Checklist for creating HTTP shares” (page 176) for information on how to create an HTTP share.
IMPORTANT: You cannot use the local root account on the StoreAll servers. If you have not done
it already, identify a local user account or a user account on Active Directory. See “Active Directory”
(page 69) for additional information.
Gather the information listed in the following table before you begin the steps in this section:
Table 28 Required information
How to obtain Required information
To obtain the name of the virtual host for the HTTP share, enter the following
command: ibrix_httpshare -l IP address and port of the virtual host
for the HTTP share
nl
To obtain the IP address of the virtual host, enter the following command:
ibrix_httpvhost -l -v 1
If the port is 80, you do not need to
include it in the command.
To find the directory path and URL path of the HTTP share, enter the following
command: Directory path and URL path of the
HTTP share
ibrix_httpshare -l -f
The directory path of the HTTP share is under the Path column, and the URL Path
is under the URL Path column.
Durability on disk
After certain commands that require writing to disk, a successful HTTP response does not guarantee
that the contents are durably on disk. The contents could still be in in-memory buffers that have not
yet been flushed to disk.
The affected commands are:
•
Create a container
•
Upload an object
•
Delete a container
•
Delete an object
For applications that have a critical requirement for durability, it is recommended that you use the
header "Sync-Requested: 1" with these commands to ensure that the operation is durable
on disk when you receive a successful HTTP response. This command header should be used
carefully because it forces a sync of the entire segment where the container/object is stored and
also syncs its parent directory, which can be stored in a different segment.
Depending on the application durability requirements, another option is to perform a batch of
operations without the "Sync-Requested: 1" header and at the end call a sync for all filesystem
segments by requesting a single HTTP PUT command to the HTTP url path with
a"Sync-Requested: 1" header. If the sync header is requested with the PUT command, the
HTTP response will return a header "Sync-Result" . The value which follows that key represents
204 HTTP-REST API object mode shares