cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Turner (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-7874) "CPU (in MHz)" does not make sense
Date Fri, 14 Nov 2014 15:14:34 GMT


Stephen Turner commented on CLOUDSTACK-7874:

We can change it, but I'd like to understand what it actually does in each hypervisor first,
to make sure we get it right this time. What API calls does it actual call in XenServer?

> "CPU (in MHz)" does not make sense
> ----------------------------------
>                 Key: CLOUDSTACK-7874
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Hypervisor Controller, UI
>    Affects Versions: 4.4.1
>         Environment: CentOS 6 x86_64 mgmt + HVs
>            Reporter: Nux
>              Labels: UI, cpu, cpuspeed
> Hello,
> This "CPU (in MHz)" description when adding a new Service Offering does not make much
sense and is misleading. 
> As far as I know this is the "cpu weight" Xen feature to determine CPU access/time priority;
it should be presented as such or it should be determined automatically based on Core count.
> In my particular setup I have edited classes/resources/ and modified
it as follows:
> label.cpu.mhz=CPU priority (same number as cores)
> Is this something that could be changed?

This message was sent by Atlassian JIRA

View raw message