MANTYCHORE
Grant Agreement No.: 261527
Intermediate Review
Sergi Figuerola (Project Coordinator)
Pau Minoves (Technical Manager)
Victor Reijs (NA2 Leader)
Brussels, March 2011
1
Agenda




13:00 - Welcome and participants presentation.
13:10 - Mantychore project overview.
13:20 - Open project considerations.
13:30 - WP1 Project Management: resource used, Gantt update and general
questions/comments.


Clarifications and updates of the DoW.
13:45 - Overview of the work done on the different work packages.



WP2 Dissemination Exploitation, Standardisation and Liaisons.
WP3 Consolidating user community and User Training.
WP4 Software refinement.
•





Use Case definition and updates.
WP5 IP Network as a Service for Virtual Research Communities.
WP6 Infrastructure resources Marketplace.
WP7 Zero-Carbon emission virtual infrastructures updates.
15:45 - Open questions from the reviewer.
16:00 - End of the meeting.
Agenda
2
Overview
MANTYCHORE PROJECT OVERVIEW
3
Mantychore @ a Glance

Mantychore legacy


2006 – Manticore
2007 – Manticore II
•


(also with RedIris, Cisco and Juniper)
2010 – Mantychore FP7
ICT-2010 Call 7

1.2.3 – Virtual Research Communities
Total Project Cost: 1,564,386€
 EC contribution: 1,399,740€
 Start date: October 2010
 Duration: 30 months


Partners composition




1 Research Center
2 NREN
3 users
1 commercial operator
Overview
4
Our Challenge
VISION

Provide a software implementation and tools for providing and managing
routers and IP networks as services.
MISION

By means of :

Infrastructure Provisioning:
•

IP Network as a Service:
•
•

Marketplace of Physical/logical routers and IP networks
Creation and configuration of IP networks
L1 and L2 integration
Providing the service to 3 virtual research communities
Mantychore will be deployed over the
infrastructure of 2 NRENS and 3 initial users.

Overview
5
User community
e-Health, Media and Grid
V
M
V
M
VM
V
M
V
M
V
V
V
M
d
Site
5
Gri
s
d
Site
3
V
M
V
M
VM M
Gri
s
V
V
M
VM M
Gri
s
d
Site
6
IP Network as a
Service
V
M
VM M
Gri
s
d
Site
1
V
M
V
M
VM
Gri
s
V
M
V
M
V
V
M
VM M
Gri
s
d
Site
4
d
Site
2
Grid-Ireland “Cloud Layer”, TCD
Improving the Health Data
Network,
Dedicated IP Networks to
support media services (Wales
and Scotland),
router
Authorized
User
Connection
Agreement
System
Health
Data
Network
Hub
router
router
router
Fixed connections + VPNs
+
MANTICORE managed IP
Networks
Site 1
router
Site 2
Overview
6
Objective 1: Deploy an operational
IP Network as a Service
Enable HEAnet and NORDUnet to provide IP Network Services to their users
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 eInfrastructures. Mantychore allow third parties to configure network addressing,
internal routing, firewalls and external routing policies.
Objective 2: Integrated Layer 1-3 services
Refine and expand the MANTYCHORE services provided by means of integrating,
with IaaS tools, solutions for optical and Ethernet/MPLS networks (Ether); thus
being able to provide integrated services at levels 1-3 to the research
community.
Overview
7
Objective 3: Marketplace for resource trading
Innovate in the business model used in services based on IaaS, establishing a
marketplace where all Infrastructure Providers can publish their
available resources with their usage conditions (SLA, price), and all customers
can automatically negotiate the SLAs getting the best resource combination for
their needs.
Objective 4: Carbon-neutral e-Infrastructures
Use MANTYCHORE services to contribute to the research performed in the
GreenStar Network (GSN) project to enable carbon-neutral infrastructures.
Objective 5: Commercial Exploitation
Evaluate the likehood of MANTYCHORE services (open source based) in a
commercial telco environment and elaborate a business plan focused
on this service for telco operators.
Overview
8
OPEN PROJECT CONSIDERATIONS
Open Project
9
Open Project Considerations

Expected benefits

Better external user involvement via increased transparency.
•

Better outcome quality via public exposition of results.
•

•
Closed mailing list for consortium-internal discussions.
Open mailing list for all technical discussions.
Welcome foreign contributions to the project effort.
•

i.e. project documentation.
Simplified communication infrastructure.
•

Welcome feedback and involvement.
Collaborate with interested developers.
Allow other projects to inspect our assets and look for reusable
contents.
Open Project
10
Open Project Approach

Official Website



Open Wiki


http://jira.i2cat.net:8090/display/MANTECH/Home
Open Mailing list




Points to all the resources
www.mantychore.eu
Open technical
Archives online
http://listas.i2cat.net/cgi-bin/mailman/listinfo/mantychore-technical
Open Source

http://anon:anon@svn.i2cat.net/repos/manticore/
Open Project
11
Open Project Approach




News
Pointers to all
past
presentations
Archives
How to get a
copy of the
source code
Open Project
12
Open Project Approach

Pointers to all
participation
channels
Partner only
area
Open Project
13
Open Project Approach






Private area
User
Documentatio
n
Working Area
Work Packages
and Task have
spaces here
Deliverables are
published here
Public readonly
Open Project
14
Achievement of the project objectives


The project is evolving as expected with two course technical
corrections with regards to the DoW.
Course corrections:

IaaS Framework
•
•
•
The work together with Canadian and EU partners has been delayed (>6M) due to
other priorities.
Mantychore has decided to fork it and create an internal version suitable for
Mantychore requirements.
Functionality integration with GSN is independent.


Done via the external API, so little impact in WP7.
Ether
•
•
Currently evaluating integration with OSCARS.
NRENs (NORDUnet) are more interested in MPLS services for cloud scenarios

•
Some trials on OSCARS are already ongoing in NORDUnet
It may also extend collaboration with GN3, ESnet & Internet2
Overview
15
Research/performance indicators I


This section presents some of the actions that are taken towards
preparing the assessment of the Mantychore indicators (p.36 DoW)
Performance / Research indicators of project results:

Scalability
•

