Resource allocation brokering in nested containers

• US 8,181,182 B1
• Filed: 11/16/2004
• Issued: 05/15/2012
• Est. Priority Date: 11/16/2004
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Oracle America, Inc. (Oracle Corporation)
• Inventors: Martin, Jean-Christophe
• Primary Examiner(s): To, Jennifer
• Assistant Examiner(s): Kawsar, Abdullah Al
• Application Number:
  US10/990,741
• Time in Patent Office: 2,737 Days
• Field of Search: 718/1, 718/100, 718/101, 718/102, 718/103, 718/104, 718/105, 719/311, 719/312, 719/313, 719/314, 719/315, 719/318, 709/201, 709/203, 709/206, 709/207, 709/215, 709/220, 709/221, 709/226
• US Class Current: 718/104
• CPC Class Codes: G06F 9/485 Task life-cycle, e.g. stopping, restarting, resuming execution G06F9/4881 takes precedence

Abstract

In accordance with one embodiment of the present invention, there is provided a technique for resource allocation brokering in nested containers. According to one aspect, a broker mechanism is established within a first container. A second container also is established within the first container. The second container has a client mechanism. The first container'"'"'s broker mechanism communicates with the second container'"'"'s client mechanism to provide notices to the second container'"'"'s client mechanism. The second container also has a broker mechanism that may or may not be a part of the second container'"'"'s client mechanism. A third container is established within the second container. The third container also has a client mechanism. The second container'"'"'s broker mechanism communicates with the third container'"'"'s client mechanism to provide notices to the third container'"'"'s client mechanism. Thus, communications are facilitated between higher-level containers and lower-level containers in a hierarchy of nested containers.

Claims

1. A machine-implemented method comprising:

sending, from a first broker process executing within a first container to a first client process executing within a second container, a first notice that a first plurality of computing resources will be removed,

wherein the first container is a virtual machine associated with the first plurality of computing resources,

wherein the second container is an operating system (OS) associated with a second plurality of computing resources,

wherein the first plurality of computing resources comprises the second plurality of computing resources, and

wherein the second container is within the first container;

instructing, by the first client process in response to receiving the first notice, a second broker process executing within the second container, to send a second notice to a second client process executing within a third container, wherein the second notice comprises the first notice; and

sending, from the second broker process in response to the instructing, the second notice to the second client process,

wherein the third container is a project associated with a third plurality of computing resources,

wherein the second plurality of computing resources comprises the third plurality of computing resources, and

wherein the third container is within the second container; and

invoking, by the second client process in response to receiving the second notice, a graceful termination mechanism of the third container,

wherein the first notice instructs the first client process that the first broker process has deallocated, from the second container, one or more of the second plurality of computing resources, and

wherein the first broker process provides the first notice to the first client process in response to the first broker process detecting that the first plurality of computing resources will be removed.

2. The method of claim 1, wherein the second notice instructs the second client process that the second broker process has deallocated, from the third container, one or more of the third plurality of computing resources.

3. The method of claim 1, wherein the first notice instructs the first client process to release, from the second container, one or more of the second plurality of computing resources.

4. The method of claim 1, wherein the second notice instructs the first client process that the first container is going to be removed.

5. The method of claim 1, wherein the second notice is provided to the second client process in response to the first client process receiving the first notice, and wherein the second notice instructs the second client process that the first container is going to be removed.

6. The method of claim 1, wherein the OS is executing within the virtual machine.

7. The method of claim 1, wherein the project is executing within the OS.

8. The method of claim 1, wherein the first notice instructs the OS to invoke a graceful termination mechanism.

9. A non-transitory computer-storage medium storing one or more sequences of instructions, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of:

sending, from a first broker process executing within a first container to a first client process executing within a second container, a first notice that a first plurality of computing resources will be removed,

wherein the first container is a virtual machine associated with the first plurality of computing resources,

wherein the second container is an operating system (OS) associated with a second plurality of computing resources,

