deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Lutterkort (Commented) (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-123) vsphere - incorrect hwp memory range
Date Sat, 21 Jan 2012 00:52:39 GMT


David Lutterkort commented on DTACLOUD-123:

Why require a minimum memory of 512MB ? It should just be 0
> vsphere - incorrect hwp memory range
> ------------------------------------
>                 Key: DTACLOUD-123
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Bug
>         Environment: deltacloud-core-vsphere-0.4.1-8.el6.noarch
> deltacloud-core-0.4.1-8.el6.noarch
>            Reporter: Jan Provaznik
>            Assignee: David Lutterkort
> When counting hwp memory for vsphere driver, max value is computed from effectiveMemory
(which is actual value - it can change in time). Minimum value is hardcoded 128. There are
2 problems:
> 1) effectiveMemory can be lower then 128, then dc api returns invalid range, I got this:
> #<DeltaCloud::HWP::Property:0x7fde69094af8 @value="128", @range={:to=>"0", :from=>"128"},
@kind=:range, @   name="memory", @unit="MB">
> 2) conductor fetches hw profiles only once when a provider account is added, so conductor
uses this  effectiveMemory (which was actual at the moment when the account was added) all
the time.
> I think most easiest way is to use total memory for computing memory range on DC API
side, though then max memory can be unavailable sometimes. 
> On the other side, for other drivers min/max memory values are hardcoded too, so using
total memory doesn't break things more (in compare to other drivers).
> Alternatively there could be some api call how to get total memory.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message