service level agreements for cloud computing - home - …978-1-4614-161… ·  ·...

26
Service Level Agreements for Cloud Computing

Upload: vantuyen

Post on 30-May-2018

217 views

Category:

Documents


0 download

TRANSCRIPT

Service Level Agreements for Cloud Computing

Foreword by

Phili Wieder • Joe M. Butlerpp

EditorsWolfgang Theilmann • Ramin Yahyapour

Service Level Agreementsfor Cloud Computing

Jessica McCarthy

ISBN 978-1-4614-1 - e-ISBN 978-1-4614-1 -DOI 10.1007/978-1-4614-1 -Springer New York Dordrecht Heidelberg London

Library of Congress Control Number: 2011939783

© Springer Science+Business Media, LLC 2011All rights reserved. This work may not be translated or copied in whole or in part without the written permission of the publisher (Springer Science+Business Media, LLC, 233 Spring Street, New York, NY 10013, USA), except for brief excerpts in connection with reviews or scholarly analysis. Use in connection with any form of information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed is forbidden.The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights.

Printed on acid-free paper

Springer is part of Springer Science+Business Media (www.springer.com)

PEditors

hilipp WiederIT & Media CenterService Computing GroupTU Dortmund University

p @

DortmundGermany

hilipp.weider udo.edu

613 5 614 2614 2

Joe M. ButlerIntel Ireland LimitedLeixlip, KildareIreland

Wolfgang TheilmannSAP ResearchKarlsruheGermany

Ramin YahyapourIT & Media CenterService Computing GroupTU Dortmund UniversityDortmundGermany

The SLA@SOI project is dedicated to providea business-ready service-orientedinfrastructure empowering the serviceeconomy in a flexible and dependable way.

Foreword

SLA@SOI is one of the most significant projects funded under the EuropeanUnion’s Seventh Framework Programme. With a budget of over 15 million Eu-ros and a consortium of twelve partners, SLA@SOI is a comprehensive integratedproject of broad scope, touching market segments in areas including managementof service level agreements (SLAs), service-oriented infrastructures (SOIs), cloudcomputing, enterprise service buses and XaaS provisioning (including Platform as aService, Software as a Service, Infrastructure as a Service, etc). Relevant initiativesinclude global-scale commercial offerings, well-supported open source projects, andlarge, strategic publicly-funded research initiatives.

SLA@SOI operates within highly dynamic and fast-moving domains, and manyworld-class players are very active in areas in which SLA@SOI can make most im-pact, namely cloud computing and service-oriented architectures. We in SLA@SOIbelieve that SLAs are a key technology for transforming service and cloud offeringsinto tradeable goods. The project has invested three years of in-depth research andanalysis into the SLA domain, developing a comprehensive architecture and refer-ence implementation for SLA management, then evaluating and incorporating theseresults in four distinct and complementary industrial use cases.

Specifically, the SLA@SOI project aims to enable automatic negotiation of per-sonalised SLAs across multiple providers, such that individual SLAs for thousandsof customers can be automatically managed and optimised. Most industrial serviceproviders have not yet come to terms with this notion of providing automated SLAswith their service offerings, which is very promising from SLA@SOI’s perspective.Currently, market leaders still rely on highly manual processes for making claimson SLA violations.

Machine-readable SLAs, on the other hand, will allow consumers and providersof online services to precisely specify the services and service levels they require,confirm that SLAs are being met, and automatically deal with any SLA violations.SLA@SOI provides a framework under which automatic SLA negotiation and SLA-aware optimisation become feasible. Machine-readable SLAs allow service levels tobe personalised, automatically negotiated, aggregated, and continuously assured.

vii

viii Foreword

The book presents a unique insight into the SLA@SOI project, with a focus onreference architectures, open reference case examples, SLA models, service con-struction meta-models, and approaches to infrastructure monitoring and runtimeprediction. The book also recounts the results of four SLA@SOI use cases—in e-government, Telco service aggregation, ERP hosting, and enterprise IT—analysingoutcomes from a business and technical research perspective.

