Update

In current Network Discovery microservice development (Dublin), southbound REST API sends OpenStack API requests instead of AAI Enricher API requests.

This page is tracking the Casablanca deliverables related to the Network Discovery Microservice.  The initial use case for this is feeding into the Post Orchestration Model Based Audit (POMBA) project.  The aim is that this Microservice (or collection of Microservice) can be leveraged in other use cases that require discovering information from primary data sources.

Presentation to Working Group, June 13, 2018

Presentation at Face to Face Meeting, June 21, 2018

See also Network Discovery Enhancements

High-level Architecture

discovery architecture

More Details

The Network Discovery solution allows for the discovery of network resources.  The longer term plan is to support a completely model-driven, self-service solution. In the short term, the solution may be slightly less extensible.

Stories in SDNC

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

Stories in Logging Project

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

  • No labels

2 Comments

  1. Zhuoyao Huang

    Hi, Sharon

          The Topology Notification flow described by CCVPN(Cross Domain and Cross Layer VPN) USE CASE indicated synchronizing topology from 3rd party STON Controllers. Does sdn network discovery consider 3rd party STON Controllers as data sources?  Thank you!

    BR.

    1. Sharon Chisholm

      They could be.  I think there are two paths to get data into ONAP.

      1. POMBA + adapter for specific data sources + common reconciliation log (future)
      2. Per data source specific integration of data sources for all functions, including retrieval of data + specific reconciliation

      The second approach is good at solving very specific solutions quickly.  The first approach, allows for leveraging the common investment in auditing and reconciliation.