© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Connect 11© 2013 Cisco and/or its affiliates. All rights re...
Agenda• Building a Data Center Baseline: Where we are coming from• Near term directions and technologies in the DC• Where ...
© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Connect 3Building a DataCenter Baseline:Where we arecoming ...
Baseline of the Legacy DC Infrastructure - Keys• Infrastructure Deployment and Operational Models• Structured DC Design fo...
Baseline of the Legacy DC Infrastructure• Linear Deployment of Capacity and Resource Needs• Straightforward model of resou...
Baseline of the Legacy DC Infrastructure• Design is Imposed on Every Rack within DC• Infrastructure designed for easy and ...
Baseline of the Legacy DC Network Infrastructure• The Data Centre Switching Design was basedon the hierarchical switching ...
Baseline of the Legacy DC Infrastructure• Ongoing Operations Managed atPoints of Intersection• Items Within Single DomainU...
Baseline of the Legacy DC Infrastructure• Today L3 knowledge on servicesdevices• Different levels of support• Configuratio...
Baseline of the Legacy DC Infrastructure• Segmentation Between DC Locations• Often a Cold Site Due to Networking and Stora...
Baseline of the Legacy DC Infrastructure• Business Need timing Impacts – Whiteboard to Service RealizationTRADITIONALINDUS...
© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Connect 12Near termdirections andtechnologies in theDC
Current DC Directions, Projects, and Goals - Keys• Abstracting, Converging, and Virtualizing more of the DC Infrastructure...
Current DC Directions, Projects, and Goals• Virtualizing the Server andits I/O brings Deploymentand Operations Advantages•...
Current DC Directions, Projects, and Goals• Virtualizing the DC Services Layer for Deployment and Operations AdvantagesDis...
Current DC Directions, Projects, and Goals• Converging the Infrastructure Silos for Deployment and Operations Advantages• ...
Current DC Directions, Projects, and Goals• Increasing Mobility of Services within multiple DCsL2 Domain Elasticity:vPC, L...
Current DC Directions, Projects, and Goals• Movement to Scale-Out HA models vs. Scale-Up• Scale Up:5 – 9’s uptimeBig IronA...
Current DC Directions, Projects, and GoalsClientsDesktop Virtualization S/WVirtualized Data CenterCiscoWAASHypervisorCisco...
Current DC Directions, Projects, and Goals• Movement of Mobile Compute into the DC (Millions)A shift from desktop-centric ...
Current DC Directions, Projects, and Goals• Outsourcing of Application• Outsourcing of Platform Management• Outsourcing of...
Current DC Directions, Projects, and Goals• Tight Coupling of Needs to Provisioning – Self Service• Emerging Capability to...
Current DC Directions, Projects, and Goals• Tight Coupling of Needs to Provisioning – Self Service Typically Mandates VM’s...
© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Connect 24Where are wegoing in the DC asan industry
The Data Center EvolutionApp 1 App 2PhysicalVirtualProgrammable• One app per server• Static environment withmanual provisi...
Coming Industry Direction inside the DC - Keys• Creating a Programmatic and Application Controlled Infrastructure – Withou...
Industry Directions inside the Data Center• Stateless Infrastructures and OPEX CostsSERVER-RELATED SPEND (CAPEX+OPEX)WW Sp...
Industry Directions inside the Data Center• Making the Infrastructure Inherently as Stateless as PossibleQueueAppOSPhysica...
Industry Directions inside the Data Center• Creating a Standardized API to Orchestrate with User ToolsConsolidateAssetsVir...
Industry Directions inside the Data Center• Beginning with a Separation of Control Plane and Data Plane• Easier Programmat...
Software Defined Networking (SDN) – What is it?Many Definitions• Openflow• Controller• Openstack• Overlays• Network virtua...
Software Defined Networking (SDN)What Is Software Defined Network(SDN)?“…In the SDN architecture, the control and dataplan...
Software Defined Networking (SDN)Software APIApplication ControlController OverlaysComputeCompute Storage Storage Services...
What Really Does a Controller Do?• These are not newWireless Controllers to centrally manage Access PointsControlling Brid...
Industry Directions inside the Data Center• One Direction is to Eliminate ControlPlane completely on Element• White Box Se...
Industry Directions inside the Data Center• Moving to Direct Control of Policies andPooling of the Underlying Infrastructu...
Industry Directions inside the Data Center• Underlying Hardware will Still Matters – Cannot Rely on Software Libraries/Ove...
Industry Directions inside the Data Center• Create “Application Profiles” to be Consumed above the Hypervisor or even OS l...
Industry Directions inside the Data Center• Pre-Integrated Stacks for Just In Time Growth and Stability• Earlier Slide Tal...
Industry Directions inside the Data Center• Ease in Provisioning and Moving Workloads between DCs, and Off Premise to Prov...
Industry Directions inside the Data Center• Scale-Out Service Availability with InProduction Maintenance• Change windows t...
Industry Directions inside the Data Center• Whiteboarding a Business Need to Deployment – Making this Automatic• Tight Cou...
© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Connect 43How is Ciscodeveloping our DCproducts to meetthes...
How Cisco is Meeting These Demands - Keys• Unification and Virtualization of the Server Infrastructure and DC Edge• Unific...
Unification and Virtualization of the ServerInfrastructure and DC EdgeNetwork interfacecard(NIC) configuration:MAC address...
Unification and Virtualization of the ServerInfrastructure and DC EdgeXML APISTANDARDAPI’SFabric Extenders(I/O modules)Ind...
Cisco UCS and the Software Defined Server
Cisco UCS and the Software Defined ServerBlade AG:BIOSRAIDCPLDBoot MethodBMC SetupAlertingEtc.NIC AG:# NICsNetworks to Tie...
Cisco UCS is a Software Defined Server• We start with a data model that includes the existence, identity, and configuratio...
Unification and Virtualization of the DC FabricFabricAppAppAppAppIntegrated Intelligent InfrastructureFabric-Based Archite...
Unification and Virtualization of the DC Fabric• Network Function Virtualization (NfV)• Compute, storage and memoryinterco...
Unification and Virtualization of the Orchestration of DCServices Layer• Network Services Virtualization (NsV)Fabric Based...
Unification of the Control and Programmatic usage ofthis InfrastructureAutomatedSelf-ServiceProvisioningArchitect Design W...
Easing Deployment with Pre-Integrated SolutionsSmartSolutionsApplicationsOperatingSystem andHypervisorManagementVerticalSo...
Software Defined Networking (SDN) and Cisco• We have a Software Defined Compute and Network Edge today in UCS• Open Networ...
Research/Academia ExperimentalOpenFlow/SDNcomponents forproductionnetworksCustomer Insights: Network ProgrammabilityNetwo...
Research/Academia ExperimentalOpenFlow/SDNcomponents forproductionnetworksMassively ScalableData Center Customize withPr...
Research/Academia ExperimentalOpenFlow/SDNcomponents forproductionnetworksMassively ScalableData Center Customize withPr...
Research/Academia ExperimentalOpenFlow/SDNcomponents forproductionnetworksMassively ScalableData Center Customize withPr...
Private CloudAutomationResearch/Academia ExperimentalOpenFlow/SDNcomponents forproductionnetworksMassively ScalableData C...
Evolution of the Intelligent NetworkPreserve What’s Working Evolve for Emerging RequirementsEvolve the Network for the Nex...
Open Network Environment (ONE)Policy AnalyticsOrchestrationProgram forOptimizedExperienceHarvestNetworkIntelligenceNetwork
Network Programmability ModelsControl PlaneData PlaneCLI,SNMP,Netflow,…Applications(Network Mgmt,Monitoring, …)
Control PlaneData PlaneVendor-specific APIsApplications1 Programmable APIsControl PlaneData PlaneVendorSpecific(e.g. onePK...
Control PlaneData PlaneControllerData PlaneApplicationsVendor-specific APIsOpenFlow,PCEP,I2RS2a Classic SDNVendorSpecific(...
Control PlaneData PlaneControllerData PlaneApplicationsVendor-specific APIsOpenFlow,PCEP,I2RS2a Classic SDNVendorSpecific(...
Control PlaneData PlaneControllerData PlaneApplicationsVendor-specific APIsOpenFlow,PCEP,I2RS2a Classic SDNVendorSpecific(...
Approach 1 Approach 2 Approach 3Implementing Customer Use CasesAppsControllerOpenFlowDeviceDevice w/OpenFlowDeviceApps App...
Open Network Environment (ONE)aIndustry’s Most Comprehensive PortfolioHardware + Software Physical + Virtual Network + Com...
Any CiscoRouter orSwitchApplicationsThat YOUCreateonePKFlexible development environment to:• Innovate• Extend• Automate• C...
Open Network Environment – Flexibility to ChooseABILITYTOSPANLAYERS Packet classifiers Marking Copy/Punt Inject Statis...
OpenDaylight and Cisco• Extension to Cisco ONE Controller• Open Source version of this Controller• Wide Vendor Backing
Public Cloud for DC Services• Greatly Simplified Drawing• Applications Need toConsume these API’s
InterCloud CharacteristicsData CenterPrivate CloudVirtual Private CloudCloud ServicesBenefits: Network consistency, securi...
InterCloud with Nexus 1000VOtherTenantsProvider Cloud(any hypervisor)Enterprise Cloud(Private/Managed/Hosted Cloud)Private...
InterCloud with Nexus 1000VTRADITIONALINDUSTRYAPPROACH1 2 3 4 5 6 7 8 9 10CreateTemplatefrom VMImageCreate VMInstanceFromT...
IT and Service Fulfillment – Brokering and Delivery• Coordination of theBusiness UsersNeeds• Where things arephysically re...
OpenStack and CiscoCisco Plug-InUCS, Nexus, OverDriveExtensions for QoSNicira Plug-InOpen vSwitchOther Plug-In
© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Connect 79Summary
Cisco Evolution of the Data CenterLAN SANComputeStorageApplicationComputeStorageApplicationLAN SANComputeStorageApplicatio...
Cisco Evolution of the Data CenterCiscoNetworkingUnified Fabricwith NexusNexus 1000VUnifiedComputingSystemsFabricPath andO...
The Evolving DC - Summary Points (Vision->Action)• Look at Adding Capacity, Consumption, while Minimizing Human Involvemen...
Complete Your Paper“Session Evaluation”Give us your feedback and you could win1 of 2 fabulous prizes in a random draw.Comp...
© 2013 Cisco and/or its affiliates. All rights reserved. Cisco Connect 84Thank you.
Upcoming SlideShare
Loading in...5
×

The Evolving Data Center – Past, Present and Future

874

Published on

The journey to Cloud is not linear. Realistically, most environments will have workloads that continue to run on both physical and virtualized infrastructures for some time. Join Cisco’s Data Centre Experts, as they outline the key technologies transforming the Data Centre, enabling an intelligent infrastructure which will support physical, virtualized and cloud applications as part of Cisco’s Unified Data Centre Architecture.

Published in: Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
874
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

The Evolving Data Center – Past, Present and Future

  1. 1. © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Connect 11© 2013 Cisco and/or its affiliates. All rights reserved.TorontoMay 30, 2013The Evolving DataCentre – Past,Present, and FutureDan Hanson, Technical MarketingEngineering, Data Center GroupFollow us on Twitter at #CiscoConnect_TO
  2. 2. Agenda• Building a Data Center Baseline: Where we are coming from• Near term directions and technologies in the DC• Where are we going in the DC as an industry• How is Cisco positioning our DC products to “Go where the puck is going to be,not where it’s been”
  3. 3. © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Connect 3Building a DataCenter Baseline:Where we arecoming from
  4. 4. Baseline of the Legacy DC Infrastructure - Keys• Infrastructure Deployment and Operational Models• Structured DC Design for Compute, LAN, Storage, Security, and Facilities• Services Capacity and Geographical Capabilities• Business Need to Service Delivery Process and Timing Capabilities
  5. 5. Baseline of the Legacy DC Infrastructure• Linear Deployment of Capacity and Resource Needs• Straightforward model of resource consumption• Each Item has its own SW and FW Images, and Configurations• Each Item also has its own Operations and MaintenanceAppOSPhysicalServerCorpAppOSPhysicalServerAppOSPhysicalServerDBDBFinanceDBAppOSPhysicalServerMktgAppOSPhysicalServerStorageEngineeringAppOSPhysicalServerAppOSPhysicalServerDBDBHR
  6. 6. Baseline of the Legacy DC Infrastructure• Design is Imposed on Every Rack within DC• Infrastructure designed for easy and repeatable integration• Layers of Management software holding the system together – integrated withother software packages• Rigid and inter-twined models to upgrade and maintain system-level designs• Multiple tools and points of configuration• Structured Design for Compute, LAN, SAN, Security, Environmentals, etc.• Manifested as rack-by-rack or row-by-row capability and limitsManagement Software LayersPEOPLE, PROCESS, TECHNOLOGY
  7. 7. Baseline of the Legacy DC Network Infrastructure• The Data Centre Switching Design was basedon the hierarchical switching we usedeverywhereThree tiers: Access, Aggregation and CoreL2/L3 boundary at the aggregationImages on devices, Configuration on devicesSmaller scale, single purpose serversDedicated structure cabling built into racks upfront (state)Add in services and you were done• What has changed? Most everythingSheer Volume and Growth RatesFragmentation and DC Space EfficiencyHypervisor LayerCloud and IaaS, PaaS, SaaSHighly Elastic ConsumptionProgrammatic Usage NeedsDifferentiated Service NeedsLayer 2Layer 3AccessCoreServicesAggregation
  8. 8. Baseline of the Legacy DC Infrastructure• Ongoing Operations Managed atPoints of Intersection• Items Within Single DomainUsage Option SetTraining RequirementsProvisioning and GrowthLess Customization• Between these DomainsWide Array of OptionsHighly Customized – more meetingsBest PracticesDisparate Points of ManagementHigher Staff and Training CostsServerStorageNetworkSecurity
  9. 9. Baseline of the Legacy DC Infrastructure• Today L3 knowledge on servicesdevices• Different levels of support• Configuration serially done• Define service providing devices as IPend-points• Virtually connect contexts as if theyare directly connected on LANsegmentsClientLayer 3Infrastructure
  10. 10. Baseline of the Legacy DC Infrastructure• Segmentation Between DC Locations• Often a Cold Site Due to Networking and Storage Restrictions• Attempts at active/active Initially were to Statically Host ServicesAsynchronousStorageWAN to DCCampus to DCDC returnDCIDC-1 DC-2
  11. 11. Baseline of the Legacy DC Infrastructure• Business Need timing Impacts – Whiteboard to Service RealizationTRADITIONALINDUSTRYAPPROACH -SIMPLIFIEDWhiteboardDesignProduce cutsheets toteamsIdentifyNeedsProvisionStorageIdentifyServerClassIdentifyNetworkNeedsMaskLUNsIdentifyServerInstanceShareWWN’sConfigureSAN EdgeDetermineDCPlacementShareLocationZoneFabricConfigureNetworkEdgeFacilitiesStageServerFirmwareUpdatesBIOSPolicySettingsRAIDSettingsImage OSCoordinateEnds ofCablesCoordinateEnds ofCablesJoinSystemsMgmtDomainUpdateSecurityPolicyInstallApplication
  12. 12. © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Connect 12Near termdirections andtechnologies in theDC
  13. 13. Current DC Directions, Projects, and Goals - Keys• Abstracting, Converging, and Virtualizing more of the DC Infrastructure for Deploymentand Operational Benefits• Easing the Restrictions of Structured Design• Embracing Service Delivery Independent of Location – Including Campus Needs• Tighter Coupling of Provisioning and Delivery for Accelerated Deployments
  14. 14. Current DC Directions, Projects, and Goals• Virtualizing the Server andits I/O brings Deploymentand Operations Advantages• Compute, Network, andStorage Virtualization at theHardware layer is anotherEnabler• Each Item still has its ownOperations andMaintenance – butconverging• Each Layer handling HAindividuallyAppOSPhysicalMachineAppOSPhysicalMachineFinanceAppOSVirtualMachineMktgAppOSPhysicalMachineEngineeringAppOSVirtualMachineAppOSVirtualMachineHRCloud Infrastructure ServiceStorageAppOSCorpVirtualMachineStorageDB ServiceQueuePhysical and Virtual Infrastructure Service
  15. 15. Current DC Directions, Projects, and Goals• Virtualizing the DC Services Layer for Deployment and Operations AdvantagesDistributed• Manual Provisioning• Flow Engineering toIntegrate Services• Limited scaling• Rack-wide VMmobilityFabric BasedCloud• Policy-basedProvisioning• Services ProvidedEverywhere withinFabric**• Scale Physical andVirtual/Cloud• DC-wide/Cross-DC VMMobilityComputeCompute Storage Storage Services ServicesL2,L3FabricCloud
  16. 16. Current DC Directions, Projects, and Goals• Converging the Infrastructure Silos for Deployment and Operations Advantages• Makes Programmatic I/O Possible without Server Virtualization Need• The key is how this is accomplished??IndividualEthernets (vNICs)DCB EthernetStorage (vHBAs)Blade ManagementChannels (BMC Connections)x86 ServerNICNICNICMgmtMgmtHBAHBAPCIe Treex86 ServerPCIe Tree
  17. 17. Current DC Directions, Projects, and Goals• Increasing Mobility of Services within multiple DCsL2 Domain Elasticity:vPC, L2MP/TRILLOTV LAN extensionsOTVVN-linknotificationsIP localization:LISPVM-awareness:VN-linkPort ProfilesStorage Elasticity:FCIP, IO AccelerationFCoE, Inter-VSAN routingDevice Virtualization:VDCs,VRF enhancementsOTVOTVOTVCompute resources are part of the cloud, location is transparent to the user
  18. 18. Current DC Directions, Projects, and Goals• Movement to Scale-Out HA models vs. Scale-Up• Scale Up:5 – 9’s uptimeBig IronAdvanced RAS FeaturesNo Outages in Maintenance ActivitiesAnalogy: Large roadway that can only have lane closures – Overbuild excess lanes for this• Scale Out:4 – 9’s uptimeLower Cost x86Intermediate RAS FeaturesEvacuate Portions of Infrastructure (Maintenance Modes)Analogy: Many smaller roads - Detour traffic and work on sections of roadway incrementally
  19. 19. Current DC Directions, Projects, and GoalsClientsDesktop Virtualization S/WVirtualized Data CenterCiscoWAASHypervisorCiscoACEDesktop O/SCiscoASACiscoMDS9000FamilyApp App DataStorageUnifiedNetwork ServicesUnifiedComputingUnifiedFabricWANPartner SolutionElements• Movement of CampusDesktops into DC• Combined joint partnersolutions with industry leaders• Cisco Validated Designs &Services to acceleratecustomer successCisco Data Center Business Advantage FrameworkVirtualization
  20. 20. Current DC Directions, Projects, and Goals• Movement of Mobile Compute into the DC (Millions)A shift from desktop-centric end-user compute to mobile devices,and intelligent endpoints - multiple networks, multiple locationsSource: IDC
  21. 21. Current DC Directions, Projects, and Goals• Outsourcing of Application• Outsourcing of Platform Management• Outsourcing of Infrastructure Sections• Moving Applications into Public CloudCost Models vs. Application Re-WritesSecurity of Content• Moving Tiers of Application into Public CloudInterconnections and Replicating ServicesPrivate ChannelsData Center InfrastructureCompanyBusinessUnit ABusinessUnit BServices/PoliciesServices/PoliciesUnit A Web ServersCloud Provider InfrastructureUnit B Web ServersUnit A Logic ServersUnit B Logic ServersUnit A Logic Servers Unit B Logic ServersUnit A DB Servers Unit B DB ServersUnit A&B SecurityUnit A Security Unit B Security
  22. 22. Current DC Directions, Projects, and Goals• Tight Coupling of Needs to Provisioning – Self Service• Emerging Capability to Allow Self Service
  23. 23. Current DC Directions, Projects, and Goals• Tight Coupling of Needs to Provisioning – Self Service Typically Mandates VM’s• Bare Metal Model Unchanged – Used for Virtualization Provider Rollouts• Management and Troubleshooting of Overlays not shown here• Single Admin with Full Control on InfrastructureAFTERINFRASTRUCTUREPRE-PROVISIONINGON HYPERVISORWhiteboardDesign Producecut sheets – butfewer teamsinvolved at timeof needIdentifyNeedsIdentifyVirtual DCDeploy VMfrom OVFUpdateSecurityPolicyUpdateVirtualizedServicesNeedsImage OS JoinSystemsMgmtDomainInstallApplicationConfigureNetworkEdgeIdentifySharedData Store
  24. 24. © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Connect 24Where are wegoing in the DC asan industry
  25. 25. The Data Center EvolutionApp 1 App 2PhysicalVirtualProgrammable• One app per server• Static environment withmanual provisioning• One app per VM• Mobile environment withdynamic provisioning• Any app, anywhere• Elastic environment withautomated provisioningMonths to provision Days to provision Minutes to provision
  26. 26. Coming Industry Direction inside the DC - Keys• Creating a Programmatic and Application Controlled Infrastructure – Without overlayingeverything with numerous software stacks• Eliminating the Restrictions of Structured Design with a Stateless Edge• Just-in-time capacity expansion with Pre-Integrated Stacks• Service delivery capabilities and location becomes and attribute requested by applicationitself• Full Integration of Business Need definition to Provisioning and Delivery
  27. 27. Industry Directions inside the Data Center• Stateless Infrastructures and OPEX CostsSERVER-RELATED SPEND (CAPEX+OPEX)WW Spending on Servers, Power & Cooling,and Mgmt. / AdministrationOVERALL SPEND DISTRIBUTIONSource: Gartner—Cisco IT, “Data Center CostPortfolio”Source: IDC, “New Economic Model for the Datacenter”HighOPEXIDC, 2011CustomerSpending($B)
  28. 28. Industry Directions inside the Data Center• Making the Infrastructure Inherently as Stateless as PossibleQueueAppOSPhysicalMachineAppOSPhysicalMachineFinanceAppOSVirtualMachineMktgAppOSPhysicalMachineEngineeringAppOSVirtualMachineAppOSVirtualMachineHRStorageAppOSCorpVirtualMachineStorageDB ServiceCloud Infrastructure ServicePool of shared resourcesSelf-service portalAPI-driven services Selective application mgmt
  29. 29. Industry Directions inside the Data Center• Creating a Standardized API to Orchestrate with User ToolsConsolidateAssetsVirtualize theEnvironmentAutomateServiceDeliveryStandardizeOperationsIncreased Agility, Efficiency and SimplicityIncreased Cloud Readiness
  30. 30. Industry Directions inside the Data Center• Beginning with a Separation of Control Plane and Data Plane• Easier Programmatic Control• API with the Centralized Controller Architecture CommonAbstract extensions for optimized services to API methodsMove to centralized policies and pools of how resources are consumed• Industry offerings vary in terms of where some middleware would liveMiddleware to control advanced ASIC functionality, and other HW capabilitiesSupport of these API extensionsExpanding these into Open Source living on the Platforms
  31. 31. Software Defined Networking (SDN) – What is it?Many Definitions• Openflow• Controller• Openstack• Overlays• Network virtualization• Automation• APIs• Application oriented• Virtual Services• Open vSwitch
  32. 32. Software Defined Networking (SDN)What Is Software Defined Network(SDN)?“…In the SDN architecture, the control and dataplanes are decoupled, network intelligence andstate are logically centralized, and the underlyingnetwork infrastructure is abstracted from theapplications…”Source: www.opennetworking.orgWhat is OpenStack?Opensource software for building publicand private Clouds; includes Compute (Nova),Networking (Quantum) and Storage (Swift)services.Source: www.openstack.orgWhat is Overlay Network?Overlay network is created on existing networkinfrastructure (physical and/or virtual) using a networkprotocol. Examples of overlay network protocol are:GRE, VPLS, OTV, LISP and VXLANWhat Is OpenFlow?Open protocol that specifies interactions betweende-coupled control and data planesNote: OF is not mandatory for SDNNote: North-bound Controller APIs are vendor-specificNote: Applicable to SDN and non-SDN networksNote: Applicable to SDN and non-SDN networksNote: SDN is not mandatory for network programmabilitynor automation
  33. 33. Software Defined Networking (SDN)Software APIApplication ControlController OverlaysComputeCompute Storage Storage Services ServicesL2,L3FabricApplications• Policy-based Provisioning• Scale Physical & Virtual/Cloud• DC-wide/Cross-DC VM MobilityComputeCompute Storage Storage Services ServicesL2,L3FabricControllerComputeCompute Storage Storage Services ServicesL2,L3FabricOverlayNetworks• Policy-based Provisioning• Multiple Tunnels (Visibility?)• Scaling (Overlay disjoint from Physical)• Writing to single ONEpk API• Infrastructure Controlled byApplications• Wide-reach, beyond Data Center
  34. 34. What Really Does a Controller Do?• These are not newWireless Controllers to centrally manage Access PointsControlling Bridge in all FEX architecturesVM Managers – things like Auto-Deploy• More than just Control Plane/Data Plane SeparationAll modern modular devices have that separation in a sense• Expanding the scopeSpan entire DC segments (or inter-DC) at scaleHost the Running Images and Components (FEX, Auto Deploy, etc.)Host the Device Configurations (FEX, Auto Deploy, WiFi, etc.)Model Driven Imposition of detailed configuration lines no longer in user spaceAdministrators configure the models end to end nowAPI’s to allow the end using processes, portals, etc. to configure the modelsAPI’s for the reporting and subscription to monitoring and event subscription
  35. 35. Industry Directions inside the Data Center• One Direction is to Eliminate ControlPlane completely on Element• White Box Servers• Merchant Silicon on networking• “White Box” Network and Storage gearcarry little management• Goal is to effectively open source code ofdevices to users• Different views by Market SegmentControllerSWHWPlatform Vendor Provided OS & MW 3rd Party AgentsInternal Processing ArchitectureGeneral Purpose ElementsOptimized ElementsBaseline Control OS – Auto PushedDevice Configuration – Auto PushedMethods for ReportingCustomerAppVendorAppISVAppElement
  36. 36. Industry Directions inside the Data Center• Moving to Direct Control of Policies andPooling of the Underlying Infrastructure• Feature Rich Integration• Controller to Element Closed in its Nature• Northbound Methods Open• UCS Model Fits here TodayControllerHWPlatform Vendor Provided OS & MW 3rd Party AgentsInternal Processing ArchitectureGeneral Purpose ElementsOptimized ElementsElement
  37. 37. Industry Directions inside the Data Center• Underlying Hardware will Still Matters – Cannot Rely on Software Libraries/Overlays Only• White Box Servers with little managementDo we have precedents here?One example: Are their advantages in processor families for workloads (VT-x, VT-d, TXT for VM boot, ) or ischeapest OK?• “White Box” Network and Storage gear with little managementSame example: Will all networking ASICs lose any value, will cheapest device be OK?• Goal is to effectively open source code of devices to usersDo we want the ability to open for some customizations, or do we want to fully write our complete controlplane?Key item here – What Optimizations are Needed and how to put in API?• Different views by Market SegmentProviders will be more capable of developing this IP and its lifecycle – will others want this vs. Off the Shelf?Example: Do we want to expose the core OS for loading of custom code, or offer API to control?
  38. 38. Industry Directions inside the Data Center• Create “Application Profiles” to be Consumed above the Hypervisor or even OS level• Needs from DC Fabric for IO and Services Mapped to PolicyPolicies Mapped to Application Hosts (PM and/or VM)Requested directly by these applications via APIStorage ServicesDirectory ServicesWeb PresenceSAML
  39. 39. Industry Directions inside the Data Center• Pre-Integrated Stacks for Just In Time Growth and Stability• Earlier Slide Talked to Management at Vendor Product IntersectionThis is key area and reason for these models• API’s Include Metering and the Pay Per Use Growing Trend• Integrated Stack Optionally Includes Orchestration (UIM, CIAC, Cloupia, etc.)• Orchestration over Scaled-Out Pods
  40. 40. Industry Directions inside the Data Center• Ease in Provisioning and Moving Workloads between DCs, and Off Premise to ProviderTime To Monetize• Innovate new products andservices at an accelerated rateTime To Develop• Real-time bridging of applicationdevelopers to users/CustomersApps and Apps• Buy Apps• Buy Services• Leverage from Partners• DevelopScale and Scale• Users, Devices, LocationsReduceCostPerBizMetricBizContinuity,DR,Security,MissionCriticalMore Applications• IDG: On an average enterprises will add 46new apps in 2013Services orientation• Apps in sync with infrastructureCross Cloud services integration• Private and Public cloudsFlexible architecture• Scale as needed• (Pay as needed)Prepare for the Unpredictable
  41. 41. Industry Directions inside the Data Center• Scale-Out Service Availability with InProduction Maintenance• Change windows that can span many days• Not just VM’s but Fabric Service ProvidersAppOSAppOSAppOSClient
  42. 42. Industry Directions inside the Data Center• Whiteboarding a Business Need to Deployment – Making this Automatic• Tight Coupling of Needs to Provisioning – Self Service for VMs and Bare Metal• All Provisioning is done on Policy Basis – Before any Rollouts• Admin expertise is retained with Control of their segment on InfrastructureAFTERINFRASTRUCTUREPRE-PROVISIONING(Physical and Virtual)Whiteboard DesignProduce FinalDesignIdentifyNeedsEnd User: Identify onbasis of securityneeds: Physical DC,or Cloud PreferencesEnd User: Deploy PM orVM from audited PolicyTemplate with SecurityAdminImage OS JoinSystemsMgmtDomainInstallApplicationEnd User: IdentifyPolicy driven networkedge, Pre-coordinated withNetwork AdminEnd User: IdentifyStorage Needs,Pre-coordinatedwith StorageAdmin
  43. 43. © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Connect 43How is Ciscodeveloping our DCproducts to meetthese needs
  44. 44. How Cisco is Meeting These Demands - Keys• Unification and Virtualization of the Server Infrastructure and DC Edge• Unification and Virtualization of the DC Fabric• Unification and Virtualization of the Orchestration of DC Services Layer• Unification of the Control and Programmatic usage of this Infrastructure• Easing Deployment with Pre-Integrated Solutions• Linking these New Infrastructure Capabilities Directly to Emerging Provisioning ModelsSoftware Defined Networking (SDN)Cisco Open Network Environment (ONE)Project Daylight and Open SourcePrivate CloudPublic CloudInterCloudOpenStack
  45. 45. Unification and Virtualization of the ServerInfrastructure and DC EdgeNetwork interfacecard(NIC) configuration:MAC address, VLAN,and QoS settings; host busadapterHBA configuration: worldwidenamesWWNs), VSANs, and bandwidthconstraints; and firmwarerevisionsProcessor MemoryHBAsNICsConfigurationToday’s Server: Fixed Set of ResourcesHypervisorApplicationServer Architecture for Virtualization and Cloud:Networked Pools of ComputingApplicationNetwork interfacecard(NIC) configuration:MAC address, VLAN,and QoS settings; host busadapterHBA configuration: worldwidenamesWWNs), VSANs, and bandwidthconstraints; and firmwarerevisionsAPI
  46. 46. Unification and Virtualization of the ServerInfrastructure and DC EdgeXML APISTANDARDAPI’SFabric Extenders(I/O modules)IndustryStandard APIsBlade Form FactorRack Form FactorFABRIC INTERCONNECTSUCS ManagerCOMPUTEAutomationIntelligenceConvergence
  47. 47. Cisco UCS and the Software Defined Server
  48. 48. Cisco UCS and the Software Defined ServerBlade AG:BIOSRAIDCPLDBoot MethodBMC SetupAlertingEtc.NIC AG:# NICsNetworks to Tie inQOS and Security Policy# HBAsVSANs to Tie inQoS and Security PolicyEtc.XML APIManagementInformation Tree(MIT)RootServerI/ORAID BIOSNIC1 HBA1I/OEdgeEth PortConfig:NIC1FC PortConfig:HBA1“Front End”“Back End”Port AG:Ether Port NetworksQoS PolicySecurity PolicyLinkages to Server NICsNetwork SegmentsEtc.Fabric AG:Storage SegmentsVSAN MappingsF Port TrunkingF Port ChannelingZoning **Etc.Other AG’s:VMM AGHost Agent AGEtc.
  49. 49. Cisco UCS is a Software Defined Server• We start with a data model that includes the existence, identity, and configuration of aserver and its various sub-componentsDeep model of very fundamental components within servers• We grow this data model to include upstream I/O needs to include the configuration ofthe upstream devices ports connecting to this serverCoupling of the “other end” of the cables that connect these servers to the DC• We include policies to define groupings of these servers, priorities, security segments,and many othersTo offer differentiated services, for example different x86 processor types• We probe newly added hardware, to classify them into service level tiers by capabilityTo ease not only the customer consumption of services, but also provider capacity growth• We map these modeled servers and all surrounding component needs to these servicelevel tiers when the actual services are required
  50. 50. Unification and Virtualization of the DC FabricFabricAppAppAppAppIntegrated Intelligent InfrastructureFabric-Based ArchitectureAppliance ArchitecturesAppSpecialized InfrastructureApp App AppAppManagement SoftwareApp App AppCommodity Server, Network and SecurityVirtual Overlay ArchitectureLegacy ArchitecturesOperational Flexibility, ScalabilityApplication,Capacity,ThroughputandPerformance
  51. 51. Unification and Virtualization of the DC Fabric• Network Function Virtualization (NfV)• Compute, storage and memoryinterconnected by a network fabric• Creates abstracted pool of resourceswithin and between data centers• Integrated and simplified management• APIs to integrate with any application,any timeComputeCompute Storage Storage Storage StorageSecure, ScalableData Center Fabric ArchitectureProgrammableMonitoringAppsNetworkingAppsEnd UserAppsMission CriticalAppsBuilt-in ManageabilityPolicy-based ProvisioningDC-wide/Cross-DC VM MobilityCharacteristics“Definition of fabric-basedinfrastructure:Compute, storage, memory and I/Ocomponents joined through a fabricinterconnect, and the software to configureand manage them” - Gartner
  52. 52. Unification and Virtualization of the Orchestration of DCServices Layer• Network Services Virtualization (NsV)Fabric BasedCloud• Policy-basedProvisioning• Services ProvidedEverywhere withinFabric**• Scale Physical andVirtual/Cloud• DC-wide/Cross-DC VMMobilityComputeCompute Storage Storage Services ServicesL2,L3FabricCloudApplication Driven• Service-centric Provisioning• Fabric Service Pointers forVirtual and Bare Metal(vPath, etc.)• Flexible – Anywhere,Anytime• Cross-cloud VM MobilityComputeCompute Storage Storage Services ServicesL2,L3Programmable ProvisionableMonitoringAppsProvisioningAppsNetworkingAppsEnd-UserAppsIntegrated Fabric and CloudWorld of Many Clouds
  53. 53. Unification of the Control and Programmatic usage ofthis InfrastructureAutomatedSelf-ServiceProvisioningArchitect Design Where CanWe Put It?Procure Install Configure Secure Is It Ready?ManualCapacityOn-DemandPolicy-BasedProvisioningBuilt-InGovernanceFROM 8 WEEKS TO 15 MINUTES
  54. 54. Easing Deployment with Pre-Integrated SolutionsSmartSolutionsApplicationsOperatingSystem andHypervisorManagementVerticalSolutionFocusEnterprise Apps Databases Business Analytics/ Big DataVirtual DesktopRISC MigrationVXIVblockFLEXPODRetailHealthcare ManufacturingFinancialServices
  55. 55. Software Defined Networking (SDN) and Cisco• We have a Software Defined Compute and Network Edge today in UCS• Open Networking Environment (ONE) to Bring to Fabric• ONE Programming Kit (ONE PK)To program the infrastructure• Physical and VirtualComputeLAN SegmentsStorage SegmentsSecurity ServicesClient Services• New Models for Controller?Can the Controller itself move from a HA pair of appliances – to a N-Wise fabric service also? Yes
  56. 56. Research/Academia ExperimentalOpenFlow/SDNcomponents forproductionnetworksCustomer Insights: Network ProgrammabilityNetwork“Slicing”
  57. 57. Research/Academia ExperimentalOpenFlow/SDNcomponents forproductionnetworksMassively ScalableData Center Customize withProgrammaticAPIs to providedeep insight intonetwork trafficCustomer Insights: Network ProgrammabilityNetwork FlowManagementNetwork“Slicing”
  58. 58. Research/Academia ExperimentalOpenFlow/SDNcomponents forproductionnetworksMassively ScalableData Center Customize withProgrammaticAPIs to providedeep insight intonetwork trafficCustomer Insights: Network ProgrammabilityCloud Automatedprovisioning andprogrammableoverlay,OpenStackScalableMulti-TenancyNetwork FlowManagementNetwork“Slicing”
  59. 59. Research/Academia ExperimentalOpenFlow/SDNcomponents forproductionnetworksMassively ScalableData Center Customize withProgrammaticAPIs to providedeep insight intonetwork trafficService Providers Policy-basedcontrol andanalytics tooptimize andmonetizeservice deliveryCustomer Insights: Network ProgrammabilityCloud Automatedprovisioning andprogrammableoverlay,OpenStackScalableMulti-TenancyNetwork FlowManagementNetwork“Slicing”Agile ServiceDelivery
  60. 60. Private CloudAutomationResearch/Academia ExperimentalOpenFlow/SDNcomponents forproductionnetworksMassively ScalableData Center Customize withProgrammaticAPIs to providedeep insight intonetwork trafficService Providers Policy-basedcontrol andanalytics tooptimize andmonetizeservice deliveryEnterprise Virtual workloads,VDI, Orchestrationof security profilesCustomer Insights: Network ProgrammabilityCloud Automatedprovisioning andprogrammableoverlay,OpenStackDiverse Programmability Requirements Across SegmentsMost Requirements are for Automation & ProgrammabilityScalableMulti-TenancyNetwork FlowManagementNetwork“Slicing”Agile ServiceDelivery
  61. 61. Evolution of the Intelligent NetworkPreserve What’s Working Evolve for Emerging RequirementsEvolve the Network for the Next Wave of Application Requirements• Resiliency• Scale and Security• Rich feature-set• Operational Simplicity• Programmability• Application aware• Business Intelligence fromNetwork• Business driven NetworkAdaptation+
  62. 62. Open Network Environment (ONE)Policy AnalyticsOrchestrationProgram forOptimizedExperienceHarvestNetworkIntelligenceNetwork
  63. 63. Network Programmability ModelsControl PlaneData PlaneCLI,SNMP,Netflow,…Applications(Network Mgmt,Monitoring, …)
  64. 64. Control PlaneData PlaneVendor-specific APIsApplications1 Programmable APIsControl PlaneData PlaneVendorSpecific(e.g. onePK)CLI,SNMP,Netflow,…Applications(Network Mgmt,Monitoring, …)
  65. 65. Control PlaneData PlaneControllerData PlaneApplicationsVendor-specific APIsOpenFlow,PCEP,I2RS2a Classic SDNVendorSpecific(e.g. onePK)Vendor-specific APIsApplications1 Programmable APIsControl PlaneData PlaneVendorSpecific(e.g. onePK)CLI,SNMP,Netflow,…Applications(Network Mgmt,Monitoring, …)
  66. 66. Control PlaneData PlaneControllerData PlaneApplicationsVendor-specific APIsOpenFlow,PCEP,I2RS2a Classic SDNVendorSpecific(e.g. onePK)ControllerData PlaneApplicationsVendor-specific APIsOpenFlow,PCEP,I2RSControl Plane2b Hybrid “SDN”Vendor-specific APIsApplications1 Programmable APIsControl PlaneData PlaneVendorSpecific(e.g. onePK)VendorSpecific(e.g. onePK)CLI,SNMP,Netflow,…Applications(Network Mgmt,Monitoring, …)
  67. 67. Control PlaneData PlaneControllerData PlaneApplicationsVendor-specific APIsOpenFlow,PCEP,I2RS2a Classic SDNVendorSpecific(e.g. onePK)ControllerData PlaneApplicationsVendor-specific APIsOpenFlow,PCEP,I2RSControl Plane2b Hybrid “SDN”ApplicationsVirtual SwitchOverlaysOverlayProtocols(e.g. VXLAN)Vendor-specific APIs3 Overlay NetworksControl PlaneData PlaneOverlaysVendor-specific APIsApplications1 Programmable APIsControl PlaneData PlaneVendorSpecific(e.g. onePK)VendorSpecific(e.g. onePK)Openstack and Network Overlays Apply to All Models (Physical/Virtual)Custom Features Can Be BuiltCLI,SNMP,Netflow,…Applications(Network Mgmt,Monitoring, …)
  68. 68. Approach 1 Approach 2 Approach 3Implementing Customer Use CasesAppsControllerOpenFlowDeviceDevice w/OpenFlowDeviceApps AppsAPIsNetwork NetworkCisco Approach: Flexibility to Choose—The Power of “AND”PhysicalandVirtualNetwork OverlaysOtherAgentsTightly-coupled HW & SWInvestment ProtectionLoosely-coupled HW & SWNew Use CasesLogical/overlay NetworksVM Mobility; Scalable Multi-tenancy
  69. 69. Open Network Environment (ONE)aIndustry’s Most Comprehensive PortfolioHardware + Software Physical + Virtual Network + ComputeMulti-layer APINetworkProgrammaticAPIsControllersand AgentsVirtualOverlaysVirtual Overlay(w/ Controller)ControllerApplications
  70. 70. Any CiscoRouter orSwitchApplicationsThat YOUCreateonePKFlexible development environment to:• Innovate• Extend• Automate• Customize• Enhance• ModifyONE Programming Kit (ONE PK)
  71. 71. Open Network Environment – Flexibility to ChooseABILITYTOSPANLAYERS Packet classifiers Marking Copy/Punt Inject StatisticsQuantum API Interface descriptions L2 network provisioning L3 and IP Addr. Mgmt. - comingRICHNESS OF FEATURESElement ElementCapabilities ConfigurationManagement Interface/PortsEvents LocationInformationUtilities Syslog Events andQueries AAA Interface Netflow Events DHCP EventsDiscovery Network ElementDiscovery Service Discovery TopologyDiscoveryDeveloper Debug Capabilities Tracing Interfaces ManagementExtensionsPolicy Interface Policy InterfaceFeature Policy ForwardingPolicy Flow ActionPolicyRouting ProtocolChangeEvents RIB TableQueriesDeveloper portalISVsTraining & Certification
  72. 72. OpenDaylight and Cisco• Extension to Cisco ONE Controller• Open Source version of this Controller• Wide Vendor Backing
  73. 73. Public Cloud for DC Services• Greatly Simplified Drawing• Applications Need toConsume these API’s
  74. 74. InterCloud CharacteristicsData CenterPrivate CloudVirtual Private CloudCloud ServicesBenefits: Network consistency, security consistency, policy consistencyOperating model: Do-it-yourself or provider-managed serviceUse cases: Bursting, DR, upgrade/migration
  75. 75. InterCloud with Nexus 1000VOtherTenantsProvider Cloud(any hypervisor)Enterprise Cloud(Private/Managed/Hosted Cloud)PrivateCloudL2 VirtualPrivate CloudNexus 1000V InterCloudSecure Hybrid CloudConsistent Policy,Management & OperationVM VM VMVSGNexus1000V vSwitchVM VM VMVSGNexus1000V vSwitch
  76. 76. InterCloud with Nexus 1000VTRADITIONALINDUSTRYAPPROACH1 2 3 4 5 6 7 8 9 10CreateTemplatefrom VMImageCreate VMInstanceFromTemplateDocumentNetwork,L4-7 PolicyShutdownAppExportVMConvertVM toProviderFormatStart VMin CloudDeploySite-to-SiteTunnelSelectVM toMigrateSelectVM toMigrateMigrateVMSelectDestinationCloud21Re-ConfigureProviderSecurityReconfigureNetworkPoliciesCISCOAPPROACH• Simplified Operations• Rapid Provisioning• Accelerated Time-to-Market
  77. 77. IT and Service Fulfillment – Brokering and Delivery• Coordination of theBusiness UsersNeeds• Where things arephysically residingdefined within SLA atservice request timePUBLICPRIVATEuser ITSaaSHybriduser ITSaaSCurrent FutureBusiness Partner andBroker of ServicesIaaSProvider of InfrastructureApp 1App 2App 3Service Portfolio
  78. 78. OpenStack and CiscoCisco Plug-InUCS, Nexus, OverDriveExtensions for QoSNicira Plug-InOpen vSwitchOther Plug-In
  79. 79. © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Connect 79Summary
  80. 80. Cisco Evolution of the Data CenterLAN SANComputeStorageApplicationComputeStorageApplicationLAN SANComputeStorageApplicationComputeStorageApplicationVMVMVMVMConverge LANand SAN,Physical andVirtualUnified FabricLAN SANComputeStorageApplicationComputeStorageApplicationVMVMVMVMIntegrateCompute andStorage to createpools ofresourcesUnified FabricUnified Computing LAN SANComputeStorageApplicationComputeStorageApplicationVMVMVMVMOpen API andProgrammableInterface into theFabricUnified FabricUnified ComputingUnified ManagementCisco ONEPhysicalServer CentricVirtualVM CentricProgrammableApplication Centric
  81. 81. Cisco Evolution of the Data CenterCiscoNetworkingUnified Fabricwith NexusNexus 1000VUnifiedComputingSystemsFabricPath andOTVCisco Cloupia andIntelligent AutomationNexus 1000VInterCloudCisco ONEPhysicalServer CentricVirtualVM CentricProgrammableApplication Centric
  82. 82. The Evolving DC - Summary Points (Vision->Action)• Look at Adding Capacity, Consumption, while Minimizing Human Involvement• Create a Standardized and Stateless Infrastructure• Add Programmatic Capacity to this InfrastructureOne model is with extensive software libraries and API’s, on Low Cost feature-poor HardwareAnother is with Optimized Hardware and these API’s for Infrastructure ProgrammabilityDe-couple the controller from the “Merchant Silicon” idea• Separation of Control and Data Planes is not EnoughMultiples of Each over a Secure Unified Infrastructure• Pre-Integrated Stacks that Include the Application are Growing RapidlyThe OS may not always be coupled with a VM Service Container Construct• Service Location is a Service Level Metric – Not a RoadblockVirtualized Servers can be another SLA item• Reduction in the Concept of an Outage WindowDrive to Zero but with full Maintenance Capacity In-Hours• Elimination of Layers between Business Need definition to Provisioning and Delivery
  83. 83. Complete Your Paper“Session Evaluation”Give us your feedback and you could win1 of 2 fabulous prizes in a random draw.Complete and return your paperevaluation form to the room attendantas you leave this session.Winners will be announced today.You must be present to win!..visit them at BOOTH# 100
  84. 84. © 2013 Cisco and/or its affiliates. All rights reserved. Cisco Connect 84Thank you.

×