SOFTWARE APPLICATION PLACEMENT USING COMPUTING RESOURCE CONTAINERS

• US 20170277558A1
• Filed: 06/12/2017
• Published: 09/28/2017
• Est. Priority Date: 10/13/2011
• Status: Active Grant

• Current Assignee: Vmware LLC (Broadcom, Inc.)
• Original Assignee: VMware, Inc. (Broadcom, Inc.)
• Inventors: AHMAD, Ifran, HOLLER, Anne Marie, UYSAL, Mustafa
• Granted Patent: US 10,540,197 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 2009/45595 Network integration; Enabling network access in virtual machine instances
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/5033 considering data affinity
• CPC Class Codes: G06F 9/5077 Logical partitioning of resources; Management or configuration of virtualized resources specific details on emulation or internal functioning of virtual machines G06F9/455
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components

Abstract

Embodiments associate software applications with computing resource containers based on a placement rule and a selected failure correlation. A placement rule indicates that a first software application is to be co-located with a second software application during execution of the first and second software applications. The placement rule also indicates that the first software application is to be separated from the second software application during execution of the first and second software applications. Failure correlations are determined for a plurality of computing resources associated with the first software application. A computing resource with a lowest failure correlation is selected from the plurality of computing resources, and the second software application is associated with the selected computing resource despite the association violating the placement rule.

Claims

1. A system for associating a software application with a computing resource, the system comprising:

a memory for storing a set of placement rules including an anti-affinity placement rule indicating that a first software application is to be separated from a second software application, wherein the first software application is associated with a first computing resource of a plurality of computing resources; and

a processor programmed to;

determine failure correlations between the plurality of computing resources, each of the failure correlations corresponding to a pair of the plurality of the computing resources;

identify a second computing resource, which is different from the first computing resource, from the plurality of computing resources such that the second computing resource has a failure correlation with the first computing resource which is either below a first threshold or the lowest among the plurality of computing resources; and

associate the second computing resource with the second software application.

2. The system of claim 1, wherein determining the failure correlations between the plurality of computing resources is based on one or more of the following:

a failure correlation from a resource manager associated with the plurality of computing resources, a configuration hierarchy indicating hardware associated with the plurality of computing resources, and performance metrics associated with the plurality of computing resources.

3. The system of claim 1, wherein the processor is further programmed to:

determine that associating the second computing resource with the second software application violates a second rule;

based on the determining, select a third computing resource from the plurality of computing resources such that the third computing resource has a failure correlation with the first computing resource which is either below the first threshold or the next lowest among the plurality of computing resources; and

associate the third computing resource, instead of the second computing resource, with the second software application.

4. The system of claim 3, wherein the second rule is one of the following:

an anti-affinity rule, an affinity rule, or a rule governing resource utilization associated with the second computing resource.

5. The system of claim 1, wherein each of the failure correlations are expressed as a value between a minimum value, representing no correlation of failures between a pair of computing resources, and a maximum value, representing a highest possible correlation of failures between a pair of computing resources.

6. The system of claim 1, wherein the processor is further programmed to:

determine performance metrics associated with the plurality of computing resources; and

determine the failure correlations based on the performance metrics.

7. The system of claim 1, wherein the performance metrics comprise one or more of the following:

input/output (I/O) latency, I/O throughput, network latency, and network bandwidth.

8. The system of claim 1, wherein the plurality of computing resources includes a first set of computing resources managed by a first computing resource container, and a second set of computing resources managed by a second computing resource container, wherein the first computing resource is managed by the first computing resource container, wherein the processor is further programmed to:

associate the second software application with the first computing resource container; and

provide the set of placement rules to the first computing resource container for enforcement.

9. The system of claim 8, wherein the processor is programmed to associate the second software application with the first computing resource container, after determining that no computing resource container other than the first computing resource container has sufficient capacity to accommodate the second software application.

10. A method comprising:

receiving a set of placement rules including an anti-affinity placement rule indicating that a first software application is to be separated from a second software application, wherein the first software application is associated with a first computing resource of a plurality of computing resources;

determining failure correlations between the plurality of computing resources, each of the failure correlations corresponding to a pair of the plurality of the computing resources;

identifying a second computing resource, which is different from the first computing resource, from the plurality of computing resources such that the second computing resource has a failure correlation with the first computing resource which is either below a first threshold or the lowest among the plurality of computing resources; and

associating the second computing resource with the second software application.

11. The method of claim 10, wherein determining the failure correlations between the plurality of computing resources is based on one or more of the following:

a failure correlation from a resource manager associated with the plurality of computing resources, a configuration hierarchy indicating hardware associated with the plurality of computing resources, and performance metrics associated with the plurality of computing resources.

12. The method of claim 10, further comprising:

determining that associating the second computing resource with the second software application violates a second rule;

based on the determining, identifying a third computing resource from the plurality of computing resources such that the third computing resource has a failure correlation with the first computing resource which is either below the first threshold or the next lowest among the plurality of computing resources; and

associating the third computing resource, instead of the second computing resource, with the second software application.

13. The method of claim 10, wherein the plurality of computing resources includes a first set of computing resources managed by a first computing resource container, and a second set of computing resources managed by a second computing resource container, wherein the first computing resource is managed by the first computing resource container, the method further comprising:

associating the second software application with the first computing resource container; and

providing the set of placement rules to the first computing resource container for enforcement.

14. The method of claim 13, wherein the process of associating the second software application with the first computing resource container is performed after determining that no computing resource container other than the first computing resource container has sufficient capacity to accommodate the second software application.

15. The method of claim 10, wherein each of the first and second software application includes a virtual machine.

16. A non-transitory computer-readable medium comprising computer-executable instructions that when executed by a processor, cause the processor to perform a method, the method comprising:

receiving a set of placement rules including an anti-affinity placement rule indicating that a first software application is to be separated from a second software application, wherein the first software application is associated with a first computing resource of a plurality of computing resources;

determining failure correlations between the plurality of computing resources, each of the failure correlations corresponding to a pair of the plurality of the computing resources;

identifying a second computing resource, which is different from the first computing resource, from the plurality of computing resources such that the second computing resource has a failure correlation with the first computing resource which is either below a first threshold or the lowest among the plurality of computing resources;

determining whether associating the second computing resource with the second software application violates a second rule;

when determining the second rule is not violated, associating the second computing resource with the second software application; and

when determining the second rule is violated,

identifying a third computing resource from the plurality of computing resources such that the third computing resource has a failure correlation with the first computing resource which is either below the first threshold or the next lowest among the plurality of computing resources;

associating the third computing resource, instead of the second computing resource, with the second software application.

17. The non-transitory computer-readable medium of claim 16, wherein the second rule is one of the following:

an anti-affinity rule, an affinity rule, or a rule governing resource utilization associated with the second computing resource.

18. The non-transitory computer-readable medium of claim 16, wherein the plurality of computing resources includes a first set of computing resources managed by a first computing resource container, and a second set of computing resources managed by a second computing resource container, wherein the first computing resource is managed by the first computing resource container, the method further comprising:

associating the second software application with the first computing resource container; and

providing the set of placement rules to the first computing resource container for enforcement.

19. The non-transitory computer-readable medium of claim 18, wherein the process of associating the second software application with the first computing resource container is performed after determining that no computing resource container other than the first computing resource container has sufficient capacity to accommodate the second software application.

20. The non-transitory computer-readable medium of claim 16, wherein each of the first and second software application includes a virtual machine.