Number of running and stopped VMs as preset variables for Network type Quota tariffs
#11689
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR aims to add two new preset variables for
Networktype Quota tariffs:value.resourceCounting.runningVmsandvalue.resourceCounting.stoppedVms.They represent the number of user instances that have a NIC on the network being processed. The preset variable
value.resourceCounting.runningVmsrefers to the number of running instances, andvalue.resourceCounting.stoppedVmsrefers to the number of stopped instances.Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
I created 3 VMs on the same guest network (2 of them in running state and 1 in stopped state), then I created a
NetworkQuota tariff with the following activation rule:I called the
quotaUpdateAPI via CMK and verified that the value 300 was being returned when executing the activation rule.How did you try to break this feature and the system with this change?