Uploaded image for project: 'SEBA'
  1. SEBA
  2. SEBA-205

Unify the management interfaces of the SEBA pod parts

    XMLWordPrintable

    Details

    • Type: Epic
    • Status: To Do (View Workflow)
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: NEM
    • Labels:
      None
    • Epic Name:
      NEM Capabilities
    • Story Points:
      9

      Description

      The network edge manager (NEM) should take in the various management channels available from the SEBA pod parts including the aggregation Ethernet switch, the OLT hardware, the linux server, and the user interfaces available from the voltha and onos applications.

      NEMs should provide an API or a set of APIs available to the operations groups supporting the customers connected by way of the SEBA pod.  These same APIs may be used for northbound systems.

      There will be nine user stories associated with this epic.  Most will describe how to handle certain faul conditions, and several will describe requirement for crucial OA&M features including backup and restore, software upgrade, and additional management features.

      Reference diagram:

       

       

        Attachments

          Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              pw1341 Paul Witko
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:

                  Gerrit Reviews

                  There are no open Gerrit changes