SEVENTH FRAMEWORK PROGRAMME

SEVENTH FRAMEWORKPROGRAMME

Grant agreement for: Combination of CP & CSA*

Annex I - "Description of Work"Project acronym: MANTYCHORE

Project full title: " IP Networks as a Service "

Grant agreement no: 261527

Date of preparation of Annex I (latest version): 2010-04-15

Date of last change: 2010-04-15

Date of approval of Annex I by Commission:

Table of Contents

Part A

A.1 Project summary ......................................................................................................................................3

A.2 List of beneficiaries ..................................................................................................................................4

A.3 Overall budget breakdown for the project ............................................................................................... 5

Workplan Tables

WT1 List of work packages ............................................................................................................................1

WT2 List of deliverables .................................................................................................................................2

WT3 Work package descriptions ................................................................................................................... 4

Work package 1......................................................................................................................................4

Work package 2......................................................................................................................................4

Work package 3......................................................................................................................................4

Work package 4......................................................................................................................................4

Work package 5......................................................................................................................................4

Work package 6......................................................................................................................................4

Work package 7......................................................................................................................................4

WT4 List of milestones .................................................................................................................................26

WT5 Tentative schedule of project reviews ................................................................................................. 28

WT6 Project effort by beneficiaries and work package ................................................................................29

WT7 Project effort by activity type per beneficiary ...................................................................................... 30

WT8 Project efforts and costs ......................................................................................................................31

A1:Project summary

261527 MANTYCHORE - Part A - 2010-04-15 22:38 - of 5

Project Number 1 261527 Project Acronym 2 MANTYCHORE

One form per project

General information

Project title 3 IP Networks as a Service

Starting date 4 01/10/2010

Duration in months 5 30

Call (part) identifier 6 FP7-INFRASTRUCTURES-2010-2

Activity code(s) mostrelevant to your topic 7

:

Free keywords 8IP network service, Infrastructure as a Service, NRENoperation tools, zero-carbon, infrastructure resourcemarketplaces, network virtualisation, services for theresearch community, renewable energy

Abstract 9

Current National Research and Education Networks (NRENs) in Europe provide connectivity services to theircustomers: the research and education community. Traditionally these services have been delivered on amanual basis, although some efforts towards automating the service setup and operation have been initiated.At the same time, more focus is being put in the ability of the community to control some characteristics of theseconnectivity services, so that users can change some of the service characteristics without having to renegotiatewith the service provider.The MANTYCHORE project wants to consolidate this trend and allow the NRENs to provide a complete, flexibleIP network service that allows research communities to create an IP network under their control, where theycan configure: i) layer 1 -optical- ii) layer 2 - Ethernet and MPLS- and iii) layer 3 -IP addressing, internal routing,peering, firewalls- . To achieve its goals, MANTYCHORE FP7 will integrate and improve the tools developed bythe past, privately funded MANTICORE projects and related initiatives (IaaS Framework efforts), and produce arobust and extensible software to operate and use the IP network service.MANTYCHORE will carry out pre-operational deployments of the IP network service at two NRENS: HEAnetand NORDUnet. Initially three communities of researchers will benefit from this service: the Nordic Health DataNetwork, the British Advance High Quality Media Services and the Irish Grid effort. Part of the project effort willbe dedicated to consolidate and enhance the community of providers (NRENs but also commercial) and users ofthe IP network service. Finally, the JRAs will research two important topics to improve the IP network service: i)an infrastructure resource marketplace, to further automate the negotiation of the resources that comprise the IPnetwork; and ii) the use of renewable energy sources to power e-Infrastructures, so that they can become carbonneutral.

A2:List of Beneficiaries



List of Beneficiaries

No Name Short name CountryProject entrymonth10

Project exitmonth

1 FUNDACIO PRIVADA I2CAT, INTERNET I INNOVACIO DIGITAL ACATALUNYA I2CAT Spain 1 30

2 NORDUNET A/S NORDUNET A/S Denmark 1 30

3 HEANET LTD HEANET Ireland 1 30

4 UNI-C DANMARKS EDB-CENTER FOR UDDANNELSE OG FORSKNING UNI-C Denmark 1 30

5 UNIVERSITY OF ESSEX UESSEX United Kingdom 1 30

6 TELEFONICA INVESTIGACION Y DESARROLLO SA TID Spain 1 30

7 THE PROVOST FELLOWS & SCHOLARS OF THE COLLEGE OF THEHOLY AND UNDIVIDED TRINITY OF QUEEN ELIZABETH NEAR DUBLIN TCD Ireland 1 30

A3:Budget Breakdown



One Form per Project

Estimated eligible costs (whole duration of the project)Participantnumberin this

project 11

Participantshort name

Fund.%12 Ind. costs13

RTD (A)Coordination

(B)Support (C)

Management(D)

Other (E)Total

A+B+C+D+E

RequestedEU

contribution

1 I2CAT 75.0 T 60,400.00 43,600.00 0.00 80,000.00 248,386.00 432,386.00 402,843.00

2 NORDUNET A/S 75.0 A 87,176.00 46,117.00 0.00 0.00 146,644.00 279,937.00 258,143.00

3 HEANET 50.0 T 35,288.00 49,705.00 0.00 0.00 81,011.00 166,004.00 131,895.00

4 UNI-C 50.0 A 0.00 32,896.00 0.00 0.00 131,680.00 164,576.00 153,679.00

5 UESSEX 75.0 T 97,280.00 31,040.00 0.00 0.00 121,600.00 249,920.00 215,318.00

6 TID 50.0 A 72,849.00 16,769.00 0.00 0.00 61,031.00 150,649.00 114,224.00

7 TCD 75.0 T 0.00 18,409.00 0.00 0.00 102,505.00 120,914.00 114,816.00

Total 352,993.00 238,536.00 0.00 80,000.00 892,857.00 1,564,386.00 1,390,918.00

Note that the budget mentioned in this table is the total budget requested by the Beneficiary and associated Third Parties.

* The following funding schemes are distinguished

Collaborative Project (if a distinction is made in the call please state which type of Collaborative project is referred to: (i) Smallof medium-scale focused research project, (ii) Large-scale integrating project, (iii) Project targeted to special groups such asSMEs and other smaller actors), Network of Excellence, Coordination Action, Support Action.

1. Project number

The project number has been assigned by the Commission as the unique identifier for your project, and it cannot be changed.The project number should appear on each page of the grant agreement preparation documents to prevent errors duringits handling.

2. Project acronym

Use the project acronym as indicated in the submitted proposal. It cannot be changed, unless agreed during the negotiations.The same acronym should appear on each page of the grant agreement preparation documents to prevent errors duringits handling.

3. Project title

Use the title (preferably no longer than 200 characters) as indicated in the submitted proposal. Minor corrections are possible ifagreed during the preparation of the grant agreement.

4. Starting date

Unless a specific (fixed) starting date is duly justified and agreed upon during the preparation of the Grant Agreement, theproject will start on the first day of the month following the entry info force of the Grant Agreement (NB : entry into force =signature by the Commission). Please note that if a fixed starting date is used, you will be required to provide a detailedjustification on a separate note.

5. Duration

Insert the duration of the project in full months.

6. Call (part) identifier

The Call (part) identifier is the reference number given in the call or part of the call you were addressing, as indicated in thepublication of the call in the Official Journal of the European Union. You have to use the identifier given by the Commission inthe letter inviting to prepare the grant agreement.

7. Activity code

Select the activity code from the drop-down menu.

8. Free keywords

Use the free keywords from your original proposal; changes and additions are possible.

9. Abstract

10. The month at which the participant joined the consortium, month 1 marking the start date of the project, and allother start dates being relative to this start date.

11. The number allocated by the Consortium to the participant for this project.

12. Include the funding % for RTD/Innovation – either 50% or 75%

13. Indirect cost modelA: Actual CostsS: Actual Costs Simplified MethodT: Transitional Flat rateF :Flat Rate

WorkplanTables

Project number

261527

Project title

MANTYCHORE—IP Networks as a Service

Call (part) identifier

FP7-INFRASTRUCTURES-2010-2

Funding scheme

Combination of CP & CSA

WT1List of work packages

261527 MANTYCHORE - Workplan table - 2010-04-15 22:38 - Page 1 of 31


LIST OF WORK PACKAGES (WP)

WPNumber53

WP TitleType ofactivity 54

Leadbeneficiarynumber 55

Person-months 56

Startmonth57

Endmonth58

WP 1 Project Management MGT 1 10.00 1 30

WP 2 Dissemination, Exploitation, Standardisationand Liaisons COORD 3 10.50 1 30

WP 3 Consolidating the User Community andUsers Training COORD 2 9.00 2 21

WP 4 Software refinement OTHER 1 39.50 2 30

WP 5 IP Networks as a Service for VirtualResearch Communities OTHER 2 56.00 10 30

WP 6 Infrastructure Resources Marketplace RTD 5 17.00 2 20

WP 7 Zero-carbon emission virtual infrastructures RTD 3 14.50 7 25

Total 156.50

WT2:List of Deliverables



List of Deliverables - to be submitted for review to EC

Delive-rableNumber61

Deliverable TitleWPnumber53

Lead benefi-ciary number

Estimatedindicativeperson-months

Nature 62

Dissemi-nation level63

Delivery date64

D1.1 ProjectPresentation 1 1 0.50 R PU 1

D1.2 First PeriodicActivity Report 1 1 4.25 R CO 15

D1.3 Final ActivityReport 1 1 4.25 R CO 30

D1.4Project ResultsEvaluationReport

1 1 1.00 R PU 30

D2.1

Exploitation,dissemination,standardisationand liaison plan

2 1 1.00 R PU 3

D2.2 Project website 2 1 2.00 O PU 5

D2.3

Report onrelated research,exploitation anddisseminationactivities andplanning update

2 3 3.50 R PU 15

D2.4

Report onstandards,exploitation anddisseminationactivities andliaison withrelated initiatives

2 3 3.50 R PU 30

D2.5MANTYCHOREsoftwarebusiness plan

2 1 0.50 R PU 14

D3.1 User manuals 3 1 4.00 R PU 6

D3.2 User communityfinal report 3 2 5.00 R PU 19

D4.1 Requirementsanalysis report 4 3 7.50 R PU 5

D4.2Softwaredevelopmentreport

4 1 32.00 P PU 30

D5.1Feasibility ofIP Networksas a Service in

5 6 5.00 R PU 20

WT2:List of Deliverables



Deliverable TitleWPnumber53

Lead benefi-ciary number


Nature 62

Dissemi-nation level63

Delivery date64

a commercialenvironment

D5.2

Report onIP Networksas a Servicedeploymentin NRENs,and its use byvirtual researchcommunities

5 2 51.00 R PU 30

D6.1

Infrastructuremarketplacemechanismsstudy

6 5 12.00 R PU 14

D6.2

Implementationof themarketplacereport

6 1 5.00 P PU 20

D7.1

IntegrationbetweenMANTYCHOREand GSN report

7 3 7.00 R PU 16

D7.2Networksmigration testsreport

7 2 7.50 R PU 25

Total 156.50

WT3:Work package description



One form per Work Package

Work package number 53 WP1 Type of activity 54 MGT

Work package title Project Management

Start month 1

End month 30

Lead beneficiary number 55 1

Objectives

The main goal of WP1 is to manage and coordinate all the activities of the project and also the financial andtechnical issues. WP1 includes all the processes related with the management, like: reporting of any progress,planning, reporting the finished work, etc. For this reason, the main related tasks aim is to manage all theseissues, this WP1 will permit to control the entire project and the progress of the different partners. This activityalso ensures that the project objectives are achieved. WP1 represents the contact point to the Commission.

Description of work and role of partners

WP1 Activity will first establish the work to be done for the internal project management. Then, it will ensure thatall the requirements that the project must accomplish are done according to the schedule and the budget. Thisactivity is also the contact point of the project to the Commission. WP1 is also responsible for supervising thateach task is being carried out during the established period of time and also it will have to manage the possibleleaving of a partner or the entrance of a new partner in the project.The work to be performed consists in the following 3 tasks:

T1.1 Project Planning (Start: M1, End: M1, Leader: i2CAT)• Before signing the contract, rules for documenting in the Consortium Agreement will have to be specified; theserules should include the roles of the GA and TEC, the voting rights of the GA, the distribution of the advancepayment and the settlement of subsequent cost claims.• Set the procedures to be followed for reporting, collecting the regular reports and sending these to theCommission and receiving and distributing the advance payments.• Set the dates for all the reports, deliverables and milestones. Moreover, this task will have to supervise all thework done.• Supervise the creation of the web which will include all the documentation elaborated during the project.

T1.2 Work Progress Tracking (Start: M2, End: M30, Leader: i2CAT)• Supervise all the deliverables elaborated during the project.• Collect all the regular reports of progress and sending them to the Commission• Ensure an open flow of information during the project.• Organise the review meetings.• Supervise the production of the Periodic Activity Reports, Periodic Management Reports and Detailed Plansreports.• Be the responsible for the contractual issues: maintaining the technical description of the work, the ConsortiumAgreements and any Contract Amendments.• Orient all the partners on administrative issues.• Plan how the knowledge arisen from the project will be disseminated and used.• Supervise the wiki and the e-mail lists.

T1.3 Project Results Evaluation (Start: M28, End: M30, Leader: i2CAT)• Collect the final reports of the different partners to prepare the final document.• Evaluate the different tasks of the project and its result, comparing them to the objectives.• Define and specify the final conclusions of the project.



Role of Partners

i2CAT is the Project Coordinator and will be the formal point of contact with the Project Officer for all contractualmatters (including the transfer of financial payments). i2CAT will chair the General Assembly (GA) meetings.i2CAT provides the first level contact to other projects (at a technical level, liaison will also be performed byactivity leaders and individual partners). This way, i2CAT is the leader and the only participant of WP1.

Person-Months per Participant

Participant number 10 Participant short name 11 Person-months per participant

1 I2CAT 10.00

Total 10.00

List of deliverables


Deliverable Title

Leadbenefi-ciarynumber


Nature 62

Dissemi-nationlevel 63

Delivery date 64

D1.1 Project Presentation 1 0.50 R PU 1

D1.2 First Periodic Activity Report 1 4.25 R CO 15

D1.3 Final Activity Report 1 4.25 R CO 30

D1.4 Project Results Evaluation Report 1 1.00 R PU 30

Total 10.00

Description of deliverables

D1.1) Project Presentation: This deliverable is a public description of the project in terms of main goals, keyissues technical approach and achievements. It is intended for publication on the Websites of the Commissionand the project. [month 1]

D1.2) First Periodic Activity Report: The First Periodic Activity Report provides a summary of the major resultsand achievements of the project during the first 15 months and reports on the resources spent to make theseachievements. [month 15]

D1.3) Final Activity Report: A Final Project Report is also produced to summarise the major results andachievements of the project and concludes the projects technical work. The regular reports from the project tothe Commission may also be considered as deliverables from this Activity. [month 30]

D1.4) Project Results Evaluation Report: A report related to the evaluation of the results of all activities carriedout during the project. For example if IP Network Services have became useful for researchers, or if themarketplace implemented has worked as it was expected, and so on. In other words, this report is intended toexplain how beneficial the project has been for the virtual research communities. [month 30]



Schedule of relevant Milestones

Milestonenumber 59 Milestone name


Deliverydate fromAnnex I 60

Comments

MS1 All project management procedures in placeand operational 1 1

MS2 First project review successfully completed 1 15

MS3 Second project review successfullycompleted 1 30

MS4 All project documentation completed 1 30





Work package number 53 WP2 Type of activity 54 COORD

Work package title Dissemination, Exploitation, Standardisation and Liaisons

Start month 1

End month 30


Objectives

WP2 is the key activity for ensuring a broad impact of the project; its main goal is to stimulate and harmonisedissemination of studies, results and evaluations reports about the deployment of IP Network as a Service atNRENs. According to the WP2 goal, it is very important to convince and mobilise the research community aboutthe benefits which IP Networks as a Service could contribute to its investigations and research activities.

In order to ensure that the project investment is effectively exploited, several dissemination activities will carryout: distribution of publicity material, presentations at scientific conferences, workshops, demonstrations atspecific academic events, and so on. Also, this activity includes an exploitation plan comprising the exploitationplans of each partner and the joint marketing plans, determining thus the exploitation phase subsequent to theend of the project.

Another important goal of WP2 is to devote efforts in contributing to standard bodies (OGF, IRTF-NRVGand TMF, for instance), above all in the IaaS topics. We also have a view towards proposing extensions orenhancements of established standards to support the project work.

Finally, liaisons with related initiatives within the research and industry community will also be executed withinthis work package.


T2.1 Dissemination (Start: M1, End: M30, Leader: i2CAT)Participants: i2CAT, HEAnet, NORDUnet, UNI-C, UEssex, TID, TCDThe work to be carried out under this task includes the following items:• Dissemination plan: a plan for all activities about dissemination.• Writing conference/magazine papers: This task will cover the publications of the project results for theconferences and magazines related to the project work.• Demonstrations and presentations: This task will cover the demonstrations and the presentations done inworkshops, scientific events, conferences, etc. The intention is to show to the European research communitywhat MANTYCHORE is, the results achieved during the project, the project state, etc. This way, it is ensured agood dissemination towards the potential project tools users, increasing thus the possibility to do new liaisonswith projects related or interested in MANTYCHORE.• Web presence: A website will be provided where all the project public information will be hosted. This taskcovers the development of this web site and its integration with the project team. Public deliverables andimportant information or results will be publicised in the web, with the objective of having a dissemination toolavailable full time, where anybody can be aware about the state of the project, the work done, the resultsachieved, etc. The web site will have a public area where anybody can access to it, and a private one only forthe people involved in the project.

T2.2 Exploitation (Start: M13, End: M30, Leader: HEAnet)Participants: i2CAT, HEAnet, NORDUnet, UNI-C, UEssex, TID, TCDExploitation is one of the key activities of the project. One of the major goals is to create impact in the Europeansociety and economy. Therefore an exploitation phase is needed where the project tools and services areexploited by the ICT industry. The creation of final products and services by the ICT industry based on



the exploitable results of the project is expected to have a positive impact on both social and economicdevelopments in Europe.The main objectives of this task are:• Deliver a global exploitation plan, where feasible, through collecting project partners individual ones.• Continue to monitor the market situation and assess the business opportunities. The results of this task will befed into the global exploitation plan.• Demonstrate the potential of IP Network as a Service solutions in creating industry business opportunities.• Produce a business plan for the MANTYCHORE software.• European patents: It will carry out a study about the possibility of patent some of the tools or services of theproject.

T2.3 Contribution to standard bodies (Start: M6, End: M30, Leader: NORDUnet)Participants: i2CAT, HEAnet, NORDUnet, UEssexAnalyse and monitor existing and emerging standards that are relevant to the project. Interaction with standardsbodies and fora. Moreover, it will do a continuous effort to contribute in several standardisation groups, above all,in the IaaS area. Some examples of the standardisation groups are: TMF, OGF, RIPE, GLIF, and IRTF-NRVG.

T2.4 Liaisons with relevant research projects (Start: M5, End: M30, Leader: HEAnet)Participants: i2CAT, HEAnet, NORDUnetThis task will include the activities related with clustering and concentration with other related initiatives such asEuropean projects or national research projects expecting to benefit from the project outcomes.

Role of Partners

i2CAT is leading and contributing in T2.1. I2CAT will strongly participate in dissemination activities and also inthe other tasks of the activity: in T2.2 will contribute on defining a good exploitation plan for MANTYCHORE,in T2.3 will collaborate with TMF, OGF and IRTF standardisation groups and finally, in T2.4 will also look forrelevant research projects to liaise.

HEAnet is leading and coordinating this activity and also T2.2 and T2.4. HEAnet will also contribute in the othertasks: in T2.1 will contribute on dissemination trying to publicize papers in some magazine and in conferences,in T2.2 will contribute in the exploitation of MANTYCHORE services, in T2.3 will collaborate with RIPE and GLIFgroups, and finally in T2.4 will contribute looking for liaisons with other research projects.

NORDUnet is leading and coordinating T2.3. They will also collaborate in the other tasks: in T2.1 NORDUnetwill write some papers to be publicized in magazines and conferences, in T2.2 will contribute in the exploitationof MANTYCHORE services and in T2.4 will look for possible research projects interested in MANTYCHOREservices.

UNI-C will contribute in task T2.1 disseminating the results obtained in using the MANTYCHORE tools toperform their research. UNI-C will write some papers and try to publicize them in some magazines andconferences. UNI-C will also participate in task T2.2, contributing to the overall exploitation of the project results.

UEssex will contribute in task T2.1 disseminating the results obtained in using the MANTYCHORE tools toperform their research. UEssex will write some papers and try to publicize them in some magazines andconferences. UEssex will also participate in task T2.2, contributing to the overall exploitation of the projectresults; and in task T2.3, trying to influence MANTYCHORE relevant standards at OGF and ETSI.

TID will contribute in task T2.1 disseminating the results of the study performed about the feasibility of deployingMANTYCHORE services in a commercial environment. Finally, TID will participate in task T2.2, contributingto the overall exploitation of the project results – focusing on the application of MANTYCHORE results in acommercial environment.

TCD will contribute in task T2.1 disseminating the results obtained in using the MANTYCHORE tools to performtheir research. TCD will write some papers and try to publicize them in some magazines and conferences. TCDwill also participate in task T2.2, contributing to the overall exploitation of the project results.





1 I2CAT 1.50

2 NORDUNET A/S 1.50

3 HEANET 1.50

4 UNI-C 1.50

5 UESSEX 1.50

6 TID 1.50

7 TCD 1.50

Total 10.50



Deliverable Title



Nature 62


Delivery date 64

D2.1 Exploitation, dissemination,standardisation and liaison plan 1 1.00 R PU 3

D2.2 Project website 1 2.00 O PU 5

D2.3Report on related research,exploitation and disseminationactivities and planning update

3 3.50 R PU 15

D2.4Report on standards, exploitation anddissemination activities and liaisonwith related initiatives

3 3.50 R PU 30

D2.5 MANTYCHORE software businessplan 1 0.50 R PU 14

Total 10.50


D2.1) Exploitation, dissemination, standardisation and liaison plan: This report identifies and defines the globalplans for exploitation, dissemination, standardisation and liaison activities within the project. This first reportrepresents the agenda and strategy to follow for the coming activities in the project. [month 3]

D2.2) Project website: This deliverable will provide the project community with an efficient public tool forpublishing the results and activities. [month 5]

D2.3) Report on related research, exploitation and dissemination activities and planning update: This report willinclude the dissemination, exploitation, standardisation and liaison activities for the period month 1 to month 15.Moreover, the report will contain an update of the planning delivered in D2.1, if any. [month 15]

D2.4) Report on standards, exploitation and dissemination activities and liaison with related initiatives: Thisdeliverable will include a composition of all the activities developed within this work packaged during the secondhalf of the project. The report will include then the exploitation, dissemination, standardisation and liaisonactivities realised during the last period of the project. [month 30]

D2.5) MANTYCHORE software business plan: During the development of the privately funded MANTICOREII project, the catalan government - through the VALTEC program, reference number VALTEC09-1-0015 -



sponsored the creation of a business plan to exploit the project software. This business plan will be translatedinto english and provided as part of the MANTYCHORE project official documentation. [month 14]





Comments

MS5 First version of the website available 1 1

MS6Related events, projects and standardsidentified. Exploit., standard. and dissem.plan ready

3 3

MS7 Website ready 1 5

MS8 At least two contributions done in workshopsor other public events 3 20

MS9 At least one liaison with other projects orgroups 3 24





Work package number 53 WP3 Type of activity 54 COORD

Work package title Consolidating the User Community and Users Training

Start month 2

End month 21


Objectives

The project user community will be formed by several user groups which represent a subset of the wide rangeof users of research, health and education networks. The project user community will start with a set of 3 usergroups interested in IP Networks as a Service that will start using the project tools when the first training phaseends (month 9). User groups could include EC projects, research groups in universities or research centres,equipment manufacturers and telecommunications research labs or even individuals (e.g. PhD students). It isnecessary and desired to consolidate the user community and expand the use of IP Networks as a Service.

For this reason the project will devote resources in three directions:• Extending the contacts with existing user organisations and projects on an ongoing basis, gatheringrequirements, providing IP networks (using NRENs' e-infrastructure) for their experiments.• To provide the necessary knowledge to users which it will permit to achieve their needs, while at the sametime, it will consolidate and enlarge the user community• Search for new NRENs that are willing to participate in the project for providing IP Networks as a Service on itse-infrastructure and offering them to the User Community.

On the other hand, WP3 also includes training activities for NRENs and the User Community. Even though theproject software is designed to be user-friendly and usable, it requires a training period to ensure a better andefficient use of it.The search for new user groups and NRENs finalises at the end of month 19, because every new user grouphas to be trained in the project tools and services, and there must be a minimum period of time in the projectof using the MANTYCHORE services (in the user groups case) or operating the services (in the NRENs case).Therefore it has decided that the search lasts 18 months (finishing at the end of month 19) and the trainingactivities finish at the end of month 21, leaving 2 months for new user groups or NRENs joining at month 19.


T3.1 Liaisons with new user groups, projects or research centres (Start: M2, End: M19, Leader NORDUnet)Participants: i2CAT, HEAnet, NORDUnetThis task is focused on establishing a strong relationship with new targeted users. This work will start at month2 by liaising with a selected set of potential user groups that could be identified before the start or during theproject.

T3.2 Training Users (Start: M7, End: M9, Start: 19, End: M21 Leader i2CAT)Participants: i2CAT, HEAnet, NORDUnet, UNI-C, UEssex, TCD• T3.2.1 Training NRENs It will be necessary to run training courses for the NRENS. These NRENs will set uptheir MANTYCHORE software. For this reason, this task provides the necessary resources for these trainingcourses: user manuals, support, software, etc.• T3.2.2 Training UNI-C, TCD, and Advanced High Quality Media Services group. The MANTYCHORE softwaredevelopment team will transfer technical knowledge produced in the project to users of the MANTYCHOREservices, by means of training and dissemination activities, including tutorials and demonstration labs. Thetraining will be supported by technical presentations, as well as by course materials to be produced by theproject participants who have gained consolidated expertise in the project’s service activities. Handout will beprovided to the trainees, plus, when relevant existing withe papers, cookbooks and CD images.



Role of Partners

i2CAT is leading and contributing in T3.2 and will also contribute to T3.1. In T3.1 i2CAT will try to put in contactwith new possible end users to use the MANTYCHORE services. In T3.2 i2CAT will be the responsible toelaborate user manuals and to train all the NRENs and virtual research communities that take part in theMANTYCHORE project.

HEAnet will collaborate in both tasks of the activity: in T3.1 HEAnet will try to look for new virtual researchcommunities and new NRENs to form part of the project and deploy or use MANTYCHORE services. In T3.2HEAnet will attend the training courses done by i2CAT in order to be able to deploy MANTYCHORE services intheir e-infrastructure.

NORDUnet is leading and coordinating this activity and also T3.1. In T3.1 NORDUnet will look for new virtualresearch communities and new NRENs to form part of the project and deploy or use MANTYCHORE services. InT3.2 NORDUnet will also contribute attending the training courses done by i2CAT in order to be able to deployMANTYCHORE services in their e-infrastructure.

UNI-C will contribute in task T3.2 attending the training courses done by i2CAT in order to be able to useMANTYCHORE services for their research activities.

UEssex will contribute in task T3.2 attending the training courses done by i2CAT in order to be able to useMANTYCHORE services for their research activities.

TCD will contribute in task T3.2 attending the training courses done by i2CAT in order to be able to useMANTYCHORE services for their research activities.



1 I2CAT 3.00

2 NORDUNET A/S 3.00

3 HEANET 1.50

4 UNI-C 0.50

5 UESSEX 0.50

7 TCD 0.50

Total 9.00



Deliverable Title



Nature 62


Delivery date 64

D3.1 User manuals 1 4.00 R PU 6

D3.2 User community final report 2 5.00 R PU 19

Total 9.00


D3.1) User manuals: This deliverable consists in all the manuals done about the project software and itsdeployment over NRENs, besides the manuals done for the end users. [month 6]



D3.2) User community final report: This deliverable will report the consolidation of the project user community[month 19]





Comments

MS10 First training completed 1 9

MS11 Internal report about the status of the usercommunity 2 10

MS12 User community consolidated 2 19

MS13 Second training completed 1 21





Work package number 53 WP4 Type of activity 54 OTHER

Work package title Software refinement

Start month 2

End month 30


Objectives

This activity will focus on the analysis of the user requirements (from NRENs and virtual research communities)and implement them. The implementation phase will include a subtask to solve the bugs that later can befound when the service will be deployed in an operational environment and used by the NRENs and the virtualresearch communities.

One requirement already requested by the NRENs is to improve MANTICORE II to offer users the possibilityof working also in L1 (optical level) and L2 (Ethernet level) of the OSI model. This capability would allow usersto configure and manage any type of network. Another important goal of this task is to improve the interface forthe end users, so that it is as simple and usable as possible, yet still allows them to fully control an IP network.Ideally, this interface should allow users to specify the configuration of their IP network in a very high level, whichwould be translated to specific actions on the devices by the software implementation.


In order to get robust and reliable software useful for the user, two main tasks can be distinguished to performall the necessary work to improve the MANTICORE II software. The first one focuses on analysing the userrequirements and the second one on implementing them.

T4.1 Requirements Analysis (Start: M2, End: M5, Leader HEAnet)Participants: i2CAT, HEAnet, NORDUnet, UNI-C, UEssex, TCDRequirements analysis encompasses those tasks that go into determining the needs or conditions to meet fora new or altered product, taking account of the possibly conflicting requirements of the various stakeholderssuch as beneficiaries or users. Requirements analysis is critical to the success of a development project.Requirements must be actionable, measurable, testable, related to identified business needs or opportunities,and defined to a level of detail sufficient for system design.Requirements can be functional and non-functional:• Functional requirements explain what has to be done by identifying the necessary task, action or activity thatmust be accomplished. Functional requirements analysis will be used as the top level functions for functionalanalysis.• Non-functional Requirements are requirements that specify criteria that can be used to judge the operation of asystem, rather than specific behaviors.Each NREN and each virtual research community (UNI-C, UEssex and TCD) must elaborate a list of the newfeatures that MANTYCHORE should have, taking into account the features that the MANTICORE II tools hasalready implemented. The new requirements specified will be discussed with the development team and it will bedecided which ones will be implemented and which ones not.Studies reveal that an inadequate attention to Software Requirements Analysis at the beginning of a project isthe most common cause for critically vulnerable projects that often do not deliver even on the basic tasks forwhich they were designed. For this reason all the partners involved in this task must pay special attention to thistask. The development team should work together with the users of the software (NRENs and virtual researchcommunities) in this phase in order to get a very consistent requirements list.

T4.2 Software development: tools integration and refinement (Start: M6, End: M30, Leader i2CAT)Participants: i2CAT



This task focuses on the implementation of the requirements specified in the task above. For the implementationphase the agile methodology called SCRUM will be used. SCRUM is an iterative incremental process ofsoftware development commonly used with agile software development.The main work items initially foreseen to be implemented by this tasks are:• Integration of MANTICORE II results with Argia and Ether• Implementation of NREN improvements (including a certain degree of adaptation to each NREN operationalenvironment)• Implementation of research communities improvements (probably focusing on a simple but powerful userinterface)• Integration with the federated European AAI infrastructure (EduGAIN)This task also focuses on treat the feedback obtained from the NRENs and final users. Following are listed theissues to be done to treat and solve the bugs:• Choose the most appropriate mechanism to report bugs and to suggest improvements.• Bugs resolution: Solve bugs reported by NRENs and virtual research communities, which will be reported usingthe method specified in the subtask above.

Role of Partners

i2CAT is leading and coordinating this activity and also T4.2. In T4.1 will collaborate with all the partnersto elaborate the requirements list. In T4.2 i2CAT will be the developer of the MANTYCHORE software, therequirements listed in T4.1 will be implemented and also bugs reported by users will be solved.

HEAnet is leading T4.1 and coordinating all the partners to define the user requirements list. HEAnet has alreadysuggested the requirement of the integration of MANTICORE II with the IaaS Framework based tools for opticaland Ethernet/MPLS networks.

NORDUnet will contribute on task T4.1 elaborating the user requirements list. NORDUnet will contribute on theuser requirements from an NREN point of view, the requirements will be focused on the GUI use and on thefunctionalities regarding routers and IP networks configuration.

UNI-C will contribute on task T4.1 elaborating the user requirements list. The requirements suggested by UNI-Cwill be from a final user point of view, focused on the configuration and use of IP networks.

UEssex will contribute on task T4.1 elaborating the user requirements list. The requirements suggested byUEssex will be from a final user point of view, focused on the configuration and use of IP networks.

TCD will contribute on task T4.1 elaborating the user requirements list. The requirements suggested by TCD willbe from a final user point of view, focused on the configuration and use of IP networks.



1 I2CAT 28.50

2 NORDUNET A/S 3.00

3 HEANET 1.00

4 UNI-C 2.00

5 UESSEX 2.00

7 TCD 3.00

Total 39.50





Deliverable Title



Nature 62


Delivery date 64

D4.1 Requirements analysis report 3 7.50 R PU 5

D4.2 Software development report 1 32.00 P PU 30

Total 39.50


D4.1) Requirements analysis report: This deliverable includes the list of the user requirements that are going tobe implemented in the task T4.2. These requirements will include the ones collected by NRENs and the onescollected by the virtual research communities previously discussed with the development team. [month 5]

D4.2) Software development report: This deliverable specifies how the requirements have been implemented,which tools have been integrated to other ones and which ones have been refined. This deliverable also includesa prototype of the project tools working with the new requirements implemented. [month 30]





Comments

MS14 Requirements analysis completed 1 5

MS15 Marketplace integrated in IP NetworkServices 1 22

MS16 Zero-carbon virtual infrastructures integratedin IP Network Services 1 27

MS17 Software development completed 1 30





Work package number 53 WP5 Type of activity 54 OTHER

Work package title IP Networks as a Service for Virtual Research Communities

Start month 10

End month 30


Objectives

The main goal of this activity is to deploy the improved MANTYCHORE services into an operationalenvironment, where NRENs have the software installed and offer this new type of service to the virtual researchcommunities.

The improved version of the MANTYCHORE software will be deployed in each NREN and used by the researchusers once WP 4 has implemented all the requirements requested by the NRENs and the virtual researchcommunities (UNI-C, UEssex and TCD). One of the key issues to address in this pre-operational deployment isto define fault resolution procedures so that users, even though they are the ones controlling the infrastructure,do not have to deal with the problem of troubleshooting the network.

During the whole activity TID will be following and analysing the results of the deployment of the MANTYCHOREservices in NRENs and how users use these services. With this information, TID will perform a study to analyseif it would be feasible to deploy MANTYCHORE services in a commercial environment, taking into accounttechnical as well as business parameters.


This activity is divided in two tasks, the first one focuses on deploying the MANTYCHORE services in the twoNRENs and the second one focuses on the use that virtual research communities make of the MANTYCHOREservices.

T5.1 Deployment and operation of MANTYCHORE at NRENs (Start: M10, End M30, Leader NORDUnet)Participants: i2CAT, HEAnet, NORDUnet, TIDThis task will focus on the deployment of MANTYCHORE services in the two NRENs: HEAnet and NORDUnet.At the beginning of the task i2CAT will help both NRENs to install the software and to deploy MANTYCHOREservices in their e-infrastructure; then, NRENs will start offering the services to the virtual research communities.If bugs are found during the deployment phase, all the bugs will be reported to the development team at i2CATto solve them. During this phase improvements can also be suggested for future versions of MANTYCHORE.NRENs will learn the day-to-day details about installing, operating, troubleshooting and maintaining IP NetworkServices provided through MANTYCHORE tools. Of particular interest will be trying to find out the associatedcost to operating IP Network Services, and the improvement in operations efficiency.Finally, TID will study the installation and operational procedures carried out at NRENs and analyse thepossibility of providing IaaS services in commercial operator networks.

T5.2 Using MANTYCHORE services in virtual research communities (Start: M10, End: M30, Leader UNI-C)Participants: i2CAT, UNI-C, UEssex, TCD, TIDThis task will focus on the use of MANTYCHORE services by virtual research communities: UNI-C, UEssex andTCD. At the beginning of the task i2CAT will help these users to install the MANTYCHORE software on theirenvironment and to get everything ready to start using the MANTYCHORE services provided by the NRENs. Ifbugs are found during the deployment phase, all of them will be reported to the development team at i2CAT tosolve them. During this phase improvements can also be suggested for future versions of MANTYCHORE.



