Instantiating VNFs which include VNFCs that are composed of independently manageable software modules
View Patent ↗An example operation may include a method comprising one or more of receiving a VNF instance creation request from a NFVO, retrieving one or more VNFC Module LCM scripts and software loads, reserving one or more NFVI VM/container resources required for a VNF instance, instantiating one or more VNFCIs associated with the VNF instance wherein installation includes at least one or more of deploying the one or more VNFC module LCM scripts and software loads to the one or more reserved NFVI VM/containers, installing the VNFC modules on the one or more VM/containers, and starting the VNFC modules on the one or more VM/containers, sending a VNF instance creation completed notification.
1. A hardware-implemented Virtual Network Function Manager (VNFM) configured to:
in response to a request to instantiate a VNF Instance (VNFI), retrieve, from a VNF catalog, a VNF Descriptor (VNFD), the VNFD comprising one or more VNF Components Instances (VNFCIs), each VNFCI comprising a plurality of independently manageable VNFC software modules;
retrieve, from the VNF catalog, a software image including the plurality of independently manageable VNFC software modules based on a corresponding VNFC module descriptor in the VNFD;
instantiate each VNFCI, wherein, when the VNFM instantiates each VNFCI, the VNFM is for each VNFCI, to:
start a VM/container that includes the software image,
install the plurality of independently manageable VNFCI software modules in the VM/container, and
start the plurality of independently manageable VNFCI software modules in the VM/container; and
send a notification indicating that the VNFI is instantiated.
2. The hardware-implemented VNFM of claim 1 , wherein the request to instantiate the VNFI includes one or more of:
a preferred deployment flavor that defines a size bounded deployment configuration related to capacity; and
a scaling level.
3. The hardware-implemented VNFM of claim 1 , wherein, when the VNFM instantiates the each VNFCI, the VNFM further is to:
retrieve LCM scripts for each of the plurality of independently manageable VNFC software modules; and
store the LCM scripts in a VNFD store.
4. The hardware-implemented VNFM of claim 1 , wherein the software image comprises one or more software loads for each of the plurality of independently manageable VNFC software modules.
5. The hardware-implemented VNFM of claim 1 , wherein, when the VNFM instantiates the each VNFCI, the VNFM further is to:
transfer the one or more software loads to a target VM/container using a Secure File Transport Protocol (SFTP).
6. The hardware-implemented VNFM of claim 1 , wherein, when the VNFM instantiates the each VNFCI, the VNFM further is to:
install the each of the plurality of independently manageable VNFC software modules in the VM/container using a custom VNFC module specific LCM install script.
7. The hardware-implemented VNFM of claim 1 , wherein, when the VNFM starts the plurality of independently manageable VNFCI software modules, the VNFM is to:
sends a request to each of the plurality of independently manageable VNFCI software modules to execute a custom VNFCI module specific LCM start script.
8. A method, comprising to:
receiving, by a Virtual Network Function Manager (VNFM), a request to instantiate a VNF Instance (VNFI);
retrieving, by a Virtual Network Function Manager (VNFM), a VNF Descriptor (VNFD) from a VNF catalog, the VNFD comprising one or more VNF Components Instances (VNFCIs), each VNFCI comprising a plurality of independently manageable VNFC software modules;
retrieving, by the VNFM, a software image from the VNF catalog, the software image including the plurality of independently manageable VNFC software modules based on a corresponding VNFC module descriptor in the VNFD;
instantiating, by the VNFM, each VNFCI, wherein the instantiating each VNFCI comprises for each VNFCI:
starting a VM/container including the software image,
installing the plurality of independently manageable VNFCI software modules in the VM/container,
starting the plurality of independently manageable VNFCI software modules in the VM/container; and
sending, by the VNFM, a notification indicating that that the VNFI is instantiated.
9. The method of claim 8 , wherein the request to instantiate the VNFI includes one or more of:
a preferred deployment flavor that defines a size bounded deployment configuration related to capacity; and
a scaling level.
10. The method of claim 8 , wherein the instantiating the each VNFCI further comprises:
retrieving LCM scripts for each of the plurality of independently manageable VNFC software modules; and
storing the LCM scripts in a VNFD store.
11. The method of claim 8 , wherein the software image comprises one or more software loads for each of the plurality of independently manageable VNFC software modules.
12. The method of claim 8 , wherein the instantiating the each VNFCI further comprises:
transferring the one or more software loads to a target VM/container using a Secure File Transport Protocol (SFTP).
13. The method of claim 8 , wherein the instantiating the each VNFCI further comprises:
installing the each of the plurality of independently manageable VNFC software modules in the VM/container using a custom VNFC module specific LCM install script.
14. The method of claim 8 , wherein the instantiating the each VNFCI further comprises:
sending a request to the each of the plurality of independently manageable VNFCI software modules to execute custom VNFCI module specific LCM start script.
15. A non-transitory computer readable medium storing one or more instructions that when read by a processor of a Virtual Network Function Manager (VNFM) cause the processor to:
in response to a request to instantiate a VNF Instance (VNFI), retrieve, from a VNF catalog, a VNF Descriptor (VNFD), the VNFD comprising one or more VNF Components Instances (VNFCIs), each VNFCI comprising a plurality of independently manageable VNFC software modules;
retrieve, from the VNF catalog, a software image including the plurality of independently manageable VNFC software modules based on a corresponding VNFC module descriptor in the VNFD;
instantiate each VNFCI, wherein, when the processor instantiates each VNFCI, the VNFM is for each VNFCI, to:
start a VM/container including the software image,
install the plurality of independently manageable VNFCI software modules in the VM/container,
start the plurality of independently manageable VNFCI software modules in the VM/container; and
send a notification indicating that the VNFI is instantiated.
16. The non-transitory computer readable medium of claim 15 , wherein the request to instantiate the VNFI includes one or more of:
a preferred deployment flavor that defines a size bounded deployment configuration related to capacity; and
a scaling level.
17. The non-transitory computer readable medium of claim 15 , wherein, when the processor instantiates the each VNFCI, the processor further is to:
retrieve LCM scripts for each of the plurality of independently manageable VNFC software modules; and
store the LCM scripts in a VNFD store.
18. The non-transitory computer readable medium of claim 15 , wherein the software image comprises one or more software loads for each of the plurality of independently manageable VNFC software modules.
19. The non-transitory computer readable medium of claim 15 , wherein, when the processor instantiates the each VNFCI, the processor further is to:
transfer the one or more software load to a target VM/container using a Secure File Transport Protocol (SFTP).
20. The non-transitory computer readable medium of claim 15 , wherein, when the processor instantiates the each VNFCI, the processor further is to:
install the each of the plurality of independently manageable VNFC software modules in the VM/container using a custom VNFC module specific LCM install script.