VMware NSX: Defining the Problem
Every good data center presentation starts with redefining The Problem and my VMware NSX Architecture webinar was no exception – the first section describes Infrastructure-as-a-Service Networking Requirements.
I sprinted through this section during the live session, the video with longer (and more detailed) explanation comes from the Overlay Virtual Networking webinar.
Recent posts in the same categories
data center
- Response: The Usability of VXLAN
- Migrating a Data Center Fabric to VXLAN
- The Mythical Use Cases: Traffic Engineering for Data Center Backups
- Video: What Is Software-Defined Data Center
- Repost: L2 Is Bad
- Path Failure Detection on Multi-Homed Servers
workshop
- Prepare for Job Interview with ipSpace.net Subscription
- How Do I Persuade My Management Automation Makes Sense?
- Automation Gone Wild
- Why Would I Attend the Virtual Firewalls Workshop?
- Sample Ansible Networking Playbooks on Github
- Help Me Plan ipSpace.net Webinars
I will say I am more of a fan of Juniper's Contrail and ALU's Nuage offerings than NSX for a pure OpenStack deployment, but obviously those don't exist for VMWare as of yet. Contrail especially since it just uses standard L3VPNs and MPLSoGRE, I already have it working with a pair of MX960s and ASR9Ks, even a SRX650 firewall in the same overlay network. The use of XMPP to distribute member router, etc. to vrouters is highly scalable as well.
As physical compute and storage have been commoditized, datacenter networking will be soon.