Field scalability tests will be performed on late stages of T5.1
Manageability
•
•
•
T4.1 Requirements Analysis has identified operation steps
Continuous feedback and interviews from operator users will help streamline the
user experience.
Mantychore will integrate wherever possible with existing infrastructure in order
to achieve low administration over-head.
Overview
16
Research/performance indicators II

Deployability
•
•

Ease of Use
•
•

Mantychore has a strong emphasis on keeping the network configuration
coherent even in case of failure.
Extensibility
•
•

User specific interfaces.
User specific documentation and training.
Reliability
•

SA2 development team will implement an automatic deployment of updates.
User Manuals will be updated with deployment setup requirements.
Mantychore, as Manticore 2, implements a modular architecture that supports
several extension points.
Mantychore will innovate and allow further customization to adapt to the
operator’s own network policies.
Controllability
•
The ACL system implemented at Manticore 2 will be updated and refined with the
current use cases.
Overview
17
NA’S STATUS
18
NA1, NA2 and NA3



NA1 – Project Management.
NA2 – Dissemination, Exploitation, Standardisation and Liasons.
NA3 – Consolidating the User Community and Users Training.
NAs
19
NA Workplan Y1
M0
M1
M2
M3
M4
M5
M6
M7
M1 All Project Management procedures in place and operational
D1.1 Project Presentation
M5 First version of the project website
M6 Related events, projects and standards
dissemination and standardisation plan is ready
identified.
Exploitation,
D2.1 MANTICORE exploitation, dissemination, standardisation and liaison plan
M8
M9
M10
M7 Project website ready
D2.2 Project website
M11
M12
M13
M14
M15
D3.1 User manuals
M10 First Training completed
M11 Internal report about the status of the user community
Time
NAs
20
NA Workplan Y2
M0
M1
M2
M3
M4
M5
M6
M7
M8
D2.5 Mantychore Software business plan
M9
M10
D1.2 First Periodic Activity Report
M11
M12
D2.3 Report on related research, exploitation and dissemination activities and
planning update
M13
M14
M2 First project review successfully completed
M15
Time
NAs
21
NA Workplan Y2-3
M16
M17
M18
M19
M20
M21
M22
M23
M24
M25
M26
M12 User community consolidated
D3.2 User community final report
M8 At least 2 contributions done in workshops or other public events
M13 Second training completed
M9 At least 1 liaison with other projects and groups
D1.3 Final activity report
M27
M28
M29
D2.4 Report on standards, exploitation, liaison and dissemination activities
M3 Final project review successfully completed
M30
D1.4 Project results evaluation report
Time
M4 All project documentation completed
NAs
22
WP1
NA1 RESOURCE USED, GANTT UPDATE
AND GENERAL QUESTIONS/COMMENTS
NA1 Project Management
23
Project Management - Admin
•
Proposed changes
•
Overall Progress
•
Deliverables
•
Milestones
•
PMs (planned vs. spent)
•
Costs (planned vs. spent)
•
Plans for the next months
NA1 Project Management
24
Small Changes in tasks and Manpower Distribution (I)

TCD



We propose to move 3 MM from Task 5.2 to 4.1
Extend Task 4.1 to end on M9 (from M6)
New status
•
•



Increase TCD’s WP4 effort from 3 to 6 MM (M1 to M9)
Decrease TCD’s WP5 effort from 19 to 16 MM
The overall effort of TCD will not vary
Positive impact on the progress of the project
HEAnet

Some preparation actions are done before the task starts to improve
the efficiency
•
Task 2.2 – Exploitation (Start: M13, End: M30) preparation activities 0.15
MM before its actual start (M8 to M13)
NA1 Project Management
25
Small Changes in tasks and Manpower Distribution (II)

WP5

Some preparation actions are done before the start to improve
the efficiency
•
Task 5.1 – Deployment and operation of MANTYCHORE at NRENs (Start:
M10, End M30).




Pre-validation: few MM and 2 meetings.
Advance start from M10 to M7
Impact < 1 MM on actual task
UPC (Third Party of i2CAT)

Re-allocation of a part of the contribution of UPC from WP4 to
WP2 (max. 1.5 MM)
NA1 Project Management
26
Project Management - Admin
•
Proposed changes
•
Overall Progress
•
Deliverables
•
Milestones
•
PMs (planned vs. spent)
•
Costs (planned vs. spent)
•
Plans for the next months
NA1 Project Management
27
Project Management - Admin
•
Overall Progress
•
Deliverables
•
Milestones
•
PMs (planned vs. spent)
•
Costs (planned vs. spent)
•
Plans for the next months
NA1 Project Management
28
Deliverables
Del. no.
Deliverable name
WP
no.
Lead
Beneficiary
Nature
Dissemination
level 3
Due
Deliver
y date
(project
month)
Effective
Delivery Date
(F) Forecast
(A) Actual
D1.1
Project Presentation
1
I2CAT
R
PU
1
11.11.2010 (A)
D2.1
Exploitation, dissemination,
Standardisation and liaison plan
2
I2CAT
R
PU
3
2.02.2011 (A)
D2.2
Project website
2
I2CAT
O
PU
5
28.02.2011 (A)
D4.1
Requirements analysis report
4
HEAnet
R
PU
5
14.03.2011 (A)
D3.1
User manuals
3
I2CAT
R
PU
6
31.03.2011 (F)
NA1 Project Management




29
Extra Deliverables
Del. no.
D1.1
Deliverable name
QPR-1
NA1 Project Management
WP
no.
Lead
Beneficiary
Nature
Dissemination
level 3
1
I2CAT
R
CO
Due
Deliver
y date
(project
month)
Effective
Delivery Date
(F) Forecast
(A) Actual
5
21.02.2011 (A)

30
Project Management - Admin
•
Overall Progress
•
Deliverables
•
Milestones
•
PMs (planned vs. spent)
•
Costs (planned vs. spent)
•
Plans for the next months
NA1 Project Management
31
Milestones
Milestone
no.
Milestone name
WP
no.
Validated
through
Due
Delivery
date
Effective
Achievement
Date
(F) Forecast
(A) Actual
MS1
All project management procedures in place and
operational
WP1
1
5.12.2010 (A)
MS5
First version of the website available
WP2
1
19.12.2010 (A)
MS6
Related events, projects and standards identified.
exploit., standard. and dissem. plan ready
WP2
3
1.02.2011 (A)
MS7
Website ready
WP2
5
14.02.2011 (A)
MS14
Requirements analysis completed
WP4
5
4.03.2011 (A)
NA1 Project Management





