Monitoring VNFCs that are composed of independently manageable software modules

1. A system, comprising:

a Virtual Network Function Manager (VNFM) in communication with a management element and a Virtual Network Function Component (VNFC) comprising a plurality of independently manageable VNFC modules, the VNFM being configured to:

determine a specific target operating system (OS) installation of a VNFC instance (VNFCI) based on a VNFCI data entry from a VNFI data store;

retrieve a list of two or more independently manageable VNFC modules of the VNFCI;

determine a status of each of the two or more independently manageable VNFC modules, wherein, when determining the statuses, the VNFM is configured to, for each corresponding VNFC module of the two or more independently manageable VNFC modules:

adapt a default status command, based on the determined status of a corresponding VNFC module of the two or more independently manageable VNFC modules, to the specific target OS installation,

send, to the VNFCI, a request to execute the adapted status command; and

receive, from the VNFCI, a status result; and

send, to the management element, a VNFC module status notification, including a normalized status result for each of the two or more independently associated manageable VNFC modules, where each normalized status result is based on a corresponding status result.

2. The system of claim 1 , wherein when the VNFM is configured to determine a status of each of the two or more independently manageable VNFC modules, the VNFM is further to:

sequentially determine a status of each remaining independently manageable VNFC module of the two or more independently manageable VNFC modules.

3. The system of claim 1 , wherein the VNFCI data entry includes an OS version installed in a Virtual Machine (VM)/container that hosts the VNFCI.

4. The system of claim 1 , wherein the VNFCI data entry includes the list.

5. The system of claim 1 , wherein, when the VNFM is configured to adapt the default status command to the specific target OS installation, the VNFM is further configured to:

adapt the default status command to match a system management framework of the specific target OS installation.

6. The system of claim 1 , wherein, when the VNFM is configured to request to execute the adapted status command, the VNFM is further configured to:

request a secure connection between the VNFM and the OS on a virtual machine (VM)/container that hosts the VNFCI.

7. The system of claim 1 , wherein the secure connection is maintained for a certain time period.

8. A method performed by a Virtual Network Function Manager (VNFM) in communication with a management element and a Virtual Network Function Component (VNFC) comprising a plurality of independently manageable VNFC modules, the method comprising:

determining a specific target operating system (OS) installation of a VNFC instance (VNFCI) based on a VNFCI data entry from a VNFI data store;

retrieving a list of two or more independently manageable VNFC modules of the VNFCI;

determining a status of each of the two or more independently manageable VNFC modules, wherein, when determining the statuses, the method further comprises, for each corresponding VNFC module of the two or more independently manageable VNFC modules:

adapting a default status command, based on the determined status of a corresponding VNFC module of the two or more independently manageable VNFC modules, to the specific target OS installation,

sending, to the VNFCI, a request for execution of the adapted status command;

receiving, from the VNFCI, a status result; and

sending, to the management element, a VNFC module status notification, including a normalized status result for each of the two or more independently associated manageable VNFC modules, where each normalized status result is based on a corresponding status result.

9. The method of claim 8 , wherein the determining a status of each of the two or more independently manageable VNFC modules further comprises:

sequentially determining a status of each remaining independently manageable VNFC module of the two or more independently manageable VNFC modules.

10. The method of claim 8 , wherein the VNFCI data entry includes an OS version installed in a Virtual Machine (VM)/container that hosts the VNFCI.

11. The method of claim 8 , wherein the VNFCI data entry includes the list.

12. The method of claim 8 , wherein the adapting the default status command to the specific target OS installation further comprises:

adapting the default status command to match a system management framework of the specific target OS installation.

13. The method of claim 8 , wherein the executing the adapted status command further comprises:

requesting a secure connection between the VNFM and the OS on a virtual machine (VM)/container that hosts the VNFCI.

14. The method of claim 8 , wherein the secure connection is maintained for a certain time period.

15. A non-transitory computer readable medium storing one or more instructions that when read by a processor cause the processor to perform:

receiving, by a Virtual Network Function Manager (VNFM) in communication with a management element and a Virtual Network Function Component VNFC) comprising a plurality of independently manageable VNFC modules;

determining, by the VNFM, a specific target operating system (OS) installation of a VNFC instance (VNFCI) based on a VNFCI data entry from a VNFI data store;

retrieving, by the VNFM, a list of two or more independently manageable VNFC modules of the VNFCI;

determining, by the VNFM, a status of each of the two or more independently manageable VNFC modules, wherein, when determining the statuses, the one or more instructions further cause the processor to perform, for each corresponding VNFC module of the two or more independently manageable VNFC modules:

adapting a default status command, based on the determined status of a corresponding VNFC module of the two or more independently manageable VNFC modules, to the specific target OS installation,

sending, to the VNFCI, a request for execution of the adapted status command, and

receiving, from the VNFCI, a status result; and

sending, to the management element, a VNFC module status notification, including a normalized status result for each of the two or more independently associated manageable VNFC modules, where each normalized status result is based on a corresponding status result.

16. The non-transitory computer readable medium of claim 15 , wherein the determining a status of each of the two or more independently manageable VNFC modules further comprises:

sequentially determining a status of each remaining independently manageable VNFC module of the two or more independently manageable VNFC modules.

17. The non-transitory computer readable medium of claim 15 , wherein the VNFCI data entry includes an OS version installed in a Virtual Machine (VM)/container that hosts the VNFCI.

18. The non-transitory computer readable medium of claim 15 , wherein the VNFCI data entry includes the list.

19. The non-transitory computer readable medium of claim 15 , wherein, when the one or more instructions cause the processor to perform the adapting the default status command to the specific target OS installation, the one or more instructions further cause the processor to perform:

adapting the default status command to match a system management framework of the specific target OS installation.

20. The non-transitory computer readable medium of claim 15 , wherein, when the one or more instructions cause the processor to perform the executing of the adapted status command, the one or more instructions further cause the processor to perform:

requesting a secure connection between the VNFM and the OS on a virtual machine (VM)/container that hosts the VNFCI.