1. 1 Prototype for the interoperability between FEDERICA slices and other IP domains by means of the IPsphere Framework Josep Pons Camps i2Cat

2. 2 Index  Motivation  The IPsphere Solution  Our prototype  Deployment and validation  SMS Child Modules  Conclusions

3. 3 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 e- Infrastructures:  Multi-virtual domain control  Management and monitoring  Virtualization services  User oriented control in federated environments

4. 4 FEDERICA e-infrastructure Physical infrastructure virtually partitioned creating slices for users

5. 5 Our new objective for FEDERICA How??

6. 6 How can negotiate and establish on demand this paths? After the stablishment of the paths, can he manage and monitor them easily? Role of IPsphere in FEDERICA Provider 1 Provider 2 He can create it through other provider ’ s networks...

7. 7 The IPsphere Solution IPsphere Framework open, flexible and accessible framework for global IP service creation and delivery On-demand service creation and delivery using standard templates Quality metrics and automated processes Extends across network domains within network operators Business Management IPsphere Control /management plane Data Plain

8. 8 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 AO 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 EO Value Users EO

9. 9 SMS Child: Resource Control SMS Parent: Service-to-Element Coordination SSS MESSAGES S3 S2 S5 S3 Interface Element Order Creates ipsf-s3.wsdl template.xsd ipsf-schema.xsd Service Script (provided manually as XML) S6 Publisher Interface Publishes Publisher.xsd publisher.wsdl IPSF registry SMS Admin CUSTOMER Resource Management Systems (xMS) Creates template.xsd Element Offer ELEMENT OWNER AO IPsphere components interactions

10. 10 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.

11. 11 Prototype Use Cases: Element Publication

12. 12 Prototype Use Cases: Element Publication Templates

13. 13 Prototype Use Cases: Activation / Deactivation Researcher (user role ) triggers the activation and deactivation of end-to-end service

14. 14 Activation Sequence xMS

15. 15 Prototype implementation : Components Developed Enhanced Configured  MANTICORE IP service: A Web Service based system that provides the ability to define and configure physical and/or logical IP networks

16. 16 Deployment and validation I Final objective : SMS Child publishes and activates elements of the i2Cat- FEDERICA slice interoperating with MANTICORE xMS  Premium content traffic is Transmitted. Phase I Using Juniper SRC instead MANTICORE Inter-domain Tests SMS Parent Simulator

17. 17 Deployment and validation II Phase I I Using both MANTICORE IP NETWORK service and Juniper SRC i2Cat intra-domain Tests SMS Parent Simulator

18. 18 Desired Final Scenario

19. 19 SMS Child Modules

20. 20 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.

21. 21 THANKS FOR YOUR ATTENTION Josep Pons ( josep.pons@i2cat.net )josep.pons@i2cat.net Sergi Figuerola ( sergi.figuerola@i2cat.net )sergi.figuerola@i2cat.net Eduard Grasa ( eduard.grasa@i2cat.net )eduard.grasa@i2cat.net