1 .. This work is licensed under a Creative Commons Attribution 4.0
2 .. International License. http://creativecommons.org/licenses/by/4.0
3 .. Copyright 2019 ONAP Contributors. All rights reserved.
5 .. _doc_guide_user_des_pre-onb:
10 * `Create a Tenant`_ (will be moved to "Service Deployment")
11 * `Generate Manifest and Package Artifacts`_ (for HEAT based VNFs)
12 * `Validate xNF Package (VNF/PNF)`_
14 .. _doc_guide_user_des_pre-onb_cre-ten:
20 This section is not really belonging to the "Design" phase,
21 but to the preparation of the "Service Deployment" and will be
22 moved in the next release
24 Each service requires a tenant_ (a group of users who share a common access)
25 in which resources are stored in the cloud. This process is performed using
26 facilities of the network cloud, outside of ONAP. Confirm that the tenant is
27 created and note the tenant ID.
29 ONAP admin users can configure a cloud-owner to add new cloud resources.
30 These are the computing and networking resources, that will support
31 running VNFs. A cloud-owner holds a keystone URL, login, region and
32 password, in the case of an Openstack cluster. A cloud-owner also
33 belongs to a region. The region name should be the same as the Openstack
34 region. Prior to creation of a cloud-owner, its region must be created
35 first. Multiple tenants can share the same cloud-owner. Note that these
36 tenants are ONAP tenants, not Openstack tenants. Tenant register
37 services that customers are allowed to deploy. Finally, the customer is
38 like an instance of the tenant.
40 Note: there is no GUI (yet) to configure these objects. REST requests
41 are sent to AAI to achieve the configuration. For a detailed list of
42 required REST commands see:
44 https://wiki.onap.org/display/DW/running+vFW+Demo+on+ONAP+Amsterdam+Release
46 The overall process is as follows:
48 #. Create a region and a cloud-owner. This steps registers Openstack
49 credentials. This is the only step requiring entering Openstack specific
52 #. Create a complex. The complex describes the coverage of the region with
55 #. Create a service. The service name should match the name of the service
58 #. Create a tenant. Tenant in ONAP stores a design for a generic customer.
60 #. Associate tenants with their allowed services.
62 #. Create an instance of the tenant or customer. The customer is visible in
63 VID. A VID user can deploy allowed services on this new customer.
68 .. _doc_guide_user_des_pre-onb_gen-man:
70 Generate Manifest and Package Artifacts
71 ---------------------------------------
74 This section describes the steps required to package a given HEAT
75 template into a zip-file, which can be onboarded to SDC. Instructions
76 to create TOSCA based VNF or PNF Onboarding Packages are not described
79 Before onboarding resources, run generate-manifest.py to generate a
80 MANIFEST file. These steps are performed outside SDC.
82 **Prerequisites:** Obtain Heat/ENV files and other files required for
83 onboarding. The requirements are found in the following document.
89 Heat requirements <../../../../submodules/vnfrqts/requirements.git/docs/Chapter5/Heat/index.rst>
91 #. Put the Heat, ENV, nested Heat, and other files used by get-file in templates
96 - The base Heat should include "base" in the name.
97 - The ENV file name should match the name of the Heat file with which it
99 - All get-file file names need to be unique.
101 #. Put the python script in a directory one level above the directory that
102 contains the Heat/ENV and other files.
104 For example, [dir x]/[dir y]
106 - [dir y] contains the Heat/ENV files and other files
107 - [dir x] contains the python script
109 #. Run the script on the Windows command line (not valid anymore):
111 .. code-block:: python
113 python generate-manifest.py -f "dir y"
115 #. Examine the manifest file and confirm that is correct.
117 #. Package all Heat/ENV files, all other files, and the MANIFEST.json
120 .. _doc_guide_user_des_pre-onb_val:
122 Validate xNF Package (VNF/PNF)
123 ------------------------------
125 VNF and PNF packages have to follow the requirements described in:
131 VNF and PNF Modeling Requirements <../../../../submodules/vnfrqts/requirements.git/docs/Chapter5/index.rst>
132 ONAP Management Requirements <../../../../submodules/vnfrqts/requirements.git/docs/Chapter7/index.rst>
134 For Validation of VNF and PNF packages the tools delivered by VNFSDK can be
141 ../../../onap-provider/vnfvalidator.rst
143 Prior to resource onboarding, the Certification Group does the following:
146 - Validation of the delivered xNF package and artifacts
147 - using the VNF Validation Tools
149 - onboards the Heat template(s) and metadata to the SDC catalog
151 - runs the Heat scanning tools
152 - shares the results with any group that approves Virtual Functions
154 In parallel, the Certification Group onboards the VF Image and OS to a
155 standalone ONAP instance (the "sandbox") and performs the following:
158 - compatibility test for the OS and vendor binary
161 The Certification group then instantiates the VF image using the vendor
162 Heat (if provided) in order to validate that the VM can run on the Network
165 No VF functionality testing is performed at this stage.
168 .. |image1| image:: media/tenant.png
169 .. _tenant: https://wiki.onap.org/display/DW/Glossary#Glossary-tenant