GutoVeronezi opened a new pull request #5909: URL: https://github.com/apache/cloudstack/pull/5909
### Description This PR solves issue #5891. The main focus of this PR is to provide a flexible manner for operators to charge and bill their cloud resources. Issue #5891 has more details and flowcharts of all the mapped and affected/changed workflows. The UI compatibility was not addressed in this PR. However, it's mapped to be the next steps. The JS interpreter used to process the activation rules requires a GCC version higher or equal to 4.9. CentOS7, by default, is shipped with GCC 4.8; therefore, to build the packages we need to build a newer GCC version and install it. To make it easier, we already have an image with the GCC 9.3 published in the docker hub ([scclouds/cloudstack-rpm-builder:centos7-jdk11-gcc9-3](https://hub.docker.com/layers/189700957/scclouds/cloudstack-rpm-builder/centos7-jdk11-gcc9.3/images/sha256-efa266127cf28048d7942da9197d8962f2d0b076dacd8d1b9250433157bc9fb7?context=repo)). ### 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) ### Feature/Enhancement Scale or Bug Severity #### Feature/Enhancement Scale - [x] Major - [ ] Minor ### How Has This Been Tested? I added unit tests to several methods, tested the whole CRUD, and the usage calculation. To test the usage calculation I created some activation rules based on the cases described in issue #5891 (doing minor changes, such as changing the UUID to be validated). Then, I manually calculated the results and verified if the output is the same as I obtained in ACS. -- 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]
