Add disks to aggregate
You can add disks to an existing aggregate.
Choose the workflow to use based on the type of Cloud Volumes ONTAP deployment:
Add disks to aggregate for single node
You can use this workflow to add disks to an aggregate in a single node working environment.
1. Select the working environment
Perform the workflow Get Google Cloud single node working environment and choose the publicId
value for the workingEnvironmentId
path parameter.
2. Select the aggregate
Perform the workflow Get aggregates and choose name
of the required aggregate for the aggregateName
path parameter.
3. Add the disks to the aggregate
HTTP method | Path |
---|---|
POST |
/occm/api/gcp/vsa/aggregates/{workingEnvironmentId}/{aggregateName}/disks |
- curl example
curl --location --request POST 'https://cloudmanager.cloud.netapp.com/occm/api/gcp/vsa/aggregates/<WORKING_ENV_ID>/<AGGR_NAME>/disks' --header 'Content-Type: application/json' --header 'x-agent-id: <AGENT_ID>' --header 'Authorization: Bearer <ACCESS_TOKEN>' --d @JSONinput
- Input
-
You must include the following path parameters:
-
<WORKING_ENV_ID>
(workingEnvironmentId)
string -
<AGGR_NAME>
(aggregateName)
string
-
Also, the JSON input example includes an input parameter as shown.
- JSON input example
{
"numberOfDisks": "1"
}
- Output
-
None
Add disks to aggregate for high availability pair
You can use this workflow to add disks to an aggregate in an HA working environment.
1. Select the working environment
Perform the workflow Get Google Cloud single node working environment and choose the publicId
value for the workingEnvironmentId
path parameter.
2. Select the aggregate
Perform the workflow Get aggregates and choose name
of the required aggregate for the aggregateName
path parameter.
3. Add the disks to the aggregate
HTTP method | Path |
---|---|
POST |
/occm/api/gcp/ha/aggregates/{workingEnvironmentId}/{aggregateName}/disks |
- curl example
curl --location --request POST 'https://cloudmanager.cloud.netapp.com/occm/api/gcp/ha/aggregates/<WORKING_ENV_ID>/<AGGR_NAME>/disks' --header 'Content-Type: application/json' --header 'x-agent-id: <AGENT_ID>' --header 'Authorization: Bearer <ACCESS_TOKEN>' --d @JSONinput
- Input
-
You must include the following path parameters:
-
<WORKING_ENV_ID>
(workingEnvironmentId)
string -
<AGGR_NAME>
(aggregateName)
string
-
Also, the JSON input example includes an input parameter as shown.
- JSON input example
{
"numberOfDisks": "1"
}
- Output
-
None