Skip to main content

Add disks to aggregate

Contributors netapp-ranuk

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 an aggregate for single node

You can use this workflow to add disks to an aggregate for a single node working environment.

1. Select the working environment to use

Perform the workflow Get working environments and choose the publicId value for the workingEnvironmentId path parameter.

2. Select the aggregate

Perform the workflow Get aggregates and choose the name value for the aggregateName path parameter.

3. Add the disks

HTTP method Path

POST

/occm/api/vsa/aggregates/{workingEnvironmentId}/{aggregateName}/disks

curl example
curl --location --request POST 'https://cloudmanager.cloud.netapp.com/occm/api/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)

  • <AGGR_NAME> (aggregateName)

Also, the JSON input example includes an input parameter as shown.

JSON input example
{
    "numberOfDisks": "1"
}
Output

None

Add disks to an aggregate for high availability pair

You can use this workflow to add disks to an aggregate for HA working environment.

1. Select the working environment to use

Perform the workflow Get working environments and choose the publicId value for the workingEnvironmentId path parameter.

2. Select the aggregate

Perform the workflow Get aggregates and choose the name value for the aggregateName path parameter.

3. Add the disks

HTTP method Path

POST

/occm/api/aws/ha/aggregates/{workingEnvironmentId}/{aggregateName}/disks

curl example
curl --location --request POST 'https://cloudmanager.cloud.netapp.com/occm/api/aws/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)

  • <AGGR_NAME> (aggregateName)

Also, the JSON input example includes an input parameter as shown.

JSON input example
{
    "numberOfDisks": "1"
}
Output

None