Device Management v OLTHA Using Redfish HTTP REST

Device Management v. OLTHA Using Redfish HTTP REST

Scope of Redfish Server • Create a build for Redfish service in OLT, which will be based on REST query and control to access asfv. OLT 16 HW components. • Functions to be supported: • • • Firmware update OLT reboot Monitoring of Fans and PSUs Monitoring of XFPs/QSFPs Session management VPD

Scope of Redfish Client • Create a build for Redfish client service in asfv. OLT 16 adapter, which will be based on REST query and control to access asfv. OLT 16 HW components using Redfish server. • Functions to be supported: • • • Session login Get Status of Fans, PSUs, XFPs, QSFPs Firmware update OLT reboot Submit alarms to v. OLTHA Board config (clock speed, watchdog, sync timings etc) - ?

Redfish Server • Redfish server will be python program based on DMTF specifications, to serve redfish client requests on the specified IP/port. • Redfish server will build on a RESTful architecture and defines the managed resources for asfv. OLT 16 (Broadcom) platform management which will be accessed through REST APIs. • It defines data models (shown in slide#5, 6), to support various management features, using resources (System, Chassis & Switch), key services (Sessions, Events & Tasks) and Schemas.

Redfish Server Data Model for Health Status

Redfish Server Data Model for FW update & OLT Reboot

Redfish Server Schemas 1. Chassis(fan-psu). json 2. Firmware_upgrade(OLT). json 3. Switch(xfp-qsfp). json 4. Session. json 5. Systems(OLT reboot)

Redfish Server Implementation Details • Redfish server using flask to add basic and session based authentication. • It implements dynamic auth token creation using uuid library and implements auth required decorator for all redfish URIs. • It implements a root dictionary which contains all the further redfish server base URIs. Eg: (/redfish/v 1/Systems). • It implements one URI to get Chassis health data, which includes FANs/PSUs. • It implements one URI to reboot OLT using POST method, with the request validation for values of reset type. • It implements one URI to get VPD (XFPs/QSPFs ports) status.

Redfish Server Directory Structure

Redfish Client • Redfish client will be python program, as an integral part of asfv. OLT 16 adapter, which will communicate with redfish server on the specified IP/port. • Redfish client will also build on a RESTful architecture and perform login/get/set functions, required for management and configuration of asfv. OLT 16 (Broadcom) OLT through REST APIs. • It defines data models (shown in slide# , ), to support various management and config features like health status(FANs/PSUs/XFPs/QSFPs), OLT reboot & FW update, using URIs exposed by redfish server.

Redfish Client Data Model for Health Status

Redfish Client Data Model for OLT Reboot

Redfish Client Data Model for OLT FW update

Redfish Client Implementation Details • Redfish client using redfish FW to add basic and session based authentication. • It implements a method to login in redfish server and fetch dynamic auth token from it. • It registers a callback method to get OLT health data periodically, using reactor library. • Based on OLT health status, it submits alarm to adapter agent. • It implements a method to send OLT reset request to redfish server. • It implements a method to send OLT FW update request to redfish server.

Redfish Client Directory Structure

Assumptions • Support is required for 1 RU chassis only • Initial version will support only HTTP • v. OLTHA redfish server and client will use management interface for communication • Redfish server will use ONLP APIs to Activate and Rollback of firmware update on ASFv. OLT 16. • Low level Board Configuration (clock speed, watchdog, Sync timings etc) will be based on information returned by ONLP APIs.

Limitations • OLT hardware • asfv. OLT 16 driver for ONL • ONLP APIs