The user communities in this task will evaluate what is the added value that NREN services provided through theMANTYCHORE tools. To perform this activity, each user group will compare how beneficial is to perform theirresearch activities using the IP Network Service versus using the services in the current NRENs portfolio.TID will be in close contact with the different research communities, analyse the added value that IP Networksas a Service provides them and use this information to elaborate their study on providing IaaS services in acommercial environment.

Role of Partners

i2CAT will collaborate in task T5.1 and T5.2 helping NRENs to deploy MANTYCHORE services in itse-infrastructure and helping virtual research communities to start using the MANTYCHORE services offered byeach NREN.

HEAnet will collaborate in task T5.1 deploying MANTYCHORE services in its e-infrastructure and offering theservices to TCD. HEAnet will have to provide feedback to i2CAT regarding possible bugs they may found ondeploying MANTYCHORE services and suggesting possible improvements on the software.

NORDUnet is leading and coordinating this activity and the task T5.1. NORDUnet will deploy MANTYCHOREservices in its infrastructure and offering the services to UNI-C. NORDUnet will also have to provide feedback toi2CAT regarding possible bugs they may found on deploying MANTYCHORE services and suggesting possibleimprovements on the software.

UNI-C is leading and coordinating the task T5.2, using the MANTYCHORE services offered by NORDUnet.UNI-C will have to provide feedback to i2CAT regarding possible bugs they may found on using MANTYCHOREservices and suggesting possible improvements on the software.

UEssex will contribute on task T5.2 using the MANTYCHORE services. UEssex will have to provide feedbackto i2CAT regarding possible bugs they may found on using MANTYCHORE services and suggesting possibleimprovements on the software.

TCD will contribute on task T5.1 elaborating the user requirements list. TCD will have to provide feedback toi2CAT regarding possible bugs they may found on using MANTYCHORE services and suggesting possibleimprovements on the software.

TID will contribute in the whole activity observing and analyzing the results of deploying MANTYCHORE servicesin the NRENs and the usage of these services that virtual research communities do. With these results TIDwill elaborate a study to conclude if it would be feasible to deploy MANTYCHORE services in a commercialenvironment.



1 I2CAT 3.00

2 NORDUNET A/S 8.00

3 HEANET 5.00

4 UNI-C 8.00

5 UESSEX 8.00

6 TID 5.00

7 TCD 19.00

Total 56.00





Deliverable Title



Nature 62


Delivery date 64

D5.1 Feasibility of IP Networks as aService in a commercial environment 6 5.00 R PU 20

D5.2Report on IP Networks as a Servicedeployment in NRENs, and its use byvirtual research communities

2 51.00 R PU 30

Total 56.00


D5.1) Feasibility of IP Networks as a Service in a commercial environment: This report also contains the resultsobtained in studying the feasibility of IP Networks as a Service in a commercial environment. Results obtained inNRENs and in virtual research communities will be contrasted and studied in deep to find out the benefits that IPNetworks as a Service could offer to the commercial telecom operators. [month 20]

D5.2) Report on IP Networks as a Service deployment in NRENs, and its use by virtual research communities:This report contains the results obtained in HEAnet and NORDUnet after deploying the service and a list of thereported bugs, suggested improvements and the results obtained in the virtual research communities (UNI-C,UEssex and TCD) after deploying the service. [month 30]





Comments

MS18Internal report of IP Networks as a Servicetools deployed in NRENs and used byresearch communities

2 17

MS19 IP Networks as a Service evaluated inNRENs and virtual research communities 2 30





Work package number 53 WP6 Type of activity 54 RTD

Work package title Infrastructure Resources Marketplace

Start month 2

End month 20


Objectives

This activity will carry out the study, design and simulation of the necessary algorithms for the implementation ofthe MANTYCHORE marketplace mechanism. A marketplace is the best way to announce products from severalvendors and, by means of Internet, to arrive to the maximum number of customers.

Marketplaces enable the automatic negotiation and reservation of resources between users and providers. Themarketplace will provide the capability to automatically select, orchestrate and reserve the best resources for agiven request; taking into account several criteria: the user request, the available resources and policies set byresource owners.

The main idea is to use the marketplace in order to allow the NRENs to announce their own infrastructureas resources of MANTYCHORE services; therefore, users from virtual research communities will be able toaccess resources from several providers. The marketplace will be specifically designed for MANTYCHORE,so only infrastructure resources and IP networks as services will be announced. NRENs will have to usethe MANTYCHORE GUI to abstract the infrastructure to web service resources, and these ones will be theresources announced in the marketplace. On the other hand, customers will get permissions for the resourcesselected and they will be able to access them using the MANTYCHORE software.

Several studies and algorithms must be designed under the marketplace scenario; first of all it is needed toperform a set of studies about how the resources will be published, how the customers will submit the requestsand how the resources will be allocated on the customers. The final study consists in the simulation of themarketplace and the study of its scalability.


The WP6 activity comprises 2 tasks.

T6.1 Infrastructure marketplace mechanisms study and simulation (Start: M2, End: M14, Leader UEssex).Participants: i2CAT, UEssex, TIDThis task focuses on study and design different mechanisms to implement the infrastructure marketplace. Thefollowing studies will be performed:• Resource Publication Mechanism will be designed to allow Infrastructure Providers to publish their resources tothe Marketplace. This design includes appropriate resource abstraction algorithms that can hide technology andinfrastructure specific details of resources and represent resources in a unified format.• Request Submission Mechanism is another necessary mechanism that allows Service Providers to submitresource requests to the Marketplace. It will be needed a design of a hierarchical resource submissionframework that can be extended and used by different Service Providers for submitting resource request withdifferent level of details. Furthermore it will be able to map Quality of Service (QoS) parameters requested byuser into appropriate QoS attributes compatible with Marketplace.• Allocation and Matchmaking mechanism is a set of search engine algorithms of a Marketplace. The searchengine will perform lookup on the available abstracted resources in the Marketplace based on the user request.This includes matchmaking algorithms that can allocate a set of resources from a pool of resources andaccording to predefined QoS constraints. The main objective here is to maximize the pool resource utilisation.



A simulation of the marketplace will be held in order to ensure that it works before integrating with theMANTICORE tools.

T6.2 Implementation of the marketplace prototype (Start: M15, End: M20, Leader i2CAT)Participants: i2CAT, NORDUnet, UEssexThis task profits from the realized studies and implements a system which will create a community for theadvertisement and exchange of resources. This marketplace will implement a prototype of all the featuresintroduced in T6.1. This prototype of the marketplace will provide:• A place to exchange different resources: routers, Ethernet switches, etc.• It will be a meeting point where different users and NRENs can publish their resources and use them. Thismarketplace pretends be a media with others users and NRENs.The prototype implementation will be integrated with the main MANTYCHORE software in T4.2.

Role of Partners

i2CAT is leading T6.2 being the responsible of implementing the necessary algorithms to integrate themarketplace in MANTYCHORE tools. i2CAT will also contribute in T6.1 helping to perform the necessary studiesto implement the marketplace prototype.

NORDUnet will contribute in T6.2 helping the development team in i2CAT to implement the marketplaceprototype.

UEssex is leading and coordinating this activity and leading T6.1. In T6.1 UEssex will perform all the necessarystudies to implement the marketplace and in T6.2 will supervise that the implementation of the prototypeaccomplishes the expectations.

TID will contribute to T6.1 by participating in the marketplace definition. Regarding the huge experience that TIDhas in commercial environments it could be very useful their point of view of the markets.



1 I2CAT 2.50

2 NORDUNET A/S 1.50

5 UESSEX 9.00

6 TID 4.00

Total 17.00



Deliverable Title



Nature 62


Delivery date 64

D6.1 Infrastructure marketplacemechanisms study 5 12.00 R PU 14

D6.2 Implementation of the marketplacereport 1 5.00 P PU 20

Total 17.00




D6.1) Infrastructure marketplace mechanisms study: This deliverable contains the results of studies performed inorder to implement the marketplace and also the results of the simulation. [month 14]

D6.2) Implementation of the marketplace report: Prototype of the infrastructure resources marketplace.This deliverable also contains a report where all the features of the implemented marketplace are listed andexplained. [month 20]





Comments

MS20 Infrastructure marketplace studies completed 5 11

MS21 Infrastructure marketplace simulationscompleted 5 14

MS22 Marketplace prototype implemented 1 20





Work package number 53 WP7 Type of activity 54 RTD

Work package title Zero-carbon emission virtual infrastructures

Start month 7

End month 25


Objectives

MANTYCHORE will start collaborations with GSN (GreenStar Network) project for the integration of its NRENinfrastructures in its test-bed where GSN network is formed by a set of green nodes where each node ispowered by sun, wind, etc. GSN Carbon Measurement Protocol is used for GSN to measure the quantity ofenergy and carbon emission permitted in these nodes allowing for better management. It will be utilized togenerate carbon credits from the reduction of carbon resulting from relocation different network resourcesamong networks and test beds. Relocating these resources could possibly save tons of carbon per year.

The NREN infrastructure will be connected to the GSN network and it will add new resources, asMANTYCHORE resources. Currently MANTYCHORE features allow new possibilities to solve different issues inconfiguration, testing, monitoring, etc:Benefits of the proposed User case studies are• The location of the consortium and its distance from other sources such as the GSN test-bed from Canadaand MANTYCHORE infrastructure at Europe add new interesting user cases to this project. These new usercases analyze how it is possible to move services to computing or networking resources and why its situationand location can influence that choice.• To collaborate to research and create cloud management algorithms making optimal use of theintermittently-available renewable energy sources.The viability and usefulness which will be measured by the degree to which the renewable energy sources canbe utilized. This usefulness will be checked in the different use cases and will specify the best options to reduceemissions and energy• These workflow and goals will be transparent for end users who will not see any difference and will not haveany interruption in their tasks. For an end user, his service will work continuously without any problem


T7.1 Integration between MANTYCHORE and GSN (Start: M7, End: M16, Leader NORDUnet)Participants: i2CAT, HEAnet, NORDUnet, TIDThe main goal of this task is to setup a GSN node which will allow access from varied NREN infrastructures tothe GSN network. To achieve this subtasks are required to carry out:• Analysis of different possibilities to connect the two infrastructures.• Integration of MANTYCHORE physical resources in GSN. It includes all the process of installation of aconnection MANTYCHORE-GSN• To specify requirement and planning of the software integration. It is necessary understand and specify howMANTYCHORE and GSN services will be able to collaborate – both will be using IaaS Framework basedsoftware, so this integration is not foreseen as a big task.• MANTYCHORE services provide facilities to configure routers and interfaces give flexibility thanks to itsIaaS architecture and give a management of logical devices. GSN profits from all these features to improve itsinfrastructure.

T7.2 Testing networks migration (Start: M17, End: M25, Leader HEAnet)Participants: i2CAT, HEAnet, NORDUnet, TID



MANTYCHORE-GSN collaboration has the objective to design necessary experiments and tests whicheventually check the viability of this movement of services (virtual machines (VMs), flexible device configurationsutilities, etc...). Goals to achieve within this task are:• Search and design algorithms which will select different policies and an optimised set of options• Every MANTYCHORE device has an energy expense will be measured using different techniques. Thissubtask will search different possibilities to study the electrical consumption of each device and to integratemeasuring and reporting algorithms into the MANTYCHORE application.• Time is an important dimension in making energy measurements, which will require data capture , logging andhistorical analysis and comparison features• Different options for migrating services are evaluated by conducting trials and experiments to highlight thefull capability of these services. GSN will profit from MANTYCHORE’s architecture to increase the flexibility oftesting and modelling services.• The GEANT Stitching Framework [54] will be extended to characterise and highlight the attributes and energyconsumption parameters to allow for easier integration into emerging solutions.

Role of Partners

I2CAT will participate in T7.1 and T7.2. In T7.1 will contribute on performing the integration between GSN andMANTYCHORE (physical integration between the GSN and the NRENs infrastructure and also the servicesintegration). In T7.2 i2CAT will participate in implementing the necessary algorithms and mechanisms tointegrate the Zero-carbon emissions virtual infrastructures into MANTYCHORE services.

HEAnet is leading and coordinating this activity and T7.2 being the responsible for the joint experimentation onmoving virtual resources based on renewable energy availability. Modifying the GEANT Stitching Frameworkis their responsible and should highlight the most relevant parameters and the interaction of their attributes toassist in the physical implementations. HEAnet will also contribute in T7.1 contributing to the physical integrationbetween MANTYCHORE and GSN infrastructures

NORDUnet is leading T7.1 and will contribute in T7.2. In T7.1 NORDUnet will focus in performing the physicalintegration between MANTYCHORE and GSN infrastructures and also the services integration. Finally, in T7.2NORDUnet will be the responsible for ensuring that the algorithms are optimised to perform network migrations.

TID will contribute in T7.1 offering part of its infrastructure to integrate MANTYCHORE and GSN. TID will alsocontribute in T7.2 performing some experiments over part of its infrastructure to ensure that the migration ofentire virtual networks works correctly.



1 I2CAT 5.00

2 NORDUNET A/S 5.00

3 HEANET 2.50

6 TID 2.00

Total 14.50



Deliverable Title



Nature 62


Delivery date 64

D7.1 Integration between MANTYCHOREand GSN report 3 7.00 R PU 16





Deliverable Title



Nature 62


Delivery date 64

D7.2 Networks migration tests report 2 7.50 R PU 25

Total 14.50


D7.1) Integration between MANTYCHORE and GSN report: This deliverable will provide all relevantinformation related with the new installed resources. It includes all the information to the connection betweenMANTYCHORE-GSN including information about physical and software components. It is intended to be thecomprehensive reference for building MANTYCHORE-GSN infrastructure [month 16]

D7.2) Networks migration tests report: All experimental algorithms are presented in this deliverable, which detailsall the algorithms evaluated. Final experimental conclusions will show the viability of those algorithms selected.As each algorithm is described, full details of implementation features, and their interaction are fully explained (ofboth the optimal and other algorithms which were researched). [month 25]





Comments

MS23 Physical networks integrated 3 11

MS24 Services integrated 1 16

MS25 Tests performed 2 25

WT4:List of Milestones



List and Schedule of Milestones

Milestonenumber 59 Milestone name WP number 53 Lead benefi-

ciary numberDelivery datefrom Annex I 60 Comments

MS1

All projectmanagementprocedures in placeand operational

WP1 1 1

MS2First project reviewsuccessfullycompleted

WP1 1 15

MS3Second projectreview successfullycompleted

WP1 1 30

MS4All projectdocumentationcompleted

WP1 1 30

MS5 First version of thewebsite available WP2 1 1

MS6

Related events,projects andstandards identified.Exploit., standard.and dissem. planready

WP2 3 3

MS7 Website ready WP2 1 5

MS8

At least twocontributions done inworkshops or otherpublic events

WP2 3 20

MS9At least one liaisonwith other projects orgroups

WP2 3 24

MS10 First trainingcompleted WP3 1 9

MS11Internal report aboutthe status of the usercommunity

WP3 2 10

MS12 User communityconsolidated WP3 2 19

MS13 Second trainingcompleted WP3 1 21

MS14 Requirementsanalysis completed WP4 1 5

MS15Marketplaceintegrated in IPNetwork Services

WP4 1 22

WT4:List of Milestones


Milestonenumber 59 Milestone name WP number 53 Lead benefi-

ciary numberDelivery datefrom Annex I 60 Comments

MS16

Zero-carbon virtualinfrastructuresintegrated in IPNetwork Services

WP4 1 27

MS17Softwaredevelopmentcompleted

WP4 1 30

MS18

Internal reportof IP Networksas a Servicetools deployedin NRENs andused by researchcommunities

WP5 2 17

MS19

IP Networks as aService evaluatedin NRENs andvirtual researchcommunities

WP5 2 30

MS20Infrastructuremarketplace studiescompleted

WP6 5 11

MS21

Infrastructuremarketplacesimulationscompleted

WP6 5 14

MS22Marketplaceprototypeimplemented

WP6 1 20

MS23 Physical networksintegrated WP7 3 11

MS24 Services integrated WP7 1 16

MS25 Tests performed WP7 2 25

WT5:Tentative schedule of Project Reviews



Tentative schedule of Project Reviews

Reviewnumber 65

Tentativetiming

Planned venueof review Comments, if any

RV 1 15 Barcelona

RV 2 30 Dublin

WT6:Project Effort by Beneficiary and Work Package



Indicative efforts (man-months) per Beneficiary per Work Package

Beneficiary number andshort-name WP 1 WP 2 WP 3 WP 4 WP 5 WP 6 WP 7 Total per Beneficiary

1 - I2CAT 10.00 1.50 3.00 28.50 3.00 2.50 5.00 53.50

2 - NORDUNET A/S 0.00 1.50 3.00 3.00 8.00 1.50 5.00 22.00

3 - HEANET 0.00 1.50 1.50 1.00 5.00 0.00 2.50 11.50

4 - UNI-C 0.00 1.50 0.50 2.00 8.00 0.00 0.00 12.00

5 - UESSEX 0.00 1.50 0.50 2.00 8.00 9.00 0.00 21.00

6 - TID 0.00 1.50 0.00 0.00 5.00 4.00 2.00 12.50

7 - TCD 0.00 1.50 0.50 3.00 19.00 0.00 0.00 24.00

Total 10.00 10.50 9.00 39.50 56.00 17.00 14.50 156.50

WT7:Project Effort by Activity type per Beneficiary



Indicative efforts per Activity Type per Beneficiary

Activity type Part. 1I2CAT

Part. 2NORDUNE

Part. 3HEANET

Part. 4UNI-C

Part. 5UESSEX

Part. 6TID

Part. 7TCD Total

1. RTD/Innovation activities

WP 6 2.50 1.50 0.00 0.00 9.00 4.00 0.00 17.00

WP 7 5.00 5.00 2.50 0.00 0.00 2.00 0.00 14.50

Total Research 7.50 6.50 2.50 0.00 9.00 6.00 0.00 31.50

3. Consortium Management activities

WP 1 10.00 0.00 0.00 0.00 0.00 0.00 0.00 10.00

Total Management 10.00 0.00 0.00 0.00 0.00 0.00 0.00 10.00

Work Packages for Coordination activities

WP 2 1.50 1.50 1.50 1.50 1.50 1.50 1.50 10.50

WP 3 3.00 3.00 1.50 0.50 0.50 0.00 0.50 9.00

Total Coordination 4.50 4.50 3.00 2.00 2.00 1.50 2.00 19.50

4. Other activities

WP 4 28.50 3.00 1.00 2.00 2.00 0.00 3.00 39.50

WP 5 3.00 8.00 5.00 8.00 8.00 5.00 19.00 56.00

Total other 31.50 11.00 6.00 10.00 10.00 5.00 22.00 95.50

Work Packages for Support activities

Total Support 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00

Total 53.50 22.00 11.50 12.00 21.00 12.50 24.00 156.50

WT8:Project Effort and costs



Project efforts and costs

Estimated eligible costs (whole duration of the project)Benefi-ciary

number

Beneficiaryshort name Effort (PM) Personnel

costs (€)Subcontracting

(€)Other Direct

costs (€)

Indirect costsOR lump sum,

flat-rate orscale-of-unit (€)

Total costsRequested EUcontribution (€)

1 I2CAT 53.50 243,268.00 0.00 23,000.00 166,118.00 432,386.00 402,843.00

2 NORDUNET A 22.00 171,600.00 0.00 12,500.00 95,837.00 279,937.00 258,143.00

3 HEANET 11.50 92,253.00 0.00 11,500.00 62,251.00 166,004.00 131,895.00

4 UNI-C 12.00 81,360.00 0.00 21,500.00 61,716.00 164,576.00 153,679.00

5 UESSEX 21.00 130,200.00 0.00 26,000.00 93,720.00 249,920.00 215,318.00

6 TID 12.50 80,600.00 0.00 10,000.00 60,049.00 150,649.00 114,224.00

7 TCD 24.00 54,072.00 0.00 21,500.00 45,342.00 120,914.00 114,816.00

Total 156.50 853,353.00 0.00 126,000.00 585,033.00 1,564,386.00 1,390,918.00

1. Project number

The project number has been assigned by the Commission as the unique identifier for your project. It cannot be changed.The project number should appear on each page of the grant agreement preparation documents (part A and part B) toprevent errors during its handling.

2. Project acronym

Use the project acronym as given in the submitted proposal. It cannot be changed unless agreed so during the negotiations.The same acronym should appear on each page of the grant agreement preparation documents (part A and part B) toprevent errors during its handling.

53. Work Package number

Work package number: WP1, WP2, WP3, ..., WPn

54. Type of activity

For all FP7 projects each work package must relate to one (and only one) of the following possible types of activity (only ifapplicable for the chosen funding scheme – must correspond to the GPF Form Ax.v):

