Changes to disk size, IOPS, or throughput on agggr disk causes destroy

[billkrolczyk444]

Changes to disk size, IOPS, or throughput on aggr disk on aws cvo ha pair causes destroy of the entire environment. Shouldn't it createa new aggr, volume move of existing volumes, then destroy the existing agggr?

[suhasbshekar]

If you look at the screenshot below, there are few APIs in Aggregate and as of now we only support adding disks to the existing aggregate.
Throughput and IOPS are not supported.

[billkrolczyk444]

are you going to add that functionality?

[billkrolczyk444]

i see in version 26.0.0 the aggregate.go was updated for the changes. where issue lies is in the cvo.go. any changes to the ebs (initial aggr) triggers a destroy before any data can be transferred. are you planning to integrate that option to cvo.go?

[suhasbshekar]

Is the UI able to achieve the same of data transfer you are referring to, if so can you show the same in UI hapeening?

[billkrolczyk444]

the biggest concern is the default aggr not being able to resize the disks. i was told to not utilize the default aggr for workloads but it consumes 8 disk attachments on a limit of 26 per EC2 in AWS. it can be done via the UI but not terraform. terraform causes replace of whole cvo