TABLE OF CONTENTS
Executive Summary . . . . . . . . . . . . . . . . . . . . . . . 1
Red Hat® OpenShift® Market Momentum . 2
The Supermicro® SuperBlade® powered by
AMD EPYC™ Processors . . . . . . . . . . . . . . . . . . . 4
Red Hat® OpenShift® on SuperBlade® –Reference Architecture . . . . . . . . . . . . . . . . . . . . 5
Reference SuperBlade® BOM………………23
Key Takeaways and Business Values….…..24

SUPERMICROSupermicro (Nasdaq: SMCI) is the leading
innovator in high-performance, highefficiency server and storage technology
and a premier provider of advanced server
Building Block Solutions® for Enterprise
Data Center, Cloud Computing, Artificial
Intelligence, and Edge Computing
Systems worldwide. Supermicro iscommitted to protecting the environment
through its “We Keep IT Green®” initiativeby providing customers with the mostenergy-efficient, environmentally friendly
solutions available on the market.

Supermicro SuperBlade with AMD EPYCTM processors powers hybrid cloud deployments

Executive Summary

Organizations must deliver applications, features, and services at the speed theirbusinesses require across increasingly diverse IT environments as technologicalinitiatives such as cloud migration, containerization, and microservices take hold.
These technologies offer the promise of more efficient and effective IT services, but
it can be challenging for organizations to realize these benefits without proper
technological platforms and solutions. Building innovative applications requires
cloud-native development to deliver great results with agility. Red Hat customers
leverage Red Hat® OpenShift® as a unified development platform to streamline
their application development efforts across their heterogeneous IT environments.
The Red Hat® OpenShift® platform empowers organizations to deliver more applications and features in less time whileproviding the functionality to their customers and business lines. These organizations thus derive significant additional value
from the higher productivity of their DevOps and application development teams by generating more revenue and making
their application development efforts more cost effective.
Server hardware innovations play a crucial role. This paper guides you through deploying and validating basic Red Hat®
OpenShift® Container Platform 4.8 functionality on Supermicro® SuperBlade® bare metal systems.

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 2022

1

Red Hat® OpenShift® Market Momentum:
Red Hat OpenShift Container Platform (OCP) provides enterprise Kubernetes bundled CI/CD pipelines. It automates builds anddeployments, enabling developers to focus on application logic while leveraging best-of-class enterprise infrastructure.
Forrester reports that the Red Hat OpenShift Container Platform leads the growing enterprise App Container market.

Figure 1: The Forrester Wave
Forrester 1 says that "Red Hat OpenShift is the most widely deployed multi-cloud container platform and boasts powerfuldevelopment and unified operations experiences across many public and on-premises platforms. Red Hat pioneered the‘operator’ model for infrastructure and application management and provides a rich partner ecosystem and popularmarketplace."

1 - The Forrester Wave™: Multicloud Container Development Platforms, Q3 2020: The Eight Providers That Matter Most and How They Stack Up Sep 2020

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 2022

2

Applications are the competitive differentiator in today’s market. Deploying cloud-native applications represents anopportunity to build recurring revenues, highmargin services, and platform renewals.
According to Gartner 2, “By 2025, more than
85% of global organizations will be running
containerized applications, a significant
increase from fewer than 35% in 2019.”

Red Hat OpenShift Container Platform
Red Hat OpenShift Container Platform is an open-source container application platform built primarily on Docker containers
and orchestrated using Kubernetes container cluster Red Hat OpenShift management. Red Hat OpenShift supports a broad
range of programming languages and services ranging from web frameworks, databases, or connectors to mobile devices andexternal back ends. The Red Hat OpenShift platform supports both cloud-native, stateless applications and traditional,
stateful applications.
The primary IT initiatives that Red Hat OpenShift targets are:•Accelerating application delivery with agile and DevOps methodologies: Red Hat OpenShift offers a common
platform for development and operations teams to ensure consistency and standardization of application
components, eliminate configuration errors, automate deployment, and enable a controlled rollout of newcapabilities into production and rollback in the event of a failure. Additional capabilities enforce policies and rolebased access control for environments with elevated security and regulatory requirements.