32
Project Management - Admin
•
Overall Progress
•
Deliverables
•
Milestones
•
PMs (planned vs. spent)
•
Costs (planned vs. spent)
•
Plans for the next months
NA1 Project Management
33
PMs (planned vs. spent)

Resource usage from M1 to M3

Initially planned 12.12 MM
•


The actual usage of person months is compared – for the sake of
simplicity – to a quasi-linearly planned distribution function. The actual
usage will have peaks at specific times during the project lifetime.
Actual mm used 9.55 MM + 0.7 MM in-kind contribution (84.6%)
The usage of human resources is considered in-line with
expectations and contributions planned.
NA1 Project Management
34
PMs (planned vs. spent)
Quarterly Human Resources Allocation
October-2010 - December-2010
NA
Partner
Name
i2CAT
Nr.
1
actual
planned
NORDUNET
2
actual
planned
HEANET
3
actual
planned
UNI-C
4
actual
planned
UESSEX
5
actual
planned
TID
6
actual
planned
TCD
7
actual
planned
UPC
ThP
Total
actual
planned
actual
planned
Acronym: Mantychore
Contract: 261527
SA
JRA
WP1
WP2
WP3
WP4
WP5
WP6
WP7
0,90
1,05
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,90
1,05
0,13
0,04
0,08
0,04
0,19
0,04
0,10
0,10
0,00
0,06
0,10
0,10
0,15
0,15
0,00
0,00
0,75
0,53
0,07
0,31
0,18
0,28
0,03
0,11
0,05
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,33
0,69
2,07
1,85
1,05
1,50
0,25
0,50
0,30
1,00
0,00
1,00
0,00
0,00
1,85
1,80
0,40
0,40
5,92
8,05
0,00
0,00
0,17
0,00
0,00
0,00
0,15
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,32
0,00
0,11
0,27
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,92
0,60
0,60
0,00
0,00
0,00
0,00
0,71
1,79
0,00
0,00
0,12
0,00
0,50
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,00
0,62
0,00
Actual = 78.8% of Planned
NA1 Project Management
Total
3,28
3,52
1,60
1,82
0,97
0,65
0,60
1,10
0,00
1,98
0,70
0,70
2,00
1,95
0,40
0,40
9,55
12,12
Actual + In-Kind = 84.6% of Planned
35
PMs (planned vs. spent)

Use of resources M1 to M3

The particular case of UESSEX:
•
•
•
•
Initially planned 1.98 MM
Actually spent 0 MM
Due to some personnel recruiting delays.
But UESSEX has performed an in-kind contribution


0.7 MM
TCD has participated in planning of training (task 3.2)
•
In-kind contribution
NA1 Project Management
36
PMs (planned vs. spent)

Use of resources on M1 to M3

Some partners have spent some resources in the
preparation and discussions on tasks not yet started on
the Gantt (total 1 MM).
•
•
•
WP3: 0.05 MM (UNI-C)
WP5: 0.17 MM (NORDUnet) + 0.15 (UNI-C)
WP7: 0.12 MM (NORDUnet) + 0.51 MM (HEAnet)
NA1 Project Management
37
PMs (planned vs. spent)
Human Resources
Quarterly expenditures
(PM)
Cumulative expenditures
from the start of the
project (PM)
Originally
estimated
Actually
spent
Originally
estimated
Actually
spent
9,55
12,12
9,55
Quarter
Oct-10 / Dec-10
Q-01
12,12
Jan-11 / March-11
Q-02
13,36
25,48
April-11 / June-11
Q-03
11,74
37,22
July-11 / Sept-11
Q-04
18,70
55,92
Oct-11 / Dec-11
Q-05
19,31
75,23
Jan-12 / March-12
Q-06
18,99
94,21
April-12 / June-12
Q-07
18,65
112,86
July-12 / Sept-12
Q-08
15,33
128,19
Oct-12 / Dec-12
Q-09
13,75
141,94
Jan-13 / March-13
Q-10
14,56
156,50
Total
156,50
NA1 Project Management
Cumulative
expenditures
accepted to
Cost Claims
(PM)
9,55
38
PMs (planned vs. spent)
180.00
160.00
140.00
120.00
100.00
80.00
Actually spent PMs
Planned PMs
60.00
40.00
20.00
NA1 Project Management
Q10 (March-13)
Q9 (Dec-12)
Q8 (Sept-12)
Q7 (June-12)
Q6 (March-12)
Q5 (Dec-11)
Q4 (Sept-11)
Q3 (June-11)
Q2 (March-11)
Q1 (Dec-10)
Kick-off
0.00
39
Project Management - Admin
•
Overall Progress
•
Deliverables
•
Milestones
•
Changes
•
PMs (planned vs. spent)
•
Costs (planned vs. spent)
•
Plans for the next months
NA1 Project Management
40
Costs (planned vs. spent)

Other expenditures

Durable equipment:
•
•
Actual expenditure 28.03 €
Not yet significant



Some equipment has not been purchased yet
Depreciation applied only on a part of the period
Travel expenses
•
Actual expenditure 6,829.25 € (8.1% of the travel budget)
NA1 Project Management
41
Costs (planned vs. spent)

Other expenditures

Consumables
•
Actual expenditure 663.56 € ( Equipment ? )
Description
Connection accessories
Book: Sprint Dynamic Modules
Dates
15 December 2010
31 December 2010
Partner
i2cat
i2cat
Total
Costs in €
620.90
42.66
663.56
 Other
• Actual expenditure 2,670.39 € ( MGT ? )
Description
Kick-off organisation
Courier services
Dates
18–19 October 2010
2010
Partner
i2cat
TCD
Total
NA1 Project Management
Costs in €
2,530.80
139.59
2,670.39
42
Project Management - Admin
•
Overall Progress
•
Deliverables
•
Milestones
•
Changes
•
PMs (planned vs. spent)
•
Costs (planned vs. spent)
•
Plans for the next months
NA1 Project Management
43
Plans for the next months

