The History and Evolution of SDN
•Download as PPTX, PDF•
3 likes•5,376 views
This document discusses the evolution of software defined networking (SDN) and application-centric infrastructure. It describes how SDN has progressed from early implementations using OpenFlow (SDN 1.0) to separating the control and data planes (SDN 2.0) to the current approach of an application-centric infrastructure with a centralized controller and policy-based automation (SDN 3.0). It emphasizes how the new approach simplifies infrastructure management, enables intelligent services, and provides dynamic security through a centralized control plane.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (19)
Similar to The History and Evolution of SDN
Similar to The History and Evolution of SDN (20)
More from Napier University
More from Napier University (20)
Recently uploaded
Recently uploaded (20)
The History and Evolution of SDN
- 1. ACI – A Policy Driven Infrastructure for the Intercloud World Salim Mehta Technical Architect Cisco Systems The History & Evolution of SDN 27 August 2015
- 3. Evolution of IT www.gartner.com/imagesrv/cio/pdf/cio_agenda_execsum2014.pdf IT Industrialization DigitalizationIT Craftsmanship Speed, Innovation and Conventional Control, Predictable, Low Risk Functional Operationally Focused
- 4. Moving to Webscale IT Self Service MTTR Light IT (1 x Admin: 150K servers) Few Applications (Customer Focused) Applications Built for Cloud Super Highly Skilled Workforce Set the Standard Clean Slate Approach Request and Wait MTBF Heavy IT (1 x Admin: 500 servers) Many Applications (Customer and Internal Focused) Applications Built for ERP Highly Skilled Workforce Follow the Standard Legacy / Historical Today Spend Time Save $ Spend $ Save Time
- 5. Moving to Webscale IT Self Service MTTR Light IT (1 x Admin: 150K servers) Few Applications (Customer Focused) Applications Built for Cloud Super Highly Skilled Workforce Set the Standard Clean Slate Approach Tomorrow Spend Time Save $ Spend $ Save Time Self Service Automation Cloud Cloud Capable Applications Software Defined Networking BiModal IT DevOps Fast IT Private Cloud
- 6. SDN 1.0 - OpenFlow VM VMVM 10.2.4.7 VM 10.9.3.37 VM 10.32.3.7 VMVM Box by box mgmt
- 7. SDN 1.0 - OpenFlow VM VMVM 10.2.4.7 VM 10.9.3.37 VM 10.32.3.7 VMVM OpenFlow Controller
- 8. SDN 1.0 - OpenFlow VM VMVM 10.2.4.7 VM 10.9.3.37 VM 10.32.3.7 VMVM Controller Control Plane Data Plane
- 9. SDN 1.0 - OpenFlow VM VMVM 10.2.4.7 VM 10.9.3.37 VM 10.32.3.7 VMVM Controller Availability? Scale?
- 10. SDN 2.0 - Separate Overlay Controller VM VMVM VM VMVM VMVM Underlay
- 11. SDN 2.0 - Separate Overlay Controller VM VMs on same DVS VMVM VM VMVM VMVM No correlation between overlay & underlay
- 12. SDN 2.0 - Separate Overlay Controller VM VMVM VM VMVM VMVM Two Points of control! Physical Hosts? Diagnostics? VMVM VM
- 13. SDN 3.0 - Application Centric Infrastructure DB Tier Storage Storage Application Client Web Tier App Tier Application policy model Policy instantiation VM VMVM 10.2.4.7 VM 10.9.3.37 VM 10.32.3.7 VMVM Integrated Underlay Distributed Control Plane APIC
- 14. SDN 3.0 - Application Centric Infrastructure DB Tier Storage Storage Application Client Web Tier App Tier Multiple isolated virtual networks VM VMVM 10.2.4.7 VM 10.9.3.37 VM 10.32.3.7 VMVM Any Hypervisor APIC
- 15. SDN 3.0 - Application Centric Infrastructure DB Tier Storage Storage Application Client Web Tier App Tier VM VMVM 10.2.4.7 VM 10.9.3.37 VM 10.32.3.7 VMVM Virtual & Physical Hosts APIC Single Point of controlVM VM Advanced telemetry for application traffic visibility
- 16. How we deliver infrastructure with policy… Storage WEB APP DB LAN LAN LAN LAN SAN LBFW LAN Connectivity Security QoS SLA Services PolicyConfiguration Point
- 17. Policy Driven Data Centre Define the Application Communication Policy Provision the Policy into the Fabric (Fully Automated) SecurityNetwork Virtualization Application Cloud Policy Framework Invest Time Spend No Time
- 18. NETWORKSECURITYCOMPUTE STORAGE OPERATIONSIMPLEMENTATIONARCHITECTURE DESIGN BEFORE AFTER Organisational Shift TECHNOLOGY SILOS VIRTUAL TEAMS NETWORK UC / VIDEO X-aaS
- 20. How Business Consumes IT Compute Network StorageSecurity ITClients Pools of Infrastructure Resource Compute Network StorageSecurity Cloud
- 21. Orchestration & Automation Resource Controllers Infrastructure Pool of Infrastructure Resource PSC UCSD How Developers Consume IT Compute Network StorageSecurity Cloud Open Daylight PNSCUCSM APICVMM Storage Controller API API API API API API
- 22. Fast IT Data Centre & Cloud Reference Architecture OpenIntegration MANAGEMENT AUTOMATION POLICY SECURITY ECOSYSTEMPARTNERS UCS Director Openstack UCS Manager Application Policy Infrastructure Controller Converged Infrastructure Managers OpenDaylight Virtual Machine Manager Process Orchestrator 3rd Party Orchestrator IaaS PaaS SaaS ITaaS Intercloud Prime Services Catalogue ORCHESTRATION SERVICES AUTOMATION PORTAL INFRASTRUCTURE MANAGEMENT Stack Designer Intercloud Fabric
- 23. Key Takeaways SIMPLE SIMPLIFY your infrastructure and INTEGRATE across silos SMART CREATE intelligent capabilities and SERVICES that fuel growth SECURE DEFEND against ATTACKS and mitigate THREATS dynamically Programmatic Interfaces Orchestration and Automation Centralized Control Fast IT
- 24. Thank you.
Editor's Notes
- Points to highlight : Entering the 3rd era and the way we deliver IT will change Supporting existing systems but ALSO delivering as a innovation engine to the business Moving at ‘cloud speed’ to address key business demands as highlighted in the earlier business outcomes slide Digitalization: Renovate the core Top technology priorities for 2014 reveal two complementary goals: renovating the core of IT and exploiting new technologies and trends. Exploiting the new speaks for itself. Meanwhile, the core of enterprise IT — infrastructure, applications such as ERP, information and sourcing — was built for the IT past and needs to be renovated for the digital future. The renovations include moving to a more loosely coupled “postmodern-ERP” paradigm, deploying public and private clouds, creating the information architecture and capabilities to exploit big data, and augmenting conventional sourcing with more innovation, including sourcing from, and partnering with, smaller and less mature enterprises (see figure below). The talent needed to execute on renovation includes different skills, such as digital design, data science, “digital anthropology,” startup skills and agile development. Reimagine the core Build bimodal capability There is an inherent tension between doing IT right and doing IT fast, doing IT safely and doing IT innovatively, working the plan and adapting. The second era of enterprise IT has been all about planning IT right, doing IT right, being predictable and creating value while maximizing control and minimizing risk — in short, about running IT like a business within a business. To capture digital opportunities, CIOs need to deal with speed, innovation and uncertainty. This requires operating two modes of enterprise IT: conventional and “nonlinear.” Those CIOs who have moved early on digitalization, learned the lessons and gotten the scars, have often extended their second-era restructuring to a more comprehensive change. In these cases, the grow-and-change function has become a more full-fledged digital development function, often reporting in a straight line to P&L/business unit owners, with a dotted line to IT for architectural governance. Teams are structured around products (not projects) and are multidisciplinary
- http://www.gartner.com/newsroom/id/2675916 http://blogs.gartner.com/cameron_haight/2013/05/16/enter-web-scale-it/
- http://www.gartner.com/newsroom/id/2675916 http://blogs.gartner.com/cameron_haight/2013/05/16/enter-web-scale-it/
- Points to highlight : Often policies are created and defined in isolation (different sources) with different languages, tooling and required intent These policy points will still exist however when we define in advance of the enforcement – working across teams in a highly collaborative way We can now insatiate that policy as required without having to invoke the ‘human chain’, in a quick and agile manner This is what ACI delivers..
- Points to highlight : Policy is critical to creating the agile and repeatable DC model allowing IT to adopt automation Today we build policy direct into the infrastructure (typically a manual process). We need to move that to a logical model where the policy is built once and repeated many times. Working across teams and groups to deliver the policy framework. To build the policy once then repeat as needed This frees up resource to focus on new and innovative things the business demands as opposed to repeating these policy tasks on a daily manual basis The figures below are taken from Deutsche Post & CollabNet - “Achieving the benefits of DevOps on an enterprise scale”. http://www.collab.net/resources/achieving-benefits-devops-enterprise-scale Although this is an example of DevOps it shows that operating in the model delivers clear and tangible results. When IT collaborates and works across team towards a common purpose. Reduced IT ops budget by 20% Decreased time to market by up to 40% Improved developer productivity up to 30% ISO / IEC compliance 10 days to migrate a project 8 x Return On Investment CollabNet provided a solution that gave Deutsche Post all those capabilities, with a set of agile processes using TeamForge to enable collaborative application development and deployment across internal and external cloud infrastructures. Benefits to Deutsche Post Transparency and traceability of changes to IT systems Increase the quality of applications in operations including improving the transition to maintenance and operations Standardization of tools, processes and informations Efficient management of different service providers Acceleration in all processes Simplification and standardization of project setups Reducing costs, for example by replacement of individual solutions Central provision of all necessary and updated information regarding an IT system for all participants along the life cycle of an application Reduction fo the used software portfolio, across all IT systems Terminology for Policy-Based Management …. http://www.ietf.org/rfc/rfc3198.txt "Policy" can be defined from two perspectives: A definite goal, course or method of action to guide and determine present and future decisions. Policies are implemented or executed within a particular context (such as policies defined within a business unit) Policies as a set of rules to administer, manage, and control access to network resource
- Points to highlight : Cultural Change – Collaboration, Cooperation, Knowledge learning/transfer Unified Process – More responsive to the business needs, Agile, Frequency, Improved visibility Unified Technology – tooling, automation, continuous X.. THIS IS HE IMPORTANT BULLET.. THE CUSTOMER HAS TO CHANGE!!!!! They cant simply buy tooling and that’s enough. It needs to be cultural and passion and a want to deliver the agile/devops world.
- Systems of Record — Established packaged applications or legacy homegrown systems that support core transaction processing and manage the organization's critical master data. The rate of change is low, because the processes are well-established and common to most organizations, and often are subject to regulatory requirements. Systems of Differentiation — Applications that enable unique company processes or industry-specific capabilities. They have a medium life cycle (one to three years), but need to be reconfigured frequently to accommodate changing business practices or customer requirements. Systems of Innovation — New applications that are built on an ad hoc basis to address new business requirements or opportunities. These are typically short life cycle projects (zero to 12 months) using departmental or outside resources and consumer-grade technologies.
- Points to highlight : Domain controllers vs orchestraiton/automation tool set. Common policy language and framework is appearing. (e.g TOSCA, Opflex)
- There is a new acronym in the industry . Its ATSOE. (Automate the SH!& Out of Everything). This is the aspiration of most customers. This is the typical architecture through which customers will consume FastIT. ACI is one of the components. You will have a layer of automation/orchestration. Some of these tools already exist in the customer. If they do, its possible the are not best suited to automate everything. In reality we use domain controllers to consume IT. The domain controller is the single point of entry into a domain. VMM = Virtual Machine Manager (e.g Vcenter, SCOM….) UCSM – UCS Manager - UCS APIC – Application Policy Infrastructure Controller – ACI PNSC – Prime Services Network Controller – Virtual Network Services (N1k, VSG, VASA……) Open Daylight – opensource SDN controller (there is also a Cisco distribution of ODL which is called XNC) EMC – Netapp – Abstracted storage controllers. (E.g EMC vipr) The Domain controller offer integration northbourd via API and southbound via API or protocol. CISCO ACI, CISCO UCS CISCO CLOUD are all designed for this architecture and consumption model.
- Points to highlight : Cisco DC reference architecture reflects the complete stack from resource management through to portal capability and to deliver Fast IT Important that this isn't a technology stack, this is a reference architecture allowing the customer to move to a policy driven automated and repeatable capability that delivers business outcomes NOT IT only outcomes Capability to consume a complete Cisco stack however we have an architecture that is open and eco-system driven Customer can choose the products and services that best suite their particular business outcome
- Agility via Programmability Enable Faster Innovation Zero Touch Automation
- Points to highlight : Cisco DC reference architecture reflects the complete stack from resource management through to portal capability and to deliver Fast IT Important that this isn't a technology stack, this is a reference architecture allowing the customer to move to a policy driven automated and repeatable capability that delivers business outcomes NOT IT only outcomes Capability to consume a complete Cisco stack however we have an architecture that is open and eco-system driven Customer can choose the products and services that best suite their particular business outcome