M a n a g i n g C l o u d H a r d w a r e. Alfie Lew, Inspur John Leung, Intel Sai Dasari, Facebook

Transcription

1 M a n a g i n g C l o u d H a r d w a r e Alfie Lew, Inspur John Leung, Intel Sai Dasari, Facebook

2 Agenda Hardware Management Overview Leverage Existing Standards Open Source Projects OpenBMC firmware Open Source Firmware OpenRMC Summary Q&A Open Software Open Hardware Open Firmware 2

3 Hardware Management (Legacy) In-band Uses main CPU, primary memory, etc. Out-of-band Uses controller (BMC) May operate at low power states OS SW Agent In-band Remote Client Off-platform Manageability of the system to a remote client IPMI over RMCP+ On-platform Manageability of devices within the platform IPMI over various protocols and connections BIOS BMC FW CPU BMC IPMI NIC NC-SI Out-of-band (IPMI) Issues: BMC firmware is not open Security concerns with RMCP+ device device other Platform On-platform

4 DMTF Manageability Standards Off-platform (Redfish) Remote Client A RESTful interface for manageability (HTTP, JSON) In-band Includes resource models for systems, chassis, managers. Other SDO's have extended Redfish to manage other type of platforms and services OS SW Agent Out-of-band (Redfish) On-platform (PLDM over MCTP) BIOS CPU NIC MCTP - A route-able transport protocol for manageability messages (connection independent) BMC FW BMC NC-SI PLDM - A bit-based request/response command model RDE - A PLDM model designed for devices to support Redfish semantics device device PLDM MCTP other Platform

5 Redfish Overview Uses cloud/web protocols, structures, security models HTTP, JSON (leverage existing tool chains) Resource schemas are accessible, to enable interface programmatically json-schema, OpenAPI/swagger schema HTTP/S Python code Output HTTP GET rawdata = urllib.urlopen( jsondata = json.loads(rawdata) print( jsondata[ SerialNumber ] ) 1A87CA442K

6 Redfish Computer System Model Service Root /redfish/v1 Root Tasks Sessions Accounts Events Registries Schemas Collection Resource Single Resource /redfish/v1/systems Collection of Systems "Logical view" /redfish/v1/chassis Collection of Chassis "Physical view" /redfish/v1/managers Collection of Managers "Mgmt hierarchy"./systems/<id> Computer System Computer Systems./Chassis/<id> Chassis Managed By./Managers/<id> BMC HTTP GET /redfish/v1/systems/cs_1/processors/2 Processors Memory Disks NICs Power Thermal LogService NW protocol Compute Platform HW Mgmt 6

7 Managing Beyond Computer Systems The Redfish Forum works with other SDOs to create models for new management domains Storage services and networked storage Ethernet Switch - map YANG to Redfish Industrial IoT Telco - Customer Premise Equipment DCIM - DC Infrastructure Mgmt (e.g. CRACs, PDUs, chillers) Redfish Client Redfish Off-platform interface Aug 2015 Aug 2016 Internet Draft 2017 System Storage Network YANG IIoT DCIM (facilities) (Starfish) Telco With the number of models increasing, how would OCP specify the required manageability of OCP platforms?

8 OCP Platform Manageability Direction OCP will use Redfish profiles to specify platform manageability The OCP Hardware Management project Will specify the manageability common across OCP platforms Interface Has approved the "OCP Baseline Hardware Management Profile" 1 Server Profile(s ) Storage Profile(s ) Network Profile(s ) Telco Profile(s ) Rack & Power Profile(s) Other OCP projects Will create platform specific profiles Hardware Mgmt Baseline Profile Profiles will extend the "Baseline Hardware Management Profile" "OCP Server Profile" is available 1 opencompute.org/wiki/hardware_management/specsanddesigns

9 OCP San Jose Compute Node Successfully ran the Redfish Interop Validator testing against the "OCP Baseline Hardware Management Profile" Demonstrated at OCP Summit (March 2018) OCP Server Profile

10 Enabling Interoperable Manageability OCP will prescribe platform manageability in machine readable JSON profile Implementers can use the profile to test conformance of an implementation Linux Foundation governs the open-source implementation of BMC firmware (OpenBMC) 10

11 OCP San Jose Compute Node Incorporated OpenBMC The implementation passed the OCP Baseline HW Manageability Profile Demo ed at OCP Regional Summit (Oct 2018, Amsterdam) Changes will be upstreamed to the OpenBMC repository 1 Target Date: March 2019 available on GitHub 1 The Linux Foundation project

12 A Brief History of OpenBMC Project Two independent implementations Facebook IBM Linux Foundation Project (IBM, Google, Intel, Microsoft, Facebook) 12

13 OpenBMC Development Model Traditional OpenBMC 3 rd Party HW Vendor 3 rd Party BMC FW Vendor 3 rd Party HW Vendor 3 rd Party BMC HW Vendor (AIC/PS/NVMe) (Aspeed/Nuvoton) (AIC/PS/NVMe) (Aspeed/Nuvoton) 3 rd Party BMC FW Vendor 3 rd Party BMC FW Vendor OpenBMC Project ODM Server Vendor BMC FW Source Code BMC FW Source Code 13

14 OpenBMC Architecture CHASSIS CONTROL CONFIGURATION MANAGER FIRMWARE UPDATE RMCP+ ENDPOINT REDFISH ENDPOINT INVENTORY MANAGER Applications SYSTEMD D-BUS GPIO/ ADC bridge FSC BT MBOX bridge KCS IPMI IPMB EWS ENDPOINT Bootloader & Kernel Linux Kernel/Drivers Boot Loader (e.g. U-Boot) Hardware BMC SoC / SPI Flash / TPM 14

15 Additional Resources Source Code: Continuous Integration Testing Code Reviews Contact Mail: IRC: #openbmc on freenode.net Riot: #openbmc:matrix.org Web Page: 15

16 Infrastructure, Tools & Eco-system support Mission: Develop an open source philosophy based system firmware (BIOS) modules, to support different Operating Systems and different CPU silicon vendors. Major Companies Contributing to OSF development: Microsoft, Intel, Google, Facebook, Lenovo, IBM, Two Sigma, ITRenew, 9 Elements, Cavium, AMD and many more. Major Work Streams: Open EDKII DXE core, Linux Boot, Core Boot, Silicon Interface Firmware Module, Intel FSP, AMD AGESA, ARM boot code, HW platform module, Build tools, Automated test support, HW requirements, etc. GitHub Repositories Collateral link: Bi-weekly OSF discussions : Architectural reviews, workstream progress, design reviews, agenda setting and other collaborative discussions on OSF development. Contact the following to subscribe, participate and contribute: gundrala.goud@ocproject.net ron.minnich@ocproject.net rajeev@opencompute.org Collaborative Community development model

17 Proposed OpenRMC sub-project Rack The rack is the fundamental building block for the Data Center Rack Manager Controller (RMC) The RMC is fundamental to Data Center Management hierarchy The RMC can be located standalone, within power shelf, or within the switch Opportunity Common language/model between RMC and nodes (aggregation, etc.) Provide an open source reference RMC nodes

18 Open Source Firmware for OCP Ecosystem OCP Design Collateral Binary Blobs Presentations Specifications Product/Company Specific Source Repo Schematics Data Sheets Firmware (Build Meta Data) Open Source Community Repo (e.g. OpenBMC, OpenRMC, LinuxBoot, Coreboot, OpenEDKII) Design Packages 3D/CAD Files OCP Specific Source Repo (e.g. LED Config, Redfish Profiles) 18

19