QPR – 2, and following reports

Allocate In-kind contributions to strengthen contingency plans

Collaboration with GSN from day one

Changes of MM between WPs (TCD, HEAnet and UPC)

Re-allocation of a part of the contribution of UPC from WP4 to
WP2 (1.5 MM)
NA1 Project Management
44
WP2
NA2 DISSEMINATION, EXPLOITATION,
STANDARDIZATION AND LIASIONS
STATUS
NA2 Dissemination, exploitation, Standardization and liasions
45
Overview and tasks


Participants: HEAnet (leader), i2cat, NORDUnet, TID, TCD, UNI-C &
University of Essex
Goals:




T2.1: Dissemination


One of key activities of Mantychore project. Stimulate project tools/service to be used by ICT industry and a
positive impact on social economic developments
T2.3: Standardisation


Providing press releases and Internet presence. Providing guidelines for papers, presentations and
demonstrations
T2.2: Exploitation


Provide a web/wiki/blog presence and general external communication deliverables (OK)
Provide frame works, guidelines and support for the other Mantychore WPs to do their
dissemination, standardisation and liaisons (OK)
Stimulate project tools/service utilisation by ICT industry and a positive impact on social
economic developments
Provide guidelines, feedback and possible contribution to standards in Mantychore’s environment
T2.4: Liaisons

Provide guidelines for liaisons with related initiatives and/or project, which might benefit from Mantychore
NA2 Dissemination, exploitation, Standardization and liasions
46
Status (I)

T2.1 Disseminiation


Started on October 2010 – March 2013
Goals:
•
•
•
•
•

