View file | ||||
---|---|---|---|---|
|
Table of Contents | ||
---|---|---|
|
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)
Video
The demo shows a request being sent to POMBA's Network Discovery Context Builder, which makes use of Service Decomposition in order to build a list of resources that comprise the specified service. The context builder then takes advantage of the Network Discovery service to obtain details from the network for each of those resources. The context builder collates the information returned by Network Discovery for each resource before providing the collected data to POMBA's Context Aggregator for inclusion in an audit.
View file | ||||
---|---|---|---|---|
|
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
Code Block | ||||
---|---|---|---|---|
| ||||
Response
Code Block | ||||
---|---|---|---|---|
| ||||
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
Code Block | ||||
---|---|---|---|---|
| ||||
Response
Code Block | ||||
---|---|---|---|---|
| ||||