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 Usage Monitor, Hypervisor, Load Balancer, Logical Network Perimeter, Resource Cluster, Resource Replication, Virtual Server
Compound PatternsBurst In, Burst Out to Private Cloud, Burst Out to Public Cloud, Cloud Authentication and Access Management, Cloud Balancing, Elastic Environment, Infrastructure-as-a-Service (IaaS), Multitenant Environment, Platform-as-a-Service (PaaS), Private Cloud, Public Cloud, Resilient Environment, Secure Burst Out to Private Cloud/Public Cloud, Software-as-a-Service (SaaS)
A sample architecture resulting from the application of the Load Balanced Virtual Server Instances pattern (Part 1)
NIST Reference Architecture Mapping
This pattern relates to the highlighted parts of the NIST reference architecture, as follows: