You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@deltacloud.apache.org by "Dies Koper (JIRA)" <ji...@apache.org> on 2012/06/28 09:49:42 UTC

[jira] [Created] (DTACLOUD-245) FGCP/DMTF: undefined method `value' for hardware profile as storage is not specified

Dies Koper created DTACLOUD-245:
-----------------------------------

             Summary: 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


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

Re: [jira] [Commented] (DTACLOUD-245) FGCP/DMTF: undefined method `value' for hardware profile as storage is not specified

Posted by "marios@redhat.com" <ma...@redhat.com>.

On 30/06/12 13:15, Koper, Dies wrote:
> Hi Marios,
> 
> One thing I noticed (maybe not related to these patches), is that through the cimi GUI the cimi/machines operation times out (RestClient::RequestTimeout ) , but with the DC GUI it displays fine.
> Are you doing anything more than calling api/instances from the cimi wrapper? (that takes such a significant amount of time?)
> 

hm - I can't think of something off hand - from what you describe it's
either a fleeting network latency or a code optimisation issue rather
than a bug - if this is consistent can you file a jira ticket (with
specifics - like 'launching cimi client and listing details of machine
foo - I should be able to see same machines as you for the fgcp
credentials i have if I recall correctly).


> Also, there may be some more spring cleaning left?
> cimi/addresses returns a 404 and cimi/vsps gives the following error:

yes - the patches I sent try to make it that any collections that
*deltacloud* knows about (like 'keys') which aren't implemented by the
given driver (so keys isn't implemented for fgcp) will not be shown in
cloudEntryPoint. We need to extend this to include *all* CIMI
collections. As you know CIMI is/was still in flux and the dust is only
starting to settle (so the list of 'collections' for example and their
names is only just starting to become 'finalised'). I expect we'll be
doing a lot more work on the CIMI side of deltacloud in the coming weeks
and issues like this should disappear - if they don't, we'd be grateful
for you to pick them up and/or report them,


all the best, marios

> 
> NoMethodError - undefined method `vsps' for #<Deltacloud::Drivers::Fgcp::FgcpDriver:0x98e2a38>:
>         d:/sources/OSS/cloud/deltacloud/server/lib/cimi/./././models/vsp.rb:44:in `find'
> 
> What is the plan for these type of operations? Just add these cimi methods to the existing classes, or are you planning to introduce new (cimi) driver classes to keep the cimi only API implementation methods separated?
> 
> Regards,
> Dies Koper
> 
>> -----Original Message-----
>> From: Dies Koper (JIRA) [mailto:jira@apache.org]
>> Sent: Saturday, 30 June 2012 7:11 PM
>> To: dev@deltacloud.apache.org
>> Subject: [jira] [Commented] (DTACLOUD-245) FGCP/DMTF: undefined
>> method `value' for hardware profile as storage is not specified
>>
>>
>>     [ https://issues.apache.org/jira/browse/DTACLOUD-
>> 245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
>> tabpanel&focusedCommentId=13404431#comment-13404431 ]
>>
>> Dies Koper commented on DTACLOUD-245:
>> -------------------------------------
>>
>> ACK.
>>
>> I've applied the patches and now instances display well, thanks!
>>
>>
>>> 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, 0002-CIMI-expose-only-supported-collections-in-
>> cloudEntry.patch, 0003-CIMI-Client-expose-only-supported-collections-in-
>> clo.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
>>
>>
>