deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Karnath (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (DTACLOUD-418) Missing href-attribute in JSON output
Date Wed, 23 Jan 2013 11:14:12 GMT

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

Christian Karnath edited comment on DTACLOUD-418 at 1/23/13 11:12 AM:
----------------------------------------------------------------------

Patch set applied fine some days ago and JSON and XML representation are consistent now (expect
'create_image' which is missing on the XML and was already mentioned by Ronelle). 
However this patch set won't apply correctly at the current development tree, because there
are some pending conflicts which must be solved. 

                
      was (Author: karnath):
    Patch set applied fine some days ago and JSON and XML representation are consistent now
(expect 'create_image' which is missing on the XML and was already mentioned by Ronelle).

However this patch set won't apply correctly at the current development tree, because there
are some pending conflicts which needs to be solved. 

                  
> Missing href-attribute in JSON output
> -------------------------------------
>
>                 Key: DTACLOUD-418
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-418
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>         Environment: Debian 6.0.6, ruby 1.9.2p0, deltacloud development
>            Reporter: Christian Karnath
>            Assignee: Michal Fojtik
>
> The 'href' attribute was present in Deltacloud 1.0.2 but it is missing in the current
development version when specifying JSON as an output format:
> Requesting /api/instances against deltacloud 1.0.2 returned:
> {
>     "instances": {
>         "instance": {
>             "name": null,
>             "owner_id": "mockuser",
>             "image": { … },
>             "realm": { … },
>             "state": "RUNNING",
>             "hardware_profile": { … },
>             "actions": { … },
>             "public_addresses": { … },
>             "private_addresses": { … },
>             "storage_volumes": null,
>             "authentication": { … },
>             "href": "https://192.168.23.101:3001/api/instances/inst0",
>             "id": "inst0"
>         }
>     }
> }
> Requesting /api/instances against deltacloud development version returns:
> {
>     "instances": [
>         {
>             "id": "inst1",
>             "name": "MockUserInstance",
>             "state": "RUNNING",
>             "owner": "mockuser",
>             "image": { … },
>             "realm": { … },
>             "actions": [ … ],
>             "instance_profile": { … },
>             "public_addresses": [ … ],
>             "private_addresses": [ … ],
>             "launch_time": null,
>             "create_image": true,
>             "storage_volumes": [ ]
>         }
>     ]
> }
> It seems that /api/images, /api/realms and so on are also inconsistent with the corresponding
xml representation (which includes the 'href'-attribute).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message