wherein the first plurality of computing resources comprises the second plurality of computing resources, and

wherein the second container is within the first container;

instructing, by the first client process in response to receiving the first notice, a second broker process executing within the second container, to send a second notice to a second client process executing within a third container, wherein the second notice comprises the first notice; and

sending, from the second broker process in response to the instructing, the second notice to the second client process,

wherein the third container is a project associated with a third plurality of computing resources,

wherein the second plurality of computing resources comprises the third plurality of computing resources, and

wherein the third container is within the second container; and

invoking, by the second client process in response to receiving the second notice, a graceful termination mechanism of the third container,

wherein the first notice instructs the first client process that the first broker process has deallocated, to the second container, one or more of the second plurality of computing resources, and

wherein the first broker process provides the first notice to the first client process in response to the first broker process detecting that the first plurality of computing resources will be removed.

10. The non-transitory computer-readable medium of claim 9 wherein the second notice instructs the second client process that the second broker process has deallocated, from the third container, one or more of the third plurality of computing resources.

11. The non-transitory computer-readable medium of claim 9, wherein the first notice instructs the first client process to release, from the second container, one or more of the second plurality of computing resources.

12. The non-transitory computer-readable medium of claim 9, wherein the first notice instructs the first client process that the first container is going to be removed.

13. The non-transitory computer-readable medium of claim 9, wherein the second notice is provided to the second client process in response to the first client process receiving the first notice, and wherein the second notice instructs the second client process that the first container is going to be removed.

14. The non-transitory computer-readable medium of claim 9, wherein the OS is executing within the virtual machine.

15. The non-transitory computer-readable medium of claim 9, wherein the project is executing within the OS.

16. The non-transitory computer-readable medium of claim 9, wherein the first notice instructs the OS to invoke a graceful termination mechanism.

17. An apparatus comprising:

a processor;

a first container comprising a first broker process executing within the first container, wherein the first container is a virtual machine associated with a first plurality of computing resources;

a second container within the first container, comprising;

a first client process executing within the second container, wherein the first broker process communicates with the first client process to provide a first notice to the first client process that the first plurality of computing resources will be removed, and

a second broker process executing within the second container,

wherein the first client process is configured to instruct the second broker process to send a second notice to a second client process, wherein the second notice comprises the first notice,

wherein the second container is an operating system (OS) associated with a second plurality of computing resources; and

a third container within the second container comprising;

the second client process executing within the third container, wherein the second broker process communicates with the second client process to provide the second notice to the second client process,

wherein the third container is a project associated with a third plurality of computing resources,

wherein the first plurality of computing resources comprises the second plurality of computing resources, wherein the second plurality of computing resources comprises the third plurality of computing resources, and wherein the third container is executing on the processor,

wherein in response to receiving the second notice, the second client process invokes a graceful termination mechanism of the third container,

wherein the first notice instructs the first client process that the first broker process has deallocated, from the second container, one or more of the second plurality of computing resources, and

wherein the first broker process provides the first notice to the first client process in response to the first broker process detecting that the first plurality of computing resources will be removed.

18. The apparatus of claim 17, wherein the second notice instructs the second client process that the second broker process has deallocated, from the third container, one or more of the third plurality of computing resources.

19. The apparatus of claim 17, wherein the first notice instructs the first client process to release, from the second container, one or more of the second plurality of computing resources.

20. The apparatus of claim 17, wherein the second notice instructs the first client process that the first container is going to be removed.

21. The apparatus of claim 17, wherein the second notice is provided to the second client process in response to the first client process receiving the first notice, and wherein the second notice instructs the second client process that the first container is going to be removed.

22. The apparatus of claim 17, wherein the OS is executing within the virtual machine.

23. The apparatus of claim 17, wherein the project is executing within the OS.

24. The apparatus of claim 17, wherein the first notice instructs the OS to invoke a graceful termination mechanism.