Where We're Headed and Where NSX Fits In

This presentation covers some broad industry trends and how those trends are driving the need for a network virtualization solution like VMware NSX.

Transcript

1. Where We’re Headed and Where NSX Fits In Scott Lowe, VCDX 39 vExpert, Author, Blogger, Geek http://blog.scottlowe.org / Twitter: @scott_lowe Colossians 3:17 A look at broad industry trends and how it affects networking
2. Before we begin • Please get involved! Feel free to ask questions, share your experience, or contribute your viewpoint. • Feel free to take pictures, record videos, or post social media updates (use #ScottishVMUG or @ScottishVMUG) • Out of courtesy to others, please silence your electronics • This presentation will be available after the event
3. https://flic.kr/p/z1zk53
4. It really all boils down to this • It’s about helping your organization get through this cycle faster • Credit goes to Joe Baguley for this diagram
5. So what are some trends that have evolved as a result?
6. https://flic.kr/p/cnorAf
7. Why DevOps? • DevOps rose out of a need to eliminate delays and problems in deploying software • DevOps != Automation • It’s primarily about culture and process (automating a broken process just gives you an automated broken process) • Automation is an important part of DevOps methodologies
8. https://flic.kr/p/abA2T4
9. https://flic.kr/p/7hkbXz
10. https://flic.kr/p/6UDnWP
11. Why cloud computing? • Faster “mean time until I can start getting work done” • Self-service infrastructure without a ticket • No more waiting on servers or VMs or networking or security • “Unlimited capacity” (from the perspective of the consumer) • Automation is pretty much a necessity (especially from the operator’s perspective)
12. https://flic.kr/p/3h5aAH
13. https://www.docker.com/
14. Why Docker? • Makes it super-easy to deploy applications just about anywhere • Docker advocates a “single process per container model” • That naturally leads toward a microservices-based architecture • An application is decomposed into smaller, more focused services • 1 application = many services, 1 service = multiple containers • Manual operations in a microservices-based architecture simply don’t cut it
15. https://github.com/kubernetes/kubernetes/blob/master/logo/logo.png
16. Why Kubernetes? • Kubernetes is aimed at orchestrating containers to build applications using a microservices-based architecture • A Pod is a group of containers • Pods are presented to the outside world as Services • Services make up applications (microservices-based architecture) • Heavily leverages load balancing as a key element (the “Service” is a load- balanced VIP that services a group of pods) • Manually configuring networking isn’t going to work for Kubernetes
17. The “TL;DR” is this • Microservices-based architectures mean more endpoints (sometimes dramatically more) • Container orchestration tools mean endpoints being created and/or destroyed in automated fashion • Cloud computing models means logical network constructs being created and destroyed on the fly • Security is needed in all these cases • This simply can’t be done without some form of network automation
18. So where does NSX fit into all this?
19. VMware NSX enables network automation • Supports the use cases we’ve described here • Private cloud use cases (via vRA or OpenStack) • Public cloud use cases (demonstrated at VMworld 2015) • Microservices-based architectures with Docker (demonstrated at VMworld 2015) • Provides the distributed network services needed (switching, routing, firewalling, load balancing) • Hardware-agnostic (only requires IP connectivity)
20. Want to learn more? • Numerous sessions today in the NSX Track: • 13:15 - Untrust to Zero Trust • 14:15 - Microsegmentation for the SDDC • 15:45 - NSX to Secure EUC Solutions • Hands-On Labs • VMworld 2015 sessions (VMUG Advantage subscribers have access to this content as part of your subscription)
21. Q&A
22. Thank you! Scott Lowe, VCDX 39 vExpert, Author, Blogger, Geek http://blog.scottlowe.org / Twitter: @scott_lowe Colossians 3:17 Please be sure to provide feedback to the VMUG leaders on this session.