summaryrefslogtreecommitdiffstats
path: root/docs/Chapter5/VNFM-Driver-Development-Steps.rst
diff options
context:
space:
mode:
authorstark, steven <ss820f@att.com>2018-06-26 13:34:59 -0700
committerstark, steven <ss820f@att.com>2018-06-27 12:18:17 -0700
commit2cbffc5b71c88fd858b654335731ea72fd80220c (patch)
tree695110bcb0d91fa22f607363b9803643dc67d233 /docs/Chapter5/VNFM-Driver-Development-Steps.rst
parent8274f893dd8e46a320a3a2b7a5c44430a8d4e765 (diff)
[VNFRQTS] break up larger rst files into toxtree
Broke all chapter files up so they follow the same patter Change-Id: I8a2152b92f0568cf4858615054bb66fabf0ea343 Issue-ID: VNFRQTS-253 Signed-off-by: stark, steven <ss820f@att.com>
Diffstat (limited to 'docs/Chapter5/VNFM-Driver-Development-Steps.rst')
-rw-r--r--docs/Chapter5/VNFM-Driver-Development-Steps.rst19
1 files changed, 19 insertions, 0 deletions
diff --git a/docs/Chapter5/VNFM-Driver-Development-Steps.rst b/docs/Chapter5/VNFM-Driver-Development-Steps.rst
new file mode 100644
index 0000000..ac06e9c
--- /dev/null
+++ b/docs/Chapter5/VNFM-Driver-Development-Steps.rst
@@ -0,0 +1,19 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. Copyright 2017 AT&T Intellectual Property. All rights reserved.
+
+VNFM Driver Development Steps
+-----------------------------
+
+Refer to the ONAP documentation for VNF Provider instructions on integrating
+vendor-specific VNFM adaptors with VF-C. The VNF driver development steps are
+highlighted below.
+
+1. Use the VNF SDK tools to design the VNF with TOSCA models to output
+the VNF TOSCA package. Using the VNF SDK tools, the VNF package can be
+validated and tested.
+
+2. The VNF Provider supplies a vendor-specific VNFM driver in ONAP, which
+is a microservice providing a translation interface from VF-C to
+the vendor-specific VNFM. The interface definitions of vendor-specific
+VNFM adaptors are supplied by the VNF Providers themselves.