Open Stack

According to the most recent user survey, more than 30% of users consume 
the XML API.

Regards,


Tom

On 14/01/14 00:06, 郭龙仓 wrote:
> approve.
>
> 2014年1月13日 下午11:39于 "Sean Dague" <sean at dague.net
> <mailto:sean at dague.net>>写道：
>
>     This is a thread on the openstack-dev list, but Russell wisely thought
>     we should get broader openstack community input.
>
>     Now is the time for opinions. Please be civil, but please express them,
>     because it will impact the decision in Nova v3 in icehouse.
>
>
>     -------- Original Message --------
>     Subject: [nova] [rfc] drop XML from v3 API entirely
>     Date: Mon, 13 Jan 2014 09:38:47 -0500
>     From: Sean Dague <sean at dague.net <mailto:sean at dague.net>>
>     To: OpenStack Development Mailing List (not for usage questions)
>     <openstack-dev at lists.openstack.org
>     <mailto:openstack-dev at lists.openstack.org>>
>
>     I know we've been here before, but I want to raise this again while
>     there is still time left in icehouse.
>
>     I would like to propose that the Nova v3 API removes the XML payload
>     entirely. It adds complexity to the Nova code, and it requires
>     duplicating all our test resources, because we need to do everything
>     onces for JSON and once for XML. Even worse, the dual payload strategy
>     that nova employed leaked out to a lot of other projects, so they now
>     think maintaining 2 payloads is a good thing (which I would argue it is
>     not).
>
>     As we started talking about reducing tempest concurrency in the gate, I
>     was starting to think a lot about what we could shed that would let us
>     keep up a high level of testing, but bring our overall time back down.
>     The fact that Nova provides an extremely wide testing surface makes this
>     challenging.
>
>     I think it would be a much better situation if the Nova API is a single
>     payload type. The work on the jsonschema validation is also something
>     where I think we could get to a fully discoverable API, which would
>     be huge.
>
>     If we never ship v3 API with XML as stable, we can deprecate it
>     entirely, and let it die with v2 ( probably a year out ).
>
>              -Sean
>
>     --
>     Sean Dague
>     Samsung Research America
>     sean at dague.net <mailto:sean at dague.net> / sean.dague at samsung.com
>     <mailto:sean.dague at samsung.com>
>     http://dague.net
>
>
>
>     --
>     Sean Dague
>     Samsung Research America
>     sean at dague.net <mailto:sean at dague.net> / sean.dague at samsung.com
>     <mailto:sean.dague at samsung.com>
>     http://dague.net
>
>
>     _______________________________________________
>     Mailing list:
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>     Post to     : openstack at lists.openstack.org
>     <mailto:openstack at lists.openstack.org>
>     Unsubscribe :
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>