Architecture
Overview
- Will demonstrate Network Discovery Microservice and Service Decomposition Microservice
- Relies on supporting Microservices not yet in ONAP, but we can show
- Standardized API and provide a sense of its extensibility to support discovering of additional components
- VM attributes from Openstack
- How this fits into POMBA architecture
- How this could be leveraged in other use cases
Southbound API
- The following is the information expected from the southbound interface to network discovery
- Examples (coming soon)
- Mocking in SoapUI (soon)
Captures
Network Discovery Context Builder → Service Decomposition
The context builder first needs to determine what resources comprise the service undergoing auditing and so it employs Service Decomposition.
Request
Service Decomposition → AAI
Service Decomposition needs to send a series of requests to the AAI in order to effectively mine the data source for the service instance's component resources.
Request
Response
Response
Network Discovery Context Builder → Network Discovery
The context builder next needs to send multiple requests – one for each resource provided by Service Decomposition – to Network Discovery in order to obtain the values of associated attributes.
Request
Network Discovery → AAI Enricher
For each resource passed to it, Network Discovery simply hands off the discovery work to the AAI Enricher, which utilizes addons to query live networks. (Note: Enricher is not in ONAP at this time but the responses could be mocked.)