From 8048568b27c8b6fb5a5a269c66f722bceb4b338d Mon Sep 17 00:00:00 2001 From: Georg Kunz Date: Wed, 2 May 2018 22:44:00 +0200 Subject: Adding documentation for API validation exemption Updating the user guide and OVP addendum to include references to the detailed document describing the API response validation exemption. JIRA: DOVETAIL-651 Change-Id: I4026f84f021704f0986b45680471e8fb711fc314 Signed-off-by: Georg Kunz --- docs/testing/user/ovpaddendum/index.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'docs/testing/user/ovpaddendum/index.rst') diff --git a/docs/testing/user/ovpaddendum/index.rst b/docs/testing/user/ovpaddendum/index.rst index a78d1997..054a3f11 100644 --- a/docs/testing/user/ovpaddendum/index.rst +++ b/docs/testing/user/ovpaddendum/index.rst @@ -414,6 +414,18 @@ documented and accepted by the reviewers. Applicants who choose to run the optional test cases can include the results of the optional test cases to highlight the additional compliance. + +Exemption from strict API response validation +============================================= + +Vendors of commercial NFVI products may have extended the Nova API to support +proprietary add-on features. These additions can cause Nova Tempest API tests +to fail due to unexpected data in API responses. In order to resolve this +transparently in the context of OVP, a temporary exemption process has been +created. More information on the exemption can be found in section +:ref:`dovetail-exemption_process_api_response_validation`. + + .. References .. _`OVP Governance Guidelines`: https://www.opnfv.org/wp-content/uploads/sites/12/2018/01/OVP-Governance-Guidelines-1.0.1-012218.pdf .. _`Pharos specification`: https://wiki.opnfv.org/display/pharos/Pharos+Specification -- cgit 1.2.3-korg