[openstack-tc] recommendation to deprecate XML in new major API versions

Doug Hellmann doug.hellmann at dreamhost.com
Tue Jan 14 14:29:07 UTC 2014

On Tue, Jan 14, 2014 at 9:20 AM, Sean Dague <sean at dague.net> wrote:

> On 01/14/2014 09:03 AM, Thierry Carrez wrote:
> > Added to the TC backlog.
> >
> > Note: while we know that this is unlikely to be very productive, we
> > still need to discuss that in public rather than on a moderated ML... so
> > I propose we reuse the openstack-dev Nova v3 API no-xml thread to
> > further discuss that. If for any reason the discussion there ends up way
> > too nova-specific, we should probably have a specific thread about this
> > universal "recommendation" sometimes next week.
> So I am definitely going to keep driving those threads on open lists as
> well. However, the way these conversations have gone in the past is in
> circles, then petering out. And we never decided anything other than
> status quo.
> As I'm responsible for part of the status quo I think it's important to
> be deliberate about this, not inertial.
> I think this is very much in the realm of technical direction for the
> overall project, so at the end of the day should be a TC decision. It
> should come with as much feedback as people want, however you will never
> get a decision out of the mailing lists, you'll just get feedback.
> The role of the TC is to make these kinds of recommendations. So the
> reason for taking it here as well is:
>  - ensure this is something we could do before icehouse release
>  - ensure that if there is specific information people feel they need
> before making a decision, we figure out what that is, so we can go and
> get it

I agree here, both with the assessment of previous discussions on this
topic and with the idea that we should try to set some direction.

I would like to see an affirmative statement from the TC like "We are
planning to start dropping XML support in APIs during Juno in order to
focus our limited development resources" (or a later release, or "we are
going to keep doing XML whether we like it or not") posted to the mailing
list for feedback, rather than the open-ended "what do you want" questions
we've been posing.

Who knows, maybe we'll end up with someone managing an XML-API-proxy
program to turn all of those JSON messages into XML. ;-)


>         -Sean
> --
> Sean Dague
> Samsung Research America
> sean at dague.net / sean.dague at samsung.com
> http://dague.net
> _______________________________________________
> OpenStack-TC mailing list
> OpenStack-TC at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-tc/attachments/20140114/96ca5d77/attachment.html>

More information about the OpenStack-TC mailing list