Data Center Hardware
Data center hardware covers the physical equipment that provides compute, storage, and networking in a facility: servers, racks, switches, cabling, power distribution, cooling systems, and the design considerations that determine reliability, density, and efficiency.
itComputer architecture and hardware | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Don't Panic
Don't Panic - Data Center Hardware
Data Center Hardware is the subject of this course. A data center turns electrical power, floor space, cooling, and network links into computing capacity. Its hardware is a system, not a pile of servers.
The useful unit of work is a closed loop: clarify the goal and boundaries, gather the inputs the practice requires, make the decision or change, record evidence, and return with owners for the next cycle. Skipping any link leaves teams busy without durable results.
Tooling supports the loop; it does not replace it. Choose tools after the boundary and evidence model are clear. Comparing products without that model produces feature matrices that do not change how the work runs.
Common failure modes include undefined ownership, metrics that count activity instead of outcomes, and irreversible steps taken without a review path. Treat those as design defects in the practice, not as individual heroics to compensate later.
Operators should be able to explain which signals would change a decision this week. If no signal can change the plan, the practice has become ritual. Keep the feedback path short enough that evidence still influences the next cycle.
Name the owners for each stage of the loop before the work scales. Unowned stages become permanent exceptions. Record decisions with enough context that a future operator can tell why a tradeoff was accepted. Prefer fewer, sharper metrics that change behavior over broad dashboards that only describe activity after the fact.
Read the Intro for the core model. Use the Cheatsheet when you need the operating map. Updates tracks official guidance when this course configures an update source; otherwise the practice is settled without a live feed.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://www.opencompute.org/community/server
Supports
- Standardized server-system scope for scale computing
- Chassis, sled, rack-compatible, and modular server design categories
- Hardware lifecycle from validation and manufacturing through operation and decommissioning
- https://www.opencompute.org/wiki/Server/ProjectOlympus
Supports
- Modular rack architecture and integrated power distribution and management
- Server enclosures, power supplies, motherboards, PCI Express risers, storage, and accelerator modules
- Rack-level monitoring, power measurement, and power capping examples
- https://www.opencompute.org/wiki/Open_Rack/SpecsAndDesigns
Supports
- Rack as a consistent interface for information-technology equipment
- Current rack, power shelf, power monitoring, battery backup, and cooling-interface specifications
- Need to evaluate rack-level mechanical, power, and infrastructure compatibility
- https://handbook.ashrae.org/Handbooks/A19/IP/a19_ch20/a19_ch20_ip.aspx
Supports
- Relationship between component heat, server inlet conditions, airflow, and facility cooling
- Recommended and allowable environmental envelopes
- Heat-load assessment and matching cooling capacity to equipment
- Air-cooled and liquid-cooled equipment concepts
- Processor, memory, storage, input and output, power-supply, fan, and heat-sink thermal considerations
- https://www.ashrae.org/file%20library/technical%20resources/bookstore/ashrae_tc0909_power_white_paper_22_june_2016_revised.pdf
Supports
- Typical data center power-distribution system layers
- Power-equipment location and temperature considerations
- Need to evaluate power equipment within changing data center environments
- https://www.energystar.gov/products/enterprise_servers
Supports
- Rack, blade, and tower or pedestal server form-factor categories
- Processor socket, memory, power-supply, power-management, active, and idle energy criteria
- Energy efficiency as a procurement and configuration concern
- https://www.opencompute.org/community/storage
Supports
- Storage project scope covering devices, chassis, components, peripherals, and network-enabled storage
- Standardization, modularization, and compatibility as storage-hardware concerns
- https://www.opencompute.org/wiki/Networking/SpecsAndDesigns
Supports
- Data center leaf, spine, and top-of-rack switch design examples
- Switch port, transceiver, speed, airflow, power, and form-factor considerations
- Hardware specifications and design packages as compatibility evidence
- https://pcisig.com/specification-overview/pci-express-base
Supports
- PCI Express as an architecture for compliant systems and peripherals
- Interconnect attributes, fabric management, and programming interfaces
- PCI Express generation and system-interconnect compatibility context
- https://www.dmtf.org/sites/default/files/standards/documents/DSP0266_1.23.0.html
Supports
- Baseboard management controller as an embedded device or service for out-of-band monitoring and management
- Redfish as a model-oriented RESTful management standard
- Managed systems, chassis, managers, sensors, power, events, and resource relationships
- https://uefi.org/specifications
Supports
- Current UEFI, Platform Initialization, ACPI, and UEFI Shell specifications
- Platform firmware interfaces and structures used by operating-system loaders and operating systems
- Firmware initialization, boot, and update as documented platform concerns
