SEBA shall provide an simplified Access Node adstract implementation for the FCAPS management of the resources in a SEBA POD

SEBA POD deployment is a key VOLTHA scenario

–This is accomplished by locating the computing resources running the VOLTHA hardware abstraction and management applications with the VOLTHA hardware components in the CO edge

–Moving forward quickly with a MVP VOLTHA solution leads AT&T to believe the fastest path is to deploy a small peripheral POD in the CO

–This POD will contain:

• Compute, fabric (agg), and VOLTHA as hardware resource
• SEBA, NEM, ONOS, ONOS Apps, and VOLTHA for software resources

–SEBA/NEM will provide an access abstraction layer to the VOLTHA specific implementation

SEBA POD Management

–A yang model interface can provide a flexible and easy to manage interface

–The BBF WT-383 models provided in the BBF provided many of the required interface definitions

–These models can be applied to a possible top down provisioning model as well as provide the various FCAPS interfaces required to operate the POD

• Providing a top down management model is not intended to impede the implementation of a bottom up model being implemented in VOLTHA 2.0
• An abstract access model is envisioned to be the glue that can merge the two model

–Areas of management

• POD Management
• OLT Management
• ONT Management
• Profile Management
• Service Provisioning
• Status Reporting
• Alarm Management
• Performance Monitoring
• Security Managment