• RTD = Research and technological development (incl. scientific coordination applicable for Collaborative Projects andNetworks of Excellence

• DEM = Demonstration - applicable for collaborative projects

• MGT = Management of the consortium - applicable for all funding schemes

• OTHER = Other specific activities, applicable for all funding schemes

• COORD = Coordination activities – applicable only for CAs

• SUPP = Support activities – applicable only for SAs

55. Lead beneficiary number

Number of the beneficiary leading the work in this work package.

56. Person-months per work package

The total number of person-months allocated to each work package.

57. Start month

Relative start date for the work in the specific work packages, month 1 marking the start date of the project, and all other startdates being relative to this start date.

58. End month

Relative end date, month 1 marking the start date of the project, and all end dates being relative to this start date.

59. Milestone number

Milestone number:MS1, MS2, …, MSn

60. Delivery date for Milestone

Month in which the milestone will be achieved. Month 1 marking the start date of the project, and all delivery dates beingrelative to this start date.

61. Deliverable number

Deliverable numbers in order of delivery dates: D1 – Dn

62. Nature

Please indicate the nature of the deliverable using one of the following codes

R = Report, P = Prototype, D = Demonstrator, O = Other

63. Dissemination level

Please indicate the dissemination level using one of the following codes:

• PU = Public

• PP = Restricted to other programme participants (including the Commission Services)

• RE = Restricted to a group specified by the consortium (including the Commission Services)

• CO = Confidential, only for members of the consortium (including the Commission Services)

• Restreint UE = Classified with the classification level "Restreint UE" according to Commission Decision 2001/844 andamendments

• Confidentiel UE = Classified with the mention of the classification level "Confidentiel UE" according to Commission Decision2001/844 and amendments

• Secret UE = Classified with the mention of the classification level "Secret UE" according to Commission Decision 2001/844and amendments

64. Delivery date for Deliverable

Month in which the deliverables will be available. Month 1 marking the start date of the project, and all delivery dates beingrelative to this start date

65. Review number

Review number: RV1, RV2, ..., RVn

66. Tentative timing of reviews

Month after which the review will take place. Month 1 marking the start date of the project, and all delivery dates being relativeto this start date.

67. Person-months per Deliverable

The total number of person-month allocated to each deliverable.

FP7-261527 MANTYCHORE Combination of CP & CSA

Description of Work 13 April 2010 Page 1 of 131

!"#$%&'%()*$+',$&!-(%*./(01$)2&32(00$!(4&',$0*+*(5&65*7(5+2*1$08*$9(*7&,&:&34$+',$;&2<$):+' ############################################################################################################################################################# =!

"!#$#!%&'%()*!+',!)-&.(%*!&".(%*/0(1$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$2!!"#$#$#"%&'()*+,-."/01023 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$4!!"#$#$5"61781"92::;30<= $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$>!B 1.1.3 Design and Architecture of MANTYCHORE services $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$#5!!"#$#$?"%&'()*+,-.",@A79<0B71"C3D"<79E309CF"192G7 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$#H!!"#$#$H"-7F7BC397"2I"%&'()*+,-."J0<E"<E7"J28K"G82L8C:"2@A79<0B71$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$#M!

"!#$#$3!4(+15-+"6(!-(156*1 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$78!"!#$7!)-&9-(11!"(:&',!*;(!1*+*(!&<!*;(!+-*$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$77!

!"#$5$#"N82A79<"@C17F037$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$55!!"#$5$5"%&'(O*,-."0332BC<0231$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$54!!"#$5$4"O3I8C1<8;9<;87"C1"C"P78B097 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$54!!"#$5$?"ON"'7<J28K"C1"C"P78B097$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$5Q!!"#$5$H"O3I8C1<8;9<;87"%C8K7<GFC97$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$45!!"#$5$>"N82B0D7"ON"37<J28K1"C1"C3"2G78C<023CF"178B097$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$4H!!"#$5$Q"N78I28:C397"R"-717C89E"03D09C<281$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$4>!

"!#$2!1=*!4(*;&,&6&9:!+',!+11&%/+*(,!>&-?!)6+'$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$2@!!"#$4$#",B78CFF"P<8C<7L="2I"<E7"J28K"GFC3 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$4Q!!"#$4$5"'7<J28K03L"&9<0B0<071"C3D"C11290C<7D"J28K"GFC3 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$4S!!"#$4$4"P78B0971"&9<0B0<071"C3D"&11290C<7D"T28K"NFC3 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$H?!!"#$4$?"U203<"-717C89E"&9<0B0<071"C3D"&11290C<7D"T28K"NFC3 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$>H!!"#$4$H",B78CFF"1<8C<7L="C3D"L7378CF"D71980G<023$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$QH!!"#$4$>"(0:03L"2I"J28K"GC9KCL71"C3D"<E708"92:G2373<1 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$M4!

!>#$.9):(9('*+*.&' ################################################################################################################################ ?@!"!7$#!4+'+9(4('*!1*-5%*5-(!+',!)-&%(,5-(1 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$A@!

!"5$#$#",8LC301C<023"1<8;9<;87$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$MQ!!"5$#$5",G78C<0231 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$MS!

"!7$7!"('(</%/+-/(1 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$B7!!"5$5$#"!737I090C8="#V"W;3DC90X"05*&("YO5*&(Z $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$S5!!"5$5$5"!737I090C8="5V"+.&37<"Y+.&37<Z $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$S?!!"5$5$4"!737I090C8="4V"',-[637<"Y',-[637<Z $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$SH!!"5$5$?"!737I090C8="?V"[73:C8K\1"O(]*73<78"I28"6DDC337F17"2L"W281K303L"Y6'O]*Z $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$S>!!"5$5$H"!737I090C8="HV"630B7810<="2I".117^"Y6.117^Z $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$SQ!!"5$5$>"!737I090C8=">V"(7F7IX309C"O3B71<0LC90X3"="[71C882FF2"Y(O[Z $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$SS!!"5$5$Q"!737I090C8="QV"(8030<="*2FF7L7"[;@F03"Y(*[Z$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$#_#!

"!7$2!%&'1&-*/54!+1!+!>;&6( $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$#87!!"5$4$#"`;CF0<="2I"<E7"923128<0;: $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$#_5!!"5$4$5"P;@]923<8C9<03L$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$#_H!!"5$4$?"(E08D"GC8<071$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$#_>!!"5$4$H",<E78"92;3<8071 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$#_M!!"5$4$>"&DD0<023CF"GC8<3781 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$#_S!

"!7$C!-(1&5-%(1!*&!"(!%&44/**(,$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$#8B!



!"5$?$#".*"923<80@;<023"23"%C3CL7:73<a"*228D03C<023a"-(["C3D",<E78"C9<0B0<071 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$##_!!"5$?$5".II28<"D01<80@;<023"03"7C9E"C9<0B0<=$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$##_!!"5$?$4"NC8<3781"03]K03D"923<80@;<0231$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$###!!"5$?$?".II28<1"I28"<E7"I;FF"D;8C<023"2I"<E7"G82A79<$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$##5!

!=#$.9)+%* ################################################################################################################################################""A!"!2$#!1*-+*(9/%!/4)+%*$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$##C!

!"4$#$#"P<7G1"<EC<"J0FF"@7"377D7D"<2"@803L"C@2;<"<E717"0:GC9<1 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$##Q!!"4$#$5"&DD7D"BCF;7"2I"J28K03L"C<"<E7".;82G7C3"F7B7F $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$##M!!"4$#$4"O:GC9<"<2"2<E78"8717C89E"C9<0B0<071 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$##S!!"4$#$?"&11;:G<0231"C3D"87F7BC3<"7^<783CF"IC9<281"<EC<"D7<78:037"0:GC9< $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$#5_!

"!2$7!)6+'!<&-!*;(!51(-!+',!,/11(4/'+*/&'!&<!<&-(9-&5',$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$#78!!"4$5$#"[0117:03C<023"&9<0B0<071 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$#5_!!"4$5$5".^GF20<C<023"GFC3"I28";17"2I"G82A79<"871;F<1 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$#5#!!"4$5$4"P<C3DC8D01C<023"C9<0B0<071$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$#5H!!"4$5$?"%C3CL7:73<"2I"O3<7FF79<;CF"N82G78<=a"b32JF7DL7"c"2<E78"87FC<7D"C9<0B0<071 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$#5>!

"!2$2!%&'*-/"5*/&'!*&!1&%/&D(%&'&4/%!/4)+%*1 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$#73!

2(6(2('%(0 ###############################################################################################################################################">B!



!"#$%&'()*+$,'-$&./)(+01)23$*4&54)22$.)6&'-$2+,+)7&87+9)7,4+3$:;<$=)+9&-&>&56$,'-$?&4@$*>,'$

!"#$#"%&'()*+",'-"*.&/)(+"&0/)(+12)3"

!"#$#$#"45678%9:;<"=131&'"

During the last years, the requirement of flexible, dynamic and application driven networks has become a key topic in the emerging e-science community. Usually, configuring the whole network can lead to tedious situations, which are increased when there are several networks involved. Thus, easy, smooth, and transparent configurable networks support an important advantage over other projects aiming at similar objectives. At the same time, the new added network management layer is able to provide new features, which will cover all the possibilities of configurations in IP networks.

MANTYCHORE will follow the Infrastructure as a Service (IaaS) paradigm to enable National Research and Education Networks (NRENs) and other e-Infrastructure providers to enhance their service portfolio by building and deploying software and tools to provide infrastructure resources like routers, switches, optical devices, and IP networks as a service to virtual research communities.

This service follows the IaaS paradigm, consisting on offering remote access and control of infrastructure elements to third party organisations through software web services. By using IaaS services these organisations can control the remote infrastructure as if they owned it and be billed either per use or based on a monthly fee, promoting the reuse of existing infrastructure and avoiding the purchase of new devices on the provider and customer sites. IaaS also provides a new level of flexibility to the e-Infrastructure operators: their infrastructure can scale up or down following its customers’ needs, therefore minimizing the cost of operating the infrastructure (both the capital and the operational expenditures).

Typically, three user roles can be identified in the IaaS scenario:

• Infrastructure Provider: The infrastructure owner. This user can assign permissions to the infrastructure resources he owns so that external users can control it. Infrastructure instances can be either physical (e.g. a physical router) or virtual (e.g. a logical router). In the MANTYCHORE case, NRENs are the Infrastructure Providers, offering their infrastructure to user communities.

• Service Provider or Virtual Operator: This user can harvest infrastructure instances from one or more Infrastructure Providers and integrate them into his management domain (e.g. he can integrate several routers into an IP network). He can also act as an Infrastructure Provider and reassign the permissions on “his” infrastructure instances so that other Service Providers can control them (it is a recursive process). He normally uses the infrastructure instances of his domain to provide some kind of service to end users (e.g. an IP Network service). In the



MANTYCHORE scenario, an international community of researchers could create a virtual organisation with their own dedicated IP network (built using resources from different NRENs). One partner of this international research community would adopt the role of the “Service Provider” – typically the leader of the testbed Work Package in a European project, for example.

• End User: Uses the services offered by the Virtual Operator. These users belong to a virtual community that receives several infrastructure resources and creates one or more IP Networks out of them. Users are empowered to change some attributes of the IP network service (such as internal routing, IP addressing, peering, create circuits between endpoints, firewalls), but wouldn’t be able to modify the number of resources in the network. In any case, it would be their virtual operator the one controlling the permissions of each individual user (hence the definition of different user profiles is possible).

However, the flexibility provided by IaaS comes at the cost of increased management complexity; therefore IaaS management solutions that keep track of permissions, infrastructure allocation, usage and monitoring are of key importance to fully realise the IaaS advantages. Even though a few IaaS commercial solutions exist (mainly Amazon EC2 and S3 [24], BlueLock [25]), they mostly focus on providing virtual machines (computing) and storage on demand, so MANTYCHORE tools and services are an important and complementary innovation within the IaaS landscape.

IP Network as a Service (IP Network Service) is seen as a key enabler of the flexible and stable e-Infrastructures of the future. Today a myriad of tool prototypes to provide point-to-point links to researchers have been developed (AUTOBAHN [12], Harmony [17], G2MPLS [19], and G-Lambda [20]). These tools, while providing high bandwidth pipes to researchers only address one side of the problem. Researchers that want to create a virtual community to address scientific problems are still connected to each institution’s networks, and it is a hard problem to directly connect them with high bandwidth pipes because it causes a number of issues such as security or routing integrity. One of the ways of efficiently solving this problem is to create a logically separated IP network (on top of the high bandwidth pipes), or by using separate instances of virtualised routers, or a combination of both, and dedicating it to the virtual research community. In order to maximize the flexibility and convenience of this IP Network Service, the users of the virtual community should be able to modify the characteristics of their IP network by themselves (such as the addressing, dynamic routing protocols, routing policies, quality of service and so on).

The main objective of the MANTYCHORE project is to allow NRENs to provide an IP Network Service to the research communities they serve: HEAnet and NORDUnet will deploy and operate it as a pre-operational service. MANTYCHORE tools that enable the NRENs to manage and operate the IP Network Service will be deployed individually over the e-Infrastructure of each NREN. Initially three research communities will benefit from the IP Network Service: the Danish Health Data Network, the British Advance High Quality Media Services and the Irish Grid effort.

MANTYCHORE vision realises the supply of an IP Networks as a Service over the NRENs e-Infrastructure; enabling the users belonging to a research community to get permissions over routers,



switches, optical devices and IP networks for the benefit of their research activities, enhancing the quality of the tools available for the European research and increasing the research capabilities and participation of researchers.

MANTYCHORE users will be able to get infrastructure resources (from one or several NRENs), and configure/manage them as if they were the owners. The IP Network Service provides the following features:

• Infrastructure provisioning service:

o Layer 3: users will be able to get management permissions over physical or logical routers, and configure their properties depending on the permissions. Both IPv6 and IPv4 will be supported.

o Layer 2: users will be able to get permissions over Ethernet and MPLS (Layer 2.5) switches, and configure different services.

o Layer 1: users will be able to get permissions over optical devices like optical switches, and configure some properties of its cards and ports.

• Connectivity provisioning service: NRENs will be able to offer to its users a connectivity service based on configuring IP networks, Ethernet networks and point-to-point optical links.

!

Fig. 1 MANTYCHORE vision

The picture above shows two user groups getting resources from NRENs using MANTYCHORE services. Each user group has its own MANTYCHORE server, managed by a virtual operator. Each MANTYCHORE user has its own IP Network managed through the MANTYCHORE server, the place from where resources assigned to each user are accessed. Once one resource is assigned to the IP



slice, the user will be able to do any operation allowed by the permissions he has been granted. Each resource has permissions that define what you can do with it. For example an Infrastructure Provider may assigns a router instance to a user, but not giving him permissions to configure the external routing, so this user will be able to access and manage the router instance but won’t be allowed to modify BGP configurations.

Another important issue is that MANTYCHORE allows the creation of IP networks using infrastructure resources placed in several countries, removing the barriers of distance. So, one user could make an IP network with one router hosted in Ireland, another hosted in Denmark and another in Spain.

The MANTYCHORE project doesn't aim to deploy a new network infrastructure to achieve its objectives. The main goal of the MANTYCHORE project is providing the MANTYCHORE services over the NRENs e-Infrastructure, thus leveraging the existing investment in e-Infrastructures.

However, MANTYCHORE users will be able to get and use infrastructure resources from several NRENs, integrating all of them in the same management domain. There it will be available to participate in one or more IP networks composed by resources aggregated from several NRENs. Hence the infrastructure available to MANTYCHORE users is scalable; any organisation could offer its resources to MANTYCHORE users by just deploying the MANTYCHORE tools over its infrastructure.

IP Network as a Service is implemented by means of the MANTYCHORE software, a web-services based tool that simplifies the management and configuration of routers, switches, optical devices and IP networks. The MANTYCHORE software will be used by Infrastructure Providers, Service Providers and end users because it is used to both assign infrastructure to third parties and to get them, always in a remote way.

!"#$#$>"?3).3"(&@@A'1+B""

The MANTYCHORE project will serve a user community that uses and takes benefit of MANTYCHORE services offered by the NRENs.

User groups must determine the activities that they will perform using MANTYCHORE services, and produce an evaluation report at the end of the project about how MANTYCHORE services have been useful for its research activities. As MANTYCHORE deployment will be a pre-operational activity with real users, it will be mandatory to receive feedback from them to improve the MANTYCHORE services and correct the bugs that could appear. It is not a pilot phase to correct some bugs, it is an evaluation that determines whether the MANTYCHORE services are useful for each particular research community. When the pre-operational phase is successful, the service can be role-out on an operational level to a large community. Each user group will perform different activities and use MANTYCHORE services for different goals. This diversification of research activities in the MANTYCHORE project is interesting, because the evaluation will be better.



The initial user community in MANTYCHORE is formed by three research user groups, where each user group will use individually the MANTYCHORE services for its own interests. These three user groups include the Danish HDN (Health Data Network), the British UHDM (Ultra High Definition Media) group, and the Irish Grid network. Part of the project effort will be dedicated to increase the provider (NREN, commercial) and user community, by contacting new research groups and presenting them the available project ideas and results.

!"#$#$%$#"&'(")*+,-'".(*/0'")*0*"1(02345"

The Danish Health Data Network has existed and is in operation since 2003. Today, all hospitals, all pharmacies, all local authorities, 80% of specialized doctors and most vendors, laboratories etc., are connected to this network. It enables clients to communicate with service providers in the field of health care in a simple, secure, fast and manageable way.

The technology behind this network – an advanced Connection Agreement System – was developed by UNI-C for MedCom, which is a co-operative venture between authorities, organisations and private firms linked to the Danish healthcare sector. The Connection Agreement System enables bilateral agreements between each party in the network. Furthermore, complete audit trail facilities are available. The solution also provides, at any moment, a comprehensive overview of approved connection agreements between parties, and a protection against unauthorized activities. In this way the connection agreement system makes it possible for organisations connected to the Danish Health Data Network to easily and safely exchange data and facilitate services.

Fig. 2 The Connection Agreement System

Technically, the Danish Health Data Network consists of a group of regional routers/gateways and a central hub, which is a cluster of routers, through which all traffic between the different institutions is routed (see Figure 2 above). The Connection Agreement System communicates with the central routers to manage the filter rules that block out irrelevant or hostile data traffic. To be connected to the Danish Health Data Network, stakeholders must either establish:

• a VPN connection from their own secure networks to the Health Data Network hub,



• or have a fixed high capacity connection directly to the hub (see Illustration 2 below).

As of November 2009, there are 94 VPN connections and 12 fixed closed lines connected to the central hub of the Danish Health Data Network and 3076 bilateral agreements.

Fig. 3 The Danish Health Data Network hub and the Connection Agreement System

Over and above an easy-to-use interface to manage the agreements, the security function in the Danish Health Data Network is a key component. It provides a basic access control between the individual systems of the institutions connected to the network hub, in addition to the locally implemented security policy. The administration of connection agreements is handled by an advanced web-based agreement system, which enables the data provider (service) and the data user (client) to create, authorize and maintain agreements made by the two parties, with information regarding involved organisations, appointed contact persons, services which may be accessed by particular clients and which protocols are used. Information about the individual participants is initially validated by the organisations in charge of the system, before new organisations and user accounts are set up in the Connection Agreement System. The information available to the parties offers an easy overview of available services as well as the creation and maintenance of connections agreed upon.

When a new institution is registered in the agreement system, it is assigned a small block of Health Data Network IP addresses, which is routed only within this network, and initially, nothing at all can be accessed through the system. After this, it is up to the local administrator to register agreements in the agreement system, which itself can be accessed on the open Internet protected by an SSL certificate. After an agreement has been concluded via the web-based interface, it is forwarded electronically to both sides of the communication for acceptance in the Agreement System before the connection is opened. Every 10 minutes the approved agreements in the Connection Agreement System are transferred automatically to routers in the form of Access Control Lists allowing traffic between parties at the Danish Health Data Network IP address level. The key advantages of this are:

• Everybody can find the services they need – and each other.

• The need for administering a huge number of VPN tunnels is eliminated.



• The documentation of who ordered a connection and how long it is supposed to exist is always available and up-to-date.

• The security administration is simplified and offers an overview of openings in the firewall at the institution level.

• There is complete administrative control of approval procedures for new organisations.

Summing up, the HDN (Health Data Network) is formed by different medical research centres in Denmark, Sweden and Spain. They exchange information about research results through a network provided by UNI-C, so they need high bandwidth and secure connections; the network is changing continuously because new research medical centres. This alliance would be provided with an IP network, entirely for their own, to perform their research, so using the MANTYCHORE tools they could configure an IP network as they wish.

For the Danish Health Data Network, MANTYCHORE provides a third solution to connect to the central hub, along with VPNs and fixed high capacity connections. One of the great advantages of this solution is that it enables to use other infrastructures, doesn’t require the installation of new hardware, but still is satisfying in terms of security and integrity of the exchanged data.

Among other things, it will benefit the users of the Health Data Network who are also connected to the Danish National and Research Education Network (NREN) – Forskningsnettet.

Benefits of using MANTYCHORE services:

• Provide hospitals higher capacity connections

• Satisfy the security requirements

• Low cost in comparison with other technologies such as MPLS

• Optimize the use of the research infrastructure

• Possibility for further IP networks between partners interested in health

Furthermore, MANTYCHORE enables fast set-up procedures. Today, connections to the hub typically take a day to set up. At the international level, the same benefits apply.

During the project, two use cases showing the different aspects of the benefits of MANTYCHORE will be carried out: one in Denmark and one abroad (could be in Sweden, Spain or Lithuania). There will be four phases per use case: i) design of the specific solution for the implementation of MANTYCHORE in this context; ii) set-up and test, iii) network in production with support and iv) evaluation with statistics over number of users, data exchanged and others.

!"#$#$%$%"678*+9(7".,:'";<*/,0=">(7,*"?(48,9(-"<0,/,-,+:">61&@ABCD"EFG"<-("9*-(H",IJ/(I(+0(7"K="

FD--(LM"

Video technology is currently experiencing rapid progress, combining high-resolution video and features that allow for enhanced user experience. Considering the enormous popularity of IP with



regards to applications such as IPTV, peer-to-peer video streaming, video on demand, video conferencing etc, there is a great demand of using the existing IP infrastructure to transport emerging media. However, HD (high definition) video streaming over IP "best effort" networks is not possible without a substantial deterioration of the quality of service. Today, in order to support this type of applications, the network operators such as NRENs must rely on a dedicated parallel network that typically requires a separate routing infrastructure to be provided.

MANTYCHORE will allow a network operator to provision multiple IP networks over a single infrastructure. The routing policy of each is independent, and the robustness of protection between the instances is a factor of the implementation of logical routers in the underlying equipment. MANTYCHORE will allow many of these logical networks to be provisioned and managed in a scalable way, so that immediate requirements for advanced IP services such as those required by HD, 3D and beyond media and visualisation applications can be met with an NREN’s core equipment, getting full advantage of the resilience and advanced services available in the main network. We envisage the following use cases: Adaptable Distribution of Pre-recorded Content

1. The pre-recorded event (concert) is streamed to two venues, a high and a low-end venue. The high-end venue is equipped with a cluster of projectors (UEssex) delivering an ultimate immersive viewing experience to a large group of people (prime network service). The high-end venue may also be configured into an ultra-wide view angle display environment for enhanced immersion.

2. The low-end venue is a room-sized environment with a number of plasma screens (i2CAT) - (high quality service).

3. In addition, the content will be accessed in a personalize way through individual desktop. In this case, improved immersion will be supported by virtual navigation functionalities (normal IP service as a benchmark)

4. Sound: We envisage an up to 100-person audience immersive remote audio experience (high quality service)

3D Live Streaming over IP

This use case focuses on broadcasting (i.e. point-to-multipoint transmission) high definition signals with dynamic selection of views. The implications of this application are likely to result in a fundamental transformation to the way public events are broadcasted and experienced. In this use case, we will support streaming of a live event, for instance a medical procedure, captured with Iconix cameras. Captured essence and metadata are encoded by Intopix JPEG 2000 and transmitted to remote stereo-capable locations to be shown (e.g., UEssex and Cardiff). The use case will support:

• full symmetric streaming between venues;

• direct interaction between participating groups of audience



The use of such individual and collective interaction concepts will allow novel, compelling experiences, blurring the boundaries between theatre, performance, games, and cinema and getting the spectators involved and immersed well beyond the “passive” consumption of content today.

Fig. 4 Use Case configurations

!"#$#$%$N"BO-A(+04(",+,0,*0,8("E&A)M"

For MANTYCHORE, the Grid-Ireland OpsCentre [51] at TCD proposes a use case related to the marriage of grid and cloud computing. The OpsCentre manages the Irish grid on behalf of Grid-Ireland, which is the Irish National Grid Initiative (NGI) and a full member of the European Grid Infrastructure (EGI) Council.

Grid-Ireland operates an independent national grid, integrated within the European grid infrastructure. It manages top-level national grid services, in addition to top-level international grid services for some international virtual organisations (VOs). It has an integrated and consistent deployment architecture, with a core infrastructure of fully virtualised “grid gateways” in 17 academic institutions in Ireland. The OpsCentre employs fabric management tools to automate deployment and configuration of middleware on these gateways and on the top-level services. It has in-depth expertise in grid middleware, and has long experience in testing, certification and deployment of grid services. It has been working on interoperability since 2004, and also now on bridging to multiple clouds.



The OpsCentre will explore the provision of a distributed federated cloud using MANTYCHORE to provide a virtual private network domain. To do this it will develop a prototype “cloud layer” for Grid-Ireland, hosted as virtual machines (VMs) on each of 6 larger grid gateways interconnected by the MANTYCHORE network, with a slice of each gateway’s computing resources aggregated into the cloud. The OpsCentre will then explore how to exploit that cloud:

• One firm use case is that the cloud VMs on the MANTYCHORE network be configured as grid compute nodes (e.g. gLite or Globus GT4 [46] worker nodes), and be managed as a federated cloud-based cluster through a gatekeeper service at the TCD grid site, so that the cloud represents an additional cluster within that site. Thus MANTYCHORE would offer a simple basis for harnessing distributed compute resources.

• A related possibility is that, given the same private network domain, the cloud resources would be exposed via an IaaS interface and used to provide “elasticity” to the existing cluster at the TCD grid site. The use of compute cloud resources to service peaks in demand on the grid is an open research issue beyond the scope of this project. This use-case would be a proof-of-concept for running an IaaS compute cloud on top of distributed resources.

The vision is then a network of clusters of virtual machines, federated via a virtual routing infrastructure provided by MANTYCHORE. It is likely that these two avenues of research will be explored concurrently.

There are two policy aspects. Firstly, these use cases require the permission from the institutions that host grid sites to extend MANTYCHORE from HEAnet’s Points-of-Presence to the grid gateways within the sites. HEAnet and Grid-Ireland will be equal responsibility for gaining permission. Secondly, the VMs would be contributed by TCD, not provided by MANTYCHORE.

Quite how widespread this cloud layer might grow is a subject for future discussion. There is a possibility of including some nodes outside the Republic of Ireland, which would represent an extremely interesting international aspect. What is certain is that the cloud would be deployed in Ireland. Beyond that, one Grid-Ireland gateway is deployed in the Belfast eScience Centre at Queen’s University Belfast (QUB) in Northern Ireland, but their involvement would be a subject for separate discussions. Other possibilities may arise from the participation of the Grid-Ireland OpsCentre in an FP7 virtualisation/cloud proposal, if funded.

B 1.1.3 Design and Architecture of MANTYCHORE services

MANTYCHORE will provide IP Network as a Service, following the Infrastructure as a Service (IaaS) paradigm. The project will use the successful results from the privately funded MANTICORE II initiative to provide a comprehensive tool that can provide Network as a Service at layers 1,2 and 3. The software tool will be based in the Infrastructure as a Service Framework, a software development and integration framework tailored to build IaaS management solutions. Some of the MANTYCHORE consortium partners are actively involved in the development (i2CAT) and use (HEAnet, NORDUnet) of the framework. This section provides an overview of the IaaS Framework goals and components.



The purpose of the IaaS Framework initiative is to design and develop and open source software framework that can serve as the integration glue for a variety of IaaS and virtualisation management solutions. This modular software framework provides a programming model, common modules and runtime to host the different components of a complete IaaS management solution capable of managing the operation of IP Network Services. The IaaS Framework provides the following features:

• Hardware and software resource abstraction, synchronisation and modelling. Heterogeneous hardware and software resources must be abstracted and represented in order to interact with them, for management and configuration purposes. The framework provides means of adding support for new devices in a simple and modular fashion.

• Resource Management. Provide a unified approach towards the management of the abstracted resources, by defining common management operations that the different types of resources may or may not implement.

• Remoting technologies for the remote interaction with the abstracted resources. The software developers that use the framework to develop their applications are able to choose within a myriad of remoting technologies (HTTP, REST, SOAP, XML-RPC, JMX, RMI, or others) to remotely expose the functionality provided by their resources.

• Security, accounting, persistence. The framework provides a security model and security libraries as plug-ins to let the software developers implement authentication and authorisation mechanisms. Also, logging mechanisms that can be plugged into different accounting and billing solutions are necessary. A persistence framework that provides access to different persistence providers is also one important feature of this framework.

• Dynamic, modular component model and runtime platform. A key element provided by the framework is a modular component model, where new modules can be plugged in an out, discovered and used at runtime. A runtime platform that serves as the hosting environment of all the modules (the framework ones plus the ones developed by the developers) is also included in the Framework.

• A Software Development Kit (SDK) to allow developers to quickly integrate the framework into their development environments, and to ease up the framework’s use.

Figure 5 illustrates the IaaS Framework architecture, showing the different modules it provides.



Fig. 5 the IaaS Framework, the basis of MANTYCHORE services

Resource Description and Management Framework. This component provides the tools to model any physical/virtual infrastructure piece (hardware and software) as an abstract resource and manage its lifecycle events (create, read, write, delete, schedule, and others). This resource framework can be seen as similar to WSRF (Web Service Resource Framework), but without being tied to any particular remoting technology. Operations on the resources can be plugged in by using the concept of capabilities (reusable blocks of functionalities). An example of use of this component would be the creation of a resource representing a router, or a switch.

An important part of this resource management framework is the drivers’ module (called “engine” in the IaaS Framework terminology). Drivers have the mission of converting abstract operations on the resource representation to configuration/control messages to the managed hardware/software device, and to synchronize the status of the managed entity with its resource representation. The creation of drivers for new types of devices should only require knowledge about the required commands to interact with the device, and the rest of the work should be done by the framework. This module will also provide transport protocol implementations (TCP, UDP, SSL, SSH, Telnet and others) to be able to remotely manage devices.

Another key point of the framework is to provide the ability to interact remotely with the resource representations. This component of the framework, called “services”, takes care of providing remoting technologies that can be attached to the operations provided by the abstract resources, therefore allowing abstract resources to provide services remotely over different protocols: SOAP, REST, HTTP, XML-RPC, RMI, JMX, and others.

Security. The security components provide tools to implement authentication, policy-based authorisation and accounting. A complete security architecture is provided by the Framework, and custom pluggable authentication and authorisation components can be integrated and tailored to each particular solutions. MANTYCHORE will leverage this feature to study the integration with



EduGain’s identity federation. Logging mechanisms that keep track of all the events on resources are also be provided, with the ability to integrate with external accounting and billing solutions.

Persistence. The persistence component main goal is to provide an abstraction for using different persistence mechanisms and/or providers. Developers must be able to change the data store where resources are persisted by specifying it on configuration files.

Graphical User Interface. The Resource Management Centre provides modular components for creating user interfaces for resource management. The framework provides a base, extensible GUI – the Resource Management Centre – with basic functionalities to interact with resources: resource discovery, inspection, creation, deletion, monitoring and others.

Runtime platform. This is the server that provides a hosting and execution environment of the applications based on the framework. The runtime platform offers a modular container where different components can be plugged in – even at execution time. A Relational Database Management System (RDMS) is shipped with the server; so that applications developed using the framework can make use of a local database. The runtime platform provides local and remote interfaces for management and interacting with it. Two types of interfaces are included: a command line interface, that enables developers and system administrators to deploy and undeploy components to the container, as well as monitor their status; and a web interface, more suited for remote administration, monitoring and maintenance of the platform.

!"#$#$C"45678%9:;<":0/)(+12)3",'-"+)(D'1(,E"3(&*)!!MANTYCHORE will exploit the Infrastructure as a Service paradigm to enable National Research and Education Networks (NRENs) and other e-Infrastructure Providers to enhance their service portfolio by building and deploying the software and tools to provide IP Networks as a Service to virtual research communities. This overall goal can be broken down into the following objectives:

Objective 1

Enable HEAnet and NORDUnet to provide IP Network Services to their customers through the MANTYCHORE tools, enhancing their service portfolio; thus providing virtual research communities with a useful service that can improve their research activities and optimize the efficiency of use of e-Infrastructures.

• Offer pre-operational services to “virtual research communities”: MANTYCHORE will provide pre-operational services to the clients (user communities) of, at least, two European NRENs: HEAnet and NORDUnet. These communities will benefit of these services being a useful tool for their research activities.

• Evaluation of the services provided through MANTYCHORE in NRENs and user communities: Each NREN will deploy MANTYCHORE as a pre-operational service. The service will be used by different research communities (Grid in Ireland, health in Denmark, media in the UK), which will evaluate how these services are useful for their research activities.



• Telefónica’s study to use MANTYCHORE services in a commercial environment: In order to evaluate the likelihood of successfully moving MANTYCHORE to a commercial environment, Telefónica I+D will study the deployment and operation of the IP Network Service and will analyse its applicability in an operator’s environment with commercial customers.

Collaboration with other worldwide projects to bring MANTYCHORE services to the maximum possible number of users:

o MANTYCHORE tools used in FEDERICA: FEDERICA project could potentially benefit from the MANTYCHORE tools. FEDERICA provides testbed facilities allowing the research community to perform experiments in the field of networks. MANTYCHORE could be used by FEDERICA to provide its clients an efficient tool to create, configure and manage the IP networks over which they pretend to perform research experiments.

o MANTYCHORE as a possible GN3 service: If MANTYCHORE proves to be a successful tool to implement the IP Network Service at NRENs, the next logical step is to evaluate its applicability to the pan-European research network: GEANT. This will need to be discussed with the GN3 project

Objective 2

Refine and expand the MANTYCHORE services provided by means of the integrating the results of the privately funded MANTICORE II project with the IaaS Framework based solutions for optical (Argia) and Ethernet/MPLS networks (Ether); thus being able to provide integrated services at levels 1-3 to the research community.

Currently, the IaaS Framework design has evolved towards a stable status, and its first beta implementation is being finished. This new implementation has been designed with modularity, extensibility and robustness in mind, and is using the latest enterprise Java technologies. All the future IaaS Framework based projects, like the next version of Argia [18] or Ether [18], will be built on this platform. Furthermore, other improvements and features can be added to enhance the added value for the research community, such as offering the possibility to perform advance reservations in IP networks.

Integration with Argia and Ether services:

o Integration of all the Engine drivers: Thanks to the engine, the IaaS Framework achieves heterogeneity in the device management and configuration, providing, in this way, an open tool to any device model from any vendor. Argia, Ether and MANTYCHORE share the same engine modular structure based on one driver per device model, so all drivers must be together in the same Engine for having a lower layer able to communicate with devices at layer 1, 2 and 3 of the OSI model.



o Integration of all web services: The core of an IaaS Framework system is based on web services where each infrastructure resource is abstracted in a web service resource. The Argia, Ether and MANTYCHORE web services are based in the same technology and are possible to put them in the same server because each one is independent from each other.

o Integration of all GUI modules: The Argia, Ether and MANTYCHORE GUIs are implemented by means of Eclipse RCP and share the same base. The specific characteristics of each tool are implemented as plug-ins that can be added on the base IaaS GUI.

Get requirements from NREN’s and user community about MANTYCHORE desired new features or improvements: At the beginning of the project, a list of requirements that MANTYCHORE should fulfil will be collected from all the users and NRENs in the project. These requirements will be prioritised and implemented by the development team.

Objective 3

Innovate in the business model used in services based on IaaS, establishing a marketplace where all Infrastructure Providers can announce their available resources and all customers can automatically negotiate the SLAs getting the best resources combination for their needs.

A system to look up which resources are available in each infrastructure provider is convenient for the final users. Without a marketplace, users have to deal with providers in a one by one basis, following a manual process to negotiate with them. The introduction of the marketplace automates the negotiation between consumers and providers, and also enables a richer choice of providers. Therefore, a marketplace will be implemented where NRENs will be able to announce the infrastructure resources they offer to final users – with its usage conditions-, and where final users will be able to check which available resources are suitable for their needs.

Objective 4

Use MANTYCHORE services to contribute to the research performed in the GreenStar Network (GSN) project to enable carbon-neutral infrastructures.

• Collaboration with the GreenStar Network project [53]: The IaaS paradigm allows e-Infrastructure providers to offer virtual resources to users; as users are not working directly with the physical devices, if virtual devices are migrated to another physical site the user should not realize of this change. This capability would be very useful for the research that the GSN project is performing about migrating entire virtual networks from one place to another one based on clean power availability. What GSN is investigating is the use of unstable renewable power sources (such as sun and wind) to power data centres and networks. When there are no solar power stocks left, all the virtual machines could be migrated to another data centre in another part of the world where is enough clean energy available. As



MANTYCHORE tools support network virtualisation, one of the research activities will be to study the possibility of migrating virtual devices from one physical site to another, following the availability of renewable energy.

!"#$#$F";)E)2,'()"&G"45678%9:;<"H1+D"+D)"H&.I"*.&J.,@"&0/)(+12)3"

The following table shows how MANTYCHORE addresses the key objectives of the Call 7, Objective INFRA-2010.1.2.3 on “Virtual Research Communities”.

INFRA-2010 Work Program target

INFRA Overall Objective Addressed by MANTYCHORE

“The overall objective of the Research Infrastructures part of the 'Capacities' specific programme is to optimise the use and development of the best research infrastructures existing in Europe,”

MANTYCHORE, based on IaaS, allows NRENs to efficiently use its current infrastructure to offer a new service enabling more agility, control and flexibility to end-users. MANTYCHORE offers the possibility of sharing and configuring infrastructure among several users; users manage each resource as they were its owner, hence management costs (OpEx) in NRENs are minimized. Moreover, NRENs' CapEx can be minimized due to the virtualisation management capabilities supported by MANTYCHORE services.

“…and to help to create in all fields of science and technology new research infrastructures of pan-European interest needed by the European scientific community to remain at the forefront of the advancement of research,”

MANTYCHORE services help research communities to have customized IP networks supported by the existing NREN e-Infrastructure. MANTYCHORE allows the creation of dedicated network research infrastructures with no investment on physical devices: instead, it makes NREN e-Infrastructure resources available to researchers, allowing them to compose their dedicated network infrastructure.

“… and able to help industry to strengthen its base of knowledge and its technological knowhow.”

Industry, represented by operators, will use MANTYCHORE project to learn how the MANTYCHORE services should be deployed in an operational environment. They will gain experience and knowledge on the operation of user-managed network services.

Objective INFRA-2010.1.2.3



“The main call objective is to enable an ever increasing number of users from all science and engineering disciplines and beyond to access and effectively use e-Infrastructures in order to increase their participation in research of global relevance and/or to allow them to access and share facilities, instruments, software and data from wherever they are based”.

MANTYCHORE tools enable to share a physical network infrastructure between several users. These tools will be deployed in the NRENs' e-Infrastructure, dedicating different subsets of the infrastructure to different research communities.

MANTYCHORE will open the researchers’ access to NRENs e-Infrastructures, getting permissions over their physical resources, sharing them between researchers and giving the management to users; thus minimizing the NRENs operational costs; and enhancing the effectiveness of the e-Infrastructure operation.

On the other hand, as MANTYCHORE will allow NRENs to provide Infrastructure as a Service (IaaS), research communities’ access to e-Infrastructures will be increased, providing, in an economic way, the infrastructure to user’s research groups.

“Removing the constraints of distance, access and usability as well as the barriers between disciplines should lead to more effective scientific collaboration and innovation and therefore increase the effectiveness of the European research”.

MANTYCHORE removes the barriers of access and opens the infrastructure to every research community. An IP network can be created using physical resources from several Infrastructure Providers or NRENs located in several countries. In fact, MANTICORE services will be deployed in two NRENs: HEAnet and NORDUnet.

Furthermore, MANTYCHORE tools simplify the way to manage devices and to configure IP networks; any research user group could make use of MANTYCHORE services without having a deep knowledge on IP networks or network configuration.

“Proposals should incorporate users from academia and industry from one or more scientific or engineering communities, computational scientists and e-Infrastructure providers. Training activities in the use of e-Science environments in order to enable researchers to fully exploit e-Infrastructures are welcome”.

MANTYCHORE consortium includes users from 3 different research communities (health, high definition media, grid), 2 NRENs and a commercial operator.



“Deployment of e-Infrastructures in research communities in order to enable multidisciplinary collaboration and address their specific needs”.

MANTYCHORE permits taking advantage of the investments that have been done by NRENs to acquire their current e-Infrastructures by means of offering a new service based on IaaS. The e-Infrastructure in the different NRENs can be virtualised and offered to many research communities, allowing them to manage their dedicated IP network.

“Deployment of end-to-end e-Infrastructure services and tools, including associated interfaces and software components, in support of virtual organisations in order to integrate and increase their research capacities”.

MANTYCHORE will provide new operational services (IP Network as a Service) to NRENs and will work over their e-Infrastructures. IP Network as a Service allows connectivity provisioning where users are able to manage and configure the provided IP Networks. The management and configuration of these services is done by means of MANTYCHORE tools that try to simplify these processes.

“Building user-configured virtual research facilities/testbeds by coalition of existing resources (e.g. sensors, instruments, networks, and computers) from diverse facilities, in order to augment the capacities of research communities for real world observation and experimentation”.

MANTYCHORE services allow users to build their IP networks according to the needs of their research activities, integrating these user-configured IP networks to their research facilities/testbeds. As MANTYCHORE is based on the IaaS Framework, it would be possible to add IaaS's tools supporting new types of resources such as sensors, instruments and computers.

“Addressing human, social and economic factors influencing the creation of sustainable virtual research communities as well as the take up/maintenance of e-Infrastructure services by communities”.

MANTYCHORE - GSN joint research in carbon neutral e-Infrastructures can have a deep impact in their sustainability, especially with the possible advent of cap and trade schemes that limit the CO2 emissions of organisations.

Table 1 MANTYCHORE contributions regarding to the work program objectives

!"#$#$K"4),3A.,0E)".)3AE+3"

The MANTYCHORE project will deliver several results to the research community. Below, the reader can find these results exposed as well as the associated delivery dates. These results can be categorized as software, experience and collateral research.

The MANTYCHORE project will produce the following software results:



• MANTYCHORE Software Toolset. Will be offered both as off-the-shelf installable product (binaries format) as well as downloadable source code. Regardless of the packaging format, the software toolset will be composed at least by:

– MANTYCHORE Server. Built over the IaaS Framework, the MANTYCHORE server component is to be installed on one or more server and is responsible for connecting to the managed resources, the engine logic and delivering the web application to clients.

– MANTYCHORE Web application for administrators and users. Will be installed on a server and accessed by the user as a regular web site. It will offer a rich interface to manage the MANTYCHORE server functionality and will be extended as additional plugging are installed on it.

Both are to be delivered at WP4 as D4.2 at month 30. Beta versions of these tools will be released during the project lifetime, starting at month 9.

• MANTYCHORE Marketplace Prototype. After a study and simulation, a prototype implementation of the marketplace using the MANTYCHORE Software Toolset will be delivered at month 20 as part of T6.2.

Additionally, the MANTYCHORE projects focused a substantial effort amount to deployment and pilot projects of software results which is intended to generate relevant experience:

• Operational experience on providing IP Networks as a Service in NRENs as a result from T5.1, which will run from months 10 to 30.

• User experience and feedback on using the service in 3 different areas (e-Health, Media, Grid) and evaluation of the commercial potential of the service (Telefónica I+D, done at WP5 from months 10 to 30).

As a result of WP6 and WP7, several collateral researches are going to be impacted and retrofitted into MANTYCHORE. Concretely:

• Resource marketplaces as a mechanism for automatically negotiating and allocating infrastructure resources at WP6 from months 2 to 20.

• Clean energy powered e-Infrastructures, energy metering, and impact of virtual infrastructure relocation on the user experience results as performed at WP7 from months 7 to 25.

Finally, studies on exploitation of the tools delivered in the project and the IaaS business models will deliver the following items:

• MANTYCHORE software business plan, delivered as D2.5 at month 14. • A technical and economical study of the feasibility of providing IP Networks as a Service in a

commercial operator environment, delivered as D5.1 at month 20.



!"#$>"L.&J.)33"0)B&'-"+D)"3+,+)"&G"+D)",.+"

!"#$>$#"L.&/)(+"0,3)E1')"

As stated before, the MANTYCHORE project is build over the foundation of MANTICORE II research project. However, the MANTYCHORE project is reinforced by the collaboration of other research initiatives, which on its turn, provide the baselines for concrete Work Packages.

Availability Source Purpose MANTICORE II October 2010 MANTICORE II project Base for WP4

The MANTICORE II project will produce as final outcome a software product. This will be composed of the server and the user interface. Both artefacts will form the baseline of further developments. Additionally, a document describing the current set of requirements satisfied at the end of the MANTICORE II project will be used as baseline to consider and decide further software refinements efforts.

IaaS Framework April 2010 IaaS Framework Project Base for WP4

The IaaS Framework project will produce periodic releases of their software framework. Latest stable release of the moment will be used as base for the design and development of the MANTYCHORE software components. As new versions of the IaaS Framework are released, they will be evaluated and eventually integrated on the development.

Argia December 2010 Argia Component for WP4

Argia is the IaaS Framework based version to provide IaaS to optical network devices. By integrating with Argia, MANTYCHORE will be able to provide as a service networks consisting of IP routers and point-to-point links provided through optical equipment. Argia will deliver a set of server side an user interface plugins that, added to the IaaS Framework base infrastructure, provide the functionality to provide optical devices as a service and create point to point links.

Ether January 2011 Ether Component for WP4

Ether is the IaaS Framework based version to provide IaaS to Ethernet and MPLS devices. By integrating with Ether, MANTYCHORE will be able to provide as a service networks consisting of IP and MPLS routers, Ethernet switches and point-to-point links provided through layer 2 equipment. Ether will deliver a set of server side a user interface plugins that, added to the IaaS Framework base infrastructure, provide the functionality to provide Ethernet and MPLS devices as a service and create layer 2 links.



GreenStar Network June 2011 GSN Base for WP7

Under the WP7, an integration and testing effort will be conducted. At month 7 of the MANTYCHORE project, when this collaboration will start, an evaluation of the current state of the GSN software stack and possible integration strategies will be done. This evaluation (deliverable D7.1) will define the baseline for the integration effort.

!"#$>$>"4567M%:;<"1''&2,+1&'3""

The MANTYCHORE project is based on the IaaS (Infrastructure as a Service) concept, providing both infrastructure resources and IP networks as a service to third parties. To achieve this goal NRENs assign permissions on a subset of their e-Infrastructure resources, so that properly authenticated researchers can control it using the MANTYCHORE tools.

At this point, routers, switches and optical devices are published as resources. All these resources are used by the virtual operators (VOs) of each user group belonging to the MANTYCHORE User Community, to build their own infrastructure, composed of physical or virtual devices provided by the NRENs. User groups’ VOs act as Service Providers, assigning resources and building several IP networks according to the needs of the research group. Finally, these IP networks are assigned to end-users in the virtual research communities. Consequently, IP Network as a Service (IPNaaS) is an important topic for the MANTYCHORE project.

The following table shows the points of innovation of the MANTYCHORE project, which are described in the following sections.

Impact Area Points of innovation

Technical Business

Infrastructure as a Service IP Network as a Service. ! !

Architecture and Business Infrastructure marketplace !

NREN services Provide IP networks as an operational service

!

Table 2 MANTYCHORE points of innovation

!"#$>$N"M'G.,3+.A(+A.)",3","O).21()""

Currently virtualisation is a hot topic. A lot of research in virtualisation related projects is being performed. This technique has been widely applied to PCs; tools like VMWare [22], Xen [23] or others provide several virtual machines on the same hardware. PC virtualisation, which was originally



used locally as a means to reduce data centres cost by maximising the server usage, has been extended by companies like Amazon or BlueLock [25] that are among the firsts to offer new type of services called Infrastructure as a Service (or IaaS), by renting hardware using proprietary solutions. IaaS [10] is the equivalent of Software as a Service (SaaS) for hardware devices, where users do not buy hardware but instead pay for the use of it to a third party (which is the real hardware owner). During the duration of the service, the user owns and controls the infrastructure as if he/she was the owner; this business model is targeted towards long term resource usage compared to on-demand services.

At the level of network virtualisation, there are manufactures currently offering IaaS capacities to reduce operational and capital expenditure. For example, Juniper Networks [44] aims to virtualise routing systems, networks and services within the network core [45]. A single platform saves on both capital and operational expenditures. The hardware logical routers partitioned at the line-card level share high-speed interfaces and WAN links and the solution consumes minimal rack space and power.

!"#$%$N$#"@**?"P4*I(2345""

The IaaS Framework [10] is a generalized approach to the outcome of years of research under the research programs funded by CANARIE. Beginning in 2001, two UCLP [13, 14] research projects were put in place to provide a virtualisation solution for optical networks: UCLP initial goal was to provide end to end paths across domains; UCLPv2 goals were to create reusable and configurable network blocks. UCLPv2 concepts have evolved into many different Physical to Virtual (P2V) products and research projects that are built on the IaaS Framework: Argia [18] is the product for optical networks (TDM, WDM and Fibre technology), Ether will be the product for Ethernet and MPLS networks, MANTICORE II is the research project for logical IP networks and, finally, the GRIM [18] project performs research on applying virtualisation to instruments and sensors.

The IaaS Framework is a set of resources, libraries and tools licensed under the Apache Software License version 2 that enable developers to quickly create new Infrastructure as a Service solutions based on the Framework programming model. The functionalities provided by these tools allow developers to choose which web service stack will be used to expose the physical infrastructure as a service (supported SOAP engines include Axis2, CXF and Spring-WS), and provide a series of modules to plug-in capabilities like security, reservation management and data persistence to the infrastructure service. The Framework also provides libraries to speed up the development of drivers to communicate with the physical devices, like protocol parsers (TL1, NetConf, CLI), transport handlers (TCP, SSL, SSH, Telnet) and a driver architecture called the IaaS Engine.

The current version of the IaaS Framework is evolving towards a new architecture. This current version is based on the Globus Toolkit 4 [46] as a base technology. However, although it provides a lot of functionalities and WSRF, WS-N and WS- Security implementations, its programming model is too tightly coupled with WSRF, so it is impossible to separate the business logic from the web service code. This is a big issue since it prevents the developers from exposing hardware resources using different remote technologies (like plain HTTP, REST-Style web service or others) and business logic is polluted with WSRF variables and statements. Therefore, these are the reasons why the IaaS Framework is being enhanced with a new internal core architecture, and no longer using the Globus Toolkit; instead, a new technology stack based on OSGi [47] (a Java standard and runtime for creating



and deploying service oriented bundle-based Java applications), the Spring Framework [48] (a Java Framework to create enterprise applications) and Apache Muse [49] (a lightweight implementation of the WSRF, WSN and WSDM standards).

!"#$%$N$%"64:,*""

Argia [18] is the IaaS Framework based prototype to create an Infrastructure as a Service solution for optical networks. Argia is the evolution of the UCLPv2 software; it is an ongoing effort towards creating a commercial product that can be deployed in production optical networks. The first Argia release (1.4) is built on the interim release of the IaaS Framework, still based on the Globus Toolkit 4. The next version of Argia, Argia 2.0, will be built on the first public version of the IaaS Framework.

The main goal of Argia is to enable Infrastructure Providers to partition their physical networks/infrastructure and to give the control of the partitioned infrastructure to third parties (infrastructure integrators) during a period of time. These third parties may use the partitioned infrastructure in house, or may deploy some intelligent software on top of the resources (like Chronos [50], a resource reservation service) to provide services for their end users or they may even further partition the infrastructure and rent it to other users.

Argia is the IaaS Framework based prototype to create an Infrastructure as a Service solution for optical networks; MANTICORE II is the IaaS Framework based system to create an Infrastructure as a Service solution for IP networks; MANTYCHORE will be the IaaS Framework based system to create Infrastructure as a Service for networks in L1, L2 and L3 of the OSI model.

!"#$%$N$N">61&@ABCD"@@"J43Q(90"

The MANTICORE II project is developing an IaaS Framework based system to manage logical routers, physical routers and IP networks. MANTICORE II builds on the success of its predecessor – the MANTICORE I project –, which produced a proof of concept prototype. This system allows a network operator to partition its physical routers in several logical routers and allows third parties to control them; thus delivering infrastructure as a service for logical and physical routers. These third parties can integrate logical/physical routers acquired from several providers into their own IP networks, and configure internal (OSPF, RIP) and external (BGP) routing protocols.

MANTICORE II project results are tested and evaluated by the National Research and Educational Networks (NRENs) participating in the project: HEAnet, NORDUnet and RedIRIS. These NRENs will produce a list of requirements that the MANTICORE FP7 software will have to accomplish before it is deployed in each of their particular networks. One of the requirements already requested by the NRENs to be implemented in MANTYCHORE FP7 is to integrate MANTICORE II with the IaaS Framework prototypes for optical and Ethernet/MPLS networks (Argia and Ether); thus delivering a complete IP network that can integrate layers 1 to 3.

The partners involved in MANTICORE II are the following ones: i2CAT, HEAnet, NORDUnet, RedIRIS, UEssex, Cisco Systems, Juniper Networks, TID and UPC (Universitat Politècnica de



Catalunya) and Inocybe Technologies and the Communications Research Centre as international support partners. All of them contribute in funding the project.

MANTICORE II project allows NRENs to offer routers as a service and IP networks as a service (L3 resources) to their users, allowing them to manage these resources as if the users were the owners. MANTYCHORE FP7 will implement new features in order to support the deployment and operation in an operational environment and allow NRENs to offer their services to virtual research communities. One of the main features of MANTYCHORE that will be implemented is the integration of MANTICORE with L1 and L2 of the OSI model.

!"#$%$N$R"RS6C)""

Nowadays, other projects are also starting to design IaaS architecture, such as 4WARD [15]. It is an important project in the European 7th Framework Program Call 1 and partly funded by EU. Work package number 3 of 4WARD aims to provide a design of network virtualisation architecture, which creates a family of dependable and interoperable networks providing direct and ubiquitous access to information, this network virtualisation will work as a meta-architecture and it permits co-existence of diverse network architectures, deployment of innovative approaches and new business roles and players. One of the aims of this ambitious project is to fix the different problems of interoperability among networks and their management.

4WARD is an interesting project that achieves the design of virtual network architecture but is not focused on getting a final product. On the other hand, MANTYCHORE will provide a functional operational service where, it also aims to be a helpful tool for research community, not only a design or a proof of concept.

"

!"#$%$N$T"UDV?DC?"

GEYSERS is an Integrated Project (IP) of the 1.1 objective (The Network of the Future) that will start on January 2010. This project will be looking at how infrastructure providers can deliver optical and IT infrastructure to third parties, so that they can deploy an enhanced GMPLS (GMPLS+) control plane on top of the infrastructure to provide “optical + IT” services to end users.

As MANTYCHORE, GEYSERS will work on IaaS Solutions for networks, but focusing on the integration of the optical network and IT resources. MANTYCHORE will deliver a comprehensive layer 3 to 1 solution for providing IP Networks as a service. However, future collaborations with GEYSERS on enhancing MANTYCHORE’s optical network services will be studied.



"

!"#$>$C"ML"6)+H&.I",3","O).21()""

!"#$%$R$#"O438,7("43<0(4-H"-2,09'(-"*+7"3J0,9*/"7(8,9(-"*-"*"-(48,9(W"@+X4*-04<90<4("J438,-,3+,+:"

An important point of innovation is to provide infrastructure resources like switches or routers as a service (it would be a specific case of IaaS). MANTYCHORE services will offer the management and control of physical and logical devices to third parties, allowing them to control the infrastructure as if they were the owners. This feature refers to offering IP Network as a Service, where parts of the e-Infrastructure are assigned to users, instead of entire IP networks. In this way, IP Network as a Service provides infrastructure resources to researchers that, for example, don’t have enough budget to buy new equipment for their research activities. Therefore, IP Network as a Service promotes the reuse of the existing equipment in NRENs’ e-Infrastructure and gives a cheap solution to acquire equipment.

Using MANTYCHORE tools, the management of an e-Infrastructure resource is done remotely using a Graphical User Interface (GUI). Usually, vendors like Juniper or Cisco offer with their devices a tool for the remote management and configuration, but it is specific for each vendor model. In our case, MANTYCHORE tools will provide a remote management for any device model (layer 1, 2 and 3), since the data structure is intended to be common for all routers. As every device model has its own protocols and commands, a driver will need to be implemented for each model. All the MANTYCHORE tools implementation is common for all device models except the lowest layer, the driver architecture (Engine), where drivers are implemented. A driver basically consists in the actions and commands specifics for one device model.

The infrastructure provisioning feature of IP Network as a Service has some similarities to other projects, like, for instance, a patent published by Fortinet Company and the ASA (Autonomic Service Architecture) framework. Below there are a brief description of both projects and the similarities and differences with MANTYCHORE project.

Fortinet, Inc. Company has developed a patent called Remote Customer Management of Virtual Routers Allocated to the Customer [43]. The patent proposes a computerized system for providing subscriber control of network parameters operable to configure the plurality of network resources (routers). The main goal is to enable ISPs (Internet Service Providers) to deliver service by provisioning network resources, including Virtual Private Network (VPNs) in an easy way. The subscriber is able to manage a VPN network by means of the allocation of resources on the part of the Service Provider. Once resources have been allocated, the subscriber is able to manage the resources without needing the Service Provider to get involved in every case. This patent describes systems, clients, servers, methods and computer-readable media of varying scope.

MANTYCHORE has a lot of advantages in comparison with this patent. Firstly, MANTYCHORE deploys its services over the e-Infrastructure of several NREN’s, offering real operational services to European virtual research communities. On the other hand, this patent does not plead for a change in the current network infrastructure; it just proposes some advantages for current Service Providers.



This patent provides Routers as a Service (RaaS) to offer VPNs that will be completely configurable by users. MANTYCHORE goes one step further, besides VPNs, MANTYCHORE services allow the creation and managing of virtual IP networks and the configuration of the majority of essential functions in IP networks: Internal and External Routing, Policy-Management, QoS Provisioning, etc.

ASA [27] (Autonomic Service Architecture) is a framework for automated service delivery over next generation networks. ASA uses WSRF (like Argia) to abstract the physical infrastructure to build services on top of a virtualised transport environment. The concept of virtual resources allows simplifying resource management providing a uniform interface for all the heterogeneous physical resources, such as routers, links and storage devices. ASA offers more than Best Effort services using Service Level Agreements (SLAs) between customers and Service Providers, and proposes an autonomic resource sharing scheme, in which the spare capacity in under loaded SLAs can be borrowed by overloaded SLAs. After customers and Service Providers negotiate the services needed and their corresponding SLAs, ASA will manage these services in order to ensure satisfactory service delivery without Service Providers intervention. In some cases, the virtual resources are offered to customers directly by Service Providers as basic networking services. A set of several basic services would be a composite service, for example Virtual Networks.

Both MANTYCHORE and ASA framework offer services on top of a set of physical resources, but MANTICORE services include routers, Ethernet switches and optical switches to the set. Another difference between them is the way to offer the service: whereas ASA uses SLAs between customers and Service Providers and has an automated control of SLAs compliance, MANTICORE services allow to assign physical resources to users and giving them the possibility to manage and configure the resources remotely as if they were the owners. Furthermore, MANTICORE is focused on offering its services as new operational services of several NRENs, to be a helpful tool for European researchers.

The FP7 FEDERICA [55] project is a sliceable e-infrastructure dedicated to European network researchers. FEDERICA uses resources (routers, switches, computing nodes) contributed by its partners and interconnected through GEANT Ethernet links as the supporting substrate. When a researcher wants to perform an experiment, the NOC allocates a set –slice– of infrastructure resources to him (computing nodes, physical or software routers), and lets the user control it to perform networking experiments. The current procedure to create and configure slices is manual, but the project Joint Research Activities (JRAs) are prototyping and automated tool –based on the MANTICORE I proof of concept– to automate these procedures.

MANTYCHORE and FEDERICA are complementary in their goals and approaches. MANTYCHORE focuses on the refinement of tools to carry out pre-operational tests of new NREN services that better serve the research community in general. Therefore, compared to FEDERICA:

• MANTYCHORE does not deploy a new e-infrastructure; it allows the existing NREN e-



infrastructures to provide a new service to the research community.

• The audience of MANTYCHORE is broader that the one of FEDERICA: the whole European –and possibly international later– research community can benefit from using IP Network Services operated using MANTYCHORE tools, not just the networking one.

• MANTYCHORE services can potentially be provided in a commercial operator’s environment.

• MANTYCHORE tools allow e-infrastructures (such as NRENs) to provide both infrastructure and pure connectivity services.

Furthermore, FEDERICA could also benefit from collaborations with the MANTYCHORE project. FEDERICA could use the robust MANTYCHORE tools to automate the operation and management of their e-infrastructure. In fact, the MANTICORE I proof of concept prototype is already being adapted to FEDERICA’s environment to demonstrate the feasibility of this approach.

!"#$%$R$%"O438,7("@O"1(02345"*-"*"-(48,9(W"A3++(90,8,0="J438,-,3+,+:"

The 1.2.4.1 section describes how IP Network as a Service provides infrastructure resources to third parties like researchers and allows them to customize the IP networks. Connectivity provisioning is one of the main features of MANTYCHORE and the most innovative point. In fact, NRENs, as Infrastructure Providers, have two use cases related to IP networks:

• Firstly, an NREN offers MANTYCHORE services to research user groups providing e-Infrastructure resources, and then they use these resources to create several IP networks according to their needs. This use case is referred to infrastructure provisioning.

• Secondly, NRENs use MANTYCHORE services to create customized IP networks according to researchers’ requirements, and deliver the customized IP networks as a service to them, and thus, researchers get customized IP networks which provide connectivity among several points of the NRENs e-Infrastructures. This use case is referred to connectivity provisioning.

Nobody else offers a service like IP Network as a Service, and into the NRENs portfolio, it does not exist any service that offers some feature similar to the ones that MANTYCHORE offers related to IP Network as a Service. Therefore IP Network as a Service could be seen as an innovative point in network research.

There are some projects that also provide infrastructure like virtual networks, for example VINI [28] (a Virtual Network Infrastructure), but these virtual networks are not IP networks. VINI is a virtual network infrastructure that allows researchers to deploy and evaluate their ideas with real routing software, traffic loads and network events and to evaluate their protocols and services in a realistic environment that also provides a high degree of control over network conditions. To provide researchers flexibility in designing their experiments, VINI supports simultaneous experiments with arbitrary network topologies on a shared physical infrastructure. The nodes at each site will initially be



high-end servers, but may eventually be programmable hardware devices that can better handle a large number of simultaneous experiments carrying a large volume of real traffic and many simultaneously running protocols.

VINI adds Layer 2 virtual networks to Planetlab [46] slices. All of the public VINI nodes are running Trellis [28], which provides the kernel support for virtual topologies. VINI currently consists of nodes at sites connected to the LambdaRail, Internet2, and CESNET (Czech Republic).

VINI is a testbed intended to provide a real network environment to run research experiments running on top of a network carrying real traffic. It provides all the characteristics of a real network, so the conclusions that can be obtained of the experiments are more realistic that if simulation is used. In this point, MANTYCHORE provides other perspective, in fact, it is not a testbed, but its services takes profit of the existing NRENs’ e-Infrastructure and are offered to European research community.

Moreover, even though VINI provides the creation of customizable virtual networks, these are created upon virtual nodes and links running in computer machines simulating real layer 2 devices. On the other hand, MANTYCHORE services work with real routers, Ethernet switches and optical switches.

Bandwidth on Demand (BoD) services present several type of connectivity provisioning on advance, commonly at level 2. This point of view is different to MANTYCHORE's services, which provide infrastructure resources, IP networks, VLANs, and optical links, allowing the management of all them, on the users’ side, as if they were the owners of each resource.

However, during the MANTYCHORE project it is planned to implement an advance reservations system, so it would be interesting to have a look on the most important existing BoD services and projects. This type of service grants the existence of an end-to-end path with a set of features. Like MANTYCHORE, these projects offer a set of operations for network configuration, particularly among domains. Some of the most relevant projects in this area are: Harmony, Dragon, AutoBAHN, AMPS and Verizon’s commercial BoD service.

MANTYCHORE avoids a lot of problems of the end-to-end paths that are caused by the fragmentation addresses, which affects the routing configuration and its integrity. The projects that create reservations in layer 2 forget all the architecture related to the different IP classes; this situation can cause serious problems in the routing.

• HARMONY [17]: is a network brokering system that provides advance reservations of network resources in a heterogeneous environment across different administrative domains and offers integration with the Grid middleware. It allows Grid applications or end users to request end-to-end paths with specific delay and limited bandwidth.

• DRAGON (Dynamic Resource Allocation in GMPLS Optical Networks) [29]: defines a research and experimental framework for high performance networks required by Grid



computing and e-science applications. The DRAGON project is developing technology and deploying network infrastructure which allows dynamic provisioning of network resources in order to establish deterministic paths in direct response to end-user requests.

• Internet2 ION [52]: It is and operational Internet2 layer 2 service based on DCN (Dynamic Circuit Networking). It is a revolutionary, virtual circuit network service that provides dedicated bandwidth for the most demanding applications. Internet2 ION uses community-developed technologies and protocols to provide on-demand, dedicated optical paths between endpoints. Internet2 ION is built on technology developed in collaboration with the Department of Energy's ESnet, GÉANT and other leading R&E network organisations. Just as the R&E community led the way decades ago in expanding the reach and capabilities of packet networking using the IP and TCP protocols, Internet2 ION breaks new ground to provide the U.S. research and education community dedicated, customizable, on-demand bandwidth.

• AutoBAHN (Automated Bandwidth Allocation across Heterogeneous Networks) [12]: GEANT2 is a high-bandwidth academic Internet network that provides several services to the European education and research communities, the GEANT2 Automated Bandwidth Allocation across Heterogeneous Networks (AutoBAHN ) system provides a user-friendly interface for instantiating dynamic circuits over global research and education (R&E) network infrastructures.

• AMPS (Advance Multi-domain Provisioning System) [35]: is a service offered into GEANT2 project that enables authorized end-users to make a single reservation for Premium IP bandwidth that is effective across a chain of participating domains. Intuitively, a premium IP service can be described as the best possible service over an IP network that uses the available high priority scheduling techniques to emulate a dedicated circuit.

• Verizon’s Bandwidth on Demand (BoD) [16]: is a revolutionary new way to manage and control SONET-based services. The “BoD Network” utilizes a Verizon-provided optical transport network with the core network devices configured in a SONET mesh topology using optical control plane technology. BoD Network devices are physically interconnected with diversely routed fibre facilities. Verizon’s BoD service allows the intelligent network to perform certain functions autonomously slashing the provisioning time for circuits remaining entirely on the BoD Network.

MANTYCHORE services and tools show a new concept of network resource and management which provides researchers a complete set of capacities for the network layer, it does not only provide connectivity or an advance reservation, it goes beyond. HARMONY, DRAGON and AutoBAHN are focused on offering dedicated paths (point-to-point) in advance; on the other hand MANTYCHORE services allows NRENs to provide connectivity by means of entire customized IP networks. Therefore, researchers not only have an end-to-end path, but they have a functional IP network which communicates several points.

Peering services

When several IP networks are connected among them, new problems regarding interoperability and routing integrity [11] can appear. To define interoperability between control frameworks from different networks with different architectures is currently a serious problem which has not been



solved yet; this causes compatibility problems that involve a lot of requirements and use cases which must be studied.

On the other hand, MANTYCHORE services solve the routing integrity problem among IP networks by means of BGP protocol. Intra-domain routing protocols (RIP, OSPF, etc.) calculate the optimal path in a route depending on the routing metric requested, MANTYCHORE uses these tools for the communication in a same IP network. When a route must be calculated between different IP networks (different autonomous systems) peering is needed. MANTYCHORE will provide peering services over its IP networks using the BGP protocol, where each IP network created by MANTYCHORE will send its routing information to others IP networks every time a change occurs.

!"#$>$F"M'G.,3+.A(+A.)"4,.I)+*E,()""

Another innovative point is the openness towards a new business model where the current Internet Service Provider (ISP) is separated in two roles: Infrastructure Provider and Service Provider. The first one manages the physical infrastructure, while the second one deploys network protocols and offers end-to-end services. The separation opens the design of new architectures and business models that should form part of the future Internet. Some projects like MANTYCHORE, CABO [30] or RESERVOIR [31] are starting to apply the ISP decoupling.

In MANTYCHORE, the business agreement between virtual operators (VOs) of the research user groups (Service Providers) and NRENs (Infrastructure Providers) is an out of band manual process. The steps that this process follows are the following 7 steps:

1. User groups need one or more infrastructure resources.

2. The VO of the user group asks to one NREN for what he/she needs.

3. The NREN administrator uses the MANTYCHORE tools to see the inventory of physical devices. The administrator looks at the current utilisation, and, if he/she can fulfil the request, agrees with the user group VO in the provision of the e-Infrastructure resources. A negotiation about the price and the characteristics of these instances (physical router, a switch...) is started among the VO and NREN.

4. The user group VO may accept the offer of the NREN, or may further negotiate with it.

5. If they agree, the NREN uses MANTYCHORE tools to quickly substrate the e-Infrastructure resources and assign permissions to them so that the VO can be able control them.

6. The user group VOs uses MANTYCHORE tools to see the infrastructure resources assigned to him/her and that can control, the VO can also assign the resources to IP networks, configure them, etc.

7. If the VO needs more infrastructure resources, he/she might repeat this process with other NRENs.

This negotiation, although it is simple to implement and works in the real world, is clearly not optimal:



The user group VO has to contact each NREN individually.

The user group VO only knows what is available when he/she negotiates with the NREN.

The NREN allocates infrastructure resources manually, which can end up in not using this physical infrastructure optimally (in terms of resource utilisation).

Therefore, the possibility to automate this process, or at least some parts of it, would be a useful enhancement to the MANTYCHORE tools. In order to achieve this goal, a marketplace prototype will be implemented. A common marketplace belongs to some broker, although in our case it does not belong to a broker, and it is a meeting point between NRENs and research user group VOs, where the products to advertise are physical resources. By means of a common, secure, neutral and reliable infrastructure, the Infrastructure Marketplace will provide a set of services and tools designed to reduce costs and enhance the efficiency in the marketing of IP network services. One of the MANTYCHORE project objectives is implement the Infrastructure Marketplace and do the integration with MANTYCHORE tools and services deployed at NRENs.

Some examples of existing marketplaces are:

• SEDO [50]: It is the leading marketplace for buying and selling domain names and websites.

• Scout24 [51]: It’s a set of seven marketplaces focused in automobiles, electronic, finances, travels, jobs, friends and partners, real properties topics.

• eBay [52]: Since eBay’s foundation in 1995 it has become the world’s largest place to buy and sell a community of hundreds of millions of regular people, small businesses, and even big businesses from all of the seven continents.

During the MANTYCHORE project the necessary algorithms for the implementation of the Infrastructure Marketplace will be studied:

• A Resource Publication Mechanism will be designed to allow the NRENs to publish their resources to the Marketplace. This design includes appropriate resource abstraction algorithms that can hide technology and infrastructure specific details of resources and represent resources in a unified format.

• The Resource Request Submission Mechanism is another necessary mechanism that allows VOs of each user group to submit resource requests to the Marketplace. A design of a hierarchical resource submission framework that can be extended and used by different VOs for submitting resource request with different level of details will be needed. Furthermore, it will be able to map parameters requested by the user into appropriate attributes compatible with the Marketplace.

• The Resource Allocation and Matchmaking mechanism is a set of search engine algorithms of the Marketplace. The search engine wills lookup on the available abstracted resources in the Marketplace based on the user request. This includes matchmaking algorithms that can allocate



a set of resources from a pool of resources and according to predefined constraints. The main objective here is to maximize the pool resource utilisation.

Infrastructure Marketplace follows the architecture shown in the picture below:

• First of all, NRENs announce infrastructure resources from their e-Infrastructure in the Infrastructure Marketplace server. This server is managed by the Broker (an intermediary agent) and consists in a web server with a data base that offers a marketplace service. So now the physical resources of several NRENs are offered from the same place.

Fig. 6 Infrastructure Marketplace architecture

• Second, each VO of the user groups will access to the marketplace using a common web navigator, and they will choose the resources needed for their services or according to their necessities. One VO can choose one or more infrastructure resources and it doesn’t matter if these ones belong to different NRENs. Finally an agreement is done between VOs and NREN, and each NREN will give permissions of use over the resources selected by the user groups’ VOs.

• Finally, user groups’ VOs use MANTYCHORE tools to get the resources assigned to them, and these resources are placed in the MANTYCHORE server of each user group. This way, VOs can assign permissions over the resources obtained to the research users according to the needs of their research activities.

Naturally, an NREN could offer its physical resources without an intermediate, the NREN could be the owner of the MANTYCHORE server and could create his/her own system to announce its resources, but it could only offer its own resources. At the beginning of the MANTYCHORE project, the



Infrastructure Marketplace won’t be ready, therefore, VOs of each user group will have to contact with NRENs and do the agreements manually.

!"#$>$K"L.&21-)"ML"')+H&.I3",3",'"&*).,+1&',E"3).21()""

MANTYCHORE services are intended to be an operational service in any NREN, where users will be able to configure their IP networks according to their needs, using the infrastructure of the NRENs. This is an innovative point because provisioning infrastructure resources and IP networks will be a new feature for the NRENs services portfolio. Other operational network services already offered in NRENs are listed below:

• IP VPN (Virtual Private Network) Service [32] (LambdaRail): A stable, production-quality, non-interruptible service using RFC2547 BGP VPNs for projects that require an overlay IP network with separation of traffic, routing, and policy from the Routed IP Service. Available to any number of sites, using new or existing PacketNet 10-gigabit and one-gigabit connections.

• Bandwidth on demand (SINET) [33]: SINET3 provides bandwidth-on-demand (BoD) services on layer-1. Users can specify destination, duration, bandwidth with a granularity of 150Mbps, and route option. The BoD server receives reservation requests, schedules accepted reservations, and triggers layer-1 path setup.

• Internet2 ION [52]: It is and operational Internet2 layer 2 service based on DCN (Dynamic Circuit Networking).

• Premium IP (DANTE-GEANT2) [35]: Premium IP offers a low loss, low delay, low jitter service. By allowing certain traffic to have priority over all other traffic on the IP network, it provides a service similar to that of a virtual leased line. PIP is useful for real-time data transfer, such as videoconferencing, voice over IP (VoIP) and specialist project traffic. An example of premium IP is the AMPS (Advance Multi-domain Provisioning System) service.

• Bandwidth on demand (DANTE-GEANT 2) [34]: The GÉANT2 Automated Bandwidth Allocation across Heterogeneous Networks (AutoBAHN) system provides a user-friendly interface for instantiating dynamic circuits over global research and education (R&E) network infrastructures.

• Ethernet Point-to-Point (BELNET) [36]: BELNET customers can opt for a completely protected Ethernet connection over the BELNET network via Point-to-Point Ethernet service. The Point-to-Point Ethernet service ensures that different affiliated organisations can be connected to each other. In addition, an affiliated institution can also connect geographically dispersed sites within the same organisation to one another.

• Packet Based Virtual Circuits (GARR) [37]: Using the MPLS technology, it is possible to configure Layer-2 virtual circuits and to implement VPN services and QoS functionalities for circuit and for VPN. These technologies are accessible from a substantially larger number of sites than those connected through dark fibres, because those based on functionalities already available in the backbone router and in many access routers. The following services can be



configured both in a single domain (as an example the GARR network) and in the multiple domains case (GARR-GEANT-NREN).

• DFNVPN (DFN) [38]: X-WIN is the most innovative generation of DFN’s network infrastructure. X-WIN users (universities, colleges and other institutions of research and education in Germany) may have access to the technical X-Win platform via a VPN service.

• Ethernet point-to-point (HEAnet) [39]: HEAnet provides two types of Ethernet services Port mode and VLAN mode. Port mode is a point-to-point port-based transparent Ethernet Virtual Circuit that is used primarily to connect geographically remote LANs over the HEAnet network. VLAN MODE is a point-to-point VLAN-based circuit. It is presented to the user as an 802.1q trunk which filters customer Layer 2 control protocols and uses the different customer VLAN IDs to direct customer traffic to different destinations.

• JANET LightPath (JA.NET) [40]: JANET Light path is a centrally managed service which will help support large research projects on the JANET network by providing end-to-end connectivity. It includes the UKLight service for fine-grained circuit provision and extends it to include whole wavelengths across the JANET optical transmission infrastructure.

• SURFlichtpaden (SURFnet) [41]: It allows the user to set up a direct data connection between two points in the SURFnet network infrastructure without intervention through routers; it also allows to establish a fast, reliable and safe connection between to colleagues elsewhere or between one person and a lab at the other side of the country. It also offers the possibility of doing research more efficiently, or doing research that used to be impossible. This is all possible with light paths, which are distinguishing for their high capacity, quality, reliability and flexibility. The SURFnet infrastructure offers scientists new and unique possibilities to work togEther and to share facilities.

Most of the services are focused in offering connectivity to the NREN network or offer bandwidth on demand point-to-point at level 2 to customers. Therefore, MANTYCHORE can be a really innovative service into the NRENs portfolio. Furthermore, if a virtual community wants IP connectivity, the IP Network service will offer it without compromising the routing integrity of the NRENs routing hierarchy.

!"#$>$P"L).G&.@,'()"Q";)3),.(D"1'-1(,+&.3"

In order to assess the adequate performance of the MANTYCHORE project results the following indicators are proposed:

1. Scalability a. Maximum number of devices managed per MANTYCHORE (virtual) server. b. Maximum number of networks supported per MANTYCHORE (virtual) server. c. Maximum number of servers supported in the system. d. Maximum number of users supported by the system.



2. Manageability

a. Interviews with HEAnet and NORDUnet staff after having operated the services for certain time.

b. NREN manpower required to operate the services. c. Manpower required to assist the NRENs during the operation of the services.

3. Deployability

a. Interviews with HEAnet and NORDUnet staff after having deployed the software at both NRENs.

b. Number of problems detected when deploying the service at both NRENs.

4. Ease of use a. Interviews with the user after some hours of experience using the service. b. Number of questions received during the user training and duration of the training. c. Number of questions received during the execution of SA2.

5. Reliability

a. Percentage of unsuccessful requests due to software failures. b. Percentage of hours of service downtime. c. Number of bug fixing related software releases. d. Alternatives provided in case of service failure. e. Time to detect service failures.

6. Extensibility

a. Manpower required in order to add a new feature (from inception to fully tested). b. Manpower required in order to support a new device (from inception to fully tested).

!"#$N"OQ7"4)+D&-&E&JB",'-",33&(1,+)-"H&.I"*E,'"

!"#$N$#":2).,EE"O+.,+)JB"&G"+D)"H&.I"*E,'"

MANTYCHORE will follow the structure of I3 projects:

• NAs (Networking Activities) • SAs (Service Activities) • JRAs (Joint Research Activities)

These activities are outlined in the table below and described in detail in sub-sections 1.3.2, 1.3.3 and 1.3.4, respectively.

Activity Task T1.1: Project Planning NA WP1: Project Management

T1.2: Work Progress Tracking



T1.3: Project Results Evaluation T2.1: Dissemination T2.2: Exploitation T2.3: Contribution to standard bodies

WP2: Dissemination, exploitation, standardisation and liaisons

T2.4: Liaisons with relevant research projects T3.1: Liaisons with new user groups, projects or research centres

WP3: Consolidating the user community and users training T3.2: Training Users

T4.1: Requirements Analysis WP4: Software refinement T4.2: Software development: tools integration and refinement T5.1: Deployment and operation of MANTYCHORE at NRENs

SA

WP5: IP Networks as a Service for virtual research communities T5.2: Using MANTYCHORE services in virtual research

communities T6.1: Infrastructure marketplace mechanisms study and simulation

WP6: Infrastructure resources marketplace

T6.2: Implementation of the marketplace prototype T7.1: Physical integration between MANTICORE and GSN T7.2: Services integration between MANTICORE and GSN

JRA

WP7: Zero-Carbon emission virtual infrastructures T7.3: Testing networks migration

Table 3 Work Plan activities

The 3 Networking Activities support project management, training, dissemination and exploitation, doing emphasis on providing input to standardisation bodies and interacting with similar activities in Europe and worldwide and consolidating the user community.

The 2 Service Activities, where WP4 will focus on the refinement and optimisation of MANTYCHORE software, implementing the requirements requested by the users. On the other hand, WP5 will focus on the deployment of MANTYCHORE services on the NRENs e-infrastructures as new operational services, and during the operative phase, users and NREN’s will evaluate and report the bugs that could appear, providing feedback to the development team at i2CAT to solve bugs and improve the software.

The 2 Joint Research Activities are targeted towards enhancing the features of MANTICORE services beyond research environments. WP6 will address the study, design and implementation of a marketplace used to announce the physical resources of the several Infrastructure Providers (like NRENs). On the other hand, WP7 will focus in improving the technologies and infrastructure used in MANTYCHORE to reduce the CO2 emissions.



!"#$%$&"'()*+,-./0"12).3.).(4"5/6"544+2.5)(6"*+,-"785/"

!"#$%$&$#"'()**"+,(-*"

Fig. 7 MANTICORE Gantt for NA activities



!"#$%$&$&"'()*"+,"-.*(/(*(0)"

Activity No

Activity title Type of activity

Lead partic no.

Lead partic. Short name

Person-

months

Start month

End month

WP1 Project Management

MGT 1 i2CAT 10 M1 M30

WP2 Dissemination, exploitation, standardisation and liaisons

COOR 2 HEAnet 10.5 M1 M30

WP3 Consolidating the User Community and users training

COOR 3 NORDUnet 9 M2 M21

TOTAL 29.5

Table 4 List of NA activities

!"#$%$&$%"'()*"+,"102(/03-420)"

Del. No. Deliverable name Activity no. Nature Dissemination level

Delivery date

(proj.month)

D1.1 Project Presentation WP1 R PU M1

D1.2 First Periodic Activity Report

WP1 R CO M15

D1.3 Final Activity Report

WP1 R CO M30

D1.4 Project results evaluation report

WP1 R PU M30

D2.1

Exploitation, dissemination, standardisation and liaison plan

WP2 R PU M3



D2.2 Project website WP2 O PU M5

D2.3

Report on related research, exploitation and dissemination activities and planning update

WP2 R PU M15

D2.4

Report on standards, exploitation and dissemination activities and liaison with related research initiatives

WP2 R PU M30

D2.5 MANTYCHORE Software business plan

WP2 R PU M14

D3.1 User manuals WP3 R PU M6

D3.2 User community final report

WP3 R PU M19

Table 5: List of NAs deliverables

!"#$%$&$5"6.*(/(*7"10).3(8*(+9)"

!"#$"%&'()*$+,-,.(/(-*$Activity number WP1 Start date or starting

event: M1

Work package title Project Management

Activity Type1 MGT

Participant number 1

Participant short name I2CAT

1 Please indicate one activity per work package: 012$3$0(4(,%)5$,-6$*()5-&7&.8),7$6(9(7&:/(-*;$2<+$3$2(/&-4*%,*8&-;$+=1$3$+,-,.(/(-*$&>$*5($)&-4&%*8?/;$

@1A<0$3$@*5(%$4:()8>8)$,)*898*8(4B$8>$,::78),C7($8-$*584$),77B$8-)7?68-.$,-D$,)*898*8(4$*&$:%(:,%($>&%$*5($6844(/8-,*8&-$,-6E&%$(F:7&8*,*8&-$&>$:%&'()*$%(4?7*4B$,-6$)&&%68-,*8&-$,)*898*8(4G$



Person-months per participant

10

Objectives

The main goal of WP1 is to manage and coordinate all the activities of the project and also the financial and technical issues. WP1 includes all the processes related with the management, like: reporting of any progress, planning, reporting the finished work, etc. For this reason, the main related tasks aim is to manage all these issues; this WP1 will permit to control the entire project and the progress of the different partners. This activity also ensures that the project objectives are achieved. WP1 represents the contact point to the Commission.

Description of work

WP1 Activity will first establish the work to be done for the internal project management. Then, it will ensure that all the requirements that the project must accomplish are done according to the schedule and the budget. This activity is also the contact point of the project to the Commission. WP1 is also responsible for supervising that each task is being carried out during the established period of time and also it will have to manage the possible leaving of a partner or the entrance of a new partner in the project.

The work to be performed consists in the following 3 tasks:

T1.1 Project Planning (Start: M1, End: M1, Leader: i2CAT)

• Before signing the contract, rules for documenting in the Consortium Agreement will have to be specified; these rules should include the roles of the GA and TEC, the voting rights of the GA, the distribution of the advance payment and the settlement of subsequent cost claims.

• Set the procedures to be followed for reporting, collecting the regular reports and sending these to the Commission and receiving and distributing the advance payments.

• Set the dates for all the reports, deliverables and milestones. Moreover, this task will have to supervise all the work done.

• Supervise the creation of the web that will include all the documentation elaborated during the project.

T1.2 Work Progress Tracking (Start: M2, End: M30, Leader: i2CAT)

• Supervise all the deliverables elaborated during the project. • Collect all the regular reports of progress and sending them to the Commission • Ensure an open flow of information during the project. • Organise the review meetings. • Supervise the production of the Periodic Activity Reports, Periodic Management Reports and

Detailed Plans reports.



• Be the responsible for the contractual issues: maintaining the technical description of the work, the Consortium Agreements and any Contract Amendments.

• Orient all the partners on administrative issues. • Plan how the knowledge arisen from the project will be disseminated and used. • Supervise the wiki and the e-mail lists.

T1.3 Project Results Evaluation (Start: M28, End: M30, Leader: i2CAT)

• Collect the final reports of the different partners to prepare the final document. • Evaluate the different tasks of the project and its result, comparing them to the objectives. • Define and specify the final conclusions of the project.

Role of Partners

i2CAT is the Project Coordinator and will be the formal point of contact with the Project Officer for all contractual matters (including the transfer of financial payments). i2CAT will chair the General Assembly (GA) meetings. i2CAT provides the first level contact to other projects (at a technical level, liaison will also be performed by activity leaders and individual partners). This way, i2CAT is the leader and the only participant of WP1.

Deliverables

Legend: Report/Prototype/Other, PUblic/COnfidential, Month of delivery

D1.1 Project Presentation (R, PU, M1)

This deliverable is a public description of the project in terms of main goals, key issues technical approach and achievements. It is intended for publication on the Websites of the Commission and the project.

D1.2 First Periodic Activity Report (R, CO, M15)

The First Periodic Activity Report provides a summary of the major results and achievements of the project during the first 15 months and reports on the resources spent to make these achievements.

D1.3 Final Activity Report (R, CO, M30)

A Final Project Report is also produced to summarise the major results and achievements of the project and concludes the projects technical work. The regular reports from the project to the Commission may also be considered as deliverables from this Activity.

D1.4 Project results evaluation report (R, PU, M30)

A report related to the evaluation of the results of all activities carried out during the project. For



example if IP Network Services have became useful for researchers, or if the marketplace implemented has worked as it was expected, and so on. In other words, this report is intended to explain how beneficial the project has been for the virtual research communities.

Milestones

MS1 All Project Management procedures in place and operational (M1)

MS2 First Project Review successfully completed (M15)

MS3 Final Project Review successfully completed (M30)

MS4 All project documentation completed (M30)

!"H$2844(/8-,*8&-B$(F:7&8*,*8&-B$4*,-6,%684,*8&-$,-6$78,84&-4$$Activity number WP2 Start date or starting

event: M1

Work package title Dissemination, exploitation, standardisation and liaisons

Activity Type2 COOR

Participant number 1 2 3 4 5 6 7

Participant short name i2CAT HEAnet NORDUnet UNI-C UEssex TID TCD


1.5 1.5 1.5 1.5 1.5 1.5 1.5

Objectives

WP2 is the key activity for ensuring a broad impact of the project; its main goal is to stimulate and harmonise dissemination of studies, results and evaluations reports about the deployment of IP Network as a Service at NRENs. According to the WP2 goal, it is very important to convince and mobilise the research community about the benefits that IP Networks as a Service could contribute to its investigations and research activities.

In order to ensure that the project investment is effectively exploited, several dissemination activities will carry out: distribution of publicity material, presentations at scientific conferences, workshops, demonstrations at specific academic events, and so on. Also, this activity includes an exploitation plan


@1A<0$3$@*5(%$4:()8>8)$,)*898*8(4B$8>$,::78),C7($8-$*584$),77B$8-)7?68-.$,-D$,)*898*8(4$*&$:%(:,%($>&%$*5($6844(/8-,*8&-$

,-6E&%$(F:7&8*,*8&-$&>$:%&'()*$%(4?7*4B$,-6$)&&%68-,*8&-$,)*898*8(4G



comprising the exploitation plans of each partner and the joint marketing plans, determining thus the exploitation phase subsequent to the end of the project.

Another important goal of WP2 is to devote efforts in contributing to standard bodies (OGF, IRTF-NRVG and TMF, for instance), above all in the IaaS topics. We also have a view towards proposing extensions or enhancements of established standards to support the project work.

Finally, liaisons with related initiatives within the research and industry community will also be executed within this work package.

Description of work

T2.1 Dissemination (Start: M1, End: M30, Leader: i2CAT)

Participants: i2CAT, HEAnet, NORDUnet, UNI-C, UEssex, TID, TCD

The work to be carried out under this task includes the following items:

• Dissemination plan: a plan for all activities about dissemination. • Writing conference/magazine papers: This task will cover the publications of the results of

MANTYCHORE for the conferences and magazines related with the project. • Demonstrations and presentations: This task will cover the demonstrations and the presentations

done in workshops, scientific events, conferences, etc. The intention is to show to the European research community what MANTYCHORE is, the results achieved during the project, the project state, etc. This way, it is ensured a good dissemination towards the potential MANTYCHORE users, increasing thus the possibility to do new liaisons with projects related or interested in MANTYCHORE.

• Web presence: A website will be provided where all the MANTYCHORE public information will be hosted. This task covers the development of this web site and its integration with the MANTYCHORE team. Public deliverables and important information or results will be publicised in the web, with the objective of having a dissemination tool available full time, where anybody can be aware about the state of the project, the work done, the results achieved, etc. The web site will have a public area where anybody can access to it, and a private one only for the people involved in the project.

T2.2 Exploitation (Start: M13, End: M30, Leader: HEAnet) Participants: i2CAT, HEAnet, NORDUnet, UNI-C, UEssex, TID, TCD

Exploitation is one of the key activities of the project. One of the major goals is to create impact in the European society and economy. Therefore an exploitation phase is needed where the project tools and services are exploited by the ICT industry. The creation of final products and services by the ICT industry based on the exploitable results of the project is expected to have a positive impact on both



social and economic developments in Europe.

The main objectives of this task are:

• Deliver a global exploitation plan, where feasible, through collecting MANTYCHORE partner individual ones.

• Continue to monitor the market situation and assess the business opportunities. The results of this task will be fed into the global exploitation plan.

• Demonstrate the potential of MANTICORE solution in creating industry business opportunities. • Produce a business plan for the MANTYCHORE software. • European patents: It will carry out a study about the possibility of patent some of the tools or

services of MANTICORE.

T2.3 Contribution to standard bodies (Start: M6, End: M30, Leader: NORDUnet)

Participants: i2CAT, HEAnet, NORDUnet, UEssex

Analyse and monitor existing and emerging standards that are relevant to the project. Interaction with standards bodies and fora. Moreover, it will do a continuous effort to contribute in several standardisation groups, above all, in the IaaS area. Some examples of the standardisation groups are: TMF, OGF, RIPE, GLIF, and IRTF-NRVG.

T2.4 Liaisons with relevant research projects (Start: M5, End: M30, Leader: HEAnet)

Participants: i2CAT, HEAnet, NORDUnet

This task will include the activities related with clustering and concentration with other related initiatives such as European projects or national research projects expecting to benefit from the project outcomes.

Role of Partners

i2CAT is leading and contributing in T2.1. I2CAT will strongly participate in dissemination activities and also in the other tasks of the activity: in T2.2 will contribute on defining a good exploitation plan for MANTYCHORE, in T2.3 will collaborate with TMF, OGF and IRTF standardisation groups and finally, in T2.4 will also look for relevant research projects to liaise.

HEAnet is leading and coordinating this activity and also T2.2 and T2.4. HEAnet will also contribute in the other tasks: in T2.1 will contribute on dissemination trying to publicize papers in some magazine and in conferences, in T2.2 will contribute in the exploitation of MANTYCHORE services, in T2.3 will collaborate with RIPE and GLIF groups, and finally in T2.4 will contribute looking for liaisons with other research projects.

NORDUnet is leading and coordinating T2.3. They will also collaborate in the other tasks: in T2.1



NORDUnet will write some papers to be publicized in magazines and conferences, in T2.2 will contribute in the exploitation of MANTYCHORE services and in T2.4 will look for possible research projects interested in MANTYCHORE services.

UNI-C will contribute in task T2.1 disseminating the results obtained in using the MANTYCHORE tools to perform their research. UNI-C will write some papers and try to publicize them in some magazines and conferences. UNI-C will also participate in task T2.2, contributing to the overall exploitation of the project results.

UEssex will contribute in task T2.1 disseminating the results obtained in using the MANTYCHORE tools to perform their research. UEssex will write some papers and try to publicize them in some magazines and conferences. UEssex will also participate in task T2.2, contributing to the overall exploitation of the project results; and in task T2.3, trying to influence MANTYCHORE relevant standards at OGF and ETSI.

TID will contribute in task T2.1 disseminating the results of the study performed about the feasibility of deploying MANTYCHORE services in a commercial environment. Finally, TID will participate in task T2.2, contributing to the overall exploitation of the project results – focusing on the application of MANTYCHORE results in a commercial environment.

TCD will contribute in task T2.1 disseminating the results obtained in using the MANTYCHORE tools to perform their research. TCD will write some papers and try to publicize them in some magazines and conferences. TCD will also participate in task T2.2, contributing to the overall exploitation of the project results.

Deliverables


D2.1 Exploitation, dissemination, standardisation and liaison plan (R, PU, M3)

This report identifies and defines the global plans for exploitation, dissemination, standardisation and liaison activities within the project. This first report represents the agenda and strategy to follow for the coming activities in the project.

D2.2 Project website (O, PU, M5)

This deliverable will provide the project community with an efficient public tool for publishing the results and activities.

D2.3 Report on related research, exploitation and dissemination activities and planning update (R, PU, M15)

This report will include the dissemination, exploitation, standardisation and liaison activities for the period month 1 to month 15. Moreover, the report will contain an update of the planning delivered in



D2.1, if any.

D2.4 Report on standards, exploitation and dissemination activities and liaison with related research initiatives (R, PU, M30)

This deliverable will include a composition of all the activities developed within this work packaged during the second half of the project. The report will include then the exploitation, dissemination, standardisation and liaison activities realised during the last period of the project.

D2.5 MANTYCHORE software business plan (R, PU, M14)

During the development of the privately funded MANTICORE II project, the catalan government - through the VALTEC program, reference number VALTEC09-1-0015 - sponsored the creation of a business plan to exploit the project software. This business plan will be translated into english and provided as part of the MANTYCHORE project official documentation.

Milestones

MS5 First version of the website available (M1)

MS6 Related events, projects and standards identified. Exploitation, standards and dissemination plan ready (M3)

MS7 Website ready (M5)

MS8 At least two contributions done in workshops or other public events (M20)

MS9 At least one liaison with other projects or groups (M24)

!"I$J&-4&786,*8-.$*5($K4(%$J&//?-8*D$,-6$?4(%4$*%,8-8-.$Activity number WP3 Start date or starting

event: M2

Work package title Consolidating the User Community and users training

Activity Type3 COOR

Participant number 1 2 3 4 5 7

Participant short name i2CAT HEAnet NORDUnet UNI-C UEssex TCD


@1A<0$3$@*5(%$4:()8>8)$,)*898*8(4B$8>$,::78),C7($8-$*584$),77B$8-)7?68-.$,-D$,)*898*8(4$*&$:%(:,%($>&%$*5($6844(/8-,*8&-$,-6E&%$(F:7&8*,*8&-$&>$:%&'()*$%(4?7*4B$,-6$)&&%68-,*8&-$,)*898*8(4G




3 1.5 3 0.5 0.5 0.5

Objectives

The project user community will be formed by several user groups which represent a subset of the wide range of users of research, health and education networks. The project user community will start with a set of 3 user groups interested in IP Networks as a Service that will start using the project tools when the first training phase ends (month 9). User groups could include EC projects, research groups in universities or research centres, equipment manufacturers and telecommunications research labs or even individuals (e.g. PhD students). It is necessary and desired to consolidate the user community and expand the use of IP Networks as a Service. For this reason the project will devote resources in three directions:

• Extending the contacts with existing user organisations and projects on an ongoing basis, gathering requirements, providing IP networks (using NRENs' e-infrastructure) for their experiments.

• To provide the necessary knowledge to users which it will permit to achieve their needs, while at the same time, it will consolidate and enlarge the user community

• Search for new NRENs that are willing to participate in the project for deploying MANTYCHORE services on its e-infrastructure and offering them to the User Community.

On the other hand, WP3 also includes training activities for NRENs and the User Community. Even though the project software is designed to be user-friendly and usable, it requires a training period to ensure a better and efficient use of it.

The search for new user groups and NRENs finalises at the end of month 19, because every new user group has to be trained in the project tools and services, and there must be a minimum period of time in the project of using the MANTYCHORE services (in the user groups case) or operating the services (in the NRENs case). Therefore it has decided that the search lasts 18 months (finishing at the end of month 19) and the training activities finish at the end of month 21, leaving 2 months for new user groups or NRENs joining at month 19.

Description of work

T3.1 Liaisons with new user groups, projects or research centres (Start: M2, End: M19, Leader NORDUnet)

Participants: i2CAT, HEAnet, NORDUnet

This task is focused on establishing a strong relationship with new targeted users. This work will start at month 2 by liaising with a selected set of potential user groups that could be identified before the



start or during the project.

T3.2 Training Users (Start: M7, End: M9, Start: 19, End: M21 Leader i2CAT)

Participants: i2CAT, HEAnet, NORDUnet, UNI-C, UEssex, TCD

• T3.2.1 Training NRENs It will be necessary to run training courses for the NRENS. These NRENs will set up their MANTYCHORE software. For this reason, this task provides the necessary resources for these training courses: user manuals, support, software, etc.

• T3.2.2 Training UNI-C, TCD, and Advanced High Quality Media Services group. The MANTYCHORE software development team will transfer technical knowledge produced in the project to users of the MANTYCHORE services, by means of training and dissemination activities, including tutorials and demonstration labs. The training will be supported by technical presentations, as well as by course materials to be produced by the project participants who have gained consolidated expertise in the project’s service activities. Handouts will be provided to the trainees, plus, when relevant existing white papers, cookbooks and CD images.

Role of Partners

i2CAT is leading and contributing in T3.2 and will also contribute to T3.1. In T3.1 i2CAT will try to put in contact with new possible end users to use the MANTYCHORE services. In T3.2 i2CAT will be the responsible to elaborate user manuals and to train all the NRENs and virtual research communities that take part in the MANTYCHORE project.

HEAnet will collaborate in both tasks of the activity: in T3.1 HEAnet will try to look for new virtual research communities and new NRENs to form part of the project and deploy or use MANTYCHORE services. In T3.2 HEAnet will attend the training courses done by i2CAT in order to be able to deploy MANTYCHORE services in their e-infrastructure.

NORDUnet is leading and coordinating this activity and also T3.1. In T3.1 NORDUnet will look for new virtual research communities and new NRENs to form part of the project and deploy or use MANTYCHORE services. In T3.2 NORDUnet will also contribute attending the training courses done by i2CAT in order to be able to deploy MANTYCHORE services in their e-infrastructure.

UNI-C will contribute in task T3.2 attending the training courses done by i2CAT in order to be able to use MANTYCHORE services for their research activities.

UEssex will contribute in task T3.2 attending the training courses done by i2CAT in order to be able to use MANTYCHORE services for their research activities.

TCD will contribute in task T3.2 attending the training courses done by i2CAT in order to be able to use MANTYCHORE services for their research activities.

Deliverables




D3.1 User manuals (R, PU, M6)

This deliverable consists in all the manuals done about the project software and its deployment over NRENs, besides the manuals done for the end users.

D3.2 User Community final report (R, PU, M19)

This deliverable will report the consolidation of the project user community

Milestones

MS10 First training completed (M9)

MS11 Internal report about the status of the user community (M10)

MS12 User community consolidated (M19)

MS13 Second training completed (M21)

!"#$%$&$:"'()*"+,";(20)*+90)"

Milestone number

Milestone name Work package(s) involved

Expected date

Means of verification

MS1 All Project Management procedures in place and operational

WP1 M1 D1.1

MS2 First Project Review successfully completed

All M15 Project Review

MS3 Final Project Review successfully completed


MS4 All project documentation completed


MS5 First version of the website ready

WP2 M1 Website operative

MS6 Related events, projects and WP2 M3 D2.1



standards identified. Exploitation, dissemination and standardisation plan is ready

MS7 Website ready WP2 M5 D2.2

MS8 At least two contributions done in workshops or other public events

WP2 M20 D2.3, D2.4

MS9 At least one liaison with other projects and groups

WP2 M24 D2.3, D2.4

MS10 First training completed WP3 M9 Project review

MS11 Internal report about the status of the user community

WP3 M10 Internal report

MS12 User community consolidated WP3 M19 D3.2

MS13 Second training completed WP3 M21 Project review

Table 6 List of NA milestones

!"#$%$&$<"=>??-37"0,,+3*"*-420"

Partc. No.

Partic. short name

NA1 NA2 NA3 Total person months

1 i2CAT 10 1.5 3 14.5

2 HEAnet 0 1.5 1.5 3

3 NORDUnet 0 1.5 3 4.5

4 UNI-C 0 1.5 0.5 2

5 UEssex 0 1.5 0.5 2

6 TID 0 1.5 0 1.5

7 TCD 0 1.5 0.5 2



Total 10 10.5 9 29.5

Table 7: NAs summary effort table

!"#$%$&$@"A03*"1(-B3-?"

Fig. 8 Pert diagram for NAs



!"#$%$%"&'()*+',"-+.*)*.*',"/01"-,,2+*/.'1"32(4"56/0"

!"#$%$%$#"&'())"

Fig. 9 Gantt of SAs



!"#$%$%$&"'()*"+,"-.*(/(*(0)"

!"#$%$#&'()'

!"#$%$#&'#$#*+' ,&-+').'/"#$%$#&'

0+/1'-/2#$"'3)4'

0+/1'-/2#$"4'56)2#'3/7+'

8+29)3:7)3#69'

5#/2#'7)3#6'

;31'7)3#6'

WP4 Software Refinement

OTH (service)

1 i2CAT 39.5 M2 M30

WP5 IP Networks as a Service for Virtual Research Communities

OTH (service)

3 NORDUnet 56 M10 M30

TOTAL 95.5

Table 8 List of service activities

!"#$%$%$%"'()*"+,"102(/03-420)"

Del. No. Deliverable name Activity no.

Nature Dissemination level

Delivery date (proj.month)

D4.1 Requirements Analysis report

WP4 R PU M5

D4.2 Software development report

WP4 R/P PU M30

D5.1 Feasibility of IP Networks as a Service in a commercial environment

WP5 R PU M20

D5.2 Report on IP Networks as a Service deployment in NRENs and its use in virtual research communities

WP5 R PU M30

Table 9: MANTICORE deliverables table of SAs



!"#$%$%$5"6.*(/(*7"10).3(8*(+9)"

!"#$%&'()*+,$-,'./,0,/($Activity number WP4 Start date or starting

event: M2

Work package title Software refinement

Activity Type4 OTH (service)


Participant short name I2CAT HEAnet NORDUnet UNI-C UEssex TID TCD


28.5 1 3 2 2 0 3

Objectives

This activity will focus on the analysis of the user requirements (from NRENs and virtual research communities) and implement them. The implementation phase will include a subtask to solve the bugs that later can be found when the service will be deployed in an operational environment and used by the NRENs and the virtual research communities.

One requirement already requested by the NRENs is to improve MANTICORE II to offer users the possibility of working also in L1 (optical level) and L2 (Ethernet level) of the OSI model. This capability would allow users to configure and manage any type of network. Another important goal of this task is to improve the interface for the end users, so that it is as simple and usable as possible, yet still allows them to fully control an IP network. Ideally, this interface should allow users to specify the configuration of their IP network in a very high level, which would be translated to specific actions on the devices by the software implementation.

Description of work

In order to get robust and reliable software useful for the user, two main tasks can be distinguished to perform all the necessary work to improve the MANTICORE II software. The first one focuses on analysing the user requirements and the second one on implementing them.

T4.1 Requirements Analysis (Start: M2, End: M5, Leader HEAnet)

4 Please indicate one activity per work package: -12$3$-,4,*+56$*/7$(,56/&8&9.5*8$7,:,8&;0,/(<$2=>$3$2,0&/4(+*(.&/<$>?1$3$>*/*9,0,/($&'$(6,$5&/4&+(.@0<$

A1B=-$3$A(6,+$4;,5.'.5$*5(.:.(.,4C$.'$*;;8.5*D8,$./$(6.4$5*88C$./58@7./9$*/E$*5(.:.(.,4$(&$;+,;*+,$'&+$(6,$7.44,0./*(.&/$*/7F&+$,G;8&.(*(.&/$&'$;+&H,5($+,4@8(4C$*/7$5&&+7./*(.&/$*5(.:.(.,4I



Participants: i2CAT, HEAnet, NORDUnet, UNI-C, UEssex, TCD

Requirements analysis encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product, taking account of the possibly conflicting requirements of the various stakeholders such as beneficiaries or users. Requirements analysis is critical to the success of a development project. Requirements must be actionable, measurable, testable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design.

Requirements can be functional and non-functional:

• Functional requirements explain what has to be done by identifying the necessary task, action or activity that must be accomplished. Functional requirements analysis will be used as the top level functions for functional analysis.

• Non-functional Requirements are requirements that specify criteria that can be used to judge the operation of a system, rather than specific behaviors.

Each NREN and each virtual research community (UNI-C, UEssex and TCD) must elaborate a list of the new features that MANTYCHORE should have, taking into account the features that the MANTICORE II tools has already implemented. The new requirements specified will be discussed with the development team and it will be decided which ones will be implemented and which ones not.

Studies reveal that an inadequate attention to Software Requirements Analysis at the beginning of a project is the most common cause for critically vulnerable projects that often do not deliver even on the basic tasks for which they were designed. For this reason all the partners involved in this task must pay special attention to this task. The development team should work together with the users of the software (NRENs and virtual research communities) in this phase in order to get a very consistent requirements list.

TSA4.2 Software development: tools integration and refinement (Start: M6, End: M30, Leader i2CAT)

Participants: i2CAT

This task focuses on the implementation of the requirements specified in the task above. For the implementation phase the agile methodology called SCRUM will be used. SCRUM is an iterative incremental process of software development commonly used with agile software development.

The main work items initially foreseen to be implemented by this tasks are:

• Integration of MANTICORE II results with Argia and Ether • Implementation of NREN improvements (including a certain degree of adaptation to each

NREN operational environment) • Implementation of research communities improvements (probably focusing on a simple but

powerful user interface) • Integration with the federated European AAI infrastructure (EduGAIN)



This task also focuses on treat the feedback obtained from the NRENs and final users. Following are listed the issues to be done to treat and solve the bugs:

• Choose the most appropriate mechanism to report bugs and to suggest improvements. • Bugs resolution: Solve bugs reported by NRENs and virtual research communities, which will

be reported using the method specified in the subtask above. • Improvements suggestions: NRENs and virtual research communities will elaborate a list of

possible improvements of the software for future versions. This task also includes the integration of the results obtained from the JRAs activities: implementing a marketplace prototype and integrating the Zero-carbon virtual infrastructures algorithms/mechanisms into the software.

Role of Partners

i2CAT is leading and coordinating this activity and also T4.2. In T4.1 will collaborate with all the partners to elaborate the requirements list. In T4.2 i2CAT will be the developer of the MANTYCHORE software, the requirements listed in T4.1 will be implemented and also bugs reported by users will be solved.

HEAnet is leading T4.1 and coordinating all the partners to define the user requirements list. HEAnet has already suggested the requirement of the integration of MANTICORE II with the IaaS Framework based tools for optical and Ethernet/MPLS networks.

NORDUnet will contribute on task T4.1 elaborating the user requirements list. NORDUnet will contribute on the user requirements from an NREN point of view, the requirements will be focused on the GUI use and on the functionalities regarding routers and IP networks configuration.

UNI-C will contribute on task T4.1 elaborating the user requirements list. The requirements suggested by UNI-C will be from a final user point of view, focused on the configuration and use of IP networks.

UEssex will contribute on task T4.1 elaborating the user requirements list. The requirements suggested by UEssex will be from a final user point of view, focused on the configuration and use of IP networks.

TCD will contribute on task T4.1 elaborating the user requirements list. The requirements suggested by TCD will be from a final user point of view, focused on the configuration and use of IP networks.

Deliverables

D4.1 Requirements Analysis report (R, PU, M5)

This deliverable includes the list of the user requirements that are going to be implemented in the task



T4.2. These requirements will include the ones collected by NRENs and the ones collected by the virtual research communities previously discussed with the development team.

D4.2 Software development report (R/P, PU, M30)

This deliverable specifies how the requirements have been implemented, which tools have been integrated to other ones and which ones have been refined. This deliverable also includes a prototype of the project tools working with the new requirements implemented.

Milestones

MS14 Requirements Analysis completed (M5)

MS15 Marketplace integrated in IP Network services (M22)

MS16 Zero-carbon virtual infrastructures integrated in IP Network services (M27)

MS17 Software development completed (M30)

!"J$K"$L,()&+M4$*4$*$%,+:.5,$'&+$:.+(@*8$+,4,*+56$5&00@/.(.,4$$Activity number WP5 Start date or starting

event: M10

Work package title IP Networks as a Service for virtual research communities

Activity Type5 OTH (service)


Participant short name i2CAT HEAnet NORDUnet

UNI-C UEssex TID TCD


3 5 8 8 8 5 19

Objectives

The main goal of this activity is to deploy the improved MANTYCHORE services into an operational environment, where NRENs have the software installed and offer this new type of service to the virtual research communities.

The improved version of the MANTYCHORE software will be deployed in each NREN and used by the research users once WP4 has implemented all the requirements requested by the NRENs and the 5 Please indicate one activity per work package: -12$3$-,4,*+56$*/7$(,56/&8&9.5*8$7,:,8&;0,/(<$2=>$3$2,0&/4(+*(.&/<$>?1$3$>*/*9,0,/($&'$(6,$5&/4&+(.@0<$

A1B=-$3$A(6,+$4;,5.'.5$*5(.:.(.,4C$.'$*;;8.5*D8,$./$(6.4$5*88C$./58@7./9$*/E$*5(.:.(.,4$(&$;+,;*+,$'&+$(6,$7.44,0./*(.&/$

*/7F&+$,G;8&.(*(.&/$&'$;+&H,5($+,4@8(4C$*/7$5&&+7./*(.&/$*5(.:.(.,4I



virtual research communities (UNI-C, UEssex and TCD). One of the key issues to address in this pre-operational deployment is to define fault resolution procedures so that users, even though they are the ones controlling the infrastructure, do not have to deal with the problem of troubleshooting the network.

During the whole activity TID will be following and analysing the results of the deployment of the MANTYCHORE services in NRENs and how users use these services. With this information, TID will perform a study to analyse if it would be feasible to deploy MANTYCHORE services in a commercial environment, taking into account technical as well as business parameters.

Description of work

This activity is divided in two tasks, the first one focuses on deploying the MANTYCHORE services in the two NRENs and the second one focuses on the use that virtual research communities make of the MANTYCHORE services.

T5.1 Deployment and operation of MANTYCHORE at NRENs (Start: M10, End M30, Leader NORDUnet)

Participants: i2CAT, HEAnet, NORDUnet, TID

This task will focus on the deployment of MANTYCHORE services in the two NRENs: HEAnet and NORDUnet. At the beginning of the task i2CAT will help both NRENs to install the software and to deploy MANTYCHORE services in their e-infrastructure; then, NRENs will start offering the services to the virtual research communities. If bugs are found during the deployment phase, all the bugs will be reported to the development team at i2CAT to solve them. During this phase improvements can also be suggested for future versions of MANTYCHORE.

NRENs will learn the day-to-day details about installing, operating, troubleshooting and maintaining IP Network Services provided through MANTYCHORE tools. Of particular interest will be trying to find out the associated cost to operating IP Network Services, and the improvement in operations efficiency.

Finally, TID will study the installation and operational procedures carried out at NRENs and analyse the possibility of providing IaaS services in commercial operator networks.

T5.2 Using MANTYCHORE services in virtual research communities (Start: M10, End: M30, Leader UNI-C)

Participants: i2CAT, UNI-C, UEssex, TCD, TID

This task will focus on the use of MANTYCHORE services by virtual research communities: UNI-C, UEssex and TCD. At the beginning of the task i2CAT will help these users to install the MANTYCHORE software on their environment and to get everything ready to start using the MANTYCHORE services provided by the NRENs. If bugs are found during the deployment phase,



all of them will be reported to the development team at i2CAT to solve them. During this phase improvements can also be suggested for future versions of MANTYCHORE.

The user communities in this task will evaluate what is the added value that NREN services provided through the MANTYCHORE tools. To perform this activity, each user group will compare how beneficial is to perform their research activities using the IP Network Service versus using the services in the current NRENs portfolio.

TID will be in close contact with the different research communities, analyse the added value that IP Networks as a Service provides them and use this information to elaborate their study on providing IaaS services in a commercial environment.

Role of Partners

i2CAT will collaborate in task T5.1 and T5.2 helping NRENs to deploy MANTYCHORE services in its e-infrastructure and helping virtual research communities to start using the MANTYCHORE services offered by each NREN.

HEAnet will collaborate in task T5.1 deploying MANTYCHORE services in its e-infrastructure and offering the services to TCD. HEAnet will have to provide feedback to i2CAT regarding possible bugs they may found on deploying MANTYCHORE services and suggesting possible improvements on the software.

NORDUnet is leading and coordinating this activity and the task T5.1. NORDUnet will deploy MANTYCHORE services in its infrastructure and offering the services to UNI-C. NORDUnet will also have to provide feedback to i2CAT regarding possible bugs they may found on deploying MANTYCHORE services and suggesting possible improvements on the software.

UNI-C is leading and coordinating the task T5.2, using the MANTYCHORE services offered by NORDUnet. UNI-C will have to provide feedback to i2CAT regarding possible bugs they may found on using MANTYCHORE services and suggesting possible improvements on the software.

UEssex will contribute on task T5.2 using the MANTYCHORE services. UEssex will have to provide feedback to i2CAT regarding possible bugs they may found on using MANTYCHORE services and suggesting possible improvements on the software.

TCD will contribute on task T5.1 elaborating the user requirements list. TCD will have to provide feedback to i2CAT regarding possible bugs they may found on using MANTYCHORE services and suggesting possible improvements on the software.

TID will contribute in the whole activity observing and analyzing the results of deploying MANTYCHORE services in the NRENs and the usage of these services that virtual research communities do. With these results TID will elaborate a study to conclude if it would be feasible to



deploy MANTYCHORE services in a commercial environment.

Deliverables

D5.1 Feasibility of IP Networks as a Service in a commercial environment (R, PU, M20)

This report also contains the results obtained in studying the feasibility of IP Networks as a Service in a commercial environment. Results obtained in NRENs and in virtual research communities will be contrasted and studied in deep to find out the benefits that IP Networks as a Service could offer to the commercial telecom operators.

D5.1 Report on IP Networks as a Service deployment in NRENs, and its use in virtual research communities (R, PU, M30)

This report contains the results obtained in HEAnet and NORDUnet after deploying the service and a list of the reported bugs, suggested improvements and the results obtained in the virtual research communities (UNI-C, UEssex and TCD) after deploying the service.

Milestones

MS18 Internal report of IP Networks as a Service tools deployed in NRENs and used by research communities (M17)

This report contains the results obtained at the moment after deploying the MANTYCHORE services in the two NRENs (HEAnet and NORDUnet) and using them in the virtual research communities (UNI-C, UEssex and TCD).

MS19 IP Networks as a Service evaluated in NRENs and virtual research communities (M30)

This report contains the final results obtained after deploying the MANTYCHORE services in the two NRENs (HEAnet and NORDUnet) and using them in the virtual research communities (UNI-C, UEssex and TCD).

!"#$%$%$:"'()*"+,";(20)*+90)"

Milestone number


Expected date


MS14 Requirements Analysis completed

WP4 M5 D4.1



MS15 Marketplace integrated in IP Network services

WP4 M22 D4.2

MS16 Zero-carbon emissions virtual infrastructures integrated in IP Network services

WP4 M27 D4.2

MS17 Software development completed

WP4 M30 D4.2

MS18

Internal report of IP Networks as a Service deployed in NRENs and used by research communities

WP5 M17 Internal report

MSA2.2 IP Networks as a Service evaluated in NRENs and virtual research communities

WP5 M30 D5.2

Table 10 List of SA Milestones

!"#$%$%$<"=>??-37"0,,+3*"*-420"

Partc. No.

Partic. short name

SA1 SA2 Total person months

1 i2CAT 28.5 3 31.5

2 HEAnet 1 5 6

3 NORDUnet 3 8 11

4 UNI-C 2 8 10

5 UEssex 2 8 10

6 TID 0 5 5

7 TCD 3 19 22

Total 39.5 56 95.5

Table 11: SAs summary effort table



!"#$%$%$@"A03*"1(-B3-?"

Fig. 10 Pert diagram for SAs



!"#$%$&"'()*+",-.-/012"31+)4)+)-."/*5"3..(1)/+-5"6(07"89/*"

!"#$%$&$#"'()**"

Fig. 11 Gantt of JRAs



!"#$%$&$'"()*+",-"./+)0)+)1*"

!"#$%$#&'()'

!"#$%$#&'#$#*+' ,&-+').'/"#$%$#&'

0+/1'-/2#$"'3)4'

0+/1'-/2#$"4'56)2#'3/7+'

8+29)3:7)3#69'

5#/2#'7)3#6'

;31'7)3#6'

WP6 Infrastructure resources marketplace

RTD 5 UEssex 17 M2 M20

WP7 Zero-carbon emissions virtual infrastructures

RTD 2 HEAnet 14.5 M7 M25

TOTAL 31.5

Table 12 List of service activities

!"#$%$&$%"()*+",-"213)014.531*"

Del. No. Deliverable name Activity no.

Nature Dissemination level

Delivery date

(proj.month)

D6.1 Infrastructure marketplace mechanisms study

WP6 R PU M14

D6.2 Implementation of the marketplace report

WP6 R/P PU M20

D7.1

Integration between MANTYCHORE and GSN report

WP7 R PU M16

D7.2 Networks migration tests report

WP7 R/P PU M25

Table 13: MANTYCHORE deliverables table of JRAs



!"#$%$&$&"6/+)0)+7"21*/4)8+),9*"

!"#$%&'()*+(,-+,(.$(.*/,(-.$0)(1.+23)-.$$Activity number WP6 Start date or starting

event: M2

Work package title Infrastructure resources marketplace

Activity Type6 RTD

Participant number 1 3 5 6

Participant short name i2CAT NORDUnet

UEssex TID


2.5 1.5 9 4

Objectives

This activity will carry out the study, design and simulation of the necessary algorithms for the implementation of the MANTYCHORE marketplace mechanism. A marketplace is the best way to announce products from several vendors and, by means of Internet, to arrive to the maximum number of customers.

Marketplaces enable the automatic negotiation and reservation of resources between users and providers. The marketplace will provide the capability to automatically select, orchestrate and reserve the best resources for a given request; taking into account several criteria: the user request, the available resources and policies set by resource owners.

The main idea is to use the marketplace in order to allow the NRENs to announce their own infrastructure as resources of MANTYCHORE services; therefore, users from virtual research communities will be able to access resources from several providers. The marketplace will be specifically designed for MANTYCHORE, so only infrastructure resources and IP networks as services will be announced. NRENs will have to use the MANTYCHORE GUI to abstract the infrastructure to web service resources, and these ones will be the resources announced in the marketplace. On the other hand, customers will get permissions for the resources selected and they will be able to access them using the MANTYCHORE software.

Several studies and algorithms must be designed under the marketplace scenario; first of all it is needed to perform a set of studies about how the resources will be published, how the customers will

6 Please indicate one activity per work package: 456$7$4.*.)(-8$)&9$+.-8&/3/:;-)3$9.<.3/20.&+=$6>?$7$6.0/&*+()+;/&=$?@5$7$?)&):.0.&+$/'$+8.$-/&*/(+;,0=$

A5B>4$7$A+8.($*2.-;';-$)-+;<;+;.*C$;'$)223;-)D3.$;&$+8;*$-)33C$;&-3,9;&:$)&E$)-+;<;+;.*$+/$2(.2)(.$'/($+8.$9;**.0;&)+;/&$

)&9F/($.G23/;+)+;/&$/'$2(/H.-+$(.*,3+*C$)&9$-//(9;&)+;/&$)-+;<;+;.*I



submit the requests and how the resources will be allocated on the customers. The final study consists in the simulation of the marketplace and the study of its scalability.

Description of work

The WP6 activity comprises 2 tasks:

T6.1 Infrastructure marketplace mechanisms study and simulation (Start: M2, End: M14, Leader UEssex).

Participants: i2CAT, UEssex, TID

This task focuses on study and design different mechanisms to implement the infrastructure marketplace. The following studies will be performed:

• Resource Publication Mechanism will be designed to allow Infrastructure Providers to publish their resources to the Marketplace. This design includes appropriate resource abstraction algorithms that can hide technology and infrastructure specific details of resources and represent resources in a unified format.

• Request Submission Mechanism is another necessary mechanism that allows Service Providers to submit resource requests to the Marketplace. It will be needed a design of a hierarchical resource submission framework that can be extended and used by different Service Providers for submitting resource request with different level of details. Furthermore it will be able to map Quality of Service (QoS) parameters requested by user into appropriate QoS attributes compatible with Marketplace.

• Allocation and Matchmaking mechanism is a set of search engine algorithms of a Marketplace. The search engine will perform lookup on the available abstracted resources in the Marketplace based on the user request. This includes matchmaking algorithms that can allocate a set of resources from a pool of resources and according to predefined QoS constraints. The main objective here is to maximize the pool resource utilisation.

A simulation of the marketplace will be held in order to ensure that it works before integrating with the MANTYCHORE tools.

T6.2 Implementation of the marketplace prototype (Start: M15, End: M20, Leader i2CAT)

Participants: i2CAT, NORDUnet, UEssex

This task profits from the realized studies and implements a system that will create a community for the advertisement and exchange of resources. This marketplace will implement a prototype of all the features introduced in T6.1. This prototype of the marketplace will provide:

• A place to exchange different resources: routers, Ethernet switches, etc. • It will be a meeting point where different users and NRENs can publish their resources and use

them. This marketplace pretends be a media with others users and NRENs.



The prototype implementation will be integrated with the main MANTYCHORE software in T4.2.

Role of Partners

i2CAT is leading T6.2 being the responsible of implementing the necessary algorithms to integrate the marketplace in MANTYCHORE tools. i2CAT will also contribute in T6.1 helping to perform the necessary studies to implement the marketplace prototype.

NORDUnet will contribute in T6.2 helping the development team in i2CAT to implement the marketplace prototype.

UEssex is leading and coordinating this activity and leading T6.1. In T6.1 UEssex will perform all the necessary studies to implement the marketplace and in T6.2 will supervise that the implementation of the prototype accomplishes the expectations.

TID will contribute to T6.1 by participating in the marketplace definition. Regarding the huge experience that TID has in commercial environments it could be very useful their point of view of the markets.

Deliverables

D6.1 Infrastructure marketplace mechanisms study (R, PU, M14)

This deliverable contains the results of studies performed in order to implement the marketplace and also the results of the simulation.

D6.2 Implementation of the marketplace report (R, PU, M20)

Prototype of the infrastructure resources marketplace. This deliverable also contains a report where all the features of the implemented marketplace are listed and explained.

Milestones

MS20 Infrastructure marketplace studies completed (M11)

MS21 Infrastructure marketplace simulations completed (M14)

MS22 Marketplace prototype implemented (M20)



!"J$K.(/L-)(D/&$.0;**;/&$<;(+,)3$;&'()*+(,-+,(.$Activity number WP7 Start date or starting event: M7

Work package title Zero-carbon emissions virtual infrastructure

Activity Type7 RTD

Participant number 1 2 3 6

Participant short name i2CAT HEAnet NORDUnet TID


5 2.5 5 2

Objectives

MANTYCHORE will start collaborations with GSN (GreenStar Network) project for the integration of its NREN infrastructures in its test-bed where GSN network is formed by a set of green nodes where each node is powered by sun, wind, etc. GSN Carbon Measurement Protocol is used for GSN to measure the quantity of energy and carbon emission permitted in these nodes allowing for better management. It will be utilized to generate carbon credits from the reduction of carbon resulting from relocation different network resources among networks and test beds. Relocating these resources could possibly save tons of carbon per year.

The NREN infrastructure will be connected to the GSN network and it will add new resources, as MANTYCHORE resources. Currently MANTYCHORE features allow new possibilities to solve different issues in configuration, testing, monitoring, etc:

Benefits of the proposed User case studies are

• The location of the consortium and its distance from other sources such as the GSN test-bed from Canada and MANTYCHORE infrastructure at Europe add new interesting user cases to this project. These new user cases analyze how it is possible to move services to computing or networking resources and why its situation and location can influence that choice.

• To collaborate to research and create cloud management algorithms making optimal use of the intermittently available renewable energy sources.

• The viability and usefulness that will be measured by the degree to which the renewable energy sources can be utilized. This usefulness will be checked in the different use cases and will specify the best options to reduce emissions and energy

• To monitor different actions and movement of services among sources.

7 Please indicate one activity per work package: 456$7$4.*.)(-8$)&9$+.-8&/3/:;-)3$9.<.3/20.&+=$6>?$7$6.0/&*+()+;/&=$?@5$7$?)&):.0.&+$/'$+8.$-/&*/(+;,0=$

A5B>4$7$A+8.($*2.-;';-$)-+;<;+;.*C$;'$)223;-)D3.$;&$+8;*$-)33C$;&-3,9;&:$)&E$)-+;<;+;.*$+/$2(.2)(.$'/($+8.$9;**.0;&)+;/&$

)&9F/($.G23/;+)+;/&$/'$2(/H.-+$(.*,3+*C$)&9$-//(9;&)+;/&$)-+;<;+;.*I



These workflow and goals will be transparent for end users who will not see any difference and will not have any interruption in their tasks. For an end user, his service will work continuously without any problem.

Description of work

T7.1 Integration between MANTYCHORE and GSN (Start: M7, End: M16, Leader NORDUnet)


The main goal of this task is to setup a GSN node that will allow access from varied NREN infrastructures to the GSN network. To achieve this subtasks are required to carry out:

• Analysis of different possibilities to connect the two infrastructures. • Integration of MANTYCHORE physical resources in GSN. It includes all the process of

installation of a connection MANTYCHORE -GSN • To specify requirement and planning of the software integration. It is necessary understand

and specify how MANTYCHORE and GSN services will be able to collaborate – both will be using IaaS Framework based software, so this integration is not foreseen as a big task.

• MANTYCHORE services provide facilities to configure routers and interfaces give flexibility thanks to its IaaS architecture and give a management of logical devices. GSN profits from all these features to improve its infrastructure.

T7.2 Testing networks migration (Start: M17, End: M25, Leader HEAnet)


MANTYCHORE-GSN collaboration has the objective to design necessary experiments and tests which eventually check the viability of this movement of services (virtual machines (VMs), flexible device configurations utilities, etc…). Goals to achieve within this task are:

• Search and design algorithms which will select different policies and an optimised set of options

• Every MANTYCHORE device has an energy expense will be measured using different techniques. This subtask will search different possibilities to study the electrical consumption of each device and to integrate measuring and reporting algorithms into the MANTYCHORE application.

• Time is an important dimension in making energy measurements, which will require data capture, logging and historical analysis and comparison features

• Different options for migrating services are evaluated by conducting trials and experiments to highlight the full capability of these services. GSN will profit from MANTYCHORE’s architecture to increase the flexibility of testing and modelling services.



• The GEANT Stitching Framework [54] will be extended to characterise and highlight the attributes and energy consumption parameters to allow for easier integration into emerging solutions.

Role of Partners

I2CAT will participate in T7.1 and T7.2. In T7.1 will contribute on performing the integration between GSN and MANTYCHORE (physical integration between the GSN and the NRENs infrastructure and also the services integration). In T7.2 i2CAT will participate in implementing the necessary algorithms and mechanisms to integrate the Zero-carbon emissions virtual infrastructures into MANTYCHORE services.

HEAnet is leading and coordinating this activity and T7.2 being the responsible for the joint experimentation on moving virtual resources based on renewable energy availability. Modifying the GEANT Stitching Framework is their responsible and should highlight the most relevant parameters and the interaction of their attributes to assist in the physical implementations. HEAnet will also contribute in T7.1 contributing to the physical integration between MANTYCHORE and GSN infrastructures

NORDUnet is leading T7.1 and will contribute in T7.2. In T7.1 NORDUnet will focus in performing the physical integration between MANTYCHORE and GSN infrastructures and also the services integration. Finally, in T7.2 NORDUnet will be the responsible for ensuring that the algorithms are optimised to perform network migrations.

TID will contribute in T7.1 offering part of its infrastructure to integrate MANTYCHORE and GSN. TID will also contribute in T7.2 performing some experiments over part of its infrastructure to ensure that the migration of entire virtual networks works correctly.

Deliverables

D7.1 Integration between MANTYCHORE and GSN report (R, PU, M16)

This deliverable will provide all relevant information related with the new installed resources. It includes all the information to the connection between MANTYCHORE-GSN including information about physical and software components. It is intended to be the comprehensive reference for building MANTYCHORE-GSN infrastructure.

D7.2 Networks migration tests report (R, PU, M25)

All experimental algorithms are presented in this deliverable, which details all the algorithms evaluated. Final experimental conclusions will show the viability of those algorithms selected. As each algorithm is described, full details of implementation features, and their interaction are fully



explained (of both the optimal and other algorithms which were researched).

Milestones

MS23 Physical networks integrated (M11)

MS24 Services integrated (M16)

MS25 Tests performed (M25)

!"#$%$&$:"()*+",-";)31*+,91*"

Milestone number


Expected date


MS20 Infrastructure marketplace studies completed

WP6 M11 D6.1

MS21 Infrastructure marketplace simulation completed

WP6 M14 D6.1

MS22 Marketplace prototype implemented

WP6 M20 D6.2

MS23 Physical networks integrated

WP7 M11 D7.1

MS24 Services integrated WP7 M16 D7.1

MS25 Tests performed WP7 M25 D7.2

Table 14 List of JRA Milestones

!"#$%$&$<"=>??.47"1--,4+"+.531"

Partc. No.

Partic. short name

JRA1 JRA2 Total person months

1 i2CAT 2.5 5 7.5

2 HEAnet 0 2.5 2.5

3 NORDUnet 1.5 5 6.5



4 UNI-C 0 0 0

5 UEssex 9 0 9

6 TID 4 2 6

7 TCD 0 0 0

Total 17 14.5 31.5

Table 15: JRAs summary effort table

!"#$%$&$@"A14+"2).B4.?"

Fig. 12 Pert diagram for JRAs



!"#$%$&"'()*+,,"-.*+.)/0"+12"/)1)*+,"2)-3*45.461"

!"#$%$:$#"C,4D"8./D.B1")9+14EF1819F19/)1*"

Workpackage

interdependencies

Involved

Task Description

Involved

Deliverables/Milesto

nes

T1.1, T1.3 ! T2.1

dissemination D1.1, D1.4

WP1 "! WP2 T1.2 !

T2.1, T2.2, T2.3, T2.4

Work progress tracking

WP1 "! WP3 T1.2 ! T3.1, T3.2


WP1"WP4 T1.2 ! T4.1, T4.2


WP1"!WP5 T1.2 ! T5.1, T5.2


WP1"!WP6 T1.2 ! T6.1, T6.2


WP1"!WP7 T1.2 ! T6.1, T6.2


WP2"!WP3 T3.1, T3.2 ! T2.1

dissemination D3.1, D3.2

WP4"!WP5 TS5.1, T5.2! T4.2

Bugs to be solved DSA5.2, DSA4.2

WP5"!WP6 T6.2 ! T4.2

Integration of the marketplace prototype

D6.2



WP5"!WP7 T7.2 ! T4.2

Integration of the Zero-carbon D7.2, D4.2

WP5"!WP3 T3.1 ! T5.2

New users to deploy the service DNA3.2

Table 16: MANTYCHORE work package inter dependencies detail table

!"#$%$:$'"G)*D*"?.9.B1?19+".9F"H,9+)9B19/7"A3.9"

Risk Management in MANTYCHORE is based on the following risk management process and cross-partner risk awareness:

Fig. 10 Risk Management Process in MANTYCHORE

Risk Planning is concerned with identifying risk management procedures and responsibilities. Risk Management Planning occurs as part of the proposal and negotiation phase.

Risk Identification is about uncovering risks before they turn into problems. Like risk planning, risk identification is an iterative process. The first phase of risk identification takes place during the proposal phase. Further risk identification will take place when the project starts as well as repeatedly throughout the project. Participants in risk identification include subject-matter experts, WP leads, and project management and team members. Risk identification techniques used comprise pre-existing checklists and brain storming activities. A risk statement involves the conditions that are causing concern for a potential loss to the project, followed by a brief description of the potential consequences of these conditions. Unless a risk is written down, there is a good chance that it will not be managed. Project-specific risks that can be identified at this stage are therefore detailed in the management section.

Risk Analysis is the most detailed phase of the entire risk management process. It involves evaluating the risk attributes, and prioritizing (ranking) the risks. Evaluating the attributes of a risk involves establishing values for probability (the likelihood the risk will occur) and the impact (in terms of significance for the project). A detailed risk analysis will be a major project management task of MANTYCHORE.

Risk Response is the process of deciding what, if anything, should be done with a risk. Risk Response answers two key questions: (i) Who owns the risk (responsibility), and (ii) What can/should be done (scope and actions). Within MANTYCHORE we have identified a range of possible risk responses. It



will be the responsibility of the project management of MANTYCHORE to, jointly with the risk owner and all involved partners, identify the right response to each risk.

Risk Monitoring is the process of keeping track of the risks and evaluating the effectiveness of the response actions. Monitoring may also provide a basis for developing additional response actions and identifying new risks. This will also take place continuously throughout the project.

Risk Id.

Short description

Likeli-hood

Impact Context and/or solution(s) envisioned

R1.1 Problems to specify the different tasks of MANTYCHORE

Medium High An incorrect specification of tasks can create important delays in the project. For this reason, it is very important to create the better specification of tasks with its times. This issue is a common error in other projects, and for this, it is necessary to try to fix it and create contingency plans. The envisioned solution is to create an accurate specification of each task. This specification is formed by different subtasks specifying closely each main task. If the situation occurs, MANTYCHORE will try to move efforts, or, alternatively an extra period of time will be specified for this type of problems.

R1.2 Delay to receive reports from the Activities

Medium Medium Problems in the communication between Activities can cause delays when it is necessary to write the MANTYCHORE reports. This risk fixes this situation and it tries to guarantee the finalisation of each report on time. It is very important have control of each Activity and of its reports. The development team must be mindful of any possible delays from the Activities. In any event, if it should be necessary, it is possible to move efforts to this task and identify the cause of the delay which must be fixed. The role of the project coordinator will avoid this situation with a detailed control of the different reports that each partner have to send him.

R1.3 A partner becomes deficient or entirely remiss in the

Low High All the members in the MANTYCHORE project have extensive EU project experience making this risk improbable. Nevertheless, should this occur, it will accord 1 month for corrective action and should the result be negative, a substitute partner



Risk Id.

Short description

Likeli-hood


execution of assigned obligations

will be introduced. Furthermore, there is a certain overlap in the knowledge and abilities of MANTYCHORE partners, making it possible to shift efforts, if needed, on specific and limited activities. It is possible to avoid this type of situation with a good contracting policy, which will be able to assure a right employer. This contracting policy can include, e.g.: English exams; technical tests, implementation of sample code. Other important point is to have well defined the role for each job.

R2.1 Different problems in the preparation of demos or trainings

Medium Low This risk covers all the possible problems that can occur at different demos and training. This eventuality is not uncommon and, for this reason, it is necessary prepare a plan that minimizes all the consequences. The preparation of different events for the dissemination, for example, trainings and demos, can give problems if the system is not stable or the event is not prepared.

For this reason, each important event will be prepared in advance with the necessary time. In any event, MANTYCHORE must guarantee the dissemination of tested elements only.

R2.2 Impossible to find some interaction with standard bodies and fora

Medium Low It is possible that we may not find any appropriate standard body or fora for an interaction. In this case, MANTYCHORE has to find a solution. The interaction with other standards is very interesting and, during the project, all the partners will attempt to find possible bodies to collaborate. However it is not indispensable to find these interactions. It may also be possible to fix the problem by extending the search.

R2.3 Impossible to find liaison with relevant projects

Low Medium Another possible risk is the incapacity to find projects and liaisons that are appropriate to MANTYCHORE. Like the previous risk, it may be that there are not liaisons or projects related to MANTYCHORE area of work. This situation is



Risk Id.

Short description

Likeli-hood


not very probable, and if it is necessary to fix this situation then, like R2.2, it is possible to extend the search with the collaboration of the partners.

R3.1 Impossible to consolidate the user community

Low High-Medium

It could be that no user group wishes to use the MANTYCHORE project once the project starts. The MANTYCHORE project will start with a set of user groups that will use MANTYCHORE services to help them in their research activities, so it would not be a problem if more user groups are not found, because the existing user community will be sufficient to evaluate MANTYCHORE services and give us feedback for that. That said, if we are un able to find any user, the effort for this task will be incremented, because a major user community is better for the project's interests.

Table 17 Risks in NAs

Risk Id.

Short description

Likely- hood Impact Context and/or solution(s) envisioned

R4.1 Delay in requirements analysis

Low High If there is a delay in the requirements analysis phase, this would impact directly in the software development phase, which would start in delay and thus, cause also a delay in the deployment phase. However, the risk is considered low because all the users of MANTYCHORE services already know more or less which requirements would like to be supported by the new MANTYCHORE. In order to avoid this risk, an advisable methodology to analyse the requirements will be followed. If finally a delay in analysis requirements occurs, the next phase –software development- could start in the programmed start time because there are two requirements already requested to be implemented (integration of MANTYCHORE services in L1 and L2) and implement a simple yet powerful user interface for end users, and the phase could start



Risk Id.

Short description


with the implementation of these requirements.

R4.2 Delay in the software development

Low High If there is a delay in the software development phase, it would cause also a delay in the deployment phase. However, the risk is considered low because the development team in i2CAT has a lot of experience in developing software, especially in MANTICORE II. To avoid this risk the SCRUM methodology will be used, which helps to control these types of risks. If problems occur during the development and a delay is caused, it could be solved by using more person-months when the risk as just been identified, and subtract these person-months added in the beginning from the end.

R4.3 Delay in marketplace implementation

Low Medium

If there is a delay in the marketplace implementation, the users would not have a site to find all the resources available. However, the impact is considered medium because users can find the resources available in the website of each NREN. This risk can be avoided if the studies performed are very accurate. However, if the marketplace is not ready on time, users can continue using each NRENs’ website to check which resources are available.

R5.1 NRENs can not offer enough e-infrastructure to final users

Low High If NRENs do not have enough resources to offer to virtual research communities, not all the final users will be able to perform research using MANTYCHORE services. This risk can be avoided being efficient in the resources assignment and planning the possible increase of the number of virtual research communities interested in the project. If finally there are more users that the ones that can be supported, each NREN can apply for economical subventions in their respective countries, and/or start charging a fee for the service.

R5.2 Virtual research communities do not find

Low High If final users find MANTYCHORE services not usable, it would cause a big impact in final project results, as it would show that the project is not



Risk Id.

Short description


MANTYCHORE services usable

feasible. However, the likelihood is low because the users that are already in the project agree that MANTYCHORE services will potentially be a very useful tool for their research. In any case, if finally the virtual research communities that will be using MANTYCHORE conclude that it is not usable, WP3 would be dedicated to find new types of users in the virtual research communities that would find usable MANTYCHORE services.

R5.3 Last mile connectivity can't be realized

Medium

Medium

Due to local procedures (of an intermediate NREN or/and a computer center department) getting the last mile between an NREN partnering in MANTYCHORE and the user, can be problematic. This needs careful and timely attention to and alignment with local procedures.

Table 18 Risks in SAs

Risk Id.

Short description

Likeli- hood


R6.1 Delay in the study of mechanisms of the MANTYCHORE marketplace

Low Low The delay of the studies would mean that the simulation of the marketplace would have to be delayed. It is not an important risk because the tasks related with marketplace (WP6 activity) are scheduled several months before the project ends and the Technical Executive Committee will be supervising all the workflow. However, if a delay happens, the WP6 leader will dedicate extra time on it.

R6.2 MANTYCHORE architecture is difficult to exploit

Low Medium It's possible that the MANTYCHORE design doesn't fit in the market expectations. Possible solutions are identifying the characteristics or modules that are problematic and redesign them to fit into market expectations.

R7.1 Impossibility to connect GSN and

Low Medium For technological issues, it is possible to find incompatibilities between devices of MANTYCHORE and GSN. This situation could



Risk Id.

Short description

Likeli- hood


MANTYCHORE with a physical link

provoke which the WP7 could not be finished For this reason, it is necessary to include an initial specification which will permit to check any incompatibility between systems (GSN and MANTYCHORE). However, at the current industry, there are a lot of possibilities that it will be able to fix these types of problem.

Table 19 Risks in JRAs



!"#$%$&"'()(*+",-".,/0"12302+45"2*6"784(/"3,)1,*4*75"

!"#$%$&$#"'()(*+,"'+)--"./+0*+1"

Fig. 13 GANTT diagram



!"#$%$&$2"3(-+/,(."'()(*+,"'+)--"3/+0*+1"

Fig. 14 Detailed GANTT diagram



!"#$%$&$%"45)6(7-8+,"9(*-"./+0*+1

The following Pert diagram shows the conceptual and functional relationship between work packages in a simple view. Further details of inter-operation between work packages are given on the detailed Pert diagram in the next section.

Fig. 15 Pert diagram



!"#$%$&$:"3(-+/,(."9(*-"./+0*+1"

The following Pert diagram shows a detailed view of work package inter-operations planned in MANTICORE. Both internal and external interactions are shown, including related tasks and deliverables.

Fig. 16 Detailed PERT Diagram



!"#$%&'()&)*+,+-.*$

!"#$%"&'(')*+*(,"-,./0,/.*"'(1"2.30*1/.*-"For managing an I3 project over a time period of 30 months efficiently, a sound, professional but also flexible management structure is of crucial importance. Accordingly, both the consortium and the governance structure must be able to use the added value of the project team expertise for attaining the critical mass of the research project itself, and, in the other hand, to lead, overlook and monitor the each activity progress during the course of the project.

At project level, transparent decision-making processes are required. Conflict managing focusing on prevention rather than resolution has to be in place from the very beginning. Contingency plans have to be envisaged and “lessons learned” derived and distributed within the project team. Structures and tools are of no help if partners are not integrated. Therefore, the proposed structure aims both at the design of clear roles and responsibilities and providing a research arena, where experts feels involved and thereby contributing to the research goals.

!"#$%$%"4.)'(5-',53("-,./0,/.*"

MANTYCHORE will follow the structure of I3 projects which consist of NAs (Network Activities), SAs (Service Activities) and JRAs (Joint Research Activities) as described in section 1. The project management is represented by the figure below, where management responsibilities exist at the project (General Assembly) and Activities Leader levels (Technical Executive Committee).

Fig. 17 Organisation diagram

!"#$%$%$%"&'(')*+",--'./+0"

The General Assembly (GA) is the highest body of the project where all consortium members are represented. The voting procedure within GA will be specified in the



Consortium Agreement. Upon recommendations from the Project Coordinator, the GA takes final decisions on the overall policy of the consortium, on modifications or extensions of the Consortium Agreement or of the objectives of the project, and on any project related with financial issues. The Project Coordinator will keep the General Assembly informed about the progress and achievements in the project.

The GA will meet physically at least every year and will decide on major issues concerning resource allocations, partner changes and/or project deliverable planning. The GA can also take decisions between meetings by correspondence, including voting via e-mail. The GA is the only project body that can make decisions on contractual matters, such as the budget, timeline, shifting resources between partners, adding/deleting partners. I2CAT chairs the GA.

!"#$%$%$#"1)23'45"622)78(*52)"98#6,:;"

The Project Coordinator function is assigned to i2CAT, which will lead the project acting as the intermediary between partners and European Commission. The functions of i2CAT as a Project Coordinator are:

• Interface with the Commission for all matters associated with the project. • Chair the General Assembly and plenary meetings. • Keep regular contacts with the partners to ensure that the project direction is

maintained. • Provide the first level contact to other projects (at as technical level, liaison will also

be performed by Activity Leaders and individual partners) • Hold regular meetings with all Activity Leaders. • Assisting the meetings (General Assembly, Plenary, Project Reviews) by preparing the

agendas, writing the minutes, leading the administrative parts, etc.) • Ensuring an open flow of information, coordinating with Activity Leaders the

preparation and distribution of all major deliverables and progress reports, and collecting and collating all them.

• Assembling the periodic reports needed for the project reviews, and ensure their delivery to the Commission.

• Supervising the Cost Claim and financial audit procedures and maintaining the financial budget status of each partner.

• Maintain accurate records of costs, resources and time scales for the project. • Maintaining the Consortium Agreement, description of work and preparing any

Contract Amendments. • Adding a level of quality of assurance in terms of validating the visible outputs, such

as deliverables, presentation material, papers, etc. • Ensure that the project maintains its technical objectives, as well as its relevance

within the programme.

!"#$%$%$<":'4=(84*+">?'4@58A'"62..855''"9+'*7"/0"8#6,:"*(7"B>,('5;"

Each Activity will be managed by an Activity Leader, who oversees and coordinates the Tasks within each Activity. All the 7 Activity Leaders (WP 1-7) form the Technical



Executive Committee (TEC) will be lead by i2CAT and HEAnet. TEC meetings will be held at least every year. Interim Activity meetings will be arranged independently.

The Technical Executive Committee main tasks are:

• Assure the overall integration of the single activities. • Drive and implement project vision. • Ensure cohesion, maintain effort synchronisation, facilitate the distribution of the

results, identify timely issues and avoid overlaps between Activities. • Assess progress, suggest changes in specific goals and promote JRAs into SAs as the

former mature. • Quality assurance within Activity.

!"#$%$%$C",458A850"D'*7')"

For each Activity, an Activity Leader will be nominated to coordinate all tasks by the Company/Research Institute responsible for the Activity. They will meet at least once every year (by means of the TEC meetings) to ensure program times, costs and resources are maintained. Their main tasks are:

• Flag any discrepancy immediately to the Technical Coordinator, and initiate corrective action for program deviations

• Prepare reports, and ensure the objectives and results of tasks within the Activity are achieved

• Ensure deliverables are available according to plan • Attend all relevant meetings, and in exceptional circumstances send a substitute, • Coordinate tasks for the nominated Activity • Arrange regular technical meetings as required for their Activity. • Ensure the horizontal information flow to other Activity Leaders.

!"#$%$%$E":*-F"D'*7')"

The Task Leader reports to the Activity Leader, coordinates technical work for his/her activity according to the project and Activity objectives, assists in the preparation of reports. In the project already at the proposition stage, responsibilities are well defined and participants to each task are identified, with their own responsibilities. Each of the partners has at least one task responsibility, and is coordinating the work done in this task. For example when one task corresponds to a common software development, the Task Leader is coordinating the development of the complete software.

!"#$%$#"42*.',53(-"

Below you can find a list of the operations carried out during the project.

!"#$%$#$%"G'48-82("H)24'--"*(7"42(I+845")'-2+@582("

Mandatory decision rules and agreements are necessary for the success of the project. The decision making process will follow the guideline to reach agreement as close as possible to



the level of execution. Only if agreement will not be reached on a given level, the decision will be escalated to the next appropriate level.

• Decision scope at task level: All partners being involved in a task are eligible to contribute to a decision regarding that certain task. In case a capable decision cannot be taken at this level, the issue has to be forwarded to the Activity Leader.

• Decision scope at Activity level: All partners being involved in an Activity are eligible to contribute to a decision with regards to this Activity. In case a capable decision cannot be taken at this level, the issue has to be forwarded to the TEC.

• Decision scope of Technical Executive Committee: All Activity Leaders are eligible to contribute to a decision in the TEC. In case a capable decision cannot be taken at this level, the issue has to be forwarded to the Project Coordinator.

Additionally, specific decision and corresponding voting procedures may be defined in the Consortium Agreement. However, it will be the general effort of all partners and all levels of decisions to achieve solutions representing unity and an overall agreement.

!"#$%$#$#"62..@(84*582("*(7"42++*/2)*582("522+-"

The project will put in place communication mechanisms supporting the structure including but not limited to: organisation meetings; planning and reporting documents, technical contributions originated by the partners and deliverables; collaboration tools such as wikis; project intranet for document repository to store and retrieve documents; video-conferencing and collaborative working tools.

!"#$%$#$<"1+*((8(J"*(7"K'H2)58(J"

Project planning and progress are documented in regular Management Reports and summarised in a Periodic Reports that will be written prior to every Review. These documents are produced by i2CAT, and compiled from inputs from the individual partners. The Management Reports contains information on the achievements and the corresponding resources used.

!"#$%$#$C"K8-F"*--'--.'(5"

The proposers have conducted a very thorough analysis of the risks (section B 1.3.5) connected with the execution of the project Activities, and affecting the eventual achievement of the project objectives. The Consortium has identified several risks for the execution of the project. The technical risks have been analysed oriented toward the Activities, and named after the Activity name (i.e. Rn.m is the m-th risk of WPn).

A number of risks have been identified during this process, and an assessment of the likelihood and impact on the project has been carried out on each of them. Preventive corrective actions have been applied on the structure of the work plan and the project consortium in order to mitigate or eliminate the most probable risks, and those with the most negative impact on the success of the project. Those risks that could not be completely



eliminated have been studied in detail in order to prepare a reasonable backup plan in case they occur.

!"#$%$#$E"L@*+850",--@)*(4'"

Quality shall not only be addressed for the deliverables but also for the Project process itself. The management process shall be submitted to periodical reviewing with respect to:

• Adequacy of the project management plan and how the work performed complies with it, including IPR management and results dissemination.

• How well the project processes are synchronized and inter-linked. • Identification and evaluation of activities and results that would adversely affect the

achievement of the project objectives. • Process improvement in the project by identifying deviations and changes.

Management will continuously monitor and control (i.e. taking corrective actions) expenses, resources and schedules versus plans. A list of precise success criteria for the project will be set-up and maintained during the project life.

Root causes for deviations, be it shortages or excesses, in costs, resources and schedules shall be identified, recorded and used as input for continual improvement.

Possible impacts of schedule changes on the budget and resources of the project and on the quality of the product should be determined.

To ensure consistent quality of each deliverable, a set of rules will be applied to the process of deliverable preparation:

• Each deliverable will have a lead partner responsible for proposing the general structure of the deliverables and assigning tasks to all contributors.

• The deliverable structure and assignment of tasks should be agreed inside the respective Activity and accepted by the corresponding Activity Leader.

• The input from all contributors will be gathered by the lead partner who is also responsible for editing the overall deliverable.

• The partner will also review the input from contributors to verify their quality and ensure the coherence and completeness of the whole document.

• In case of insufficient quality of the inputs or unacceptable delays in providing inputs, the lead partner should inform the respective Activity Leader as well as the project coordinator to trigger the appropriate management procedures.

• The complete deliverable must be approved by the Activity Leader and then by the Project Coordinator.

!"#$%$#$M"N*(*J'.'(5"2I"F(2O+'7J'"*(7"2I"P(5'++'45@*+"1)2H')50"

Due to the innovative aspects of MANTYCHORE, it is expected that partners will generate Intellectual Property that has to be protected through patents, yet made available for other



partners for their own work in the project, and exploited outside of the project by appropriate licensing.

The management of knowledge and IPR extends over the whole project duration with the main following objectives:

• Inventory and respect of the background brought by the MANTYCHORE partners. • Continuous monitoring of innovation throughout the project to scout. • Spot where potential intellectual property is generated and incites partners or groups

of partners to take appropriate measures (patent filing, etc.) • Orientate main knowledge advances towards the standardisation bodies once the IPR

protection is completed. A summary of the way that access rights and IPR will be handled in the project is given in section B 3.2.4: “Management of Intellectual Property”.

!"#$#"!*(*6505'.5*-"

!"#$#$%"!*(*6505'.7"%8"9/(1'05:"5#;<=">?#;<=@"

i2CAT Foundation (www.i2cat.cat) is a not for profit Spanish organisation founded by the UPC (Technical University of Catalonia –www.upc.edu) and the local government of Catalonia (Generalitat de Catalunya –www.gencat.cat). i2CAT Foundation is an experimental platform for collaboration in research and development of IT projects between the public and private sector. It performs research and innovation projects under the scope of the new generation of Internet.

UPC (the Technical University of Catalonia) is involved in MANTYCHORE as a third party affiliated to i2CAT, this relation is contemplated on the special clause 10. UPC is an external support for i2cat, in charge to carry out a part of the i2CAT tasks. The researchers from UPC are Xavier Hesselbach, Juan Felipe Botero and Lisset Diaz.

Relevant expertise / know how: Currently i2CAT is involved in three major European projects, both related to networking (among many others national ones). i2CAT is co-leading a work package of the IST FP7 FEDERICA project, which aims to build a European-wide network that can be sliced. The control of each slice can be assigned to a different user, scoped to researchers dealing with Future Internet projects. i2CAT is mainly in charge of the studies about network resource processes abstraction, in order to create different virtual/segmented slices of the experimental L3 network infrastructure. i2CAT is also participating in service activities (Tools to support multi-domain workflows) and joint research activities (Hybrid Network Provisioning, Monitoring, Network Factory and Composable Network Services) of the GEANT3 project, under a subcontract that takes 40% of the work of RedIRIS (the Spanish NREN). Finally, i2CAT is the overall technical leader and work package leader of the IST FP7 GEYSERS project (currently under negotiations), to



design and implement a logical infrastructure composition layer that allows infrastructure providers to provide network and IT infrastructure to service providers for assembling their dedicated logical networks. i2CAT was also the leader of work package 1 of the IST FP6 PHOSPHORUS project, a project that aimed to treat the network as a first class grid resource allowing unified provisioning of network and grid resources. Among other projects, i2CAT has participated in both UCLPv1 and UCLPv2 projects in partnership with the Communications Research Centre of Canada and the University of Ottawa, with the support of CANARIE Inc. Research under these two projects paved the way to the IaaS Framework (Infrastructure as a Service), an ongoing effort to define a framework for creating open source solutions enabling infrastructure resources as services to the user. The IaaS Framework will be the basis of Argia and MANTYCHORE, two solutions for delivering IaaS to optical and IP networks, respectively.

Role in the project: i2CAT is the Coordinator of the MANTYCHORE project and is in charge of all tasks in WP1 Activity (Project Management), being the only participant. Furthermore i2CAT participates in the other Network Activities (WP2 and WP3) collaborating in the dissemination tasks by means of through the participation in several standardisation bodies where i2CAT is working currently (OGF, IRTF and TMF). Moreover it will prepare the necessary manual and tutorials for the user training phase. In other aspects, i2CAT, as one of the IaaS Framework developers, will have the main role in the WP4 tasks (Software refinement), and it will participate during the deployment phase of the MANTYCHORE services (WP5) giving the necessary support. Eventually, it is leader of the Joint Research tasks (WP6 and WP7) , giving support for all the steps to the integration for the different related tasks.

UPC collaborates in the refinement of the MANTICORE tools and services (WP4 Activity) with 4 person-months.

6Q-"2I"F'0"H')-2(-"

Sergi Figuerola

He is the Coordinator of the Network Technologies Cluster of the i2CAT Foundation since 2004. He is graduated in Telecommunication Engineering by the Technical University of Catalonia (UPC, January 2002),and holds a Masters in Project Management from La Salle (Universitat Ramón Llull- 2004). He is currently also acting as Work Package leader 1 of the PHOSPHORUS project (EC IP FP6) and JRA1 co-leader of the FEDERICA project (EC IP FP7), and will be the technical leader and WP3 leader of the GEYSERS project (EC IP FP7, currently under negotiations), among its coordination of other national projects. From 2000 to 2003 he was involved in research at the UPC’s Optical Communications Group (GCO), and he is PhD candidate of the Signal Theory and Communications Department (awarded on 2002 with a PhDs fellowship by the Spanish Science and Education Ministry).

Eduard Grasa



Graduate in Telecommunication Engineering of the Technical University of Catalonia (UPC, July 2004) and Ph.D. (UPC, February 2009). In 2003 he joined the Optical Communications Group (GCO), where he does his thesis on software architectures for the management and control of sliceable networks. He has participated in several national and international research projects, including UCLPv1, UCLPv2, HULP, FP6 PHOSPHORUS, FP7 FEDERICA, DREAMS, HPDMnet, IaaS Framework. He is knowledgeable about several service oriented technologies (Jini/Javaspaces, OGSA, WSRF, Web Services, OSGi), network technologies (DWDM, Ethernet, SONET/SDH, IP) and management protocols (TL-1, CLI, SNMP, NetConf), and has 5 years of computer programming experience in Java.

!"#$#$#"!*(*6505'.7"#8"AB<(*,">AB<(*,@"

HEAnet (Dublin, Ireland) -- Ireland’s National Education and Research Network, providing high quality Internet Services to Irish Universities, Institutes of Technology and the research and educational community, including all Irish primary and secondary schools. HEAnet provides a high-speed national network with direct connectivity for its community to other networks in Ireland, Europe, the USA and the rest of the world. Established in 1984 by the seven major universities with the support of the Higher Education Authority to promote the interchange of information electronically within third level education, HEAnet plays a critical role in establishing Ireland as a global centre of excellence in Internet activity. HEAnet’s participation in MANTYCHORE will include Andrew Mackarel, Victor Reijs and Dave Wilson.

Relevant expertise / know-how: HEAnet Limited is the not for profit organisation that has operated the Irish National Education and Research Network since 1997. It is involved in many high profile networking projects both nationally and internationally and has experience building operational networks and services, careful management of public procurement projects, and participation in international research projects including GEANT2, GEANT3 and FEDERICA. It provides strong operational, technical and project management expertise as well as its history of innovating in the NREN area. Role in the project: HEAnet is the leader of the exploitation tasks in WP2, and it will collaborate during the users training phase and in the consolidation of the User Community. As NREN, it will have a direct collaboration in the specification of the MANTYCHORE tools and services requirements (T4.1) and in the deployment of MANTYCHORE services (T5.1). Currently HEAnet is collaborating with the GSN project, and for this reason, also it has been assigned as the leader of WP7, leading the T7.1. It will also contributes with the T7.3 by means of performing experiments to test, if the network migration implemented works correctly.

6Q-"2I"F'0"H')-2(-"

Andrew Mackarel



Andrew Mackarel has worked as Project Manager in HEAnet’s NetDev Group for the past two years. He has worked on several projects such as installation of New IP network and GEANT’s AutoBAHN Project. He has a keen interesting in Renewable Energy technologies. Previously Andrew has worked for Bells Labs and Lucent Technologies as Test Manager in their Optical Networking Group. Prior to joining HEAnet he was a Principal Test Engineer with Lucent and Ascend Communications and Stratus Computers. Andrew has over 25 years work experience in the Telecommunications and Computing Industries.

Victor Reijs

After studying at the University of Twente in the Netherlands, Victor Reijs worked for KPN Telecom Research and SURFnet. He was involved in CLNS/TUBA (one of the earlier alternatives for IPv6). Experience was gained with X.25 and ATM in a national and international environment. His last activity at SURFnet was the tender for SURFnet5 (a step towards optical networking). Emigrating to Ireland, he is managing the Network Development department of HEAnet and is actively involved in international activities such as GN3 and FEDERICA as well as (optical) networking, point-to-point links and monitoring in general.

Dave Wilson

Dave Wilson has worked for HEAnet, the Irish National Research & Education Network since 1996. Dave's work concerns planning of the national IP research network, including a close focus on areas such as BGP policy and IPv6, and he led the procurement and deployment of the latest iteration of this network. Dave also participates actively in a number of international fora, including RIPE, where he has been a working group chair, in GÉANT2 and GÉANT3 in areas of bandwidth on demand and virtualisation (with an eye to the interesting ways in which these interact with IP policy) and in the Irish IPv6 task force, which he helped to found and gain government support. Dave is a member of the ICANN ASO Address Council, having been elected by the membership of RIPE. He also contributes to other European projects including FEDERICA.

!"#$#$C"!*(*6505'.7"C8"D4EFG(*,">D4EFG(*,@"

NORDUnet is the regional research & education network for the 5 Nordic countries (Norway, Finland, Sweden, Denmark, and Iceland). NORDUnet has more than 25 years of history in state of the art networking for the research community, and has participated in numerous advanced international initiatives, including EU-funding initiatives. Recent initiatives include strong contributions to 6NET, GN2, GN3, and FEDERICA.

NORDUnet today has a fibre-and-DWDM core infrastructure providing lambda and hybrid networking services and a state of the art 10 Gbps IP network. In addition, NORDUnet hosts the Nordic Data Grid Facility (NDGF), an advanced facility for e-Science and grid computing, several high-level services for the research community, and is provides operations and management services through the Nordic University NOC (NUNOC). As such, NORDUnet is a provider of infrastructure for education and (e)-science.



Role in the project: NORDUNET will participate at different disseminations, exploitation, standardisation and liaisons tasks related with WP2. Furthermore, it has been assigned the leader of WP3 where it will be responsible to find new research communities and NRENs interested in MANTYCHORE. Regarding to SA activities, it will collaborate with the specification of use requirements. As well, it will coordinate the deployment phase of the MANTICORE services (WP5). Finally, NORDUnet will participate in the WP7 Activity, being the leader of the 7.1 task, and contributing with T7.2 and T7.3 tasks.

6Q-"2I"F'0"H')-2(-"

Lars Fischer

Chief Technology Officer – is responsible for leading development initiatives and projects within NORDUnet. He leads NORDUnet’s participation in European projects and initiatives, and its relationships with European NRENs and the European networking community. He also coordinates Nordic e-Infrastructure initiatives in collaboration with Nordic partners and works with Nordic advanced users of e-Infrastructure. Before joining NORDUnet in 2004, Lars spent ten years in the Internet and telecommunications industry as Technical Director at Tele2 and COLT Telecom. Before this, Lars carried out research into programming systems and collaborative computing environments. Lars has worked with advanced networking and computing systems for the past 25 years.

Per Nihlen

IP Network Manager – joined NORDUnet in 2007 after leaving a position as a network specialist at the Royal Institute of Technology. Per heads the NORDUnet IP team, which is responsible for the NORDUnet IP network and middleware development initiatives. He is also participating in several European Projects (Including GN3, Federica and MANTICORE). Per Nihlen’s expertise lies in the area of IP routing and MPLS network design.

Linus Nordberg

Software developer -- has a long background in designing and realizing software systems for a variety of technologies, including network equipment and security infrastructure. He previously worked at Net Insight, developing protocols and applications for their DTM systems.

!"#$#$H"!*(*6505'.7"H8"F*(+'.IJ-"?=K;*(,*."63."G11'((*L-*"3)"93.-I(5()">GD?K;@"

UNI-C, the Danish IT Centre for Education and Research, is a public institution under the Danish Ministry of Education. UNI-C provides a broad spectrum of ICT services for the educational and research community, and more than 500 000 users are in frequent contact with UNI-C’s products and ICT services. UNI-C has more than 300 employees, and offices in Copenhagen, Lyngby and Århus.



Relevant expertise / know-how: UNI-C has an extensive experience in developing and operating large e-Infrastructures as well as to train local operators in large networks. It operates the Danish National Research and Education Network (NREN), Forskningsnettet, as well as the Danish Internet Exchange Point D-IX, where most Danish Internet Service Providers exchange network traffic. UNI•C also developed and operates the Danish Health Data Network run by MedCom. As the operator of the Danish NREN, UNI-C has collaborated internationally with several of the members of the Consortium who also are responsible for NRENs: the University of Belgrade, AARNet and Informika (RUNNet).

Role in the project: UNI-C, as the coordinator of the Danish Health Data Network, represents a user group that will use the MANTYCHORE services; hence it also participates in the T4.2 task related with the use of MANTYCHORE services in virtual research communities. Finally UNI-C participates in tasks about dissemination and training in WP2 and WP3 activities.

6Q-"2I"F'0"H')-2(-"

Martin Bech (MSc)

He has been with UNI-C since 1986 where he has been a driving force in many pioneering projects: large-scale student computing facilities, firewalls and security, part of the first commercial Internet Service Provider in Denmark (in 1993), nation-wide services for schools in Denmark, the Danish Health Data Network and many other projects. Today, he is deputy director and responsible for the commercial IT services offered by UNI-C as well as the operation and development activities of the Danish National Research and Education Network.

Tangui Coulouarn

He holds a PhD in political science from the University of Paris I and is consultant at UNI-C where he works with international projects. His tasks include fund raising as well as project integration. Prior to joining UNI-C, he was engaged in teaching and research at different universities in France and in Denmark.

!"#$#$M"!*(*6505'.7"M8"G(5N*.-5,7"36"B--*O">GB--*O@"

The High Performance Networks group (HPNG: http://hpn.essex.ac.uk/) at the University of Essex specializes in the application of advanced technologies to future communication network infrastructures together with the study of control, node architectures, and technologies best suited for future requirements. The group consists of the following labs and experimental facilities:

• Photonic Network Lab (PNL)

• Networked Media Lab (NML)

• Future Internet Experimental Facility



PNL is extremely well equipped with transmission capabilities of 160 Gbit/s and switching testbeds for circuit, packet and burst switching. The Laboratory also has four full photonic switching nodes and 3 Carrier Grade Ethernet nodes, enabling a full captive network with photonic and electronic switching layers together with control software. Led by Prof Simeonidou a successful bid was made to JISC for a dark fibre network connecting Essex, Cambridge, London and Southampton to allow advanced networking experiments to be undertaken between these centres. This fibre network also supports connective with Europe and North America. The University has recently approved an investment of more than !2m to extend this activity with a new Networked Media Laboratory (NML) which operates as an interdisciplinary laboratory focused in research & development for efficient deployments of Ultra-High Definition Multimedia Applications over Photonic Networks.

The Group’s mission is realised by our commitment to research through the creation, advancement and facilitation of innovative multi-disciplinary photonic network research particularly in the fields of Optical Transport Networks (OBS, OPS, OCS, multi-granular and high speed systems and networks), Grid/Cloud Networking (Optical grids, Integrated management of IT and network resources, consumer Grids, cloud computing), Network and Service Management (architectural extensions, virtualisation technologies, service oriented and application aware networking), Network technologies and Architecture for Ultra High Performance media. HPN group is committed to a high standard by extensively publishing in selected highly-ranked journals and conferences and contributing to standardisation activities.

Relevant expertise / know how: The Group has a very strong collaborative profile and interacts with researchers and users in the UK, EU, US, Japan and China; many of these links were established due to the support offered by EPSRC platform grants. The Group has strong links with user Groups through EU projects such as BREAD (brings togEther users and technologists), EU Networks of Excellence such as ePhoton/One+ (FP6), BONE (FP7), Eurofos (FP7) and technology and network projects such as MUFINS, TRIUMPH, MUSE, PHOSPHORUS, DICONET, GEANT3, GEYSERS, STRONGEST and MAINS. The group has been core contributor to several EPSRC/DTI funded research: PLATFORM grant, OPORON, PRINCE, PROTAGON, SOAPS, UPC projects in collaboration with industry and other universities.

Role in the project: The HPN Group at the University of Essex plans to use its networked Ultra High Definition testbed in order to interconnect the JANET UHD special interest group infrastructure with MANTICORE and evaluate the JANET use case. Essex will also lead WP6: Infrastructure resources marketplace.

6Q-"2I"F'0"H')-2(-"

Dimitra Simeonidou

She is the Head of the HPN group at the University of Essex, UK. She joined Essex in 1998 (previously with Alcatel Submarine Networks). She is an active member of the optical networking and Grid research communities and participates in several national and European



projects and initiatives. Main areas of research are: photonic switching, ultra high-speed network technologies and architectures, control and service plane technologies for photonic networks and architectural considerations for photonic Grid networks. She is the author and co-author of over 250 papers, 11 patents and several standardisation documents.

Reza Nejabati

He joined University of Essex in 2001 and he is currently a member of Photonic Network Group at the University of Essex. His main areas of research are ultra high-speed optical networks, service oriented and application-aware networks, network service virtualisation, control and management of optical networks, high-performance network architecture and technologies for e-science. He has more than 60 publications in the area of optical networks and he has been editor of several standardisation documents.

Kun Yang

He received his PhD from University College London (UCL), UK and is currently a Reader in the School of Computer Science and Electronic Engineering, University of Essex, UK. Prior to this post, he worked at UCL on several European Union research projects. His main research interests include wireless networks, pervasive service engineering, and IP network management. He has published more than 100 papers in the above areas. He serves on the editorial boards of both IEEE and non-IEEE journals.

!"#$#$P"!*(*6505'.7"P8"=*L*6:(50'"?(N*-,5)'05:("7"F*-'..3LL3">=?F@"

Telefónica I+D (Investigación y Desarrollo) is the innovation company of the Telefónica Group. Founded in 1988, it contributes to the Group's competitiveness and modernity through technological innovation, and developing advanced products and services. It is the largest private R+D centre in Spain, and is the most active company in Europe in terms of European research projects in the ICT sector.

Relevant expertise / know-how: TID has participated in programs like RACE I, RACE II, ESPRIT II, ESPRIT III, TEN-IBS, TEN-ISDN, CTS, COST, EURESCOM, BRITE, ACTS, IST, Ten-Telecom, e-Ten, e-Content, EUREKA (ITEA, MEDEA & CELTIC. It currently collaborates with technological leaders and numerous organisations in 42 different countries - among which figure more than 150 universities located in different parts of the world. It also participates in the most important international forums on technological know-how, thus creating one of the largest innovation ecosystems in the ICT sector. Products such as the public phones in the booths currently used by Telefónica (1990), the large fixed and mobile network management systems (1990), data switches (1991), Internet access services (1996), developments for digital homes and connected cars (2000), the prepaid system for mobile phones (1999), interactive a la carte digital television (Imagenio) (2004), new services for television and the new business models on Internet (2006)... are just some of the projects the company has worked on. Over the last few years, within the global market Telefónica I+D has grown to become a network of centres of technological excellence extending its R+D activities to offices situated in Barcelona, Granada, Huesca, Madrid, Valladolid, São Paulo



(Brazil) and Mexico, while working for the companies in the Telefónica Group in the rest of Europe, America and Asia. In addition to the numerous technical awards it has won since its foundation, the company received the Príncipe Felipe Award for Business Excellence in 2002.

Role in the project: TID is in charge of carry out the study related to provide MANTYCHORE services in a commercial environment (delivered as D5.1), hence it will be collaborating with the NRENs in the deployments tasks in WP5 activity.

6Q-"2I"F'0"H')-2(-"

Cristina Peña Alcega

She got a degree in Telecommunications Engineer from the University of Zaragoza. She wrote her master thesis about Mobile IP and multicast advanced features of the IPv6 protocol in Telefónica I+D, which she joined in 2001. Main research is focused in NGN, mobile technologies, evolution of xDSL and their applicability to Rural Scenarios. She has worked in several EC funded projects related to IPv6 advanced mechanisms (IST FP5 LONG and Euro6IX) evolution of broadband access networks (IST FP6 MUSE and MUSE II), and new paradigms to improve communications in Rural areas by means of collaborative platforms and heterogeneous infrastructures (INTERRURAL and IST FP6 C@R).

David Ortega Abad

He got his degree in Computer Engineer from the University of Zaragoza in 2004. He joined Telefónica I+D in 2003, where he has been working in Network Management and IP Network Access Technologies departments. He has participated in several European research projects, including IST ATRIUM, @LIS E-LANE or CELTIC MADEIRA or IST C@R. He has been also involved in several projects dealing with Telefónica’s transport and access networks. He also collaborates as Associate Professor at “Escuela de Informática” of the “Universidad San Jorge” in Huesca (Spain).

Álvaro Cappa Gómez

He is Telecommunication Engineer from Universidad de Málaga. He joins Telefónica I+D in 1999 participating in the development of Intelligent Network services in mobile and fixed access networks. After that stage he starts working in the development of new functionalities for the voice mail service and enriched SMS notification service of Telefónica Móviles. Then he starts working with Telefónica Corporate helping at the coordination of the network deployments and provider selection among the different Telefónica business units. After participating in the OMA standardisation forum he starts to work at the European CELTIC project BOSS, regarding WiMAX and UMTS communication issues to improve the security of inside trains. Right now he works in the development of tecno-economics models for telecommunication operators.



!"#$#$Q"!*(*6505'.7"Q8"=.5(5,7";3LL*)*"F/RL5(">=;F@"

Trinity College Dublin (TCD) is the leading university in Ireland, ranked 13th in Europe and 43rd in the World by The Times Higher Educational Supplement global rankings 2009. The Department of Computer Science opened in 1969 and consists of over 60 academic staff, 35 research staff and 180 postgraduate students, recently amalgamated within the School of Computer Science and Statistics. The School hosts the Grid-Ireland OpsCentre that manages the Irish grid on behalf of Grid-Ireland (the Irish NGI, see http://grid.ie/).

Relevant expertise / know-how: Grid-Ireland has always run an independent national grid, integrated with EGEE. Hence it has always run top-level national grid services, and also runs top-level international grid services for some international VOs. It has an integrated deployment architecture, with a core infrastructure of fully virtualised “grid gateways” in 17 academic institutions in Ireland, that employs fabric management tools to automate deployment of middleware to these gateways and central services. It has its own helpdesk and user technical support.

TCD were the first to deploy EGEE Grid infrastructure servers on virtual machines. It operates significant virtualised testbeds for middleware certification, e-Learning, and experimental development, and is also working on tools for improved management of virtualized testbeds. It has been working on interoperability since 2004, and also now on bridging to multiple clouds. It has in-depth expertise in middleware, and has long experience in testing, certification and deployment of grid services. It began a Grid Middleware Porting Activity in Oct-2003, drawing on prior experience in porting code to Linux, Windows, Solaris and AIX from 1995 onwards. As the coordinator of the multiplatform and porting support in EGEE-II/III, TCD has touched into many areas of the gLite (SA3/JRA1), VDT and ETICS software development, see: http://grid.ie/autobuild/. TCD holds an unusual position in dealing with EGEE SA3, JRA1 and ETICS, coordinating portability, multiplatform support, and development QA (especially standards compliance).

Role in the project: the Grid-Ireland OpsCentre at TCD will be one of the MANTICORE users participating in NA: the dissemination task (T2.1) and the user training task (T3.2). But TCD will focus its efforts in defining use requirements (T4.1) and use and evaluate the MANTYCHORE services (T5.2).

6Q-"2I"F'0"H')-2(-"

Brian Coghlan

B.E., M.A., Ph.D, C.Eng. is a Senior Lecturer in Trinity College Dublin, leader of the Computer Architecture and Grid Research Group (CAG), and responsible for its grid activities. He is the Irish representative on the EGI Council, a founding Director of Grid-Ireland, Director of the Grid-Ireland OpsCentre, a member of the Institution of Engineering and Technology, and a Professional Chartered Engineer.



John Walsh

B.A.(Mod), M.Sc., is Grid Manager for Grid-Ireland. He is responsible for all its production infrastructure activities.

!"#$C";3(-3.,5/+"'-"'"ST3L*"

!"#$C$%"U/'L5,7"36",T*"03(-3.,5/+"

The partners comprising the MANTYCHORE consortium have all the necessary skills and proven expertises on the different topics addressed by the project, and well complement each other. The consortium represents an excellent mixture of research centres (i2CAT), commercial telco operators (TID), renowned EU universities (UEssex), and National Research and Education Networks (HEAnet, NORDUnet, UNI-C) profiles from throughout the Europe. This critical mass off partners has all the capabilities, commitments and balance to successfully pursue the mid/long-term MANTYCHORE vision about the new helpful services for the research community.

Fig. 18 MANTICORE Consortium Sectors

Figure 18 illustrates the different roles that the MANTYCHORE Consortium partners will play in the project. MANTYCHORE’s main goal is to allow NRENs to provide an innovative IP network service that allows users to build community-specific networks under their control. The consortium is composed by the critical mass of partners that will allow this goal to come true: i) i2CAT will integrate and enhance the tools to operate and use the IP network services leveraging the successful results from different projects (MANTICORE-II, IaaS Framework, Argia); ii) HEAnet and NORDUnet will deploy the tools in a subset of their networks and will provide IP network services to selected groups of users; iii) UNI-C, UEssex and TCD will use the IP network services provided by HEAnet and NORDUnet to improve their research activities (health, ultra high definition media and grids respectively and iv) TID



will analyse the IP network service operation and study the feasibility of providing commercial IP network services in an operator environment.

Fig. 19 European dimension of the MANTYCHORE consortium

The European dimension of the MANTYCHORE consortium is represented on Figure 19. There are two participants from Spain (i2CAT and TID), two from Ireland (HEAnet and TCD), two from Denmark (NORDUnet and UNI-C), and one from the UK (UEssex). Table 19 provides an overview of the expertise of each partner in the consortium and their main goals in the project; showing how the consortium members complement each other.

Partner Type Relevant Expertise Main goals in the project

i2CAT (Spain)

Software developer and integrator

• Part of the main developers of the IaaS Framework and Argia initiatives

• FEDERICA partner

• MANTICORE I and II partner

• GreenStar Network project collaborator

• Develop, integrate and support the tools required to provide the IP Network service

• Train e-Infrastructure providers and users on the tools utilisation

• Prototype an implementation of a infrastructure resource marketplace

• Participate on the joint experimentation with the GSN project

HEAnet (Ireland)

Public e-Infrastructure service provider (NREN)

• Irish NREN, provide operational services to support research customers. Testing UCLP/IaaS since 5 years.


• Green Star Network

• Deploy the MANTYCHORE tools on a subset of HEAnet’s network and provide the IP Network Service to selected users (TCD and some NOC usage).

• Extend the number of NRENs that provide IP network services (targeted initially are JANET and RedIRIS) and the number of



project collaborator

• FEDERICA and GN3 partner

user communities taking advantage of this service (like OSAmI-Commons)

• Collaborate on the specification of the requirements for the MANTYCHORE tools


NORDUnet (Denmark)

Public e-Infrastructure service provider (NREN)

• International Nordic NREN, provide operational services to support research customers


• Deploy the MANTYCHORE tools on a subset of NORDUnet’s network and provide the IP Network Service to selected users (initially the health data network represented by UNI-C)

• Extend the number of NRENs that provide IP network services (targeted initially are Janet and RedIRIS) and the number of user communities taking advantage of this service (like OSAMI-Commons)


• Collaborate on the specification of the infrastructure resource marketplace


UNI-C (Denmark)

Users: Health Research (hospitals network)

• Operators of the health data network

• Developers of the connection agreement software

• Use the IP Network Services provided by NORDUnet to create a private IP network under their control to connect private data sources of several Danish and Swedish hospitals together and make them accessible to authenticated and authorised researchers




UEssex (UK)

Users: ICT Research (high definition media)

• 4k/8k media research and experimentation

• Infrastructure management,

• MANTICORE II partner

• Use the IP Network Services provided by HEAnet (and later JANET) to create a dedicate IP network under their control to perform research about ultra high definition media (streaming, videoconferencing)

• Lead the research on infrastructure resources marketplaces

TID (Spain) Private e- Infrastructure service provider (commercial operator)

• International commercial operator

• MANTICORE II partner

• Analyze the operational deployment and use of the MANTYCHORE services at NRENs

• Study how the IP Network Services could be commercialized in an operator environment

• Participate on the research about infrastructure resources marketplaces

• Study the applicability of the techniques for building zero-carbon infrastructures to a commercial operator’s environment

TCD (Ireland)

Users: ICT Research (Grid)

• Independent national grid integrated with EGEE project

• gLite partner

• ETICS partner

• Use the IP Network Services provided by HEAnet to create a private IP network under their control that connects their remote grid sites


Table 20 Overview of the consortium and their experience related to the project goals

!"#$C$#"V/RK03(,.'0,5()"

There are no activities to be sub-contracted in MANTYCHORE project foreseen.



!"#$C$H"=T5.1"2'.,5*-"

UPC will be a third party of i2CAT. The following table briefly describes the UPC organisation, the key people involved in the project, the role they will play and the resources that will be made available to them.

Legal Name Universitat Politecnica de Catalunya, UPC, Design and Evaluation of Broadband Networks and Services (BAMPLA)

Legal Signatory Mgfc. Sr. Antoni Giro Roca, Rectorate of the UPC Agreement date April 2010 Effective as of Project official start date Profile The Design and Evaluation of Broadband Networks and Services

(BAMPLA) research group is part of the Telematics Engineering Department (ENTEL) at the Universitat Politecnica de Catalunya (UPC). The BAMPLA research group has more than seventeen years of experience and it is recognized as a consolidated research group by the Catalonian Government (2009 SGR 1475), and by the UPC itself. The research of the group focuses in the field of application design, transport protocols, traffic modeling, medium access protocols and IP network management of high speed networks. At present the group has more than twenty members. Since 10 years, the group started the research on access networks (HFC, xDSL, FFTH) using ATM, addressing problems related access protocols that are able to support different kinds of traffic (VBR, CBR, ABR and UBR), resource management at the head-end of the network (admission control, bandwidth distribution over the upstream channel) and the behavior of the network offering unicast and multicast services, with different services categories. Currently the group is working in the design of new access protocols for technologies like xPON and OBS. The BAMPLA group has proven experience in international research projects and it has participated in several European programs and projects. For instance, some of these projects are: ATDMA, Teleregions I, Teleregions II, Advanced and High Secure Mobile Platform (@DAN, IST 2001-2003), Provisioning and monitoring of optical services (PROMISE, Eureka Project 2003-2006), Emerging Networking Experiments and Technologies (E-NEXT, ISP 2003-2006), Lambda User Controller Infrastructure for European Research (PHOSPHORUS, IST 2005-2008), Federated E-infrastructure Dedicated to European Researchers Innovating in Computing network Architectures (FEDERICA, INFRA-2007-1.2.2) and Multi-Gigabit European Research and Education Network and Associated Services (GN3, FP7 I3). The group also takes part in some Networks of Excellence, such as the EURO-NGI (ISP 2003-2006) and its continuation in the EURO-FGI (IST 2006-2009) and EURO-NF (IST FP7-ICT-2007-1).

Role The role of the UPC is to bring our networking expertise and research background in WP4. UPC will participate in task 4.2 working closely with the i2CAT development team to deliver a comprehensive solution to provide a network comprising layer 1 to 3



technologies as a service. Budget Effort: 4 mm

Costs: 39.186 ! (10.3% of i2CAT’s costs) Requested EC contribution: 39.186 ! (10.7% of i2CAT’s requested EC contribution)

Participants Dr. Xavier Hesselbach is Associate Professor at the ETSETB. He received the M.S. degree in Telecommunications Engineering in 1994 and the PhD. degree in 1999, from the Universitat Politécnica de Catalunya (UPC). In 1993, he joined the Design, modelling and evaluation of broadband networks group in the Telematics Engineering Department of the UPC. His research interests include broadband networks (in particular MPLS), multimedia streaming services, streaming protocols in traffic interruption conditions, source rate control, internet and intranet services and Java and CORBA based applications. During the period 1994-2000 he has been working as Assistant Professor at the Department of Telematics Engineering, and since 2000 as Associate Professor at the same Department. He has been engaged in several national and international projects (such as COST293, RIU253, EuroNGI, EuroFGI, EuroNF). He is author on more than 50 national and international publications in conferences and journals and author or co-author of 4 books. He has been Information Systems Chair in Infocom 2006 and belonged to several program committees, such as Eunice’97 International Conference, the WIU253-2003 the Workshop on MPLS networks. Since 1991 he belongs to the Institute of Electrical and Electronics Engineers, Inc., IEEE. In 1994 he received the award from the COIT/AEIT of Spain for the best Master Thesis on Networks and Telecommunication Services. MSc. Juan Felipe Botero is a Ph.D student at the the Technical University of Catalonia, UPC, in Barcelona, Spain. In 2006 he received his Computer Science Degree from the University of Antioquia, Colombia, and the M.Sc. degree in Telematics Engineering in 2008 from the Technical University of Catalonia, UPC, in Barcelona, Spain. In 2008, he joined the Design, modelling and evaluation of broadband networks group in the Telematics Engineering Department. He have worked in several projects, such as "Digital Mobile Companion" in the Electronics Engineering department of the University of Antioquia in 2006, he also have been working since 2007 in the MANTICORE (Providing users with a Logical IP Network Service) project in the Telematics Department of the UPC. Lisset Díaz is a student at Technical University of Catalonia UPC and Pontificia Universidad Católica del Perú, both. She is engaged in the Manticore project from i2CAT Foundation and his Masther Thesis is entitled "Evaluation of GNS3 tool with connectivity to real routers". He has participated in the 2005 - Inter-University Research Event “Implementation of videoconferencing at the PUCP through



the peruvian NREN- RAAP". References (since 2006)

! "#$%&&%'()*+,- .#/)(0%1)2,- 3#45'6)&- 78+%- 69:)*2- 5;%0- 2+%- :)*<%2&-&%=>%?*%- )2- 2+%-5>2:>2- 6?2%0@)*%- 6?- '5)A-()')?*6?1- &20)2%16%&7#- B*25?-CDDE#-F5226?1+)9,-G?62%A-46?1A59,-CDDE#-

! H#$>%02),- I#J)A6''),- "#$%&&%'()*+,- .#/)(0%1)2,- K#.);%'5#- LMN2%?A%A-O>@@%0- 3):)*62P- Q''5*)265?R- Q- 9%2+5A- 25- S5T- &>::502- 5?- HJUT-?%2V50<&L#- T%'%*2%A- 35'59(6)?- I5>0?)'- 5@- 359:>2)265?#- I>?%- CDDE#-BTTF-WEXYZC[\W#-

• H#$>%02),- "#$%&&%'()*+,- .#/)(0%1)2#- 7Q?- Q::05)*+- 25- K:2696])265?&-U6?<&-G26'6])265?- 6?-HJUT-F%2V50<&L#- B33^B_DE#- BMMM#-Q>1>&2-WZ\,-CDDE-O>*+)0%&2,-.59)?6)#-

! `);6A- Q?1>%0),- ");6%0- $%&&%'()*+- LQ- S>%>%- T6]%- Q::05)*+- @50-J05;6A6?1-S5T-6?-HJUTZ`6@@&%0;-()&%A-F%2V50<&7#-a^FER-b-a50<&+5:-6?-^cHJUT-?%2V50<&#-WCZW\-Q:06'-CDDY,-^605?),-T:)6?#-

! H5?6*)- $>%02),- ");6%0- $%&&%'()*+,- .)95?- /)(0%1)2,- I+5?- J)A6''),-K&V)'A5- .);%'5- )?A- .51%0- 3'52%2- 7H6?696])265?- 5@- 35?1%&265?- 6?-HJUT- F%2V50<&- (P- 9%)?&- 5@- /'5V&- K:2696])265?- 8%*+?6=>%&L- BMMM-U)26?-Q9%06*),-T%:2#-CDDY-;5'-X,-6&&>%-X#-

! T%0165-H)*+)A5,-I);6%0-K]5?-)?A-");6%0-$%&&%'()*+#-T20>*2>0%A-J%%0Z25ZJ%%0-F%2V50<- @50- U6;%Z35?2%?2-`6&206(>265?#- UF3T#-b5'#- d[DEcCDDY-7K?- 2+%- H5;%- 25- H%)?6?1@>'- B?2%0?%2- TP&2%9&- CDDYR- K8H- CDDY-a50<&+5:&7#-BTOF-eY[Z\ZXdDZYE[[eZD-

! M#- ^0)&),- "#- $%&&%'()*+,- T#- /61>%05'),- b#- .%6f&,- `#-a6'&5?,- I%)?ZH)0*-G]%,- U)0&- /6&*+%0- )?A- 859)&- A%- H61>%'#- 78+%- HQF8B3K.M- :05f%*2R-J05;6A6?1- >&%0&- V62+- )- U516*)'- BJ- F%2V50<- T%0;6*%L- 8%0%?)- 8F3#-O0>11%&,-O%'16>9#-H)P-CDD[#-

! ");6%0-$%&&%'()*+,-Hg?6*)-$>%02)-)?A-.5A5'@5-Q';6]>#-7T20)2%1P-@50-BJ-20)@@6*- &>::502- V62+- S5T- 6?- KOT- ?%2V50<&L- B38KF- CDD[#- Q2+%?&,-^0%%*%#-

! I#/#O52%05- )?A- "#$%&&%'()*+- 78+%- O522'%?%*<%A- b602>)'- F%2V50<-J05('%9- 6?- O)?AV6A2+- Q''5*)265?- @50- F%2V50<- b602>)'6])265?L- BMMM-U)26?*599-CDDe#-

! I#/#O52%05,- "#$%&&%'()*+- 7K:2696])265?- H5A%'- @50- O)?AV6A2+-Q''5*)265?- 6?- )- F%2V50<- b602>)'6])265?- M?;605?9%?2L- />2>0%- B?2%0?%2-Q0*+62%*2>0%&RF%V-80%?A&- 6?- T%0;6*%-Q0*+62%*2>0%&#- T)?2)?A%0,- T:)6?,-CDDe#-

! H)06)?)-M&*5')0,-");6%0-$%&&%'()*+-7.5>26?1-V62+-J0650626])265?-O)&%A-5?-T2)26&26*&-6?-KOT-F%2V50<&L-BMMM-B38KF-CDDe,-Q]50%&,-J502>1)'#-

! "#$%&&%'()*+,- I#Q#^)0*h)ZM&:h?- 7Q- ?%V- )>25Z:05;6&65?%A- &=>)2Z()&%A-20)@@6*- 9)?)1%9%?2- &20)2%1P- @50- 9>'26*')&&- ?%2V50<&L- M>05F/-a50<&+5:- 5?- 80)@@6*- H)?)1%9%?2- )?A- 80)@@6*- M?16?%%06?1- @50- 2+%-/>2>0%-B?2%0?%#-J)06&,-/0)?*%-CDDe#-

! I#/#O52%05,-"#$%&&%'()*+#-7K:269)'-H)::6?1-5@-b602>)'-F%2V50<&-V62+-$6AA%?-$5:&-7#-8%'%*599>?6*)265?-TP&2%9&-I5>0?)',-CDWD#-

Table 21 UPC description

!"#$C$M"4,T*."03/(,.5*-"

No partners from countries outside Europe are requesting EU funding.



!"#$C$P"<115,53('L"2'.,(*.-"

No additional partners are foreseen in the MANTYCHORE proposal.

!"#$H"E*-3/.0*-",3"R*"03++5,,*1"The MANTYCHORE resources are analysed below in terms of effort (person-months) and money. This section describes this analysis from a full duration of the project perspective, emphasizing the different resource allocations among MGT, COOR, RTD and OTH activities and detailing expenditures on travels, costs and equipment. The overall budget figures are the following ones:

• Total cost of the project: 1.506.204 ! • Requested EC contribution: 1.399.744 ! (93%)

Figure 20 illustrates the cost distribution of the project. The majority of the personnel costs come from service activities, the main focus of the project. The project’s philosophy is that NRENs provide their own equipment to support the IP Network services provided through MANTYCHORE tools, which is reflected in the equipment costs: just 2.8% of the total project costs and mainly dedicated to acquire Ethernet switches to connect the end users to the NRENs.

Fig. 20 MANTYCHORE cost distribution

The travel costs have been minimised (5.6% of the project total costs) through the anticipated use of conference calls, videoconferencing and the exploitation of meeting in conjunction with other events where several of the partners will be participating anyway. However, some amount of travel is required and important, especially for the networking activities dedicated to disseminate the project results (WP2) and to consolidate and expand the NREN and user communities (WP3).

Management costs have been kept as low as possible (5.3% of the costs –including the associated overhead- and 5.7% of EC contribution) to ensure that there is enough manpower



to perform appropriated management activities (planning, reporting, quality assurance, conflict solving) in a project with 7 partners without imposing a cumbersome structure.

!"#$H$%"B;"03(,.5R/,53("3("&'(')*+*(,W";33.15(',53(W"E=F"'(1"4,T*."'0,5N5,5*-"

In accordance to the reimbursement rates in FP7, the EC contribution has been calculated on the following basis:

Fig. 21 MANTYCHORE distribution of EC Contribution

• WP1 (MGT) is reimbursed at 100%

• WP2 and WP3 (COOR) are reimbursed at 100% (taking into account that indirect costs are maximum 7% of the direct eligible costs)

• WP4 and WP5 (OTH) are service activities and reimbursed at 100%

• WP6 and WP7 (RTD) are reimbursed at 50% for large non-public organisations, and at 75% for: non-profit public bodies, secondary and higher education establishments, research organisations and SMEs.

!"#$H$#"B663.,"15-,.5R/,53("5("*'0T"'0,5N5,7"

Figure 22 illustrates the effort distribution in the different activities of the project. SAs concentrate the highest amount of manpower (61%), showing that providing MANTYCHORE managed IP network services to research communities is the main goal of the project. WP5 is the activity that requires more effort (36%) because it involves the deployment of the MANTYCHORE software at HEAnet and NORDUnet, the operation of the IP network service and the use of it by 3 different research communities: health (UNI-C), grid (TCD) and high definition media (UEssex). SA1 will provide the software tools required by the NRENs to manage the service and the user interface for end users. Even though the effort of creating such a tool is big, WP4 is an integration activity that will leverage the results from the MANTICORE II project and the IaaS Framework initiatives; therefore 25% of the project manpower is an adequate effort to successfully carry out this activity.

JRAs have been allocated 20% of the project effort showing that, although not being the central objective of the project, their results will be very valuable for the improvement of the



IP Network service; both in terms of enhanced flexibility to request infrastructure resources (WP6) and of improving the environmental sustainability of the supporting e-Infrastructure (WP7).

Fig. 22 MANTYCHORE effort distribution per activity (%)

Finally NAs contribute with 22% of the project effort; ensuring that enough work is carried out to i) correctly manage the project lifecycle, ii) the project results are disseminated and exploited, contributing to standards where appropriate and liaising with relevant projects, and iii) consolidating the user community through training activities and making it grow by looking for new IP network service providers and research communities.

!"#$H$C"X'.,(*.-"5(KI5(1"03(,.5R/,53(-"

!"#$C$<$%"B>,('5"

A summary of the Project budget (not funded by the EC) for HEAnet’s MANTYCHORE activity includes setup of a MANTYCHORE capable experimental core network and the use case projects. The total amount of HEAnet’s in-kind contribution is around 160,000 !.

Concept Item Cost

MANTYCHORE HEAnet Core Network 82,000 !

MANTYCHORE Virtual CPE 5,000 !

MANTYCHORE Alternative IP Services 1,000 !

Capital budget

MANTYCHORE Grid Ireland Connectivity

4,000 !



GSN related activities 28,000 !

TOTAL 120,000 !

HEAnet Core Network 14,000 !

MANTYCHORE Virtual CPE 1,000 !

MANTYCHORE Alternative IP Services 1,000 !

MANTYCHORE Grid Ireland Connectivity

4,000 !

GSN related activities 20,000 !

Expense budget

TOTAL 40,000 !

Total in-kind contribution 160,000 !

Table 22 HEAnet in-kind contribution

!"#$C$<$#"RSKGT('5"

NORDUnet will offer access to the NORDUnet core network and access to partner networks and institutions. Access will be provided on shared IP, dedicated circuit networks, and on experimental dynamic circuit network resources as appropriate.

!"#$H$H"B663.,-"63.",T*"6/LL"1/.',53("36",T*"2.3Y*0,"

The following table shows the detailed breakdown of the person months per partner in each of the Activities is shown in the following table.

i2C

AT

HE

Ane

t

NO

RD

Une

t

UN

I-C

UE

ssex

TID

TC

D

TO

TA

L

MGT Activities

WP1: Project Management 10 0 0 0 0 0 0 10

Total MGT Activities 10 0 0 0 0 0 0 10

COOR Activities

WP2: Dissemination, Exploitation, Standardisation

1.5 1.5 1.5 1.5 1.5 1.5 1.5 10.5



and Liaisons

WP3: Consolidating the user community and users training

3 1.5 3 0.5 0.5 0 0.5 9

Total COOR Activities 4.5 3 4.5 2 2 1.5 2 19.5

OTH (Service) Activities

WP4: MANTICORE software refinement

28.5 1 3 2 2 0 3 39.5

WP5: MANTICORE services for virtual research communities

3 5 8 8 8 5 19 56

Total OTH(Service) Activities

31.5 6 11 10 10 5 22 95.5

RTD Activities

WP6: Infrastructure resources marketplace

2.5 0 1.5 0 9 4 0 17

WP7: Zero-carbon emissions e-Infrastructures

5 2.5 5 0 0 2 0 14.5

Total RTD Activities 7.5 2.5 6.5 0 9 6 0 31.5

TOTAL ACTIVITIES 53.5 11.5 22 12 21 12.5 24 156.5

Table 23 MANTICORE effort (pm) allocation to the different project activities



!/#$%&',0+$

!"C$%"V,.',*)50"5+2'0,"The MANTYCHORE project focuses on deploying its tools at the NRENs, so that they can deliver an IP Network Service to the European user research community. The following picture shows graphically the flow of impacts since the MANTYCHORE project starts:

Fig. 23 The flow of Impact from MANTYCHORE into the European society and economy

• First the MANTYCHORE services are deployed at HEAnet and NORDUnet, delivering them to a reduced part of the European user research community, the MANTYCHORE User Community. This community will start with three user groups (described in the 1.1.2 section), so the impact is small compared to targeting the whole European research community. At this point, the industry is also interested in MANTYCHORE, the telecom Spanish operator, Telefónica I+D, is in charge of studying the viability of porting MANTYCHORE tools and services into the industry environment. Furthermore two device vendors like Juniper and Cisco are also supporting the MANTYCHORE FP7 project, and are already involved in the MANTICORE II project.

• During the project lifetime, the MANTYCHORE consortium will dedicate efforts to expand the ecosystem of providers (other NRENs and even commercial operators in the long run) and users (other members of the European research community) that can benefit of the tools provided by MANTYCHORE; thus increasing the impact of the project results.

• On the other hand, a second line of exploitation is open, consisting in porting the MANTYCHORE tools and services to the European ICT industry, because it is the way to achieve a strong impact on the European society and economy.

• Finally, the increased effectiveness of European researchers thanks to the services offered through MANTYCHORE causes their research to deliver higher quality results in less time, impacting the European Industry (ICT and other areas) and, at the long run, the European society and economy.

Therefore the MANTYCHORE project can potentially have a deep impact over NRENS, European research groups, the ICT industry and the European society and economy with respect to the relevant points of the INFRA-2010-2 Work Programme for Objective 1.2.3:

1. Increased effectiveness of European research through the broader use of e-Infrastructures by research communities.



2. The emergence of virtual research communities of European and international dimension that cannot be achieved by national initiatives alone.

3. Easier development and adoption of standards, common tools, procedures and best practices.

4. Use of e-Infrastructure services and tools by actors from new disciplines and scientific communities.

5. Increased quality and attractiveness of e-Infrastructures. The following table shows the relation between the MANTYCHORE impacts and the work programme expected impacts:

Impacts on the European NREN community WP

impact nº

Efficient management of their e-Infrastructure: MANTYCHORE tools offer a management system which allows a simple, scalable and agile management of several physical and logical devices at level 1, 2 and 3. These tools are based on the IaaS Framework which offers a programming model, modular runtime environment and a set of libraries to develop IaaS management solutions. This allows developers to improve the existing IaaS Framework based tools or to create new ones in an easy way, reducing the development time.

5, 3

More dynamic and flexible e-Infrastructures: the IaaS based services allow adapting IP networks to the user requirements in an agile way; users can change service characteristics in an automated fashion – without requiring the participation of the service provider.

5

Reduction of operational costs (OpEx): NRENs can assign permissions to users to have control over the infrastructure resources, so that they can perform simple configuration tasks; thus lowering the NRENs operational costs.

5

Optimize use efficiency: MANTYCHORE tools are compatible with the virtualisation mechanisms of physical devices. Thus, researchers could share the same physical device at the same time, leaving available the unused ports or cards to create another virtual instance, improving the efficiency of use.

5

Minimizing the CapEx costs: the fact that virtualisation allows managing the same physical device by different users, reduces the necessity to buy new equipment when the demand of infrastructure grows up. Thereby, the use of the existing e-Infrastructures will be enhanced.

5

Infrastructure sustainability: MANTYCHORE research on the viability of e-Infrastructures powered by renewable energy sources has the potential to improve the infrastructure environmental sustainability, even more if CO2 emission quotas are imposed to organisations.

5



Provide new services over its e-Infrastructures which enhance the quality and potential of tools available for European researchers, bringing closer the European user research community and the NRENs.

1, 5

Impacts on the European research community

The MANTYCHORE tools and services provide the capacity to bring together all the e-Infrastructure resources from European NRENs, unifying the access to these ones by using a single mechanism: the Infrastructure marketplace.

1, 2

MANTYCHORE tools offer to users the capacity to manage remotely the infrastructure resources and IP networks as if they were the owners of the physical devices. This fact achieves reducing the time to deploy new network requirements, because the users are able to configure each device without the participation of the NREN network administrator.

5

Infrastructure resources as a service: customers only pay for the use of resources, and they don’t have to waste their budget in buying equipment that is difficult to amortize.

1, 5

Improve the European research: researchers will be able to validate their ideas over customized e-Infrastructures according to their needs. In fact, the MANTYCHORE User Community starts with three user groups that already leverage the benefits of MANTYCHORE tools and services.

4

Thanks to IaaS services, researchers can get quicker infrastructure and connectivity resources achieving faster innovation cycles.

5

Impacts on the European ICT industry

Telefónica I+D will achieve awareness about the benefits of the services based on IaaS combined with the virtualisation properties of physical devices.

5

The implantation of IaaS services over infrastructures will promote the apparition of virtual operators, thus increasing the competition and lowering the prices of ICT services.

5

Impacts on the European society and economy

The contributions done on the research about carbon neutral e-Infrastructures may result in a future scenario where all the energy consumed by networks and data centres is free of CO2 emissions. This way, the overall CO2 emissions will be reduced, decreasing the effect of the climate change and increasing the European citizens’ quality of life.

5

Thanks to the proliferation of virtual operators, the prices in the market related to the ICT services will be reduced.

5

The increased effectiveness of European researchers thanks to the MANTYCHORE tools will cause the science “time-to-market” to decrease,

1



enabling the European society to benefit from the scientific research in a shorter timeframe.

Table 24 MANTYCHORE Impacts

!"C$%$%"V,*2-",T',"S5LL"R*"(**1*1",3"R.5()"'R3/,",T*-*"5+2'0,-"

1. Develop robust tools and services to be deployed at NRENs as new operational services: When the MANTYCHORE project starts, the available MANTYCHORE tools are the result of the development done in the MANTICORE II project. But during the MANTYCHORE project these tools will be adapted and refined according to the requirements of the NRENs and user groups. To further enhance the capabilities and the scope of the MANTYCHORE layer 3 services, the MANTYCHORE tools will be integrated with the Ether (IaaS based services at level 2) and Argia (IaaS services based at level 1) systems. !

2. Find several NRENs willing to deploy MANTYCHORE services and provide them to virtual research communities: MANTYCHORE will start with deployments and pre-operational tests at two NRENs: HEAnet and NORDUnet. During the project some resources will be spent in continue looking for new NRENs willing to try the MANTYCHORE tools and provide IP Network Services to researchers, because the more NRENs deploy MANTYCHORE services, the more attractive it will be for end users (because they can create dedicated IP networks integrating resources from various NRENs). RedIRIS and Janet have already expressed their interest to try MANTYCHORE through letters of support. !

3. Find several research user groups to form a consolidated MANTYCHORE User Community that uses and take profit of the MANTYCHORE services: The project starts with three user groups: the Danish HDN (Health Data Network), the Advanced High Quality Media Services research group in the UK, and the Irish Grid Community. The idea is start the project with a few user groups forming the MANTYCHORE User Community, and continue growing the community during the project. !

4. Evaluate MANTYCHORE services on the part of NRENs and research groups to refine the MANTYCHORE tools and services: MANTYCHORE tools and services will be used by real users by the first time, so it is possible that some errors can appear during the operational phase. In this case, the MANTYCHORE development team will put all its effort in fixing all the bugs and errors that may appear. The objective is to refine MANTYCHORE tools and services to become strong and robust to be operated by real Infrastructure Providers like NRENs and be used by real users like researchers, going beyond of a simple proof of concept. !



5. Develop and implement a marketplace to bring together all infrastructure providers and customers: MANTYCHORE services offer the possibility to create several independent IP networks using resources from different e-Infrastructures. The problem is, when this happens, a user group must contact with each NREN that provides resources, and negotiate a certain level of service (SLA). Infrastructure marketplaces are a solution to make more dynamic and simplify the search for resources and the SLA negotiation process. In a marketplace all NRENs can publish their available e-Infrastructure resources, and research user can browse and select the combination of resources that better suits their needs.

6. Do a good dissemination of MANTYCHORE to reach a relevant amount of the

research and scientific community, showcasing its benefits for European research: Dissemination is an important part of the project if MANTYCHORE has the intention to become a well-known project in the European research community. Assisting to workshops and events like TERENA is a good way to show how MANTYCHORE services can benefit NRENs and the research community. !

7. Migrate MANTYCHORE services to the industry to reach the European society beyond the research community: Once MANTYCHORE has proved that their services and tools are beneficial for NRENs and the research community, it will be the time to port it to the industry, because is the way to arrive to the European society. To perform this step several studies will be needed, studies about the viability of MANTYCHORE services in the industry, for instance, how it can be beneficial for telecom operators. Before the project ends, these studies will be done.

!"C$%$#"<11*1"N'L/*"36"S3.I5()"',",T*"B/.32*'("L*N*L"

Working at a European level is essential for the development of the MANTYCHORE project because of the following main reasons:

• The MANTYCHORE project has the intention to have an impact to the European researchers, if the MANTYCHORE services were deployed at national scale, for example only at HEAnet, only the Irish research community could benefit of this European action. And the investment done should see reflected at all European research community.

• The MANTYCHORE project also tries to bring together the European NRENs community and the European user research community. Our tools, services and marketplace will open widely the access of NRENs’ e-Infrastructures to the European researchers. Therefore, it is nonsense to treat MANTYCHORE as national initiative alone. It is required the participation of the whole European research community, and the MANTYCHORE project is the start point to achieve this rapprochement.

• Finally, MANTICORE I (Proof of concept) and MANTICORE II projects have achieved the attention of several European funded project like FEDERICA and



GEANT, two projects with an EU scope, where it would be interesting port the results of the MANTYCHORE project to their e-Infrastructures. This way, thanks to the foreseen EU scope of MANTICOREI and II, the MANTYCHORE project is already start impacting to the European research community.

!"C$%$C"?+2'0,",3"3,T*.".*-*'.0T"'0,5N5,5*-"

MANTYCHORE tools and services aim to be helpful for the European research community, this involves not only the European NRENs, but also involves all the European research projects related with the MANTYCHORE objectives or simply projects which find MANTYCHORE a useful tool to enhance the quality of their research activities.

The following table explains the foreseen collaborations of MANTYCHORE with other projects.

Project MANTYCHORE contribution

GEANT3 FP7

The connections among NRENs e-Infrastructures are managed by GEANT2. These connections are necessary for the viability of the MANTYCHORE project, because we need all the NREN’s e-Infrastructures connected together, and thus, researchers will be able to create customized IP networks using resources from different NRENs. Furthermore, it is expected a collaboration between GEANT3 and MANTYCHORE where it would study the possibility to port MANTYCHORE services to become new services of GEANT3.

FEDERICA FP7

The results achieved in the MANTYCHORE project may contribute to the future evolution of FEDERICA (FEDERICA II). Actually, in FEDERICA I, an extended version of MANTICORE I (Proof of concept) has been used as the main software to manage the resources on the FEDERICA e-Infrastructure.

OSAmI-Commons

MANTYCHORE services would help to OSAmI-Commons project by means of the creation of customized IP networks where it can be used as demonstrators for the OSAmI-Commons activities. Thanks to the IaaS based MANTYCHORE services, these demonstrators would be created and reconfigured by themselves according to the requirements in that moment, accelerating and making more dynamic the process.

CLARIN CLARIN project would be interested in being a new user for MANTYCHORE services to manage in an efficient way their infrastructures, achieving a better service quality towards their users.

GreenStar Network

GreenStar Network (GSN) is not a European project but MANTYCHORE will collaborate with them during the project because is a really interesting initiative. The GSN Consortium is interested in use the MANTYCHORE tools and services to allow the creation of IP networks that can be



reconfigured easily. Moreover, during the project is foreseen to collaborate in the exploration of new technical challenges about integrating renewable energy sources in networks.

Table 25 Projects related with MANTYCHORE

!"C$%$H"<--/+2,53(-"'(1".*L*N'(,"*O,*.('L"6'0,3.-",T',"1*,*.+5(*"5+2'0,"

Risk/Factor Action

No new user research groups or NRENs are

found

It is possible that no new user group or NREN wants to join to our initiative. However NORDUnet and HEAnet have already detected some user groups interested in the benefits provided by MANTYCHORE services; and will continue actively looking for new-interested organisations.

The use of the MANTYCHORE

services is very low

The MANTYCHORE consortium includes 3 user groups with a high-expected use of MANTYCHORE services. Nevertheless if these groups don’t use the services, it will potentiate the effort to find a useful case for these groups.

NRENs don’t have enough infrastructure

resources

The e-Infrastructure resources where the MANTYCHORE services are deployed are not funded by EC. It would be possible that if the MANTYCHORE user community grows up quickly, they don’t have enough resources to deliver to users. To avoid this risk NRENs will study what resources should be dedicated to MANTYCHORE project, considering the scenario of a fast growing user community. If this situation happens, one solution would be to start charging the users.

The ICT industry is not interested or project is

not feasible

It would be possible that our initiative doesn’t fit in ICT industry. Several companies like TID, Juniper or Cisco are already interested and give support to continue researching in this direction.

Table 26 External factors

!"C$#"XL'("63.",T*"/-*."'(1"15--*+5(',53("36"63.*).3/(1"

!"C$#$%"F5--*+5(',53("<0,5N5,5*-"

A structured plan for dissemination will be implemented during the MANTYCHORE project in order to support an effective sharing of the results within the partners, as well as across external research communities. The partners are currently actively participating in the most relevant research forums and cooperating in projects and have experience in organizing and managing successful dissemination activities. Results obtained in the MANTYCHORE project will be channelled through the routes described in the Table below.

Activity Planned Results Main Target Group



Web Presence Web site, YouTube, videos Industry, Academia, Media, Public at large

Scientific papers on magazines

IEEE Network, IEEE Communications Magazine, Springer Computer Networks, Springer Computer Communication

Acad.

Conference papers

IEEE Infocom, ACM Sigcomm, IEEE Globecom Acad. Indus.

PhD and MSc thesis

1-2 PhDs, 1-2 MSc thesis Academia

Articles in professional journals

NetworkWorld, LightReading Indus.

Conferences , Workshops and seminars

TERENA Networking Conference, Future Internet Assembly (FIA), HEAnet conference, NORDUnet conference, GLIF meetings

Acad, Indus

Press releases Press release to showcase important results Aced, Indus, media

Table 27 Dissemination activities

The project will plan activities adequately resourced devoted to dissemination for specialised constituencies and general public, in particular for awareness and educational purposes. The dissemination plan deliverable has to consider adequate messages about the objectives of the project and its societal and economic impact. The tools to be used should include web-based communication, press releases, brochures, booklets, multimedia material, etc. The 'dissemination material' should be regularly updated to provide the latest version of the project status and objectives. Electronic and/or paper versions of this 'dissemination material' will be made available to the Project Officer beforehand for consultation and upon its final release.

!"C$#$#"BO2L35,',53("2L'("63."/-*"36"2.3Y*0,".*-/L,-"

Taking into account the MANTYCHORE consortium (infrastructure providers, network operators, research centres, universities), the exploitation of results in MANTYCHORE will address research community, industry community and finally the user community. The exploitable results are:

Exploitable Results Potential Exploiters

Description

MANTYCHORE software and user manuals

i2CAT, HEAnet, NORDUnet, UNI-C, TCD

The implemented software and its manuals will be used for NRENs and end users for its daily use. The MANTYCHORE software will be deployed at the NRENs and end users, and



the user manuals will be the necessary support.

Report on the feasibility of MANTYCHORE services in a commercial environment (D5.1) and business plan of the MANTYCHORE software (D2.5)

i2CAT,TID

Telefónica (TID) and i2CAT will be interested in the results of the studies performed in order to specify the feasibility of deploying MANTYCHORE in a commercial environment. They will profit from this information to find a commercial exploitation for MANTYCHORE product.

Infrastructure marketplace mechanism study and implementation (D6.1, D6.2)

i2CAT, HEAnet, NORDUnet, UEssex

This designed infrastructure marketplace in the D6.1 will explain the different possibilities to create an infrastructure marketplace. Furthermore, its implementation provides a solution that the partners will be able to reuse for their objectives.

Networks migration tests report (D7.2)

i2CAT, HEAnet, NORDUnet

The final report (D7.2) will collect the information of the experiments results and conclusion. I2CAT will incorporate the resulting mechanisms in the MANTYCHORE tool and HEAnet and NORDUnet may continue internal research on how they could become carbon-neutral.

‘know-how’ of partners and end users

i2CAT, HEAnet, NORDUnet, UNI-C, TCD, UEssex, TID

All the acquired experience of the partners and users will be exploited by continuing the operation of the services, transitioning to a fully operational phase; and deploying them in a commercial operator environment.

Table 28 MANTYCHORE Exploitable results

!"<$#$#$%"1*)5(')-"'?H+285*582("8(5')'-5"

For the magnitude of the solution, there are many different exploitation opportunities with great potential. The members of the MANTYCHORE consortium have a concrete commitment and well defined, though provisional, exploitation plans. These are briefly summarized in the following table.

Partner Exploitation Statements



i2CAT

i2CAT will establish different exploitation agreements with integrity entities. These entities will be responsible of: marketing and promotion of the product; installation and integration of MANTYCHORE service in user infrastructures. These entities will provide technical support to fix incidences and client requests. In this marketing model, I2CAT will provide to integrity entities: transference of ‘know-how’ knowledge; it will give support to technical problems to level 3 (MANTYCHORE services) which entity integrity cannot fix it; support for the development of new features in MANTYCHORE. i2CAT will contact with different technologic consultants and show them the new features and advantages which MANTYCHORE service provides. Finally, the objective is that the technologic consultants are to act like advisors of our software. Furthermore, it will try to establish new contacts with new possible advisors. These advisors are specialized consultants in the scope of the telecommunications and operators which have important participations at installation, deployment and optimisation of the telecommunication operators.

HEAnet

HEAnet plans to exploit the results of the MANTYCHORE: • HEAnet has concrete plans to virtualise the expensive Customer Premises

Equipment that is currently required to provide a managed IP service to its clients. MANTYCHORE will allow it to roll out this service in a manageable and scalable way, and allow it to delegate management of the logical routers to individual customers or retain management of it, at the customer’s discretion.

• HEAnet also has a number of alternative IP networks that are based on the same underlying infrastructure as its main network, but require a separately managed network of IP equipment. MANTYCHORE will allow HEAnet to reduce the physical infrastructure required to support these services while improving the maintenance of the network and allow the alternative networks to leverage the advantages of the HEAnet core.

• Logical networks based on MANTYCHORE will provide a much clearer demarcation and more functional service to its clients, so that they can design and implement a full IP network which can then be integrated in a clear way with the existing BGP-based connection between HEAnet and its clients.

NORDUnet

NORDUnet will deploy the MANTYCHORE framework on the NORDUnet core network as well as on national networks and local campus networks of the Nordic countries as appropriate. NORDUnet is committed to the MANTYCHORE architecture and will exploit MANTYCHORE technology as a tool for Network Operations and Management, for both day-to-day operations of end-user network resources and for the provision of experimental network resources. NORDUnet will deploy MANTYCHORE on internal testbed facilities, will exploit MANTYCHORE in the



NORDUnet NOC, and will use MANTYCHORE technology in collaborative projects. NORDUnet is involved in projects in the global networking community, in GLIF and elsewhere. NORDUnet believes that virtualisation and Infrastructure as a Service plays a crucial role in the future of these communities, and will offer MANTYCHORE as a key contribution to work going forward.

UNI-C

UNI-C plans to exploit the results of the MANTYCHORE project internally and demonstrate the benefits of this technology in two use-cases. In the long term, the implementation of MANTYCHORE in the Danish NREN is part of a larger strategy to address the specific needs of NREN users in the field of health. One of the great advantages of this solution is that it enables to use other infrastructures at a low cost but still is satisfying in terms of security and integrity of the exchanged data, which are key requirements in the field of health

UEssex

UESSEX is interested in MANTYCHORE results both for internal and external exploitation purposes. In particular, Essex will focus on knowledge transfer. UESSEX plans to make use of the results for students' education at all-levels and to provide training to associated researchers. UESSEX will also promote to its industrial partners the importance of devising the MANTYCHORE solutions to provide better services for the EU technical community. In addition UEssex will deploy the MANTYCHORE tools in its extensive experimental infrastructure in order to support services for the network research and user communities using this infrastructure. An example of such user communities is the special interest Ultra High Definition group managed by JANET UK.

TID

TID, as the innovation company of Telefónica Group, must be always researching on top of State of the Art and looking for innovative technologies which can benefit Telefónica’s business units and anticipate business needs. Participation in MANTYCHORE will enable TID to go further into networks virtualisation and to evaluate the advantages and capabilities that deployment of proposed IaaS services can bring to a Network Operator. In particular TID will translate MANTYCHORE approach into a telco environment in order to exploit “Router as a Service” and “IP Network as a Service” as follows. Firstly, new customized and dynamic connectivity and networking services may be offered to a market place of different players and users. Both players and users may be network providers, infrastructure providers, academically communities, scientific corporations, remote and distributed business, individual, etc. Secondly, a more profitable usage of deployed network infrastructures is done because more resources are



available to be commercially exploited without requiring new investment in equipment. And last, but no least, management costs are not increased. Summarizing, TID will extract from MANTYCHORE approach fruitful business models which can improve the efficiency of use of its networks whereas minimizing CAPEX and OPEX.

TCD

TCD is a university, with a research mandate, and hence will focus on reporting its results in scientific publications and conference presentations. But it has multi-faceted interests: (i) as a grid resource provider, (ii) as an OpsCentre/ROC and (iii), as an academic research group. It has been and is especially interested in and an intensive developer of operational grid infrastructure and middleware. It fully expects to harness the project results in its own activities, both in research and in infrastructure deployment (as manager of the Irish grid, Grid-Ireland). In particular TCD expects to create and exploit the opportunities for collaboration on new IaaS ideas.

Table 29 Partners individual exploitation plan

!"C$#$C"V,'(1'.15-',53("'(1"L5'5-3("'0,5N5,5*-"

The consortium will be active in few working groups of the main international standardisation groups and fora in this area:

Standard groups Description

IRTF-NRVG It will provide different solutions and ideas about the network virtualisation thanks to MANTYCHORE and its specification of virtual networks

TMF It aims to contribute to this standardisation group in terms of collaboration between service and infrastructure providers

OGF. NSI-WG MANTYCHORE will collaborate with its interface specification and it provides new features and possible designs for configured networks which NSI-WG will be able to reuse

ETSI, RIPE, IETF, ITU-T

MANTYCHORE partners will target different standardisation areas and try to influence their specification by contributing the project ideas and results

Table 30 Envisioned contributions to standard bodies

The project will actively participate in the Concertation activities and meetings related with the e-Infrastructures area. The objective is to optimise synergies between projects by providing input and receiving feedback from working groups addressing activities of common interest (e.g. from clusters and projects). Projects may offer advice and guidance and receiving information relating to 7th Framework programme implementation, standardisation, policy and regulatory, EU Member States initiatives or relevant international initiative.



!"C$#$H"&'(')*+*(,"36"?(,*LL*0,/'L"X.32*.,7W"Z(3SL*1)*"["3,T*.".*L',*1"'0,5N5,5*-"

In general, knowledge, innovations, concepts and solutions that are not going to be protected by patent applications by the participants will be made public after agreement between the partners, to allow others to benefit from these results and exploit them.

The Consortium Agreement for the MANTYCHORE project will set out clear provisions around intellectual property and confidential information. The general principles will be:

• The parties will be obliged to protect each other’s confidential information from unauthorised disclosure or use during the project and for a certain time period after the end of the project.

• Intellectual Property created out of the project will either be solely owned by the creating party, or jointly owned if two or more parties jointly create it.

• Access to IPR needed for the execution of the project will be deemed granted.

• Access to IPR needed to utilise the results of the project will be deemed granted, however access to a party’s background or side ground IPR (being IPR created before the start of the Project or unrelated to the Project) will be granted on fair and reasonable licence terms.

• Intellectual Property created out of the project will be licensed to others on fair, reasonable and non-discriminatory terms.

• General scope for the parties to mutually agree specific provisions during the course of the project, as required.

• Before dissemination, all public deliverables, papers, standards submissions and so on will go through an approvals procedure. One reason is to allow partners to do an IPR check before their public release. The Technical Executive Committee (TEC) will assist in a conflicts resolution procedure.

!"C$C";3(,.5R/,53(",3"-3053K*03(3+50"5+2'0,-"The economic benefits that can bring the MANTYCHORE project are numerous and can be differentiated depending on the type of the business role.

From the NRENs’ (National Research and Education Networks) point of view, the main benefit that MANTYCHORE tools offer is to reduce OpEx and CapEx thanks to the MANTYCHORE virtualisation tools. This benefit can be broken down as follows:

• Virtualisation allows different virtual e-Infrastructures working independently over the same physical substrate; therefore, using MANTYCHORE tools each virtual infrastructure will be able to be managed by a different and independent virtual operator (VO). Consequently, VOs won’t need to contact NRENs anymore to perform changes in the configuration of the virtual infrastructure (OpEx costs reduction).



• Virtualisation allows to reduce the physical space and the power consumption since less devices are needed. It also especially increases the optimisation and use of the network resources and thus, necessary investments are reduced.

• Since MANTYCHORE tools help to manage the entire e-Infrastructure in a more efficient way, NRENs will be able to support more virtual research communities that perform their experiments on their infrastructure; therefore, more research projects will be able to be carried at the same time.

From virtual research communities’ point of view, the main benefit that MANTYCHORE tools offer is to allow virtual research communities to manage its own e-Infrastructure. This benefit has the following impacts:

• As any change in the configuration of the virtual e-Infrastructure can be done by them, instead of contacting the NREN that provides the physical infrastructure, the possibility of performing new types of experiments and to research new topics in e-Infrastructures is opened.

• Research cycles can be shortened because the e-Infrastructure needed will be ready in less time and experiments will start earlier.

From commercial telecom operators’ point of view, the main benefits that MANTYCHORE tools can offer are the following ones:

• From an internal and structural point of view: as in the case of NRENs, OpEx and CapEx could be reduced thanks to the virtualisation tool of MANTYCHORE.

• From a new business challenges point of view: Telecom operators could offer part of their physical infrastructure to new virtual providers as Infrastructure as a Service (IaaS). This new type of service offers the possibility to telecom operators to get more income without needing to invest in the physical infrastructure, just sharing resources that were not fully used.

• From a network deployment point of view: MANTYCHORE tools allow to deploy shared networks between different operators in order to reach to some places that would not be worthwhile to deploy an individual network (reduce CapEx costs). Moreover, each operator could administrate and manage its virtual infrastructure completely independently from the others (reduce OpEx costs).

• From client’s point of view: the tool to virtualise networks can offer its customers Infrastructure as a Service as a complement to other computational services virtualisation capabilities, storage capacity or Software as a Service that was already offered to its customers. This fact would allow ISPs (Internet Service Providers) to obtain new incomes from these new services, and also would allow them to be positioned in a competitive situation, differentiating to other ISPs that have not implemented this type of service.

• From a user’s point of view: If the operator that provides the communications infrastructure to ISP connecting WAN allowed a virtual management, the Service



Provider would have a greater flexibility to manage the use and configuration of its output to the Internet. This would allow achieving OpEx savings related to the reduction of time required to handle requests for changes to the operator. Moreover, the flexibility of the network would allow to reduce the time required to implement changes in the services contracted by the clients and thus, start billing customers in a shorter timeframe.

From final user’s point of view, the main benefit that MANTYCHORE tools can offer is a reduction on the Internet services cost. This reduction can be carried by the definition of a new business model which is currently opening new topics in the future internet issue: the decoupling of the current Internet Service Provider (ISP) in two roles: Infrastructure Provider and Service Provider. The first one manages the physical infrastructure, while the second one deploys network protocols and offers end-to-end services. This decoupling would channel Service Provider as a new source of revenue in the market of ICT (Information and Communication Technologies) as an agent that would increase competition in the market for network infrastructures and consequently, reduce the Internet services cost.

From environmental and sustainability point of view, the main benefits that MANTYCHORE tools can offer are the following ones:

• Reduce CO2 emissions: Due to the collaboration with the GSN project, CO2 emissions can potentially be reduced since renewable energy sources will be used. Nowadays one of the main worries is to reduce the CO2 emissions to the atmosphere in order to decrease the greenhouse effect.

• Cape and trade: as no CO2 emissions will be produced and soon enterprises will have to pay taxes to emit CO2, e-Infrastructures powered by renewable energy sources will be tax free regarding the CO2 emissions.



1)2)3)*0)4$

[1] Fundacio i2CAT: http://www.i2cat.net

[2] HEAnet: http://www.heanet.ie

[3] NORDUnet: http://www.nordunet.net

[4] REDIRIS: http://www.rediris.es

[5] Cisco Systems: http://www.cisco.com

[6] University of Essex: http://www.essex.ac.uk

[7] Telefónica I+D: http://www.tid.es

[8] MANTICORE:E. Grasa, X. Hesselbach, S. Figuerola, V. Reijs, D. Wilson, J. UzÃ©, L. Fischer, T. de Miguel; "The MANTICORE Project: Providing users with a Logical IP Network Service". TERENA Networking Conference, Bruge, May 2008. [Online] http://tnc2008.terena.org/schedule/presentations/show.php?pres_id=98

[9] FEDERICA Project homepage. Available online at: http://www.fp7-federica.eu/

[10] IaasFramework website. Available online at: http://www.iaasframework.com/

[11] Dave Wilson, "Routing Integrity in a world of Bandwidth on Demand", TNC 2006. Available online a: http://www.terena.org/events/tnc2006/programme/presentations/show.php?pres_id=242

[12] Autobahn: GEANT2 Bandwidth on Demand (BoD ) User and Application Survey (DJ.3.2.1), URL: http://www.geant2.net/upload/pdf/GN2-05-086v11.pdf

[13] UCLPv2 website. Available online at: http:/www.uclp.ca/

[14] UCLPv2: Grasa, S. Figuerola, A. LÃ"pez, G. Junyent, M. Savoie, “UCLPv2, a Network Virtualization Framework built on Web Services”, IEEE Communications Magazine, Feature Topic on Web Services in Telecommunications part II, pp. 126-134

[15] 4WARD website. Available online at: http://www.4ward-project.eu/

[16] Verizon's BoD Service, available online at: http://www22.verizon.com/wholesale/solutions/solution/bod.html

[17] HARMONY: A. Willner, C. Barz, J. A. Garcia, J. Ferrer, S. Figuerola, P. Martini,” Work in Progress: Harmony – Advance Reservations in Heterogeneous Multi-domain Environments”, IFIP TC6, Networking Congress 2009

[18] Argia: E. Grasa, S. Figuerola, A. Forns, G. Junyent, J. Mambretti " Extending the Argia software with a dynamic optical multicast service to support high performance digital media " Optical Switching and Networking, Vol 6, Issue 2, pp. 120-128, April 2009

[19] G2MPLS : http://www.ist-phosphorus.eu/software.php?id=g2mpls

[20] G-Lambda website online available at: http://www.g-lambda.net/

[21] GÉANT3 white paper, online available at: http://www.geant2.net/upload/pdf/GN3-08-034-GN3-White-Paper_20080808173508.pdf



[22] VMWare website online at: http://www.vmware.com/

[23] Xen website online at: http://www.cl.cam.ac.uk/research/srg/netos/xen/

[24] Amazon web services website online at: http://aws.amazon.com/

[25] BlueLock website online at: http://www.bluelock.com/

[26] CANARIE website online at: http://www.canarie.org/

[27] ASA (Autonomic Service Architecture): Yu Cheng, Ramy Farha, Myung Sup Kim, Alberto Leon-Garcia, James Won-Ki Hong "A generic architecture for autonomic service and network management" online available at: http://www.ece.iit.edu/~yucheng/YCheng_CompCom.pdf

[28] VINI website online at: http://www.vini-veritas.net/

[29] DRAGON website online at: http://dragon.east.isi.edu/twiki/bin/view/DRAGON/WebHome

[30] CABO project: Nick Feamster, Lixin Gao, Jennifer Rexford "How to Lease the Internet in Your Spare Time" online available at: http://www.cs.princeton.edu/~jrex/virtual.html

[31] RESERVOIR project: S. BECO, et al. "Cloud Computing and RESERVOIR project", online available at: http://www.haifa.ibm.com/projects/systech/reservoir/public/Reservoir-CloudComputing.pdf

[32] National LambdaRail IP VPN Service, online available at: http://www.nlr.net/packetnet.php

[33] SINET BoD service, online available at: http://www.sinet.ad.jp/

[34] Victor Reijs, Afrodite Sebasti, "AutoBAHN: Automated Bandwidth Allocation across Heterogeneous Networks", GLIF 2007, online available at: http://www.glif.is/meetings/2007/plenary/sevasti-autobahn.pdf

[35] Patil, A. ,Belter, B. ,Polyrakis, A. , Rodwell, T. , Przybylski, M. , Grammatikou, M."GEANT2 ADVANCE MULTI-DOMAIN PROVISIONING SYSTEM, AMPS", online available at: http://www.terena.org/events/tnc2006/core/getfile.php?file_id=760

[36] BELNET Ethernet Point-to-Point service: http://www.belnet.be/

[37] GARR Packet based virtual circuits service: http://www.garr.it/mbs/garr-b-mbs-engl.shtml

[38] H.-M. Adler, P. Eitner, K. Ullmann, H. Waibel, M. Wilhelm (DFN-Verein) "X-WiN: The Network Infrastructure of DFN, online available at: http://www.dfn.de/fileadmin/1Dienstleistungen/XWIN/X-WiNbroschuere09engl.pdf

[39] HEAnet Ethernet Point-to-Point Services, online available at: http://www.heanet.ie/sites/default/files/HEAnet_Ethernet_Point-to-Point_Services.pdf

[40] JA.NET JANET Lightpath service, online available at: http://www.ja.net/services/lightpath/index.html

[41] SURFnet SURFlichtpaden service, online available at: http://www.surfnet.nl/en/diensten/netwerkinfrastructuur/Pages/lightpaths.aspx

[42] Nick Feamster, Lixin Gao, and Jennifer Rexford. How to lease the internet in your spare time. Computer Communication Review, 37(1), 2007.

[43] Larkin, Daithi and Rajagopalan, Nara. 2007. Remote Customer Management of Virtual Routers Allocated to the Customer. U.S. Patent 7,159,031, filed Jan.26, 2001, and issued Jan.2, 2007

[44] Juniper Networks website at: http://www.juniper.net



[45] Khoo Boo Leong, IaaS adoption grows, virtualized core keeps costs down, online available at: http://www.searchstorageasia.com/content/iaas-adoption-grows-virtualized-core-keeps-costs-down?page=0%252C0,0

[46] Globus Toolkit website: http://www.globus.org/

[47] OSGi Framework website: http://www.osgi.org/

[48] Spring Framework website: http://www.springsource.org/

[49] Apache Muse website: http://ws.apache.org/muse/

[50] Chronos: Laia Ferrao, Xavier Barrera, Eduard Grasa, Sergi Figuerola "And inmmediate reservations of virtualized networks resources" TERENA Networking Conference, Malaga, June 2009 [Online] http://tnc2009.terena.org/schedule/presentations/show.php?pres_id=25

[51] OPsCentre website at: http://grid.ie/opscentre.html

[52] Internet2 ION website: http://www.internet2.edu/ion/

[53] GreenStar Network: http://www.GreenStarnetwork.com/

[54] The GEANT Stitching Framework: http://wiki.geant2.net/pub/JRA3/Jra3WorkingArea/GN2-07-066v5-DJ3-5-3-Report_on_Testing_of_Technology_Stitching.pdf

[55] FP7 FEDERICA: P. Szegedi, S. Figuerola, M. Campanellla, V. Maglaris, C. Cervelló; “With Evolution For Revolution: Managing FEDERICA for Future Internet research”. IEEE Communications Magazine, Vol. 47, Issue 7, pp. 34-39; July 2009.

SEVENTH FRAMEWORK PROGRAMME

Documents

Transcript of SEVENTH FRAMEWORK PROGRAMME