1 / 17

OpenADN: Mobile Apps on Global Clouds Using SDN

OpenADN: Mobile Apps on Global Clouds Using SDN. Raj Jain Project Leader: Subharthi Paul Washington University in Saint Louis Saint Louis, MO 63130 Jain@cse.wustl.edu May 16, 2012. Overview. Networking Application Trends OpenFlow and SDN OpenADN Vision and Extensions Experimental Results

audra-ford
Télécharger la présentation

OpenADN: Mobile Apps on Global Clouds Using SDN

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. OpenADN: Mobile Apps on Global Clouds Using SDN Raj Jain Project Leader: Subharthi Paul Washington University in Saint LouisSaint Louis, MO 63130Jain@cse.wustl.edu May 16, 2012

  2. Overview • Networking Application Trends • OpenFlow and SDN • OpenADN Vision and Extensions • Experimental Results • Key Features

  3. Trend: Explosion of Mobile Apps • All top 50 Internet sites are services [Alexa] • Almost all services are now mobile apps: Google, Facebook, Bank of America, … • Almost all services need to be global (World is flat) • Almost all services use cloud computing (Easy management) Networks need to support efficient service setup and delivery Ref: Top 500 sites on the web, http://www.alexa.com/topsites

  4. Solution: OpenADN • Open Application Delivery Networking PlatformPlatform = OpenADN aware clients, servers, switches, and middle-boxes • Allows Application Service Providers (ASPs) to quickly setup services on Internet using cloud computing ServersA2 Servers A1, B1 OpenADNSwitches OpenADNmiddle-box Internet Routers Access ISP Access ISP Clients Clients

  5. Google WAN Google L7 Proxy • OpenADN appliances are like Google appliances in Tier 3 ISPs • Details of Google WAN are not public • ISPs can not use it: L7 proxies require app msg reassembly Network POP Google Data Center #1 Access ISP Google WAN Access ISP Google Data Center #2 Google L7 Proxy

  6. Extension 1: Application Level Policies Server A1 Server A2 ASPs want: • Server selection • Load balancing between servers • Fault tolerance • Server mobility • User Mobility • Secure L5-L7 headers and data (rat hole) • Middlebox services: Intrusion detection, Content based routers, application firewalls, … • Control plane and data plane MBs • Middlebox traversal sequence • Message level policies • TCP Splicing Load BalancerMiddlebox FaultToleranceMiddlebox

  7. OpenADN in SDN’s Layered Abstraction ASP1 ASP2 ASP3 Application Level Control (ASP) • SDN provides standardized mechanisms for distribution of control information OpenADN OpenADN OpenADN Network Level Control (ISP) App4 App1 App2 App3 Network OS Network OS1 Network OS2 Network OS3 Network Virtualization Virtualization Forwarding HW Forwarding OpenADN Aware OpenFlow Forwarding HW Forwarding HW

  8. OpenADN Innovations • Extended OpenFlow flow-based handling, centralized policy control • Software Defined Networking: Standardized abstractions, Multi-Tenants, Control Plane programming for data plane • ID/Locator Split • Layer 7 Proxies (Similar to Google’s proxies in Access PoPs) • Cross-Layer Communication • MPLS like Labels

  9. Key Features of OpenADN • Edge devices only.Core network can be current TCP/IP based, OpenFlow or future SDN based • Coexistence (Backward compatibility): Old on New. New on Old • Incremental Deployment • Economic Incentive for first adopters • Resource owners (ISPs) keep complete control over their resources Most versions of Ethernet followed these principles. Many versions of IP did not.

  10. Demo Configuration Policies ASP • Single user and single ASP with 2 servers • OpenADN Appliances: A, B, C, D, E • ISP offers ADN services: Fault tolerance and Load Balancing Server 1 Server State Controller MB Configuration Forwarding Rules FT D B User (Data Source) IP Backbone A Server 2 E C LB

  11. Validation of Functionality Availability Both up 1 down Both up Load Balancing 50:50 70:30 30:70

  12. Resource Control • ASPs keep complete control of their data. ISP does not have to look at the application headers or data to enforce application level policies • ISPs keep complete control of their equipment. ASPs communicate their policies to ISP’s control plane • Middle boxes can be located anywhere on the global Internet(Of course, performance is best when they are close by) • ISPs own OpenADN switches and offer them as a service • ASPs or ISPs can own OpenADN middle boxes • No changes to the core Internet

  13. Beneficiaries of This Technology • Equipment/Software vendors: Sell openADN appliances, openADN-aware applications • ASPs: Deploy servers anywhere and move them anytime • ISPs: Offer new services • Cloud Service Providers (CSPs): Freedom to move VMs, Less impact of downtime CSP ISP ASP Middleboxes User

  14. Application Servers L2 Switches Application Level Gateways & Content-Based Routers CBR CBR CBR CBR ALG ALG ALG ALG Load Balancers Application Firewalls Load Balancers Intrusion Detection and Prevention Systems Load Balancers SSL Offloaders Load Balancers L2 Switches Data Center Public Internet Data Center Applications SSL SSL SSL SSL • Repeated classification and load balancing • No application level control over MBs traversed • Unnecessary traversals and reduced performance

  15. OpenADN in Data Center • No repeated classification and load balancing • Application flow specific traversal through MBs • Reduced number of appliances and increased performance

  16. OpenADN Without OpenFlow/SDN • OpenADN clients, servers, middle-boxes use only APLS labels. • OpenADN aware devices need an API to communicate with controllers • API can be vendor specific State State Rules Rules ASP2 ASP1 Control ISP Middle-boxes

  17. Summary • Explosion of Apps using cloud services • OpenADN appliances can provide ASPs networking services they need • OpenADN extends using best of OpenFlow, SDN, MPLS, ID/Locator Split, Cross-layer communications, middle box appliances • Keeps resource control under resource owners • Can be implemented incrementally now

More Related