•

Modernizing application architectures toward microservices: Red Hat OpenShift provides a common platform forcloud-native microservices applications alongside existing traditional stateful applications. A broad choice of
application frameworks, programming languages, and developer tools empowers customers to prototype innovative
applications more quickly. Red Hat OpenShift also allows access to a broad range of Red Hat and third-party services,
application and middleware services, API management, and storage services.

•

Adopting a consistent application platform for hybrid cloud deployments: IT organizations that want to decouple
application dependencies from the underlying infrastructure adopt container technology to migrate and deploy
applications across multiple cloud environments and data centers. Red Hat OpenShift provides a consistent
application development and deployment platform regardless of the underlying infrastructure. It also provides
operations teams with a scalable, secure, and enterprise-grade application platform and unified container and cloud
management capabilities.

Red Hat OpenShift is commonly delivered as either:•

Red Hat OpenShift Container Platform for enterprise customers that want to deploy and manage Red Hat OpenShiftin their own datacenter or at a public cloud provider.

•

As a cloud-based service.

2 - Gartner Infrastructure, Operations, and Cloud Summit 2020

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 2022

3

The Supermicro® SuperBlade® powered by AMD EPYC™ Processors
SUPERMICRO AMD SUPERBLADE

8U SuperBlade Server System Enclosure
SBE-820H/C/J/L-822/622/422

Supermicro SuperBlade is built for the most demanding workloads that require
high CPU density and the fastest networking available today. Supermicro's new
generation blade portfolio is designed to optimize the TCO of key components fortoday's datacenters, such as cooling, power efficiency, node density, andnetworking management. In addition, the Supermicro SuperBlade powered by 3rd
Gen AMD EPYC™ Processors is a trusted platform that meets enterprise customer
demands for on-premises private/hybrid cloud deployments.
The Supermicro SuperBlade comes in an 8U chassis, accommodates up to 20 hotpluggable single socket nodes, and delivers high performance with AMD EPYC™
Processors and DDR4 3200MHz memory, and fast I/O with PCIe® Gen4. There are 3
AMD powered SuperBlade models available, a SAS model, a SATA model, and a GPU
accelerated model, all of which can be mixed in a single 8U enclosure. The 8U
SuperBlade can support up to 40 single width GPUs or 20 double width GPUs.
SuperBlade SAS/SATA models support AIOM for front I/O, which extends the Open
Compute Project 3.0 specification to support a wide range of networking options ina small size form factor. The 8U SuperBlade also provides customers with advanced
networking options, such as 200G HDR InfiniBand or 25G Ethernet switches.
The Supermicro SuperBlade offers the significant advantage of sharing cooling andpower between the server blades to reduce power consumption compared toindividual rackmount servers that contain their own non-sharable fans and power
supplies. Supermicro is also committed to protecting the environment through our“We Keep IT Green®” initiative that provides customers with the most energyefficient, environmentally-friendly solutions available on the market.

SBA-4114S-C2N
AIOM for Front I/O

SBA-4119SG
GPU /PCIe Cards

Each SuperBlade enclosure contains at least one Chassis Management Module(CMM). The CMM allows administrators to remotely manage and monitor server
blades, power supplies, cooling fans, and networking switches. SuperCloud
Composer (SCC) is a composable cloud management platform that provides aunified dashboard to administer software-defined data centers. SCC canorchestrate cloud workloads via the streamlined industry-standard Redfish API.
SCC can also monitor and manage a broad portfolio of multi-generation
Supermicro servers from a single pane of glass, including SuperBlade.
The new 3rd Gen AMD EPYC 7003 Series Processors are built around the "Zen3" corethat delivers up to 19% more instructions per cycle than previous generations andcontains up to 64 cores per socket for industry-leading performance on popularbenchmarks and real-world workloads. As a result, Supermicro and AMD have set
multiple world records for performance. 3

