Certainly it's wrong at the moment, because XenServer doesn't allow you to change the MHz of the CPU of a VM. Can someone find out which XenServer API calls it actually makes? Then we can work out how to describe it.
-- Stephen Turner -----Original Message----- From: Logan Barfield [mailto:[email protected]] Sent: 10 November 2014 16:24 To: [email protected] Subject: Re: UI: "CPU (in MHz)" doesn't make sense I agree completely. We've set all of our service offerings to equal weights, and hard coded the same weight into the custom offering form. It's a bit too confusing otherwise. The way I understand the weights for (Xen/KVM at least) is that they're just relative, so 1 vs 2 is the same as 1 vs 1000. That being the case I'd suggest a solution that has worked for us in the past: set the weight equal to the memory amount (in MB). Thoughts? Thank You, Logan Barfield Tranquil Hosting On Mon, Nov 10, 2014 at 11:17 AM, Nux! <[email protected]> wrote: > Hi, > > Basically I'm annoyed with the "CPU (in MHz)" usage in service > offerings as they are a lie basically. > Opened https://issues.apache.org/jira/browse/CLOUDSTACK-7874 and > suggest to have calculated automatically based on CPU cores number or > at least having it renamed to something like "cpu weight". > MHz means nothing. > > Thoughts? > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro >
