Cloud Computing Patterns, Mechanisms > Virtual Server and Hypervisor Connectivity and Management Patterns > Virtual Server Connectivity Isolation
Virtual Server Connectivity Isolation (Erl, Naserpour)
How can a given virtual server be isolated and prevented from communicating with the external network while remaining in contact with other virtual servers and resources?
Problem
A virtual server’s communication needs to be limited to only the virtual server and other resources it needs to remain in contact with, and isolated from all other parts of the external network.
Solution
The virtual server is not allowed to connect to any part of the solution that has a communication path to the external network or internal network, outside of what is required.v
Application
The virtual server is isolated via the use of an additional virtual switch, thereby isolating it from the traffic of other virtual servers.
Mechanisms
Hypervisor, Physical Uplink, Virtual Firewall, Virtual Infrastructure Manager, 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)
Virtual Server B is given its own virtual switch, so that it can be completely isolated from all other virtual servers besides Virtual Server A.
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.