Cloud Computing Patterns | Design Patterns | Virtual Server-to-Host Anti-Affinity


Cloud Computing Patterns, Mechanisms > Virtual Server and Hypervisor Connectivity and Management Patterns > Virtual Server-to-Host Anti-Affinity
Home > Design Patterns > Virtual Server-to-Host Anti-Affinity

Virtual Server-to-Host Anti-Affinity (Erl, Naserpour)

How can a virtual server be guaranteed to not be hosted on a particular host or group of hosts?

Virtual Server-to-Host Anti-Affinity

Problem

A virtual server cannot be hosted on a specific host or group of hosts.

Solution

Anti-affinity rules are used to ensure that the virtual server or bundled workload will not be hosted on the target host or hosts.

Application

Virtual server-to-host anti-affinity rules are applied and configured, and controlled and dedicated by the VIM server to prevent the virtual server or workload from being hosted on the target host or group of hosts.

Virtual Server-to-Host Anti-Affinity: The Virtual Server-to-Host Anti-Affinity pattern is applied by configuring rules that create an anti-affinity relation between Virtual Server A and Hypervisor C. This configuration is performed via the VIM server and is replicated across the cluster.

The Virtual Server-to-Host Anti-Affinity pattern is applied by configuring rules that create an anti-affinity relation between Virtual Server A and Hypervisor C. This configuration is performed via the VIM server and is replicated across the cluster.

Virtual Server-to-Host Anti-Affinity: An anti-affinity rule is created and applied to the virtual server and hypervisor (Part I).

An anti-affinity rule is created and applied to the virtual server and hypervisor (Part I).

Virtual Server-to-Host Anti-Affinity: The steps involved in applying this pattern are shown (Part II).

The steps involved in applying this pattern are shown (Part II).

Virtual Server-to-Host Anti-Affinity: Virtual Server B is now powered on at Hypervisor C, while Virtual Server A has been powered on at Hypervisor B (Part III).

Virtual Server B is now powered on at Hypervisor C, while Virtual Server A has been powered on at Hypervisor B (Part III).


CCP Module 17: Advanced Cloud Virtualization

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.