As exploitation manager for SLA@SOI, I have observed firsthand the interestthis research project has generated from both industry and academia. The projectis differentiated from other commercial and research offerings in that it has anSLA-driven approach that considers a range of stakeholders (e.g. service providers,software providers, infrastructure providers and service customers) while explicitlytackling challenges at the business, software and infrastructure levels. SLA@SOIaims to provide an automated and holistic awareness of personalised SLAs along-side a business-ready SOI that empowers the service economy and Future Internetin a flexible and dependable way.

By defining a cohesive research agenda for Europe going forward, the FutureInternet initiative will provide important medium- and long-term opportunities forexploitation of SLA@SOI.

Dublin, June 2011 Jessica McCarthy

Preface

IT-supported service provisioning is of major relevance for almost all industries andIT domains. And with the evolution of ecosystems where everything can becomea service and the actual IT provisioning is virtualized, the importance of service-related infrastructures will further increase. The so-called clouds already have thebuy in from industry, resulting in terms like everything-as-a-service, scale out, multitenancy, and pay-as-you-go become increasingly popular to describe this new ap-proach, showing on the one hand the business model behind the cloud offerings andon the other hand underlining its commercial character. From a research perspec-tive, this somehow young discipline offers a large variety of topics and novel topicswill certainly emerge.

The research project SLA@SOI (funded under the Seventh Framework Pro-gramme with grant number FP7- 216556) provides a major milestone for the furtherevolution towards a service-oriented economy, where IT-based services can be flex-ibly traded as economic good, i.e. under well-defined and dependable conditionsand with clearly associated costs. Eventually, this will allow for dynamic value net-works that can be flexibly instantiated thus driving innovation and competitiveness.SLA@SOI created a holistic view for the management of service level agreements(SLAs) and provides an SLA management framework that can be easily integratedinto a service-oriented infrastructure.

Europe has set high goals in becoming the most active and productive serviceeconomy in the world. Especially IT supported services evolved into a commonutility which is offered and consumed by many stakeholders. Cloud computinggained significant attention and commercial uptake in many business scenarios. Thisrapidly growing service oriented economy has highlighted key challenges and op-portunities in IT-supported service provisioning. With more companies incorporat-ing cloud-based IT services as part of their own value chain, reliability and de-pendability become a crucial factor in managing business. Service level agreementsare the common means to provide the necessary transparency between service con-sumers and providers.

SLA@SOI as a major European project addresses the issues surrounding the im-plementation of automated SLA management solutions for service oriented infras-

ix

x Preface

tructures and evaluates their effectiveness. As of today, SLAs are in general eithernot yet formally defined, or they are defined by a single party, mostly the provider,without further interaction with the consumer. Or SLAs are negotiated in a lengthyprocess with bilateral human interaction. For a vivid IT service economy, bettertools are necessary to support end-to-end SLA management on a holistic scale.

SLAs are particularly relevant to cloud computing, an increasingly importantand relevant deployment model for infrastructure, services, or platforms. SLA@SOIallows such services to be described by service providers through formal templateSLAs. Once these template SLAs are machine readable, service composition can beestablished using automatic negotiation of SLAs. Moreover, the management of theservice landscape can focus on the existence and state of all necessary SLAs.

A major innovation of SLA@SOI is the multi-layered aspect of the service stack.Typically, a service is dependent on many other services. For example, the offeringof a software service requires infrastructure resources, software licenses or othersoftware services. The SLA framework developed by SLA@SOI supports the con-figuration of complex service hierarchies with arbitrary layers. This allows end-to-end management of resources and services for the business value chain.

