From ece05dc96677e0b3f210117c6e17b00b87fdc1e0 Mon Sep 17 00:00:00 2001 From: Hagop Bozawglanian Date: Thu, 7 Feb 2019 18:59:56 +0000 Subject: VNFRQTS - Removing unused footnotes Issue-ID: VNFRQTS-551 Change-Id: I89081c98e46e8ace2f3bdf054ffd09684b1312df Signed-off-by: Hagop Bozawglanian --- docs/Chapter2.rst | 27 --------------------------- 1 file changed, 27 deletions(-) (limited to 'docs') diff --git a/docs/Chapter2.rst b/docs/Chapter2.rst index ad7219b..3f02e5c 100644 --- a/docs/Chapter2.rst +++ b/docs/Chapter2.rst @@ -65,30 +65,3 @@ VNF Requirements corresponding Information Elements w/Range limits ------------------------------------------------------------------------------ Will be generated in future releases. - -.. [#4.1.1] - Refer to NCSP’s Network Cloud specification - -.. [#4.5.1] - Refer to NCSP’s Network Cloud specification - -.. [#4.5.2] - Not currently supported in ONAP release 1 - -.. [#7.3.1] - https://github.com/mbj4668/pyang - -.. [#7.3.2] - Recall that the Node Object **is required** to be identical across - all VMs of a VNF invoked as part of the action except for the "name". - -.. [#7.3.3] - Upstream elements must provide the appropriate FQDN in the request to - ONAP for the desired action. - -.. [#7.3.4] - Multiple ONAP actions may map to one playbook. - -.. [#7.4.1] - This option is not currently supported in ONAP and it is currently - under consideration. -- cgit 1.2.3-korg