cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Huang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-711) CPU and Memory OverCommit
Date Fri, 08 Mar 2013 02:12:13 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596700#comment-13596700
] 

Alex Huang commented on CLOUDSTACK-711:
---------------------------------------

Does it make sense to update the API or just set it in the cluster details.  Just leave it
as something that's documented instead?

Also have you thought about how to reflect this in statistics calculations and capacity calculations?
 Alert generations.  I don't see anything in the spec regarding this.
                
> CPU and Memory OverCommit
> -------------------------
>
>                 Key: CLOUDSTACK-711
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-711
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Hari Kannan
>            Assignee: Bharat Kumar
>             Fix For: 4.2.0
>
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CPU+and+Memory+OverCommit

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

Mime
View raw message