From f0e192121064c0b06308ac3c36a7df53ad099185 Mon Sep 17 00:00:00 2001 From: Rich Bennett Date: Wed, 4 Apr 2018 10:56:50 -0400 Subject: Provide structure for VNFs Add to index hierarchy guides/onap-developer/architecture Create section template vnf-reference Change-Id: If1b7b2b89de906c66e43382a9bc9dc2bee4086e5 Issue-ID: DOC-260 Signed-off-by: Rich Bennett --- docs/templates/sections/vnf-reference.rst | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 docs/templates/sections/vnf-reference.rst (limited to 'docs/templates') diff --git a/docs/templates/sections/vnf-reference.rst b/docs/templates/sections/vnf-reference.rst new file mode 100644 index 000000000..165eee530 --- /dev/null +++ b/docs/templates/sections/vnf-reference.rst @@ -0,0 +1,29 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 + +VNF +=== + +.. note:: + * This section is used to describe Virtual Network Function software + + * This section is typically provided: as additional detail on use cases, + to illustrate end to end platform architecture, and to describe + compliance with ONAP VNF requirements. + + * The VNF Heading above should be replaced with the VNF NAME + + * This note must be removed after content has been added. + +Version +------- + +User Documentation +------------------ + +Source +------ + +ONAP VNF Requirements Compliance +-------------------------------- + -- cgit 1.2.3-korg