ISSUE TYPE

Improvement request

COMPONENT NAME

Component: Improvement

CLOUDSTACK VERSION

Cloudstack version 4.20.x

SUMMARY

Should Cloudstack consider Minops and Maxops for a vm deployment

Steps to reproduce the issue

The following pr introduced used_iops feature for localstorage

#10034

1. Launch a cloudstack environment with local storage

2. Navigate to the local storage and edit the storage

3. Update the value of IOPS total to smaller value say 7

4. Create a local storage service offering and disk offering

5. Compute offering > storage > Provide Minops and Maxops

6. Disk offering > Min ops and Max ops

7. Create a vm deployment by selecting the service offering and disk offering

Actual behaviour

The vm deployment succeeds

Questions about this behaviour

Does cloudstack validate when the Assigned primary storage “Total Iops “ is less than “UsedIops” , should the vm deployement fail ?

Does cloudstack validate the service offerings and disk offerings for (Min iops , MAX iops) for a primary localstorage ?

Should we remove the option the UI in when end user selects “Storage type” as Local and “QOS type” as storage ?

Expected behaviour

The vm deployment should fail, I think it makes sense to only show the Qos (maxops, miniops ) for a managed storage (ceph, powerflex)