Introduction to FEDERICA

Transcription

1 Introduction to FEDERICA Mauro Campanella GARR FEDERICA tutorial, June 7 th Malaga, Spain

2 Agenda Introduction to FEDERICA, Mauro Campanella (GARR) Virtualisation features - Miguel Angel Sotos & Ajay Daryanani Arjandas (RedIRIS) Connecting and using slices - Björn Rhoads (KTH) Coffee break Connecting and using slices (cont..) - Björn Rhoads (KTH) Demonstration of FEDERICA end-user IP slice configuration/management prototype - Alejandro Berna (i2cat) User panel - chair Peter Szegedi (TERENA) 2

3 Tutorial: to whom? This tutorial is planned for two broad classes of researchers: Users who want to access the infrastructure and request a slice for their projects Researchers who want to understand the FEDERICA architecture and possibly duplicate it in their labs 3

4 FEDERICA at a glance What: When: Who: European Community co-funded project in its 7 th Framework Program in the area Capacities - Research Infrastructures, 3.7 MEuro EC contribution, 461 PMs 1 st January June 2010 (30 months) 20 partners, based on stakeholders on network research and management: 11 National Research and Education Networks, DANTE (GÉANT2), TERENA, 4 Universities, Juniper Networks, 1 small enterprise (MARTEL), 1 research centre (i2cat) - Coordinator: GARR (Italian NREN) Where: Europe-wide e-infrastructure, open to external connections 4

5 FEDERICA Vision An e-infrastructure based on virtualization in both computers and network is a fundamental tool for researchers on Future (and current) Internet. The facility should allow researchers a complete control of their set of resources in a slice, enabling disruptive experiments at all communication layers. Particular care should be placed in reproducibility of the experiments and in the avoidance of complexity. Such e-infrastructure can be built on existing infrastructures using a practical approach and should be able to federate with other facilities. 5

6 FEDERICA: an e-infrastructure over NRENS e-infrastructures Router/Switch Host for Virtual nodes Raw Ethernet 1Gbps (Fiber later) 6

7 Infrastructure Status: Operational SUNET KT H SE NORDU NET HEAnet IE DFN DE PSNC PL SWITCH CH GARR IT CESNET CZ FCCN PT i2cat ES Red.es ES GRNET ICCS GR Hungarnet HU 1 Gbps Ethernet Each core PoP is equipped with a switch/router (Juniper) and two or more V-Nodes 7

8 Project Timeline proceeding according to schedule. Jan 2008 June 2009 Jun 2010 Slices Month 11 8

9 Offering Slices for any Research Using Virtualization technologies the FEDERICA e-infrastructure creates slices composed by virtual resources (circuits, nodes, routers) The slices are configured according to users requests Possible use cases: - new routing protocols - behavior on the network of distributed applications - Inter-domain services Global Internet FEDERICA substrate (only core is shown) 9

10 FEDERICA - Onelab A Panlab node can be hosted in a slice. That specific node has full control of its network interface and circuits up to the egress from FEDERICA into General Internet Onelab Slice NRENs and Global Internet FEDERICA substrate 10

11 FEDERICA vs. other projects Project: Onelab2/ Emulab FEDERICA Planetlab Operating system fixed fixed User choice (almost any) Control of lower layers No emulation control down to raw Ethernet IP Mandatory used to connect then emulation Used to connect, then not needed Physical delay and capacity choice guarantees of reproducibility No emulation Yes (up to 1 Gb) No emulation Yes User access limits Almost none, at any time Almost none, at any time regulated by a User Policy Board Cost limited none none Scalability medium large limited 11

12 Summary: Infrastructure and Offer The infrastructure is planned for : - Almost clean slate - achieving reproducibility of tests - fast provisioning - control of lower network layers - full control of virtual resources by the user - Access from everywhere in Internet to slices - May host user s equipment - Free-of-charge use of standard offer - Access request moderated by a user policy board - Simultaneous use by researchers groups ICCS 12

13 Questions? FEDERICA : NRENs : GÉANT2 : 13

14 Extra 14

