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?)
Also, there may be some more spring cleaning left?
cimi/addresses returns a 404 and cimi/vsps gives the following error:
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:[email protected]]
> Sent: Saturday, 30 June 2012 7:11 PM
> To: [email protected]
> 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
>
>
