GENUS Virtualisation Service for GANT and European NRENs

  • Slides: 29
Download presentation
GENUS Virtualisation Service for GÉANT and European NRENs Design, Implementation and Demonstration Joan A.

GENUS Virtualisation Service for GÉANT and European NRENs Design, Implementation and Demonstration Joan A. García-Espín (i 2 CAT) On behalf of Reza Nejabati and JRA 1 -T 4 TNC 2012, May 2012 connect • communicate • collaborate

Talk Overview I. Infrastructure virtualisation: Concept and Motivation II. GÉANT 3 activity and approach

Talk Overview I. Infrastructure virtualisation: Concept and Motivation II. GÉANT 3 activity and approach on infrastructure virtualisation III. GENUS (GÉa. Nt virt. Ualisation Service) Architecture IV. GENUS Virtual Infrastructure Operation and Support Services V. Drawback analysis VI. GENUS prototype and proof of concept connect • communicate • collaborate 1

What Is Infrastructure Virtualisation? Slicing Network virtualisation Router/switch virtualisation Bandwidth and connectivity virtualisation Layered

What Is Infrastructure Virtualisation? Slicing Network virtualisation Router/switch virtualisation Bandwidth and connectivity virtualisation Layered based Virtualisation – Layer 1 Photonic, Layer II CGEthernet, Layer III IP Aggregating § IT virtualisation – Hardware virtualisation – Local computing/storage virtualisation – Networked computing/storage virtualisation connect • communicate • collaborate 2 I

Virtual Infrastructure connect • communicate • collaborate 3 I

Virtual Infrastructure connect • communicate • collaborate 3 I

Infrastructure Virtualisation Definition GENUS Point of View In the context of network and computing

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. connect • communicate • collaborate 4 I

Motivation for Infrastructure Virtualisation Next step for Bo. D services in the R&E environment

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

Research on Infrastructure Virtualisation in GÉANT 3 Research activity GÉANT 3 -JRA 1 -Task

Research on Infrastructure Virtualisation in GÉANT 3 Research activity GÉANT 3 -JRA 1 -Task 4 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 connect • communicate • collaborate 6 II

Research on Infrastructure Virtualisation in GÉANT 3 The European research community has managed to

Research on Infrastructure Virtualisation in GÉANT 3 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, multivendor, multi-technology. connect • communicate • collaborate 7 II

Existing Virtualisation Frameworks Comparison Study Analysis of frameworks and definition of existing virtualisation services

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 (L 2/L 3), fully integratedwith cloud GEYSERS: Layer 1 , IT (computing/Storage) virtualisation OFELIA: Layer 1 , 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) connect • communicate • collaborate 8 II

Comparison Study Parameters Protocol dependency: states whethere is any protocol dependency for the users

Comparison Study Parameters Protocol dependency: states whethere 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. connect • communicate • collaborate 9 II

Comparison Study (Complete table in deliverable) connect • communicate • collaborate 10 II

Comparison Study (Complete table in deliverable) connect • communicate • collaborate 10 II

Lesson learnt so far The current infrastructure virtualisation technologies resulting from the existing projects

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 interand/or intra- domain as well as multi-layer infrastructure virtualisation services. connect • communicate • collaborate 11 II

GENUS (GÉa. Nt virt. Ualization Service) GENUS architecture is a multi-layer, multi-domain and multi-technology

GENUS (GÉa. Nt virt. Ualization 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. connect • communicate • collaborate 12 III

GENUS approach on virtualisation GENUS Virtual Resource orchestration & stitching connect • communicate •

GENUS approach on virtualisation GENUS Virtual Resource orchestration & stitching connect • communicate • collaborate 13 III

GENUS approach on virtualisation Multi layer Federated Virtual infrastructure GENUS NREN B Virtualisation Mechanism

GENUS approach on virtualisation Multi layer Federated Virtual infrastructure GENUS NREN B Virtualisation Mechanism NREN A Virtualisation Mechanism Autobahn GEANT Bo. D Service NREN Infra. L 1/L 2/L 3 Computing connect • communicate • collaborate 14 III

GENUS Architecture connect • communicate • collaborate 15 III

GENUS Architecture connect • communicate • collaborate 15 III

GENUS Architecture Distributed connect • communicate • collaborate 16 III

GENUS Architecture Distributed connect • communicate • collaborate 16 III

Virtualised Operation Support Services (VOSS) • Idea: • Apply virtualisation to OSS • How:

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 connect • communicate • collaborate 17 IV

GENUS Drawback Analysis connect • communicate • collaborate 18 V

GENUS Drawback Analysis connect • communicate • collaborate 18 V

GENUS Basic Services For Prototyping Facility registration Resource discovery Requesting a virtual infrastructure Booking

GENUS Basic Services For Prototyping Facility registration Resource discovery Requesting a virtual infrastructure Booking Resources Decommissioning a virtual infrastructure Releasing resources connect • communicate • collaborate 19 VI

GENUS Basic Services Information Model Adopted IMF model from FP 7 porject GEYSERS •

GENUS Basic Services Information Model Adopted IMF model from FP 7 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 connect • communicate • collaborate 20 VI

GENUS Current Prototype Status connect • communicate • collaborate 21 VI

GENUS Current Prototype Status connect • communicate • collaborate 21 VI

GENUS Current Prototype Snapshot connect • communicate • collaborate 22 VI

GENUS Current Prototype Snapshot connect • communicate • collaborate 22 VI

GENUS Current Prototype Snapshot connect • communicate • collaborate 23 VI

GENUS Current Prototype Snapshot connect • communicate • collaborate 23 VI

GENUS Current Prototype Snapshot connect • communicate • collaborate 24 VI

GENUS Current Prototype Snapshot connect • communicate • collaborate 24 VI

GENUS Test-bed & Software Releases GENUS First release + Demo is scheduled for July

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 connect • communicate • collaborate 25 VI

Moltes gràcies Thank you connect • communicate • collaborate 26

Moltes gràcies Thank you connect • communicate • collaborate 26

GENUS USE Case Demo HD on Demand Video Streaming connect • communicate • collaborate

GENUS USE Case Demo HD on Demand Video Streaming connect • communicate • collaborate 27 VI

GENUS USE Case Demo HD on Demand Video Streaming 150 mbps 200 mbps Virtualisation

GENUS USE Case Demo HD on Demand Video Streaming 150 mbps 200 mbps Virtualisation (OFELIA test-bed) Bo. D/CTRL (Autobahn test-bed) Virtualisation ( MANTYCHORE test-bed) Domain B (NREN) Domain A (NREN) Domain B (GÉANT ) connect • communicate • collaborate 28 VI