Transcript PowerPoint-presentation

Prototype for the interoperability
between FEDERICA slices and other IP
domains by means of the IPsphere
Framework
Josep Pons Camps
i2Cat
1
Index






Motivation
The IPsphere Solution
Our prototype
Deployment and validation
SMS Child Modules
Conclusions
2
FEDERICA Goals

Create an e-Infrastructure for allowing researchers
on Future Internet to make experiments with full
control of the resources of their partitions.

Support research in virtualization of eInfrastructures:




Multi-virtual domain control
Management and monitoring
Virtualization services
User oriented control in federated environments
3
FEDERICA e-infrastructure
Physical infrastructure virtually partitioned creating slices for users
4
Our new objective for FEDERICA
How??
5
Role of IPsphere in FEDERICA
Provider 2
Provider 1
• How can negotiate and establish on demand this paths?
He can create it through other provider’s networks...
• After the stablishment of the paths, can he manage and monitor them easily?
6
The IPsphere Solution
IPsphere Framework
Business
IPsphere
• open, flexible and accessible framework
for global IP service creation and
delivery
• On-demand service creation and
delivery using standard templates
• Extends across network domains within
network operators
Data Plain
Control /
management plane
• Quality metrics and automated
processes
Management
7
IPsphere Framework Roles
 Element Owner (EO)
 The organization who administers and contributes the physical
network or IT resources to a service – and is compensated for it
 E.g. a transport provider offering IP transit
• Administrative Owner (AO)
• The organization who “owns” the customer relationship, and brokers use
of the end-to-end value chain.
• E.g. the retail provider offering a video service
AO
EO
Users
Value
EO
Value
EO
Value
8
IPsphere components interactions
publisher.wsdl
CUSTOMER
Publisher.xsd
IPSF registry
Publishes
S6
Publisher
Interface
SMS Admin
Service Script
(provided manually as
XML)
Creates
S2
template.xsd
ipsf-schema.xsd
SMS Parent:
Service-to-Element
Coordination
AO
Element Offer
Creates
template.xsd
ipsf-s3.wsdl
SSS MESSAGES
S3
SMS Child:
Resource Control
S3
Interface
S5
ELEMENT
OWNER
Resource Management Systems (xMS)
Element Order
9
Prototype Use Cases: Element Publication
In the context of the previous scenario, the researcher/SP that owns a
slice is a special case  can play three roles of IPsphere: EO, AO and
Users.
All the EO (included the researcher) of all domains involved in the scenario have to
publish their element offers to the IPsphere registry.
Element
Offer 4
Element
Offer 1
Registry
Element
Offer 3
Provider 2
(Commercial ISP)
Element
Offer 2
Provider 1
(NREN)
10
Prototype Use Cases: Element Publication
11
Prototype Use Cases: Element Publication
Templates
12
Prototype Use Cases: Activation / Deactivation
Researcher (user role ) triggers the activation and deactivation of end-to-end service
SMS
Admin
SMS
Parent
SMS Child
SMS Child
Slice xMS
SMS Child
SMS Child
xMS
Provider 1
xMS
Provider 1
Provider 2
(Commercial ISP)
MANTICORE
Provider 1
(NREN)
13
Activation Sequence
xMS
14
Prototype implementation : Components
Developed
Enhanced
MANTICORE IP service:
A Web Service based
system that provides the
ability to define and
configure physical and/or
logical IP networks
Configured
15
Deployment and validation I
•Final objective : SMS Child publishes and activates elements of the i2CatFEDERICA slice interoperating with MANTICORE xMS  Premium content
traffic is Transmitted .
• Phase I
•
Using Juniper SRC instead MANTICORE
•
Inter-domain Tests
•
SMS Parent Simulator
16
Deployment and validation II
• Phase I I
•
Using both MANTICORE IP NETWORK service and Juniper SRC
•
i2Cat intra-domain Tests
•
SMS Parent Simulator
17
Desired Final Scenario
18
SMS Child Modules
19
Conclusions

Prototype implementation gives to FEDERICA researchers mechanisms
required for merging its slice with another slice from FEDERICA or other
similar e-infrastructures.

SMS Child component of IPsphere Framework has been implemented
in the scope of FEDERICA project.
 Can publish elements to a IPsphere registry
 Handles the requests from SMS Parent for activating required elements
published earlier
 Communicates with control/management system of the slice:
MANTICORE/Juniper SRC for triggering activation of the corresponding
xMS-Service

Tested using different scenarios (phase I and II )

Proposal for the definitive validation :
 Showcase interoperability of SMS Child (developed within FEDERICA) with
one or more SMS Parents (other organizations)
 Showcase an IPsphere service configuring CONTENTsphere Field Trial and
FEDERICA slice elements.
20
THANKS FOR YOUR
ATTENTION
Josep Pons
( [email protected] )
Sergi Figuerola ( [email protected] )
Eduard Grasa ( [email protected] )
21