Supermicro's high performance, density
optimized, and energy-efficientrd
The
SupermicroSuperBladepoweredSuperBlade®
can significantly
reduceinitialby 3 Gen AMD EPYC processors includes a range of compute systems designed formanythemost demanding
capitalofandoperational
expenses.applications: Artificial Intelligence (AI), Machine Learning (ML), High Performance Computing(HPC), enterprise applications, and cloud deployments. These systems help organizations reduce time-to-solution for a wide
3 - https://www.amd.com/en/processors/epyc-world-records

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 2022

4

range of applications, add advanced security features, and allow all workloads to run either on-prem or in a public or private
cloud. The Supermicro SuperBlade offers the highest density, maximum performance, best power efficiency, and lowest Total
Cost of Ownership (TCO).

Supermicro and Red Hat
Supermicro and Red Hat are working together to offer proven, validated solutions and reference architectures across multiple
Red Hat software platforms, including Red Hat OpenShift. This collaboration involves careful engineering and testing thatremoves much of the time, risk, and time required to deploy modern hybrid cloud infrastructure, allowing organizations tofocus on their applications.

Red Hat OpenShift on SuperBlade – Reference Architecture
Customers requiring a bare metal on-premise container platform solution can use the new Red Hat feature-assisted installer
available from https://cloud.redhat.com/openshift/install/metal.
A fully-populated 20-node SuperBlade in an 8U Chassis can be configured as:•

1 admin/provisioner node for the Red Hat OpenShift cluster.

•

3 Red Hat OpenShift master nodes to manage the Kubernetes cluster and schedule pods to run on worker nodes.

•

4 Red Hat OpenShift container-native storage nodes to provide containers with persistent storage.

•

8 Red Hat OpenShift worker nodes to host the application pods.

•

3 Red Hat OpenShift infrastructure nodes to run routing services, the container application registry.

•

1 load balancer node.

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 20225

1 admin node,
3 Master Nodes(Manage K8S Cluster, schedule
pods to run on worker nodes)•••

8 Worker Nodes (host the application
pods)
3 Infra Nodes (routing, registry)
1 Load Balancer (HAProxy)
4 Container Native
Storage Nodes

Persistent
VolumesFigure 2: Deploying Red Hat OpenShift Container Platform on Supermicro SuperBlade

Installation Overview
The assisted installer focuses on bare-metal deployments and helps simplify Red Hat OpenShift Container Platform (OCP)
installation. The service discovers and validates targeted hardware and significantly improves installation success rates. Thissection guides you through installing the Red Hat SaaS portal to deploy an OCP cluster using Supermicro SuperBlade ascontrol plane nodes for compute/storage resources. The benefits of containerization include:•

Highly available control plane nodes via affinity rules.

•

Resource consolidation for physical hosts.

•

Simplified backup and restore.

Note: A fully-populated Supermicro SuperBlade can accommodate 20 nodes; however, this white paper uses seven nodes fortesting this deployment.
The prerequisites for deploying OCP are:1.

Shared VLAN: The assisted installer requires all nodes to be present on the same VLAN to use a virtual IP address forboth ingress and API.

2.

DHCP: The shared VLAN requires DHCP, much like an Installer-Provisioned Installation (IPI).

3.

DNS: The cluster requires DNS records for ingress and API access. The assisted installer supports creating theserecords for the user via route53, but in this white paper, the following DNS records have been created.

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 2022

6

