U.S. patent application number 15/922493 was filed with the patent office on 2019-02-07 for technologies for separating control plane management from data plane management for distributed storage in a disaggregated architecture.
The applicant listed for this patent is Intel Corporation. Invention is credited to Anjaneya Reddy Chagam Reddy, Arun Raghunath, Sujoy Sen, Yi Zou.
Application Number | 20190042090 15/922493 |
Document ID | / |
Family ID | 65037934 |
Filed Date | 2019-02-07 |
![](/patent/app/20190042090/US20190042090A1-20190207-D00000.png)
![](/patent/app/20190042090/US20190042090A1-20190207-D00001.png)
![](/patent/app/20190042090/US20190042090A1-20190207-D00002.png)
![](/patent/app/20190042090/US20190042090A1-20190207-D00003.png)
![](/patent/app/20190042090/US20190042090A1-20190207-D00004.png)
![](/patent/app/20190042090/US20190042090A1-20190207-D00005.png)
![](/patent/app/20190042090/US20190042090A1-20190207-D00006.png)
![](/patent/app/20190042090/US20190042090A1-20190207-D00007.png)
![](/patent/app/20190042090/US20190042090A1-20190207-D00008.png)
![](/patent/app/20190042090/US20190042090A1-20190207-D00009.png)
![](/patent/app/20190042090/US20190042090A1-20190207-D00010.png)
View All Diagrams
United States Patent
Application |
20190042090 |
Kind Code |
A1 |
Raghunath; Arun ; et
al. |
February 7, 2019 |
TECHNOLOGIES FOR SEPARATING CONTROL PLANE MANAGEMENT FROM DATA
PLANE MANAGEMENT FOR DISTRIBUTED STORAGE IN A DISAGGREGATED
ARCHITECTURE
Abstract
Technologies for separating control plane management from data
plane management for distributed storage in a disaggregated
architecture include a compute sled. The compute sled includes a
network interface controller and circuitry to receive, through a
network and with the network interface controller, a data access
request from a compute device. The data access request includes a
data payload indicative of an object to be stored. The circuitry is
also to map the object to a set of multiple data storage sleds for
distributed storage of the object. Additionally, the circuitry is
to send, through the network and with a local data bus protocol
mapped onto a network protocol, a write request to the mapped data
storage sleds to store the object in one or more data storage
devices located on each data storage sled. Other embodiments are
also described and claimed.
Inventors: |
Raghunath; Arun; (Portland,
OR) ; Chagam Reddy; Anjaneya Reddy; (Chandler,
AZ) ; Sen; Sujoy; (Beaverton, OR) ; Zou;
Yi; (Portland, OR) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Intel Corporation |
Santa Clara |
CA |
US |
|
|
Family ID: |
65037934 |
Appl. No.: |
15/922493 |
Filed: |
March 15, 2018 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
62584401 |
Nov 10, 2017 |
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
G06F 2213/0064 20130101;
H04L 9/0894 20130101; G06F 3/0632 20130101; H04L 41/0677 20130101;
G06F 16/25 20190101; G06F 3/0611 20130101; G06F 12/1054 20130101;
G06F 12/1063 20130101; G06F 16/9014 20190101; H04L 47/11 20130101;
G06F 3/0604 20130101; G06F 9/4494 20180201; G06F 9/5044 20130101;
G11C 29/38 20130101; G06F 3/0631 20130101; G06F 3/065 20130101;
G06F 15/161 20130101; G06F 16/2255 20190101; G06F 16/2365 20190101;
G06F 2209/509 20130101; G11C 29/36 20130101; G06F 12/0802 20130101;
G06F 2212/601 20130101; Y02D 10/00 20180101; G06F 12/14 20130101;
G06F 13/4068 20130101; H04L 49/9005 20130101; H04L 69/12 20130101;
G06F 3/0605 20130101; G06F 9/445 20130101; G06F 13/42 20130101;
G06F 3/0629 20130101; G06F 3/067 20130101; G06F 3/0685 20130101;
G06F 16/2453 20190101; G06F 16/24553 20190101; H04L 9/0819
20130101; G06F 12/0607 20130101; H04L 41/0893 20130101; G06F 3/0659
20130101; G06F 9/4401 20130101; G06F 2212/1052 20130101; G11C 8/12
20130101; G06F 3/0647 20130101; G06F 3/0673 20130101; G06F 3/0683
20130101; H04L 45/7453 20130101; G06F 16/221 20190101; H04L 41/0896
20130101; G06F 9/4411 20130101; H04L 41/0213 20130101; G06F 9/5088
20130101; G06F 12/023 20130101; G06F 16/2455 20190101; G06F 30/34
20200101; G06F 15/17331 20130101; G06F 16/248 20190101; G06F
2201/85 20130101; G06F 2212/1044 20130101; G11C 29/028 20130101;
H04L 47/125 20130101; H04L 49/30 20130101; G06F 3/0613 20130101;
G06F 16/2237 20190101; G11C 29/44 20130101; H04L 41/0668 20130101;
H04L 69/32 20130101; H04L 69/321 20130101; H04L 49/351 20130101;
G06F 9/28 20130101; G06F 9/4406 20130101; G06F 13/1668 20130101;
G06F 3/0644 20130101; H04L 45/28 20130101; G06F 12/06 20130101;
G06F 13/1663 20130101; G06F 16/119 20190101; H04L 69/22 20130101;
G06F 16/2282 20190101 |
International
Class: |
G06F 3/06 20060101
G06F003/06; G06F 13/42 20060101 G06F013/42; G06F 13/40 20060101
G06F013/40; G06F 13/16 20060101 G06F013/16 |
Foreign Application Data
Date |
Code |
Application Number |
Aug 30, 2017 |
IN |
201741030632 |
Claims
1. A compute sled comprising: a network interface controller; and
circuitry to: receive, through a network and with the network
interface controller, a data access request from a compute device,
wherein the data access request includes a data payload indicative
of an object to be stored; map the object to a set of multiple data
storage sleds for distributed storage of the object; and send,
through the network and with a local data bus protocol mapped onto
a network protocol, a write request to the mapped data storage
sleds to store the object in one or more data storage devices
located on each data storage sled.
2. The compute sled of claim 1, wherein to send, through the
network and with a local data bus protocol mapped onto a network
protocol, a write request comprises to tunnel the write request
through a non-volatile memory express over fabric (NVMeOF)
connection to the data storage sleds.
3. The compute sled of claim 1, wherein to map the object to the
data storage sleds comprises to map the object to data storage
sleds in different failure domains.
4. The compute sled of claim 1, wherein the circuitry is further to
send, through the network and to one or more other compute sleds,
metadata associated with the object.
5. The compute sled of claim 4, wherein to send, through the
network and to one or more other compute sleds, metadata associated
with the object comprises to send the metadata to one or more
compute sleds associated with the mapped data storage sleds.
6. The compute sled of claim 4, wherein to send the metadata
comprises to send one or more of an object identifier associated
with the object or metadata indicative of one or more attributes of
the object.
7. The compute sled of claim 1, wherein to map the object to the
data storage sleds comprises to map the object as a function of a
hash of a uniform resource locator associated with the object.
8. The compute sled of claim 1, wherein the circuitry is further to
verify, prior to sending the write request to the mapped data
storage sled, that the data payload represents an object that is
not already stored on one or more of the data storage sleds.
9. The compute sled of claim 8, wherein to verify that the data
payload represents and object that is not already stored on one or
more of the data storage sleds comprises to compare an object
identifier associated with the object to object identifiers for
objects stored in a data storage sled associated with the compute
sled.
10. The compute sled of claim 1, wherein the circuitry is further
to: receive a request a read a second object, wherein the request
includes an identifier of the second object; and determine, in
response to the read request, one or more storage sleds mapped to
the identifier of the second object; send, through the network and
with the local data bus protocol mapped onto the network protocol,
a read request to the mapped one or more data storage sleds; and
receive the read object from the mapped one or more data storage
sleds.
11. The compute sled of claim 10, wherein to send, through the
network and with the local data bus protocol mapped onto the
network protocol, a read request comprises to tunnel the read
request through a non-volatile memory express over fabric (NVMeOF)
connection to the one or more data storage sleds.
12. One or more machine-readable storage media comprising a
plurality of instructions stored thereon that, in response to being
executed, cause a compute sled to: receive, through a network and
with a network interface controller, a data access request from a
compute device, wherein the data access request includes a data
payload indicative of an object to be stored; map the object to a
set of multiple data storage sleds for distributed storage of the
object; and send, through the network and with a local data bus
protocol mapped onto a network protocol, a write request to the
mapped data storage sleds to store the object in one or more data
storage devices located on each data storage sled.
13. The one or more machine-readable storage media of claim 12,
wherein to send, through the network and with a local data bus
protocol mapped onto a network protocol, a write request comprises
to tunnel the write request through a non-volatile memory express
over fabric (NVMeOF) connection to the data storage sleds.
14. The one or more machine-readable storage media of claim 12,
wherein to map the object to the data storage sleds comprises to
map the object to data storage sleds in different failure
domains.
15. The one or more machine-readable storage media of claim 12,
wherein, when executed, the plurality of instructions further cause
the compute sled to send, through the network and to one or more
other compute sleds, metadata associated with the object.
16. The one or more machine-readable storage media of claim 15,
wherein to send, through the network and to one or more other
compute sleds, metadata associated with the object comprises to
send the metadata to one or more compute sleds associated with the
mapped data storage sleds.
17. The one or more machine-readable storage media of claim 15,
wherein to send the metadata comprises to send one or more of an
object identifier associated with the object or metadata indicative
of one or more attributes of the object.
18. The one or more machine-readable storage media of claim 12,
wherein to map the object to the data storage sleds comprises to
map the object as a function of a hash of a uniform resource
locator associated with the object.
19. A method comprising: receiving, by a compute sled with a
network interface controller, a data access request from a compute
device, wherein the data access request includes a data payload
indicative of an object to be stored; mapping, by the compute sled,
the object to a set of multiple data storage sleds for distributed
storage of the object; and sending, by the compute sled, through a
network and with a local data bus protocol mapped onto a network
protocol, a write request to the mapped data storage sleds to store
the object in one or more data storage devices located on each data
storage sled.
20. The method of claim 19, wherein sending, through the network
and with a local data bus protocol mapped onto a network protocol,
a write request comprises tunneling the write request through a
non-volatile memory express over fabric (NVMeOF) connection to the
data storage sleds.
21. The method of claim 19, wherein mapping the object to the data
storage sleds comprises mapping the object to data storage sleds in
different failure domains.
22. The method of claim 19, further comprising sending, by the
compute sled, through the network and to one or more other compute
sleds, metadata associated with the object.
23. A data storage sled comprising: a network interface controller;
a set of data storage devices; and circuitry to: receive, through
the network interface controller and with a local data bus protocol
mapped onto a network protocol, a write request from a compute sled
of a distributed data storage system, wherein the write request
includes an object to be written to one or more of the data storage
devices; determine one or more blocks of the set of data storage
devices to write the object to; write an identifier of each
determined block to a block ownership database in association with
an identifier of the object; and write the object to the determined
one or more blocks.
24. The data storage sled of claim 23, wherein the data storage
devices have different performance characteristics resulting from
different physical storage media in each data storage device and
wherein to determine the one or more blocks of the set of data
storage devices to write the object to comprises to determine the
one or more blocks as a function of a target access latency.
25. The data storage sled of claim 23, wherein to determine the one
or more blocks of the set of data storage devices to write the
object to comprises to determine the one or more blocks as a
function of a data storage device wear leveling scheme.
26. The data storage sled of claim 23, wherein the circuitry is
further to: receive, through the network interface controller, a
read request from the compute sled, wherein the read request
includes the identifier of the object; determine, from the block
ownership database, the one or more blocks of the set of data
storage devices to read the object from; read the object from the
determined one or more blocks of the set of data storage devices;
and send the object to the compute sled.
27. A method comprising: receiving, through a network interface
controller of a data storage sled and with a local data bus
protocol mapped onto a network protocol, a write request from a
compute sled of a distributed data storage system, wherein the
write request includes an object to be written to one or more data
storage devices of the data storage sled; determining, by the data
storage sled, one or more blocks of the data storage devices to
write the object to; writing, by the data storage sled, an
identifier of each determined block to a block ownership database
in association with an identifier of the object; and writing, by
the data storage sled, the object to the determined one or more
blocks.
28. One or more machine-readable storage media comprising a
plurality of instructions stored thereon that, in response to being
executed, cause a data storage sled to: receive, through a network
interface controller of the data storage sled and with a local data
bus protocol mapped onto a network protocol, a write request from a
compute sled of a distributed data storage system, wherein the
write request includes an object to be written to one or more data
storage devices of the data storage sled; determine, by the data
storage sled, one or more blocks of the data storage devices to
write the object to; write, by the data storage sled, an identifier
of each determined block to a block ownership database in
association with an identifier of the object; and write, by the
data storage sled, the object to the determined one or more blocks.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] The present application claims the benefit of Indian
Provisional Patent Application No. 201741030632, filed Aug. 30,
2017 and U.S. Provisional Patent Application No. 62/584,401, filed
Nov. 10, 2017.
BACKGROUND
[0002] In some data centers, data sets may be stored in multiple
data storage devices located in different areas of the data center
(e.g., in different failure domains). Typically, in such systems,
one compute device may receive a request to store a data set (e.g.,
a payload) and may store the data set in one or more data storage
devices that are physically located on the compute device (e.g.,
connected through a local data bus such as a Peripheral Component
Interconnect Express (PCIe) bus). Additionally, the compute device
may send the data set to one or more other similarly equipped
compute devices (e.g., in different failure domains), to store the
same data set in data storage devices that are physically located
on those compute devices. As such, typical distributed data storage
systems are designed such that control plane management operations
(e.g., selection of compute devices that are to store the data set)
and data plane management operations (e.g., allocation of data
blocks on a physical data storage device, fragmentation management,
etc.) are performed on the same compute device.
[0003] In data centers in which resources are disaggregated (e.g.,
some compute devices have comparatively more compute resources and
less data storage resources, or comparatively more data storage
resources and less compute resources), typical data storage systems
may operate less efficiently, as the resources for performing both
compute intensive operations (e.g., control plane operations) and
storage device management operations (e.g., data plane management)
are not equally present in the same physical compute device. For
example, a data storage-focused compute device may have
insufficient compute resources to efficiently perform control plane
management operations.
BRIEF DESCRIPTION OF THE DRAWINGS
[0004] The concepts described herein are illustrated by way of
example and not by way of limitation in the accompanying figures.
For simplicity and clarity of illustration, elements illustrated in
the figures are not necessarily drawn to scale. Where considered
appropriate, reference labels have been repeated among the figures
to indicate corresponding or analogous elements.
[0005] FIG. 1 is a simplified diagram of at least one embodiment of
a data center for executing workloads with disaggregated
resources;
[0006] FIG. 2 is a simplified diagram of at least one embodiment of
a pod that may be included in the data center of FIG. 1;
[0007] FIG. 3 is a perspective view of at least one embodiment of a
rack that may be included in the pod of FIG. 2;
[0008] FIG. 4 is a side elevation view of the rack of FIG. 3;
[0009] FIG. 5 is a perspective view of the rack of FIG. 3 having a
sled mounted therein;
[0010] FIG. 6 is a is a simplified block diagram of at least one
embodiment of a top side of the sled of FIG. 5;
[0011] FIG. 7 is a simplified block diagram of at least one
embodiment of a bottom side of the sled of FIG. 6;
[0012] FIG. 8 is a simplified block diagram of at least one
embodiment of a compute sled usable in the data center of FIG.
1;
[0013] FIG. 9 is a top perspective view of at least one embodiment
of the compute sled of FIG. 8;
[0014] FIG. 10 is a simplified block diagram of at least one
embodiment of an accelerator sled usable in the data center of FIG.
1;
[0015] FIG. 11 is a top perspective view of at least one embodiment
of the accelerator sled of FIG. 10;
[0016] FIG. 12 is a simplified block diagram of at least one
embodiment of a storage sled usable in the data center of FIG.
1;
[0017] FIG. 13 is a top perspective view of at least one embodiment
of the storage sled of FIG. 12;
[0018] FIG. 14 is a simplified block diagram of at least one
embodiment of a memory sled usable in the data center of FIG. 1;
and
[0019] FIG. 15 is a simplified block diagram of a system that may
be established within the data center of FIG. 1 to execute
workloads with managed nodes composed of disaggregated
resources;
[0020] FIG. 16 is a simplified block diagram of at least one
embodiment of a system for providing distributed storage with
physically separated control plane management and data plane
management in a disaggregated architecture;
[0021] FIGS. 17-19 are a simplified block diagram of at least one
embodiment of a method for executing control plane management
operations in response to a data access request that may be
performed by a compute sled of FIG. 16; and
[0022] FIGS. 20-21 are a simplified block diagram of at least one
embodiment of a method for executing data plane management
operations that may be performed by a data storage sled of FIG.
16.
DETAILED DESCRIPTION OF THE DRAWINGS
[0023] While the concepts of the present disclosure are susceptible
to various modifications and alternative forms, specific
embodiments thereof have been shown by way of example in the
drawings and will be described herein in detail. It should be
understood, however, that there is no intent to limit the concepts
of the present disclosure to the particular forms disclosed, but on
the contrary, the intention is to cover all modifications,
equivalents, and alternatives consistent with the present
disclosure and the appended claims.
[0024] References in the specification to "one embodiment," "an
embodiment," "an illustrative embodiment," etc., indicate that the
embodiment described may include a particular feature, structure,
or characteristic, but every embodiment may or may not necessarily
include that particular feature, structure, or characteristic.
Moreover, such phrases are not necessarily referring to the same
embodiment. Further, when a particular feature, structure, or
characteristic is described in connection with an embodiment, it is
submitted that it is within the knowledge of one skilled in the art
to effect such feature, structure, or characteristic in connection
with other embodiments whether or not explicitly described.
Additionally, it should be appreciated that items included in a
list in the form of "at least one A, B, and C" can mean (A); (B);
(C); (A and B); (A and C); (B and C); or (A, B, and C). Similarly,
items listed in the form of "at least one of A, B, or C" can mean
(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and
C).
[0025] The disclosed embodiments may be implemented, in some cases,
in hardware, firmware, software, or any combination thereof. The
disclosed embodiments may also be implemented as instructions
carried by or stored on a transitory or non-transitory
machine-readable (e.g., computer-readable) storage medium, which
may be read and executed by one or more processors. A
machine-readable storage medium may be embodied as any storage
device, mechanism, or other physical structure for storing or
transmitting information in a form readable by a machine (e.g., a
volatile or non-volatile memory, a media disc, or other media
device).
[0026] In the drawings, some structural or method features may be
shown in specific arrangements and/or orderings. However, it should
be appreciated that such specific arrangements and/or orderings may
not be required. Rather, in some embodiments, such features may be
arranged in a different manner and/or order than shown in the
illustrative figures. Additionally, the inclusion of a structural
or method feature in a particular figure is not meant to imply that
such feature is required in all embodiments and, in some
embodiments, may not be included or may be combined with other
features.
[0027] Referring now to FIG. 1, a data center 100 in which
disaggregated resources may cooperatively execute one or more
workloads (e.g., applications on behalf of customers) includes
multiple pods 110, 120, 130, 140, each of which includes one or
more rows of racks. Of course, although data center 100 is shown
with multiple pods, in some embodiments, the data center 100 may be
embodied as a single pod. As described in more detail herein, each
rack houses multiple sleds, each of which may be primarily equipped
with a particular type of resource (e.g., memory devices, data
storage devices, accelerator devices, general purpose processors),
i.e., resources that can be logically coupled to form a composed
node, which can act as, for example, a server. In the illustrative
embodiment, the sleds in each pod 110, 120, 130, 140 are connected
to multiple pod switches (e.g., switches that route data
communications to and from sleds within the pod). The pod switches,
in turn, connect with spine switches 150 that switch communications
among pods (e.g., the pods 110, 120, 130, 140) in the data center
100. In some embodiments, the sleds may be connected with a fabric
using Intel Omni-Path technology. In other embodiments, the sleds
may be connected with other fabrics, such as InfiniBand or
Ethernet. As described in more detail herein, resources within
sleds in the data center 100 may be allocated to a group (referred
to herein as a "managed node") containing resources from one or
more sleds to be collectively utilized in the execution of a
workload. The workload can execute as if the resources belonging to
the managed node were located on the same sled. The resources in a
managed node may belong to sleds belonging to different racks, and
even to different pods 110, 120, 130, 140. As such, some resources
of a single sled may be allocated to one managed node while other
resources of the same sled are allocated to a different managed
node (e.g., one processor assigned to one managed node and another
processor of the same sled assigned to a different managed
node).
[0028] A data center comprising disaggregated resources, such as
data center 100, can be used in a wide variety of contexts, such as
enterprise, government, cloud service provider, and communications
service provider (e.g., Telco's), as well in a wide variety of
sizes, from cloud service provider mega-data centers that consume
over 100,000 sq. ft. to single- or multi-rack installations for use
in base stations.
[0029] The disaggregation of resources to sleds comprised
predominantly of a single type of resource (e.g., compute sleds
comprising primarily compute resources, memory sleds containing
primarily memory resources), and the selective allocation and
deallocation of the disaggregated resources to form a managed node
assigned to execute a workload improves the operation and resource
usage of the data center 100 relative to typical data centers
comprised of hyperconverged servers containing compute, memory,
storage and perhaps additional resources in a single chassis. For
example, because sleds predominantly contain resources of a
particular type, resources of a given type can be upgraded
independently of other resources. Additionally, because different
resources types (processors, storage, accelerators, etc.) typically
have different refresh rates, greater resource utilization and
reduced total cost of ownership may be achieved. For example, a
data center operator can upgrade the processors throughout their
facility by only swapping out the compute sleds. In such a case,
accelerator and storage resources may not be contemporaneously
upgraded and, rather, may be allowed to continue operating until
those resources are scheduled for their own refresh. Resource
utilization may also increase. For example, if managed nodes are
composed based on requirements of the workloads that will be
running on them, resources within a node are more likely to be
fully utilized. Such utilization may allow for more managed nodes
to run in a data center with a given set of resources, or for a
data center expected to run a given set of workloads, to be built
using fewer resources.
[0030] Referring now to FIG. 2, the pod 110, in the illustrative
embodiment, includes a set of rows 200, 210, 220, 230 of racks 240.
Each rack 240 may house multiple sleds (e.g., sixteen sleds) and
provide power and data connections to the housed sleds, as
described in more detail herein. In the illustrative embodiment,
the racks in each row 200, 210, 220, 230 are connected to multiple
pod switches 250, 260. The pod switch 250 includes a set of ports
252 to which the sleds of the racks of the pod 110 are connected
and another set of ports 254 that connect the pod 110 to the spine
switches 150 to provide connectivity to other pods in the data
center 100. Similarly, the pod switch 260 includes a set of ports
262 to which the sleds of the racks of the pod 110 are connected
and a set of ports 264 that connect the pod 110 to the spine
switches 150. As such, the use of the pair of switches 250, 260
provides an amount of redundancy to the pod 110. For example, if
either of the switches 250, 260 fails, the sleds in the pod 110 may
still maintain data communication with the remainder of the data
center 100 (e.g., sleds of other pods) through the other switch
250, 260. Furthermore, in the illustrative embodiment, the switches
150, 250, 260 may be embodied as dual-mode optical switches,
capable of routing both Ethernet protocol communications carrying
Internet Protocol (IP) packets and communications according to a
second, high-performance link-layer protocol (e.g., Intel's
Omni-Path Architecture's, InfiniBand, PCI Express) via optical
signaling media of an optical fabric.
[0031] It should be appreciated that each of the other pods 120,
130, 140 (as well as any additional pods of the data center 100)
may be similarly structured as, and have components similar to, the
pod 110 shown in and described in regard to FIG. 2 (e.g., each pod
may have rows of racks housing multiple sleds as described above).
Additionally, while two pod switches 250, 260 are shown, it should
be understood that in other embodiments, each pod 110, 120, 130,
140 may be connected to a different number of pod switches,
providing even more failover capacity. Of course, in other
embodiments, pods may be arranged differently than the
rows-of-racks configuration shown in FIGS. 1-2. For example, a pod
may be embodied as multiple sets of racks in which each set of
racks is arranged radially, i.e., the racks are equidistant from a
center switch.
[0032] Referring now to FIGS. 3-5, each illustrative rack 240 of
the data center 100 includes two elongated support posts 302, 304,
which are arranged vertically. For example, the elongated support
posts 302, 304 may extend upwardly from a floor of the data center
100 when deployed. The rack 240 also includes one or more
horizontal pairs 310 of elongated support arms 312 (identified in
FIG. 3 via a dashed ellipse) configured to support a sled of the
data center 100 as discussed below. One elongated support arm 312
of the pair of elongated support arms 312 extends outwardly from
the elongated support post 302 and the other elongated support arm
312 extends outwardly from the elongated support post 304.
[0033] In the illustrative embodiments, each sled of the data
center 100 is embodied as a chassis-less sled. That is, each sled
has a chassis-less circuit board substrate on which physical
resources (e.g., processors, memory, accelerators, storage, etc.)
are mounted as discussed in more detail below. As such, the rack
240 is configured to receive the chassis-less sleds. For example,
each pair 310 of elongated support arms 312 defines a sled slot 320
of the rack 240, which is configured to receive a corresponding
chassis-less sled. To do so, each illustrative elongated support
arm 312 includes a circuit board guide 330 configured to receive
the chassis-less circuit board substrate of the sled. Each circuit
board guide 330 is secured to, or otherwise mounted to, a top side
332 of the corresponding elongated support arm 312. For example, in
the illustrative embodiment, each circuit board guide 330 is
mounted at a distal end of the corresponding elongated support arm
312 relative to the corresponding elongated support post 302, 304.
For clarity of the Figures, not every circuit board guide 330 may
be referenced in each Figure.
[0034] Each circuit board guide 330 includes an inner wall that
defines a circuit board slot 380 configured to receive the
chassis-less circuit board substrate of a sled 400 when the sled
400 is received in the corresponding sled slot 320 of the rack 240.
To do so, as shown in FIG. 4, a user (or robot) aligns the
chassis-less circuit board substrate of an illustrative
chassis-less sled 400 to a sled slot 320. The user, or robot, may
then slide the chassis-less circuit board substrate forward into
the sled slot 320 such that each side edge 414 of the chassis-less
circuit board substrate is received in a corresponding circuit
board slot 380 of the circuit board guides 330 of the pair 310 of
elongated support arms 312 that define the corresponding sled slot
320 as shown in FIG. 4. By having robotically accessible and
robotically manipulable sleds comprising disaggregated resources,
each type of resource can be upgraded independently of each other
and at their own optimized refresh rate. Furthermore, the sleds are
configured to blindly mate with power and data communication cables
in each rack 240, enhancing their ability to be quickly removed,
upgraded, reinstalled, and/or replaced. As such, in some
embodiments, the data center 100 may operate (e.g., execute
workloads, undergo maintenance and/or upgrades, etc.) without human
involvement on the data center floor. In other embodiments, a human
may facilitate one or more maintenance or upgrade operations in the
data center 100.
[0035] It should be appreciated that each circuit board guide 330
is dual sided. That is, each circuit board guide 330 includes an
inner wall that defines a circuit board slot 380 on each side of
the circuit board guide 330. In this way, each circuit board guide
330 can support a chassis-less circuit board substrate on either
side. As such, a single additional elongated support post may be
added to the rack 240 to turn the rack 240 into a two-rack solution
that can hold twice as many sled slots 320 as shown in FIG. 3. The
illustrative rack 240 includes seven pairs 310 of elongated support
arms 312 that define a corresponding seven sled slots 320, each
configured to receive and support a corresponding sled 400 as
discussed above. Of course, in other embodiments, the rack 240 may
include additional or fewer pairs 310 of elongated support arms 312
(i.e., additional or fewer sled slots 320). It should be
appreciated that because the sled 400 is chassis-less, the sled 400
may have an overall height that is different than typical servers.
As such, in some embodiments, the height of each sled slot 320 may
be shorter than the height of a typical server (e.g., shorter than
a single rank unit, "1 U"). That is, the vertical distance between
each pair 310 of elongated support arms 312 may be less than a
standard rack unit "1 U." Additionally, due to the relative
decrease in height of the sled slots 320, the overall height of the
rack 240 in some embodiments may be shorter than the height of
traditional rack enclosures. For example, in some embodiments, each
of the elongated support posts 302, 304 may have a length of six
feet or less. Again, in other embodiments, the rack 240 may have
different dimensions. For example, in some embodiments, the
vertical distance between each pair 310 of elongated support arms
312 may be greater than a standard rack until "1 U". In such
embodiments, the increased vertical distance between the sleds
allows for larger heat sinks to be attached to the physical
resources and for larger fans to be used (e.g., in the fan array
370 described below) for cooling each sled, which in turn can allow
the physical resources to operate at increased power levels.
Further, it should be appreciated that the rack 240 does not
include any walls, enclosures, or the like. Rather, the rack 240 is
an enclosure-less rack that is opened to the local environment. Of
course, in some cases, an end plate may be attached to one of the
elongated support posts 302, 304 in those situations in which the
rack 240 forms an end-of-row rack in the data center 100.
[0036] In some embodiments, various interconnects may be routed
upwardly or downwardly through the elongated support posts 302,
304. To facilitate such routing, each elongated support post 302,
304 includes an inner wall that defines an inner chamber in which
interconnects may be located. The interconnects routed through the
elongated support posts 302, 304 may be embodied as any type of
interconnects including, but not limited to, data or communication
interconnects to provide communication connections to each sled
slot 320, power interconnects to provide power to each sled slot
320, and/or other types of interconnects.
[0037] The rack 240, in the illustrative embodiment, includes a
support platform on which a corresponding optical data connector
(not shown) is mounted. Each optical data connector is associated
with a corresponding sled slot 320 and is configured to mate with
an optical data connector of a corresponding sled 400 when the sled
400 is received in the corresponding sled slot 320. In some
embodiments, optical connections between components (e.g., sleds,
racks, and switches) in the data center 100 are made with a blind
mate optical connection. For example, a door on each cable may
prevent dust from contaminating the fiber inside the cable. In the
process of connecting to a blind mate optical connector mechanism,
the door is pushed open when the end of the cable approaches or
enters the connector mechanism. Subsequently, the optical fiber
inside the cable may enter a gel within the connector mechanism and
the optical fiber of one cable comes into contact with the optical
fiber of another cable within the gel inside the connector
mechanism.
[0038] The illustrative rack 240 also includes a fan array 370
coupled to the cross-support arms of the rack 240. The fan array
370 includes one or more rows of cooling fans 372, which are
aligned in a horizontal line between the elongated support posts
302, 304. In the illustrative embodiment, the fan array 370
includes a row of cooling fans 372 for each sled slot 320 of the
rack 240. As discussed above, each sled 400 does not include any
on-board cooling system in the illustrative embodiment and, as
such, the fan array 370 provides cooling for each sled 400 received
in the rack 240. Each rack 240, in the illustrative embodiment,
also includes a power supply associated with each sled slot 320.
Each power supply is secured to one of the elongated support arms
312 of the pair 310 of elongated support arms 312 that define the
corresponding sled slot 320. For example, the rack 240 may include
a power supply coupled or secured to each elongated support arm 312
extending from the elongated support post 302. Each power supply
includes a power connector configured to mate with a power
connector of the sled 400 when the sled 400 is received in the
corresponding sled slot 320. In the illustrative embodiment, the
sled 400 does not include any on-board power supply and, as such,
the power supplies provided in the rack 240 supply power to
corresponding sleds 400 when mounted to the rack 240. Each power
supply is configured to satisfy the power requirements for its
associated sled, which can vary from sled to sled. Additionally,
the power supplies provided in the rack 240 can operate independent
of each other. That is, within a single rack, a first power supply
providing power to a compute sled can provide power levels that are
different than power levels supplied by a second power supply
providing power to an accelerator sled. The power supplies may be
controllable at the sled level or rack level, and may be controlled
locally by components on the associated sled or remotely, such as
by another sled or an orchestrator.
[0039] Referring now to FIG. 6, the sled 400, in the illustrative
embodiment, is configured to be mounted in a corresponding rack 240
of the data center 100 as discussed above. In some embodiments,
each sled 400 may be optimized or otherwise configured for
performing particular tasks, such as compute tasks, acceleration
tasks, data storage tasks, etc. For example, the sled 400 may be
embodied as a compute sled 800 as discussed below in regard to
FIGS. 8-9, an accelerator sled 1000 as discussed below in regard to
FIGS. 10-11, a storage sled 1200 as discussed below in regard to
FIGS. 12-13, or as a sled optimized or otherwise configured to
perform other specialized tasks, such as a memory sled 1400,
discussed below in regard to FIG. 14.
[0040] As discussed above, the illustrative sled 400 includes a
chassis-less circuit board substrate 602, which supports various
physical resources (e.g., electrical components) mounted thereon.
It should be appreciated that the circuit board substrate 602 is
"chassis-less" in that the sled 400 does not include a housing or
enclosure. Rather, the chassis-less circuit board substrate 602 is
open to the local environment. The chassis-less circuit board
substrate 602 may be formed from any material capable of supporting
the various electrical components mounted thereon. For example, in
an illustrative embodiment, the chassis-less circuit board
substrate 602 is formed from an FR-4 glass-reinforced epoxy
laminate material. Of course, other materials may be used to form
the chassis-less circuit board substrate 602 in other
embodiments.
[0041] As discussed in more detail below, the chassis-less circuit
board substrate 602 includes multiple features that improve the
thermal cooling characteristics of the various electrical
components mounted on the chassis-less circuit board substrate 602.
As discussed, the chassis-less circuit board substrate 602 does not
include a housing or enclosure, which may improve the airflow over
the electrical components of the sled 400 by reducing those
structures that may inhibit air flow. For example, because the
chassis-less circuit board substrate 602 is not positioned in an
individual housing or enclosure, there is no vertically-arranged
backplane (e.g., a backplate of the chassis) attached to the
chassis-less circuit board substrate 602, which could inhibit air
flow across the electrical components. Additionally, the
chassis-less circuit board substrate 602 has a geometric shape
configured to reduce the length of the airflow path across the
electrical components mounted to the chassis-less circuit board
substrate 602. For example, the illustrative chassis-less circuit
board substrate 602 has a width 604 that is greater than a depth
606 of the chassis-less circuit board substrate 602. In one
particular embodiment, for example, the chassis-less circuit board
substrate 602 has a width of about 21 inches and a depth of about 9
inches, compared to a typical server that has a width of about 17
inches and a depth of about 39 inches. As such, an airflow path 608
that extends from a front edge 610 of the chassis-less circuit
board substrate 602 toward a rear edge 612 has a shorter distance
relative to typical servers, which may improve the thermal cooling
characteristics of the sled 400. Furthermore, although not
illustrated in FIG. 6, the various physical resources mounted to
the chassis-less circuit board substrate 602 are mounted in
corresponding locations such that no two substantively
heat-producing electrical components shadow each other as discussed
in more detail below. That is, no two electrical components, which
produce appreciable heat during operation (i.e., greater than a
nominal heat sufficient enough to adversely impact the cooling of
another electrical component), are mounted to the chassis-less
circuit board substrate 602 linearly in-line with each other along
the direction of the airflow path 608 (i.e., along a direction
extending from the front edge 610 toward the rear edge 612 of the
chassis-less circuit board substrate 602).
[0042] As discussed above, the illustrative sled 400 includes one
or more physical resources 620 mounted to a top side 650 of the
chassis-less circuit board substrate 602. Although two physical
resources 620 are shown in FIG. 6, it should be appreciated that
the sled 400 may include one, two, or more physical resources 620
in other embodiments. The physical resources 620 may be embodied as
any type of processor, controller, or other compute circuit capable
of performing various tasks such as compute functions and/or
controlling the functions of the sled 400 depending on, for
example, the type or intended functionality of the sled 400. For
example, as discussed in more detail below, the physical resources
620 may be embodied as high-performance processors in embodiments
in which the sled 400 is embodied as a compute sled, as accelerator
co-processors or circuits in embodiments in which the sled 400 is
embodied as an accelerator sled, storage controllers in embodiments
in which the sled 400 is embodied as a storage sled, or a set of
memory devices in embodiments in which the sled 400 is embodied as
a memory sled.
[0043] The sled 400 also includes one or more additional physical
resources 630 mounted to the top side 650 of the chassis-less
circuit board substrate 602. In the illustrative embodiment, the
additional physical resources include a network interface
controller (NIC) as discussed in more detail below. Of course,
depending on the type and functionality of the sled 400, the
physical resources 630 may include additional or other electrical
components, circuits, and/or devices in other embodiments.
[0044] The physical resources 620 are communicatively coupled to
the physical resources 630 via an input/output (I/O) subsystem 622.
The I/O subsystem 622 may be embodied as circuitry and/or
components to facilitate input/output operations with the physical
resources 620, the physical resources 630, and/or other components
of the sled 400. For example, the I/O subsystem 622 may be embodied
as, or otherwise include, memory controller hubs, input/output
control hubs, integrated sensor hubs, firmware devices,
communication links (e.g., point-to-point links, bus links, wires,
cables, waveguides, light guides, printed circuit board traces,
etc.), and/or other components and subsystems to facilitate the
input/output operations. In the illustrative embodiment, the I/O
subsystem 622 is embodied as, or otherwise includes, a double data
rate 4 (DDR4) data bus or a DDR5 data bus.
[0045] In some embodiments, the sled 400 may also include a
resource-to-resource interconnect 624. The resource-to-resource
interconnect 624 may be embodied as any type of communication
interconnect capable of facilitating resource-to-resource
communications. In the illustrative embodiment, the
resource-to-resource interconnect 624 is embodied as a high-speed
point-to-point interconnect (e.g., faster than the I/O subsystem
622). For example, the resource-to-resource interconnect 624 may be
embodied as a QuickPath Interconnect (QPI), an UltraPath
Interconnect (UPI), or other high-speed point-to-point interconnect
dedicated to resource-to-resource communications.
[0046] The sled 400 also includes a power connector 640 configured
to mate with a corresponding power connector of the rack 240 when
the sled 400 is mounted in the corresponding rack 240. The sled 400
receives power from a power supply of the rack 240 via the power
connector 640 to supply power to the various electrical components
of the sled 400. That is, the sled 400 does not include any local
power supply (i.e., an on-board power supply) to provide power to
the electrical components of the sled 400. The exclusion of a local
or on-board power supply facilitates the reduction in the overall
footprint of the chassis-less circuit board substrate 602, which
may increase the thermal cooling characteristics of the various
electrical components mounted on the chassis-less circuit board
substrate 602 as discussed above. In some embodiments, voltage
regulators are placed on a bottom side 750 (see FIG. 7) of the
chassis-less circuit board substrate 602 directly opposite of the
processors 820 (see FIG. 8), and power is routed from the voltage
regulators to the processors 820 by vias extending through the
circuit board substrate 602. Such a configuration provides an
increased thermal budget, additional current and/or voltage, and
better voltage control relative to typical printed circuit boards
in which processor power is delivered from a voltage regulator, in
part, by printed circuit traces.
[0047] In some embodiments, the sled 400 may also include mounting
features 642 configured to mate with a mounting arm, or other
structure, of a robot to facilitate the placement of the sled 600
in a rack 240 by the robot. The mounting features 642 may be
embodied as any type of physical structures that allow the robot to
grasp the sled 400 without damaging the chassis-less circuit board
substrate 602 or the electrical components mounted thereto. For
example, in some embodiments, the mounting features 642 may be
embodied as non-conductive pads attached to the chassis-less
circuit board substrate 602. In other embodiments, the mounting
features may be embodied as brackets, braces, or other similar
structures attached to the chassis-less circuit board substrate
602. The particular number, shape, size, and/or make-up of the
mounting feature 642 may depend on the design of the robot
configured to manage the sled 400.
[0048] Referring now to FIG. 7, in addition to the physical
resources 630 mounted on the top side 650 of the chassis-less
circuit board substrate 602, the sled 400 also includes one or more
memory devices 720 mounted to a bottom side 750 of the chassis-less
circuit board substrate 602. That is, the chassis-less circuit
board substrate 602 is embodied as a double-sided circuit board.
The physical resources 620 are communicatively coupled to the
memory devices 720 via the I/O subsystem 622. For example, the
physical resources 620 and the memory devices 720 may be
communicatively coupled by one or more vias extending through the
chassis-less circuit board substrate 602. Each physical resource
620 may be communicatively coupled to a different set of one or
more memory devices 720 in some embodiments. Alternatively, in
other embodiments, each physical resource 620 may be
communicatively coupled to each memory device 720.
[0049] The memory devices 720 may be embodied as any type of memory
device capable of storing data for the physical resources 620
during operation of the sled 400, such as any type of volatile
(e.g., dynamic random access memory (DRAM), etc.) or non-volatile
memory. Volatile memory may be a storage medium that requires power
to maintain the state of data stored by the medium. Non-limiting
examples of volatile memory may include various types of random
access memory (RAM), such as dynamic random access memory (DRAM) or
static random access memory (SRAM). One particular type of DRAM
that may be used in a memory module is synchronous dynamic random
access memory (SDRAM). In particular embodiments, DRAM of a memory
component may comply with a standard promulgated by JEDEC, such as
JESD79F for DDR SDRAM, JESD79-2F for DDR2 SDRAM, JESD79-3F for DDR3
SDRAM, JESD79-4A for DDR4 SDRAM, JESD209 for Low Power DDR (LPDDR),
JESD209-2 for LPDDR2, JESD209-3 for LPDDR3, and JESD209-4 for
LPDDR4. Such standards (and similar standards) may be referred to
as DDR-based standards and communication interfaces of the storage
devices that implement such standards may be referred to as
DDR-based interfaces.
[0050] In one embodiment, the memory device is a block addressable
memory device, such as those based on NAND or NOR technologies. A
memory device may also include next-generation nonvolatile devices,
such as Intel 3D XPoint.TM. memory or other byte addressable
write-in-place nonvolatile memory devices. In one embodiment, the
memory device may be or may include memory devices that use
chalcogenide glass, multi-threshold level NAND flash memory, NOR
flash memory, single or multi-level Phase Change Memory (PCM), a
resistive memory, nanowire memory, ferroelectric transistor random
access memory (FeTRAM), anti-ferroelectric memory, magnetoresistive
random access memory (MRAM) memory that incorporates memristor
technology, resistive memory including the metal oxide base, the
oxygen vacancy base and the conductive bridge Random Access Memory
(CB-RAM), or spin transfer torque (STT)-MRAM, a spintronic magnetic
junction memory based device, a magnetic tunneling junction (MTJ)
based device, a DW (Domain Wall) and SOT (Spin Orbit Transfer)
based device, a thyristor based memory device, or a combination of
any of the above, or other memory. The memory device may refer to
the die itself and/or to a packaged memory product. In some
embodiments, the memory device may comprise a transistor-less
stackable cross point architecture in which memory cells sit at the
intersection of word lines and bit lines and are individually
addressable and in which bit storage is based on a change in bulk
resistance.
[0051] Referring now to FIG. 8, in some embodiments, the sled 400
may be embodied as a compute sled 800. The compute sled 800 is
optimized, or otherwise configured, to perform compute tasks. Of
course, as discussed above, the compute sled 800 may rely on other
sleds, such as acceleration sleds and/or storage sleds, to perform
such compute tasks. The compute sled 800 includes various physical
resources (e.g., electrical components) similar to the physical
resources of the sled 400, which have been identified in FIG. 8
using the same reference numbers. The description of such
components provided above in regard to FIGS. 6 and 7 applies to the
corresponding components of the compute sled 800 and is not
repeated herein for clarity of the description of the compute sled
800.
[0052] In the illustrative compute sled 800, the physical resources
620 are embodied as processors 820. Although only two processors
820 are shown in FIG. 8, it should be appreciated that the compute
sled 800 may include additional processors 820 in other
embodiments. Illustratively, the processors 820 are embodied as
high-performance processors 820 and may be configured to operate at
a relatively high power rating. Although the processors 820
generate additional heat operating at power ratings greater than
typical processors (which operate at around 155-230 W), the
enhanced thermal cooling characteristics of the chassis-less
circuit board substrate 602 discussed above facilitate the higher
power operation. For example, in the illustrative embodiment, the
processors 820 are configured to operate at a power rating of at
least 250 W. In some embodiments, the processors 820 may be
configured to operate at a power rating of at least 350 W.
[0053] In some embodiments, the compute sled 800 may also include a
processor-to-processor interconnect 842. Similar to the
resource-to-resource interconnect 624 of the sled 400 discussed
above, the processor-to-processor interconnect 842 may be embodied
as any type of communication interconnect capable of facilitating
processor-to-processor interconnect 842 communications. In the
illustrative embodiment, the processor-to-processor interconnect
842 is embodied as a high-speed point-to-point interconnect (e.g.,
faster than the I/O subsystem 622). For example, the
processor-to-processor interconnect 842 may be embodied as a
QuickPath Interconnect (QPI), an UltraPath Interconnect (UPI), or
other high-speed point-to-point interconnect dedicated to
processor-to-processor communications.
[0054] The compute sled 800 also includes a communication circuit
830. The illustrative communication circuit 830 includes a network
interface controller (NIC) 832, which may also be referred to as a
host fabric interface (HFI). The NIC 832 may be embodied as, or
otherwise include, any type of integrated circuit, discrete
circuits, controller chips, chipsets, add-in-boards, daughtercards,
network interface cards, or other devices that may be used by the
compute sled 800 to connect with another compute device (e.g., with
other sleds 400). In some embodiments, the NIC 832 may be embodied
as part of a system-on-a-chip (SoC) that includes one or more
processors, or included on a multichip package that also contains
one or more processors. In some embodiments, the NIC 832 may
include a local processor (not shown) and/or a local memory (not
shown) that are both local to the NIC 832. In such embodiments, the
local processor of the NIC 832 may be capable of performing one or
more of the functions of the processors 820. Additionally or
alternatively, in such embodiments, the local memory of the NIC 832
may be integrated into one or more components of the compute sled
at the board level, socket level, chip level, and/or other
levels.
[0055] The communication circuit 830 is communicatively coupled to
an optical data connector 834. The optical data connector 834 is
configured to mate with a corresponding optical data connector of
the rack 240 when the compute sled 800 is mounted in the rack 240.
Illustratively, the optical data connector 834 includes a plurality
of optical fibers which lead from a mating surface of the optical
data connector 834 to an optical transceiver 836. The optical
transceiver 836 is configured to convert incoming optical signals
from the rack-side optical data connector to electrical signals and
to convert electrical signals to outgoing optical signals to the
rack-side optical data connector. Although shown as forming part of
the optical data connector 834 in the illustrative embodiment, the
optical transceiver 836 may form a portion of the communication
circuit 830 in other embodiments.
[0056] In some embodiments, the compute sled 800 may also include
an expansion connector 840. In such embodiments, the expansion
connector 840 is configured to mate with a corresponding connector
of an expansion chassis-less circuit board substrate to provide
additional physical resources to the compute sled 800. The
additional physical resources may be used, for example, by the
processors 820 during operation of the compute sled 800. The
expansion chassis-less circuit board substrate may be substantially
similar to the chassis-less circuit board substrate 602 discussed
above and may include various electrical components mounted
thereto. The particular electrical components mounted to the
expansion chassis-less circuit board substrate may depend on the
intended functionality of the expansion chassis-less circuit board
substrate. For example, the expansion chassis-less circuit board
substrate may provide additional compute resources, memory
resources, and/or storage resources. As such, the additional
physical resources of the expansion chassis-less circuit board
substrate may include, but is not limited to, processors, memory
devices, storage devices, and/or accelerator circuits including,
for example, field programmable gate arrays (FPGA),
application-specific integrated circuits (ASICs), security
co-processors, graphics processing units (GPUs), machine learning
circuits, or other specialized processors, controllers, devices,
and/or circuits.
[0057] Referring now to FIG. 9, an illustrative embodiment of the
compute sled 800 is shown. As shown, the processors 820,
communication circuit 830, and optical data connector 834 are
mounted to the top side 650 of the chassis-less circuit board
substrate 602. Any suitable attachment or mounting technology may
be used to mount the physical resources of the compute sled 800 to
the chassis-less circuit board substrate 602. For example, the
various physical resources may be mounted in corresponding sockets
(e.g., a processor socket), holders, or brackets. In some cases,
some of the electrical components may be directly mounted to the
chassis-less circuit board substrate 602 via soldering or similar
techniques.
[0058] As discussed above, the individual processors 820 and
communication circuit 830 are mounted to the top side 650 of the
chassis-less circuit board substrate 602 such that no two
heat-producing, electrical components shadow each other. In the
illustrative embodiment, the processors 820 and communication
circuit 830 are mounted in corresponding locations on the top side
650 of the chassis-less circuit board substrate 602 such that no
two of those physical resources are linearly in-line with others
along the direction of the airflow path 608. It should be
appreciated that, although the optical data connector 834 is
in-line with the communication circuit 830, the optical data
connector 834 produces no or nominal heat during operation.
[0059] The memory devices 720 of the compute sled 800 are mounted
to the bottom side 750 of the of the chassis-less circuit board
substrate 602 as discussed above in regard to the sled 400.
Although mounted to the bottom side 750, the memory devices 720 are
communicatively coupled to the processors 820 located on the top
side 650 via the I/O subsystem 622. Because the chassis-less
circuit board substrate 602 is embodied as a double-sided circuit
board, the memory devices 720 and the processors 820 may be
communicatively coupled by one or more vias, connectors, or other
mechanisms extending through the chassis-less circuit board
substrate 602. Of course, each processor 820 may be communicatively
coupled to a different set of one or more memory devices 720 in
some embodiments. Alternatively, in other embodiments, each
processor 820 may be communicatively coupled to each memory device
720. In some embodiments, the memory devices 720 may be mounted to
one or more memory mezzanines on the bottom side of the
chassis-less circuit board substrate 602 and may interconnect with
a corresponding processor 820 through a ball-grid array.
[0060] Each of the processors 820 includes a heatsink 850 secured
thereto. Due to the mounting of the memory devices 720 to the
bottom side 750 of the chassis-less circuit board substrate 602 (as
well as the vertical spacing of the sleds 400 in the corresponding
rack 240), the top side 650 of the chassis-less circuit board
substrate 602 includes additional "free" area or space that
facilitates the use of heatsinks 850 having a larger size relative
to traditional heatsinks used in typical servers. Additionally, due
to the improved thermal cooling characteristics of the chassis-less
circuit board substrate 602, none of the processor heatsinks 850
include cooling fans attached thereto. That is, each of the
heatsinks 850 is embodied as a fan-less heatsink. In some
embodiments, the heat sinks 850 mounted atop the processors 820 may
overlap with the heat sink attached to the communication circuit
830 in the direction of the airflow path 608 due to their increased
size, as illustratively suggested by FIG. 9.
[0061] Referring now to FIG. 10, in some embodiments, the sled 400
may be embodied as an accelerator sled 1000. The accelerator sled
1000 is configured, to perform specialized compute tasks, such as
machine learning, encryption, hashing, or other
computational-intensive task. In some embodiments, for example, a
compute sled 800 may offload tasks to the accelerator sled 1000
during operation. The accelerator sled 1000 includes various
components similar to components of the sled 400 and/or compute
sled 800, which have been identified in FIG. 10 using the same
reference numbers. The description of such components provided
above in regard to FIGS. 6, 7, and 8 apply to the corresponding
components of the accelerator sled 1000 and is not repeated herein
for clarity of the description of the accelerator sled 1000.
[0062] In the illustrative accelerator sled 1000, the physical
resources 620 are embodied as accelerator circuits 1020. Although
only two accelerator circuits 1020 are shown in FIG. 10, it should
be appreciated that the accelerator sled 1000 may include
additional accelerator circuits 1020 in other embodiments. For
example, as shown in FIG. 11, the accelerator sled 1000 may include
four accelerator circuits 1020 in some embodiments. The accelerator
circuits 1020 may be embodied as any type of processor,
co-processor, compute circuit, or other device capable of
performing compute or processing operations. For example, the
accelerator circuits 1020 may be embodied as, for example, field
programmable gate arrays (FPGA), application-specific integrated
circuits (ASICs), security co-processors, graphics processing units
(GPUs), neuromorphic processor units, quantum computers, machine
learning circuits, or other specialized processors, controllers,
devices, and/or circuits.
[0063] In some embodiments, the accelerator sled 1000 may also
include an accelerator-to-accelerator interconnect 1042. Similar to
the resource-to-resource interconnect 624 of the sled 600 discussed
above, the accelerator-to-accelerator interconnect 1042 may be
embodied as any type of communication interconnect capable of
facilitating accelerator-to-accelerator communications. In the
illustrative embodiment, the accelerator-to-accelerator
interconnect 1042 is embodied as a high-speed point-to-point
interconnect (e.g., faster than the I/O subsystem 622). For
example, the accelerator-to-accelerator interconnect 1042 may be
embodied as a QuickPath Interconnect (QPI), an UltraPath
Interconnect (UPI), or other high-speed point-to-point interconnect
dedicated to processor-to-processor communications. In some
embodiments, the accelerator circuits 1020 may be daisy-chained
with a primary accelerator circuit 1020 connected to the NIC 832
and memory 720 through the I/O subsystem 622 and a secondary
accelerator circuit 1020 connected to the NIC 832 and memory 720
through a primary accelerator circuit 1020.
[0064] Referring now to FIG. 11, an illustrative embodiment of the
accelerator sled 1000 is shown. As discussed above, the accelerator
circuits 1020, communication circuit 830, and optical data
connector 834 are mounted to the top side 650 of the chassis-less
circuit board substrate 602. Again, the individual accelerator
circuits 1020 and communication circuit 830 are mounted to the top
side 650 of the chassis-less circuit board substrate 602 such that
no two heat-producing, electrical components shadow each other as
discussed above. The memory devices 720 of the accelerator sled
1000 are mounted to the bottom side 750 of the of the chassis-less
circuit board substrate 602 as discussed above in regard to the
sled 600. Although mounted to the bottom side 750, the memory
devices 720 are communicatively coupled to the accelerator circuits
1020 located on the top side 650 via the I/O subsystem 622 (e.g.,
through vias). Further, each of the accelerator circuits 1020 may
include a heatsink 1070 that is larger than a traditional heatsink
used in a server. As discussed above with reference to the
heatsinks 870, the heatsinks 1070 may be larger than traditional
heatsinks because of the "free" area provided by the memory
resources 720 being located on the bottom side 750 of the
chassis-less circuit board substrate 602 rather than on the top
side 650.
[0065] Referring now to FIG. 12, in some embodiments, the sled 400
may be embodied as a storage sled 1200. The storage sled 1200 is
configured, to store data in a data storage 1250 local to the
storage sled 1200. For example, during operation, a compute sled
800 or an accelerator sled 1000 may store and retrieve data from
the data storage 1250 of the storage sled 1200. The storage sled
1200 includes various components similar to components of the sled
400 and/or the compute sled 800, which have been identified in FIG.
12 using the same reference numbers. The description of such
components provided above in regard to FIGS. 6, 7, and 8 apply to
the corresponding components of the storage sled 1200 and is not
repeated herein for clarity of the description of the storage sled
1200.
[0066] In the illustrative storage sled 1200, the physical
resources 620 are embodied as storage controllers 1220. Although
only two storage controllers 1220 are shown in FIG. 12, it should
be appreciated that the storage sled 1200 may include additional
storage controllers 1220 in other embodiments. The storage
controllers 1220 may be embodied as any type of processor,
controller, or control circuit capable of controlling the storage
and retrieval of data into the data storage 1250 based on requests
received via the communication circuit 830. In the illustrative
embodiment, the storage controllers 1220 are embodied as relatively
low-power processors or controllers. For example, in some
embodiments, the storage controllers 1220 may be configured to
operate at a power rating of about 75 watts.
[0067] In some embodiments, the storage sled 1200 may also include
a controller-to-controller interconnect 1242. Similar to the
resource-to-resource interconnect 624 of the sled 400 discussed
above, the controller-to-controller interconnect 1242 may be
embodied as any type of communication interconnect capable of
facilitating controller-to-controller communications. In the
illustrative embodiment, the controller-to-controller interconnect
1242 is embodied as a high-speed point-to-point interconnect (e.g.,
faster than the I/O subsystem 622). For example, the
controller-to-controller interconnect 1242 may be embodied as a
QuickPath Interconnect (QPI), an UltraPath Interconnect (UPI), or
other high-speed point-to-point interconnect dedicated to
processor-to-processor communications.
[0068] Referring now to FIG. 13, an illustrative embodiment of the
storage sled 1200 is shown. In the illustrative embodiment, the
data storage 1250 is embodied as, or otherwise includes, a storage
cage 1252 configured to house one or more solid state drives (SSDs)
1254. To do so, the storage cage 1252 includes a number of mounting
slots 1256, each of which is configured to receive a corresponding
solid state drive 1254. Each of the mounting slots 1256 includes a
number of drive guides 1258 that cooperate to define an access
opening 1260 of the corresponding mounting slot 1256. The storage
cage 1252 is secured to the chassis-less circuit board substrate
602 such that the access openings face away from (i.e., toward the
front of) the chassis-less circuit board substrate 602. As such,
solid state drives 1254 are accessible while the storage sled 1200
is mounted in a corresponding rack 204. For example, a solid state
drive 1254 may be swapped out of a rack 240 (e.g., via a robot)
while the storage sled 1200 remains mounted in the corresponding
rack 240.
[0069] The storage cage 1252 illustratively includes sixteen
mounting slots 1256 and is capable of mounting and storing sixteen
solid state drives 1254. Of course, the storage cage 1252 may be
configured to store additional or fewer solid state drives 1254 in
other embodiments. Additionally, in the illustrative embodiment,
the solid state drivers are mounted vertically in the storage cage
1252, but may be mounted in the storage cage 1252 in a different
orientation in other embodiments. Each solid state drive 1254 may
be embodied as any type of data storage device capable of storing
long term data. To do so, the solid state drives 1254 may include
volatile and non-volatile memory devices discussed above.
[0070] As shown in FIG. 13, the storage controllers 1220, the
communication circuit 830, and the optical data connector 834 are
illustratively mounted to the top side 650 of the chassis-less
circuit board substrate 602. Again, as discussed above, any
suitable attachment or mounting technology may be used to mount the
electrical components of the storage sled 1200 to the chassis-less
circuit board substrate 602 including, for example, sockets (e.g.,
a processor socket), holders, brackets, soldered connections,
and/or other mounting or securing techniques.
[0071] As discussed above, the individual storage controllers 1220
and the communication circuit 830 are mounted to the top side 650
of the chassis-less circuit board substrate 602 such that no two
heat-producing, electrical components shadow each other. For
example, the storage controllers 1220 and the communication circuit
830 are mounted in corresponding locations on the top side 650 of
the chassis-less circuit board substrate 602 such that no two of
those electrical components are linearly in-line with each other
along the direction of the airflow path 608.
[0072] The memory devices 720 of the storage sled 1200 are mounted
to the bottom side 750 of the of the chassis-less circuit board
substrate 602 as discussed above in regard to the sled 400.
Although mounted to the bottom side 750, the memory devices 720 are
communicatively coupled to the storage controllers 1220 located on
the top side 650 via the I/O subsystem 622. Again, because the
chassis-less circuit board substrate 602 is embodied as a
double-sided circuit board, the memory devices 720 and the storage
controllers 1220 may be communicatively coupled by one or more
vias, connectors, or other mechanisms extending through the
chassis-less circuit board substrate 602. Each of the storage
controllers 1220 includes a heatsink 1270 secured thereto. As
discussed above, due to the improved thermal cooling
characteristics of the chassis-less circuit board substrate 602 of
the storage sled 1200, none of the heatsinks 1270 include cooling
fans attached thereto. That is, each of the heatsinks 1270 is
embodied as a fan-less heatsink.
[0073] Referring now to FIG. 14, in some embodiments, the sled 400
may be embodied as a memory sled 1400. The storage sled 1400 is
optimized, or otherwise configured, to provide other sleds 400
(e.g., compute sleds 800, accelerator sleds 1000, etc.) with access
to a pool of memory (e.g., in two or more sets 1430, 1432 of memory
devices 720) local to the memory sled 1200. For example, during
operation, a compute sled 800 or an accelerator sled 1000 may
remotely write to and/or read from one or more of the memory sets
1430, 1432 of the memory sled 1200 using a logical address space
that maps to physical addresses in the memory sets 1430, 1432. The
memory sled 1400 includes various components similar to components
of the sled 400 and/or the compute sled 800, which have been
identified in FIG. 14 using the same reference numbers. The
description of such components provided above in regard to FIGS. 6,
7, and 8 apply to the corresponding components of the memory sled
1400 and is not repeated herein for clarity of the description of
the memory sled 1400.
[0074] In the illustrative memory sled 1400, the physical resources
620 are embodied as memory controllers 1420. Although only two
memory controllers 1420 are shown in FIG. 14, it should be
appreciated that the memory sled 1400 may include additional memory
controllers 1420 in other embodiments. The memory controllers 1420
may be embodied as any type of processor, controller, or control
circuit capable of controlling the writing and reading of data into
the memory sets 1430, 1432 based on requests received via the
communication circuit 830. In the illustrative embodiment, each
memory controller 1420 is connected to a corresponding memory set
1430, 1432 to write to and read from memory devices 720 within the
corresponding memory set 1430, 1432 and enforce any permissions
(e.g., read, write, etc.) associated with sled 400 that has sent a
request to the memory sled 1400 to perform a memory access
operation (e.g., read or write).
[0075] In some embodiments, the memory sled 1400 may also include a
controller-to-controller interconnect 1442. Similar to the
resource-to-resource interconnect 624 of the sled 400 discussed
above, the controller-to-controller interconnect 1442 may be
embodied as any type of communication interconnect capable of
facilitating controller-to-controller communications. In the
illustrative embodiment, the controller-to-controller interconnect
1442 is embodied as a high-speed point-to-point interconnect (e.g.,
faster than the I/O subsystem 622). For example, the
controller-to-controller interconnect 1442 may be embodied as a
QuickPath Interconnect (QPI), an UltraPath Interconnect (UPI), or
other high-speed point-to-point interconnect dedicated to
processor-to-processor communications. As such, in some
embodiments, a memory controller 1420 may access, through the
controller-to-controller interconnect 1442, memory that is within
the memory set 1432 associated with another memory controller 1420.
In some embodiments, a scalable memory controller is made of
multiple smaller memory controllers, referred to herein as
"chiplets", on a memory sled (e.g., the memory sled 1400). The
chiplets may be interconnected (e.g., using EMIB (Embedded
Multi-Die Interconnect Bridge)). The combined chiplet memory
controller may scale up to a relatively large number of memory
controllers and I/O ports, (e.g., up to 16 memory channels). In
some embodiments, the memory controllers 1420 may implement a
memory interleave (e.g., one memory address is mapped to the memory
set 1430, the next memory address is mapped to the memory set 1432,
and the third address is mapped to the memory set 1430, etc.). The
interleaving may be managed within the memory controllers 1420, or
from CPU sockets (e.g., of the compute sled 800) across network
links to the memory sets 1430, 1432, and may improve the latency
associated with performing memory access operations as compared to
accessing contiguous memory addresses from the same memory
device.
[0076] Further, in some embodiments, the memory sled 1400 may be
connected to one or more other sleds 400 (e.g., in the same rack
240 or an adjacent rack 240) through a waveguide, using the
waveguide connector 1480. In the illustrative embodiment, the
waveguides are 64 millimeter waveguides that provide 16 Rx (i.e.,
receive) lanes and 16 Tx (i.e., transmit) lanes. Each lane, in the
illustrative embodiment, is either 16 GHz or 32 GHz. In other
embodiments, the frequencies may be different. Using a waveguide
may provide high throughput access to the memory pool (e.g., the
memory sets 1430, 1432) to another sled (e.g., a sled 400 in the
same rack 240 or an adjacent rack 240 as the memory sled 1400)
without adding to the load on the optical data connector 834.
[0077] Referring now to FIG. 15, a system for executing one or more
workloads (e.g., applications) may be implemented in accordance
with the data center 100. In the illustrative embodiment, the
system 1510 includes an orchestrator server 1520, which may be
embodied as a managed node comprising a compute device (e.g., a
processor 820 on a compute sled 800) executing management software
(e.g., a cloud operating environment, such as OpenStack) that is
communicatively coupled to multiple sleds 400 including a large
number of compute sleds 1530 (e.g., each similar to the compute
sled 800), memory sleds 1540 (e.g., each similar to the memory sled
1400), accelerator sleds 1550 (e.g., each similar to the memory
sled 1000), and storage sleds 1560 (e.g., each similar to the
storage sled 1200). One or more of the sleds 1530, 1540, 1550, 1560
may be grouped into a managed node 1570, such as by the
orchestrator server 1520, to collectively perform a workload (e.g.,
an application 1532 executed in a virtual machine or in a
container). The managed node 1570 may be embodied as an assembly of
physical resources 620, such as processors 820, memory resources
720, accelerator circuits 1020, or data storage 1250, from the same
or different sleds 400. Further, the managed node may be
established, defined, or "spun up" by the orchestrator server 1520
at the time a workload is to be assigned to the managed node or at
any other time, and may exist regardless of whether any workloads
are presently assigned to the managed node. In the illustrative
embodiment, the orchestrator server 1520 may selectively allocate
and/or deallocate physical resources 620 from the sleds 400 and/or
add or remove one or more sleds 400 from the managed node 1570 as a
function of quality of service (QoS) targets (e.g., performance
targets associated with a throughput, latency, instructions per
second, etc.) associated with a service level agreement for the
workload (e.g., the application 1532). In doing so, the
orchestrator server 1520 may receive telemetry data indicative of
performance conditions (e.g., throughput, latency, instructions per
second, etc.) in each sled 400 of the managed node 1570 and compare
the telemetry data to the quality of service targets to determine
whether the quality of service targets are being satisfied. The
orchestrator server 1520 may additionally determine whether one or
more physical resources may be deallocated from the managed node
1570 while still satisfying the QoS targets, thereby freeing up
those physical resources for use in another managed node (e.g., to
execute a different workload). Alternatively, if the QoS targets
are not presently satisfied, the orchestrator server 1520 may
determine to dynamically allocate additional physical resources to
assist in the execution of the workload (e.g., the application
1532) while the workload is executing. Similarly, the orchestrator
server 1520 may determine to dynamically deallocate physical
resources from a managed node if the orchestrator server 1520
determines that deallocating the physical resource would result in
QoS targets still being met.
[0078] Additionally, in some embodiments, the orchestrator server
1520 may identify trends in the resource utilization of the
workload (e.g., the application 1532), such as by identifying
phases of execution (e.g., time periods in which different
operations, each having different resource utilizations
characteristics, are performed) of the workload (e.g., the
application 1532) and pre-emptively identifying available resources
in the data center 100 and allocating them to the managed node 1570
(e.g., within a predefined time period of the associated phase
beginning). In some embodiments, the orchestrator server 1520 may
model performance based on various latencies and a distribution
scheme to place workloads among compute sleds and other resources
(e.g., accelerator sleds, memory sleds, storage sleds) in the data
center 100. For example, the orchestrator server 1520 may utilize a
model that accounts for the performance of resources on the sleds
400 (e.g., FPGA performance, memory access latency, etc.) and the
performance (e.g., congestion, latency, bandwidth) of the path
through the network to the resource (e.g., FPGA). As such, the
orchestrator server 1520 may determine which resource(s) should be
used with which workloads based on the total latency associated
with each potential resource available in the data center 100
(e.g., the latency associated with the performance of the resource
itself in addition to the latency associated with the path through
the network between the compute sled executing the workload and the
sled 400 on which the resource is located).
[0079] In some embodiments, the orchestrator server 1520 may
generate a map of heat generation in the data center 100 using
telemetry data (e.g., temperatures, fan speeds, etc.) reported from
the sleds 400 and allocate resources to managed nodes as a function
of the map of heat generation and predicted heat generation
associated with different workloads, to maintain a target
temperature and heat distribution in the data center 100.
Additionally or alternatively, in some embodiments, the
orchestrator server 1520 may organize received telemetry data into
a hierarchical model that is indicative of a relationship between
the managed nodes (e.g., a spatial relationship such as the
physical locations of the resources of the managed nodes within the
data center 100 and/or a functional relationship, such as groupings
of the managed nodes by the customers the managed nodes provide
services for, the types of functions typically performed by the
managed nodes, managed nodes that typically share or exchange
workloads among each other, etc.). Based on differences in the
physical locations and resources in the managed nodes, a given
workload may exhibit different resource utilizations (e.g., cause a
different internal temperature, use a different percentage of
processor or memory capacity) across the resources of different
managed nodes. The orchestrator server 1520 may determine the
differences based on the telemetry data stored in the hierarchical
model and factor the differences into a prediction of future
resource utilization of a workload if the workload is reassigned
from one managed node to another managed node, to accurately
balance resource utilization in the data center 100.
[0080] To reduce the computational load on the orchestrator server
1520 and the data transfer load on the network, in some
embodiments, the orchestrator server 1520 may send self-test
information to the sleds 400 to enable each sled 400 to locally
(e.g., on the sled 400) determine whether telemetry data generated
by the sled 400 satisfies one or more conditions (e.g., an
available capacity that satisfies a predefined threshold, a
temperature that satisfies a predefined threshold, etc.). Each sled
400 may then report back a simplified result (e.g., yes or no) to
the orchestrator server 1520, which the orchestrator server 1520
may utilize in determining the allocation of resources to managed
nodes.
[0081] Referring now to FIG. 16, a system 1610 for providing
distributed storage with physically separated control plane
management and data plane management in a disaggregated
architecture includes an orchestrator server 1620 similar to the
orchestrator server 1520, in communication with multiple sleds
1616, including a compute sled 1630 that executes an application
1650 (e.g., a workload), similar to the application 1532, on behalf
of a client device 1614. The system 1610 additionally includes
multiple compute sleds 1632, 1634, 1636 that make up
compute-focused portions of a distributed storage system (e.g.,
software defined storage servers, replication servers, object
storage daemons, etc.), and data storage sleds 1640, 1642, 1644
that form data storage-focused portions of the distributed storage
system. Each compute sled 1632, 1634, 1636 operates a control plane
manager 1660, which may be embodied as any circuitry or logic
(e.g., a co-processor, an ASIC, software, etc.) capable of
performing control plane management operations, such as placement
grouping, logical storage pooling, and failure domain mapping
functions, to determine which data storage sleds 1640, 1642, 1644
are to store a data set, referred to herein as an object. In doing
so, the control plane manager 1660 may produce a hash of the data
set and compare the hash to a database that relates hashes to
partitions (e.g., compute sleds and their corresponding data
storage sleds) of the distributed storage system. Further, in
performing the control plane management operations, the control
plane manager (e.g., the control plane manager 1660), in the
illustrative embodiment, causes an object to be stored across
multiple failure domains 1690, 1692, 1694 (e.g., to guard against
inaccessibility of the object if a power failure occurs in a
failure domains). Each failure domain 1690, 1692, 1694 may be
embodied as any physical grouping of compute devices (e.g., sleds
1616) and associated infrastructure, that may become inoperative
(e.g., due to a loss of power) without affecting the availability
of devices and infrastructure in other failure domains.
[0082] In the illustrative embodiment, data plane management
operations (e.g., block allocation, fragmentation management, wear
leveling, etc.), which are typically performed by the same compute
device that performs the control plane management operations, are
decoupled from the compute sleds 1632, 1634, 1636 and, instead, are
performed by data plane managers 1670, 1672, 1674, each of which
may be embodied as any circuitry or logic (e.g., a co-processor, an
ASIC, software, etc. capable of performing data plane operations,
on the same sled (e.g., the data storage sled(s)) where an object
is actually written to and/or read from physical storage media
(e.g., the data storage devices 1680, 1682, 1684, which are similar
to the data storage 1250 of FIG. 12). As such, the control plane
management operations, which may be compute intensive, are confined
to the compute sleds 1632, 1634, 1636, which are relatively better
equipped to perform compute-intensive tasks, while the data plane
management operations, which pertain to management of the physical
storage media, are kept local to the corresponding data storage
sleds 1640, 1642, 1644 where the data storage devices 1680, 1682,
1684 are physically located, resulting in significant improvements
in efficiency over typical distributed data storage systems.
[0083] The orchestrator server 1620, the sleds 1616, and the client
device 1614 are illustratively in communication via a network 1612,
which may be embodied as any type of wired or wireless
communication network, including global networks (e.g., the
Internet), local area networks (LANs) or wide area networks (WANs),
cellular networks (e.g., Global System for Mobile Communications
(GSM), 3G, Long Term Evolution (LTE), Worldwide Interoperability
for Microwave Access (WiMAX), etc.), digital subscriber line (DSL)
networks, cable networks (e.g., coaxial networks, fiber networks,
etc.), or any combination thereof.
[0084] Referring now to FIG. 17, the compute sled 1632, in
operation, may execute a method 1700 for executing control plane
operations in response to a data access request (e.g., to store an
object or to read an object from distributed storage). The method
1700 begins with block 1702, in which the compute sled 1632
receives a data access request. In the illustrative embodiment, the
compute sled 1632 receives the data access request (e.g., a PUT
request or a GET request from a representational state transfer
(REST) application programming interface (API)), from the
application 1650 executed by the compute sled 1630, as indicated in
block 1704. As indicated in block 1706, the compute sled 1632 may
obtain a write request (e.g., a PUT request, as stated above). In
receiving a write request, the compute sled 1632 may receive, from
the requesting compute device (e.g., the compute sled 1630) a data
payload (e.g., a data set) indicative of the object to be stored,
as indicated in block 1708. Alternatively, the compute sled 1632
may receive a read request (e.g., a GET request, as stated above),
as indicated in block 1710. The data access request may include an
object identifier, which may be any sequence of characters,
numbers, or other symbols that identify the object to be stored or
read, as indicated in block 1712. Subsequently, in block 1714, the
compute sled 1632 determines the subsequent course of action as a
function of whether the data access request is a write request.
[0085] If the compute sled 1632 determines that the data access
request is a write request, the method 1700 advances to block 1716,
in which the compute sled 1632 verifies that the data payload
represents an unstored object (e.g., an object that is not already
stored in the distributed storage system). In doing so, the compute
sled 1632 may produce an object identifier from a uniform resource
locator (URL) of the object (e.g., by performing a hashing function
on the URL), as indicated in block 1718. If the write request
received in block 1702 included an object identifier, the compute
sled 1632 may skip the production of an object identifier in block
1716. In block 1720, the compute sled 1632 determines whether the
object identifier corresponds to a stored object. In doing so, the
compute sled 1632, in the illustrative embodiment, compares the
object identifier to a database (e.g., in the memory 720) of object
identifiers for objects stored in its data storage sled 1640, as
indicated in block 1722. In block 1724, the compute sled 1632
determines the subsequent course of action as a function of whether
the payload represents an unstored object (e.g., whether the
payload identifier matches an object identifier of an object that
is already stored in one or more of the data storage sleds 1640,
1642, 1644). If the data payload does not represent an unstored
object (e.g., the object identifier matches the object identifier
or an already-stored object), the method 1700 advances to block
1726, in which the compute sled 1632 sends a response message
(e.g., to the compute sled 1630) that the object is already stored.
In doing so, the compute sled 1632 may add the object identifier to
the response message, as indicated in block 1728. Subsequently, the
method 1700 loops back to block 1702 in which the compute sled 1632
awaits another data access request. Otherwise, if the object is not
already stored, the method 1700 advances to block 1730 of FIG. 18,
in which the compute sled 1632 maps the object to a set of data
storage sleds (e.g., the data storage sleds 1640, 1642, 1644). In
some embodiments, the compute sled 1632 may skip the verification
of whether the object identifier matches an already-stored object
and proceed on the basis that any such object will be overwritten
by the new object having the same object identifier.
[0086] Referring now to FIG. 18, in mapping the object to a set of
data storage sleds, the compute sled 1632 may map the object as a
function of the object identifier, as indicated in block 1732. For
example, in cases in which the object identifier is a hash
associated with the object (e.g., a hash of the URL of the object),
the compute sled 1632 may map the object to a set of data storage
sleds as a function of the hash (e.g., using a table that
associates hashes, or portions of hashes, with data storage sleds),
as indicated in block 1734. As indicated in block 1736, the compute
sled 1632, in the illustrative embodiment, maps the object to data
storage sleds in different failure domains (e.g., the data storage
sleds 1640, 1642, 1644 in corresponding failure domains 1690, 1692,
1694). As indicated in block 1738, the compute sled 1632 maps the
object to a set of data storage sleds that are to store
corresponding replicas (e.g., copies) or erasure coded sections of
the object. Additionally, as indicated in block 1740, the compute
sled 1632 may associate, in a database, the object identifier with
the data storage sleds that the object has been mapped to (e.g., by
identifying the counterpart compute sleds 1634, 1636 that will own
the object and identifying the corresponding data storage sleds
1642, 1644 of those counterpart compute sleds).
[0087] In block 1742, the compute sled 1632 may send metadata
associated with the object to other compute sleds with control
plane managers (e.g., the compute sleds 1634, 1636 with control
plane managers 1662, 1664) associated with the mapped data storage
sleds (e.g., the data storage sleds 1642, 1644). In doing so, the
compute sled 1632 may send the object identifier to the compute
sleds 1634, 1636, as indicated in block 1744. Further, the compute
sled 1632 may send metadata indicative of one or more attributes of
the object (e.g., a data type of the object, such as an image, a
video, or other data type, the size of the object, and/or other
attributes), as indicated in block 1748.
[0088] In block 1750, the compute sled 1632, in the illustrative
embodiment, sends a write request to the mapped data storage sleds
1640, 1642, 1644 using a local bus protocol that is mapped onto a
network protocol. As indicated in block 1752, in sending the write
request, the compute sled 1632 sends the object (e.g., the data
payload) and the object identifier to the mapped data storage sleds
1640, 1642, 1644. In the illustrative embodiment, in sending the
write request with a local bus protocol mapped onto a network
protocol, the compute sled 1632 tunnels the write request through a
non-volatile memory express over fabric (NVMeOF) connection, as
indicated in block 1754. For example, the compute sled 1632 may
send the write request to one or more block devices that are
exposed by an NVMeOF driver of the compute sled 1632 and that are
associated with (e.g., represent) the mapped data storage sleds
1640, 1642, 1644, as indicated in block 1756. As such, the compute
sled 1632, in the illustrative embodiment, operates as an NVMeOF
initiator and each data storage sled 1640, 1642, 1644 operates as
an NVMeOF target. In some embodiments, the compute sled 1632 may
send the write request to one or more data storage sleds located in
a different rack, pod, or data center than the compute sled 1632,
as indicated in block 1758.
[0089] Referring back to block 1714 of FIG. 17, if the compute sled
1632 instead determines that the data access request is not a write
request (e.g., the data access request is a read request), the
method 1700 advances to block 1760 of FIG. 19, in which the compute
sled 1632 determines a set of data storage sleds that are mapped to
the object identifier included in the data access request. In doing
so, the compute sled 1632 may compare the object identifier to a
database of object identifiers for objects stored in one or more of
the data storage sleds 1640, 1642, 1644 (e.g., the database
referenced in block 1722 of FIG. 17), as indicated in block 1762.
Subsequently, the method 1700 advances to block 1764 in which the
compute sled 1632 sends a read request to one or more of the mapped
data storage sleds 1640, 1642, 1644. In doing so, the compute sled
1632 sends the object identifier to one or more of the mapped data
storage sleds 1640, 1642, 1644, as indicated in block 1766. In the
illustrative embodiment, in sending the read request, the compute
sled 1632 tunnels the read request through NVMeOF to one or more of
the mapped data storage sleds 1640, 1642, 1644, as indicated in
block 1768. For example, and as indicated in block 1770, the
compute sled 1632 may send the read request to one or more block
devices exposed by an NVMEOF driver of the compute sled 1632 and
that are associated with the mapped data storage sleds 1640, 1642,
1644. As indicated in block 1772, the compute sled 1632 may send
the read request to one or more data storage sleds located in a
different rack, pod, or data center than the compute sled 1632.
Subsequently, in block 1774, the compute sled 1632 receives the
read object from one or more of the data storage sleds 1640, 1642,
1644. In doing so, in the illustrative embodiment, the compute sled
1632 receives the object through an NVMEoF connection between the
data storage sled (e.g., the data storage sled 1640) and the
compute sled 1632, as indicated in block 1776. In some embodiments,
the compute sled 1632 may receive erasure coded sections of the
object from the data storage sleds 1640, 1642, 1644 to be combined
to produce the object, as indicated in block 1778. Subsequently,
the method 1700 advances to block 1780, in which the compute sled
1632 sends the object to the requesting compute device. For
example, and as indicated in block 1782, the compute sled 1632
sends the object to the compute sled 1630 executing the application
1650.
[0090] Referring now to FIG. 20, a data storage sled (e.g., the
data storage sled 1640) may execute a method 2000 for executing
data plane management operations in response to a data access
request. The method 2000 begins with block 2002, in which the data
storage sled 1640 determines whether a data access request (e.g., a
write request or a read request from a compute sled, such as the
compute sled 1632) has been received. If so, the method 2000
advances to block 2004, in which the data storage sled 1640
determines the subsequent course of action as a function of whether
the data access request is a write request or not. In response to a
determination that the data access request is a write request, the
method 2000 advances to block 2006, in which the data storage sled
1632 determines one or more blocks of the data storage devices 1680
to write the object to. Each block may be embodied as any fixed
amount of data storage capacity (e.g., a gigabyte, a megabyte, a
kilobyte, one byte, etc.). In doing so, the data storage sled 1640
may determine the one or more blocks as a function of the object
identifier (e.g., by using a portion of the object identifier as a
logical block address), as indicated in block 2008. Additionally or
alternatively, the data storage sled 1640 may determine the one or
more blocks as a function of a fragmentation management scheme
(e.g., to prioritize allocating physically contiguous blocks), as
indicated in block 2010. As indicated in block 2012, the data
storage sled 1260 may determine the blocks as a function of a wear
leveling scheme (e.g., to prioritize evenly distributing writes
among the data storage devices 1682 rather than repeatedly writing
to the same data storage devices 1682). Further, as indicated in
block 2014, the data storage sled 1640 may determine the blocks to
write the object to as a function of a target access latency to be
obtained. For example, the data storage sled 1640 may determine to
write the different portions of the object across multiple data
storage devices 1682, rather than writing the object to the blocks
of a single data storage device 1682, to lower the amount of time
needed to read back the object in response to a subsequent read
request. As indicated in block 2016, the data storage sled 1640 may
write an identifier of each determined block to a block ownership
database (e.g., in the memory 720) in association with the object
identifier. In block 2018, the data storage sled 1640 writes the
object (e.g., a replica of the object or erasure coded sections of
the object) to the determined block(s) of the corresponding data
storage device(s) 1682. Afterwards, the method 2000 loops back to
block 2002, in which the data storage sled 1640 awaits another data
access request. Referring back to block 2004, if the data storage
sled 1640 instead determines that the data access request is not a
write request (e.g., the data access request is a read request),
the method 2000 advances to block 2020 of FIG. 21, in which the
data storage sled 1640 determines one or more blocks of the data
storage device(s) 1682 to read the object from.
[0091] Referring now to block 2022 of FIG. 21, in determining the
one or more blocks to read the object from, the data storage sled
1640 may read an identifier for each block from a block ownership
database that associates object identifiers with block identifiers
(e.g., block addresses). For example, the data storage sled 1640
may read from the block ownership database described above with
reference to block 2016 of FIG. 20. Subsequently, in block 2024,
the data storage sled 1640 reads the object from the determined one
or more blocks of the data storage device(s) 1682 and, in block
2026, sends the object to the requesting compute sled (e.g., the
compute sled 1632).
EXAMPLES
[0092] Illustrative examples of the technologies disclosed herein
are provided below. An embodiment of the technologies may include
any one or more, and any combination of, the examples described
below.
[0093] Example 1 includes a compute sled comprising a network
interface controller; and circuitry to receive, through a network
and with the network interface controller, a data access request
from a compute device, wherein the data access request includes a
data payload indicative of an object to be stored; map the object
to a set of multiple data storage sleds for distributed storage of
the object; and send, through the network and with a local data bus
protocol mapped onto a network protocol, a write request to the
mapped data storage sleds to store the object in one or more data
storage devices located on each data storage sled.
[0094] Example 2 includes the subject matter of Example 1, and
wherein to send, through the network and with a local data bus
protocol mapped onto a network protocol, a write request comprises
to tunnel the write request through a non-volatile memory express
over fabric (NVMeOF) connection to the data storage sleds.
[0095] Example 3 includes the subject matter of any of Examples 1
and 2, and wherein to map the object to the data storage sleds
comprises to map the object to data storage sleds in different
failure domains.
[0096] Example 4 includes the subject matter of any of Examples
1-3, and wherein the circuitry is further to send, through the
network and to one or more other compute sleds, metadata associated
with the object.
[0097] Example 5 includes the subject matter of any of Examples
1-4, and wherein to send, through the network and to one or more
other compute sleds, metadata associated with the object comprises
to send the metadata to one or more compute sleds associated with
the mapped data storage sleds.
[0098] Example 6 includes the subject matter of any of Examples
1-5, and wherein to send the metadata comprises to send one or more
of an object identifier associated with the object or metadata
indicative of one or more attributes of the object.
[0099] Example 7 includes the subject matter of any of Examples
1-6, and wherein to map the object to the data storage sleds
comprises to map the object as a function of a hash of a uniform
resource locator associated with the object.
[0100] Example 8 includes the subject matter of any of Examples
1-7, and wherein the circuitry is further to verify, prior to
sending the write request to the mapped data storage sled, that the
data payload represents an object that is not already stored on one
or more of the data storage sleds.
[0101] Example 9 includes the subject matter of any of Examples
1-8, and wherein to verify that the data payload represents and
object that is not already stored on one or more of the data
storage sleds comprises to compare an object identifier associated
with the object to object identifiers for objects stored in a data
storage sled associated with the compute sled.
[0102] Example 10 includes the subject matter of any of Examples
1-9, and wherein the circuitry is further to receive a request a
read a second object, wherein the request includes an identifier of
the second object; and determine, in response to the read request,
one or more storage sleds mapped to the identifier of the second
object; send, through the network and with the local data bus
protocol mapped onto the network protocol, a read request to the
mapped one or more data storage sleds; and receive the read object
from the mapped one or more data storage sleds.
[0103] Example 11 includes the subject matter of any of Examples
1-10, and wherein to send, through the network and with the local
data bus protocol mapped onto the network protocol, a read request
comprises to tunnel the read request through a non-volatile memory
express over fabric (NVMeOF) connection to the one or more data
storage sleds.
[0104] Example 12 includes one or more machine-readable storage
media comprising a plurality of instructions stored thereon that,
in response to being executed, cause a compute sled to receive,
through a network and with a network interface controller, a data
access request from a compute device, wherein the data access
request includes a data payload indicative of an object to be
stored; map the object to a set of multiple data storage sleds for
distributed storage of the object; and send, through the network
and with a local data bus protocol mapped onto a network protocol,
a write request to the mapped data storage sleds to store the
object in one or more data storage devices located on each data
storage sled.
[0105] Example 13 includes the subject matter of Example 12, and
wherein to send, through the network and with a local data bus
protocol mapped onto a network protocol, a write request comprises
to tunnel the write request through a non-volatile memory express
over fabric (NVMeOF) connection to the data storage sleds.
[0106] Example 14 includes the subject matter of any of Examples 12
and 13, and wherein to map the object to the data storage sleds
comprises to map the object to data storage sleds in different
failure domains.
[0107] Example 15 includes the subject matter of any of Examples
12-14, and wherein, when executed, the plurality of instructions
further cause the compute sled to send, through the network and to
one or more other compute sleds, metadata associated with the
object.
[0108] Example 16 includes the subject matter of any of Examples
12-15, and wherein to send, through the network and to one or more
other compute sleds, metadata associated with the object comprises
to send the metadata to one or more compute sleds associated with
the mapped data storage sleds.
[0109] Example 17 includes the subject matter of any of Examples
12-16, and wherein to send the metadata comprises to send one or
more of an object identifier associated with the object or metadata
indicative of one or more attributes of the object.
[0110] Example 18 includes the subject matter of any of Examples
12-17, and wherein to map the object to the data storage sleds
comprises to map the object as a function of a hash of a uniform
resource locator associated with the object.
[0111] Example 19 includes a method comprising receiving, by a
compute sled with a network interface controller, a data access
request from a compute device, wherein the data access request
includes a data payload indicative of an object to be stored;
mapping, by the compute sled, the object to a set of multiple data
storage sleds for distributed storage of the object; and sending,
by the compute sled, through a network and with a local data bus
protocol mapped onto a network protocol, a write request to the
mapped data storage sleds to store the object in one or more data
storage devices located on each data storage sled.
[0112] Example 20 includes the subject matter of Example 19, and
wherein sending, through the network and with a local data bus
protocol mapped onto a network protocol, a write request comprises
tunneling the write request through a non-volatile memory express
over fabric (NVMeOF) connection to the data storage sleds.
[0113] Example 21 includes the subject matter of any of Examples 19
and 20, and wherein mapping the object to the data storage sleds
comprises mapping the object to data storage sleds in different
failure domains.
[0114] Example 22 includes the subject matter of any of Examples
19-21, and further including sending, by the compute sled, through
the network and to one or more other compute sleds, metadata
associated with the object.
[0115] Example 23 includes a data storage sled comprising a network
interface controller; a set of data storage devices; and circuitry
to receive, through the network interface controller and with a
local data bus protocol mapped onto a network protocol, a write
request from a compute sled of a distributed data storage system,
wherein the write request includes an object to be written to one
or more of the data storage devices; determine one or more blocks
of the set of data storage devices to write the object to; write an
identifier of each determined block to a block ownership database
in association with an identifier of the object; and write the
object to the determined one or more blocks.
[0116] Example 24 includes the subject matter of Example 23, and
wherein the data storage devices have different performance
characteristics resulting from different physical storage media in
each data storage device and wherein to determine the one or more
blocks of the set of data storage devices to write the object to
comprises to determine the one or more blocks as a function of a
target access latency.
[0117] Example 25 includes the subject matter of any of Examples 23
and 24, and wherein to determine the one or more blocks of the set
of data storage devices to write the object to comprises to
determine the one or more blocks as a function of a data storage
device wear leveling scheme.
[0118] Example 26 includes the subject matter of any of Examples
23-25, and wherein the circuitry is further to receive, through the
network interface controller, a read request from the compute sled,
wherein the read request includes the identifier of the object;
determine, from the block ownership database, the one or more
blocks of the set of data storage devices to read the object from;
read the object from the determined one or more blocks of the set
of data storage devices; and send the object to the compute
sled.
[0119] Example 27 includes a method comprising receiving, through a
network interface controller of a data storage sled and with a
local data bus protocol mapped onto a network protocol, a write
request from a compute sled of a distributed data storage system,
wherein the write request includes an object to be written to one
or more data storage devices of the data storage sled; determining,
by the data storage sled, one or more blocks of the data storage
devices to write the object to; writing, by the data storage sled,
an identifier of each determined block to a block ownership
database in association with an identifier of the object; and
writing, by the data storage sled, the object to the determined one
or more blocks.
[0120] Example 28 includes one or more machine-readable storage
media comprising a plurality of instructions stored thereon that,
in response to being executed, cause a data storage sled to
receive, through a network interface controller of the data storage
sled and with a local data bus protocol mapped onto a network
protocol, a write request from a compute sled of a distributed data
storage system, wherein the write request includes an object to be
written to one or more data storage devices of the data storage
sled; determine, by the data storage sled, one or more blocks of
the data storage devices to write the object to; write, by the data
storage sled, an identifier of each determined block to a block
ownership database in association with an identifier of the object;
and write, by the data storage sled, the object to the determined
one or more blocks.
* * * * *