Project Name:

• Proposed name for the project: OpenSource Access Manager
• Proposed name for the repository: osam

Project description:

OpenSource Access Manager is a vendor agnostic operation suite for managing consumer broadband network elements and capabilities disaggregated from proprietary monolithic Access Network hardware and Element Management Systems (EMS).

A key component to simplify multi-vendor support is a mediation layer currently under development called VOLTHA (ONF open source project).  VOLTHA uses low-level abstraction of the network device to provide a simplified approach to higher level management and analytics.  Currently xPON and G.FAST are the initial products under active development in collaboration with ONF. 

Scope:

OpenSource Access Manager is a domain specific module for ONAP consisting of the OA&M User interface, flows, web services and microservices in support of virtualized multi-access network for consumer broadband services.  At a high level it divides into global and localized functions to operate at large scale and performance for edge networks.  The major components of Access Module that do not exist in ONAP today are the user interface (UI), the carrier grade access controller and hardware abstraction though OSAM-HA (ONF: VOLTHA).  Access specific data models, services and flows will be built on existing ONAP components and may feed additional requirements.  The infrastructure elements, services, flows, data collection processes will be utilized and existing or planned feature sets should not be impacted.

Below are the functions of access network needed on top of the infrastructure services that are already provided as part of ONAP.  The requirements for Access will be isolated to the Access Module to not impact the core ONAP capabilities and deliverables.

Access network is broken down into central and edge deployments.  Some functions of the control and management will be located centrally and some may be located at the edge in support of access.

Central Compute

• User interfaces in support of access.
  • Common ONAP interfaces (Portal, SDC, VID, OOM, CLAMP, CLI) will be reused
  • UI for Broadband Subscriber Access Network devices and Services
  • Reuse of ElasticStack (Kibana, Log Stash and Elastic Search)
• Reuse of the common ONAP functions (In addition to above - limited to the context of access)
  • AAI
  • DCAE
  • SO 
  • DMaaP
  • AAF
  • Policy
   

Generally Edge Compute (Could be with Central Compute)

• User interfaces in support of access.
  • Common ONAP interfaces (Portal, SDC, VID, OOM, CLAMP, CLI) will be reused
  • UI for Broadband Subscriber Access Network devices and Services
  • Reuse of ElasticStack (Kibana, Log Stash and Elastic Search)
• Reuse of the common ONAP functions (In addition to above)
  • DCAE
  • SO 
  • DMaaP
  • AAI
  • Policy
  • APP-C
  • SDN-C
  • Multi-Cloud VIM
• Access Specific Functions
  • DSC- OSAM - Control for Dynamic User Control Plane
    • Incudes the subscriber Virtual Tenant Network
    • Authentication Tenants
    • Subscriber DHCP Relay
    • Subscriber BNG Associations 
  • OSAM - HA - Network Abstraction Layer for Access Devices
  • FreeRADIUS for Subscriber 802.1X authentication
  • OpenLDAP for Subscriber policies and configurations 
  • OSAM Collector for DCAE
  • OSAM Analytics for DCAE

User stories/WIP:

• Access Network services will operate as containers generally in an edge cloud environment utilizing Docker containers.
• Edge Network services will utilize Kubernetes and K8 models
• Virtualized Access containers will be deployed and lifecycle managed by ONAP core components
• Services provided for the Virtual Access Network will be orchestrated through SO

Operational User Interface - Functionality:

•    Pulls resources, interfaces and data elements from ONAP, DCAE and JSC into a cohesive interface supporting the Access Network Infrastructure.

•    Configure settings exposed by API against 1 or more devices and services

•    Ability to bulk execute a list of devices against exposed services including (Node-Red/Directed Graphs)

    o    Services directly imported into interface once deployed

•    A view of error details for functions/devices streaming with related hot links into the low level details (e.g. Abstraction Layer, OLT, Port, ONU, ONU Uplink Port, ONU UNI Ports, DPU,  CPE, MicroServices, and future components)

    o    Advanced text and regular expression based filters based on device names or event details

    o    Time range based filters