This book covers a large number of topics related to Clouds and service orientedinfrastructures that are relevant for researchers and practitioners. It is divided intoeight parts, as there are ‘Introduction to Service Level Agreements in Service Ori-ented Infrastructures’, ‘Foundations for Service Level Agreements’, ‘Scientific In-novations’, ‘Core Components of the Service Level Agreements Framework’, ‘Man-agement of the Business Layer’, ‘Management of the Software Layer’, ‘Manage-ment of the Infrastructure Layer’, and ‘Selected Business Use Cases’. Comprising21 chapters in total, this book addresses fundamental topics related to service provi-sioning and SLAs, it tackles scientific challenges including the modelling of the re-lationships between SLA properties, and it introduces a generic management frame-work, as well as its layers and components, that can be applied to a large variety ofuse cases. Last but not least, the book highlights four such use cases to demonstratethe applicability of the framework and to give users and IT providers hints on howto integrate and provide services governed by guarantees on service-quality.

We hope that readers benefit from the results of three years of research and de-velopment conducted by SLA@SOI and, at the same time, enjoy the book.

Dortmund, Karlsruhe, Leixlip Philipp WiederJuly 2011 Joe M. Butler

Wolfgang TheilmannRamin Yahyapour

Acknowledgements

The outstanding research and development results produced by the SLA@SOIproject, and hence also the book at hand, would not have been possible without thededication of numerous people. Although it is not possible to mention everybody in-volved in the project, especially since SLA@SOI collaborated with a large numberof other projects, standardisation bodies, and industrial fora, the editors would liketo express special gratitude to the following people. First and foremost the editorswould like to thank all the project partners for three years of great work. Althoughthis book cannot cover all outcomes of the project, it provides a brought yet detailedoverview of the various scientific and technical achievements, which comprise con-tributions from everyone active in the project. The editors gratefully acknowledgethe guidance from the European Commission and the project reviewers. Their eval-uation of the progress of the project and the assessment of direction and resultshelped to make SLA@SOI a success. The quality of the book has been confirmedand strengthened with the help of experts who carefully examined the various bookchapters and who provided feedback on scientific and technical content. The editorswould like to acknowledge the contribution of the following scientists:

• Simon Caton, Karlsruhe Institute of Technology• Bjorn Hagemeier, Forschungszentrum Julich• Peter Hasselmeyer, NEC Laboratories Europe• Sebastian Hudert, University of Bayreuth• Bastian Koller, Universitat Stuttgart• Andreas Metzger, University of Duisburg-Essen• Ariel Oleksiak, Poznan Supercomputing and Networking Center• Alexander Papaspyrou, TU Dortmund University• Alexander Willner, Universitat Bonn• Oliver Waldrich, Fraunhofer-Institute for Algorithms and Scientific Computing• Wolfgang Ziegler, Fraunhofer-Institute for Algorithms and Scientific Computing

Last but not least the editors would like to thank Cristy Burns for reviewing thebook and the people at Springer for their support and help during the process ofpublication.

xi

Contents

Part I Introduction to Service Level Agreements in Service Oriented

Architectures

Motivation and Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Joe M. Butler, Ramin Yahyapour, and Wolfgang Theilmann

1 Socio-economic Context and Motivation . . . . . . . . . . . . . . . . . . . . . . 31.1 Towards a Service Economy . . . . . . . . . . . . . . . . . . . . . . . . 31.2 Cloud Computing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.3 Future Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.4 Business Need for Systematic SLA Management . . . . . . . 5

2 Vision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Technical Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Related Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.1 ITIL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84.2 Autonomic Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5 Conclusion and Book Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

A Reference Architecture for Multi-Level SLA Management . . . . . . . . . . . 13Jens Happe, Wolfgang Theilmann, Andrew Edmonds, and Keven T. Kearney

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Scope and Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Foundation Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.1 Service Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2 Management of Services and SLAs. . . . . . . . . . . . . . . . . . . 173.3 Data Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204.1 Building Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204.2 Top-Level Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234.3 Main Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5 Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

xiii

References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

xiv Contents

The Open Reference Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Christoph Rathfelder, Benjamin Klatt, and Giovanni Falcone

1 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Adapted ORC Use Case Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2.1 Stakeholders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.2 Supported Business Process . . . . . . . . . . . . . . . . . . . . . . . . . 30

3 ORC Architecture and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.1 ORC Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

4 ORC Deployment Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 Interactions with the SLA@SOI Framework . . . . . . . . . . . . . . . . . . . 35

5.1 Discovery Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375.2 Provisioning Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385.3 Monitoring Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

