...
- Topology Notification flow
1. Register the 3rd party SOTN Controller to ESR.
2. ESR trigger a 3rd Controller registered event to Dmaap.
3. SDNC subscribe the event and this event notified .
4. SDNC synchronize the topology from 3rd SOTN controller.
5. SDNC analyse the data from 3rd SDN controller. Get the nodes, links, terminal points of the topology.
6. SDNC call A&AI to create the nodes, links terminal points to save the topology.
Note: For multi 3rd SDN controllers, there will be several topologies notified. The links across the domain topology should be discovered or created by ONAP. - Vpn SOTN VPN Infra Service Deploy Flow
- 1. UUI /Portal create SOTN VPN Infra Service
- 2. 1 SO create service instance to AAIA&AI
- 23. 2 SO decompose the service template.
- 2.3 SO call SDNC create VPN resource
- 2.4 SDNC call AAI to create VPN resource instance
- 2.5 SO call SDNC to activate VPN resource
- 4. SO allocate the resources needed by cross ONAP deploy.
- 5. SO call the East/West APIs of ONAP of service provider partner, to create the service in the partner side.
- 6. SO create SPPartner resource information in A&AI. this will maintain the service instance uuid from the partner side.
- 7. SO call SDN-C to create SOTN connectivity resource.
- 8. SDN-C create SOTN connectivity resource instance in A&AI.
- 9. SO call SDN-C to activate SOTN connectivity resource.
- 10. SDN-C call 3rd party 2.6 SDNC call 3rd SOTN controller to create SOTN VPN instance if it is needed. For EPLine/EVPLine ,this operation is not needed here. For EPLAN/EVPLAN, it is needed to create a VPN with no UNIs in the 3rd SOTN controller.
- 2.7 SDNC call AAI 11. SDN-C call A&AI to create SOTN VPN Instance, the instance will be related to VPN resource instance.
- 2.8 SDNC call 3rd SD-WAN controller to create SD-WAN VPN instance. This means all the sites deployed later will be attached to the same VPN.
- 2.9 SDNC call AAI to create SD-WAN VPN instance, the instance will be related to VPN resource instance.
...