•    Customizations

    o    Customizations by a user, group or system level

    o    Context sensitive interface changes driven by exposed APIs

    o    Ability to store and share views

    o    Ability for a user to load multiple views at the same time

•    Single application for Network visualization with integrated  analytics from DCAE, Elastic Stack and Grafana

    o    Operational dashboard showing geographic distribution of the network and services health (“Heat Map”)

    o    Established links between devices/service management and the graphical representations

•    Interface for scheduling and coordinating access related devices and software

    o    Firmware Release Management and Upgrades

    o    Snapshot management of Access devices and configurations

          This will be utilized for comparison, restoral and migration activities

    o    VNF Service Versioning Management at a collection or subscriber level

    o    User Migration flows in coordination with Firmware and VNF release management

    o    Rollback and notification under failure conditions or forced action

    o    Ability to create collections of subscribers, VNFs, and devices

    o    Configurable Maintenance Window

    o    Ability to operate in serial or parallel at the collection level

    o    Ability to establish dependencies prior to execution

•    Support for systems, network, software, service and configuration segmentation (slicing)

    o    Can be configured by Global, Site, DMA, Service Type or Device Type and each being subdivided by Release Type

    o    Support different lifecycle states of software, firmware and configuration within

        * Examples Crawl, Walk, and Run methodology of deploying changes

        * Examples Development, Test, Incubation, and Production state of services

    o    Software Versions, Firmware, Policies, and configurations should be configured as a package

        * Deployed for a specific set of hardware

        * Ability to manage hierarchical configuration management and version controlled

    o    Tool for viewing historical changes, comparison, events, and health of a segment

Service Engines and Message Routing for the Access Network:

•    Application Interfaces exposed to north bound systems are simplified to Create, Read, Update and Delete (CRUD) functions for subscriber associated services

•    Global

    o    Provides the high level APIs that span multiple local sites and interactions with the centralized ONAP sites

    o    The Message routing will be planned to be built on the ONAP’s Direct Messaging Engine (DME)

    o    The service engine will be planned to be built on the ONAP JSC Service Framework

    o    Global Access Network Related Flows will be built utilizing Directed Graphs

    o    Provides data caching and on-demand fetch of data elements on ONAP and Local Access Services

        *   APIs can be setup with a cache, lifespan and scope (user/group/all)

        *  Cache will reload using an on-demand fetch update model

•    Local

    o    Exposes the mid-level APIs to be utilized for the Edge devices and services

    o    The service engine will be planned to be built on the ONAP JSC Service Framework

    o    Local Access Network Related Flows will be built utilizing Directed Graphs

    o    JSC will be the point of entry from the global sites for service instantiation flows

Data Store consists of the data store for the access subscriber data. Functionality:

•    Object based storage system built on existing OpenSource Object Storage technology deployed for ONAP Inventory system AAI.

•    Isolation of data from the AAI in order to ensure subscriber data stores do not impact ONAP operations and to limit subscriber data access

•    Hierarchical and horizontal scalability to support billions of subscribers and access elements (physical and virtual)

    o    Subscriber Information, Security and Polices

        *    This information will likely be stored in an existing BSS when integration into a carrier network, but will be needed for ONAP implementation

    o    Physical plant assets

    o    Access Physical and Virtual Infrastructure and Service components

    o    Subscriber Services and Service Chains

Components utilized from Open Networking Foundation (ONF) project

•    Access Application and Tenants

•    VOLTHA hardware abstraction providing disaggregation of many of the functions currently performed by OLT hardware

    o    Protocol Abstraction and Multi-Access API uniformity

    o    Device persistence

    o    Data Harmonization

Other components

•    Message Bus for event and counter collection

•    RADIUS for authentication by the fixed access network

    o    Integrated through a module within the access network controller.

•    VES data collection agents in Application Containers to provide system analytics to DCAE

    o    Events will be allocated to different DMaaP topics and partitions based on model driven classification to improve efficiency of event processing by Closed loop