6 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Part II Foundations for Service Level Agreements

The SLA Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Keven T. Kearney and Francesco Torelli

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 Basic Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 SLAs and SLA Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

3.1 SLA(T) Parties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483.2 SLA(T) Interface Declarations . . . . . . . . . . . . . . . . . . . . . . . 493.3 SLA(T) Agreement Terms . . . . . . . . . . . . . . . . . . . . . . . . . . 50

4 Interface Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 Value Types (the abstract constraint language) . . . . . . . . . . . . . . . . . 54

5.1 Constraint Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545.2 Constants and Datatypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565.3 Parametrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

6 Domain-Specific Vocabularies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587 An Example SLA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Service Construction Meta-Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Jens Happe, Wolfgang Theilmann, and Alexander Wert

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692 Service Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703 Software Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714 Core elements of the SCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

4.1 ServiceType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724.2 Service Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734.3 ServiceBuilder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754.4 Service Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Contents xv

5 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776 Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Translation of SLAs into Monitoring Specifications . . . . . . . . . . . . . . . . . . . 79Khaled Mahbub, George Spanoudakis, and Theocharis Tsigkritis

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792 The Monitoring Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803 Overview of EC-Assertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834 Parsing SLA Guarantee Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865 Generation of Operational EVEREST Monitoring Specifications . . 88

5.1 Templates for Basic QoS Terms . . . . . . . . . . . . . . . . . . . . . . 895.2 Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

6 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987 Related Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988 Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Part III Scientific Innovations

Penalty Management in the SLA@SOI Project . . . . . . . . . . . . . . . . . . . . . . . 105Constantinos Kotsokalis, Juan Lambea Rueda, Sergio Garcıa Gomez, andAugustın Escamez Chimeno

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1062 Business Considerations for Penalty Calculation and Reporting . . . 1073 Business Terms Associated with Penalties . . . . . . . . . . . . . . . . . . . . . 1074 The SLA@SOI Penalty Management Architecture . . . . . . . . . . . . . 109

4.1 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094.2 Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114.3 Violations and Penalties Management . . . . . . . . . . . . . . . . 113

5 A Formal, Novel Penalty Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1166 Example Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1187 Related Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1208 Summary and Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Dynamic Creation of Monitoring Infrastructures . . . . . . . . . . . . . . . . . . . . . 123Howard Foster and George Spanoudakis

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1232 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

2.1 Monitoring Features Specification . . . . . . . . . . . . . . . . . . . . 1263 Approach to Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274 SLA Term Decomposition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1295 Monitoring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

´

5.1 Monitor Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1305.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1315.3 Configuration Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . 132

xvi Contents

6 Implementation and Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1336.1 The MonitoringManager Packages . . . . . . . . . . . . . . . . . . . 1336.2 Testing and Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

7 Related Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1358 Conclusions and Future Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Runtime Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Davide Lorenzoli and George Spanoudakis

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1392 Related Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1413 Example Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1414 Background: The EVEREST Monitoring Framework . . . . . . . . . . . 1435 Prediction Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

5.1 Predictor Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1465.2 QoS Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

6 Architecture Of EVEREST+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1486.1 Prediction Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1496.2 Monitoring Specification Generator . . . . . . . . . . . . . . . . . . 1506.3 Model Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1506.4 QoS Predictor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

7 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Software Performance and Reliability Prediction . . . . . . . . . . . . . . . . . . . . . 153Franz Brosch

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1532 Goals and Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1543 QoS Meta-Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1554 Prediction Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1575 Prediction Realisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1595.2 Prediction Engine Internals . . . . . . . . . . . . . . . . . . . . . . . . . 1605.3 Prediction Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

6 Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Part IV Core Components of the Service Level Agreements Framework

G-SLAM – The Anatomy of the Generic SLA Manager . . . . . . . . . . . . . . . 167Miguel Angel Rojas Gonzalez, Peter Chronz, Kuan Lu, Edwin Yaqub,Beatriz Fuentes, Alfonso Castro, Howard Foster, Juan Lambea Rueda, and

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Escamez ChimenoAugustın

2 Plug-in-based Approach to the G-SLAM Architecture . . . . . . . . . . . 1683 The G-SLAM Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Contents xvii

3.1 Technology Used by the Plug-in-based G-SLAMArchitecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

4 Generic Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1704.1 Core of the G-SLAM via Interfaces . . . . . . . . . . . . . . . . . . 1704.2 Abstraction Layer for the Domain-Specific Components

PAC and POC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1724.3 Main Bundle for the G-SLAM . . . . . . . . . . . . . . . . . . . . . . . 1724.4 Syntax Conversion for Interoperability . . . . . . . . . . . . . . . . 1724.5 Protocol Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1734.6 SLATemplateRegistry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1744.7 SLARegistry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1744.8 MonitoringManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1754.9 Authorisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

5 Advertisements System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1766 Planning and Optimisation Component (POC) . . . . . . . . . . . . . . . . . 1787 Provisioning and Adjustment Component (PAC) . . . . . . . . . . . . . . . 1808 Skeleton SLAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

8.1 Maven Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1849 Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

A Generic Platform for Conducting SLA Negotiations . . . . . . . . . . . . . . . . . 187Edwin Yaqub, Philipp Wieder, Constantinos Kotsokalis, Valentina Mazza,Liliana Pasquale, Juan Lambea Rueda, Sergio Garcıa Gomez, and AugustınEscamez Chimeno

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1872 State of the Art . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1893 Protocol Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

3.1 Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1924 Protocol Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

4.1 Related Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1944.2 Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1954.3 Bilateral Negotiations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

5 Negotiation Rationality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2005.1 Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2005.2 Protocol Customisation Mechanism . . . . . . . . . . . . . . . . . . 2025.3 Business Take-Up of Negotiations . . . . . . . . . . . . . . . . . . . 203

6 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Part V Management of the Business Layer

Management of the Business SLAs for Services eContracting . . . . . . . . . . . 209Sergio Garcıa Gomez, Juan Lambea Rueda, and Augustın Escamez Chimeno

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2092 Business SLA Management in Current e-Contracting Proposals . . 210

xviii Contents

2.1 Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2102.2 Negotiation and Offer Building . . . . . . . . . . . . . . . . . . . . . . 2112.3 Contracting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2122.4 Runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

3 An SLA-Aware e-Contracting Proposal . . . . . . . . . . . . . . . . . . . . . . . 2133.1 Comprehesive SLA-Aware e-Contracting Suite . . . . . . . . . 2133.2 Customisation of Business SLA Definitions . . . . . . . . . . . 2143.3 Business SLA Post-Sale Management . . . . . . . . . . . . . . . . 214

4 Business Layer Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2154.1 Business Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2154.2 Business SLA Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

5 Modelling SLA Business Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2175.1 Business Terms Integration . . . . . . . . . . . . . . . . . . . . . . . . . 217

6 Future Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2217 Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Part VI Management of the Software Layer

Model-Driven Framework for Business Continuity Management . . . . . . . . 227Ulrich Winkler and Wasif Gilani

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2272 Business Continuity Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2293 Related Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2294 Model-Driven and Process-Centric BCM Framework . . . . . . . . . . . 231

4.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2314.2 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2334.3 Stakeholders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2344.4 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2344.5 Workflow and Methodology . . . . . . . . . . . . . . . . . . . . . . . . . 2354.6 Business Process Requirements Annotation . . . . . . . . . . . . 2364.7 IT BCM Model Derivation . . . . . . . . . . . . . . . . . . . . . . . . . . 2384.8 BEAM Derivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2404.9 Alpha BEAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2404.10 Beta BEAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2424.11 Gamma BEAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2434.12 Business Continuity Analysis . . . . . . . . . . . . . . . . . . . . . . . 2444.13 Analysis Result Presentation . . . . . . . . . . . . . . . . . . . . . . . . 2444.14 Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2454.15 Context-Sensitive Presentation Mode . . . . . . . . . . . . . . . . . 2464.16 Document-Oriented Presentation Mode . . . . . . . . . . . . . . . 246

5 Conclusions and Outlook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Contents xix

