HP 3PAR Web Service API 1.3.1 Developer's Guide

In response to a query for space information for a given CPG or LDLayout object, the system will
return a single JSON object. Members of the CPG query response for available space are shown
in Table 137 (page 139).
Table 137 JSON Objects for cpg Space Query Response
DescriptionValue RangeJSON TypeMember
Capacity allocated to a
layout associated with the
CPG name.
See Table 139 (page 139).LDLayoutCapacity objectLDLayoutCapacity
(Since WSAPI 1.2)
Upon querying for space information based on an LDLayout object, the system will return a single
JSON object. Its members are described in Table 139 (page 139).
Table 138 JSON Objects for LDLayout Space Query Response
DescriptionValue RangeJSON TypeMember
See Table 137 (page 139)LDLayout objectLDLayout objectLDLayout
In the response body following a query for space information in an LDLayout object, the system
returns a single JSON object whose members are described in Table 139 (page 139).
Table 139 JSON objects for LDLayoutCapacity Query Response
DescriptionValue RangeJSON TypeMember
Raw free capacity in MiB.uint64numberrawFreeMiB
(Since WSAPI 1.2)
LD free capacity in MiB.uint64numberusableFreeMiB
(Since WSAPI 1.2)
Space Query Errors
Possible errors following a space query are described in Table 140 (page 139). For generic API
error codes, see Table 5 (page 22).
Table 140 Space Query API and HTTP Error Codes
DescriptionHTTP CodeAPI Error
The set size is invalid for the selected
RAID type.
400 Bad RequestINV_SET_SIZE
Invalid input: one of the parameters is
required.
400 Bad RequestINV_INPUT_ONE_REQUIRED
(Since WSAPI 1.2)
Invalid input: string length exceeds limit.400 Bad RequestINV_INPUT_EXCEEDS_LENGTH
(Since WSAPI 1.2)
Invalid input: parameters cannot be
present at the same time.
400 Bad RequestINV_INPUT_PARAM_CONFLICT
Insufficient space for requested
operation.
400 Bad RequestNO_SPACE
Bad CPG pattern specified.400 Bad RequestBAD_CPG_PATTERN
CPG does not exist.404 Not FoundNON_EXISTENT_CPG
Space Query Errors 139