HP 3PAR Web Service API 1.3.1 Developer's Guide

Table 20 Message Body JSON Objects for CPG Creation and Modification (continued)
DescriptionIgnored ValuesAPI TypeJSON TypeMember
If True, CPG auto grow is
disabled. The default setting
is False.
BooleandisableAutoGrow
For CPG modification only.
If True, no auto grow limit is
enforced. The default setting
is False.
BooleanrmGrowthLimit
For CPG modification only.
If True, no warning limit is
enforced. The default setting
is False.
BooleanrmWarningAlert
For CPG modification only.
CPG Creation Success
A successful operation returns the HTTP status code 201 Created. There is no message body.
Upon successful creation of the CPG, the Location portion of the response header contains the
URI for the newly created CPG in the following format:
/api/v1/cpgs/<cpg name>
CPG Creation Errors
If an error occurs, the system returns one of the error codes shown in Table 21 (page 47), or a
general error code listed in “Generic WSAPI code Member Status and Error Codes” (page 22):
Table 21 CPG Creation and Modification Error Codes
DescriptionHTTP CodeAPI Error
A pattern in a CPG LDLayout specifies
illegal values.
400 Bad RequestBAD_CPG_PATTERN
The snap CPG is not in the same
domain as the user CPG.
403 ForbiddenCPG_NOT_IN_SAME_DOMAIN
(Since WSAPI 1.2)
CPG already exists.409 ConflictEXISTENT_CPG
The CPG cannot be removed because
it is in use by a volume.
409 ConflictIN_USE
Missing CPG name.400 Bad RequestINV_INPUT
Invalid input: string length exceeds
limit.
400 Bad RequestINV_INPUT_EXCEEDS_LENGTH
Invalid input: number exceeds
expected range.
400 Bad RequestINV_INPUT_EXCEEDS_RANGE
CPG grow size is too small400 Bad RequestINV_OPERATION_GROW_SIZE_TOO_SMALL
(Since WSAPI 1.2)
Input contains one or more illegal
characters.
400 Bad RequestINV_INPUT_ILLEGAL_CHAR
Invalid input: Some or all required
parameters are missing.
400 Bad RequestINV_INPUT_MISSING_REQUIRED
Creating a CPG 47