openstack/neutron-specs
Code Issues Proposed changes

Repropose pecan-switch for Liberty

Browse Source 
Updated assignees a bit as well. Kevin and Brandon are going to work
together on this for Liberty with assistance from others as needed.

Change-Id: Iab7c8ebcb580921324b913246624841ded7528bf
This commit is contained in:
Kyle Mestery 2015-04-09 08:32:51 +00:00
parent a0dc78d7ae
commit 2e94925b52
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
specs/kilo-backlog/pecan-switch.rst → specs/liberty/pecan-switch.rst
View File

@ -14,9 +14,9 @@ This document describes a plan to replace the current home-grown WSGI
framework, including REST controllers, with a solution entirely based framework, including REST controllers, with a solution entirely based
on the Pecan framework [1]_ on the Pecan framework [1]_
The specification discussed in this document assumes that the REST controllers The specification discussed in this document can make use of the V3
will dispatch calls to the plugin in a different way, leveraging a new plugin specification, though it is no longer assumed to be dependent
interface which is thoroughly discussed in [2]_ on that specification. See [2]_ for more details.
Problem Description Problem Description
=================== ===================
@ -78,11 +78,9 @@ This means that we expect the following for the Kilo release:
3) The Pecan REST controller will simply take care of serializing responses 3) The Pecan REST controller will simply take care of serializing responses
and deserializing requests into appropriate transfer objects describing and deserializing requests into appropriate transfer objects describing
API resources. However, the REST layer will no longer be responsible for API resources. Until the V3 plugin layer referenced here [2]_ is merged,
authorization and quota enforcement. These operations will be handled by REST layer will continue to be responsible for authorization and quota
the new plugin layer discussed in the spec [2]_. For the sake of this enforcement.
document it is enough to say that these operations won't be performed by
the plugin implementation.
Request validation will occur in the REST API layer. The goal is to Request validation will occur in the REST API layer. The goal is to
specify constraints using JSON schema. At the time of writing this spec it specify constraints using JSON schema. At the time of writing this spec it
has not yet been analyzed whether it is possible to express all the has not yet been analyzed whether it is possible to express all the
@ -220,12 +218,13 @@ Assignee(s)
----------- -----------
Primary assignee: Primary assignee:
Mark McClain (markmcclain)
Kevin Benton (kevinbenton) Kevin Benton (kevinbenton)
Brandon Logan (blogan)
Other contributors: Other contributors:
Sean Collins (sccal68) [developer docs] Sean Collins (sccal68) [developer docs]
Salvatore Orlando (salv-orlando) [reserve dev] Salvatore Orlando (salv-orlando) [reserve dev]
Mark McClain (markmcclain)
Work Items Work Items
---------- ----------
@ -245,7 +244,8 @@ Work Items
Dependencies Dependencies
============ ============
* New plugin interface specification [2]_ While not a direct dependency, the V3 plugin interface [2]_ is listed in the
case it is proposed again for Liberty.
Testing Testing
======= =======