Building service testbeds on FIRE

BonFIRE open call info teleconference February 9th, 2012 Josep Martrat – ATOS

Agenda

• • • •

Project vision and objectives Three Scenarios overview Project activities Open call data sheet • Topic A Experiments • Topics B Cloud provider • Open call objectives and calendar • Experiment structure • Experiment submission

2

FIRE open calls info call

BonFIRE 2

BonFIRE data sheet • • • • •

Type of project: Integrated Project Project coordinator: ATOS Project start date: 1st June 2010 Duration: 42 months EC contribution: 7.2M€ (orig 6.7 M€) (1.34 M€ for 2 open calls)

The BonFIRE (Building service testbeds for Future Internet Research and Experimentation) project is designing, building and operating a multi-site cloud facility to support research across applications, services and systems targeting services research community on Future Internet.

3

BonFIRE 3

BonFIRE Overview Testing experiments selected in open calls Service Components in virtual machines to be deployed on the Cloud

• Access and Controlled deployment • Monitoring • Heterogeneous and virtualised • Compute, storage and networking resources

Permanent & On-Request infrastructure facilities

4

BonFIRE 4

Three Scenarios

1. Extended multi-site clouds connected through normal internet 2. Cloud scenario with emulated network 3. Extended Cloud scenario with controlled network (implies federation with network facility)

5

BonFIRE 5

BonFIRE sites EPCC (Edinburg)

Scenario 3 Geant Autobanh and studyng Federica-like PSNC (Poznan)

Scenario 1 Scenario 2

(normal internet) HP (Bristol)

Emulab (Virtual Wall)

IBBT (Ghent)

HLRS (Stuttgart) INRIA (Rennes) Permanent (<350cores / 30TB) & On-Request (theoretically +3000 cores) infrastructures Note: network links not representative

6

BonFIRE 6

Bonfire (simplified!) Architecture* (*details later) Restf uly

Portal

OVF

Experiment descriptor

ID

BonFIRE API Experiment manager scheduler

BonFIRE Broker

Resource manager orchestrator

Enactor

…

… OCCi

Cloud API (OCCi) Monitoring

Cloud Provider

7

…

Cloud Provider

KVM

XEN

ESXi

Open Nebula Cells VMWare…

BonFIRE 7

Project Activities

Each new experiment will be a WP in the Activity 5

Cloud Provider will mainly participate in Act 3 (Act2/6 partially)

8

FIRE open calls info call

BonFIRE 8

BonFIRE Partnership

Facility operation Facility construction

Researchers OPEN CALLS

Facility sustainability

EXPERIMENTS

Project coordination 9

BonFIRE 9

Open call for new experiments and a cloud provider This open call: € 600.000 total available EC funding Two Topics; A) Experiments (500K€) in Scenarios 1-2-3 – Funding per experiment: max 150K€ (about 3-4 experiments, round 100K€ typical) – Participants: 1 or 2 organizations/experiment max – Duration: maximum 12 months

B) Cloud provider (100K€) – 1 company offering infrastructure and becoming a BonFIRE Cloud site (Proof of Concept) – Duration: 15 months

Start date in the project: September 2012 Evaluation (FP7 rules): external evaluators and consensus meeting Note: Payment scheme: 30% advance payment. Q1 cost. Rest at the end. BonFIRE 10 10

What are we looking for? (Topic A - Experiments) • Testing Experiments to trial on the Cloud semi-consolidated software technologies or semi-mature results of R&D Internet of Services community. • Pre-comercial software or prototypes to be optimised, consolidated or study their behaviour on the cloud facility • Not pure eScience (Grid-like) applications looking only for capacity / storage but innovative multi-cloud usage scenarios on the facility. • Typically the experiment would need to be distributed, with VMs deployed across at least 2 sites/admin domains (scenario 1&3). • Certain emphasis is given to scenario 3 (FI research that is very sensible to network parameters (bandwidth reservation) • Justify the need of a multi-cloud facility (scenario 1&3) or sophisticated network emulation (scenario 2) in your experiment. • Combination of scenarios in an experiment proposal is possible (pahses in an ‘increase of realism). Explain the approach in detail. 11

BonFIRE 11

What are we looking for? (Topic B – Cloud provider) • Company with proven commercial experience in Cloud service provision (with its own IaaS “off-the-shelf” solutions portfolio) and reference clients • Cloud provider offering access to its own infrastructure becoming BonFIRE site (IaaS). Dedicated computing environment where experiments can be deployed. • Access via OCCI-based API and web-based interfaces (explain approach) • Mínimum requested capacity from 8 to 16 nodes x 4 cores (3GHz) 8 GB RAM and 2-3 Tb SAN (Note: the purchase of hardware is not covered by the project – not elegible costs) • Organization willing to install and test the BonFIRE stack (broker and portal) in their environment and report the experience • Contribute with feedback on sustainability and exploitation tasks 12

BonFIRE 12

Open call for new experiments What we offer: BonFIRE features: • Controlled deployment on multi-site clouds (scenario 1,2,3) • Monitoring of standard metrics at VM or physical level • Monitoring of user specified metrics (application level) at VM level • Controlled/advanced emulated network (emulab) (for scenario 2) – VirtualWorld • Controlled deployment with network bandwidth guarantee between 2 cloud sites (scenario 3) • Access to heterogeneous resources.

13

BonFIRE 13

Open call: structure of experiments To smooth integrate the experiments into the project: • • • •

Basic task list set Common deliverable list Participation in project reporting by partner and Workpackage Interactions with cross activities: experiment support

(more on the applicant guide & proposal template)

14

BonFIRE 14

Open call experiment structure: tasks

• • • • • •

Task 1 – Motivation and Design Task 2 - Experimental set up Task 3 – Execution and subsequent iteration Task 3 – Execution and subsequent iteration Task 4 - Experimental write up Task 5 – Dissemination and Case studies

• Gantt diagram can be adapted to specifities of each call (explain this) • Synchronised timescale (approx) • Control Points (asociated milestones or deliverables) • Other structure is possible but must be well justified.

15

FIRE open calls info day

BonFIRE 15

Our Open Call Calendar Date (2012)

Period

Jan 3rd (or before) -30 days February 1st

Day 1: call open

February 7th

16

Action Call announcment to PO Call publication (last of 3 newspapers + international magazine) + Cordis

InfoCall

March 7th

At least +5 weeks

Close Call : 17:00 Brussels time (WED)

March 23rd

Weeks 6,7 ( 2 weeks)

Finalise Call Evaluation Preparations, Communicate Experts to the Commission, Conduct Evaluation

April 13th

Week 10 (3 weeks)

Submit Evaluation Report to the PO and request accession of the new beneficiaries

June 27th

Week 17 (7 weeks but can be less)

Project Officer approves accession of new beneficiaries to grant agreement; project communicates the result of each proposal to the proposer

July - August

Contract Amendment to reflect new Partners

September 1

New Partners operative / starting date

BonFIRE 16

IPR issues

17

• BonFIRE Project interest in the open call experiments is the use and improvement of the BonFIRE facility and not the (protected) content per se. • The new cloud site is treated separately in terms of IPR. Access API (TBD depending on development contributions and starting point). No ownership rights over Broker (access & use) • Experiments are considered sub-projects. Access rights within the sub-project are reserved to sub-project members. • In general terms, sub-project partners are not granted access to the foreground or background of the other Parties and the other Parties are not granted access to the foreground or background of the sub-project members. (CA available ondemand) • All experiments have to provide a publishable report of their experiment / case study.

BonFIRE 17

Open call: support Support documentation available • • • •

Full call text Template for proposal and guidelines FAQ / also set up as a blog for interactive questions Support mailing list (process and technical questions) [email protected]

• http://www.bonfire-project.eu/involved/open-call-info 18

BonFIRE 18

Open call: submission Submission of proposals: • • • •

Use proposal template provided PDF format – one file Language - ENGLISH By email with subject: "Call 2– BonFIRE /your proposal acronym vx.x"

• SUBMISSION EMAIL: [email protected] • DEADLINE: 7th March 17:00 Brussels time

19

BonFIRE 19

Building service testbeds on FIRE

Thank you for your attention