Hyperconverge Your Way to 2-SKU Data Center

Transcription

1 Hyperconverge Your Way to 2-SKU Data Center Ivan Pepelnjak Network Architect ipspace.net AG

2 Who is Ivan Pepelnjak Past Kernel programmer, network OS and web developer Sysadmin, database admin, network engineer, CCIE Trainer, course developer, curriculum architect Team lead, CTO, business owner Present Network architect, consultant, blogger, webinar and book author Teaching the art of Scalable Web Application Design Focus Large-scale data centers, clouds and network virtualization Scalable application design Core IP routing/mpls, IPv6, VPN ipspace.net/about 2 ipspace.net 2017 Hyperconverge Your Way to 2-SKU Data Center

3 Data Center Network (cca 2010) Core WAN A B Layer 3 Aggregation + Services Layer 2 Layer 3 Layer 2 Access (TOR/EOR) Layer 2 Layer 2 3 ipspace.net 2017 Hyperconverge Your Way to 2-SKU Data Center

4 It Doesn t Get Any Better Core Aggregation + Services WAN Typical new build: 10+ vendors A B Layer 3 Layer 3 24 hardware/software platforms Source: Thomas Wacker, UBS Layer 2 Layer 2 Access (TOR/EOR) Layer 2 Layer 2 Can we build a data center with just two hardware platforms? 4 ipspace.net 2017 Hyperconverge Your Way to 2-SKU Data Center

5 Virtualize the Servers

6 Rightsizing the Servers Modern servers support large number of CPU cores Find a server model with optimum price-per-core Compute virtualization ratio (number of VMs per server) 50+ VMs per server is reasonable Use RAM-per-core ratio (based on VM utilization data) to compute server RAM requirements Maximum RAM or # of cores might be the limiting factor è repeat as required Virtualization makes sense even for single-vm servers 6 ipspace.net 2017 Hyperconverge Your Way to 2-SKU Data Center

7 Some Real-Life Data: Sockets, Cores, VM Density Data collected by PernixData Cloud: 84% of servers have two sockets Most servers have between 8 and 24 cores 16 cores) Most ESXi hosts have between 192 and 512 GB of memory 256 GB, 384 GB) VM density data is all across the board: From 10 VM per host to 250 VM per host 70% of ESXi hosts have more than 20 VMs 34% of ESXi hosts have more than 50 VMs ipspace.net 2017 Hyperconverge Your Way to 2-SKU Data Center

8 Ditch Legacy Technologies

9 1GE or 10GE uplinks? What I Recommended in 2012 Gigabit Ethernet + Well known, field tested + Copper cabling + NIC on motherboard Numerous NICs per hypervisor host (user data, vmotion, storage) No storage/networking convergence No lossless transport 10 Gigabit Ethernet + Much faster vmotion + Converged storage+network (FCoE or lossless iscsi/nfs) + Reduce the number of NICs per server + Built-in QoS with ETS and PFC + Uses fiber cabling (lower energy consumption and error rate) More expensive Usually requires fiber cabling NICs/CNAs still price premium 9 ipspace.net 2017 Hyperconverge Your Way to 2-SKU Data Center

10 1GE or 10GE uplinks? What I Recommended in GE uplinks (don t even think about 1GE anymore) 10GBASE-T in small deployments ToR switches (don t forget inter-switch links) Servers with 10GBASE-T LOM or Intel X540-T2 adapter SFP+/QSFP deployments Twinax SFP+ for short distances (when you need SFP+ connectivity) Fiber SFP+ for longer (inter-rack or inter-row) distances Images: Out-of-band Arista 7050T-64, management Cisco 5548P, Cisco / KVM Twinax / ILO SFP+ network is an exception 10 ipspace.net 2017 Hyperconverge Your Way to 2-SKU Data Center

11 Minimize Uplinks

12 Read the Latest vsphere Design Guide Kernel VM Network PG PG PG VMkernel Uplink port group iscsi Queue ESX host Physical network vsphere 4 vsphere 5+ (since 2011) 12 ipspace.net 2017 Hyperconverge Your Way to 2-SKU Data Center

13 Use IP-based Storage

14 Replace FC/FCoE with iscsi or NFS FC IP Core 14 ipspace.net 2017 Hyperconverge Your Way to 2-SKU Data Center

15 Distributed File Systems

16 Distributed File Systems with DAS Hypervisor Host Hypervisor Host Virtual NIC Virtual SCSI Virtual NIC Virtual SCSI SCSI emulator?? File system Hypervisor Distributed file system SCSI emulator?? File system Hypervisor IP transport (underlay) network Each hypervisor uses local disks (DAS) and/or SSDs Global file system or object store with file replication between hypervisors nodes Examples: Ceph, GlusterFS, VMware VSAN, OpenStack Swift 16 ipspace.net 2017 Hyperconverge Your Way to 2-SKU Data Center

17 Virtualize Network Services

18 Virtual Appliances = Network Services in VM Format Advantages Avoid hardware-dependent delays Increase flexibility and mobility Simplify disaster recovery Minimal time-to-deploy Minimize sparing Outside Inside Hypervisor host Sample products Network Routers: Brocade Vyatta, Cisco CSR, Juniper vmx Firewall: pfsense, Juniper vsrx, Palo Alto, Vyatta, vshield Edge (VMware), vasa (Cisco) Load balancer: BIG-IP VTM (F5), Zeus Traffic Manager (now Riverbed), vshield Edge (VMware), Embrane, LineRate Systems (now F5), Citrix NetScaler VM 18 ipspace.net 2017 Hyperconverge Your Way to 2-SKU Data Center

19 Virtualize the Appliances 19 ipspace.net 2017 Hyperconverge Your Way to 2-SKU Data Center

20 Final Result

21 Going All Virtual WAN All servers are virtualized è small number of hypervisor hosts Distributed file system è no extra storage components Virtualized appliances è only two hardware components 21 ipspace.net 2017 Hyperconverge Your Way to 2-SKU Data Center

22 Will It Work? WAN 1500 VMs in 28 RU (56 blade hosts) Cisco Nexus has 96 10GE ports. Arista, Cumulus and Juniper have similar products Conclusion: Two switches is all you need to build most data centers 22 ipspace.net 2017 Hyperconverge Your Way to 2-SKU Data Center

23 Stay in Touch Web: ipspace.net Blog: blog.ipspace.net SDN: ipspace.net/sdn Webinars: ipspace.net/webinars Consulting: ipspace.net/consulting 23 ipspace.net 2017 Hyperconverge Your Way to 2-SKU Data Center

24 Questions? Send them to 24 ipspace.net 2017 Hyperconverge Your Way to 2-SKU Data Center