...
| PlantUML Macro | ||
|---|---|---|
| ||
@startuml participant OSS_BSS participant SDC participant SO participant ETSI_Catalog_Mgr participant SOL003_Adapter participant SOL005_Adapter participant VNFM participant NFVO autonumber OSS_BSS -> SDC : Vendor SOL004 package onboarding,\nincluding SOL001 VNFD SDC -> SO : SDC VNF package including\nthe original vendor SOL004 VNF package SO -> ETSI_Catalog_Mgr : Store VNF package including\n the original vendor package opt VNFM -> SOL003_Adapter : Request for a VNF package SOL003_Adapter -> ETSI_Catalog_Mgr : Request for a VNF package ETSI_Catalog_Mgr -> SOL003_Adapter : Response with a VNF package SOL003_Adapter -> VNFM : Response with a VNF package end opt NFVO -> SOL005_Adapter : Request for a NS package SOL005_Adapter -> ETSI_Catalog_Mgr : Request for a NS package ETSI_Catalog_Mgr -> SOL005_Adapter : Response with a NS package SOL005_Adapter -> NFVO : Response with a NS package end @enduml |
- Open Issues:
- Will the external NFVO get the NS package thru ETSI Catalog Mgr and SOL005 Adapter? <need input from Verizon>
- Does the SOL002 Adapter need packages?
Package Security
A VNF package uses the signature and certificate to ensure package integrity and validity. A CSAR file is digitally signed with the VNF provider private key. During the VNF package onboarding to SDC, SDC validates the package and then does the following:
...