deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dies Koper (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DTACLOUD-208) Odering of Hardware Profiles returned from the Openstack provider by Deltacloud API
Date Fri, 04 May 2012 00:18:55 GMT

    [ https://issues.apache.org/jira/browse/DTACLOUD-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267974#comment-13267974
] 

Dies Koper commented on DTACLOUD-208:
-------------------------------------

Just wanted to comment that although for FGCP the order is the same as the backend reports,
I thought it would be nice if DC ordered the profiles in some defined order (cpu/memory low
to high for example) instead of leaving it to the provider.
                
> Odering of  Hardware Profiles returned from the Openstack provider by Deltacloud API
> ------------------------------------------------------------------------------------
>
>                 Key: DTACLOUD-208
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-208
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>         Environment: Deltacloud git commit version: c13da7b50bbbbdc529b42207f58dbe5099006ad1
> RHEL 6.2, Fedora 16
> Openstack V2.0
>            Reporter: Ronelle Landy
>            Assignee: Marios Andreou
>
> The Hardware_profiles seem to be returned out of order from Deltacloud API  (looks different
to the HP's interface ordering):
> curl -X GET --user "<un>:<pw>" "http://qe-blade-14.idm.lab.bos.redhat.com:3008/api/hardware_profiles?format=xml"
> <?xml version='1.0' encoding='utf-8' ?>
> <hardware_profiles>
>   <hardware_profile href='http://qe-blade-14.idm.lab.bos.redhat.com:3008/api/hardware_profiles/100'
id='100'>
>     <name>100</name>
>     <property kind='fixed' name='architecture' unit='label' value='x86_64' />
>     <property kind='fixed' name='memory' unit='MB' value='1024' />
>     <property kind='fixed' name='cpu' unit='count' value='1' />
>     <property kind='fixed' name='storage' unit='GB' value='30' />
>   </hardware_profile>
>   <hardware_profile href='http://qe-blade-14.idm.lab.bos.redhat.com:3008/api/hardware_profiles/101'
id='101'>
>     <name>101</name>
>     <property kind='fixed' name='architecture' unit='label' value='x86_64' />
>     <property kind='fixed' name='memory' unit='MB' value='2048' />
>     <property kind='fixed' name='cpu' unit='count' value='2' />
>     <property kind='fixed' name='storage' unit='GB' value='60' />
>   </hardware_profile>
>   <hardware_profile href='http://qe-blade-14.idm.lab.bos.redhat.com:3008/api/hardware_profiles/105'
id='105'>
>     <name>105</name>
>     <property kind='fixed' name='architecture' unit='label' value='x86_64' />
>     <property kind='fixed' name='memory' unit='MB' value='32768' />
>     <property kind='fixed' name='cpu' unit='count' value='8' />
>     <property kind='fixed' name='storage' unit='GB' value='960' />
>   </hardware_profile>
>   <hardware_profile href='http://qe-blade-14.idm.lab.bos.redhat.com:3008/api/hardware_profiles/103'
id='103'>
>     <name>103</name>
>     <property kind='fixed' name='architecture' unit='label' value='x86_64' />
>     <property kind='fixed' name='memory' unit='MB' value='8192' />
>     <property kind='fixed' name='cpu' unit='count' value='4' />
>     <property kind='fixed' name='storage' unit='GB' value='240' />
>   </hardware_profile>
>   <hardware_profile href='http://qe-blade-14.idm.lab.bos.redhat.com:3008/api/hardware_profiles/102'
id='102'>
>     <name>102</name>
>     <property kind='fixed' name='architecture' unit='label' value='x86_64' />
>     <property kind='fixed' name='memory' unit='MB' value='4096' />
>     <property kind='fixed' name='cpu' unit='count' value='2' />
>     <property kind='fixed' name='storage' unit='GB' value='120' />
>   </hardware_profile>
>   <hardware_profile href='http://qe-blade-14.idm.lab.bos.redhat.com:3008/api/hardware_profiles/104'
id='104'>
>     <name>104</name>
>     <property kind='fixed' name='architecture' unit='label' value='x86_64' />
>     <property kind='fixed' name='memory' unit='MB' value='16384' />
>     <property kind='fixed' name='cpu' unit='count' value='4' />
>     <property kind='fixed' name='storage' unit='GB' value='480' />
>   </hardware_profile>
> </hardware_profiles>
> Logging this JIRA as it seems like something that might impact Conductor's list of hardware
profiles returned - although I am not sure about how Conductor returns this list. Feel free
to close this JIRA out if it is deemed 'not needed'. Never the less, the order seems a little
off.

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

        

Mime
View raw message