2010 IEEE Network Operations and Management Symposium - NOMS 2010 2010
DOI: 10.1109/noms.2010.5488431
|View full text |Cite
|
Sign up to set email alerts
|

Redundant virtual machine placement for fault-tolerant consolidated server clusters

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
5

Citation Types

0
52
0

Year Published

2011
2011
2023
2023

Publication Types

Select...
3
3
1

Relationship

0
7

Authors

Journals

citations
Cited by 109 publications
(52 citation statements)
references
References 14 publications
0
52
0
Order By: Relevance
“…Some of this work does not minimize energy [15,30,33] or it applies to a model different than ours (VM migration [35,36], knowledge of future load [31,36], feasibility of allocation [13], multilevel architecture [32,35,27], interconnected VMs [14], etc.). On the other hand, some of the experimental work where minimization of energy is evaluated focus on a more restrictive cost function [39,27,40].…”
Section: Related Workmentioning
confidence: 99%
“…Some of this work does not minimize energy [15,30,33] or it applies to a model different than ours (VM migration [35,36], knowledge of future load [31,36], feasibility of allocation [13], multilevel architecture [32,35,27], interconnected VMs [14], etc.). On the other hand, some of the experimental work where minimization of energy is evaluated focus on a more restrictive cost function [39,27,40].…”
Section: Related Workmentioning
confidence: 99%
“…In on-demand clouds, there are potentially two types of VM-placement decisions to be made: (1) initial placement [13][14][15][16][17][18][19][20][21][22][23] and (2) migration (and/or resizing) of VMs over time [24][25][26][27][28][29][30], as PM availability changes, as consolidation is needed to conserve power and in response to the degree to which service-level agreements (SLAs) are being achieved. Most previous research on initial VM placement considered only PMs within a single cloud, but in one case [22] placement decisions considered which of several clouds to choose.…”
Section: Related Workmentioning
confidence: 99%
“…When VMs communicate, placing them on the same cluster makes good sense because communication among the VMs will be local to a cluster switch. Most existing research [13][14][15][16][17][18][19][20][21][22][23] considers PMs as an unstructured pool, where restricting VMs to a shared cluster would be accomplished by designating a Boolean attribute, one of potentially many attributes over which some optimization algorithm or binpacking heuristic would be executed. In our study, guided by the open-source code in Eucalyptus (v1.6) [6], we adopt explicit use of two distinct decisions levels: (1) choosing a cluster for all VMs in a given request and then (2) choosing specific PMs within the selected cluster.…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations