ETSI's Bug Tracker - SOL003 - Or-Vnfm protocols spec
View Issue Details
0007811SOL003 - Or-Vnfm protocols spec[NFV Specifications] Feature Gappublic15-10-2018 10:3821-02-2019 10:39
Bruno Chatras 
Uwe Rauschenbach 
normalminorhave not tried
0007811: Relation between vnfdId and vnfPkgId
The correlation between the 2 identifiers vnfId and vnfPkgId is maintained by the NFVO. Upon request of vnf Instance Id creation the VNFM needs to query the NFVO to retrieve the vnfPgkId.
It was suggested to allow/recommend the NFVO to add this information in the createVnfInstanceReq
No tags attached.
Issue History
15-10-2018 10:38Bruno ChatrasNew Issue
15-10-2018 10:40Bruno ChatrasSummaryRelation be tween vnfdId and vnfPkgId => Relation between vnfdId and vnfPkgId
21-02-2019 10:39Uwe RauschenbachNote Added: 0015334
21-02-2019 10:39Uwe RauschenbachAssigned To => Uwe Rauschenbach
21-02-2019 10:39Uwe RauschenbachStatusnew => resolved
21-02-2019 10:39Uwe RauschenbachResolutionopen => fixed
21-02-2019 10:39Uwe RauschenbachFixed in Version => 2.5.5
21-02-2019 10:39Uwe RauschenbachTarget Version => 2.5.5

Uwe Rauschenbach   
21-02-2019 10:39   
This bug has been resolved by dropping the vnfPkgId from the LCM interface. In the LCM interface, a VNF Package is now consisntently identified by the vnfdId. The vnfPkgId is retained in the VNF Package Management interface.