15 Virtual Internet From physical to virtual 15

16 The Core Substrate - HW Switch: Juniper MX480, Dual CPU, 1 line card with 32 ports at 1Gb Ethernet. Virtual and logical routing, MPLS, VLANs, IPv4, IPv6, 2 of the 4 line cards have hardware QoS capabilities) V-Nodes: each is a 2 x Quad core 2GHz, 32GB RAM, 8 network interfaces, 2x500GB disks, Virtualization SW FEDERICA substrate 16

17 The Core Substrate - IP Management plane defined as an IP Autonomous System: AS : (public, no transit, peers with GARR, PSNC which announce the AS to GN2 and General Internet) active IP v4 : /23 (public addresses) active IP v6 : 2001:760:3801::/48 (public) (to be configured soon) NRENs and Global Internet FEDERICA substrate 17

18 Pictorial of creation of a Slice The user requests an Infrastructure made of L2 circuits, un-configured virtual nodes, to test a new BGP version. Creation of: 1. user credentials and authentication and a Slice 2. Virtual Gateway (in red) to bridge the user from outside into the slice 3. Create resources and connect them as specified by the user NRENs and Global Internet FEDERICA substrate (only CORE is shown) 18

19 FEDERICA Data and Control Plane Access protocol : initially paper due to need for scheduling, security and technical agreements (no first come, first serve policy). Next step may be based on SOA (need standard representation of resources) Control plane is not fully automated and it is a set of tools and manual configuration (due to the combined network and system resources) NRENs and Global Internet Network Layer substrate Data Link layer substrate IPv4 (and v6), AS snmp monitoring Ethernet Physical Layer substrate Fibre and Copper 19

20 Slice Data and Control Plane SLICE Application Layer May host any control plane Basic Data Plane is IP SLICE Network Layer SLICE Data Link layer Ethernet Fibre and Copper SLICE Physical Layer Network Layer substrate IPv4 (and v6), AS NRENs and Global Internet Data Link layer substrate Ethernet Physical Layer substrate Fibre and Copper 20

21 Federating FEDERICA Data plane is IP based (packet switched Ethernet) Physical connectivity can be accepted, currently with wired Ethernet Access is regulated by humans for first access, automated protocols (control) can be used later (trust and AAI needed) Not yet resources representation schemas available (needed to describe the available services) Inter-facility control plane not available (SOA?) Intra-facility control plane is very complex, due to scheduling and slice mapping to physical topology tasks, still manual A slice may host whatever internal control plane 21

22 Federating FEDERICA We should differentiate between various forms of federation: 1. integrated ( the facilities can be used as one with a inter-domain common control plane) 2. partially integrated (only part of the control is exchanged, e.g. calendar, AAA information) 3. overlay (each facility just uses the services of the other without a common control plane, just a data plane, there is an exchange of information related to monitoring, faults, and so on) All these possibilities present challenges 22

23 Federating FEDERICA (cont) Having a common control plane in a multidomain environment is very difficult, as it places many constraints to each facility (in time, technology and developments). Need to develop standard resources representation schemas for virtual resources and virtual resource sets to exchange services. The inter-facility exchange of information and synchronization between facilities has to scale gracefully. The Intra-facility control plane is complex, due to resource scheduling and resources mapping from virtual topology (slice) to physical topology, especially if reproducibility or guarantees are mandated. 23

24 FEDERICA - Onelab2 pre-federation OneLab nodes can be hosted in a slice. Those node have full control of their network interface and circuits up to the egress from FEDERICA into General Internet. The slice can contain also a OneLab router Onelab Slice NRENs and Global Internet FEDERICA substrate 24

25 Conclusions (for panel debate) An infrastructure based on virtualization, network and computing resources can offer a very useful platform for innovation and research at many (if not all) communication layers and can be realized on existing facilities. The physical resources functionalities and infrastructure engineering should ensure the functionality to guarantee the quality of the virtualization for reproducibility. Federation is of outmost importance (e.g. to access new technologies and to ensure a larger facility), but has many facets and complexities. A practical approach through a supportive or pre -federation is advised. 25