Project Name:
- Proposed name for the project: OpenSource Access ManagementManager
- Proposed name for the repository: osam
Project description:
OpenSource Access Management 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.
Global Functions for Access
• OA&M user interface (UI) for operational support of the Access Network
o Visualization utilizing Grafana and ElasticStack
• Java Service Container (JSC)
o High level APIs created for subscriber service instantiation
• Direct Messaging Engine (DME)
o Handles message routing to the localized JSC
• Active and Available Inventory (AAI)
o Data Store models and services to be extended for Access Network Models covering the physical network, facilities, ports, subscriber services and profile information.
• Global Services will interact with the MSO, DMaaP and DCAE
• Scheduler for planning of updates to system services and access devices
• CLAMP for closed loop automation in the context of the Global resources
• Directed Graphs/Node-Red for global service flows (TBD)
Local Functions for Access
• Java Service Container (JSC)
o Low level APIs created for subscriber service instantiation
• Directed Graphs/Node-Red for local service flows
• Access Application
o vAccess Related tenants
• VOLTHA Hardware Abstraction for access devices
• Active and Available Inventory (AAI)
o Federated data store for access network data
• FreeRADIUS for subscriber 802.1x authentication
• All Components will feed data into DMaaP/DCAE
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)
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
- DSC- OSAM - Control for Dynamic User Control Plane
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 o The service engine will be planned to be built on the ONAP JSC Service Framework
...
• 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.
• 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:
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:
| Component | Effort | Project Impacts |
|---|---|---|
| Active and Available Inventory (AAI) | Inventory of the devices and user services | No AAI Impacts |
| Application Authorization Framework | Define application roles and access | |
| Application Controller (AAP-C) | Directed Graphs | No Core APP-C Impacts |
| Closed Loop Automation Management Platform (CLAMP) | CLAMP will be utilized to view and manage the automation flows Interface CLAMP from OSAM-UI (Future Release) | No Core CLAMP Impacts |
| Command Line Interface | No Impacts | |
| Common Controller Developer Kit (CCDK) | Used by SDNC and APPC | No Core CCDK Changes |
| Data Collection Analytics and Events (DCAE) | vAccess to VES Collector Connector vAccess to DMaaP Collector Connector | No Core Impacts to DCAE |
| Data Movement as a Platform (DMaaP) | Topic and Partition Creation | No Core DMaaP Impacts |
| Documentation | ||
| External API Framework | No Impact | |
| Holmes | Not Used | No Impact |
| Integration | No Impact | |
| Logging Enhancements Project | No Impact | |
| Microservices Bus | Not Used | No Impact |
| Modeling | Reuse of existing modeling rules and standards | |
| Multi-Cloud (VIM) | Interface for container instantiation, management and control | No Core Product Changes |
| ONAP Operations Manager (OOM) | Docker/Kubernetes Container Management | No Impacts |
| Optimization Framework | No Impacts | |
| Policy Framework | Reuse of the existing Threshold Crossing. Impacts to the Control and Abstraction output to VES | Minimal impact to reuse TCA |
| Portal Platform | Portal Interface to the DSC and Hardware Abstraction utilizing the Portal SDK | Reference to OSAM Control and OSAM-HA interfaces |
| Service Design and Creation (SDC) | Development of the Rules, Recipes, Flows, Models, Policies and Services for virtualized Access. | TBD |
| Virtual Infrastructure Deployment (VID) | VID will be utilized for the management of applications. Interface VID from OSAM-UI | No VID Impacts |
| SDNC | Establish EVPN tunnel between Access Peripheral and BNG termination point | No Core SDNC Impacts |
| Service Orchestration (SO) | Orchestration of Access Device and Service instantiation and updates | No Core Impacts |
No Core SDNC Impacts
Inventory of the devices and user services
Creation of Models in SDC
Subscribers will utilize LDAP for Access service profiles and authentication
No System Impact
System to retrieve messages for service changes
Creation of Topics and Queues
vAccess to VES Collector Connector
vAccess to DMaaP Collector Connector
vAccess components currently provide data through FluentD to Kafka
Access Network Components:
| Component | Effort | Impact |
|---|---|---|
| OSAM - UI | Provides High Order Management interface for Access Services and devices | Built on Portal SDK |
| OSAM - Control | Provides Dynamic Control & User Plane | Domain Specific Control |
| OSAM - HA | Hardware Abstraction layer of physical network device exposing | Network Function Layer |
| OpenRADIUSFreeRADIUS | Provides Subscriber Authentication services for 802.1X | Network Function Layer |
| OpenLDAPOpenLDAP | Provides authentication profiles for the authentication process | Network Function Layer |
S3P:
Scale:
Access Network functions are built to cluster horizontally and scale to meet carrier performance and response requirements.
...
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
...
- Names and affiliations of any other contributors
- Project Roles (include RACI chart, if applicable)
Other Information:
- link to seed code (if applicable)
- Vendor Neutral
- Meets Board policy (including IPR)
...