Coordinated container scheduling for improved resource allocation in virtual computing environment

1. A method for allocating resources in a computing system, comprising:

receiving, by one or more processors, a first scheduling request to initiate a first container on a first virtual machine having a set of resources;

allocating, by the one or more processors, a first amount of resources from the set of resources to the first container on the first virtual machine in response to the first scheduling request;

notifying, by the one or more processors, a hypervisor in a host of the first amount of resources allocated to the first container;

allocating, by the one or more processors, a second amount of resources from the set of resources to a second virtual machine in the host;

determining, by the one or more processors, if a full amount of the set of the resources on the host is consumed or an unused amount of resources is available in the set of resources on the host, wherein the unused amount of resources is monitored in real time by a container scheduler;

in response to the unused amount of resources being available in the set of resources on the host, notifying the hypervisor in real time by a container scheduler about the unused amount of resources of the set of resources available on the first virtual machine, wherein the unused amount of resources is dynamically rearranged or allocated by the hypervisor; and

in response to the full amount of the set of the resources on the host being consumed, notifying, by the one or more processors, the container scheduler when the full amount of the set of resources on the host is consumed.

2. The method of claim 1 , further comprising:

receiving, by the one or more processors, a second scheduling request to initiate a second container on the first virtual machine; and

allocating, by the one or more processors, a third amount of resources from the set of resources to the second container on the first virtual machine in response to the second scheduling request.

3. The method of claim 2 , further comprising:

notifying, by the one or more processors, the hypervisor of the third amount of resources from the set of resources allocated to the second container; and

allocating, by the one or more processors, a fourth amount of resources from the set of resources to a third virtual machine in the host.

4. The method of claim 1 , wherein the first virtual machine is a virtual machine registered with a container scheduling system.

5. The method of claim 1 , wherein the container scheduler and the hypervisor are both controlled by a cloud service provider.

6. The method of claim 1 , wherein receiving the first scheduling request further comprises:

assigning, by the one or more processors, an upper bound of the set of resources on the first virtual machine; and

notifying, by the one or more processors, the hypervisor about the upper bound of the set of resources on the first virtual machine.

7. The method of claim 1 , wherein notifying the first virtual machine or the container scheduler about the unused amount of resources further comprises:

notifying the first virtual machine or the container scheduler by the hypervisor about the unused amount of resources.

8. The method of claim 1 , wherein allocating the first amount of resources further comprises:

utilizing a balloon driver to allocate the resources.

9. The method of claim 1 , wherein receiving the first scheduling request for scheduling the first container further comprises:

checking, by the one or more processors, workload consumed in the first container; and

maintaining, by the one or more processors, the workload below the first amount of resources as requested.

10. The method of claim 1 , wherein the container scheduler and the hypervisor are configured to communicate bidirectionally.

11. The method of claim 1 , wherein the first container is initiated in a pod deployed in the first virtual machine.

12. A computing system for allocating resources, comprising:

one or more processors configured to:

receive a first scheduling request to initiate a first container on a first virtual machine having a set of resources;

allocate a first amount of resources from the set of resources to the first container on the first virtual machine in response to the first scheduling request;

notify a hypervisor in a host of the first amount of resources allocated to the first container;

allocate a second amount of resources from the set of resources to a second virtual machine in the host;

determine if a full amount of the set of the resources on the host is consumed or an unused amount of resources is available in the set of resources on the host, wherein the unused amount of resources is monitored in real time by a container scheduler;

in response to the unused amount of resources being available in the set of resource on the host, notify the hypervisor in real time by the container scheduler about the unused amount of resources of the set of resources available on the first virtual machine, wherein the unused amount of resources is dynamically rearranged or allocated by the hypervisor; and

in response to the full amount of the set of the resources on the host being consumed, notify the container scheduler by the hypervisor when the full amount of the set of resources on the host is consumed.

13. The computing system of claim 12 , wherein the one or more processors are further configured to:

receive a second scheduling request to initiate a second container on the first virtual machine; and

allocate a third amount of resources from the set of resources to the second container on the first virtual machine in response to the second scheduling request.

14. The computing system of claim 13 , wherein the one or more processors are further configured to:

notify the hypervisor of the third amount of resources from the set of resources allocated to the second container; and

allocate a fourth amount of resources from the set of resources to a third virtual machine in the host.

15. The computing system of claim 12 , wherein the container scheduler and the hypervisor are both controlled by a cloud service provider.