Posted by on
Categories: Containers NSX SDN VMware

#VMware today released a new version of its #NSX virtual networking software that aims to make it easier to manage network requirements of cloud-native and application-container-based applications. The move represents the latest example of a network vendor evolving its automation tooling to operate in not just traditional data center and campus networks, but increasingly in cloud environments that cater to a faster-pace of application development. What #SDN is and where its going  @VMware has two separate versions of its software-defined networking (SDN) software. The more popular and widely-used version named NSX integrates with VMware’s #vSphere virtualization management software and the company’s popular ESXi compute hypervisor. SponsoredPost Sponsored by Intel Future-Ready Analytics In 2016 VMware announced another version named NSX-T, which supports hypervisors other than ESXi, including the Kernel Virtual Machine (KVM). It’s meant to run in public and private cloud environments and in recent months VMware has extended NSX-T to support application container networking too. This week, at Pivotal’s SpringOne Platform conference in San Francisco, VMware is announcing NSX-T 2.1, which supports Pivotal’s Cloud Foundry platform as a service – a container-based application-development platform. Cloud environments, and particularly those that that use application containers, present unique challenges from a networking perspective says IDC data center networking research director Brad Casemore. Application containers – which developers use to package applications into modular components – have very short life spans compared to virtual machines. They sometimes run for mere seconds at a time, compared to virtual machines that can be live indefinitely. There are typically a large number of containers that make up a microservices-based application; dozens of containers can run in a single virtual machine, for example. “It’s not just about the network architecture and topology supporting container runtimes. Operationally there’s an even greater impetus for more extensive automation,” Casemore says. “If you’ve got an environment that’s that vibrant, that subject to change, with processes starting up and ending, processed in a distributed microservices environment, you can’t be doing things manually.”

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.