OCP's Rack Manager Controller Subproject (Openrmc)

OCP's Rack Manager Controller Subproject (Openrmc)

OSF-OpenRMC OCP's Rack Manager Controller subproject (OpenRMC) John Leung, Principle Engineer Intel Corporation Han Wang, Senior Architect Inspur OpenRMC Overview OpenRMC OPENRMC • Goals and Motivation • Logistics and meetings Specifications Status • Reviewed of existing rack management implementations Embedded • Specifying interface and requirements Software • Received Code Contributions RMC for openEdge Platform to DC The OpenRMC Goals manager Specify the Rack Manager Controller service RMC Client interfaces • Northbound interface to datacenter manager (spec) Redfish • Southbound interface requirements to OCP Northbound Interface platforms in the rack Rack Manager Controller Deliver a Rack Manager implementation Service • Available as open source Southbound Interface OCP compliant hardware designs I2C IPMI Redfish • Handled by other OCP projects to OCP platforms Motivation for OpenRMC RMC Rack Mgr Service Controller 1. System Firmware (BIOS) 3 In-band • OCP System Firmware project SW OS 2. BMC Firmware Agent Out-of-band • OpenBMC governed by Linux Foundation (Redfish) 3. Rack Manager Software/Firmware BIOS CPU NIC 1 • OCP OpenRMC NC-SI BMC FW BMC 2 • With OpenBMC, the industry unified the various repositories in 2018 device other • With rack manager, OCP will provide a device source repository and prevent splintering Server The RMC can be hosted in various locations OpenRACK EIA, OpenRACK Olympus (within power shelf) (within switch) (standalone) Switch RMC FW Switch w/ RMC FW Switch Power Shelf w/ RMC FW Server Server Server Server Server Server Server Server Server Server Server Server Server Server Server Server Server Server Logistics • A subproject of the Hardware Management project • John Leung (Intel) and Han Wang (Inspur) are co-chairs • Wiki • Mail-list • Participation • ARM, Microsoft, Facebook, Huawei, Inspur, Nokia, Intel, etc OpenRMC project has since Nov 2018 Reviewed and compare • Existing RMC interfaces and architectures from Facebook, Intel, Inspur and Microsoft (Comparison of interfaces) Draft specifications and requirments • Draft of Northbound API Specification • Draft of Southbound interface requirements Reviewed RMC code contributions • From Microsoft, Inspur, and Intel Source Repository On OCP Github (github.com/opencomputeproject/Rack-Manager) Contrib-Microsoft, Contrib-Inspur, Contrib-Intel folders ./OpenRMC folder Language Architecture Processor Memory Microsoft C++ OpenBMC AST2500 Inspur C++ OpenBMC AST2500 Intel C++ Intel NUC OpenRMC project goals Replacing firmware binaries with buildable source • An OCP location exists for RMC sources • OCP RMC contribution can reference the source repository Open RMC • RMC source that conform to the OpenRMC Northbound API Nokia Airframe openEdge Chassis Airframe openEdge RMC Interface supported : • DMTF Redfish • DMTF SMASH • IPMI • SNMP Testing OpenRMC conformance • The OpenRMC profile file represents the Describe Prescribe Implement Test Northbound interface specification in a JSON format (Redfish resources & properties) DMTF OCP DMTF • The Redfish Interop Validator: 1) reads the OpenRMC profile, 2) autogenerates the tests, and 3) runs them against an implementation Redfish Interop • The Interop Validator is a component of the Validator Redfish conformance test suite, which also tests Specifications Embedded includes OpenRMC Profile Software • Redfish Service Conformance Check • Redfish Service Validator • Redfish Usecase Checkers to DC Status against Goals manager Specify the Rack Manager Controller service interfaces RMC Client • OpenRMC Northbound interface (v0.3) in review • Expect to be proper subset of openEdge RMC Redfish requirements Deliver a Rack Manager implementation Northbound Interface Rack Manager • Three RMC code repositories in an OCP Github location Controller OCP compliant hardware designs Service • Expect contributions to conform to the OCP OpenRMC Southbound Interface profile I2C IPMI Redfish • Expect contributions to include buildable source, instead of a firmware image to OCP platforms Call to Action • Join the OpenRMC discussion • [email protected] • Participate in the OpenRMC meetings • opencompute.org/wiki/Hardware_Management/Open_RMC • Contribute to the OpenRMC source & profile • github.com/opencomputeproject/Rack-Manager • github.com/opencomputeproject/OCP-Profiles .

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    16 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us