Introduction to Redfish

December, 2017
The Status Quo

Inefficient High barrier to Security Scaling Outdated Tools

architecture entry Risks Limitations • Layers needed to
• Designed for 8-bit • Protocols not • Can’t describe adapt to the
• Not developed current tool chain.
microarchitectures human readable modern systems
with security • Special Utilities,
of the past • Significant (i.e. multi-node)
focus libraries &
• Increased expertise required • Current specs do
• No security best reformatting
development cost to develop for not address scale
practices needed to meet
from using multiple legacy protocols data centers
deployed customer needs.
incompatible • Proprietary • As scale
protocols & tools protocols and increases, the • Layers on layers
• In-band access fragmentation from need to monitor • Inefficiencies in
differs from out-of- OEM extensions and manage representation and
band • Lack of efficiently number of IOs
interoperability increases
exponentially
What we did to fix the Status Quo
Bring forth a modern standard that advances
capabilities started by IPMI, SMASH, DASH, etc.

Build a consortium of industry leaders using an

existing standards body

Strive for broad adoption of specification across

industry to meet growing customer demand

Seed ecosystem with open source

Unprecedented level of interoperability

Expand scope to rest of Software Defined IT Infrastructure over time

How to Re-invent IT Management

Well defined management Scalable and extensible

interface that exposes data model
information directly to the purpose built for managing
modern tool chain Software Defined Hybrid IT

Interoperability
is key

Leverage web standards,

Human readable but
best practices &
machine capable
security methods.
A Hybrid IT Management Solution
• Leverage common Internet / Web Services standards, other standards where appropriate
• Represent modern hardware designs (standalone to scale-out, current silicon, OCP)
Design • Does not require a PhD to design or use.
Tenets • Separation of protocol from data model, allowing them to be revised independently

• HTTPS / SSL: Primary data transport

• SSDP from uPnP: Service Discovery
Protocol • HTTP-based alert subscription
Suite • Leverage OData v4

• Modern, standards-based
• Widely used for web services, software defined and public APIs
REST & • Easy for IT professionals and amateurs to utilize
JSON

• Schema-based, starting with CSDL & JSON Schema

•Prepare to add schema language definitions as market changes
Data • An easy to use data model that a human can just read
Model • Create new modeling tenants to facilitate ease of design (inheritance by copy, polymorphism by union)
Why REST, HTTP and JSON?

• REST: The API architecture

• Rapidly replacing SOAP
• HTTPS: The Web protocol
• Well-understood by admins
• Known security model
• Known network configuration
• JSON: Modern data format
• Human-readable
• Simpler than XML
• Modern language support
• The combination of language support and
ubiquity of REST, HTTP and JSON means that
IT management tasks can be performed using
the same skill set and tool chain as all other IT
and dev/ops tasks. JSON vs XML

6
Scalable Platforms Management Forum
(DMTF group that defines Redfish)
Co-Chairs: Jeff Autor (HPE), Mike Raineri (Dell)
SPMF Leadership Companies

SPMF Supporting Companies

American Megatrends, Inc., ARM, Inc., Artesyn Embedded Systems, Cray, Inc., Flex, Fujitsu,
Huawei, IBM, Insyde Software Corp., Mellanox Technologies, Microsemi, MPSTOR, NetApp,
OSIsoft, LLC, Quanta Computer, Solarflare Communications Toshiba, Western Digital
Corporation

SPMF Industry Alliance Partners & efforts

