From 2cbffc5b71c88fd858b654335731ea72fd80220c Mon Sep 17 00:00:00 2001 From: "stark, steven" Date: Tue, 26 Jun 2018 13:34:59 -0700 Subject: [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 --- docs/Chapter5/VNFM-Driver-Development-Steps.rst | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 docs/Chapter5/VNFM-Driver-Development-Steps.rst (limited to 'docs/Chapter5/VNFM-Driver-Development-Steps.rst') 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. -- cgit 1.2.3-korg