Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

PlantUML Macro
typedot
@startuml
participant OSS_BSS
participant SDC
participant SO
participant ETSI_Catalog_Mgr
participant SOL003_Adapter
participant SOL005_Adapter
participant VNFM
participant VFC
participant Ext_NFVO
autonumber 

	OSS_BSS -> SDC : Vendor SOL004 package onboarding,\nincluding SOL001 VNFD

group VNF PACKAGE TO SVNFM
	SDC -> SO : SDCONAP VNFinternal package with the including\nthe originalnoriginal vendor SOL004 VNF packageCSAR/Zip
	SO -> ETSI_Catalog_Mgr: :store StoreONAP VNFinternal package including\nnwith the original vendor package
optCSAR/Zip
	VNFMETSI_Catalog_Mgr -> SOL003_Adapter : Requestretrieve forthe aoriginal VNFvendor packageCSAR/Zip
	SOL003_Adapter -> ETSI_Catalog_MgrVNFM : forward the Requestoriginal for a VNF package
	ETSI_Catalog_Mgrvendor CSAR/Zip
end

group VNF PACKAGE TO Ext NFVO
	SDC -> SOL003_AdapterSO : ONAP internal Responsepackage with the aoriginal VNFvendor packageCSAR/Zip
	SOL003_AdapterSO -> VNFM : Response with a VNF package
end
opt
	NFVO ETSI_Catalog_Mgr: store ONAP internal package with the original vendor CSAR/Zip
	ETSI_Catalog_Mgr -> SOL005_Adapter : Requestretrieve forthe aoriginal NSvendor packageCSAR/Zip
	SOL005_Adapter -> ETSIExt_Catalog_MgrNFVO : Requestforward forthe aoriginal NS package
	ETSI_Catalog_Mgr -> SOL005_Adapter : Response with a NS package
	SOL005_Adaptervendor CSAR/Zip
end

group VNF PACKAGE TO VFC 
	SDC -> NFVOVFC : ONAP internal Responsepackage with the aoriginal NSvendor packageCSAR/Zip
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?

...

  • The original vendor package contents between the Adapters and SVNFMs/NFVOs could be one of the following.
    • Vendor package including certificate and signature (Zip format)
    • Vendor package without certificate and signature (CSAR format)
  • Open Issues:
    1. Distribution of vendor VNF packages with certificates and signatures to SVFNM need to be sorted out.
    2. Currently, VF-C supports CSAR-format without certificate or signature – TBD
  • The following diagram depicts the ETSI package distribution. 



  • The following sequence diagram depicts the Package Information Flows.
PlantUML Macro
typedot
@startuml
participant SDC
participant SO
participant ETSI_Catalog_Mgr
participant SOL003_Adapter
participant SOL005_Adapter
participant VNFM
participant VFC
participant Ext_NFVO
autonumber 

group VNF PACKAGE TO SVNFM
	SDC -> SO : ONAP internal package with the \noriginal vendor CSAR/Zip
	SO -> ETSI_Catalog_Mgr: store ONAP internal package \nwith the original vendor CSAR/Zip
	ETSI_Catalog_Mgr -> SOL003_Adapter : retrieve the original vendor CSAR/Zip
	SOL003_Adapter -> VNFM : forward the original vendor CSAR/Zip
end

group VNF PACKAGE TO Ext NFVO
	SDC -> SO : ONAP internal package with the original vendor CSAR/Zip
	SO -> ETSI_Catalog_Mgr: store ONAP internal package with the original vendor CSAR/Zip
	ETSI_Catalog_Mgr -> SOL005_Adapter : retrieve the original vendor CSAR/Zip
	SOL005_Adapter -> Ext_NFVO : forward the original vendor CSAR/Zip
end

group VNF PACKAGE TO VFC 
	SDC -> VFC : ONAP internal package with the original vendor CSAR/Zip
end	
	
@enduml

...