Use Case Authors:
...
- Service and resource on-boarding
- Service configuration
- Service termination
- Self service adaptation (Bandwidth on demand to be added)
- Auto-scaling based on fault and performance (stretch goal)
- fault detection and auto-healing (stretch goal)
- data correlation and analytics (stretch goal)
...
- 1. SDC/CLAMP Portal design and activate policy.
- 2. SDC/CLAMP config and activate the policy.
- 3. SDC/CLAMP distribute the DCAE config.
- 4. SDC/CLMAP distribute the alarm correlation rules to Holmes.
- 5. 3rd party SOTN controller report link down alarm to DCAE
- 6. DCAE will do data cleaning and filtering for the alarms
- 7. DCAEk keep track the datas.
- 8. Holmes do analysis for the alarms.
- 9. Holmes notify the reroute event.
- 10. Policy matching the reroute rules.
- 11. Policy call SO to delete the old services and create the new services. For the creation flow, a variable route will be recalculated.
5.1 DCAE Flow in Close Loop (with better diagram later on)
- RestConf Collector (RC)subscribes for remote failure alarm to SOTN Controller (SC)
- RC requests to set up a long term tunnel with the 3rd party SC
- SC responses with OK upon successful tunnel setting
- SC pushes service route status data to the collector
- RC receives alarm data, converts it into JSON format and publishes on DMAAP with topic of ROUTE_ALARM_OUTPUT
- UVA consumes the alarm message
- UVA requests the RestConf2VES mapping
- UVA converts json alarm into VES event
- UVA publishes the VES event on DMAAP for further correlation
6. Service Design Flow
- 1. Design the service in SDC portal
- 2. SDC distribute the service information to SO
- 3. SDC distribute the service network information to SDNC
- 4. SDC distribute the service model information to AAI
- 5. SDC distribute the service VNF information to VFC/APPC.
...