Lifecycle management of VNFC software modules

1. A system, comprising:

a Virtual Network Function Manager (VNFM) configured to perform:

receive a Virtual Network Function Component (VNFC) module Lifecycle Management (LCM) request where the LCM request specifies a VNFC instance (VNFCI), an identity of an independently manageable VNFC module within the VFNCI, and an LCM operation to be performed on the independently manageable VNFC module of the VFNCI;

retrieve a VNFCI data entry;

determine a target Operating System (OS) installation of the VNFCI;

establish a secure connection to a target OS on a VNFCI hosting VM/container;

determine a default command for the LCM operation;

adapt the default command to the target OS;

execute the adapted command on the identified independently manageable VFNC module;

normalize a response code; and

send a response to the VNFC module LCM request.

2. The system of claim 1 , wherein the VNFCI data entry is retrieved from a VNFI data store.

3. The system of claim 1 , wherein the VNFCI data entry includes an OS version that runs in a container/VM hosting the VNFCI.

4. The system of claim 1 , wherein the establish a secure connection includes dynamically set up a new secure connection or the reuse of a secure connection to the target OS that runs on the VNFCI hosting VM/container.

5. The system of claim 1 , wherein the execute of the adapted command includes a start of a response timer, wherein the length of the response timer is based on at least one of an LCM request parameter, a configured value, and a default value.

6. The system of claim 1 , wherein the response includes at least one of an original, non-normalized result, and a normalized response code.

7. The system of claim 1 , wherein the response includes an initial state of the target independently manageable VNFC module after the execution of the adapted command.

8. A method, comprising:

receiving a Virtual Network Function Component (VNFC) module Lifecycle Management (LCM) request where the LCM request specifies a VNFC instance (VNFCI), an identity of an independently manageable VNFC module within the VFNCI, and an LCM operation to be performed on the independently manageable VNFC module of the VFNCI;

retrieving a VNFCI data entry;

determining a target Operating System (OS) installation of the VNFCI;

establishing a secure connection to a target OS on a VNFCI hosting VM/container;

determining a default command for the LCM operation;

adapting the default command to the target OS;

executing the adapted command on the identified independently manageable VFNC module;

normalizing a response code; and

sending a response to the VNFC module LCM request.

9. The method of claim 8 , wherein the VNFCI data entry is retrieved from a VNFI data store.

10. The method of claim 8 , wherein the VNFCI data entry includes an OS version running in a container/VM hosting the VNFCI.

11. The method of claim 8 , wherein establishing a secure connection includes dynamically setting up a new secure connection or re-using an existing secure connection to the target OS running on the VNFCI hosting VM/container.

12. The method of claim 8 , wherein executing the adapted command includes starting a response timer, wherein the length of the response timer is based on at least one of an LCM request parameter, a configured value, and a default value.

13. The method of claim 8 , wherein the response includes at least one of an original, non-normalized result, and a normalized response code.

14. The method of claim 8 , wherein the response includes an initial state of the target VNFC module after executing the adapted command.

15. A non-transitory computer readable medium comprising instructions, that when read by a processor, cause the processor to perform:

receiving a Virtual Network Function Component (VNFC) module Lifecycle Management (LCM) request where the LCM request specifies a VNFC instance (VNFCI), an identity of an independently manageable VNFC module within the VFNCI, and an LCM operation to be performed on the independently manageable VNFC module of the VFNCI;

retrieving a VNFCI data entry;

determining a target Operating System (OS) installation of the VNFCI;

establishing a secure connection to a target OS on a VNFCI hosting VM/container;

determining a default command for the LCM operation;

adapting the default command to the target OS;

executing the adapted command on the identified independently manageable VFNC module;

normalizing a response code; and

sending a response to the VNFC module LCM request.

16. The non-transitory computer readable medium of claim 15 , wherein the VNFCI data entry is retrieved from a VNFI data store.

17. The non-transitory computer readable medium of claim 15 , wherein the VNFCI data entry includes an OS version running in a container/VM hosting the VNFCI.

18. The non-transitory computer readable medium of claim 15 , wherein establishing a secure connection includes dynamically setting up a new secure connection or re-using an existing secure connection to the target OS running on the VNFCI hosting VM/container.

19. The non-transitory computer readable medium of claim 15 , wherein executing the adapted command includes starting a response timer, wherein the length of the response timer is based on at least one of an LCM request parameter, a configured value, and a default value.

20. The non-transitory computer readable medium of claim 15 , wherein the response includes at least one of an original, non-normalized result, and a normalized response code.