Reliability Support in Virtual Infrastructures 2 nd IEEE - - PowerPoint PPT Presentation
Reliability Support in Virtual Infrastructures 2 nd IEEE International Conference on Cloud Computing Technology and Science, Indianapolis, 2010 RESO Guilherme Koslovski (INRIA University of Lyon) Wai-Leong Yeow (DoCoMo USA Labs) Cedric
RESO
Guilherme Koslovski (INRIA – University of Lyon) Wai-Leong Yeow (DoCoMo USA Labs) Cedric Westphal (DoCoMo USA Labs) Tram Truong Huu (University of Nice – I3S) Johan Montagnat (CNRS – I3S) Pascale Vicat-Blanc Primet (INRIA - LYaTiss) 2nd IEEE International Conference on Cloud Computing Technology and Science, Indianapolis, 2010
2nd IEEE CloudCom – 2010
2
– Failure => credits – Lock-ins – No guarantees at all 99.95% availability 99.9% availability 99.95% reliability 100% uptime 100% network uptime
2nd IEEE CloudCom – 2010
3
Convergence of computing and communication: Virtual Infrastructure is a concept emerging from Virtual Networks and Infrastructures as a Service New models and tools to manage virtualized substrate & to help users in execution of their applications
Network virtualization Grid computing experience Resources virtualization Users Complex applications Distributed & virtualized substrate IaaS, PaaS, … XaaS concepts
2nd IEEE CloudCom – 2010
4
2nd IEEE CloudCom – 2010
5
Application
User
PM
VM 1
PM
VM 2
PM
VM n
PM
BKP 1
PM
BKP 2
PM
BKP n
Provide me a basic infrastructure Provide me a reliable infrastructure
2nd IEEE CloudCom – 2010
6
Application User
PM
VM 1
PM
VM 2
PM
VM n
PM
BKP 1
PM
BKP 2
PM
BKP n
Reliability becomes a service offered by the infrastructure provider
Transparent realibility provisioning Users (applications) have no knowledge about physical failures
2nd IEEE CloudCom – 2010
7
Reliable Virtual Infrastructure description Automatic generation of backup nodes and backup links Allocation algorithm
Evaluation through a use case application Conclusion & Future work
2nd IEEE CloudCom – 2010
8
I. Virtual Infrastructure description II. Translation of reliability requirements into real backup nodes III. Allocation of a reliable virtual infrastructure
2nd IEEE CloudCom – 2010
9
VXDL file Resources description Network topology description Timeline description General description VXDL: Virtual private eXecution infrastructure Description Language
– http://www.ens-lyon.fr/LIP/RESO/Software/vxdl/
vm1 database [1 GB, 2 GB] 2 GHz 2 cores Location: lyon.fr Reliability: 99.99% workers [100 nodes] 1 GB, 2 GHz 2 cores Location: lyon.fr Reliability: 99.9%
2nd IEEE CloudCom – 2010
10
Opportunistic Redundancy Pooling (ORP) mechanism [W. Yeow et al, 2010]: Input:
Reliability level (user requirement) Probability of physical failures (from MTBF) Number of protected virtual nodes (user requirement)
Output: the number of backup nodes – Backup nodes can be shared among different groups of critical nodes – For example, two sets of backup nodes (k1 and k2) can be shared to protect two groups of critical nodes.
Thanks to ORP is required only the min(k1, k2)
[W. Yeow et al, 2010]: Designing and embedding reliable virtual infrastructures, VISA workshop 2010.
2nd IEEE CloudCom – 2010
11
Step 1 Step 2 Step 3
2nd IEEE CloudCom – 2010
12
An extended graph is composed by original description + backup components Backup components can have specific constraints: – For example, original node and backup node should be allocated on different physical racks Subgraph-isomorphism detection [Lischka et al, 2009]
Physical substrate Embedded graph
2nd IEEE CloudCom – 2010
13
2nd IEEE CloudCom – 2010
14
Bronze Standard: distributed large-scale application
– Quantifies the maximal error resulting from medical-image analysis – Large databases: more the data, more the accuracy – 31 VMs: 512 MB,1 GHz – 10 Mbps for each virtual link between the database and the workers
Two scenarios of reliability requirements:
– Database protection: a failure stops the application execution – Workers protection: a failure increases the execution time
Testbed: Grid’5000
– Physical substrate is composed by 100 nodes: – MTBF simulation values: 60000s, 30000s, 15000s
[D. Atwood et al., 2008]
I) Translated into VXDL II) Submitted to HIPerNet
2nd IEEE CloudCom – 2010
15
Prices for computing nodes protection (30 VMs, 99.9%):
Short term Long term MTBF Backup Nodes Total cost Reliability cost / total cost Total cost Reliability cost / total cost 60000 s 5 $3.42 16.1% $3.10 5.3% 30000 s 8 $3.71 25.8% $3.19 8.4% 15000 s 12 $4.09 38.7% $3.32 12.6%
Goal: quantify the cost of a reliable virtual infrastructure
Prices are based on Amazon EC2 for Europe We do not include any specific link pricing cost without reliability support (short term lease): $2.95 / h VM specifications Basic node Short term lease $0.095 Long term lease $0.031
2nd IEEE CloudCom – 2010
16
Goal: evaluate the application behavior when executing with reliability support
Application makespan without substrate failures: 1205s, used as baseline – Database protection:
DB label: database is the unique component protected Makespan increases proportionally to the number of failures
– Worker nodes protection:
WN label: only computing nodes are protected Makespan slightly increases MTBF DB Increase WN Increase NI 60000s 16.26% 0.2% 30000s 26.47% 1.7% 15000s 40.08% 3.2%
200 400 600 800 1000 1200 1400 1600 1800 NI 60000s 30000s 15000s DB WN
2nd IEEE CloudCom – 2010
17
– Application is aware about substrate failures – A task is resubmitted on a new computing node – The makespan difference would have been more if backup nodes were not pre-allocated and configured
MTBF Makespan Increase 60000s +13.08% 30000s +19.67% 15000s +22.19%
200 400 600 800 1000 1200 1400 1600 60000s 30000s 15000s Reliability Resubmission
2nd IEEE CloudCom – 2010
18
Reliability becomes a service offered by the infrastructure provider We have developed a framework to provide transparent reliability:
– A language to specify the reliability requirements; – A mechanism to interpret these requirements and transform it in replicas (nodes and links) – A map and allocation process to provisioning the reliability level required by the user
The framework was implemented on top of the HIPerNet framework, and validated over the Grid’5000 testbed Future work includes:
– the implementation of a mechanism to protect virtual links – a detailed investigation on the economical aspects
– Tomorrow there is a demonstration about the industry version of the HIPerNet framework (LYaTiss core) - http://www.lyatiss.com/
2nd IEEE CloudCom – 2010
19
guilherme.koslovski@ens-lyon.fr, wlyeow@ieee.org, cwestphal@docomolabs-usa.com, tram@polytech.unice.fr, johan@i3s.unice.fr, pvb@lyatiss.com
2nd IEEE CloudCom – 2010
20
Specifying and provisioning Virtual Infrastructures with HIPerNET. Fabienne Anhalt, Guilherme Koslovski, and Pascale Vicat-Blanc Primet. ACM International Journal of Network Management (IJNM) - special issue on Network Virtualization and its Management, 2010; Joint elastic cloud and network framework for application performance optimization and cost reduction. Tram Truong Huu, Guilherme Koslovski, Fabienne Anhalt, Pascale Vicat-Blanc Primet, and Johan Montagnat. Journal of Grid Computing (JoGC) , 2010; Reliability support in virtual infrastructures. Guilherme Koslovski, Wai-Leong, Cedric Westphal, Tram Truong Huu, Pascale Vicat-Blanc Primet, and Johan Montagnat. In 2nd IEEE CloudCom 2010, Indianapolis, USA; A scalable security model for enabling Dynamic Virtual Private Execution Infrastructures on the Internet. Pascale Vicat-Blanc Primet, Jean-Patrick Gelas, Olivier Mornard, Guilherme Koslovski, Vincent Roca, Lionel Giraud, Johan Montagnat, and Tram Truong Huu. In IEEE/ACM CCGrid2009, Shanghai, May 2009; Exploring the virtual infrastructure service concept in Grid'5000. Pascale Vicat-Blanc Primet, Fabienne Anhalt, and Guilherme Koslovski. In 20th ITC Specialist Seminar on Network Virtualization, Hoi An, Vietnam, May 2009; Executing distributed applications on virtualized infrastructures specified with the VXDL language and managed by the HIPerNET framework. Guilherme Koslovski, Tram Truong Huu, Johan Montagnat, and Pascale Vicat-Blanc
Virtual Resources and Interconnection Networks Description Language. Guilherme Koslovski, Pascale Vicat-Blanc Primet, and Andrea Schwertner Charão. In GridNets 2008, Oct. 2008; HIPernet: A Decentralized Security Infrastructure for Large Scale Grid Environments. Julien Laganier, Pascale Vicat-Blanc Primet. In 6th IEEE/ACM International Conference on Grid Computing (GRID 2005), November 13-14, 2005, Seattle, Washington, USA, Proceedings, pages 140-147, 2005. IEEE;
2nd IEEE CloudCom – 2010
21
2nd IEEE CloudCom – 2010
22
VXDL file Resources description Network topology description Timeline description General description
– Location – Security – Monitoring
2nd IEEE CloudCom – 2010
23
VXDL file Resources description Network topology description Timeline description General description
Virtual routers/switches Virtual machines Virtual storages Virtual access points
– Exclusivity – Specific devices – Location
2nd IEEE CloudCom – 2010
24
VXDL file Resources description Network topology description Timeline description General description
– Bandwidth (forward and reverse) – Latency – Reliability – Security
2nd IEEE CloudCom – 2010
25
VXDL file Resources description Network topology description Timeline description General description
simultaneously or all along the VI lifetime
provisioning processes
by temporal marks
2nd IEEE CloudCom – 2010
26
Total cost is: original cost + reliability cost Original cost Reliability cost
2nd IEEE CloudCom – 2010
27
Bronze Standard workflow is analyzed and translated into a VXDL file:
– 31 VMs: 512 MB,1 GHz – 10 Mbps for each virtual link between the database and the workers
Two scenarios of reliability requirements:
– Database protection: a failure stops the application execution – Workers protection: a failure increases the execution time
Physical substrate: Grid’5000 testbed
I) Translated into VXDL II) Submitted to HIPerNet
2nd IEEE CloudCom – 2010
28
vm1 Node - vm2 [1 GB, 2 GB] 2 GHz 2 cores Location: lyon.fr Reliability: 99.9% vm3 vm4 Routers – r1, r2 Layer: Ethernet Dynamically configured Link - l1 [20 Mb/s, 200 Mb/s] with monitoring Links – l2, l3 [10 Mb/s, 100 Mb/s] Link – l4, l5 {10 Mb/s, 50 Mb/s, 100 Mb/s} Reliability: 99.99%
2nd IEEE CloudCom – 2010
29
Goals:
Evaluate the application behavior when executing with reliability support Quantify the cost of a reliable ViPXi
Application makespan without substrate failures: 1205s, used as baseline Simple cost model for the pricing:
– ViPXi cost + replicas cost – Prices are based on Amazon EC2 for Europe – 1 hour reservation – We do not include any specific link pricing
ViPXi cost without reliability support (short term lease): $2.95, used as baseline
Physical substrate is composed by 100 nodes:
MTBF simulation values: 60000s, 30000s, 15000s VM specifications Basic node (1.7GB RAM) Short term lease $0.095 Long term lease $0.031
2nd IEEE CloudCom – 2010
30
Prices for database protection (1 VM, 99.99%):
Short term Long term MTBF Fail prob. Backup Nodes Total cost Reliability cost / total cost Total cost Reliability cost / total cost 60000 s 0.03 2 $3.13 6% $3.01 2% 30000 s 0.06 3 $3.23 10% $3.04 3% 15000 s 0.12 4 $3.33 13% $3.07 4%
Prices for computing nodes protection (30 VMs, 99.9%):
Short term Long term MTBF Fail prob. Backup Nodes Total cost Reliability cost / total cost Total cost Reliability cost / total cost 60000 s 0.03 5 $3.42 16.1% $3.10 5.3% 30000 s 0.06 8 $3.71 25.8% $3.19 8.4% 15000 s 0.12 12 $4.09 38.7% $3.32 12.6%
Goal: Quantify the cost of a reliable ViPXi
Prices are based on Amazon EC2 for Europe We do not include any specific link pricing cost without reliability support (short term lease): $2.95 VM specifications Basic node Short term lease $0.095 Long term lease $0.031