File: Sample DNSMASQ (/etc/dnsmasq.d) Configuration file used in this white paper
Dnsmasq is a lightweight, easy to configure, DNS forwarder, and DHCP server. It is designed to provide DNS and,optionally, DHCP to a small network.
# DHCP and Forward & Reverse DNS configuration# /etc/dnsmasq.d/domain_name.conf# Don't use /etc/resolv.conf
no-resolv
interface=baremetal#interface=lo
listen-address=<Enter Listen_IP_addr here>bind-interfaces# Don't use /etc/hosts
no-hosts# Recursive DNS
server=<Enter server_IP_addr here># Set local domain
domain=<Enter domain_name here>#### DHCP (dnsmasq --help dhcp)
dhcp-range=<Enter start_IP_addr, end_IP_addr here>#set DHCP options
dhcp-option=<Enter option:netmask,subnet_netmask_24 here>
dhcp-option=<Enter option:router,router_IP_addr here>
dhcp-option=<Enter option:dns-server,dns-server_IP_addr here># External API endpoint (External API VIP)
address=<Enter /api.domain_name/endpoint_IP_addr here># Internal API endpoint (Internal API VIP)
address=<Enter /api-int.domain_name/endpoint_IP_addr here># wildcard domain *.apps.<clusterName>.<baseDomain> (Ingres VIP)
address=<Enter /.apps.domain_name/ingres_IP_addr here># master0 / etcd-0
dhcp-host= <Enter master0_MAC_addr,master0_IP_addr,master-0.domain_name here>
address=<Enter /master-0.domain_name/master0_IP_addr here>
ptr-record=<Enter master0_ptr-record_IP_addr.in-addr.arpa,master-0.domain_namehere># master1 / etcd-1
dhcp-host= <Enter master1_MAC_addr,master1_IP_addr,master-1.domain_name here>
address=<Enter /master-1.domain_name/master1_IP_addr here>
ptr-record=<Enter master1_ptr-record_IP_addr.in-addr.arpa,master-1.domain_namehere># master2 / etcd-2
dhcp-host= <Enter master2_MAC_addr,master2_IP_addr,master-2.domain_name here>
address=<Enter /master-2.domain_name/master2_IP_addr here>
ptr-record=master2_ptr-record_IP_addr.in-addr.arpa,master-2.domain_name here>

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 2022

7

# worker1
dhcp-host= <Enter worker1_MAC_addr,worker1_IP_addr,worker-1.domain_name here>
address=<Enter /worker-1.domain_name/worker1_IP_addr here>
ptr-record=<Enter worker1_ptr-record_IP_addr.in-addr.arpa,worker-1.domain_namehere># worker2
dhcp-host= <Enter worker2_MAC_addr,worker2_IP_addr,worker-2.domain_name here>
address=<Enter /worker-2.domain_name/worker2_IP_addr here>
ptr-record=<Enter worker2_ptr-record_IP_addr.in-addr.arpa,worker-2.domain_namehere># worker3
dhcp-host= <Enter worker3_MAC_addr,worker3_IP_addr,worker-3.domain_name here>
address=<Enter /worker-3.domain_name/worker3_IP_addr here>
ptr-record=<Enter worker3_ptr-record_IP_addr.in-addr.arpa,worker-3.domain_namehere>## END OF FILE

Node Requirements•

CPU architecture: All nodes must use x86_64 CPU architecture.

•

Identical nodes: Red Hat recommends that all nodes in a single cluster share an identical configuration (brand,
model, CPU, RAM, and storage).

•

Baseboard Management Controller access: The provisioner node must be able to access the Baseboard
Management Controller (BMC) of each OCP cluster node using either IPMI, Redfish, or a proprietary protocol.

•

Latest generation: IPI relies on BMC protocols that must be compatible across nodes. All nodes must be recent
enough to support RHEL 8 for the provisioner node and RHCOS 8 for the control plane and worker nodes.
Additionally, RHEL 8 ships with the most recent RAID controller drivers.

•

Registry node: (Optional) If you are setting up a disconnected mirrored registry, then Red Hat recommends having
the registry reside in its own node.

•

Provisioner node: IPI requires one provisioner node.

