Inter SDN Controller Communication (SDNi)教材.pdfVIP

Inter SDN Controller Communication (SDNi) Rafat Jahan, R&D Lead(SDN), Tata Consultancy Services #ODSummit Introduction #ODSummit Need for SDNi • SDN will be deployed in large-scale networks, where it is divided into multiple connected SDN domains, for better scalability and security. • To utilize network resources efficiently, SDN controllers need to communicate with each other. • Networks are moving towards cloud architecture, where multiple SDN domains will be prevalent. • Enabling this communication in ODL encourages adoption of OpenDaylight controller. #ODSummit Sample Business Use Cases Bandwidth on Demand When the network resources are distributed among multiple SDN domains, controllers from each domain need to communicate with the controller of the source domain, to share network parameters. This enables the controller of the source domain to confirm and process the bandwidth requirement. Content Delivery Networks Service Providers have to meet the content delivery requirements as per the committed QoS. If the CDN server or cache nearest to the customer location is experiencing high loads and is unable to serve the customer, the request is sent to a CDN server/ cache that is not loaded. However, this CDN Server/ Cache may be located in a different SDN domain in the network. Hence, the source SDN controller needs to communicate (over SDNi) with the other SDN controllers within the network to negotiate a path to the best possible CDN server/ cache that meets the customer's QoS expectation. Separate SDN Controllers for Various Networks If the customer (retail, enterprise) demands a service that is provided by the data center, the SDN controllers of access, edge, core networks, and the data center need to communicate with each other. SDN controllers need to pass on parameters like QoS and policy information from the acc