The untouchable NSD & VNFD

[shuaibsiddiqui]

We plan to have Package catalogue, NS catalogue, VNF Catalogue, etc in the SP-Catalogues. Does this imply that a authorized developer can download a package (including PD, NSD & VNFDs, images, etc.) or a NS (including NSD, VNFD, images, etc) or a VNF (including VNFD, image, etc.) ?

The reason I ask this question is, if the answer to above question is YES then the vm_image path in the VNFD has to be edited according to the VNF.zip file to be returned to the requested developer, as we are not going to send back the complete package.zip file that was prepated by the original/author developer. Thus our efforts to keep the VNFD untouched will go in vain anyway.

This occurs because we receive a complete Network Service package, we extract it and store its contents separately and make them available to other developer as separate entities.

[mbredel]

So your question is: Do we allow to download only parts of a package? I haven't thought about it that much before, but I think it would be a nice feature - for the second year :-)

However, I don't think that we need to modify the VNFD for that. I would assume that we generate new descriptors + package (there would be no VNF.zip, but a new .SON-package) for such a download. No?

Maybe another approach could be that we separate the SP from a (public) catalogue that offers these features. They are kind of orthogonal to what the SP has to do. Or?