btzq opened a new issue, #9693:
URL: https://github.com/apache/cloudstack/issues/9693
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
Compute Cluster UI
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.19.1.1
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
##### SUMMARY
<!-- Explain the problem/feature briefly -->
We have 2 Compute Clusters:
- Cluster 1 : Oversubcription = 1
- Cluster 2 : Oversubcription = 2
Refering to the screenshot below, Cluster 1 is showing the correct No. of
CPU Cores allocated.
But for Cluster 2, it seems inaccurate. The number of allocation exceeded
whats available. Resulting in a UI error.
But the bigger problem now, is that both clusters have exceeded the
allocation threshold, but there was no notification sent. And neither did
cloudstack stop users from creating new virtual machines from the clusters.
Without this, Admins would not be able to ensure n+1 sufficient capacity in
the event of a node failure.
In summary, there are 3 Issues:
- No. Of Allocated CPU Cores should display the full available amount, after
oversubscription
- Admin should get Notification if exceeded the global setting threshold
(cluster.cpu.allocated.capacity.notificationthreshold)
- User should not be able to create resources into the cluster after
exceeding global setting threshold
(cluster.cpu.allocated.capacity.disablethreshold)
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
- No. Of Allocated CPU Cores should display the full available amount, after
oversubscription
- Admin should get Notification if exceeded the global setting threshold
(cluster.cpu.allocated.capacity.notificationthreshold)
- User should not be able to create resources into the cluster after
exceeding global setting threshold
(cluster.cpu.allocated.capacity.disablethreshold)
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
- No. Of Allocated CPU Cores should not displaying total available cores
correctly, after oversubscription.
- Admin did not get Notification if exceeded the global setting threshold
(cluster.cpu.allocated.capacity.notificationthreshold)
- User is able to create resources into the cluster after exceeding global
setting threshold (cluster.cpu.allocated.capacity.disablethreshold)
~~~
--
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: commits-unsubscr...@cloudstack.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