Open Compute Project – Collaborating on profile definition
UEFI – Collaborating on Firmware Update and Host Interface work
SNIA – Collaborating on Storage modeling / alignment between SNIA SSM and Redfish
TGG – Pursuing relationship to work on Power/Cooling (existing DMTF Alliance Partner)
IETF – working on Switch modeling (no official alliance)
ASHRAE – American Society of Heating, Refrigerating and Air Conditioning Engineers
BBF – Broadband Forum
What is Redfish?
• Industry Standard Software Defined
Management for Converged, Hybrid IT
• HTTPS in JSON format based on OData v4
• Schema-backed but human-readable
• Equally usable by Apps, GUIs and Scripts
• Extensible, Secure, Interoperable
• Version 1 focused on Servers
• A secure, multi-node capable replacement for IPMI-over-LAN
• Represent full server category: Rackmount, Blades, HPC, Racks, Future
• Intended to meet OCP Remote Machine Management requirement
• Expand scope over time to rest of IT infrastructure
• Additional features coming out approximately every 4 months
• Working with SNIA to cover more advanced Storage (Swordfish)
• Working with The Green Grid & ASHRAE to cover Facilities
(Power/Cooling)
• Work with the IETF to cover some level of Ethernet Switching
Redfish Resource Map (simplified)
Collection Singleton Subordinate
/redfish/v1 Resource Resource Resources
& Collections
Service Root /redfish/v1/Systems
./Systems/<id>
Collection of Systems
Computer Processors
Tasks "Logical view" System
Disks
Sessions
Computer Systems NICs
Accounts /redfish/v1/Chassis

Events ./Chassis/<id>
Collection of Chassis
Power
Registries "Physical view" Chassis
Thermal
Schemas
Managed By
/redfish/v1/Managers
./Managers/<id>
Collection of Managers
LogService
"Management" BMC
NW protocol

GET http://<ip-addr>/redfish/v1/Systems/{id}/Processors/{id}
Use the Redfish Resource Explorer (redfish.dmtf.org) to explore the resource map
Timeline of Redfish® Specification
• The DMTF Redfish technology
• Sep 2014: SPMF Formed in DMTF.
• Released multiple work-in-progress for public feedback
• Aug 2015: Redfish Specification with base models (v1.0)
• May 2016: Models for BIOS, disk drives, memory, storage, volume (2016.1)
• Aug 2016: Models for endpoint, fabric, switch, PCIe device, zone,
software/firmware inventory & update (2016.2)
• Dec 2016: Adv. communications devices (multi-function NICs), host
interface (KCS replacement), privilege mapping (2016.3)
• May 2017: Composability (2017.1)
• WIP for Telemetry
• Aug 2017: Location, errata (2017.2)
• WIPs for Ethernet Switching, DCIM, OCP & Profiles
• Alignment with other standard organizations
• Aug 2016: SNIA releases first model for network storage services
(Swordfish)
• Working with IETF to create an open YANG Redfish mapping algorithm
• DMTF created work registers with UEFI Forum, TGG, OCP, ASHRAE,
Broadband Forum, ETSI-NFV, ODCA for work on applying Redfish
Host Interface
• Replacement for IPMI KCS, etc.
• Exposes a NIC from Management
Controller to OS
• SMBIOS records provide information to
allow kernel access
• Same access in-band as out-of-band
• Kernel mode or user mode accessible
• Encouraging OS vendors to begin
consuming Redfish data.
• This means you can get to the iLO
homepage from the OS.
• This means you can write your tools for
the iLO homepage or Redfish and run
them in the host OS.
• Anything that accesses the out of band
can be run on the host OS to access to
local management subsystem.
Redfish Device Enablement: PLDM Redfish Providers
Server
Redfish Server Ethernet
REST Management Network
Client Controller Adapter

Any
Adapter
PMCI WG developing a standard to enable a server
Management Controller to present a Redfish-conformant I/O Adapter Operations:

management of I/O Adapters in a server without building in • Discovery

• Read properties (GET) Storage Storage
code specific to each adapter family/vendor/model. • Create/Delete resource
(POST/DELETE) Controller Device
• Update properties
• Support adapter “self-contained, self-describing” including •
(PATCH)
Custom Actions (POST)
value-add (OEM) properties • Tasks, Events, OEM
extensions
• New managed devices (and device classes) do not require
Management Controller firmware updates
• Support a range of capabilities from primitive to advanced
1
devices (lightweight/low bandwidth options) 2
• Leveraging PLDM, a provider architecture is being specified
that can binary encode the data in a small enough format for
devices to understand and support.
• MC acts as a broker to encode/decode the data to/from the
provider
• PLDM works over I2C & PCIe VDM. Additional mappings
under consideration.
Interoperability Profiles: Goals
• An “Interoperability Profile” provides a common ground for Service
implementers, client software developers, and users
• A profile would apply to a particular category or class of product (e.g. “Front-end
web server”, “NAS”, “Enterprise-class database server”)
• It specifies Redfish implementation requirements, but is not intended to mandate
underlying hardware/software features of a product
• Provides a target for implementers to meet customer requirements
• Provide baseline expectations for client software developers utilizing Redfish
• Enable customers to easily specify Redfish functionality / conformance in RFQs
• Create a machine-readable Profile definition
• Document must be human-readable
• Can be created by dev/ops personnel and non-CS professionals
• Enable authoring of Profiles by DMTF, partner organizations, and others
• Create open source tools to document and test conformance
Tools Task Force: Redfish Tools Description
SPMF Tools TF open source tools to enable Redfish http://www.dmtf.org/standards/opensource
Tool Description
CSDL Validator Validates the CSDL conforms to Redfish requirements
CSDL-to-JSON schema convertor Generates json-schema files from CSDL
Extend

