US2022012105A1PendingUtilityA1
Technologies for allocating resources across data centers
Est. expiryAug 30, 2037(~11.1 yrs left)· nominal 20-yr term from priority
Inventors:Anjaneya Reddy Chagam Reddy
H04L 69/32H04L 41/14H04L 41/0893H04L 41/0896H04L 9/0819H04L 69/321H04L 47/83H04L 43/20H04L 41/149H04L 41/0895H04L 41/40H04L 41/34H04L 69/18G06F 2209/5019G06F 9/5055G06F 9/5022G06F 9/5044G06F 9/5088H04L 67/1001G06F 11/3466H04L 41/5025G06F 11/3006G06F 11/3442G06F 2201/885H04L 41/044H04L 43/0876H04L 41/5019H04L 43/065H05K 7/1498G06N 3/063G06F 11/3409H04L 41/0816Y02D10/00H04L 43/16G06F 2201/86G06F 3/0665G06F 3/0629G06F 16/9014G06F 9/44G11C 29/028G06F 2200/201G06F 13/42G06F 16/25G06F 3/0605G06F 3/067H04L 41/142H04L 47/781H04L 41/0677H04L 41/0213G06F 3/0613G06F 2212/1044G06F 16/2455G06F 16/2453G06F 12/1054G06F 9/5061H05K 7/20209H05K 7/20736H04L 47/125G06F 16/221H04L 41/0668H05K 7/1489H04L 49/9005G06F 16/2365H04L 69/12G06F 15/7867G06F 2213/0064H04L 69/22G06F 9/4494G06Q 10/0631G06F 3/0685G06F 3/065G06Q 30/0283H04L 45/28G06F 12/1063G06F 3/0604G06F 16/119G06F 16/2255H04L 63/0428G06F 30/34G06F 3/0647H04L 67/1008G06F 2212/601H04L 47/11G06F 2212/1052G06F 3/0659G06F 3/0683G06F 16/2282G06F 9/4411G06F 9/4406H04L 45/7453G06F 12/14H04L 49/30G06F 3/0631H04L 9/0894G06F 15/161G06F 21/105G06F 16/248G06F 9/505G11C 8/12G06F 15/17331G11C 29/44G06F 3/0644G06F 16/2237H04L 41/16G06F 2201/85G06F 12/0607G06F 13/4022G06F 3/0673G06F 3/0611G06F 9/4401G06F 9/28G06F 13/4068G06F 3/0632G06F 12/0802G11C 29/36G11C 29/38H04L 49/351H05K 7/18G06F 9/445H04L 49/40G06F 13/1663G06F 13/1668G06F 12/06G06F 12/023G06F 2209/509G06F 9/4856G06F 16/24553G06F 1/20G06F 15/7807B25J 15/0014G06F 1/183G06F 2213/3808G06F 2213/0026G06F 15/1735G06F 15/173H04Q 11/0062H04Q 11/0005
75
PatentIndex Score
0
Cited by
0
References
0
Claims
Abstract
Technologies for allocating resources across data centers include a compute device to obtain resource utilization data indicative of a utilization of resources for a managed node to execute a workload. The compute device is also to determine whether a set of resources presently available to the managed node in a data center in which the compute device is located satisfies the resource utilization data. Additionally, the compute device is to allocate, in response to a determination that the set of resources presently available to the managed node does not satisfy the resource utilization data, a supplemental set of resources to the managed node. The supplemental set of resources are located in an off-premises data center that is different from the data center in which the compute device is located. Other embodiments are also described and claimed.
Claims
exact text as granted — not AI-modified1 . A server comprising:
a node, the node comprising resources, the resources including:
a compute resource to execute an application;
a data storage resource;
an accelerator resource; and
a memory resource; and
one or more non-transitory machine-readable storage media comprising a plurality of instructions stored thereon that, in response to being executed, cause the server to: communicate with a remote server via a public cloud service to allocate a remote resource in the remote server to the node based on the resources available in the server; and obtain address information from the remote server for use by the node to access the remote resource as if the remote resource was in the server.
2 . The server of claim 1 , wherein the server to select the remote resource as a function of availability and cost.
3 . The server of claim 1 , wherein the server to utilize an application programming interface to communicate with the remote server in a format specific to the remote server.
4 . The server of claim 1 , wherein the server to communicate with the remote resource using a non-volatile memory express over fabric (NVMe-oF) bus protocol.
5 . The server of claim 1 , wherein the server to communicate with the remote server via the public cloud service to deallocate the remote resource in the remote server to the node if the resources to be used in an execution of a workload by the node decrease below the resources available in the server.
6 . The server of claim 1 , wherein the remote resource is a remote accelerator resource.
7 . The server of claim 1 , wherein the remote resource is a remote storage resource.
8 . One or more non-transitory machine-readable storage media comprising a plurality of instructions stored thereon that, in response to being executed, cause a server to:
communicate with a remote server via a public cloud service to allocate a remote resource in the remote server to a node based on resources available in the server, the node comprising the resources, the resources including a compute resource to execute an application, a data storage resource, an accelerator resource, and a memory resource; and obtain address information from the remote server for use by the node to access the remote resource as if the remote resource was in the server.
9 . The one or more non-transitory machine-readable storage media of claim 8 , wherein the server to select the remote resource as a function of availability and cost.
10 . The one or more non-transitory machine-readable storage media of claim 8 , wherein the server to utilize an application programming interface to communicate with the remote server in a format specific to the remote server.
11 . The one or more non-transitory machine-readable storage media of claim 8 , wherein the server to communicate with the remote resource using a non-volatile memory express over fabric (NVMe-oF) bus protocol.
12 . The one or more non-transitory machine-readable storage media of claim 8 , wherein the server to communicate with the remote server via the public cloud service to deallocate the remote resource in the remote server to the node if the resources to be used in an execution of a workload by the node decrease below the resources available in the server.
13 . The one or more non-transitory machine-readable storage media of claim 8 , wherein the remote resource is a remote accelerator resource.
14 . The one or more non-transitory machine-readable storage media of claim 8 , wherein the remote resource is a remote storage resource.
15 . A method comprising:
communicating, by a server, with a remote server via a public cloud service to allocate a remote resource in the remote server to a node based on resources available in the server, the node comprising the resources, the resources including a compute resource to execute an application, a data storage resource, an accelerator resource and a memory resource; and obtaining, by the server, address information from the remote server for use by the node to access the remote resource as if the remote resource was in the server.
16 . The method of claim 15 , wherein the server to select the remote resource as a function of availability and cost.
17 . The method of claim 15 , wherein the server to utilize an application programming interface to communicate with the remote server in a format specific to the remote server.
18 . The method of claim 15 , wherein the server to communicate with the remote resource using a non-volatile memory express over fabric (NVMe-oF) bus protocol.
19 . The method of claim 15 , wherein the server to communicate with the remote server via the public cloud service to deallocate the remote resource in the remote server to the node if the resources to be used in an execution of a workload by the node decrease below the resources available in the server.
20 . The method of claim 15 , wherein the remote resource is a remote accelerator resource.
21 . The method of claim 15 , wherein the remote resource is a remote storage resource.Join the waitlist — get patent alerts
Track US2022012105A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.