...
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
| 1 | VNF Developers developers use VNF SDK the VNFSDK tools to create VNF descriptors based on the TOSCA YAML templates. If a given VNF has hardware platform capability dependenciesrequirements, if any, they are included captured in the VNF descriptor. |
| 2 | VNF Developers use V.NF SDK developers use the VNFSDK tools to create VNF packages and upload them to the VNF marketplace. VNF marketplace validates uploaded VNFs and makes them available for downloadUploaded packaged are validated and made available for use by ONAP operator(s). |
| 3 | The SDC downloads VNF packages are downloaded from the VNF marketplace using SDC tools and on-boards them boarded into the SDC catalog for use by Service DesignersONAP service designers. |
| 4 | Service Designers designers use SDC design tools to create build and maintain network services and make them available . Network services are stored in the catalog for use by Service ConsumersSDC catalog and made available to service consumers. |
| 5 | Service Consumers consumers browse the SDC catalog and choose a service services for instantiation. |
| 6 | Requests for instantiation are passed to the SO. The SO downloads appropriateobtains NSD and VNFD definitionsinformation from the SDC. If hardwareHardware platform capability requirements were present, theyare downloaded as wellpart of the VNFD data. |
| 7 | The SO decomposes the performs service decomposition and calls the OOF to optimize its service/VNF homing and placement. Hardware platform capability requirements are passed to the OOF as well. |
| 8 | The OOF consults uses the resource information stored in the AAI inventory database to obtain resource topology and capability informationcapabilities data. It them makes use of placement policies to determine optimal homing and placement of a given network service. |
| 9 | Infrastructure Providers providers register VIMs with the Multi-VIM layer, as part of the resource on-boarding process. |
| 10 | As part of During the VIM registration process, resource topology information and hardware platform capabilities are data is discovered and persisted in the AAI inventory database for subsequent use by the OOF. 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. |
General Assumptions
This proposal does not require changes to the ONAP architecture and makes use of the existing ONAP management components. The following diagram identifies the ONAP components affected by this project:
...