Jump to content

EU Centre of ExcellenceISO 9001

ERCIMW3C MemberFraunhofer Project Center

BonFIRE

BonFIRE
Full name: Building service testbeds on FIRE
Homepage: http://www.bonfire-project.eu/
Department: Department of Distributed Systems, Informatics Laboratory
Start date: 2012. 09. 01.
End date: 2013. 09. 01.
External identifier: 257386

Participants

ATOS, HP, SAP, UCM, EPCC, HLRS Stuttgart, IBBT, TUB, IT Innovation, FhG Fokus, Inria, i2CAT, University of Manchester, CESGA, CETIC, Cloudium Systems, RedZinc, ICCS Athens, Televes SA, MTA SZTAKI, IN2, University of Patras, Wellness Telecom

Description

BonFIRE will design, build and operate a multi-site Cloud prototype FIRE facility to support research across applications, services and systems at all stages of the R&D lifecycle, targeting the services research community on Future Internet.

The BonFIRE vision is to give researchers in these areas access to a facility that supports large scale multi-disciplinary experimentation of their systems and applications addressing all aspects of research across all layers. We develop and support a framework which allows service-based computing practitioners to experiment with their latest ideas in service orientation and distributed computing. Our overall goal is to encourage new communities of experimenters to take advantage of the opportunities offered by the FIRE infrastructure to guide the development of the Future Internet from a service-based applications standpoint.

The basis of our KOPFire experiment is the KOPI Plagiarism Search Portal. KOPI is a nationwide plagiarism service in Hungary. KOPI works asynchronously: it accepts requests in the form of uploaded documents, which is checked for copied content over various databases. After this, a report is sent to the user containing the copied parts and their original sources. KOPI service is implemented as a multi-layer infrastructure which means an interconnected set of virtual hosts with different capabilities. KOPI typically suffers from bursts of incoming requests, and therefore would benefit from automatic, elastic scaling of its service infrastructure.

The experiment investigates the costs and effects of various scaling operations in a cloud federation and their possible combinations in an elasticity strategy. The final goal of the elasticity strategy is to stabilize end-to-end QoS (the quality of experience) around desired values for the processing of incoming plagiarism search requests while keeping resource usage at a minimum. The ideal strategy has to effectively detect and avoid the bottlenecks in the system, by duplicating, stopping or moving the appropriate components, and furthermore it also has to detect capacity overhead and downscale the infrastructure accordingly in order to minimize resource usage in clouds.