•Control plane: IPI requires three control plane nodes for high availability.

•

Worker nodes: While not required, a typical production cluster has one or more worker nodes. Smaller clusters are
more resource-efficient for administrators and developers during development, production, and testing.

•

Network interfaces: Each node must have at least one 10 Gigabit Ethernet (GbE) network interface for theroutable bare metal network. By default, each node must also have one 10GbE network interface for

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 20228

a provisioning network when using the provisioning network for deployment. Network interface names must follow
the same naming convention across all nodes. For example, the first NIC name on a node, such as eth0 or eno1,
must be the same name on all the other nodes. The same principle applies to the remaining NICs on each node.
•

Unified Extensible Firmware Interface (UEFI): Installer-provisioned installation requires UEFI boot on all OCP
nodes when using IPv6 addressing on the provisioning network. UEFI Device PXE settings must also be set to use theIPv6 protocol on the provisioning network NIC. (Omitting the provisioning network removes this requirement.)

One of the master nodes will be used to bootstrap the cluster and then converted into another master node. Both the
kubeconfig and a link to the cluster console will be available for download once the cluster installation is complete.
Configure the node BIOS settings for the virtual CD mount and enable virtualization for the hyper-converged nodes. Next,
configure the nodes by assigning a hostname and an IP address along with the desired IPMI user name and password, as
shown below.

Blade #

Hostname

IPMI IP

IPMI User

IPMI PW

B1

admin

172.17.41.80

SMCI

Super123

B2

master-0

172.17.41.81

SMCI

Super123

B3

master-1

172.17.41.82

SMCI

Super123

B4

master-2

172.17.41.83

SMCI

Super123

B5
B6
B7

worker-1
worker-2
worker-3

172.17.41.84
172.17.41.85
172.17.41.86

SMCI
SMCI
SMCI

Super123
Super123
Super123Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 2022

9

Step 1Set Boot Mode
Select to UEFI.

Step 2Set Boot Option#1 to the correct
UEFI boot disk.

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 202210

Step 3Set SVM Mode to
Enabled to enable
CPU virtualization.

Step 4Set SR-IOVSupport toEnabled.

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 2022

11

Step 5Set IOMMU to
Enabled.

Step 6
Set PCI AER
Support toEnabled.

Step 7
Download theSupermicro IPMI
tool toSMCIPMITool is an out-of-band Supermicro utility that allows users to interface with SuperBladesystems and IPMI devices via the Command Line Interface (CLI). It is available here.
https://www.supermicro.com/SwDownload/SwSelect_Free.aspx?cat=IPMIRed Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 202212

mount/unmountUSB virtual media
and System Power
Control.

Step 8Log in to
the portal using
your Red Hat
credentials. This
will auto-populate
any pull secrets
required to pullcontainer images
associated withthe account. Oncelogged in, click theCreate Cluster
button to start the
new OCPinstallation.

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 2022

13

Enter the desiredcluster name andthe version of Red
Hat OpenShift tobe deployed.
This example uses
ldc2-sanjose as
the cluster name.
Click Next tocontinue.

Step 9Click theGenerate
Discovery ISO
button.

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 2022

14

Step 10
Provide the SSH
public key of theadmin/provisioner
node from where
you can manage
the cluster.
Click theGenerate
Discovery ISO
button.

Step 11
Download the
Discovery ISO to a
Samba file shareor webserver from
where you canmount the image
using theSupermicrocommand line
tools.

Step 12Unmount any
existing virtual
media from allcontrol andcompute nodes
Step 13
Mount thedownloaded Red
Hat OpenShiftfor i in {1..6};
do ./SMCIPMITool 172.17.41.8$i SMCI Super123 wsiso umount;done

for i in {1..6};
do ./SMCIPMITool 172.17.41.8$i SMCI Super123 wsiso mount/share/discovery_image_ldc2-sanjose.iso;done

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 2022

172.17.41.1

15

