Cross Transport API Spec

Registered by Flavio Percoco on 2013-10-25

Define an API spec that supports extensions, versioning and that is also cross-transport. This will allow Zaqar to define its API in a single module and allow transport for translating the API to something supported by the protocol they implement.

It has been discussed during the Kilo summit that this feature will be implemented for non-RESTful transports. The WSGI transport won't be affected for this.

Blueprint information

Status:
Complete
Approver:
Flavio Percoco
Priority:
Medium
Drafter:
Flavio Percoco
Direction:
Needs approval
Assignee:
Victoria Martinez de la Cruz
Definition:
Approved
Series goal:
Accepted for kilo
Implementation:
Implemented
Milestone target:
milestone icon 2015.1.0
Started by
Flavio Percoco on 2014-01-14
Completed by
Flavio Percoco on 2015-02-05

Related branches

Sprints

Whiteboard

it won't be ready for i-3. Moving to Juno

Moving back to discussion, I believe this needs to be re-evaluated.
-- flaper87

This change is partially addressed by https://review.openstack.org/#/c/61476/
-- vkmc

Gerrit topic: https://review.openstack.org/#q,topic:bp/cross-transport-api-spec,n,z

Addressed by: https://review.openstack.org/140919
    Slighty refactoring for the cross api spec

Addressed by: https://review.openstack.org/141280
    API handler and API v1.1 endpoints

Addressed by: https://review.openstack.org/148265
    Refactor Request and Response classes to enhance consistency

Gerrit topic: https://review.openstack.org/#q,topic:bp/persistent-transport,n,z

Addressed by: https://review.openstack.org/164007
    Adds a status code field to the Response

Addressed by: https://review.openstack.org/164008
    Adds a representation for the Request and Response objects

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.