blob: 9eb757f90030416228ac167a81a09b7b9cfc195b [file] [log] [blame]
Chris Donley17032db2017-09-20 06:42:44 -07001.. This work is licensed under a Creative Commons Attribution 4.0 International License.
2
Chris Donley29648052017-10-05 11:40:40 -07003
4VNFSDK Documentation
5====================
6
Chris Donley17032db2017-09-20 06:42:44 -07007.. toctree::
8 :maxdepth: 1
Chris Donley825678b2017-10-02 10:06:12 -07009 :titlesonly:
Chris Donley17032db2017-09-20 06:42:44 -070010
Chris Donley825678b2017-10-02 10:06:12 -070011 files/vnfsdk-apis
Chris Donley17032db2017-09-20 06:42:44 -070012
Chris Donley1ac02e72017-09-21 08:59:41 -070013Components
14----------
Chris Donley17032db2017-09-20 06:42:44 -070015
Chris Donleyfecfefd2017-09-22 09:25:38 -070016VNF Packaging Model/Blueprint
17-----------------------------
Chris Donley1ac02e72017-09-21 08:59:41 -070018
Chris Donley17032db2017-09-20 06:42:44 -070019VNF product model/blueprint provides a declarative way to define deployment, operational and functional attributes of a VNF product. The VNF product is defined in terms of deployment time requirements and dependencies and exposed telemetry indicator definitions.
20
21The deployment time requirements and dependencies define any and all compute infrastructure needs of the VNF product, such as specific hardware architecture, on-chip features, instruction set availability and hypervisor capabilities.
22
23The telemetry indicator definitions define a set of default indicators exposed by a given VNF product for use by monitoring and assurance tools. This list can be extended and customized once a given VNF product is on-boarded and instantiated at run-time.
24
25The VNF product model is specified using the TOSCA NFV simple profile. It is persisted, along with the product executables and data, using TOSCA CSAR files.
26
Chris Donley825678b2017-10-02 10:06:12 -070027.. toctree::
28 :maxdepth: 1
29 :titlesonly:
Chris Donley29648052017-10-05 11:40:40 -070030 :glob:
Chris Donley825678b2017-10-02 10:06:12 -070031
Chris Donley29648052017-10-05 11:40:40 -070032 files/pkgtool
33 files/*blueprints
Chris Donley825678b2017-10-02 10:06:12 -070034
Chris Donleydbf7fb12017-10-06 16:45:44 -070035VNF SDK Marketplace
36-------------------
Chris Donley2edcb8b2017-10-10 11:20:43 -070037
38.. include:: files/marketplace-overview.rst
39
40Installation instructions
41-------------------------
42
Chris Donleydbf7fb12017-10-06 16:45:44 -070043.. toctree::
44 :maxdepth: 1
45
Chris Donley2edcb8b2017-10-10 11:20:43 -070046 files/mktplace-install
Chris Donleydbf7fb12017-10-06 16:45:44 -070047
Chris Donleyfecfefd2017-09-22 09:25:38 -070048VNF SDK Tools
49-------------
Chris Donley1ac02e72017-09-21 08:59:41 -070050
Chris Donley17032db2017-09-20 06:42:44 -070051VNF SDK tools provide VNF product DevOps engineers with command line tools and client side API language bindings to define the VNF product model and package content. The following tools are included...
52
53• VNF Package Builder - creates a CSAR file based on inputs provided by the VNF product DevOps engineer
54
55• VNF Package Validator - validates the content of the VNF packages to ensure that everything has been built correctly
56
57• VNF Package Extractor - extracts VNF product model and executables from the CSAR file
58
59• VNF Package Parser - translates VNF proeduct blueprint into a format consumable by OPEN-O components
60
61• VNF Package Dry Run - performs a "dry run" install to ensure that the package can be deployed during instantiation
62
Chris Donley17032db2017-09-20 06:42:44 -070063
Chris Donleyfecfefd2017-09-22 09:25:38 -070064User Guides
65-----------
Chris Donley1ac02e72017-09-21 08:59:41 -070066
Chris Donleyfecfefd2017-09-22 09:25:38 -070067VNF Package Tools User Guide
68----------------------------
Chris Donley17032db2017-09-20 06:42:44 -070069
70VNF Package Designer, provides VNF product DevOps engineers with a graphical tool to define the VNF product model and package content. It is made available as part of the VNF Supplier SDK tools.The package designer makes use of the VNF SDK command line interfaces (CLIs) and client-side API language bindings in order to define the model and the package content. As such, it is functionally equivalent to the VNF SDK tools.
71
Chris Donley825678b2017-10-02 10:06:12 -070072.. toctree::
73 :maxdepth: 1
74 :titlesonly:
Chris Donley29648052017-10-05 11:40:40 -070075 :glob:
Chris Donley825678b2017-10-02 10:06:12 -070076
Chris Donley29648052017-10-05 11:40:40 -070077 files/*Bundling*
Chris Donley825678b2017-10-02 10:06:12 -070078
Chris Donleyfecfefd2017-09-22 09:25:38 -070079Marketplace User Guide for Operators
80------------------------------------
Chris Donley17032db2017-09-20 06:42:44 -070081
Chris Donleydbf7fb12017-10-06 16:45:44 -070082.. toctree::
83 :maxdepth: 1
84 :titlesonly:
85
86 files/VNFSDK-Marketplace-userguide-operators
Chris Donley17032db2017-09-20 06:42:44 -070087
Chris Donleyfecfefd2017-09-22 09:25:38 -070088Marketplace User Guide for VNF Suppliers
89----------------------------------------
Chris Donley17032db2017-09-20 06:42:44 -070090
Chris Donleydbf7fb12017-10-06 16:45:44 -070091.. toctree::
92 :maxdepth: 1
93 :titlesonly:
94
95 files/VNFSDK-Marketplace-userguide-vendors
96