Return-Path: 
 <dev-return-4540-apmail-deltacloud-dev-archive=deltacloud.apache.org@deltacloud.apache.org>
X-Original-To: apmail-deltacloud-dev-archive@www.apache.org
Delivered-To: apmail-deltacloud-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 742C39D35
	for <apmail-deltacloud-dev-archive@www.apache.org>;
 Mon, 21 May 2012 08:35:45 +0000 (UTC)
Received: (qmail 51273 invoked by uid 500); 21 May 2012 08:35:45 -0000
Delivered-To: apmail-deltacloud-dev-archive@deltacloud.apache.org
Received: (qmail 51142 invoked by uid 500); 21 May 2012 08:35:44 -0000
Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@deltacloud.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@deltacloud.apache.org>
List-Post: <mailto:dev@deltacloud.apache.org>
List-Id: <dev.deltacloud.apache.org>
Reply-To: dev@deltacloud.apache.org
Delivered-To: mailing list dev@deltacloud.apache.org
Received: (qmail 51089 invoked by uid 99); 21 May 2012 08:35:42 -0000
Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 May 2012 08:35:42 +0000
Received: from isssues-vm.apache.org (localhost [127.0.0.1])
	by issues-vm (Postfix) with ESMTP id C504614002E
	for <dev@deltacloud.apache.org>; Mon, 21 May 2012 08:35:41 +0000 (UTC)
Date: Mon, 21 May 2012 08:35:40 +0000 (UTC)
From: "Marios Andreou (JIRA)" <jira@apache.org>
To: dev@deltacloud.apache.org
Message-ID: <1744820787.2697.1337589341810.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <1709101896.23578.1336075968389.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (DTACLOUD-208) Odering of  Hardware Profiles
 returned from the Openstack provider by Deltacloud API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Marios Andreou closed DTACLOUD-208.
-----------------------------------


pushed to master after review - commit hash: ef31a07e467ffae110b1c1d68580a88cdad8d6ce
                
> 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: Ronelle Landy
>         Attachments: 0001-Adds-ordering-of-hardware-profiles-returned-from-the.patch
>
>
> 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