On Wed, Feb 25, 2015, at 09:33 AM, Eugeniya Kudryashova wrote: > Hi, stackers! > > As was suggested in topic , using an HTTP header was a good solution > for > communicating common/standardized OpenStack API error codes. > > So I’d like to begin working on a common library, which will collect all > openstack HTTP API errors, and assign them string error codes. My > suggested > name for library is openstack.error, but please feel free to propose > something different. > > The other question is where we should allocate such project, in openstack > or stackforge, or maybe oslo-incubator? I think such project will be too > massive (due to dealing with lots and lots of exceptions) to allocate it > as a part of oslo, so I propose developing the project on Stackforge and > then eventually have it moved into the openstack/ code namespace when the > other projects begin using the library. > > Let me know your feedback, please!
I'm not sure a single library as a home to all of the various error messages is the right approach. I thought, based on re-reading the thread you link to, that the idea was to come up with a standard schema for error payloads and then let the projects fill in the details. We might need a library for utility functions, but that wouldn't actually include the error messages. Did I misunderstand? Doug > > >  - > http://lists.openstack.org/pipermail/openstack-dev/2015-January/055549.html > __________________________________________________________________________ > 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 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