Overview: Nova has many RESTful APIs, and not all API parameters are completely validated. To implement comprehensive validations, I'd like to propose Nova API validation framework. The benefits of this framework will be the followings: * Validate every API parameters. * Unify an error message format of the response, if the same cause. ex) ".. is too short.", ".. is too long.", ".. is not integer." * Clarify the API parameter definitions. * Clean up codes, because of merging error handling methods.
Talking points: I created a prototype for API validation framework, and found some points which need discussions. I'd like to talk/discuss about the following in this session: * Overview of API validation framework * Plans for Havana release ** Current development status ** What are TODOs for Havana? ** Migration plans (How to apply the framework to all APIs smoothly) Need Nova community agreement because of many implementations and reviews. Need useful framework to implement each API validation step by step. Need some implementation rules to achieve all APIs by Havana release. * Next features of the framework * And more
Related Summit Talk: There was a similar session in Grizzly Design Summit, and the session contained good discussions for API validation: * Refactoring API Input Validation: https://etherpad.openstack.org/grizzly-nova-input-validation In the session proposed by me, I'd like to discuss how to achieve implementations of all APIs based on some prototype.
