prashant kumar mishra created CLOUDSTACK-1538:
-------------------------------------------------
Summary: CS does not display how much overcommited resourced
(ram/cpu) are available(or leftover after deploying a vm) (Dashboard displaying
actual resource)
Key: CLOUDSTACK-1538
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1538
Project: CloudStack
Issue Type: Improvement
Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.2.0
Reporter: prashant kumar mishra
At any point of time it is not known how much overcommited resources are
leftover(until unless admin does manual calculation) ,so that admin can choose
a proper service offering to deploy vm without failure.
==========
Actual Memory=1GB
Overcommit ratio for Memory=2
Overcommited Memory=2GB
1-Deployed a vm with service offering having Memory=1.5 GB
2-To deploy second vm he used Service offering having Memory=1GB (deployment
failed)
3-He has to try again with service offering=512MB
If it is known how much Overcommited Memory is available or leftover, step 2
failure can be avoided by choosing a proper service offering at first place.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