install virtual
media, which canbe either an SMB
share or http URL
for thedownloaded ISO.
This example uses
an SMB share.
Step 14
Set the one-timebootable device tothe virtual USB
media as in Step
7.

for i in {1..6};
do ./SMCIPMITool 172.17.41.8$i SMCI Super123 ipmi power bootoption 13;
done

Step 15
Check the power
status of all
master andworker nodes.

for i in {1..6};
do ./SMCIPMITool 172.17.41.8$i SMCI Super123 ipmi power status;
done

Reset or turn on
the power tomount the onetime virtual USB
media which was
set in step 13,

for i in {1..5};
do ./SMCIPMITool 172.17.41.8$i SMCI Super123 ipmi power reset;
doneOr
for i in {1..5};
do ./SMCIPMITool 172.17.41.8$i SMCI Super123 ipmi power up;
done

Step 16
The inventory
should look likethis once theservers boot withthe discovery
image and theinventory isfinished.

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 2022

16

Step 17
Assign theappropriate roles
and hostnames
for the systems.
Check the Install
OpenShift
Virtualization
and Install
OpenShiftContainer
Storagecheckboxes forthehyperconverged
worker nodes.
Step 18
Either add the API
and ingress VIPs
or allow DCHP
assignment.
This example uses
software-defined
networking.

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 2022

17

Step 19
Click the Install
Cluster button to
begin the baremetal/VM cluster
installation.

Step 20
One of themasters will be
used to bootstrap
the cluster thenconverted intoanother masternode.
The kubeconfig
and a link to thecluster console
will be available
for download
once the cluster
installation
completes.
Step 21Once theinstallation iscomplete, you canlog in to theconsole with theprovided DNS
entries and the
kubeadmin
password.
Download the
kubeconfig file for
the OCP CLI tools.

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 2022

18

Step 22
Add the DNS
entries to yourexternal DNS(preferred) or
localhost file.

(Local /etc/hosts)

Step 23
Launch the OCP
console byclicking the“LaunchOpenShift
Console” in theabove step 21 andlogin with the
kubeadmin and its
passwords
recorded in Step
20.

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 2022

19

Step 24
Access the OCP
Nodes screen.

Step 25
Export the
downloaded
kubeconfig file to
run the OCP
commands.
Step 26
Get the Red Hat
OpenShift nodes
status.

Step 27
Get the installed
Red Hat OpenShiftversion.

export KUBECONFIG=/home/kni/kubeconfig[kni@provisioner ~]$ oc get nodes
NAME
STATUS
ROLES
AGE
master-0
Readymaster50m
master-1
Readymaster52m
master-2
Readymaster33m
worker-1
Readyworker37m
worker-2
Readyworker37m
worker-3
Readyworker38m[kni@provisioner ~]$ oc version
Client Version: 4.8.4
Server Version: 4.8.2

Red Hat® OpenShift® on Supermicro® SuperBlade®

VERSIONv1.21.1+051ac4f
v1.21.1+051ac4f
v1.21.1+051ac4f
v1.21.1+051ac4f
v1.21.1+051ac4f
v1.21.1+051ac4f©Supermicro, Inc. January, 2022

20

Figure 3: Topology diagram – Red Hat OpenShift admin, master, and worker node deployment on Supermicro SuperBlade

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 2022

21

Figure 4: Red Hat OpenShift control plane nodes
The installer automatically destroys the bootstrap VM and moves the virtual IP addresses (VIPs) to the control plane nodes
when the Red Hat OpenShift control plane node installation is complete and fully operational.

Figure 5: Red Hat OpenShift control plane nodes fully operational

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 2022

22

Reference SuperBlade BOM
The Bill of Materials (BOM) used for the Red Hat OpenShift Container Platform installation described in this white paper
includes:ADMIN NODE(x1)Part Type
System

SBA-4114S-C2N

Processor
MemoryInternal Storage(for Operating
System)Internal Storage(for Data)

