Re: [Openstack] [openstack-dev] [nova] Call for Help -- OpenStack API XML Support

2012-08-10 Thread George Reese
On Aug 10, 2012, at 2:52 PM, Jay Pipes wrote: > On 08/09/2012 11:05 PM, George Reese wrote: >> On Aug 9, 2012, at 8:14 PM, Doug Davis > > wrote: >>> Situations like this are always interesting to watch. :-) >>> >>> On the one hand its open-source, so if you care about s

Re: [Openstack] [openstack-dev] [nova] Call for Help -- OpenStack API XML Support

2012-08-10 Thread Jay Pipes
On 08/09/2012 11:05 PM, George Reese wrote: > On Aug 9, 2012, at 8:14 PM, Doug Davis > wrote: >> Situations like this are always interesting to watch. :-) >> >> On the one hand its open-source, so if you care about something then >> put up the resources to make it happen.

Re: [Openstack] [openstack-dev] [nova] Call for Help -- OpenStack API XML Support

2012-08-10 Thread Kevin L. Mitchell
On Fri, 2012-08-10 at 09:52 -0500, George Reese wrote: > I personally believe (and this is described in great detail in my API > book) that you never, ever auto-generate JSON and XML from model > objects for your REST APIs. You need your models to be free to evolve > independent from the API repres

Re: [Openstack] [openstack-dev] [nova] Call for Help -- OpenStack API XML Support

2012-08-10 Thread George Reese
This doesn't fit into the "things that make me grumpy" bucket, but instead an opinion on how APIs should be doneā€¦ I personally believe (and this is described in great detail in my API book) that you never, ever auto-generate JSON and XML from model objects for your REST APIs. You need your mode

Re: [Openstack] [openstack-dev] [nova] Call for Help -- OpenStack API XML Support

2012-08-09 Thread Vishvananda Ishaya
On Aug 9, 2012, at 6:28 PM, Daryl Walleck wrote: > As part of my work on Tempest, I've created an alternate backend > configuration to use XML requests/responses. This right now mostly covers > Nova, but could easily be extended to test other projects as well. I hadn't > pushed it yet because

Re: [Openstack] [openstack-dev] [nova] Call for Help -- OpenStack API XML Support

2012-08-09 Thread George Reese
On Aug 9, 2012, at 8:14 PM, Doug Davis wrote: > > Situations like this are always interesting to watch. :-) > > On the one hand its open-source, so if you care about something then put up > the resources to make it happen. This attitude always bothers me. This isn't some Open Source labor

Re: [Openstack] [openstack-dev] [nova] Call for Help -- OpenStack API XML Support

2012-08-09 Thread Daryl Walleck
As part of my work on Tempest, I've created an alternate backend configuration to use XML requests/responses. This right now mostly covers Nova, but could easily be extended to test other projects as well. I hadn't pushed it yet because it seemed to be low priority, but I'd be more than glad to

Re: [Openstack] [openstack-dev] [nova] Call for Help -- OpenStack API XML Support

2012-08-09 Thread Doug Davis
Situations like this are always interesting to watch. :-) On the one hand its open-source, so if you care about something then put up the resources to make it happen. On the other hand, that doesn't mean that as a developer you get to ignore the bigger picture and only do 1/2 of the work becaus

Re: [Openstack] [openstack-dev] [nova] Call for Help -- OpenStack API XML Support

2012-08-09 Thread Christopher B Ferris
: ->To: OpenStack Development Mailing List>>From: Vishvananda Ishaya >Sent by: openstack-bounces+chrisfer=us.ibm@lists.launchpad.net>Date: 08/09/2012 07:05PM>Cc: "openstack@lists.launchpad.net \(openstack@lists.launchpad.net\)">>Subject: Re: [Openstack] [o

Re: [Openstack] [openstack-dev] [nova] Call for Help -- OpenStack API XML Support

2012-08-09 Thread Vishvananda Ishaya
On Aug 9, 2012, at 3:32 PM, George Reese wrote: > Why aren't the integration tests both XML and JSON? The simple answer is that no one has taken the time to write them. Our devstack exercises use the python client bindings. Tempest has json clients but no xml clients[1]. I think this demonstr