Milestone M5: First version of the project website 
Milestone M6: Related events, projects and standards identified.
Exploitation, dissemination and standardisation plan is ready 
Deliverable D2.1 : MANTICORE exploitation, dissemination, standardisation
and liaison plan 
Milestone M: Project website ready 
Deliverable D2.2: Project website (http://www.mantychore.eu/) 
T2.2 Exploitation


Starts on October 2011 – March 2013
Status
•
Some preparational activities have started (like the exploitation plan part of
D2.1)
NA2 Dissemination, exploitation, Standardization and liasions
47
Status (II)
 T2.3 Standardisation
 Started on March 2011 – March 2013
 Status:
•
•
•
•
Standardisation plan has been made as part of D2.1
Different levels have been agreed: follow, participate, contribute, liaison
Special interest on NVRG (IRTF) and OGF (IsOD-WG)
http://jira.i2cat.net:8090/display/MANTECH/IRTF+VNRG++Threads+and+useful+information+to+participate
 T2.4 Liaison
 Started on February 2011 – March 2013
 Status:
•
•
•
•
Liaison plan has been made as part of D2.1
Different liaison strategies made for Peering organisations, Providers and Users
An MoU with GreenStar Network (GSN) project
Establishing contact with GN3 on three fronts: network virtualisation (GN3-JRA1T4), GSN use case description (GN3-NA4-T1) and possible use of GEANT BoD in
WP7 (GN3-SA2-T2).
NA2 Dissemination, Exploitation, Standardization and Liaisons
48
Dissemination criteria


Every Call for papers will be marked with the following criteria.
Regarding the topic:

Strategic value according to DoW (agreed by the WP2 responsible)
•
•
•

Number of partners participant (more is better):
•
•
•

0: minor relevance
1: relevant
2: essential
0: 1 partner.
1: 2 partners.
2: More than 2.
Regarding the targeted forum (universal impact of the action to disseminate):
Activity
Report
Workshop or national conference
International Conference less that A in CORE1
International Conference with A in CORE
International Conference with A* in CORE
Journal not indexed in JCR
Journal indexed in JCR
Patent

Points
0
1
2
3
4
2
3 + Impact factor
3
Higher mark indicates more priority in the action
1
NA2 Dissemination, Exploitation, Standardization and Liaisons
CORE index: http://www.core.edu.au/
49
Procedures

CFP, workshops, journals,… should be announced.



Uploading the information and deadline.
To the Calls Section at http://jira.i2cat.net:8090/display/MANTECH/T2.1+Dissemination
Before submitting, preliminary information should be uploaded to the Wiki
(http://jira.i2cat.net:8090/display/MANTECH/Proposals) and contact the responsible person
to make a preliminar selection.

4 types of Parameters considered
•
Universal impact of the publication.



•
Strategic impact for the Mantychore project.



•
•


JCR Impact Factor
CORE list
Standarization impact
Target
Scope
Current DoW commitments
Special interest arising from a subset of partners and virtual research communities.
Moreover, associated costs and distance will be included in considerations.
If the proposal is considered as discarded, the reason will be marked at the wiki.
If the proposal is considered as interesting, it will be forwarded to the Coordination Board for
final approval.

If agreed, it will directly go to the TEC that will analyze what WPs should lead it and the suggested
person to edit it.
NA2 Dissemination, Exploitation, Standardization and Liaisons
50
Dissemination done

NORDUnet Conference 2011


TERENA 2011


Extended abstract.
Extended Abstract and Presentation.
Submitted posters


EUNIS 2011
ACM SIGCOMM 2011
NA2 Dissemination, Exploitation, Standardization and Liaisons
51
WP3
NA3 CONSOLIDATING THE USER
COMMUNITY AND USERS TRAINING
NA3 Consolidating the User community and users training
52
Consolidating the User Community and Users
Training


Participants: NORDUnet (leader), i2CAT, HEAnet, UNI-C, UEssex & TCD
Goals:




Tasks:



Extending the contacts with existing user organisations
Search for new user organisations that are willing to participate
Provide the necessary knowledge to users
Liaisons with new user groups, projects or research centres
Training Users
Status:



We have defined a new user: ”The cloud user”. NORDunet has been included with the set
of users by providing a cloud use case scenario.
Different projects have been approached but liasions are not yet closed (i.e. GSN
community, and some contacts with Jive, GN3, GEYSERS, and support letters recieved )
We are currently working on material to present the set of MANTYCHORE use cases to the
community.
•
Training material D3.1 is going to be closed in M6.
NA3 Consolidating the User community and users training
D3.1 User Manuals

Re-adapted in an Open Project context.


Constantly evolving documentation.
Documentation available online for external visitors.
•




Open wiki.
Several WP interact with and consume the User
documentation.
Rules and procedures established to keep
documentation updated by all workpackages.
http://jira.i2cat.net:8090/display/MANTECH/D3.1+User+Manuals
http://jira.i2cat.net:8090/display/MANTECH/User Documentation
NA3 Consolidating the User community and users training
54
SA’S STATUS
SAs
55
SA’s Gantt

Two SA:



SA1 – Software refinement.
SA2 – IP Networks as a Service for Virtual Research
Communities.
Gantt:
SAs
56
SA Workplan Y1
M0
M1
M2
M3
M4
M14 Requirements analysis completed
M5
M6
D4.1 Requirements analysis report
M7
M8
M9
M10
M11
M12
M13
M14
M15
Time
SAs
57
SA Workplace Y2-3
M16
M18 Internal report of IP Networks as a Service deployed in NRENs and used
by research communities
M17
M18
M15 Marketplace integrated in IP Network services
M19
M20
M21
M16 Zero-carbon emissions virtual infrastructures integrated in IP Network
services
M22
M23
D5.1 Report on MANTICORE services deployment in NRENs and virtual
research communities results and feasibility of MANTICORE services in a
commercial environment
M24
M25
M26
M17Software development completed
M27
M28
D4.2 Software development report
M29
M19 IP Networks as a Services evaluated in NRENs and virtual research
communities
M30
D5.2 Report on IP Networks as a Service deployment in NREN and its use in
virtual research communities
Time
SAs
58
WP4
SA1 SOFTWARE REFINEMENT
STATUS
SA1 Software Refinement
59
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.

Main duties


Use cases definition
Collect user requirements
•
•


Software development
Improve interface
•

Analysis
Implementation
 Deliverables
 Deliverable 4.1
Requirements analysis report
Deliverable 4.2 Software
development report and
prototype
Usability
Support and bug fixing
SA1 Software Refinement
60
Tasks

T4.1 Requirements Analysis


Determine 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 must be
•
•
•
•
•

Actionable
measurable
testable
related to identified business needs or opportunities
defined to a level of detail sufficient for system design
T4.2 Software development: tools integration and refinement

Implementation of the requirements specified in task 4.1

The main work items initially foreseen to be implemented
•
•
•
•
Integration of MANTICORE II results with L1 and L2 services
Implementation of NREN improvements
Implementation of research communities improvements
Integration with the federated European AAI infrastructure (EduGAIN)
SA1 Software Refinement
61
Status

T4.1 Requirement analysis


Started on November 2010- Ended on February 2011
Workshop Dublin 23-24th February 2011
•
•

NOCs, users and developers get together
Definition and discussion of Use Cases
Goals:
•
•
Milestone M14: Requirements Analysis completed 
Deliverable 4.1 : Requirements analysis report 


Use cases described
T4.2 Software development: tools integration and refinement


Started on March 2011
Status
•
•
Analysing requirements obtained from task 4.1
Deploying software
SA1 Software Refinement
62
Interaction from WP4 to other WPs
INPUTS
WP5
• Software User
feedback
WP6
• Marketplace
Use Case
WP7
• GSN Use Case
SA1 Software Refinement
OUTPUTS
WP5
WP6
WP7
• Implementation
of requirements
WP2
• Demos
WP3
• Trainings
• Transfer technical
knowledge
• User manual
63
Use Cases definition.
SA1
T4.1 REQUIREMENT ANALYSIS
SA1 Software Refinement
64
Virtual CPE – Scenario 1
Provider’s domain
(HEAnet)
CPE
Client A domain
Client B domain
 Providers enforce parts of the
CPE configuration
 i.e. BGP policies.
 Delegation of partial
configuration rights to clients.
 Internal IGP
 VRRP
 Firewall
…
 Automatic provisioning of
new clients.
 Reduce need for new
hardware deployments.
Physical Router
Logical Router
SA1 Software Refinement
65
Virtual CPE – Scenario 2
Provider’s domain
(Health Data Net.)
MPLS LSP’s
Provider’s domain
(UNI·C)
CPE
Client A domain
Physical Router
Logical Router
VPN
SA1 Software Refinement
 Providers enforce parts of the
CPE configuration
 i.e. BGP policies.
 Delegation of partial
configuration rights to clients.
 Internal IGP
 VRRP
 Firewall
…
 Automatic provisioning of
access to provider LSP
channels.
 Directly or via a VPN.
 Reduce need for new
hardware deployments.
 Reporting to existing
accounting infrastructure.
66
Virtual CPE – Scenario 2
Provider’s domain
(Health Data Net.)
MPLS LSP’s
Provider’s domain
(UNI·C)
CPE
Client A domain
Physical Router
Logical Router
VPN
SA1 Software Refinement
 Providers enforce parts of the
CPE configuration
 i.e. BGP policies.
 Delegation of partial
configuration rights to clients.
 Internal IGP
 VRRP
 Firewall
…
 Automatic provisioning of
access to provider LSP
channels.
 Directly or via a VPN.
 Reduce need for new
hardware deployments.
 Reporting to existing
accounting infrastructure.
67
Distributed and Private Cloud – Scenario 1
 This scenario will use
Grid-Ireland nodes to
test complex cloud-like
sharing of resources
and flexible networks.
 A grid site is formed
by:
 Infrastructure
nodes
 Worker nodes
 Currently, only
infrastructure nodes
have connectivity.
SA1 Software Refinement
68
Distributed and Private Cloud – Scenario 1
 We foresee a two stage
implementation:
 At a first stage:
 Use of a L3 VPN
 Policies at TCD.
 Low impact
 Will allow the. grid
site to meet at a
NREN-managed
logical router
 Worked nodes, will be
able to be aggregated in
a flexible cloud.
SA1 Software Refinement
69
Distributed and Private Cloud – Scenario 1
 We foresee a two
stage implementation:
 At a first stage:
 Use of a L3 VPN
 Will allow the.
grid site to meet
at a NRENmanaged logical
router
 Worked nodes, will be
able to be aggregated
in a flexible cloud.
SA1 Software Refinement
70
Distributed and Private Cloud – Scenario 1
 We foresee a two
stage implementation:
 At a second stage:
 Institutional IT
departments will
be involved in the
setup.
 Implement L2
solutions where
possible.
 Avoid tunneling
overhead.
SA1 Software Refinement
71
Distributed and Private Cloud – Scenario 2
 Three actors involved:
 Virtual Machine IaaS Provider – NREN or comercial
operator.
 Offer virtual private clouds.
 Configurable user addressing space.
 L2 access.
 Network IaaS Provider – NREN
 SUnet.
 Redundant Full mesh LSPs.
 Campus
 Computing resources consumer.
 Router partially managed by Mantychore.
 Main requirement:
 Network transparency.
 Avoid any reconfiguration of >L4 services.
SA1 Software Refinement
VM
migration
72
Mantychore vs new Amazon VPC


Amazon VPC launched dynamic networks on March‘11
Amazon VPC has four templates:





Mantychore will implement:


D -> C -> A.
Base technologies



A) VPC with public subnet.
B) VPC with public and private subnet.
C) VPC with Internet and VPN access.
D) VPC with VPN only access.
Support IPv6 is being studied.
VPNs both at L3 and L2 (MPLS, pure-VLAN).
Open Source.




