[openstack-dev] [Neutron] REST API - entity level validation

Avishay Balderman AvishayB at Radware.com
Mon Jun 16 11:27:50 UTC 2014

Will Neutron is going to follow Nova?


From: Salvatore Orlando [mailto:sorlando at nicira.com]
Sent: Monday, June 16, 2014 12:36 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] REST API - entity level validation


what you say here is correct.
However, as we are in the process of moving to Pecan as REST API framework I would probably refrain from adding new features to it at this stage.

Therefore, even if far from ideal, this kind of validation should perhaps be performed in the DB layer. I think this already happens for several API resources.


On 5 June 2014 13:01, Avishay Balderman <AvishayB at radware.com<mailto:AvishayB at radware.com>> wrote:
With the current REST API engine in neutron we can declare attributes validations.
We have a rich set of validation functions https://github.com/openstack/neutron/blob/master/neutron/api/v2/attributes.py
However we do not have the concept of entity level validation.

I have an API ‘create-something’ and Something is an entity having 2 attributes:
Something {
  Attribute A
 Attribute B
And according to the business logic A must be greater than B

As for today our framework cannot handle  this kind of validation and the call is going inside a lower layer of neutron and must be validated there.
Example: https://review.openstack.org/#/c/93871/9

With this we have the validations implemented across multi layers. I think we better have the validations in one layer.



OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140616/afe62c3e/attachment.html>

More information about the OpenStack-dev mailing list