10 http-rest api object mode shares, Terminology for storeall rest api object mode – HP StoreAll Storage User Manual

Page 138

Advertising
background image

10 HTTP-REST API object mode shares

The StoreAll REST API share in object mode provides concepts similar to OpenStack Object Storage
API to support programmatic access to user-stored files. Users create containers within each account
to hold objects (files), and the user's string identifier for the object maps to a hashed path name
on the file system.

Terminology for StoreAll REST API object mode

Table 15 Terminology for StoreAll REST API object mode

Description

Term

The user is represented by an account. Accounts are implemented as existing LDAP, AD, or
local user accounts. Accounts can contain up to 10,000 containers.

Account

Objects are stored in containers. Containers cannot be nested. A container maps to a
subdirectory of the account directory on the file system.

Container

Container names must be at least 3 and no more than 63 characters long. Container names
must also be a series of one or more labels separated by a period (.), where each label:

Must start with a lowercase letter or a number

Must end with a lowercase letter or a number

Can contain lowercase letters, numbers and dashes

Container names support the full UTF-8 character set.

Valid container names:

15.226.48.204

10.10.10.10.hello

10.10-10.10xyz123.----10.20

10-10-10-10

10---------10

1.2.3.4. newcontainer.1.2.3.4

Consecutive periods (..) are illegal in a container name, as shown in the following example:

new..container

A label is defined as a string of any combination of one or more:

Label

Lowercase characters

Digits

‘-‘ characters

A file uploaded by a user into a container within a user's account. Users can store an infinite
amount of objects in a container.

Object

A string unique to this object within a container, identifying the object. It does not have to
relate to the original file being uploaded. It can be a path and file name, such as:

Object ID

/dir1/file1.txt

But it does not have to be a file system construct. It can be any string, such as:

Monthly_report-Jan2013

The file is stored in a directory with the filename defined by StoreAll on the file system, in the
given container's directory, based on a hash code of the object ID string. The file location in
the file system is not based on any paths in the object ID string.

138

HTTP-REST API object mode shares

Advertising