Inspect the source code.
Adapt, customize.
Deploy on your own infrastructure.
Integrate with existing deployed systems.
SA1 Software Refinement
73
Ultra High Definition Applications
 Deployment of next
Physical topology
generation multimedia
applications
Logical topology
 3D, UHD
 Stream producers and
consumers.
 3D medical
applications.
 3D virtual
tourism.
USERS
USERS
GLASGOW
ESSEX
JANET UK-IP
USERS
USERS
 Flexibility to adjust,
network independent of
underlying infrastructure.
Bandwidth on
Demand.
SA1 Software Refinement
CARDIFF
USE
RS
USE
RS
74
SA1
T4.2 SOFTWARE DEVELOPMENT
SA1 Software Refinement
75
Router WS
Router
Engine
Manticore 2 architecture
IP Network WS
 Desktop based GUI
 Only interface
 Web service client.
 Fat client.
 One UI-fits them all.
 Main functionality exposed via
two WS:
 Router
 IP Network
 Integrated User management
and policy definition.
 Development based on GT4.
SA1 Software Refinement
Proto
Impl.
User Mngt. WS
Policies WS
Globus Toolkit 4
76

Resource Manager Center
SA1 Software Refinement
77
Planned Mantychore architecture
Router WS
Router
Engine
 User Management
 Extract User Management functionalities to Mantychore’s GUI.
 Integrate with NREN’s existing Identify Provider functionality.
 EduGAIN, etc
 This is not a core Mantychore functionality and we can reach more complex
setups by externalizing it.
IP Network WS
User Mngt. WS
Policies WS
Proto
Impl.
External
ID. P.
Globus Toolkit
SA1 Software Refinement
78
Planned Mantychore architecture
Router
Engine
 Base technologies
 Upgraded to state of the art (see next slide).
 Globus Toolkit dropped in favor of Fuse ServiceMix (OSGi).
 Upgraded development environment:
 Build system (Maven).
 Test environment.
 Runtime.
Router WS
 Friendlier to developers.
IP Network WS
Proto
Impl.
User Mngt. WS
Policies WS
Fuse Service Mix
SA1 Software Refinement
79
Technologies

Testing
Development
FUSE ESB Kernel
Console
Logging
Provisioning
Deployer
Admin
Spring DM
Security
OSGI Framework
SA1 Software Refinement
80
 External API
 Functionality exported in smaller blocks.
 Called “Capabilities”.
 Allows for functionality discovery.
 Allow for easier client development.
 Better extensibility
Router WS
BGP
Logical Routers
…
Router
Engine
Planned Mantychore architecture
Proto
Impl.
IP Network WS
Fuse Service Mix
SA1 Software Refinement
81
Planned Mantychore architecture
Router WS
Router
Engine
 Reporting System.
 Better reporting of execution outcome.
 Some use cases don’t need the user to receive the error but an external role (IT
department, NOC operator, etc).
IP Network WS
Reporting
Proto
Impl.
External
Infrastr.
Fuse Service Mix
SA1 Software Refinement
82
Planned Mantychore architecture
Router WS
Router
Engine
 Web based interface.
 Main GUI will be ported to web technologies.
 Much more streamlined update process, easier to deploy upgrades.
 Additionally simpler single Use Case interfaces will be developed.
IP Network WS
Proto
Impl.
User Mngt. WS
Policies WS
Web
SA1 Software Refinement
Fuse Service Mix
83
Development methodology
Continuous integration
Monthly release
• SA1
Software
Refinement
Periodic feedback
• SA1 Software
Refinement
• T5.1 + T5.2 +
T6.2 + T7.1
WP4
Development
Deployment /
Installation
USERS
FEEDBACK
NEW
RELEASES
Feedback
Usage /
Testing /
Demos
• SA1 Software
Refinement
• T5.1 + T5.2 +
T6.2 + T7.1
SA1 Software Refinement
• T5.1 + T5.2
+ T6.2 +
T7.1
WP5
84
WP5
SA2 IP NETWORKS AS A SERVICE FOR
VIRTUAL RESEARCH COMMUNITIES
SA2 IP Networks as a service for virtual research communities
85
IP Networks as a Service for Virtual Research
Communities


Participants: NORDUnet (leader), HEAnet, i2CAT, UNI-C,
UEssex , TCD, TID
Goals:


Deploy the Manthycore software into an operational
environment and offer this as a service to virtual research
communities.
Conduct a feasibility study and analyze whether Manthycore can
be deployed in a commercial environment
SA2 IP Networks as a service for virtual research communities
86
Status

T5.1 Deployment and operation of MANTYCHORE in
HEAnet/NORDUnet


T5.2Using MANTYCHORE services in virtual research
communities



Is scheduled to start in M10 of the project
Is scheduled to start in M10 of the project
Some meetings with users have already been done in
order to identify and facilitate the deployment of
MANTYCHORE services
Next users planned meeting will take place late May 2011
SA2 IP Networks as a service for virtual research communities
87
JRA’S STATUS
JRAs
88
JRA1 and 2

