RESOURCE ALLOCATION STATE MANAGEMENT

• US 20190317811A1
• Filed: 04/17/2018
• Published: 10/17/2019
• Est. Priority Date: 04/17/2018
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Mani, Ajay, Greeff, Esaias E., Dion, David A., Joshi, Shailesh P.
• Granted Patent: US 10,733,020 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 2009/45595 Network integration; Enabling network access in virtual machine instances
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/5005 to service a request
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• 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

Abstract

According to examples, an apparatus may include a processor and a memory on which is stored machine readable instructions that are to cause the processor to receive an allocation request from an allocator client, determine a resource allocation for the received job allocation request, store a record of the determined resource allocation in a records store, and send the determined resource allocation to the allocator client, in which an acknowledgement to the sent determined resource allocation is to be received from the allocator client. The instructions may also cause the processor to manage a state of the determined resource allocation using the record stored in the records store based on whether the acknowledgement is received from the allocator client.

Claims

1. An apparatus comprising:

a processor; and

a memory on which is stored machine readable instructions that are to cause the processor to;

receive an allocation request from an allocator client;

determine a resource allocation for the received job allocation request;

store a record of the determined resource allocation in a records store;

send the determined resource allocation to the allocator client, wherein an acknowledgement to the sent determined resource allocation is to be received from the allocator client; and

manage a state of the determined resource allocation using the record stored in the records store based on whether the acknowledgement is received from the allocator client.

2. The apparatus of claim 1, wherein the instructions are further to cause the processor to:

determine whether the acknowledgement is received from the allocator client; and

based on a determination that the acknowledgement is received, identify whether the determined resource allocation was successful or was unsuccessful from the received acknowledgement.

3. The apparatus of claim 2, wherein the instructions are further to cause the processor to:

based on an identification that the determined resource allocation was successful, delete the record in the records store.

4. The apparatus of claim 3, wherein to manage the state of the determined resource allocation, the instructions are further to cause the processor to:

determine that the acknowledgement was not received from the allocator client;

undo, using the record of the determined resource allocation stored in the records store, the determined resource allocation for the allocator client based on a determination that the acknowledgement was not received; and

commit results pertaining to the determined resource allocation for the allocator client being undone in a placement store.

5. The apparatus of claim 3, wherein to manage the state of the determined resource allocation, the instructions are further to cause the processor to:

determine, based on a determination that the acknowledgement is received, that the determined resource allocation was unsuccessful;

undo, using the record of the determined resource allocation in the records store, the determined resource allocation for the allocator client based on a determination that the determined resource allocation was unsuccessful; and

commit results pertaining to the determined resource allocation for the allocator client being undone in a placement store.

6. The apparatus of claim 1, wherein the instructions are further to cause the processor to:

receive a plurality of allocation requests from a plurality of allocator clients;

determine resource allocations for the received plurality of allocation requests;

store records of the determined resource allocations in the records store;

send the determined resource allocations respectively to the plurality of allocator clients, wherein acknowledgements to the sent determined resource allocations are to be received from the plurality of allocator clients; and

manage states of the determined resource allocations using the records stored in the records store based on whether the acknowledgements are received from the plurality of allocator clients.

7. The apparatus of claim 1, wherein the instructions are further to cause the processor to:

receive a first allocation request from a first allocator client;

determine a first resource allocation for the received first allocation request;

store a first record of the determined first resource allocation in the records store;

send the determined first resource allocation to the first allocator client;

prior to receipt of an acknowledgement to the determined first resource allocation,

receive a second allocation request from a second allocator client; and

determine a second resource allocation for the received second allocation request.

8. The apparatus of claim 1, wherein the instructions are further to cause the processor to:

receive resource inventory information from a plurality of resource inventory providers; and

update a resource map based on the received resource inventory information.

9. The apparatus of claim 1, wherein the instructions are further to cause the processor to:

prior to receipt of an acknowledgement to the sent determined resource allocation from the allocator client, commit the determined resource allocation to a placement store, wherein a resource is to pull a workload from the placement store corresponding to the committed resource allocation for the resource.