Converts a YANG model into a set of Redfish CSDL files, enabling Ethernet switching
YANG to Redfish
standard access via Redfish
Document Generator Generates documentation from json-schema
Mockup Server Exposes a mockup as a static HTTP service (GETs only)
Working Svc

Mockup Creator Creates a mockup from a Redfish service

Profile Simulator Dynamic simulator of the proposed Redfish profile for OCP
Interface Emulator Emulate a Redfish interface statically or dynamically.
Service Validator Validates a Redfish service is conformant
JSON Schema Response Validator Validates any JSON resource against DMTF provided JSON schemas
Test

Reference Checker Validates the reference URLs in CSDL files

Use Case Checker Collection of tools to validate common use cases for Redfish Services.
Service Conformance Tool Verifies conformance of a Redfish service to assertions in the Redfish Specification
CLI (redfishtool) A command line tool for interacting with a Redfish service (similar to ipmitool)
A lightweight HTTPS server that can be executed to read and record events from a
Event Listener
Client

Redfish Service
C Library (libRedfish) C libraries for interacting with Redfish services
Python Utility & Library A Command line tool with UI and python libraries for interacting with Redfish services

14
Redfish Developer Hub: redfish.dmtf.org
• Resources
• Schema Index
• Specifications
• GitHub for Redfish Tools
• Registries
• Other Documentation
• Mockups
• Simple Rack-mounted Server
• Bladed System
• Proposed OCP Redfish Profile
• More being added
• Education/Community
• Redfish User Forum
• Whitepapers, Presentations
• YouTube shorts & Webinars

15
Thank you!

16
Backup Material

17
How simple is Redfish?

Example Python code to retrieve serial number from a server:

rawData = urllib.urlopen(‘http://192.168.1.135/redfish/v1/Systems/1’)
jsonData = json.loads(rawData)
print( jsonData[‘SerialNumber’] )

Output is:
1A87CA442K

Three lines of code: point to the resource, get the data, print the serial number.

*Example uses Redfish ComputerSystem resource

 Redfish v1.0 Feature Set
Retrieve “IPMI class” data Perform Common Actions
•Basic server identification and asset info • Reboot / power cycle server
•Health state • Change boot order / device
•Temperature sensors and fans • Set power thresholds
•Power supply, power consumption and thresholds

Basic I/O infrastructure data Access and Notification

•Host NIC MAC address(es) for LOM devices • Serial console access via SSH
•Simple hard drive status / fault reporting • Alert / event notification method(s)
• Event Log access method(s)
Discovery
•Service endpoint (network-based discovery)
BMC infrastructure
•System topology (rack/chassis/server/node)
• View / configure BMC network settings
• Manage local BMC user accounts
Security
•Session-based leverages HTTPS Working on more…
Network Infrastructure task force: YANG to Redfish
• Enable converged infrastructure management
• One interface (one tool chain) to manage compute, storage and network
• Switches have platform components in common with servers and storage
• Network Functions Virtualization (NFV) will need common manageability
for compute and networking
• DMTF wants to leverage the networking industry's expertise
• YANG is the basis for general network industry manageability
• Large body of existing YANG work
• Model driven approach to network management

Redfish
YANG
model
model Redfish
(CSDL)
YANG to Tools
Redfish
Mapping
Spec

20