...
1 | VNF developers use the VNFSDK tools to create VNF descriptors based on the TOSCA YAML templates. VNF hardware platform capability requirements, if any, are captured in the VNF descriptor. |
2 | VNF developers use the VNFSDK tools to create VNF packages and upload them to the VNF marketplace. Uploaded packaged are validated and made available for use by ONAP operator(s). |
3 | VNF packages are downloaded from the VNF marketplace using SDC tools and on-boarded into the SDC catalog for use by ONAP service designers. |
4 | Service designers use SDC design tools to build and maintain network services. Network services are stored in the SDC catalog and made available to service consumers. |
5 | Service consumers browse the SDC catalog and choose services for instantiation. |
6 | Requests for instantiation are passed to the SO. The SO obtains NSD and VNFD information from the SDC. Hardware platform capability requirements are downloaded as part of the VNFD data. |
7 | The SO performs SO at present has 2 possible options to take over from here
Hardware platform capability requirements are passed to the OOF. |
8 | The OOF uses the resource information stored in the AAI inventory database to obtain resource topology and capabilities data. It them makes use of placement policies to determine optimal homing and placement of a given network service. |
9 | Infrastructure providers register VIMs with the Multi-VIM layer, as part of the resource on-boarding process. |
10 | During the VIM registration process, resource topology and capabilities data is discovered and persisted in the AAI inventory database. From the HPA perspective, the AAI acts as the system of record for all HPA related information. |
11 | Any "day 2" operations that require VNF (re)instantiation, are performed by calling the SO and OOF components. Therefore, no changes to the "day 2" controllers is required in support of HPA. |
...