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
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.
- POMBA
- SDNC
- - SDNC-314Getting issue details... STATUS
- Parameter Mapping
- Network Discovery API Swagger
- Data Sources
- Context Builders Mapping to Common Model
- OpenStack Specific
- Networks
- https://wiki.openstack.org/wiki/Neutron/APIv2-specification
- GET http://host:9696/v2.0/networks
- VM
- https://developer.openstack.org/api-ref/compute/
- GET http://host:port//servers
- Networks
Stories in SDNC
Stories in Logging Project
2 Comments
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.
Sharon Chisholm
They could be. I think there are two paths to get data into ONAP.
The second approach is good at solving very specific solutions quickly. The first approach, allows for leveraging the common investment in auditing and reconciliation.