No. of CPU Cores in Compute Cluster doesnt display correctly when Cluster has oversubscription more than 1

##### ISSUE TYPE

* Bug Report

##### COMPONENT NAME

~~~
Compute Cluster UI
~~~

##### CLOUDSTACK VERSION

~~~
4.19.1.1
~~~

##### CONFIGURATION

##### OS / ENVIRONMENT

##### SUMMARY

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

~~~

~~~

##### EXPECTED RESULTS

~~~
- 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

~~~
- 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)
~~~

Commencez par le comportement de la Compute Cluster UI décrit pour la surallocation, ainsi que par les paramètres cluster.cpu.allocated.capacity.notificationthreshold et cluster.cpu.allocated.capacity.disablethreshold. Le payload ne mentionne aucun fichier source ni aucun test. Suivez donc d’abord l’affichage de l’allocation du CPU et la gestion des seuils ; le travail est terminé lorsque l’affichage de la capacité, la notification et l’empêchement de la création de nouvelles VMs sont corrects.

Rédigé par le modèle d'indexation à partir du texte de l'issue.