HP 3PAR Web Service API 1.3.1 Developer's Guide

/api/v1/volumes/<volume name>
Volume Creation Errors
An error condition returns one of the errors in Table 35 (page 57). For generic API error codes,
see Table 5 (page 22).
Table 35 Base-Volume and Snapshot Creation Error Codes
DescriptionHTTP CodeAPI Error
Invalid parameter or JSON object.400 Bad RequestINV_INPUT
The volume already exists.409 ConflictEXISTENT_VOL
Volume size is above the architectural
limit.
400 Bad RequestTOO_LARGE
Not enough space is currently available.400 Bad RequestNO_SPACE
No snapshot space is available.409 ConflictNO_SNAP_CPG
Allocation warning level is higher than the
limit.
400 Bad RequestINV_INPUT_WARN_GT_LIMIT
User space allocation alerts are valid only
with TPVVs.
400 Bad RequestINV_INPUT_USR_ALRT_NON_TPVV
Retention time is greater than expiration
time.
400 Bad RequestINV_INPUT_RETAIN_GT_EXPIRE
Invalid policy specification (for example,
caching or system set to true).
400 Bad RequestINV_INPUT_VV_POLICY
Invalid input: string length exceeds limit.400 Bad RequestINV_INPUT_EXCEEDS_LENGTH
Invalid time specified.400 Bad RequestINV_INPUT_TIME
ID exists.409 ConflictEXISTENT_ID
Modifying a Virtual Volume
To modify or update a volume, use the HTTP PUT method in the URI:
https://<storage_system>:8080/api/v1/volumes/<volume_name>
where <volume_name> is the name of the volume being modified. The message body is a JSON
object with members. Members that can be included in a VV modification request are shown in
Table 36 (page 57).
Table 36 Message Body JSON Objects for Volume Modification Request
DescriptionIgnored ValuesAPI TypeJSON TypeMember
New name of the
volume.
Nonename31stringnewName
(Since WSAPI 1.2)
Comment about the
volume.
Noneprint511stringcomment
(Since WSAPI 1.2)
Time in hours that the
volume would expire.
Zero and negative
values
igint32numberexpirationHours
(Since WSAPI 1.2)
Modifying a Virtual Volume 57