kiranchavala opened a new issue, #10199: URL: https://github.com/apache/cloudstack/issues/10199
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 https://github.com/apache/cloudstack/pull/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 <img width="711" alt="Image" src="https://github.com/user-attachments/assets/7f9afef9-d5f6-4ba7-b787-de954b96c44c"; /> <img width="476" alt="Image" src="https://github.com/user-attachments/assets/0416a60b-f820-481b-86b0-4bd8b0f6eeaf"; /> 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) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
