...
3. Site Enterprise Service Deploy Flow
- 3.0 UUI/Portal create 1. UUIcreate Site Enterprise Service
- 32. 1 SO create service instance to AAI
- 3. 2 SO decompose the service template.3
- 4. 3 SO call SDNC create PNF resource
- 3.4 SDNC call AAI to create PNF resource instance
- 3.5 SO call SDNC to activate the PNF resource
- 3.6 SDNC call 3rd SD-WAN controller to create device of the site.
- 3.7 SO call SDNC to create site resource.
- 3.8 SDNC call AAI to create site resource instnace.
- 3.9 SO call SDNC to activate the site resource.
- 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 Check the site location to check if it is locate in local ONAP.
- 8. SO call SDN-C to create PNF resource
- 9. SDN-C call A&AI to create PNF resource instance
- 10. SO call SDN-C to activate the PNF resource
- 11. SDN-C call 3rd party 3.10 SDNC call 3rd SD-WAN controller to create device of the site.
- 12. SDN-C create device instance in A&AI.
- 13. SO call SDN-C to create site 3.11 SO call SDNC to create VPN attachment resource.
- 3.12 SDNC call AAI to create VPN attachment resource.
- 3.13 SO query the network access point information from inventory OSS of SP.
- 3.14 SO call SDNC to activate the VPN attachment resource. SDNC will get the existing VPN Infra Service information and the VPN attachment resource , to get the L1/L2 connectivity needed.
- 14. SDN-C call A&AI to create site resource instnace.
- 15. SO call SDN-C to activate the site resource.
- 16. SDN-C call 3rd SD-WAN controller to create site.
- 17. SO call SDN-C to create SOTN VPN attachment resource.
- 18. SDNC call AAI to create SOTN VPN attachment resource.
- 19. SO query the network access point information from inventory OSS of SP.
- 20. SO call SDN-C to activate the VPN attachment resource. SDN-C will get the existing VPN Infra Service information and the VPN attachment resource , to get the L1/L2 connectivity needed.
- 21. SDN-C call OOF to do L1/L2 connectivity route calculate between 3.15 SDNC call OOF to do L1/L2 connectivity route calculate between multi 3rd SOTN controller topologys.
- 322. 16 OOF will query AAI for the whole topology notified by multi SOTN controllers.
- 323. 17 OOF do route calculate.3.18 ,OOF return the route informations for L1/L2 connectivity VPNs on each SOTN controller.
- 3.19 SDNC 24. SDN-C will loop the VPNs , and create the SOTN VPN instance to AAIA&AI. This will also upate the VPN Infra service instance.
- 3.20 SDNC call 3rd SOTN controller to create VPN over topology.
- 3.21 SDC add relationship between the VPN instance and the topology.
- 3.22 SDNC call SD-WAN controller to attach the site to the SD-WAN VPN instance.
- 3.23 SDNC call SD-WAN controller to create LAN for the Site.
- VPN Infra service instance.
- 25. SDN-C call 3rd SOTN controller to create VPN over topology.
- 26. SDN-C add relationship between the VPN instance and the topology.
- 27. SO call SDN-C to create SD-WAN VPN attachment resource
- 28. SDN-C call A&AI to create SD-WAN VPN attachment resource instance.
- 29. SO call SDN-C to activate the SDN-WAN VPN attachment resource.
- 30. SDN-C call SD-WAN controller to attach the site to the SD-WAN VPN instance.
- 31. SO call SDN-C to create WAN port resource.
- 32. SDN-C call A&AI to create WAN port resource instance.
- 33. SO call SDN-C to activate WAN port resource.
- 33. SDN-C call SD-WAN controller to create WAN port for the Site.
- 34. SO call SDN-C to create LAN port resource.
- 35. SDN-C call A&AI to create LAN port resource instance.
- 36. SO call SDN-C to activate LAN port resource.
- 37. SDN-C 3.24 SDNC call SD-WAN controller to create WAN LAN port for the Site.
4. Site DC Service Deploy Flow
...