Re: [openstack-dev] [qa][swift] Signature of return values in tempest swift client
On Fri, Feb 13, 2015 at 2:15 PM, David Kranz dkr...@redhat.com wrote: Swift is different in that most interesting data is in the headers except for GET methods, and applying the same methodology as the others does not make sense to me. There are various ways the swift client could be changed to return one value, or it could be left as is. Can you point to the relevant implementation? FWIW, we've found in swiftclient that's it's been extremely restrictive to return tuples and in retrospect would have preferred either a (status, headers, body) signature (which unfortunately leaves a lot of interesting parsing up to the client) or something more like a dictionary or SwiftResponse that as described in the spec has properties for getting at interesting values - and most importantly allow for future additive changes. It sounds like you're on the right track trying to make clients return a single value (or a dict or something) - I'm tertiarily curious with what you come up. -Clay __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [qa][swift] Signature of return values in tempest swift client
Almost all of the OpenStack REST apis return little of user value in the response headers, with json bodies containing the returned data. The tempest client methods had been returning two values with one always being ignored. To clean that up before moving the service clients to tempest-lib, we changed the client methods to return one value instead as recorded in this blueprint: https://blueprints.launchpad.net/tempest/+spec/clients-return-one-value. This is mostly done except for swift. Swift is different in that most interesting data is in the headers except for GET methods, and applying the same methodology as the others does not make sense to me. There are various ways the swift client could be changed to return one value, or it could be left as is. I am soliciting proposals from those most interested in the swift tests. If there is no input or consensus on how this should be changed, I will leave the swift client as-is and close the blueprint. -David __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