10. A method comprising:

receiving, by a processor, a first allocation request from a first allocator client;

determining, by the processor, a first resource allocation for the received first allocation request;

storing, by the processor, a first record of the first resource allocation in a records store;

sending, by the processor, the first resource allocation to the first allocator client;

prior to receiving an acknowledgement to the sent first resource allocation from the first allocator client, by the processor,

receiving a second allocation request from a second allocator client;

determining a second resource allocation for the second allocation request;

storing a second record of the determined second resource allocation in the records store;

sending the second resource allocation to the second allocator client; and

managing a state of the first resource allocation and a state of the second resource allocation using the first record and the second record stored in the records store based on whether the acknowledgement is received from the first allocator client or the second allocator client.

11. The method of claim 10, further comprising:

determining whether the acknowledgement is received from the first allocator client; and

based on a determination that the acknowledgement is received from the first allocator client, identifying whether the first resource allocation was successful or was unsuccessful from the received acknowledgement.

12. The method of claim 11, further comprising:

based on an identification that the first resource allocation was successful, deleting the first record in the records store.

13. The method of claim 12, wherein managing the state of the first resource allocation further comprises:

determining that the acknowledgement was not received from the first allocator client;

undoing, using the first record of the first resource allocation stored in the records store, the first resource allocation for the first allocator client based on a determination that the acknowledgement was not received; and

committing results pertaining to the first resource allocation for the first allocator client being undone in a placement store.

14. The method of claim 12, wherein managing the state of the first resource allocation further comprises:

determining, based on a determination that the acknowledgement is received, that the first resource allocation was unsuccessful;

undoing, using the first record of the first resource allocation in the records store, the first resource allocation for the first allocator client based on a determination that the first resource allocation was unsuccessful; and

committing results pertaining to the first resource allocation for the first allocator client being undone in a placement store.

15. The method of claim 10, further comprising:

receiving resource inventory information from a plurality of resource inventory providers; and

updating a resource map based on the received resource inventory information.

16. A non-transitory computer readable medium on which is stored machine readable instructions that when executed by a processor, cause the processor to:

receive a plurality of resource allocation requests from a plurality of allocator clients;

determine respective resource allocations for the plurality of resource allocation requests;

store records of the resource allocations in an escrow;

send the resource allocations to the allocator clients according to the allocator clients that submitted the resource allocation requests; and

manage states of the resource allocations using the records stored in the escrow based on whether acknowledgements to the sent resource allocations are received from the allocator clients.

17. The non-transitory computer readable medium of claim 16, wherein to manage the states of the resource allocations, the instructions are further to cause the processor to:

determine whether an acknowledgement is received from a first allocator client of the plurality of allocator clients;

based on a determination that the acknowledgement is received from the first allocator client, identify whether a first resource allocation for the first allocator client was successful or was unsuccessful from the received acknowledgement; and

based on an identification that the first resource allocation was successful, delete the first record in the records store.

18. The non-transitory computer readable medium of claim 17, wherein to manage the states of the resource allocations, the instructions are further to cause the processor to:

determine that the acknowledgement was not received from the first allocator client;

undo, using the first record of the first resource allocation stored in the records store, the first resource allocation for the first allocator client based on a determination that the acknowledgement was not received; and

commit results pertaining to the first resource allocation for the first allocator client being undone in a placement store.

19. The non-transitory computer readable medium of claim 17, wherein to manage the states of the resource allocations, the instructions are further to cause the processor to:

determine, based on a determination that the acknowledgement is received, that the first resource allocation was unsuccessful;

undo, using the first record of the first resource allocation in the records store, the first resource allocation for the first allocator client based on a determination that the first resource allocation was unsuccessful; and

commit results pertaining to the first resource allocation for the first allocator client being undone in a placement store.

20. The non-transitory computer readable medium of claim 16, wherein the instructions are further to cause the processor to:

receive resource inventory information from a plurality of resource inventory providers; and

update a resource map based on the received resource inventory information.