Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@deltacloud.apache.org
Date: Thu, 28 Jun 2012 10:19:42 +0000 (UTC)
From: "Marios Andreou (JIRA)" <jira@apache.org>
To: dev@deltacloud.apache.org
Message-ID: <1540128073.66053.1340878783798.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <627683938.65760.1340869784582.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Resolved] (DTACLOUD-245) FGCP/DMTF: undefined method
 `value' for hardware profile as storage is not specified
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Marios Andreou resolved DTACLOUD-245.
-------------------------------------

    Resolution: Fixed

attache patch should address issue - waiting for testing ACK before pushing to master
                
> FGCP/DMTF: undefined method `value' for hardware profile as storage is not specified
> ------------------------------------------------------------------------------------
>
>                 Key: DTACLOUD-245
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-245
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>         Environment: fgcp driver and cimi interface
>            Reporter: Dies Koper
>            Assignee: Marios Andreou
>         Attachments: 0001-CIMI-Adds-guards-in-conversion-of-hardware_profile-t.patch
>
>
> cimi/machine_configurations gives error page with fgcp driver.
> In fgcp, hardware profiles do not define the storage size, that depends on the image you launch.
> So the storage field is not set, which leads to a nice(?) 'empty' symbol in the DC UI.
> machine_configuration.rb:56 is expecting a value for storage.
> Where should this be fixed? Nil check in dmtf server or set a value (what?) in fgcp driver?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira