openstack team mailing list archive

Thread
Date

[Nova] Consistent API validation and error responses

To: "<openstack@xxxxxxxxxxxxxxxxxxx> (openstack@xxxxxxxxxxxxxxxxxxx)" <openstack@xxxxxxxxxxxxxxxxxxx>, "dprince@xxxxxxxxxx" <dprince@xxxxxxxxxx>
From: "Karajgi, Rohit" <Rohit.Karajgi@xxxxxxxxxxx>
Date: Tue, 30 Oct 2012 14:26:37 +0000
Accept-language: en-US
Thread-index: Ac22qp/aWEoTjxbVRbiqmg1/BqBzCg==
Thread-topic: [Nova] Consistent API validation and error responses

Hi,

Referring to the bug https://bugs.launchpad.net/nova/+bug/1072734, I would like to get some thoughts around our API validation approach.

Are we looking at enhancing the API validations in Grizzly, or Nova v3 spec to ensure that all validations are made consistently "after" the Nova API layer?
Currently, image and flavor uuids are validated upfront in the v2 API, however volume uuid validation does not happen at this stage.

Though I agree with Dan's thoughts on the performance hit, ensuring that validations are consistently made for images and volumes enhances usability.
Can we consider this change for v2 API?


Best Regards,
Rohit Karajgi | Lead Engineer | NTT Data Global Technology Services Private Ltd | w. +91.20.6604.1500 x 378 |  m. +91 992.242.9639 | rohit.karajgi@xxxxxxxxxxx<mailto:rohit.karajgi@xxxxxxxxxxx>


______________________________________________________________________
Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data.  If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding