OS API 1.1 has id and uuid in server details

[Mark Washenberger]

For example, in this response:

{
    "server": {
        "addresses": {
            "private": [],
            "public": []
        },
        "adminPass": "my_password",
        "flavorRef": "http://127.0.0.1:8774/v1.1/flavors/1",
        "hostId": "",
        "id": 33,
        "imageRef": 3,
        "links": [
            {
                "href": "http://127.0.0.1:8774/v1.1/servers/33",
                "rel": "self"
            },
            {
                "href": "http://127.0.0.1:8774/v1.1/servers/33",
                "rel": "bookmark",
                "type": "application/json"
            },
            {
                "href": "http://127.0.0.1:8774/v1.1/servers/33",
                "rel": "bookmark",
                "type": "application/xml"
            }
        ],
        "metadata": {
            "key1": "value1",
            "key2": "value2"
        },
        "name": "testserver",
        "status": "BUILD",
        "uuid": "97ce15ba-32b3-4c8b-b5b0-e51f2ed3add2"
    }
}

I believe there should only be the 'id' field, and its value should be the value of the 'uuid' field.

[Thierry Carrez (ttx)]

Looking at the spec, the uuid field is certainly superfluous, but I'm not sure its value should replace the one under id.

[Thierry Carrez (ttx)]

@Mark: Could you motivate a bit more this id = uuid request ?

[Brian Waldon (bcwaldon)]

@Thierry: I think there are two motives here --
1) The spec indicates communicating a single 'id' field
2) We do not need to provide two unique fields to the user

[Openstack Gerrit (openstack-gerrit)]

Reviewed: https://review.openstack.org/964
Committed: http://github.com/openstack/nova/commit/e1a743a7eab1aaa8686873fc94249cefebd90e7c
Submitter: Jenkins
Branch: master

 status fixcommitted
 done

commit e1a743a7eab1aaa8686873fc94249cefebd90e7c
Author: Mark Washenberger <email address hidden>
Date: Wed Oct 19 14:12:23 2011 -0400

    Use UUIDs instead of IDs for OSAPI servers.

    Continues to support both UUIDs and IDs in the compute and db layers,
    but only exposes UUIDs in the ID fields of OSAPI responses. Technically,
    old ID-based URIs still work, but you likely can't find them any longer.
    This only affects servers--images and flavors still use integer IDs.

    Fixes bug 804093

    Change-Id: Iecf25c5402f355dd3f227b87a936fcc1b81371b6