Managing Composite Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Sam Guinea, Annapaola Marconi, Natalia Rasadka, and Paolo Zampognaro

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2511.1 The Health and Mobility Use Case . . . . . . . . . . . . . . . . . . . 253

2 Management Approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2543 A Dynamic Orchestration Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2564 Dynamic Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2575 Process Restructuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2606 Related Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2647 Conclusions and Future Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Part VII Management of the Infrastructure Layer

SLA-Enabled Infrastructure Management . . . . . . . . . . . . . . . . . . . . . . . . . . 271John Kennedy, Andrew Edmonds, Victor Bayon, Pat Cheevers, Kuan Lu,Miha Stopar, and Damjan Murn

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2712 SLA-Aware Infrastructure Architecture . . . . . . . . . . . . . . . . . . . . . . . 2723 Infrastructure SLA Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2734 Infrastructure SLA Manager Implementation . . . . . . . . . . . . . . . . . . 274

4.1 Infrastructure Planning and Optimisation . . . . . . . . . . . . . . 2754.2 Infrastructure Provisioning and Adjustment . . . . . . . . . . . . 276

5 Infrastructure Service Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2775.1 Open Cloud Computing Interface . . . . . . . . . . . . . . . . . . . . 278

6 Infrastructure Service Manager Implementation . . . . . . . . . . . . . . . . 2787 Provisioning System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

7.1 Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2807.2 Re-provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

8 Infrastructure Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2829 Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Part VIII Selected Business Use Cases

Introduction to the SLA@SOI Industrial Use Cases . . . . . . . . . . . . . . . . . . 291Joe M. Butler

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2912 Considerations for Use Case Selection . . . . . . . . . . . . . . . . . . . . . . . . 2913 Use Case Key Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

The ERP Hosting Use Case Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295Wolfgang Theilmann, Jens Happe, and Ulrich Winkler

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2952 Business Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

xx Contents

2.1 Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2972.2 Business Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

3 Foundations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2993.1 Service Hierarchies for Business Applications . . . . . . . . . 2993.2 Related Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

4 SLA Management Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3005 SLA Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

5.1 SLA Terms and Translation . . . . . . . . . . . . . . . . . . . . . . . . . 3025.2 Integrated planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

6 Business Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3066.1 Improvements to enable dynamic service provisioning . . . 3066.2 Improvements to increase efficiency and reduce costs . . . 3076.3 Improvements to enhance transparency . . . . . . . . . . . . . . . 307

7 Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

The Enterprise IT Use Case Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Michael Nolan and Joe M. Butler

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3112 Business Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

2.1 Business Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3132.2 Managing IT Like a Business . . . . . . . . . . . . . . . . . . . . . . . 3132.3 The Provisioning Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . 3152.4 The Runtime Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3152.5 The Investment Governance Scenario . . . . . . . . . . . . . . . . . 3182.6 Business Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3192.7 Business Process Changes . . . . . . . . . . . . . . . . . . . . . . . . . . 3202.8 Integrating BLOs into the Digital SLA . . . . . . . . . . . . . . . . 320

3 SLA Management Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3224 Business Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

4.1 Improvements for IT Enabling the Enterprise . . . . . . . . . . 3254.2 Improvements to IT Efficiency . . . . . . . . . . . . . . . . . . . . . . 3254.3 Improvements to IT Investment and Technology Adoption326

5 Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

The Service Aggregator Use Case Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . 329Juan Lambea Rueda, Sergio Garcıa Gomez, Augustın Escamez Chimeno

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3292 Business Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

2.1 Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3322.2 Business Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

3 Foundations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3343.1 Service Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3343.2 Related Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

4 SLA Management Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

´´

Contents xxi

5 SLA Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3385.1 SLA Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

6 Business Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3396.1 Improved Customer Satisfaction . . . . . . . . . . . . . . . . . . . . . 3396.2 Improved Dependability . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3406.3 Improved End-To-End Manageability . . . . . . . . . . . . . . . . . 3406.4 Improved Decision-Making . . . . . . . . . . . . . . . . . . . . . . . . . 3406.5 Improved Agility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3406.6 Improved Operational and Energy Efficiency . . . . . . . . . . 341

