On Fri, Jan 15, 2016 at 09:08:54AM +0100, Michał Dulko wrote: > On 01/15/2016 07:14 AM, Jethani, Ravishekar wrote: > > Hi Devs, > > > > I have come across a few 500 response issues while sending request > > body as XML to cinder service. For example: > > > > <snip!> > > > > I can see that XML support has been marked as depricated and will be > > removed in 'N' release. So is it still worth trying fixing these > > issues during Mitaka time frame? > > > > Thanks. > > Ravi Jethani > > One of the reasons XML API was deprecated is the fact that it weren't > getting much CI testing and as Doug Hellmann once mentioned - "if > something isn't tested then it isn't working". > > I'm okay with fixing it (if someone really needs that feature), but we > don't have any means to prevent further regressions, so it may not be > worth it.
I'm in the same boat. I think we have other more important things to focus on right now, but if there is someone that wants to submit a patch to fix these - and do their own testing to validate the fix - I'm fine with letting that through. But given that this code will all be removed shortly, I would really rather see that effort going the other way to update the API consumer's code to switch to JSON. > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
