deltacloud-dev mailing list archives

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

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

Michal Fojtik commented on DTACLOUD-418:
----------------------------------------

Patch sent for review to list:

http://tracker.deltacloud.org/set/253

commit b099704e53ea8a41e294d1d8dd49bae3eb07b3bd
Author: Michal Fojtik <mfojtik@redhat.com>
Date:   Wed Jan 16 13:20:05 2013 +0100

    Core: Added 'href' attribute to JSON output (DTACLOUD-418)
                
> 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