1. Device Management vOLTHA
Using Redfish HTTP REST

2. Scope of Redfish Server
Create a build for Redfish service in OLT, which will be based on REST query and control to access ASFvOLT16 HW components.
Functions to be supported:
Software upgrade
OLT reboot
Monitoring of fans and PSUs
Monitoring of XFP/QSFP
Session management
VPD

3. Scope of Redfish Client
Create a build for Redfish client service in asfvOLT16 adapter, which will be based on REST query and control to access ASFvOLT16 HW components using Redfish server.
Functions to be supported:
Session login
Get Status of fan, PSUs, XFP, QSFP
Board config (clock speed, watchdog, sync timings etc)
Post software upgrade, OLT reboot
Submit alarms to vOLTHA

4. 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 asfvOLT16 (Broadcom) platform management which will be accessed through REST APIs.
It defines a data models (shown in slide#5,6), to support various management features, using resources (System, Chassis & Managers), key services (Sessions, Events & Tasks) and Schemas.

5. Redfish Server Data Model for Health Status

6. Redfish Server Data Model for FW update & OLT Reboot

7. Redfish Server Schemas
Chassis(fan-psu).json
Firmware_upgrade(OLT).json
Managers(xfp-qsfp).json
Session.json
Systems(OLT reboot)

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

9. Limitations
OLT hardware
asfvOLT16 driver for ONL
ONLP APIs

10. Redfish Client
TBD