brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aled Sage (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (BROOKLYN-398) Provisioning property minRam not dealt with correctly
Date Thu, 27 Apr 2017 16:48:04 GMT

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

Aled Sage closed BROOKLYN-398.
------------------------------
       Resolution: Cannot Reproduce
    Fix Version/s: 0.11.0

> Provisioning property minRam not dealt with correctly
> -----------------------------------------------------
>
>                 Key: BROOKLYN-398
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-398
>             Project: Brooklyn
>          Issue Type: Bug
>            Reporter: Duncan Godwin
>             Fix For: 0.11.0
>
>
> When launching a VM, and a provisioning property of {{minRam: 2gb}} is set, a machine
with 4gb is provisioned. When {{minRam: 2000}} is set, a machine with 2gb is provisioned.
> [This line|https://github.com/apache/brooklyn-server/blob/master/locations/jclouds/src/main/java/org/apache/brooklyn/location/jclouds/JcloudsLocation.java#L1272]
indicates that both should launch a machine with 2gb of ram but this appears to not be the
case.
> Tested on openstack and AWS.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message