Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

The Second Wave of Virtualisation

635 views

Published on

This session examines the second wave of the virtualisation tsunami to hit the shores of the data centre: that of network and application infrastructure. It looks at the architectural implications of Application Delivery Controller virtualisation in the data centre with a view to maintaining appropriate levels of reliability and scalability.

Published in: Technology
  • Be the first to comment

The Second Wave of Virtualisation

  1. 1. The Second Wave of Virtualisation<br />Owen Cole <br />Technical Director <br />F5 UK, Ireland and Sub Saharan Africa <br />
  2. 2. Opposing forces<br />We are being pushed to deliver uptime, responsiveness and compliance.<br />Vs.<br /><ul><li>…but budgetary strains are prompting consolidation </li></li></ul><li>Virtualisation... What's that then??<br />Virtualisation<br />Two general ‘techniques’<br />Physical Thing<br />Virtual Thing<br />Virtual Thing 1<br />Virtual Thing 2<br />Virtual Thing 3<br />Virtual Thing N<br />Physical Thing 1<br />Physical Thing N<br />Physical Thing 2<br />Physical Thing 3<br />
  3. 3. Physical OS Virtualization<br />One machine running multiple OS instances<br />Windows 2003 running virtual Linux and Vista<br />Example: VMware, MS HyperV, Xen<br />
  4. 4. Application Server Virtualization <br />L4/L7ApplicationSwitch<br />Network<br />Multiple services appearing as one<br />Reverse proxy architectures<br />Web Farm<br />Clients<br />
  5. 5. Network Virtualization<br />One physical network, multiple virtual networks<br />One switch in the DC with overlapping IP blocks<br />VLANs<br />Multi-routing tables<br />VRTs<br />NAT<br />Trunking<br />
  6. 6. Storage Virtualization<br />Block: Disassociating storage drive from physical drive (iSCSI)<br />File: Virtual File Location<br />
  7. 7. Service Virtualization<br />L2/L3Switch<br />L4/L7ApplicationSwitch<br />Network<br />switch<br />switch<br />TMM 1<br />TMM 2<br />TMM 3<br />TMM 4<br />Virtual Kitchen Sink<br />Dynamic Provisioning & Flexible Infrastructures<br />Data Center Consolidation<br />
  8. 8. Application Delivery Architectures<br />The Complexity of Real World Application Delivery<br />
  9. 9. ?<br />Application<br />Problem: Infrastructures Aren’t Adaptable<br />- New security hole<br />- High cost to scale<br />- Slow performance<br />Network Administrator<br />Application Developer<br />Applications focus on business logic and functionality<br />Traditional networks are focused on connectivity<br />
  10. 10. Application<br />Multiple Point Solutions<br />More <br />Bandwidth<br />Network Administrator<br />Application Developer<br />Add more infrastructure?<br />Faster and centralised fix, applications are offloaded<br />Costly, complex and hard to manage<br />Hire an army of developers?<br />Expensive (code, manage, maintain)<br />Consumes server cycles<br />Often not possible<br />?<br />How Do You Fix the Problem?<br />
  11. 11. Advanced ADC Strategy<br />Secure, Fast, Available, Flexible<br />
  12. 12. Individual Silo Approach<br />Benefits<br />Regional Data Center<br />Individual LTM / Service<br /><ul><li>True “Airgap” Architecture
  13. 13. Direct BU Access
  14. 14. Controlled deployments</li></ul>6 -10 pairs of LTM’s <br />per regional datacenter<br />LDAP<br />Radius<br />VOIP, VM, IMS<br />Network DVR<br />DNS<br />Provisioning<br />TFTP, SNMP<br />Adv. ADC<br />Adv. ADC<br />Adv. ADC<br />Adv. ADC<br />Adv. ADC<br />Adv. ADC<br />Individual Service Pods<br />Individual LTM / Service<br /><ul><li>Application-specific hardware sizing
  15. 15. Each pod can be managed separately.</li></ul>Current Solution:<br />Different hardware models can be purchased for different applications specific to their traffic patterns.<br />Core Switching<br />
  16. 16. Shared Architrecture<br />Benefits<br />Individual LTM / Service<br /><ul><li>Lower TCO
  17. 17. Savings on maintenance</li></ul>1-2 Pairs of Scalable LTM’s<br />Per regional datacenter<br />Dallas Data Center<br />LDAP<br />Radius<br />VOIP, VM, IMS<br />Network DVR<br />DNS<br />Provisioning<br />TFTP, SNMP<br />Ease of Scalability<br />ADC<br />ADC<br />ADC scalable architecture<br /><ul><li>Network attack protection
  18. 18. Scale through application traffic spikes
  19. 19. Shared High Level Security architecture</li></ul>NO PROBLEM!<br />Add a blade to your current infrastructure with no additional management<br />Core Switching<br />
  20. 20. HybridArchitrecture<br />Benefits<br />Individual LTM / Service<br /><ul><li>Lower Capex
  21. 21. Uses Stock Hardware
  22. 22. Integrates with Dynamic provisioning strategy</li></ul>1-2 Pairs of Scalable LTM’s<br />Per regional datacenter<br />Plus<br />Virtual ADCs On Demand<br />Dallas Data Center<br />LDAP<br />Radius<br />VOIP, VM, IMS<br />Network DVR<br />DNS<br />Provisioning<br />TFTP, SNMP<br />vADC<br />vADC<br />vADC<br />vADC<br />vADC<br />vADC<br />Ease of Scalability<br />ADC scalable architecture<br /><ul><li>Network attack protection from Core ADC
  23. 23. Individual specific protection per application
  24. 24. Shared High Level Security architecture
  25. 25. On-Demand provisioning of ADC resources as required
  26. 26. Fully integrates with your Green Power strategy</li></ul>ADC<br />ADC<br />Core Switching<br />
  27. 27. The Cloud...... <br />That's Virtualisation right???<br />
  28. 28. Virtualization to Cloud Maturity Model<br />Separate<br />Consolidate<br />Aggregate<br />Automate<br />Liberate<br />Self-Managing Datacenters<br />Server Consolidation<br />Test and Development<br />CapacityOn Demand<br />Enterprise Computing Clouds On and Off Premise<br />Public<br />Private<br />Or<br />Here<br />Or<br />Here<br />Or<br />Here<br />You Are Here<br />Enterprise Objective: An IT Services On-Demand Platform<br />
  29. 29. Traditional Model is Inflexible<br />Users<br />Resources<br />Private<br />Public<br />Physical<br />Virtual<br />Cloud<br />Multi-Site DCs<br />
  30. 30. What’s Needed<br />Users<br />Dynamic Services Model:<br />Reusable services that understand context and can provide control regardless of application, virtualization, user, device, platform or location<br />Resources<br />Private<br />Public<br />Physical<br />Virtual<br />Cloud<br />Multi-Site DCs<br />
  31. 31. The Dynamic Control Plane Architecture<br />Users<br />Dynamic<br />Control<br />Availability<br /><ul><li>Scale
  32. 32. HA / DR
  33. 33. Bursting
  34. 34. Load-Balancing</li></ul>Optimization<br /><ul><li>Network
  35. 35. Application
  36. 36. Storage
  37. 37. Offload</li></ul>Security<br /><ul><li>Network
  38. 38. Application
  39. 39. Data
  40. 40. Access</li></ul>Management<br /><ul><li> Integration
  41. 41. Visibility
  42. 42. Orchestration</li></ul>Application and Data Delivery Network<br />Resources<br />Private<br />Public<br />Physical<br />Virtual<br />Multi-Site DCs<br />Cloud<br />
  43. 43. Q. Dynamic control plane benefits?<br />Cost savings from this strategy?<br /><ul><li> How does context awareness improve our </li></ul>Application Deliver or Securitystrategy?<br />
  44. 44. Virtualisation Summary<br />Support virtualized environments at whatever level suits you<br />From Server to Service<br />Integrate and accelerate VMware and Microsoft <br />Dynamic Provisioning for ADCS and Application Architectures<br />Secure virtual environments<br />At the network layer<br />DoS protection, Secure VLANs, Packet Filtering<br />At the application layer<br />Multi-protocol Application Firewall<br />

×