•    Nagios for System, VM and Container Alerting and Monitoring

•    Zero Touch Provisioning flows are being defined and will be added to the scope of this document and will impact several components of both the Access Module and ONAP [TBD]

•    Access services, models and flows will be part of an Access module that are deployable on top of the ONAP framework with impacting the core ONAP requirements and functionality.

Access Integration into ONAP

•    Infrastructure Initialization Policies

    o    SDC and TOSCA Models

        *    TOSCA Models created for the Access Network Components

        *    Service Policy creation of the operation health and scaling

    o    MSO and HEAT Templates

        *    HEAT templates for initializing the VM/Containers, Underlay network in support of the Access Network

    o    VIM

        *    VIM will be used to manage and configure the VM/Containers

        *    VIM will not be directly interface, but interface from the Service Engines (SE) through the MSO

    o    SDN-C and Directed Graphs for in support of the underlay network

•    DCAE / DMaaP

    o    Data collection and migration to central data lake

        *    Data collection will contain information about the virtualized access hardware, software, VMs, containers, network and physical nodes

    o    Interface for Network visualization through Grafana in the Access Network

    o    Tracks the utilization of the network and compute resources

        *    The information is correlated with the Access Data Store to associate to the subscriber’s service chain

    o    Aggregate subscriber capacity reports are to be processed by DCAE

        *    DCAE will require interface or feed from the Access Data Store

•    AAI     

    o    Stores the underlying VM/Container inventory and network inventory including the relationships between elements.

    o    The information will be needed by the Web Service Framework (JSC) and associated to the Access Data Store housing the physical access elements, subscriber interfaces (e.g. xDSL, Ethernet, ONT, G.FAST, etc.), network interface, profiles and services.

•    CLAMP

    o    Policy Rules and Execution Development

        *    Subscriber based profile management will be executed in the Access Applications

•    When profile SLAs are not being met a message is communicated on the DMaaP in a dedicated Topic.  Control Loop polices would be configured using CLAMP to detect messages placed on DMaaP.

    o    Fault Detection

    o    Auto-Scaling

•    Scheduler

    o    Coordinates subscriber migrations and software updates.

Architecture Alignment:

OpenSource Access Manager is a domain specific management and services stack interfacing and interacting with the core ONAP capabilities that support and maintain the underlying virtual and physical infrastructure.

OpenSourceAccessManager_ONAP_2.png

•    How does this project fit into the rest of the ONAP Architecture?

    o    ONAP manages the physical infrastructure hosting the virtual network function and the underlay network.

    o    Access Management will leverage many of the existing infrastructure components (AAI, DME, JSC, and Directed Graphs).

        *    Access Network Models, Flows and API’s will be developed as part of the project.  

    o    Utilizes : SDC, AAI, Scheduler, MSO, DCAE, Policy, CLAMP, VID and DMaaP

•    How does this align with external standards/specifications?

    o    Alignment with the ONF, OpenAPI, BBF, IETF and ITU Standards

•    Are there dependencies with other open source projects?

    o    Integration with the VOLTHA projects in ONF

    o    Integration with the OSAM - Dynamic Control & User Plane

Impacts:

ONAP Components: 

Access Network Components:

S3P:

Scale:

Access Network functions are built to cluster horizontally and scale to meet carrier performance and response requirements.

Stability:

All Access network components are designed to operate in a horizontal scale in order to provide a seamless user operation.

Security:

The reside on ONAP secured infrastructure.

Performance:

All Access Network components have been developed and tested to support high performance.  If performance issues are found during testing the application

Resources:

• Primary Contact Person: Blaine McDonnell (bm2535@att.com) 
• Names, gerrit IDs, and company affiliations of the committers

Committers:

Contributors:

• Names and affiliations of any other contributors
• Project Roles (include RACI chart, if applicable)

Other Information:

• link to seed code (if applicable)
• https://github.com/opencord
• Vendor Neutral
• Meets Board policy (including IPR)