Systems and methods for orchestration of network functions

1. A system comprising:

a centralized orchestration device to:

store a catalog of virtual network function descriptors (VNFDs) in an input language,

generate, based on the catalog of VNFDs, intents for containerized network function (CNF) deployments, and

store the generated intents as blocks in a central intent database, wherein the blocks include an input data model for the CNF services; and

a multi-cluster container management (MCCM) platform including one or more processors to:

receive and store a copy of the intent database,

read design time policies from the copy of the intent database, and

convert the input data model into a vendor-specific output data model in an output language.

2. The system of claim 1 , wherein the one or more processors of the MCCM platform are further to:

provide an intent sensor service, wherein the intent sensor service includes an intent sensor to detect an intent type in the copy of the intent database.

3. The system of claim 2 , wherein the one or more processors of the MCCM platform are further to:

provide an intent actuator service, wherein the intent actuator service includes an intent actuator for executing the intent type.

4. The system of claim 2 , wherein the intent sensor service includes a different intent sensor for each intent type in the copy of the intent database.

5. The system of claim 1 , wherein the MCCM is included within a network function virtualization management and orchestration (NFV-MANO) architectural framework.

6. The system of claim 1 , wherein the input data model includes a network service descriptor (NSD) or a platform configuration descriptor (PCD), and wherein the output data model includes a custom resource definition (CRD) or a custom resource (CR).

7. The system of claim 1 , wherein, when generating the intents for the CNF deployments, the centralized orchestration device is further to:

identify normative keywords from the catalog of VNFDs,

deduce the intents, based on the identifying, and

enter the intents into the central intent database.

8. The system of claim 1 , wherein the MCCM is configured to interface with one or more of a container infrastructure service manager (CISM) or a virtualization infrastructure manager (VIM).

9. The system of claim 1 , wherein the centralized orchestration device includes a VNF orchestrator (VNFO).

10. A method comprising:

storing, by a centralized orchestration device, a catalog of virtual network function descriptors (VNFDs);

generating, by the centralized orchestration device and based on the catalog of VNFDs, intents for containerized network function (CNF) services;

storing, by the centralized orchestration device, the generated intents as blocks in a central intent database, wherein the blocks include an input data model for the CNF services;

receiving, by a multi-cluster container management (MCCM) instance, a copy of the intent database;

reading, by the MCCM instance, design time policies from the copy of the intent database; and

converting, by the MCCM instance, the input data model into a vendor-specific output data model in an output language.

11. The method of claim 10 , further comprising:

detecting, by the MCCM instance, each intent type in the copy of the intent database.

12. The method of claim 11 , further comprising:

generating, after the detecting, a custom resource definition (CRD) or a custom resource (CR).

13. The method of claim 10 , wherein the input data model includes an application descriptor or a cloud deployment descriptor.

14. The method of claim 10 , wherein the input data model includes a network service descriptor (NSD) or a platform configuration descriptor (PCD).

15. The method of claim 10 , wherein converting the input data model into the vendor-specific output data model includes:

generating a custom resource definition (CRD) or a custom resource (CR) in a language that is different than the input language.

16. The method of claim 10 , further comprising:

sending the vendor-specific output data model to a container infrastructure service manager (CISM) or a virtualization infrastructure manager (VIM).

17. A non-transitory, computer-readable storage medium storing instructions executable by a processor of a network device, which when executed cause the network device to:

receive, from a centralized orchestration device, a copy of a central intent database, wherein the central intent database includes blocks of generated intents for an input data model in an input language;

read design time policies from the copy of the central intent database; and

convert the input data model into a vendor-specific output data model in an output language.

18. The non-transitory, computer-readable medium of claim 17 , further storing instructions, which when executed cause the network device to:

detect each intent type in the copy of the central intent database.

19. The non-transitory, computer-readable storage medium of claim 17 , wherein the instructions to convert the input data model, when executed further cause the network device to:

convert the input data model to a custom resource definition (CRD) or a custom resource (CR).

20. The non-transitory, computer-readable storage medium of claim 19 ,

send the vendor-specific output data model to a container infrastructure service manager (CISM) or a virtualization infrastructure manager (VIM).