Load Balanced Virtual Server Instances (Erl, Naserpour)
How can a workload be balanced across virtual servers and their physical hosts?
ProblemIf a runtime workload is improperly distributed across both virtual servers and their physical hosts, then some virtual servers become over-utilized, while others are under-utilized or running idle.
SolutionThe workload is recalculated at runtime and virtual servers are correspondingly moved between hosting physical servers to ensure even distribution across virtual and physical layers.
ApplicationA capacity watchdog surveys physical and virtual servers and reports variance to the VIM, which interacts with a load balancer and live VM migration to dynamically adjust virtual server locations.
MechanismsAutomated Scaling Listener, Cloud Storage Device, Cloud Usage Monitor, Hypervisor, Live VM Migration, Load Balancer, Logical Network Perimeter, Resource Cluster, Resource Replication, Virtual Infrastructure Manager, Virtual RAM, Virtual Server, Virtual Switch, Virtualization Monitor
Compound PatternsBurst 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)
The virtual server instances are evenly distributed across the physical server hosts.
A cloud architecture scenario resulting from the application of the Load Balanced Virtual Server Instances pattern (Part I).
A cloud architecture scenario resulting from the application of the Load Balanced Virtual Server Instances pattern (Part II).
A cloud architecture scenario resulting from the application of the Load Balanced Virtual Server Instances pattern (Part III).
NIST Reference Architecture Mapping
This pattern relates to the highlighted parts of the NIST reference architecture, as follows: