1. Joan A. García-Espín (i2CAT)
GENUS Virtualisation Service for GÉANT and European NRENs Design, Implementation and Demonstration
Joan A. García-Espín (i2CAT)
On behalf of Reza Nejabati and JRA1-T4
TNC2012, May 2012

2. Talk Overview Infrastructure virtualisation: Concept and Motivation
GÉANT3 activity and approach on infrastructure virtualisation
GENUS (GÉaNt virtUalisation Service) Architecture
GENUS Virtual Infrastructure Operation and Support Services
Drawback analysis
GENUS prototype and proof of concept

3. What Is Infrastructure Virtualisation?
Slicing
Aggregating
Network virtualisation
Router/switch virtualisation
Bandwidth and connectivity virtualisation
Layered based Virtualisation
Layer1 Photonic, Layer II CG-Ethernet, Layer III IP
IT virtualisation
Hardware virtualisation
Local computing/storage virtualisation
Networked computing/storage virtualisation I

4. Virtual Infrastructure

5. Infrastructure Virtualisation Definition GENUS Point of View
In the context of network and computing infrastructure, virtualisation is creation of:
A virtual version of a physical resource (e.g. network, router, switch, optical device or computing server), based on an abstract model of that, which is often achieved by partitioning (slicing) and/or aggregating.
A Virtual Infrastructure (VI) is a set of virtual resources interconnected together and managed by a single administrative entity.
The VI can be a resource itself, with specific attributes of traditional network services: start time, end time, etc. I

6. Motivation for Infrastructure Virtualisation
Next step for BoD services in the R&E environment
Network-based applications with requirements not limited to bandwidth
UHD
Video Conferencing
E-Science
Remote
Instrumentation
Cloud
Computing
Profound transformations of operators/providers infrastructure
Transport networks’ technologies (100 GE, Beyond 100G, programmable transport network,…)
Dynamic Network management and control planes
Current
Mobility of Petabytes of Internet data
Projected
Exabyte Mobility & Processing of Internet data
Core Network Infra.
It is neither feasible nor scalable for network operators to setup and configure dedicated network for each application type or category I

7. Research on Infrastructure Virtualisation in GÉANT3
Research activity
GÉANT3-JRA1-Task4 research activity
Analyze the current available solutions suitable for NREN and GÉANT infrastructure virtualisation and possible use of them
Virtualisation of network and IT resources
Network node and transport service virtualisation
Virtualisation of computing resources
Virtualisation in multi-domain environment
Creating a single virtual domain comprising resources from multiple domain II

8. Research on Infrastructure Virtualisation in GÉANT3
The European research community has managed to achieve significant progress on infrastructure virtualisation technologies through several new and on-going research projects
Requirements for virtualisation service are different for each NREN and not exactly defined
Not intending to propose or develop yet another virtualisation technology or mechanism
We aim to build GÉANT virtualisation service based on the developments and achievements of EU projects
Enabling Interoperability and federation between the existing European virtualisation mechanisms to achieve a virtualisation mechanism for GEANT and associated NREN capable of supporting multi-domain, multi-layer, multi- vendor, multi-technology. II

