GutoVeronezi opened a new pull request, #8481: URL: https://github.com/apache/cloudstack/pull/8481
### Description ACS does not allow operators to set the configuration `storage.overprovisioning.factor` for `SharedMountPoint` primary storages, presenting the following message when one tries to change it:  Also, the global setting does not impact `SharedMoundPoint` primary storages, which means that the over-provisioning is not applied properly for this storage type. Furthermore, the metric presents that the `SharedMountPoint` has the global over-provisioning applied; however, in a scenario where the over-provision factor is 2, the allocation threshold is 80%, and the metrics show that storage has 40% allocated, one cannot allocate to it anymore. This PR intends to enable over-provisioning for `SharedMountPoint` primary storages. ### Types of changes - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] New feature (non-breaking change which adds functionality) - [ ] Bug fix (non-breaking change which fixes an issue) - [x] Enhancement (improves an existing feature and functionality) - [ ] Cleanup (Code refactoring and cleanup, that may add test cases) - [ ] build/CI ### Feature/Enhancement Scale or Bug Severity #### Feature/Enhancement Scale - [ ] Major - [x] Minor ### Screenshots (if appropriate): ### How Has This Been Tested? In an environment where the global over-provision factor was 1, the allocation threshold was 80%, and the `SharedMountPoint` primary storage had 80% allocated, I was able to change the over-provisioning factor of the `SharedMountPoint` primary storage and allocate a new volume on it, as, with the over-provisioning, ACS considered it as having 40% allocated. -- 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]
