sidebar | permalink | keywords | summary |
---|---|---|---|
sidebar |
cm/wf_gcp_ontap_create_aggr.html |
cloud, manager, rest, api, aggregate, publicid, working, environment, aws |
You can create a new aggregate within a working environment. |
You can create new aggregates within a Cloud Volumes ONTAP working environment using this workflow.
Choose the workflow to use based on the type of Cloud Volumes ONTAP deployment:
You can use this workflow to create aggregates in a single node working environment.
Perform the workflow Get working environment and choose the publicId
value for the workingEnvironmentId
parameter in the JSON input.
Perform the Get Google Cloud disk types workflow and choose the size
and supportedDiskType
values of the required diskSize
and providerVolumeType
parameters in the JSON input.
HTTP method | Path |
---|---|
POST |
occm/api/gcp/vsa/aggregates |
- curl example
curl --location --request POST 'https://cloudmanager.cloud.netapp.com/occm/api/gcp/vsa/aggregates' --header 'Content-Type: application/json' --header 'x-agent-id: <AGENT_ID>' --header 'Authorization: Bearer <ACCESS_TOKEN>' --d @JSONinput
- Input
-
The JSON input example includes the minimum list of input parameters.
- JSON input example
{
"name": "ziv01agg01",
"workingEnvironmentId": "vsaworkingenvironment-sfrf3wvj",
"numberOfDisks": 1,
"diskSize": {
"size": 100,
"unit": "GB"
},
"providerVolumeType": "pd-ssd"
}
- Output
-
None
You can use this workflow to create aggregates in an HA working environment.
Perform the workflow Get working environment and choose the publicId
value for the workingEnvironmentId
parameter in the JSON input.
Perform the Get Google Cloud disk types workflow and choose the size
and supportedDiskType
values of the required diskSize
and providerVolumeType
parameters in the JSON input.
HTTP method | Path |
---|---|
POST |
occm/api/gcp/ha/aggregates |
- curl example
curl --location --request POST 'https://cloudmanager.cloud.netapp.com/occm/api/gcp/ha/aggregates' --header 'Content-Type: application/json' --header 'x-agent-id: <AGENT_ID>' --header 'Authorization: Bearer <ACCESS_TOKEN>' --d @JSONinput
- Input
-
The JSON input example includes the minimum list of input parameters.
- JSON input example
{
"name": "ziv01we02agg01ha",
"workingEnvironmentId": "vsaworkingenvironment-blg9ei6u",
"numberOfDisks": 1,
"diskSize": {
"size": 100,
"unit": "GB"
},
"providerVolumeType": "pd-ssd"
}
- Output
-
None