cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "prashant kumar mishra (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-1705) Overcommit ratio can be set at cluster level , Parameter "cpu.overprovisioning.factor" should be there in Global settings
Date Mon, 18 Mar 2013 07:34:15 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

prashant kumar mishra updated CLOUDSTACK-1705:
----------------------------------------------

    Attachment: screenshot-1.jpg
    
> Overcommit ratio can be set at cluster level , Parameter "cpu.overprovisioning.factor"
should be there in Global settings 
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1705
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1705
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: prashant kumar mishra
>            Assignee: prashant kumar mishra
>            Priority: Minor
>             Fix For: 4.2.0
>
>         Attachments: screenshot-1.jpg
>
>
> cpu.overprovisioning.factor:
> --------------------------------------
> Used for CPU overprovisioning calculation; available CPU will be (actualCpuCapacity *
cpu.overprovisioning.factor)
> Since overcommit ratio can be set on cluster level  , cpu.overprovisioning.factor is
 not going to be in use , we should not have this parameter in global settings.

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