Today, many entities must create and manage complex data centers capable of storing and accessing hundreds of terabytes of data (e.g., text, image, and video data) that are generated and consumed every day by their users. These complex data centers often need to be capable of creating and storing duplicate copies of this data for disaster-recovery, testing, regulatory, or other purposes. Generally, different types of data have different storage requirements. Moreover, the storage requirements for any particular instance of data may change over time. For example, new or popular data may be considered “hot data” and need to be stored to fast storage devices and managed by fast servers. Alternatively, old or unpopular data may be considered “cold data” that may be stored to slower storage devices and/or managed by slower servers.
A typical data center generally includes different types of storage systems that have each been designed and configured for a single fixed purpose (e.g., warm-data storage, cold-data storage, etc.). Unfortunately, these different types of storage systems often use or require different types of components (e.g., different types of storage devices, storage controllers, servers, and network interfaces) that each operate and/or interface using one of several incompatible protocols or technologies. These complexities may make managing, configuring, servicing, replacing, and reconfiguring a data center's storage-system components difficult for those individuals enlisted to perform these tasks.
As will be described in greater detail below, the instant disclosure describes various apparatus, systems, and methods that enable a flexible storage-system drawer platform to take on many different storage-system configurations. In one example, a configurable storage-system drawer may include (1) a chassis, (2) a slide assembly coupled to a side of the chassis that is configured to enable the chassis to be temporarily pulled out of a data-center rack, and (3) a passive drive-plane board housed within the chassis and configured to enable storage-system modules that differ between two or more storage-system configurations of the storage-system drawer to be interchanged. In some examples, the passive drive-plane board may include (1) storage-drive connectors that are each configured to detachably mate with a storage drive, (2) a storage-system-module connector configured to detachably mate with a storage-system module that includes one or more components necessary for one of the two or more storage-system configurations, and (3) electrical interconnects that electrically couple the storage-drive connectors to the storage-system-module connector.
In some examples, the two or more storage-system configurations of the storage-system drawer may include a single-server configuration, a dual-server configuration, and/or a just-a-bunch-of-drives (JBOD) configuration. In some examples, the single-server configuration may require a first type of input/output module, the dual-server configuration may require a second type of input/output module, and the storage-system-module connector may be an input/output-module connector configured to accept any input/output module of the first type or any input/output module of the second type. In at least one example, the single-server configuration may require a first type of storage-controller module, the dual-server configuration may require a second type of storage-controller module, the JBOD configuration may require a third type of storage-controller module, and the storage-system-module connector may be a storage-controller-module connector configured to accept any storage-controller module of the first type, any storage-controller module of the second type, and/or any storage-controller module of the third type.
In some examples, the single-server configuration may require a first type of input/output module, one compute module, and a first type of storage-controller module; the dual-server configuration may require a second type of input/output module, two compute modules, and a second type of storage-controller module; and the JBOD configuration may require no input/output modules, no compute modules, but a third type of storage-controller module. In these examples, the storage-system-module connector may be a storage-controller-module connector configured to accept any storage-controller module of the first type, any storage-controller module of the second type, or any storage-controller module of the third type. In addition, the passive drive-plane board may further include (1) an input/output-module connector configured to accept any input/output module of the first type or any input/output module of the second type and (2) two compute-module connectors that each are configured to accept a compute module. In some examples, the storage-system-module connector may be a compute-module connector configured to detachably mate with a compute module that includes a central processing unit.
In at least one example, the chassis may include a front through which air is able to pass and a rear through which air is able to pass, and the configurable storage-system drawer may further include (1) a fan coupled to a rear of the chassis that is configured to pull an airflow rearward through the chassis and (2) airflow-retaining members that are configured to cause substantially all of the airflow to enter the chassis through the front of the chassis when the configurable storage-system drawer is pulled out of the data-center rack. In at least one example, the storage-system module may be an input/output module having a heatsink, and one of the airflow-retaining members may include an opening that is configured to enable a portion of the airflow to bypass the front of the chassis and instead pass from under the configurable storage-system drawer across the heatsink. In some examples, the slide assembly may include (1) a first dampening member configured to reduce a shock applied to the chassis when the configurable storage-system drawer is pulled out of the data-center rack and (2) a second dampening member configured to reduce a shock applied to the chassis when the configurable storage-system drawer is pushed into the data-center rack.
According to various embodiments, a corresponding storage-system drawer may include (1) storage drives, (2) a first storage-controller module that includes one or more storage-controller components necessary for one of two or more configurations of the storage-system drawer, (3) a second storage-controller module that includes the one or more storage-controller components necessary for one of the two or more configurations of the storage-system drawer, (4) a chassis, (5) a slide assembly coupled to a side of the chassis configured to enable the chassis to be temporarily pulled out of a data-center rack, and (6) a passive drive-plane board housed within the chassis and configured to enable storage-system modules that differ between the two or more configurations of the storage-system drawer to be interchanged. In some examples, the passive drive-plane board may include (1) storage-drive connectors that each are configured to detachably mate with one of the storage drives, (2) two storage-controller-module connectors that each are configured to detachably mate with the first storage-controller module or the second storage-controller module, (3) two input/output-module connectors that each are configured to detachably mate with an input/output module that includes one or more input/output components necessary for one of the two or more storage-system configurations, (4) two compute-module connectors that each are configured to detachably mate with a compute module that includes a central processing unit necessary for one of the two or more storage-system configurations, and (5) electrical interconnects that electrically couple the storage-drive connectors, the two storage-controller-module connectors, the two input/output-module connectors, and/or the two compute-module connectors.
In some examples, the two or more configurations of the storage-system drawer may include a single-server configuration, a dual-server configuration, and/or a JBOD configuration. In some examples, the single-server configuration may require a first type of storage-controller module, the dual-server configuration may require a second type of storage-controller module, the JBOD configuration may require a third type of storage-controller module, and the two storage-controller-module connectors may be configured to accept any storage-controller module of the first type, any storage-controller module of the second type, or any storage-controller module of the third type. In some examples, the single-server configuration may require a first type of input/output module, the dual-server configuration may require a second type of input/output module, and the two input/output-module connectors may be configured to accept any input/output module of the first type or any input/output module of the second type.
In certain examples, the single-server configuration may require a first type of input/output module, one compute module, and a first type of storage-controller module; the dual-server configuration may require a second type of input/output module, two compute modules, and a second type of storage-controller module; and the JBOD configuration may require no input/output modules, no compute modules, but a third type of storage-controller module. In one example, the storage-system drawer may have the single-server configuration, the first storage-controller module and the second storage-controller module may be of the first type of storage-controller module, and the storage-system drawer may further include an input/output module of the first type of input/output module coupled to one of the two input/output-module connectors and a compute module coupled to one of the two compute-module connectors. In another example, the storage-system drawer may have the dual-server configuration, the first storage-controller module and the second storage-controller module may be of the second type of storage-controller module, and the storage-system drawer may further include two input/output modules of the second type of input/output module coupled to the two input/output-module connectors and two compute modules coupled to the two compute-module connectors. In another example, the storage-system drawer may have the JBOD configuration, the first storage-controller module and the second storage-controller module may be of the third type of storage-controller module, the two input/output-module connectors may be empty, and the two compute-module connectors may be empty.
In addition to the various configurable storage-system drawers described herein, the instant disclosure presents exemplary methods associated with reconfiguring storage-system drawers. For example, a method may include pulling out a storage-system drawer capable of a first storage-system configuration and a second storage-system configuration from a data-center rack. In this example, the storage-system drawer may include (1) a chassis, (2) a slide assembly coupled to a side of the chassis and configured to enable the chassis to be temporarily pulled out of the data-center rack, (3) a first storage-system module that includes one or more components necessary for the first storage-system configuration, and (4) a passive drive-plane board housed within the chassis and configured to enable active storage-system modules that differ between the first storage-system configuration and the second storage-system configuration to be interchanged. In some examples, the passive drive-plane board may include (1) storage-drive connectors that each are configured to detachably mate with a storage drive, (2) a storage-controller-module connector configured to detachably mate with the first storage-system module, and (3) electrical interconnects that electrically couple the storage-drive connectors to the storage-controller-module connector. In some examples, the method may further include (1) removing the first storage-system module from the storage-controller-module connector, (2) inserting a second storage-system module into the storage-controller-module connector, with the second storage-system module including one or more components necessary for the second storage-system configuration, and (3) pushing the storage-system drawer back into the data-center rack.
Features from any of the above-mentioned embodiments may be used in combination with one another in accordance with the general principles described herein. These and other embodiments, features, and advantages will be more fully understood upon reading the following detailed description in conjunction with the accompanying drawings and claims.
The accompanying drawings illustrate a number of exemplary embodiments and are a part of the specification. Together with the following description, these drawings demonstrate and explain various principles of the instant disclosure.
Throughout the drawings, identical reference characters and descriptions indicate similar, but not necessarily identical, elements. While the exemplary embodiments described herein are susceptible to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and will be described in detail herein. However, the exemplary embodiments described herein are not intended to be limited to the particular forms disclosed. Rather, the instant disclosure covers all modifications, equivalents, and alternatives falling within the scope of the appended claims.
The present disclosure is generally directed to a flexible storage-system drawer platform that may support a variety of storage-system configurations, such as single-server configurations, dual-server configurations, and JBOD configurations. As will be explained in greater detail below, by including some or all of the common components shared between two or more possible configurations of a storage system in a passive drive-plane board and modularizing the components that differ, the apparatus, systems, and methods disclosed herein may enable a storage-system drawer that contains the passive drive-plane board to take on any one of the configurations and/or be later reconfigured to take on any of the others. In some examples, the passive drive-plane board may include various connectors and electrical interconnects configured to mechanically and electrically couple various types of modularized components, such as compute modules, storage drives, storage controllers, input/output modules, auxiliary components, and other active storage-system components. In some examples, the passive drive-plane board may be protocol and/or connector agnostic to enable different forms of each type of modularized component to be mixed and matched. In some examples, the flexible storage-system drawer platform may be substantially self-contained. For example, the flexible storage-system drawer platform may contain substantially all necessary power cabling, fans, and sensors needed for each supported storage-system configuration. The flexible storage-system drawer platform may also include various cutouts and baffles that enable the flexible storage-system drawer platform to be extended from a data-center rack for long periods of time for servicing purposes without its components overheating.
Embodiments of the instant disclosure may provide various features and advantages over conventional storage-system drawers. For example, the flexible storage-system drawer platform disclosed herein may allow for modularized storage-system components to be replaced by modularized storage-system components of other types, formats, and/or form factors without requiring the purchase or configuration of entirely new drawer hardware and/or the reconfiguration of data-center racks. In addition, the mechanisms disclosed herein may facilitate more efficient management of data center facilities. For example, the flexible storage-system drawer platform disclosed herein may enable data-center administrators to reconfigure a storage-system drawer to meet their changing needs by simply changing or replacing the storage-system drawer's modularized components rather than replacing the entire storage-system drawer.
The following will provide, with reference to
In some examples, passive drive-plane board 100 may be adapted to enable a storage-system chassis, such as a rack-mounted drawer, to take on several different storage-system configurations. As used herein, the term “storage-system configuration” generally refers to the forms and/or arrangements of the components that make up a storage system. Two storage-system configurations may be considered as different if they use different types, forms, or arrangements of components. In some examples, passive drive-plane board 100 may include some or all of the common components that are shared between a dual-server configuration 400 illustrated in
As shown in
Each of storage-drive connectors 104 may be configured to interface with a single storage drive. The term “storage drive,” as used herein, generally refers to any device capable of storing electronic data. In some examples, storage-drive connectors 104 may be configured to interface with solid state drives, hard disk drives, and/or optical drives. In some examples, storage-drive connectors 104 may be configured to interface with two or more different types of storage drives. For example, storage-drive connectors 104 may be configured to interface with storage drives that have different physical form factors, that are made up of different types of storage (e.g., solid state or hard disk), that use different protocols, and/or that use different types of connectors. In some examples, storage-drive connectors 104 may be configured to interface with serial attached small computer system interface (SAS) drives, serial advanced technology attachment (SATA) drives, and/or Non-Volatile Memory Express (NVMe) drives. In some examples, storage-drive connectors 104 may be configured to enable hot-swapping of storage drives.
Each of compute-module connectors 106 may be configured to interface with a compute module. The term “compute module,” as used herein, generally refers to any server module whose primary function is computational and/or any server module whose primary function is to provide data storage services. In some examples, compute-module connectors 106 may be configured to interface with two or more different types of compute modules. Additionally or alternatively, passive drive-plane board 100 and compute-module connectors 106 may be collectively configured to allow one or both of compute-module connectors 106 to be left empty. In some examples, compute-module connectors 106 may be configured to enable hot-swapping of compute modules. In one non-limiting example, passive drive-plane board 100 and each of compute-module connectors 106 may be collectively configured to (1) connect a single compute module to a single storage-controller module that controls 36 storage drives in a storage-system drawer and (2) logically separate the compute module and the storage-controller module from other compute modules, storage-controller modules, and storage drives in the storage-system drawer.
Each of storage-controller connectors 108 may be configured to interface with a storage-controller module. The term “storage-controller module,” as used herein, generally refers to any storage-system module whose primary function is to control and communicate with storage drives. In some examples, storage-controller connectors 108 may be configured to interface with two or more different types of storage-controller modules, such as those illustrated in
Each of I/O-module connectors 110 may be configured to interface with an I/O module. The term “I/O module,” as used herein, generally refers to any storage-system module whose primary function is to facilitate data transfer in and out of a storage system. In some examples, I/O-module connectors 110 may be configured to interface with two or more different types of I/O modules, such as those illustrated in
Passive drive-plane board 100 may have additional elements other than those illustrated in
In some embodiments, NIC 410, SAS IOC 414, CPU 420, and/or SAS IOC 424 may all be connected to PCIE bus 416 via PCIe connectors and electrical interconnects contained within passive drive-plane board 100. In one embodiment, BMC 412, CPU 420, and/or drive power control and sensors 430 may be connected to SAS expander 426 via electrical interconnects contained within passive drive-plane board 100. In some embodiments, BMC 412, CPU 420, and/or drive power control and sensors 430 may be connected to SAS expander 426 via eight lanes of PCIe generation 3 connectors contained within passive drive-plane board 100. In some embodiments, SAS IOC 424 may be connected to SAS expander 426 via a SAS connection. For example, SAS IOC 424 may be connected to SAS expander 426 via eight lanes of twelve gigabyte SAS connections. In some embodiments, SAS expander 426 may be connected to drives 434 via a SATA connection contained within passive drive-plane board 100. In other embodiments, SAS expander 426 may be connected to drives 434 via a SAS connection contained within passive drive-plane board 100. For example, SAS expander 426 may be connected to drives 434 via thirty-six lanes of twelve gigabyte SAS connections contained within passive drive-plane board 100 and/or six gigabyte SATA connections contained within passive drive-plane board 100.
Similarly, an I/O module 464 may include an NIC 440, BMC 442, SAS IOC 444, and/or PCIe bus 446; a compute module 466 may include memory 448, a CPU 450, and/or a boot SSD 452; and/or a storage controller card 468 may include a SAS IOC 454 and/or a SAS expander 456. The aforementioned components may be connected to one another and to the components on passive drive-plane board 100 in a similar manner to the components hosted within I/O module 404, compute module 406, and/or storage controller card 408. In one embodiment, the only external connection between the storage-system drawer and other systems may be an Ethernet link. In at least one example, SAS IOC 414 may not be populated on I/O module 404 since drives 434 may be directly connected, and/or SAS IOC 444 may not be populated on I/O module 464 since drives 436 may be directly connected. In this example, SAS IOC 424 on storage controller card 408 may be used to connect to SAS expander 426, which attaches drives 434, and/or SAS IOC 454 on storage controller card 468 may be used to connect to SAS expander 456, which attaches drives 436.
In some examples, BMC 412 and BMC 442 may handle the majority of storage-system management in the storage-system drawer. For example, BMC 412 may manage compute module 406, storage controller card 408, drives 434, fans 428, and drive power control and sensors 430. Similarly, BMC 442 may manage compute module 466, storage controller card 468, drives 436, fans 428, and drive power control and sensors 432. Additionally, SAS Expanders 426 and 456 may handle communication with individual drives as well as monitor certain sensors.
As illustrated in
In some embodiments, NIC 610, SAS IOC 614, CPU 620, and/or SAS IOC 624 may all be connected to PCIE bus 616 via PCIe connectors and electrical interconnects contained within passive drive-plane board 100. In some embodiments, SAS connector 640 may be connected to SAS IOC 614 via a SAS connection. For example, SAS connector 640 may be connected to SAS IOC 614 via six lanes of twelve gigabyte SAS connections. In one embodiment, BMC 612, fans 628, drive power control and sensors 632, and/or SAS expander 626 may all be connected to CPU 620 via connections contained within passive drive-plane board 100. In some embodiments, SAS expander 626 may be connected to SAS IOC 624, drives 634, and/or SAS connector 638. In some examples, SAS expander 626 may be connected to SAS IOC 624 and/or SAS connector 638 via 6 gigabyte SAS connections. Additionally, SAS expander 626 may be connected to drives 634 via 6 gigabyte SAS connections contained within passive drive-plane board 100. In one example, SAS expander 626 may be connected to SAS IOC 624 via eight lanes of SAS connections, to SAS connector 638 via four lanes, and/or to drives 634 via thirty-six lanes. Similarly, SAS expander 646 may be connected to SAS IOC 644, drives 636, and/or SAS connector 648. In some embodiments, SAS connector 638 may be connected to SAS connector 648 via a connection path not contained within passive drive-plane board 100. In some examples, internal MiniSAS connectors of storage controller card 608 and storage controller card 650 may be connected via an x4 cable to connect drives 634 and 636.
In some examples, BMC 612 may handle the majority of storage-system management in the storage-system drawer. For example, BMC 612 may manage compute module 606, storage controller card 608, drives 634, fans 628, and drive power control and sensors 632. In some examples, storage controller card 650 may manage drives 636, fans 628, and drive power control and sensors 630. Additionally, SAS Expanders 626 and 646 may handle communication with individual drives as well as monitor certain sensors.
In some embodiments, SAS expander 814 and/or SAS expander 818 may be connected to and/or control fans 828 via electrical interconnects contained within passive drive-plane board 100. In one embodiment, SAS expander 814 may be connected to drive power control and sensors 830 via electrical interconnects contained within passive drive-plane board 100. Similarly, SAS expander 818 may be connected to drive power control and sensors 832 via electrical interconnects contained within passive drive-plane board 100. In one embodiment, SAS expander 814 may be connected to SAS connector 810, SAS IOC 812, SAS connector 822, and/or drives 834. In one example, SAS expander 814 may be connected to drives 834 via electrical interconnects contained within passive drive-plane board 100. In some examples, SAS expander 814 may be connected to SAS connector 810 via four lanes of twelve gigabyte SAS connections, may be connected to SAS IOC 812 via eight lanes of twelve gigabyte SAS connections, may be connected to SAS connector 822 via a four lane miniSAS high-density (HD) internal cable, and/or may be connected to drives 834 via thirty-six lanes of twelve gigabyte SAS connections. In some embodiments, SAS expander 818 may be connected to SAS connector 820, SAS IOC 816, SAS connector 824, and/or drives 836 in a similar fashion. In some examples, SAS IOC 812 and/or SAS IOC 816 may not be populated. In some embodiments, multiple JBOD servers may be used as nodes behind a head node that is configured as a single-server drawer and/or a JBOD-server drawer. In some examples, storage controller cards 806 and 808 may handle the majority of storage-system management in the storage-system drawer. For example, storage controller card 808 may manage drives 834, fans 828, and drive power control and sensors 830. Similarly, storage controller card 806 may manage drives 836, fans 828, and drive power control and sensors 832.
Returning to
In some examples, the chassis of storage-system drawer 1000 may be sized to house all of the storage-system components illustrated in
Additionally or alternatively, storage-system drawer 1000 may be configured so that some of the storage-system components that are contained within storage-system drawer 1000 may be serviced through the front, the bottom, or the rear of storage-system drawer 1000. For example, storage-system drawer 1000 may include front-accessible I/O-module drawers, such as I/O-module drawers 1032 and 1034, that are adapted to secure I/O modules within storage-system drawer 1000. As shown in
As shown in
As step 1320, a first storage-system module that includes one or more components necessary for the first storage-system configuration may be removed from the storage-system drawer. For example, when reconfiguring storage-system drawer 1000 from configuration 400 to configuration 600 or configuration 800, one or more of I/O module 404, compute module 406, storage controller card 408, I/O module 464, compute module 466, and storage controller card 468 may be removed from storage-system drawer 1000. Similarly, when reconfiguring storage-system drawer 1000 from configuration 600 to configuration 400 or configuration 800, one or more of I/O module 604, compute module 606, storage controller card 608, and storage controller card 650 may be removed from storage-system drawer 1000. Likewise, when reconfiguring storage-system drawer 1000 from configuration 800 to configuration 400 or configuration 600, storage controller card 808 and storage controller card 806 may be removed from storage-system drawer 1000.
As step 1330, a second storage-system module that includes one or more components necessary for the second storage-system configuration may be inserted into the storage-system drawer. For example, when reconfiguring storage-system drawer 1000 to configuration 400 from configuration 600 or configuration 800, one or more of I/O module 404, compute module 406, storage controller card 408, I/O module 464, compute module 466, and storage controller card 468 may be inserted into storage-system drawer 1000. Similarly, when reconfiguring storage-system drawer 1000 to configuration 600 from configuration 400 or configuration 800, one or more of I/O module 604, compute module 606, storage controller card 608, and storage controller card 650 may be inserted into storage-system drawer 1000. Likewise, when reconfiguring storage-system drawer 1000 to configuration 800 from configuration 400 or configuration 600, storage controller card 808 and storage controller card 806 may be inserted into storage-system drawer 1000.
As step 1340, the storage-system drawer may be pushed back into the data-center rack. Using
As explained above, by including some or all of the common components shared between two or more possible configurations of a storage system in a passive drive-plane board and modularizing the components that differ, the apparatus, systems, and methods disclosed herein may enable a storage-system drawer that contains the passive drive-plane board to take on any one of the configurations and/or be later reconfigured to take on any of the others. In some examples, the passive drive-plane board may include various connectors and electrical interconnects configured to mechanically and electrically couple various types of modularized components, such as compute modules, storage drives, storage controllers, input/output modules, auxiliary components, and other active storage-system components. In some examples, the passive drive-plane board may be protocol and/or connector agnostic to enable different forms of each type of modularized component to be mixed and matched.
The process parameters and sequence of the steps described and/or illustrated herein are given by way of example only and can be varied as desired. For example, while the steps illustrated and/or described herein may be shown or discussed in a particular order, these steps do not necessarily need to be performed in the order illustrated or discussed. The various exemplary methods described and/or illustrated herein may also omit one or more of the steps described or illustrated herein or include additional steps in addition to those disclosed.
The preceding description has been provided to enable others skilled in the art to best utilize various aspects of the exemplary embodiments disclosed herein. This exemplary description is not intended to be exhaustive or to be limited to any precise form disclosed. Many modifications and variations are possible without departing from the spirit and scope of the instant disclosure. The embodiments disclosed herein should be considered in all respects illustrative and not restrictive. Reference should be made to the appended claims and their equivalents in determining the scope of the instant disclosure.
Unless otherwise noted, the terms “connected to” and “coupled to” (and their derivatives), as used in the specification and claims, are to be construed as permitting both direct and indirect (i.e., via other elements or components) connection. In addition, the terms “a” or “an,” as used in the specification and claims, are to be construed as meaning “at least one of.” Finally, for ease of use, the terms “including” and “having” (and their derivatives), as used in the specification and claims, are interchangeable with and have the same meaning as the word “comprising.”
This application is a continuation of U.S. application Ser. No. 15/688,830, filed 28 Aug. 2017, the disclosure of which is incorporated, in its entirety, by this reference.
Number | Name | Date | Kind |
---|---|---|---|
355538 | Keyes | Jan 1887 | A |
517703 | Ludwig | Apr 1894 | A |
922852 | Cannan | May 1909 | A |
1062733 | Rahotina | May 1913 | A |
1516692 | Andreas | Nov 1924 | A |
1777074 | Cordrey | Sep 1930 | A |
3447850 | Samson | Jun 1969 | A |
3536348 | Tedesco | Oct 1970 | A |
3601463 | Watt et al. | Aug 1971 | A |
3711140 | Onori | Jan 1973 | A |
3996500 | Coules | Dec 1976 | A |
D294800 | Nilsson | Mar 1988 | S |
4969065 | Petri | Nov 1990 | A |
4993762 | Rogers et al. | Feb 1991 | A |
5262705 | Hattori | Nov 1993 | A |
5281149 | Petri | Jan 1994 | A |
5724803 | Pea | Mar 1998 | A |
5793614 | Tollbom | Aug 1998 | A |
5957659 | Amou et al. | Sep 1999 | A |
6021044 | Neville, Jr. et al. | Feb 2000 | A |
6109767 | Rodriguez | Aug 2000 | A |
6116375 | Lorch et al. | Sep 2000 | A |
6159031 | Llapitan et al. | Dec 2000 | A |
6181549 | Mills et al. | Jan 2001 | B1 |
6259032 | Fernandez | Jul 2001 | B1 |
6260441 | Landl | Jul 2001 | B1 |
6331915 | Myers | Dec 2001 | B1 |
6373707 | Hutchins | Apr 2002 | B1 |
6385036 | Chien | May 2002 | B1 |
6385051 | Perez et al. | May 2002 | B1 |
6404646 | Tsai et al. | Jun 2002 | B1 |
6469899 | Hastings et al. | Oct 2002 | B2 |
6515854 | Claprood | Feb 2003 | B1 |
6535394 | Hirzmann | Mar 2003 | B1 |
6545879 | Goodwin | Apr 2003 | B1 |
6552915 | Takahashi | Apr 2003 | B2 |
6556433 | Love et al. | Apr 2003 | B1 |
6621692 | Johnson et al. | Sep 2003 | B1 |
6695629 | Mayer | Feb 2004 | B1 |
6786691 | Alden, III | Sep 2004 | B2 |
6791843 | Dobbs et al. | Sep 2004 | B1 |
6798669 | Hsu | Sep 2004 | B1 |
6813165 | Cheng et al. | Nov 2004 | B2 |
6921227 | De Jong et al. | Jul 2005 | B1 |
6987674 | El-Batal | Jan 2006 | B2 |
6992885 | Wang | Jan 2006 | B2 |
6995982 | Gonzalez et al. | Feb 2006 | B2 |
7004764 | Boudreau et al. | Feb 2006 | B2 |
7084654 | Zhao et al. | Aug 2006 | B2 |
7085131 | Peng et al. | Aug 2006 | B2 |
7088579 | Konshak | Aug 2006 | B1 |
7167371 | Coles et al. | Jan 2007 | B2 |
7301778 | Fang | Nov 2007 | B1 |
7304855 | Milligan | Dec 2007 | B1 |
7408770 | Peng et al. | Aug 2008 | B2 |
7411787 | Katakura et al. | Aug 2008 | B2 |
7423354 | Suzuki et al. | Sep 2008 | B2 |
7505286 | Brovald et al. | Mar 2009 | B2 |
7515413 | Curtis | Apr 2009 | B1 |
7649750 | Lee | Jan 2010 | B2 |
7826208 | Wang et al. | Nov 2010 | B2 |
8020902 | Li | Sep 2011 | B1 |
8064195 | Zhang et al. | Nov 2011 | B2 |
8127059 | Carr et al. | Feb 2012 | B1 |
8203851 | Boetzer | Jun 2012 | B2 |
8310828 | Collins | Nov 2012 | B2 |
8331095 | Hu et al. | Dec 2012 | B2 |
8369080 | Huang | Feb 2013 | B2 |
8517054 | Lai et al. | Aug 2013 | B2 |
8570720 | Yao et al. | Oct 2013 | B2 |
8585336 | Tao et al. | Nov 2013 | B2 |
8622673 | Wong et al. | Jan 2014 | B2 |
8636528 | Sass et al. | Jan 2014 | B2 |
8657619 | Lin et al. | Feb 2014 | B2 |
8743549 | Frink et al. | Jun 2014 | B2 |
8749966 | Boudreau et al. | Jun 2014 | B1 |
8770681 | Hu | Jul 2014 | B2 |
8848349 | Ke | Sep 2014 | B2 |
8944538 | Li | Feb 2015 | B2 |
8971052 | Fu | Mar 2015 | B2 |
8979458 | Sun et al. | Mar 2015 | B2 |
9066438 | Chen | Jun 2015 | B2 |
9070419 | Zhu et al. | Jun 2015 | B1 |
9098233 | Keffeler | Aug 2015 | B2 |
9101210 | Lin | Aug 2015 | B2 |
9113567 | Stotz, Jr. | Aug 2015 | B2 |
9203188 | Siechen et al. | Dec 2015 | B1 |
9274548 | Foisy | Mar 2016 | B2 |
9298230 | Wei | Mar 2016 | B2 |
9313909 | Huang | Apr 2016 | B1 |
9354003 | Lin | May 2016 | B2 |
9448601 | Beall et al. | Sep 2016 | B1 |
9454190 | Mao et al. | Sep 2016 | B2 |
9456519 | Bailey et al. | Sep 2016 | B2 |
9461389 | Novack et al. | Oct 2016 | B2 |
9474190 | Beall et al. | Oct 2016 | B1 |
9538684 | Chen et al. | Jan 2017 | B2 |
9545028 | Hoshino et al. | Jan 2017 | B2 |
9572276 | Haroun | Feb 2017 | B2 |
9583877 | Angelucci | Feb 2017 | B1 |
9609778 | Spencer et al. | Mar 2017 | B1 |
9763350 | Rust et al. | Sep 2017 | B2 |
9763353 | Beall | Sep 2017 | B1 |
9795052 | Hsiao et al. | Oct 2017 | B2 |
9936611 | Beall et al. | Apr 2018 | B1 |
9949407 | Beall | Apr 2018 | B1 |
10058006 | Huang et al. | Aug 2018 | B2 |
10165703 | Adrian | Dec 2018 | B1 |
10178791 | Kho | Jan 2019 | B1 |
10240615 | Kho et al. | Mar 2019 | B1 |
10264698 | Kho et al. | Apr 2019 | B2 |
10354699 | Gopalkrishna et al. | Jul 2019 | B1 |
10372360 | Adrian | Aug 2019 | B2 |
10687435 | Adrian et al. | Jun 2020 | B2 |
20030112594 | Smith | Jun 2003 | A1 |
20030123221 | Liao | Jul 2003 | A1 |
20030183448 | Sleet et al. | Oct 2003 | A1 |
20030200472 | Midorikawa et al. | Oct 2003 | A1 |
20030200475 | Komoto | Oct 2003 | A1 |
20040052046 | Regimbal et al. | Mar 2004 | A1 |
20040227443 | Sandoval | Nov 2004 | A1 |
20050057909 | El-Batal et al. | Mar 2005 | A1 |
20050136747 | Caveney et al. | Jun 2005 | A1 |
20050162099 | Kemper | Jul 2005 | A1 |
20050182874 | Herz et al. | Aug 2005 | A1 |
20050238421 | Doerr et al. | Oct 2005 | A1 |
20060075155 | Fuller et al. | Apr 2006 | A1 |
20060134953 | Williams et al. | Jun 2006 | A1 |
20060146507 | Lee | Jul 2006 | A1 |
20060198097 | Kuwajima et al. | Sep 2006 | A1 |
20060274508 | LaRiviere et al. | Dec 2006 | A1 |
20070195542 | Metros et al. | Aug 2007 | A1 |
20070230111 | Starr et al. | Oct 2007 | A1 |
20070233781 | Starr | Oct 2007 | A1 |
20070234081 | Makino et al. | Oct 2007 | A1 |
20080007913 | Sullivan et al. | Jan 2008 | A1 |
20080056844 | Aukzemas et al. | Mar 2008 | A1 |
20080117569 | Lee | May 2008 | A1 |
20080174949 | Lai et al. | Jul 2008 | A1 |
20080195786 | Lee | Aug 2008 | A1 |
20080239650 | Fujie et al. | Oct 2008 | A1 |
20080264192 | Christensen | Oct 2008 | A1 |
20090245745 | Krampotich et al. | Oct 2009 | A1 |
20090271950 | Wang | Nov 2009 | A1 |
20090274429 | Krampotich et al. | Nov 2009 | A1 |
20090310303 | Najbert | Dec 2009 | A1 |
20100153608 | Olesiewicz et al. | Jun 2010 | A1 |
20100195304 | Takao | Aug 2010 | A1 |
20100296791 | Makrides-Saravanos et al. | Nov 2010 | A1 |
20110208937 | Hayashi et al. | Aug 2011 | A1 |
20110273850 | Chen | Nov 2011 | A1 |
20110299237 | Liang | Dec 2011 | A1 |
20110309730 | Retchloff et al. | Dec 2011 | A1 |
20120004772 | Rahilly et al. | Jan 2012 | A1 |
20120020006 | Xu et al. | Jan 2012 | A1 |
20120134086 | Zhang | May 2012 | A1 |
20120230815 | Teramoto et al. | Sep 2012 | A1 |
20120243170 | Frink et al. | Sep 2012 | A1 |
20120257360 | Sun | Oct 2012 | A1 |
20120305745 | Chen et al. | Dec 2012 | A1 |
20120320519 | Wu et al. | Dec 2012 | A1 |
20130050955 | Shinsato | Feb 2013 | A1 |
20130058054 | Zhou | Mar 2013 | A1 |
20130162127 | Hu | Jun 2013 | A1 |
20130258580 | Nakayama | Oct 2013 | A1 |
20130325183 | Rahilly | Dec 2013 | A1 |
20140111930 | Henderson | Apr 2014 | A1 |
20140118936 | Merlet et al. | May 2014 | A1 |
20140187068 | Chia et al. | Jul 2014 | A1 |
20140191636 | Li | Jul 2014 | A1 |
20140203696 | Rust et al. | Jul 2014 | A1 |
20140247569 | Foisy et al. | Sep 2014 | A1 |
20140362521 | Pronozuk et al. | Dec 2014 | A1 |
20140369002 | Takeuchi et al. | Dec 2014 | A1 |
20150156912 | Liang et al. | Jun 2015 | A1 |
20150163946 | Kyle et al. | Jun 2015 | A1 |
20150208548 | Chu et al. | Jul 2015 | A1 |
20150235673 | Lo | Aug 2015 | A1 |
20150320204 | Byrne et al. | Nov 2015 | A1 |
20150380059 | Bell et al. | Dec 2015 | A1 |
20160018859 | Mao et al. | Jan 2016 | A1 |
20160042768 | Yang et al. | Feb 2016 | A1 |
20160150659 | Chen et al. | May 2016 | A1 |
20160150667 | Xu et al. | May 2016 | A1 |
20160330858 | Ehlen | Nov 2016 | A1 |
20160381824 | Chu | Dec 2016 | A1 |
20170325361 | Chen et al. | Nov 2017 | A1 |
20180027059 | Miller | Jan 2018 | A1 |
20180168071 | Edge et al. | Jun 2018 | A1 |
20180260349 | Mondal et al. | Sep 2018 | A1 |
20190069432 | Kho et al. | Feb 2019 | A1 |
20190069440 | Adrian | Feb 2019 | A1 |
20190073008 | Adrian | Mar 2019 | A1 |
20190075668 | Adrian et al. | Mar 2019 | A1 |
20190079565 | Adrian | Mar 2019 | A1 |
20190090374 | Kho et al. | Mar 2019 | A1 |
20190090376 | Kho et al. | Mar 2019 | A1 |
20190098795 | Adrian | Mar 2019 | A1 |
Number | Date | Country |
---|---|---|
10 2009 023 341 | Feb 2011 | DE |
2 896 852 | Jul 2015 | EP |
Entry |
---|
Final Office Action received for U.S. Appl. No. 15/687,406 dated Sep. 12, 2018, 13 pages. |
Notice of Allowance received for U.S. Appl. No. 15/687,406 dated Dec. 19, 2018, 23 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/708,075 dated Feb. 10, 2020, 36 pages. |
Final Office Action received for U.S. Appl. No. 15/708,075 dated Jul. 17, 2020, 37 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/713,609 dated Jun. 26, 2018, 33 pages. |
Notice of Allowance received for U.S. Appl. No. 15/713,609 dated Nov. 15, 2018, 28 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/688,830 dated Sep. 5, 2018, 54 pages. |
Final Office Action received for U.S. Appl. No. 15/688,830 dated Mar. 19, 2019, 5 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/688,830 dated Jul. 30, 2019, 20 pages. |
Notice of Allowance received for U.S. Appl. No. 15/688,830 dated Feb. 10, 2020, 36 pages. |
Jason David Adrian et al.; Apparatus, System, and Method for Reconfigurable Media-Agnostic Storage; U.S. Appl. No. 15/694,068, filed Sep. 1, 2017. |
Jason David Adrian; Apparatus, System, and Method for Indicating the Status of and Securing Hard Drives; U.S. Appl. No. 15/700,112, filed Sep. 9, 2017. |
Jason David Adrian; Apparatus, System, and Method for Directing Air in a Storage-System Chassis; U.S. Appl. No. 15/689,650, filed Aug. 29, 2017. |
Jason David Adrian et al.; Apparatus, System, and Method for Securing Hard Drives in a Storage Chassis; U.S. Appl. No. 15/697,405, filed Sep. 6, 2017. |
Jason David Adrian; Apparatus, System, and Method for Detecting Device Types of Storage Devices; U.S. Appl. No. 15/698,540, filed Sep. 7, 2017. |
Chuankeat Kho et al.; Removeable Drive-Plane Apparatus, System, and Method; U.S. Appl. No. 15/693,362, filed Aug. 31, 2017. |
Chuankeat Kho et al.; Systems and Methods for Mounting Assembly Pullhandles; U.S. Appl. No. 15/687,406, filed Aug. 25, 2017. |
Jason David Adrian; An Apparatus, System, and Method for Reconfiguring Air Flow Through a Chassis; U.S. Appl. No. 15/716,251, filed Sep. 26, 2017. |
Jason Adrian; Introducing Bryce Canyon: Our next-generation storage platform; https://code.facebook.com/posts/1869788206569924/introducing-bryce-canyon-our next-generation-storage-platform/; Mar. 8, 2017. |
Jason Adrian et al.; Bryce Canyon Storage Specification; Jan. 31, 2017. |
Open Compute Project; http://opencompute.org/; as accessed Sep. 29, 2017. |
Jason David Adrian; Data-Center Drawer and Cable Track Assembly; U.S. Appl. No. 15/720,647, filed Sep. 29, 2017. |
Sisson; How Facebook Does Storage; https://thenewstack.io/facebook-storage. |
What's the Difference Between SATA and SAS Hard Drives?; https ://www.pickaweb.co. uk/kb/difference-between-sata-sas-hard-drives/. |
Chuankeat Kho; Apparatus, System, and Method for Securing Computing Components to Printed Circuit Boards; U.S. Appl. No. 15/713,607, filed Sep. 23, 2017. |
Chuankeat Kho et al.; Apparatus, System, and Method for Partitioning a Storage-System Chassis; U.S. Appl. No. 15/708,069, filed Sep. 18, 2017. |
Chuankeat Kho et al.; Apparatus, System, and Method for Dampening Vibrations Generated by Exhaust Fans; U.S. Appl. No. 15/713,609, filed Sep. 23, 2017. |
Chuankeat Kho et al.; Apparatus, System, and Method for Resisting Shock to a Data-Center Rack; U.S. Appl. No. 15/708,075, filed Sep. 18, 2017. |
Acoustic Attenuation; https://en.wikipedia.org/wiki/Acoustic attenuation; Oct. 22, 2012. |
Electromagnetic Shielding; https://en.wikipedia.org/wiki/Electromagnetic_shielding; May 15, 2016. |
Non-Final Office Action received for U.S. Appl. No. 15/700,112 dated Aug. 9, 2018, 15 pages. |
Final Office Action received for U.S. Appl. No. 15/700,112 dated Jan. 2, 2019, 10 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/700,112 dated May 30, 2018, 13 pages. |
Notice of Allowance received for U.S. Appl. No. 15/700,112 dated Oct. 2, 2019, 64 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/689,650 dated Sep. 24, 2018, 38 pages. |
Notice of Allowance received for U.S. Appl. No. 15/689,650 dated Feb. 28, 2019, 44 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/716,251 dated Aug. 8, 2019, 50 pages. |
Final Office Action received for U.S. Appl. No. 15/716,251 dated Jan. 13, 2020, 39 pages. |
Notice of Allowance received for U.S. Appl. No. 15/716,251 dated Apr. 22, 2020, 49 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/720,647 dated May 18, 2018, 45 pages. |
Notice of Allowance received for U.S. Appl. No. 15/720,647 dated Aug. 15, 2018, 23 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/697,405 dated Jun. 7, 2018, 33 pages. |
Final Office Action received for U.S. Appl. No. 15/697,405 dated Dec. 13, 2018, 46 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/697,405 dated May 21, 2019, 64 pages. |
Notice of Allowance received for U.S. Appl. No. 15/697,405 dated Oct. 31, 2019, 60 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/698,540 dated Nov. 14, 2018, 40 pages. |
Notice of Allowance received for U.S. Appl. No. 15/698,540 dated May 30, 2019, 29 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/694,068 dated Nov. 19, 2018, 18 pages. |
Notice of Allowance received for U.S. Appl. No. 15/694,068 dated Mar. 15, 2019, 23 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/693,362 dated Dec. 19, 2019, 53 pages. |
Notice of Allowance received for U.S. Appl. No. 15/693,362 dated Apr. 2, 2020, 33 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/713,607 dated Apr. 16, 2018, 39 pages. |
Notice of Allowance received for U.S. Appl. No. 15/713,607 dated Sep. 6, 2018, 22 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/708,069 dated Apr. 30, 2019, 52 pages. |
Notice of Allowance received for U.S. Appl. No. 15/708,069 dated Oct. 23, 2019, 54 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/687,406 dated Mar. 21, 2018, 33 pages. |
Number | Date | Country | |
---|---|---|---|
Parent | 15688830 | Aug 2017 | US |
Child | 16876159 | US |