API Multiplexing of Multiple Pod Requests

1 . A method for organizing and deploying containerized applications within a cloud-network architecture framework, comprising:

receiving a plurality of pod requests;

organizing the plurality of pod requests into one or more batches;

for each of the one or more batches:

determining a resource requirement for each pod request in the plurality of pod requests in the batch;

determining a host availability and a host resource availability of one or more hosts; and

deploying each pod request in the plurality of pod requests in each of the one or more batches to the one of the one or more hosts based on the host availability and the host resource availability.

2 . The method of claim 1 , wherein the resource requirement for each pod request comprises resource requirements for each pod request within the plurality of pod requests, and wherein the resource requirement count for each pod request within the batch comprises a pod request value and a pod limit value for each pod request.

3 . The method of claim 2 , further comprising determining whether a pod request is a critical pod request, wherein the pod request is a critical pod request when the pod request value equals the pod limit value.

4 . The method of claim 3 , further comprising deploying critical pod requests to one of the one or more hosts before other pod requests in the batch.

5 . The method of claim 1 , wherein deploying each pod request is performed according to a user defined algorithm, and wherein the algorithm is a best-fit distribution.

6 . The method of claim 1 , wherein deploying each pod request is performed according to a user defined algorithm, and wherein the algorithm is a first-fit distribution.

7 . The method of claim 1 , wherein determining the host resource availability of the one or more hosts comprises determining whether the host resource availability of the host exceeds the resource requirement count of the pod request.

8 . The method of claim 3 , wherein the critical pod request comprises a user-annotation to indicate when a pod request is a critical pod request.

9 . The method of claim 1 , wherein deploying the pod requests to one of the one or more hosts comprises deploying the pod requests according to a round-robin distribution.

10 . The method of claim 1 , wherein the plurality of pod requests are organized into the batch according to a configuration by a user, and wherein the configuration comprises a number of pod requests or a time period.

11 . The method of claim 1 , wherein the one or more hosts comprise a placement policy, and wherein the placement policy determines whether to deploy each pod request to a same host or to a different host.

12 . The method of claim 11 , wherein the placement policy determines whether to deploy each pod request to a host according to a user-annotation on the pod and a user-annotation on the host, wherein the user-annotation on the pod and the user-annotation on the host must match.

13 . The method of claim 11 , wherein the placement policy determines whether to deploy each pod request to a host according to whether the host is running a service, and wherein the placement policy determines whether to deploy each pod request to the host whether or not the host is running the service.

14 . A system comprising:

a memory; and

a computer-readable storage medium comprising programming instructions thereon that when executed, cause the system to:

receive a plurality of pod requests;

organize the plurality of pod requests into one or more batches;

for each batch:

determine a resource requirement for each pod request in the plurality of pod requests in the batch;

determine a host availability and a host resource availability of one or more hosts; and

deploy each pod request in the plurality of pod requests in each of the one or more batches to the one of the one or more hosts based on the host availability and the host resource availability.

15 . The system of claim 14 , wherein the resource requirement for the batch comprises a resource requirement for each pod request within the plurality of pod requests, and wherein the resource requirement for each pod request within the batch comprises a pod request value and a pod limit value for each pod request.

16 . The system of claim 14 , wherein the programming instructions further cause the system to determine the availability status of the one or more hosts by determining whether the host resource count of the host exceeds the resource requirement count of the pod request.

17 . The system of claim 14 , wherein the one or more hosts comprise a placement policy, and wherein the placement policy determines whether to deploy each pod request to a same host or to a different host.

18 . The system of claim 18 , wherein the placement policy determines whether to deploy each pod request to a host according to a user-annotation on the pod and a user-annotation on the host, wherein the user-annotation on the pod and the user-annotation on the host must match.

19 . The system of claim 18 , wherein the placement policy determines whether to deploy each pod request to a host according to whether the host is running a service, and wherein the placement policy determines whether to deploy each pod request to the host whether or not the host is running the service.

20 . A method comprising:

receiving a plurality of pod requests;

organizing the plurality of pod requests into one or more batches;

for each of the one or more batches:

determining a resource requirement for the batch;

determining a host resource availability for each of the one or more hosts, and

deploying each pod request in the plurality of pod requests in each of the one or more batches to the one of the one or more hosts based on the host availability and according to a distribution algorithm when the resource requirement of the pod request does not exceed the host resource availability of the host.