Onboarding VNFs which include VNFCs that are composed of independently manageable software modules
An example operation may include a method comprising one or more of constructing a VNF package that includes at least one of a VNFD with one or more VNFC module descriptors or one or more VNFC module artifacts, generating a VNF package archive, receiving the VNF package archive containing the VNF package, processing a manifest file in the VNF package archive, onboarding one or more traditional VNF package components including a VNFD file and at least one software artifact, onboarding one or more independently manageable VNFC software module components in the VNF package, and enabling a VNF in a service catalog.
1. A system for on-boarding a Virtual Network Function (VNF) comprising a Virtual Network Function Component (VNFC), the apparatus comprising:
a hardware-implemented network function virtualization management and orchestration (NFV MANO) module configured to:
receive an archive, containing contents of a VNF package including a VNF Descriptor (VNFD) file containing a plurality of VNFC module descriptors, each VNFC module descriptor corresponding to one of a plurality of independently manageable VNFC modules;
onboard the VNFD file to a VNF catalog of the NFV MANO; and
onboard the plurality of independently manageable VNFC modules to the VNF catalog after the on-boarding of the VNFD file; and
enable the VNF in a service catalog of the NFV MANO;
wherein VNFC module artifacts contained in the archive comprise:
a VNF specific lifecycle management (LCM) script;
a VNFC module specific lifecycle management script;
binary software images for each VNFC module of the plurality of independently manageable VNFC modules; and
a VNFC module software load.
2. The system of claim 1 , wherein the NFV MANO further configured to:
process a signing certificate located in the archive based on the identifying a manifest file.
3. The system of claim 1 , wherein the NFV MANO further configured to:
store the VNFD file and the VNFC software element artifacts in the service catalog.
4. The system of claim 1 , wherein the archive further includes:
a VNFC directory that contains a separate directory for each VNFC of the plurality of independently manageable VNFCs.
5. The system of claim 1 , wherein the NFV MANO is further configured to:
store the VNFD file in a remote database; and
add a reference to the remote database to the VNF catalog.
6. The system of claim 1 , wherein, when the NFV MANO enables the VNF, the NFV MANO is further configured to:
automatically enable the VNF in the service catalog based on a completion of the on-boarding process.
7. A method for on-boarding a Virtual Network Function (VNF) comprising a Virtual Network Function Component (VNFC), the method comprising:
receiving, by a hardware-implemented network function virtualization management and orchestration (NFV MANO) module, an archive, containing contents of a VNF package including a VNF Descriptor (VNFD) file containing a plurality of VNFC module descriptors, each VNFC module descriptor corresponding to one of a plurality of independently manageable VNFC modules;
onboarding, by the NFV MANO, the VNFD file to a VNF catalog of the NFV MANO;
onboarding, by the NFV MANO, the plurality of independently manageable VNFC modules to the VNF catalog after the on-boarding of the VNFD file; and
enabling, by the NFV MANO, the VNF in a service catalog of the NFV MANO;
wherein VNFC module artifacts contained in the archive comprise:
a VNF specific lifecycle management (LCM) script;
a VNFC module specific lifecycle management script;
binary software images for each VNFC module of the plurality of independently manageable VNFC modules; and
a VNFC module software load.
8. The method of claim 7 , further comprising:
processing, by the NFV MANO, a signing certificate located in the archive based on the identifying a manifest file.
9. The method of claim 7 , further comprising:
storing, by the NFV MANO, the VNFD file and the VNFC software element artifacts in the service catalog.
10. The method of claim 7 , wherein the VNF archive further includes:
a VNFC directory that contains a separate directory for each VNFC of the plurality of independently manageable VNFCs.
11. The method of claim 7 , further comprising:
storing, by the NFV MANO, the VNFD file in a remote database; and
adding, by the NFV MANO, a reference to the remote database to the.
12. The method of claim 7 , wherein, when the NFV MANO enables the VNF, the NFV MANO is further configured to:
automatically enable the VNF in the service catalog based on a completion of the on-boarding process.
13. A non-transitory computer readable medium storing instructions for on-boarding Virtual Network Function (VNF) comprising a Virtual Network Function Component (VNFC) that when read by a processor of a hardware-implemented server executing network function virtualization management and orchestration (NFV MANO) module cause the processor to:
receiving an archive containing contents of a VNF package including a VNF Descriptor (VNFD) file containing a plurality of VNFC module descriptors, each VNFC module descriptor corresponding to one of a plurality of independently manageable VNFC modules;
onboarding the VNFD file to a VNF catalog of the NFV MANO;
onboarding the plurality of independently manageable VNFC modules to the VNF catalog after the on-boarding of the VNFD file; and
enabling the VNF in a service catalog of the NFV MANO;
wherein VNFC module artifacts contained in the archive comprise:
a VNF specific lifecycle management (LCM) script;
a VNFC module specific lifecycle management script;
binary software images for each VNFC module of the plurality of independently manageable VNFC modules; and
a VNFC module software load.
14. The non-transitory computer readable medium of claim 13 , wherein the instructions further cause the processor to perform:
processing a signing certificate located in the archive based on the identifying a manifest file.
15. The non-transitory computer readable medium of claim 13 , wherein the instructions further cause the processor to perform:
storing the VNFD file and the VNFC software element artifacts in the service catalog VNF package archive is in the Cloud Service Archive (CSAR) format.
16. The non-transitory computer readable medium of claim 13 , wherein the archive further includes:
a VNFC directory that contains a separate directory for each VNFC of the plurality of independently manageable VNFCs.
17. The non-transitory computer readable medium of claim 13 , wherein the instructions further cause the processor to perform:
storing the VNFD file in a remote database; and
adding a reference to the remote database to the.