[openstack-dev] [Nova] Blueprint: nova-api-validation-fw
Ken'ichi Ohmichi
oomichi at mxs.nes.nec.co.jp
Wed Mar 27 06:25:13 UTC 2013
Hi MOTOKI-san,
On Tue, 26 Mar 2013 22:56:35 +0900
Akihiro MOTOKI <amotoki at gmail.com> wrote:
>
> Looks interesting.
>
> You might already know Quantum has the similar validation mechanism.
> You can find it at
> https://github.com/openstack/quantum/blob/master/quantum/api/v2/attributes.py.
> The validation logic is called in the API layer automatically.
> It is also used to define resources provided by extensions and an
> extension can extend an existing resource definition.
>
> When discussing the API validation framework, it must be another good
> example and candidate I believe.
Thanks for your advice.
I will investigate Quantum's validation mechanism for better basic design.
Thanks
Ken'ichi Ohmichi
---
> 2013/3/26 Ken'ichi Ohmichi <oomichi at mxs.nes.nec.co.jp>:
> >
> > Hi Sean,
> >
> > On Tue, 26 Mar 2013 08:24:35 -0400
> > Sean Dague <sean at dague.net> wrote:
> >> >
> >> > This is RFC of blueprint nova-api-validation-fw.
> >> > Blueprint: https://blueprints.launchpad.net/nova/+spec/nova-api-validation-fw
> >> > Details : https://wiki.openstack.org/wiki/NovaApiValidationFramework
> >> >
> >> > Nova has many RESTful APIs, and not all API parameters are completely
> >> > validated. We would like to propose an API validation framework to
> >> > implement comprehensive validation.
> >> > The benefits of this framework will be the followings:
> >> > * Validate every API parameters.
> >> > * Unify both message format and HTTP code of error response, if
> >> > the same cause.
> >> > ex) ".. is too short.", ".. is too long.", ".. is not integer."
> >> > * Clarify the API parameter definitions.
> >> > * Clean up codes by merging error handling methods.
> >> >
> >> > Using the JSON Schema library, we have created a prototype and examined
> >> > this API validation framework. The following URL is the prototype code.
> >> > https://review.openstack.org/25358
> >> >
> >> > We'd like to discuss the framework design, so any comments are welcome.
> >>
> >> This looks like a nice start, and it would be really good to consolidate
> >> the validation to a central point.
> >
> > Thanks, the comment encouraged me.
> >
> >> Have you submitted a design summit session on this as well?
> >
> > Yes, I have submitted a session(http://summit.openstack.org/cfp/details/183).
> >
> >
> > Thanks
> > Ken'ichi Ohmichi
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> --
> Akihiro MOTOKI <amotoki at gmail.com>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
More information about the OpenStack-dev
mailing list