Two Joint Research Activities:



JRA1 - Infrastructure resources marketplace
JRA2 - Zero-carbon emissions virtual infrastructure
Gantt:
JRAs
89
JRA Workplan Y1-Y2
M0
M1
M2
M3
M4
M5
M6
M7
M8
M20 Infrastructure marketplace studies completed
M9
M23 Physical networks integrated
M10
M11
M21Infrastructure marketplace simulation completed
M12
M13
D6.1 Infrastructure marketplace mechanisms study
M14
M15
Time
JRAs
90
JRA Workplan Y2-3
M16
M17
M18
M24 Services integrated
M19
M20
D7.1 Integration between Mantychore and GSN report
M21
M22 Marketplace prototype implemented
M22
D6.2Implementation of the marketplace report
M23
M24
M25 Tests performed
M25
D7.2 Network migration tests report
M26
M27
M28
M29
M30
Time
JRAs
91
WP6
JRA1 INFRASTRUCTURE RESOURCES
MARKETPLACE
JRA1 Infrastructure resources marketplace
92
WP6 Overall Objective

Study, design and simulation of the necessary algorithms for the
implementation of the MANTYCHORE marketplace mechanism

Enable the automatic negotiation and reservation of resources between
users and providers.
•

The capability to automatically select, orchestrate and reserve the best resources
for a given request
To use the marketplace in order to allow the NRENs to announce
their own infrastructure as resources of MANTYCHORE services

Users from virtual research communities will be able to access resources
from several providers
JRA1 Infrastructure resources marketplace
93
WP6 Overall Plan and Current Status

Task 6.1: Status

Study and analysis of existing and state of the art work
•

Definition of a market place based use case
•

Use cased is defined and is under development
Initial design of market place
•

completed
Initial design is on going and first version is available
Simulation and emulation analysis
•
Simulation and emulation environment is under development
JRA1 Infrastructure resources marketplace
94
Technical Progress

Study and analysis of existing and state of the art
work

Review of projects and framework relevant to L3
virtualization and virtual IP resource allocation
•
•
•
•
•

XBONE
PLanetLab
VIOLIN
AUTOI
AGAVE
Review of existing network brokering mechanisms
•
•
Internet2 approach: NARB (Network Aware Resource Broker)
Grid approach: Market-Oriented Grid algorithms
JRA1 Infrastructure resources marketplace
95
Technical Progress

Definition of market place based use case

The use case will be based on UK Ultra-high Definition (UHD)
consortium network infrastructure
•
•
The UK Ultra-high Definition (UHD) consortium is a networked infrastructure for
the development and deployment of next generation networked multimedia
applications and services. It consists of five members namely: University of Essex
(Essex), University of Strathclyde (Glasgow), Digital Design Studio (Glasgow),
University of Cardiff (Cardiff), and Technium CAST (Bangor).
The current setup is made up of three networked nodes – Essex, Glasgow, and
Cardiff – which are interconnected via the JANET UK network, and is investigating
the development and deployment of interactive UHD 3D media applications in
the medical and cultural heritage/ virtual tourism domains.
JRA1 Infrastructure resources marketplace
96
Technical Progress

Definition of market place based use case

Use case emulated infrastructure
Emulated Infrastrcuture2
Emulated Infrastrcuture1
JRA1 Infrastructure resources marketplace
97
Technical Progress

Definition of market place based use case

Use case emulated infrastructure
•
There are two independent emulated infrastructures


•
•
•
Infrastructure 1: Ring
Infrastructure 2: Star
Edge devices (visualization + servers) are same in both infrastructure but
for simplicity they are shown in separately. It means there are two
independent providers (infrastructure) providing connectivity service for
user to same edge devices/resource but the cost and QoS for each
infrastructure is different
This emulates two providers provisioning connectivity service to same set
of visualization devices and computing servers
Market place will facilitate resource brokerage, selection and negotiation
for user request
JRA1 Infrastructure resources marketplace
98
Technical Progress

Definition of market place based use case

Mantychore +Market place
Mantychore Market place in emulation
Mantychore software tools
JRA1 Infrastructure resources marketplace
99
Resource advertisment (InPs)
General information, nodes locations, border nodes, prices,..
Technical Progress
Resource classification and storage in the
marketplace
VNT request by SP

Initial design of market place for starting and
stimulating discussion and feedback from
partners

Figure guide:
•
•
•

Inp: infrastructure provider
VNT: virtual network
Sp: service provider ( requester of VNT)
A document to be released on details of
algorithm and designs
VNT request analysis in the marketplace based on:
Demand and supply
VNT mapper (in the marketplace) is responsible for:
Coordination with InPs to map all the VNT
InP11
InP21
InP31
InP12
InP22
InP32
InP13
InP23
InP33
All VNT is mapped
OR Failure
All VNT is mapped
OR Failure
All VNT is mapped
OR Failure
Possible options aggregation with price of each option
VNT mapping
acknowledgement and
Contract creation
JRA1 Infrastructure resources marketplace
yes
SP acceptance
on one option
No
No deal
100
Technical Progress

Simulation and emulation

Simulation
•

Large scale performance analysis and measurements for MarketPlace
algorithms
Emulation
•
•
•
•
•
Use case implementation
Mantychore tools and software installation
Market place algorithms deployment
Interfacing (not integration) Market Place and Mantychore (end product
of T6.1) tools and evaluation
Deployment of integrated Mantychore and Market Place (end product of
T6.2) and evaluation
JRA1 Infrastructure resources marketplace
101
Simulation

Simulation environment

Development started based on OMnet++
JRA1 Infrastructure resources marketplace
102
Emulation

Emulation environment

Preparation for emulated use case implementation has been started
•
Based on UEssex TocuhStone Emulation facility
Emulation environment
JRA1 Infrastructure resources marketplace
103
WP7
JRA2 ZERO-CARBON EMISSION VIRTUAL
INFRASTRUCTURES STATUS
JRA2 Zero-carbon emission virtual infrastructures
104
Scope of JRA2