7 Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

The eGovernment Use Case Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343Giampaolo Armellin, Annamaria Chiasera, Ganna Frankova, LilianaPasquale, Francesco Torelli, and Gabriele Zacco

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3442 Business Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

2.1 Mobility and health care services . . . . . . . . . . . . . . . . . . . . 3442.2 Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3452.3 Business Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

3 Use Case Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3474 SLA Management Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3495 SLAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3526 Evaluation: Practice and Experience . . . . . . . . . . . . . . . . . . . . . . . . . . 3547 Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

List of Contributors

Giampaolo ArmellinGPI, Via Ragazzi del ’99, 13, Trento 38123, Italy e-mail: [email protected]

Victor BayonIntel Labs Europe, Collinstown Industrial Estate, Leixlip, Co. Kildare, Ireland,e-mail: [email protected]

Franz BroschFZI Research Center for Information Technology, Haid-und-Neu-Str. 10-14, 76131Karlsruhe, Germany, e-mail: [email protected]

Joe M. ButlerIntel Labs Europe, Collinstown Industrial Estate, Leixlip, Co. Kildare, Ireland,e-mail: [email protected]

Alfonso CastroTelefonica I+D, Distrito-C. Ronda de la Comunicacin s/n. Edificio Oeste 1, planta5. 28050 Madrid, Spain, e-mail: [email protected]

Pat CheeversIntel Labs Europe, Collinstown Industrial Estate, Leixlip, Co. Kildare, Ireland,e-mail: [email protected]

Peter ChronzTU Dortmund University, Service Computing Group/ITMC, August-Schmidt-Strasse 12, 44227 Dortmund, Germany, e-mail: [email protected]

Annamaria ChiaseraGPI, Via Ragazzi del ’99, 13, Trento 38123, Italy,e-mail: [email protected]

Augustın Escamez ChimenoTelefonica I+D, c/Recogidas 24, Portal B, Escalera A, Planta 1, Puerta A, 18002Granada, Spain, e-mail: [email protected]

xxiii

xxiv List of Contributors

Beatriz FuentesTelefonica I+D, Distrito-C. Ronda de la Comunicacin s/n. Edificio Oeste 1, planta5. 28050 Madrid, Spain, e-mail: [email protected]

Jens HappeSAP Research, Vincenz-Priessnitz-Str. 1, 76131 Karlsruhe, Germany, e-mail:[email protected]

Andrew EdmondsIntel Labs Europe, Collinstown Industrial Estate, Leixlip, Co. Kildare, Ireland,e-mail: [email protected]

Giovanni FalconeFZI Research Center for Information Technology, Haid-und-Neu-Str. 10-14, 76131Karlsruhe, Germany, e-mail: [email protected]

Ganna FrankovaGPI, Via Ragazzi del ’99, 13, Trento 38123,e-mail: [email protected]

Sergio Garc a GomezTelefonica I+D, c/Abraham Zacuto 10, Parque Tecnologico de Boecillo, 47151Valladolid, Spain, e-mail: [email protected]

Wasif GilaniSAP Research, The Concourse, Queen’s Road, Titanic Quarter, Belfast, BT3 9DT,United Kingdom, e-mail: [email protected]

Sam GuineaPolitecnico di Milano, v. Golgi 42, Milano, Italy,e-mail: [email protected]

Howard FosterDepartment of Computing, City University London, Northampton Square, EC1V0HB, London, e-mail: [email protected]

Keven T. KearneyEngineering Ingegneria Informatica spa, Via Riccardo Morandi, 32, 00148 Roma,Italy, e-mail: [email protected]

John KennedyIntel Labs Europe, Collinstown Industrial Estate, Leixlip, Co. Kildare, Ireland,e-mail: [email protected]

Benjamin KlattFZI Research Center for Information Technology, Haid-und-Neu-Str. 10-14, 76131Karlsruhe, Germany, e-mail: [email protected]

Constantinos KotsokalisTU Dortmund University, August-Schmidt-Strasse 12, 44227 Dortmund, Germany,e-mail: [email protected]

