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.\nThe 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.\n+MORE AT NETWORK WORLD: What SDN is and where its going +\nVMware has two separate versions of its software-defined networking (SDN) software. The more popular and widely-used version named NSX integrates with VMware\u2019s vSphere virtualization management software and the company\u2019s popular ESXi compute hypervisor.\nIn 2016 VMware announced another version named NSX-T, which supports hypervisors other than ESXi, including the Kernel Virtual Machine (KVM). It\u2019s meant to run in public and private cloud environments and in recent months VMware has extended NSX-T to support application container networking too.\nThis week, at Pivotal\u2019s SpringOne Platform conference in San Francisco, VMware is announcing NSX-T 2.1, which supports Pivotal\u2019s Cloud Foundry platform as a service \u2013 a container-based application-development platform.\nCloud 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 \u2013 which developers use to package applications into modular components \u2013 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.\n\u201cIt\u2019s not just about the network architecture and topology supporting container runtimes. Operationally there\u2019s an even greater impetus for more extensive automation,\u201d Casemore says. \u201cIf you\u2019ve got an environment that\u2019s that vibrant, that subject to change, with processes starting up and ending, processed in a distributed microservices environment, you can\u2019t be doing things manually.\u201d\nCisco, Juniper also manage container networking \nThere is a broad market of container management platforms, Casemore says. Cisco, for example, recently rolled out support for containers and container managers, including Kubernetes, Docker Data Center and Mesos in the 3.0 release of its Application Centric Infrastructure (ACI) SDN. Juniper supports containers with its Contrail SDN, Nuage supports them with its VSP, and there are a variety of startups such as Tigera and Weaveworks that also aim to solve container networking issues.\nVMware group product marketing manager Matt De Vincentis says many container runtime platforms such as Docker, Pivotal\u2019s CF, Red Hat\u2019s OpenShift and even the open source Kubernetes software include basic inter-container network functionality. He says using a platform like NSX-T makes it easier to manage containers at scale and integrate them with other network services such as firewalls and load balancers.\nMeanwhile, container adoption is nascent, but growing quickly. According to a 2016 Voice of the Enterprise survey by 451 Research, only 25% of respondents were using containers and of those only 34% described their usage of the technology as broad. As organizations more fully embrace application containers and start running them in production, Casemore believes organizations will begin realizing pain points of managing their network requirements.