MANTYCHORE-GSN collaboration has the objective to design necessary
experiments and tests which eventually check the viability of the
movement of services (virtual machines (VMs and applications)) using
flexible device configuration utilities such as Infrastructure as a Service
and Bandwidth on Demand solutions.
Perform the integration between GSN and MANTYCHORE (physical
integration between the GSN and the NRENs infrastructure and also the
services integration).
EPA building rooftop, Ireland
JRA2 Zero-carbon emission virtual infrastructures
Dunhill, Ireland
105
GSN Objectives


Initiate a consortium of industry, universities and government
agencies with the common goal of reducing greenhouse gas (GHG)
emissions arising from information & communication technology
(ICT) services
Create tools, protocols, procedures, and use cases for a growing
network of ICT service providers that offers customers the lowest
price and greenest services
JRA2 Zero-carbon emission virtual infrastructures
106
GSN Node & Network
GSN associates and MANTYCHORE
GSN / Mantychore Integration team meetings active focusing on
• Test Case Generation
• Solution Integration requirements and benefits analysis
• Training
JRA2 Zero-carbon emission virtual infrastructures
107
IBBT GSN Node
JRA2 Zero-carbon emission virtual infrastructures
108
Riba Roja Green Node
Datos del nodo
 Localización
 Riba Roja del Ebre
 Conectividad
 Link óptico.
 Panel solar
 Capacidad: 2000W
 Configuración switch y
PDU
 Energía verde
 Regular grid para
mantenimiento y
operaciones
JRA2 Zero-carbon emission virtual infrastructures
109
Thanks for listening
ANY QUESTIONS?
110
BACKUP SLIDES
Protocol Architecture
M2M network
Web Service

User Access

Http
 Resource control
 Juniper- Netconf
 Cisco- WSMA
(on coming)
WP4- SOFTWARE REFINEMENT
Mantychore
Server
112
Federation Architecture


Users can configure
resources from
external domains
Create/configure




WP4- SOFTWARE REFINEMENT
Logical switches
Logical routers
IP networks
Provisioning L1 & L2
113
Complete Gantt
WP4- SOFTWARE REFINEMENT
114
AutoBAHN and OSCARS

From GEANT SA2-T5-AutoBAHN





AutoBAHN is compatible with DICE IDC Protocol version 1.1
Possibility to cooperate with other BoD systems (eg. OSCARS,
Harmony) to set up the circuits
Signaling and notification messages properly exchanged
Authentication interoperability based on certificates (both
Transport and Web Services layers)
Automated topology exchange (final testing phase)
WP4- SOFTWARE REFINEMENT
115
Q3: Please describe the software and tools being brought from other projects including previous
MANTICORE projects and FEDERICA. What are your contingency plans associated with these
externalities?
Tool
Project
Available at
Purpose /
Dependency
Contingency
IaaS
Framework
April 2010
Base
development
framework /
HIGH
i2CAT, with CRC and Inocybe are the main
developers of the IaaS Framework. If delays in
the deliverables that could affect MANTICORE
should occur, these would be identified soon
enough by i2CAT, and, jointly with CRC and
Inocybe, mobilize more resources to meet the
deliverable deadline with the sufficient quality.
MANTICORE
basic modules
October 2010
Initial
MANTICORE
modules / HIGH
Most of the partners of MANTICORE FP7 are
currently working together to finish the
privately funded MANTICORE II (MII) project
deliverables. Should the FP7 project start
before the end of MII, different teams would
be assigned to the two projects, in order to
allow the 2 projects to run in parallel for a
short period of time without overlapping.
December 2010
Integrate with
layer 1
functionalities /
MEDIUM
Delays in the delivery of Argia would just
mean that IP Network service of MANTICORE
wouldn’t provide Layer 1 capabilities until a
later stage in the project. However, i2cat,
being one of the organizations involved in the
Argia development, will make sure that the
proper resources are mobilized within the
Argia consortium to meet the deadlines.
MANTICORE II
Argia
116
Q3: Please describe the software and tools being brought from other projects including previous
MANTICORE projects and FEDERICA. What are your contingency plans associated with these
externalities? (continued)
Tool
Project
Available at
Purpose /
Dependency
Contingency
Ether
Ether
December 2010
Integrate with layer
2 functionalities /
MEDIUM
Delays in the delivery of Argia would just mean
that IP Network service of MANTICORE wouldn’t
provide Layer 2 capabilities until a later stage in
the project. However, the Canadian consortium
who conduct the Ether implementation effort is
aware of this dependency and will make sure the
delivery date is met.
GSN
Software
June 2011
Integration with GSN
software / MEDIUM
If all the GSN software is not complete by the
time it has to integrate with MANTICORE, the
scope of the joint experiments will be modified.
eduGAIN
Final deliverable
by 2013,
prototypes
before
Integration with
NRENs federated
AAI infrastructure /
MEDIUM-LOW
If the eduGAIN software suite is not available
during the project lifetime, MANTICORE own AAI
can be integrated with HEAnet’s and NORDUnet’s
local AAI infrastructures.
Stitching
Framework
GN2 deliverable
already available,
updates during
GN3 lifetime
Make it “energy”
aware / LOW
Instead of using the Stitching Framework, the
project might use a more ad-hoc methodology of
stitching user' wishes to network/energy
resources
XORP
Module
June 2010
Manage software
routers in JRA2 /
LOW
i2CAT is the main developer of this module, and
its status is almost completed.
117
WP6 Expected Outcomes

Infrastructure marketplace mechanisms study, design and
simulation




Resource Publication Mechanism
Request Submission Mechanism
Allocation and Matchmaking mechanism
Implementation of the marketplace prototype



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
WP4- SOFTWARE REFINEMENT
118
IaaS Framework contingency
IaaS Framework approach:
 Modern set of technologies
 Fuse ServiceMix.
 Base components with IaaS
design concepts:
 i.e. Capabilities concept.
 Reutilization of components
between IaaS projects.
Our contingency approach:
 We have upgraded to similar
technologies on our own.
 We are implementing lighter
versions of the base
components:
 They better suit our project
needs.
 Design concepts are still valid.
 We target internal reutilization
in other IaaS projects.
WP4- SOFTWARE REFINEMENT
119