PSE-MLN7543P-001
MEM-DR416L-SL02-ER32

Part Description
Supermicro SuperBlade (AMD Powered SingleSocket SAS model)
3rd Gen AMD EPYC™ 7003 Series Processor(7543P - 32 Cores, 2.8GHz, 225W TDP)
16GB DDR4-3200

HDS-IMN0-SSDPELKX020T8

2 TB M.2 NVMe SSD

Part Type
SystemProcessor
MemoryInternal Storage(for Operating
System)Internal Storage(for Data)
Part Type
SystemProcessor
MemoryInternal Storage(for Operating
System)Internal Storage(for Operating
Data)

Part #

HDS-IUN2-SSDPE2KX020T8
2 TB U.2 NVMe SSD
MASTER NODES(x3)Part #Part Description
Supermicro SuperBlade (AMD Powered SingleSBA-4114S-C2N
Socket SAS model)
3rd Gen AMD EPYC™ 7003 Series Processor
PSE-MLN7543P-001(7543P - 32 Cores, 2.8GHz, 225W TDP)
MEM-DR432L-SL02-ER32
32GB DDR4-3200

HDS-IMN0-SSDPELKX020T8

2 TB M.2 NVMe SSD

HDS-IUN2-SSDPE2KX020T8
2 TB U.2 NVMe SSD
WORKER NODES(x3)Part #Part Description
Supermicro SuperBlade (AMD Powered SingleSBA-4114S-C2N
Socket SAS model)
3rd Gen AMD EPYC™ 7003 Series Processor
PSE-MLN7763-0312(7763 – 64 Cores, 2.45GHz, 280W TDP)
MEM-DR464L-SL01-ER32
64GB DDR4-3200

Qty

2

1
1
8

2
Qty
1
1
8

2
2
Qty
1
1
8

HDS-IMN0-SSDPELKX020T8

2 TB M.2 NVMe SSD

2

HDS-IUN2-SSDPE2KX020T8

2 TB U.2 NVMe SSD

2

Red Hat® OpenShift® on Supermicro® SuperBlade®

©Supermicro, Inc. January, 2022

23

Key Takeaways and Business Values
Red Hat® OpenShift® Container Platform provides enterprise
Kubernetes bundled CI/CD pipelines, automated builds, anddeployments that allow developers to focus on application
logic while leveraging all best-of-class enterpriseinfrastructure.
Deploying Red Hat OpenShift on Supermicro® SuperBlade®
gives organizations a consistent application development
and deployment platform. Operations teams benefit fromthe scalable, secure, enterprise-grade application platform
with unified container and cloud management capabilities.
This validated reference architecture allows customers toefficiently design, deploy, and operate a containerized
DevOps/PaaS platform.
Supermicro SuperBlade powered by 3rd Gen AMD EPYC™ 7003
Series Processors allows Kubernetes to be run in production
environments with the operational efficiency andconsistency needed to meet various SLAs and IT initiatives. It
enables increased productivity, reduced total cost ofownership, and scalability into your datacenter.

Red Hat® OpenShift® on Supermicro® SuperBlade®

SUPERMICRO SUPERBLADE PROVIDES BUSINESSVALUES TO ENTERPRISE CUSTOMERS
Better performance per watt and per dollar
SuperBlade offers:• Maximum performance and highest density at lowest
cost.
• Cost benefits from reduced cabling, shared power andcooling efficiencies, and front serviceability.
Faster, better performance on cloud workloads
SuperBlade offers better performance with:• High-core-count 3rd Gen AMD EPYC™ processors.
• Unmatched network performance with 10/25/100 GbE
network switch connectivity.
• High bandwidth and low latency with 100/200 G
InfiniBand.
Greener environmental impact and lower TCO• Maximum power optimization using titanium-level
power supplies with 96% efficiency.
• Modular upgrades that reduce e-waste.

©Supermicro, Inc. January, 202224