Closed shuaibsiddiqui closed 7 years ago
The package has various components (see https://github.com/sonata-nfv/son-schema/tree/master/package-descriptor). For the descriptors, such as VNFD, NSD, and SSM/FSM-D, I think your approach is fine. The images, for example, should be moved to the VIM image repository, say OpenStack Glance. Similar is true for the SSM/FSM images/containers.
Storing the ZIP-file as such also requires some naming e.g. for versioning. I proposed a naming schema for the package descriptor based in GroupID, Name, and version, very similar to Java Maven (https://maven.apache.org/guides/mini/guide-naming-conventions.html). We could use the same schema to rename and store the ZIP-files.
Just resurrecting the topic to conclude :)
That is what I had in mind, more or less.
@shuaibsiddiqui @mbredel can this be closed?
As we are storing the whole package file in SP-Catalogues anyway so this discussion does not make anymore sense. However, we are not storing image files associated with the VNFs in the Catalogues and a proper solution for that has to be devised for Y2.
Yes, we can close this issue :)
How the validated Package (.zip) will be stored by the SP-Catalogue. Initial Thoughts: Once the GK, after validation, sends the package descriptor, along with the extracted respective NSD and VNFDs, it will store it ... and similarly it will store the package (.zip) like it would do for an image for an VNF .. the mongoDB will have a URI pointing to the .zip file of a stored package descriptor ..