´ı

List of Contributors xxv

Davide LorenzoliSchool Of Informatics, Department Of Computing, City University, Northamptonsquare, London, NW1 0TY, UK,e-mail: [email protected]

Kuan LuTU Dortmund University, Service Computing Group/ITMC, August-Schmidt-Strasse 12, 44227 Dortmund, Germany, e-mail: [email protected]

Khaled MahbubDepartment of Computing, City University London, Northampton Square, London,EC1V 0HB, UK, e-mail: [email protected]

Annapaola MarconiFondazione Bruno Kessler, via alla Cascata 56C, 38121 Povo, Trento, Italy, e-mail:[email protected]

Valentina MazzaPolitecnico di Milano, piazza L. Da Vinci, 32 - 20133 Milano, Italy e-mail:[email protected]

Jessica McCarthyIntel Labs Europe, Collinstown Industrial Estate, Leixlip, Co. Kildare, Ireland,e-mail: [email protected]

Damjan MurnXLAB d.o.o., Pot za Brdom 100, 1000 Ljubljana, Slovenia, e-mail: [email protected]@xlab.si

Michael NolanIntel Labs Europe, Collinstown Industrial Estate, Leixlip, Co. Kildare, Ireland,e-mail: [email protected]

Liliana PasqualePolitecnico di Milano, piazza L. Da Vinci, 32 - 20133 Milano, Italy e-mail:[email protected]

Natalia RasadkaFondazione Bruno Kessler, via alla Cascata 56C, 38121 Povo, Trento, Italy, e-mail:[email protected]

Christoph RathfelderFZI Research Center for Information Technology, Haid-und-Neu-Str. 10-14, 76131Karlsruhe, Germany, e-mail: [email protected]

Miguel Angel Rojas GonzalezTU Dortmund University, Service Computing Group/ITMC, August-Schmidt-Strasse 12, 44227 Dortmund, Germany, e-mail: [email protected]

Juan Lambea RuedaTelefonica I+D, Distrito-C. Ronda de la Comunicacin s/n. Edificio Oeste 1, planta

xxvi List of Contributors

5, 28050 Madrid, Spain, e-mail: [email protected]

George SpanoudakisDepartment of Computing, City University London, Northampton Square, London,EC1V 0HB, UK, e-mail: [email protected]

Miha StoparXLAB d.o.o., Pot za Brdom 100, 1000 Ljubljana, Slovenia, e-mail: [email protected]

Wolfgang TheilmannSAP Research, Vincenz-Priessnitz-Str. 1, 76131 Karlsruhe, Germany, e-mail:[email protected]

Theocharis TsigkritisDept. of Computing, City University London, Northampton Square, London, EC1V0HB, UK, e-mail: [email protected]

Francesco TorelliEngineering Ingegneria Informatica Spa, Via Riccardo Morandi, 32, 00148 Roma,Italy, e-mail: [email protected]

Alexander WertSAP Research, Vincenz-Priessnitz-Str. 1, 76131 Karlsruhe, Germany, e-mail:[email protected]

Philipp WiederTU Dortmund University, Service Computing Group/ITMC, August-Schmidt-Strasse 12, 44227 Dortmund, Germany, e-mail: [email protected]

Ulrich WinklerSAP Research, The Concourse, Queen’s Road, Titanic Quarter, Belfast, BT3 9DT,United Kingdom, e-mail: [email protected]

Ramin YahyapourTU Dortmund University, Service Computing Group/ITMC, August-Schmidt-Strasse 12, 44227 Dortmund, Germany,e-mail: [email protected]

Edwin YaqubTU Dortmund University, Service Computing Group/ITMC, August-Schmidt-Strasse 12, 44227 Dortmund, Germany, e-mail: [email protected]

Gabriele ZaccoFondazione Bruno Kessler, Via Santa Croce 77, 38122 Trento, Italy, e-mail:[email protected]

Paolo ZampognaroEngineering, Engineering Ingegneria Informatica Spa, Via Riccardo Morandi, 32,00148 Roma, Italy, e-mail: [email protected]