9. Existing Virtualisation Frameworks Comparison Study
Analysis of frameworks and definition of existing virtualisation services
A comprehensive comparison study of major existing virtualisation frameworks
GENI : SFA framework and architecture
AKARI: multilayer multi-technology virtualisation
Panlab/Planetlab: Teagle framework and architecture (service+ SW based network node)
NOVI: an SFA based Virtual infrastructure creation and federation mechanism
SAIL: Self-managed virtual network (L2/L3), fully integratedwith cloud
GEYSERS: Layer 1 , IT (computing/Storage) virtualisation
OFELIA: Layer1 , layer 2 , IT (computing/Storage /virtualisation
MANTYCHORE: Layer 3,layer 2 virtualisation
Phosphurus: Layer 1 virtualisation
Federica:Layer 1 , IT (computing/Storage) virtualisation
A sample commercial (Amazon & Google) II

10. Comparison Study Parameters
Protocol dependency: states whether there is any protocol dependency for the users of the virtualised infrastructure.
Network layer virtualisation: the OSI layers for which virtualisation is provided.
Computing virtualisation: whether computing virtualisation is provided.
Virtualisation technology: how virtualisation is achieved.
Reason for deploying virtualisation: what is the added value that virtualisation offers.
User community: the community that the virtualisation technology is targeting.
Who manages the virtualised infrastructure. Two broad roles are identified:
Physical infrastructure owner – the party that owns the substrate infrastructure that is used for implementing virtualisation.
User – the party that exploits the subset of the physical infrastructure that constitutes the virtualised infrastructure.
Management tools: what are the tools that are used for managing the virtualised infrastructure. It should be specified if these tools are used by the physical infrastructure owner or the user.
Offered services: the services that are offered to the users.
Potential use in a multi-domain environment: whether deployment of the virtualisation framework is possible in a multi-domain environment. II

11. Comparison Study (Complete table in deliverable)II

12. Lesson learnt so far
The current infrastructure virtualisation technologies resulting from the existing projects and framework are still in their research and development stage. It is therefore not realistic to propose a specific virtualisation technology solution to the NREN and GÉANT community.
We propose an integrated architectural approach that allows the different virtualisation technologies deployed across the NRENs and GÉANT to be integrated, offering a multi-domain, multi-layer and multi-technology virtualisation service
This approach enables each NREN to adopt one or multiple virtualisation technologies, depending on their requirements, and to offer to its users inter- and/or intra- domain as well as multi-layer infrastructure virtualisation services. II

13. GENUS (GÉaNt virtUalization Service)
GENUS architecture is a multi-layer, multi-domain and multi-technology virtualisation architecture suitable for NREN and GÉANT requirements
GENUS is not a virtualisation mechanism or framework. It leverages on virtualisation frameworks, mechanisms, tools and software already implemented within various EU projects and initiatives as well as GÉANT bandwidth on demand provisioning system (Autobahn)
GENUS requires NRENs to adopt an existing virtualisation mechanisms. The choice of virtualisation framework and mechanism is up to each NREN based on their requirements and constrains
NRENs and GÉANT backbone network are the infrastructure providers of GENUS and GENUS itself has no resources.
III

14. GENUS approach on virtualisation
Virtual Resource orchestration & stitching
III

15. GENUS approach on virtualisation
Multi layer Federated Virtual infrastructure
GENUS
GEANT
BoD
Service
NREN A Virtualisation Mechanism
NREN B Virtualisation Mechanism
Autobahn
NREN Infra.
L1/L2/L3
Computing
III

16. GENUS Architecture
III

17. GENUS Architecture Distributed
III

18. Virtualised Operation Support Services (VOSS)
Idea:
Apply virtualisation to OSS
How:
Define Management Resources, compared to Worker Resources (data plane)
Specify atomic management functions as Managemet Resources capabilities
Allow independent manipulation of Mgmt Resources capabilities to different players (provider, consumer…)
Define rules/policies for enabling multi-tenancy
Adopt the Network as a Service model IV

19. GENUS Drawback AnalysisV

20. GENUS Basic Services For Prototyping
Facility registration
Resource discovery
Requesting a virtual infrastructure
Booking Resources
Decommissioning a virtual infrastructure
Releasing resources VI

21. GENUS Basic Services Information Model
Adopted IMF model from FP7 porject GEYSERS
Use of current implementation of GENUS system can request far a virtual infrastructure using two methods:
Describing the virtual infrastructure based on the aforementioned IMF model and in accordance with UML specifications
Browsing through available facilities and registered resources within GENUS system and selecting the required services/resources VI

22. GENUS Current Prototype StatusVI

23. GENUS Current Prototype SnapshotVI

24. GENUS Current Prototype SnapshotVI

25. GENUS Current Prototype SnapshotVI

26. GENUS Test-bed & Software Releases
GENUS First release + Demo is scheduled for July 2012
Final release of the first prototype and final demo April 2013 VI

27. Moltes gràcies
Thank you

28. GENUS USE Case Demo HD on Demand Video Streaming

29. GENUS USE Case Demo HD on Demand Video Streaming
150mbps
200mbps
Virtualisation
(OFELIA test-bed)
BoD/CTRL
(Autobahn test-bed)
Virtualisation
( MANTYCHORE test-bed)
Domain B (NREN)
Domain A (NREN)
Domain B (GÉANT ) VI