Cloud Computing Patterns, Mechanisms > Virtual Server and Hypervisor Connectivity and Management Patterns > Virtual Switch Isolation
Virtual Switch Isolation (Erl, Naserpour)
How can network contention and bandwidth competition between virtual servers be decreased?
Problem
Network contention and bandwidth competition between virtual servers on the same virtual switch needs to be alleviated.
Solution
The virtual server traffic needs to be isolated.
Application
Virtual switches can be used as isolation mechanisms to reduce network contention and bandwidth competition.
Mechanisms
Hypervisor, Physical Uplink, Virtual Infrastructure Manager, Virtual Network, Virtual Switch
Compound Patterns
Burst In, Burst Out to Private Cloud, Burst Out to Public Cloud, Cloud Authentication, Cloud Balancing, Elastic Environment, Infrastructure-as-a-Service (IaaS), Isolated Trust Boundary, Multitenant Environment, Platform-as-a-Service (PaaS), Private Cloud, Public Cloud, Resilient Environment, Resource Workload Management, Secure Burst Out to Private Cloud/Public Cloud, Software-as-a-Service (SaaS)
Each virtual server is provided with access to a physical uplink and virtual switch that cannot be accessed by the other virtual server.
Virtual Switches A and B are each provided with an individual physical uplink.
The two physical uplinks are connected to Physical Switch A.
Virtual Servers A and B are connected to Virtual Switches A and B.
The virtual servers are still connected to the virtual switches and cloud service consumers even if a physical switch or NIC experiences failure.
This pattern is covered in CCP Module 17: Advanced Cloud Virtualization.
For more information regarding the Cloud Certified Professional (CCP) curriculum, visit www.arcitura.com/ccp.