Method and system for containerized network function management service
A method, a device, and a non-transitory storage medium are described in which a containerized network function (CNF) management service is provided. The service may provide for allocating discrete sets of CNF resources deployed as pods to provide application services to end devices; identifying at least one threshold resource value associated with a first number of the deployed pods which are activated to provide the application services; determining an anticipated nonsatisfaction of the at least one threshold resource value associated with the first number of the deployed pods; and invoking, for a period of time, horizontal pod autoscaling (HPA) via an application programming interface to activate a second number of the deployed pods to provide the application services, wherein the HPA is performed non-incrementally until at least one of the period of time has elapsed or each of the deployed pods has been activated to provide the application services.
1. A method comprising:
allocating, by a network device of an application service layer network, discrete sets of containerized network function (CNF) resources deployed as a plurality of pods to provide application services to end devices;
identifying, by the network device, threshold resource values associated with a first number of the deployed pods which are activated to provide the application services;
determining, by the network device, a first state of anticipated nonsatisfaction of multiple ones of the threshold resource values;
invoking, by the network device responsive to the first state and for a configurable period of time, non-incremental horizontal pod autoscaling (HPA) via an application programming interface (API) to activate a second number of the deployed pods to provide the application services;
determining, by the network device, a second state of anticipated satisfaction of at least one of the multiple threshold resource values; and
invoking, by the network device responsive to the second state, incremental HPA via the API to activate a third number of the deployed pods until each of the plurality of deployed pods has been activated, to provide the application services.
2. The method of claim 1 , wherein the anticipated nonsatisfaction corresponds to an unplanned spike in a demand for the application services, and
wherein the API comprises a Representational State Transfer (REST) API.
3. The method of claim 1 , wherein the anticipated nonsatisfaction corresponds to a planned spike in a demand for the application services, and
wherein the API comprises a graphical user interface.
4. The method of claim 1 , wherein the at least one threshold resource value relates to at least one of a key performance indicator (KPI), a processing capacity usage, or a memory capacity usage associated with the first number of deployed pods.
5. The method of claim 1 , wherein the network device comprises a container orchestration platform.
6. The method of claim 1 , wherein the non-incremental. HPA is invoked for a duration of the configurable period of time.
7. The method of claim 1 , wherein the first number, the second number, and the third number of the deployed pods constitute an entirety of the plurality of deployed pods.
8. A network device of an application service layer network, comprising:
a processor configured to:
allocate discrete sets of containerized network function (CNF) resources deployed as a plurality of pods to provide application services to end devices;
identify threshold resource values associated with a first number of the deployed pods which are activated to provide the application services;
determine a first state of anticipated nonsatisfaction of multiple ones of the threshold resource values;
invoke, responsive to the first state and for a configurable period of time, non-incremental horizontal pod autoscaling (HPA) via an application programming interface (API) to activate a second number of the deployed pods to provide the application services;
determine a second state of anticipated satisfaction of at least one of the multiple threshold resource values; and
invoke, responsive to the second state, incremental HPA via the API to activate a third number of the deployed pods until each of the plurality of deployed pods has been activated, to provide the application services.
9. The network device of claim 8 , wherein the anticipated nonsatisfaction corresponds to an unplanned spike in a demand for the application services, and
wherein the API comprises a Representational State Transfer (REST) API.
10. The network device of claim 8 , wherein the anticipated nonsatisfaction corresponds to a planned spike in a demand for the application services, and
wherein the API comprises a graphical user interface.
11. The network device of claim 8 , wherein the at least one threshold resource value relates to at least one of a key performance indicator (KPI), processing capacity usage, or memory capacity usage associated with the first number of deployed pods.
12. The network device of claim 8 , wherein the network device comprises a container orchestration platform.
13. The network device of claim 8 , wherein the non-incremental HPA is invoked for a duration of the configurable period of time.
14. The network device of claim 8 , wherein the first number, the second number, and the third number of the deployed pods constitute an entirety of the plurality of deployed pods.
15. A non-transitory computer-readable storage medium storing instructions executable by a processor of a network device of an application service layer network, wherein the instructions are configured to:
allocate discrete sets of containerized network function (CNF) resources deployed as a plurality of pods to provide application services to end devices;
identify threshold resource values associated with a first number of the deployed pods which are activated to provide the application services;
determine a first state of anticipated nonsatisfaction of multiple ones of the threshold resource values;
invoke, responsive to the first state and for a configurable period of time, non-incremental horizontal pod autoscaling (HPA) via an application programming interface (API) to activate a second number of the deployed pods to provide the application services;
determine a second state of anticipated satisfaction of at least one of the multiple threshold resource values; and
invoke, responsive to the second state, incremental HPA via the API to activate a third number of the deployed pods until each of the plurality of deployed pods has been activated, to provide the application services.
16. The non-transitory computer-readable storage medium of claim 15 , wherein the anticipated nonsatisfaction corresponds to an unplanned spike in a demand for the application services, and
wherein the API comprises a Representational State Transfer (REST) API.
17. The non-transitory computer-readable storage medium of claim 15 , wherein the anticipated nonsatisfaction corresponds to a planned spike in a demand for the application services, and
wherein the API comprises a graphical user interface.
18. The non-transitory computer-readable storage medium of claim 15 , wherein the at least one threshold resource value relates to at least one of a key performance indicator (KPI), processing capacity usage, or memory capacity usage associated with the first number of deployed pods.
19. The non-transitory computer-readable storage medium of claim 15 , wherein the non-incremental HPA is invoked for a duration of the configurable period of time.
20. The non-transitory computer-readable storage medium of claim 15 , wherein the first number, the second number, and the third number of the deployed pods constitute an entirety of the plurality of deployed pods.