1. Building service testbeds on FIRE The cloud to network interface in the BonFIRE infrastructure Gino Carrozzo, Nextworks TNC2012 Reykjavík, 21-24 May 2012

2. BonFIRE 2 2 The cloud-to-net rationale Cloud computing (but also grids and SOAs at large, and BonFIRE) relies on a vital commodity: the network An ever-increasing number of distributed [super-] computing applications pose highly-demanding requirements for dynamicity and flexibility in Net + IT resource control (e.g. automated scaling up/down) …but their network service(s) still treated as “always-on” –Application layer unable to exploit the automatic control potentialities of the current optical (and not-optical) network technologies IT resources dynamics completely uncorrelated from the network ones Common trend to over-provision network services  inefficient resource utilization in the network, above all in case of fault recovery TNC2012, Reykjavík, 21-24 May 2012

3. BonFIRE 3 3 Some reference network control technologies TNC2012, Reykjavík, 21-24 May 2012 Cloud/User-to-Network Interface Academic solutionsCommercial Solutions AutoBAHN UAP OGF NSI NIPS-UNI (ICT-GEYSERS) G.UNI (IST-PHOSPHORUS) OIF UNI 2.0 Carrier’s Bandwidth on Demand systems (e.g. Verizon BoD) Network Control Academic solutionsCommercial Solutions GÉANT BoD Manticore I (i2Cat and Juniper) Manticore II (i2CAT and Cisco) FP7-RI-Mantychore (i2Cat) Grid-enabled G 2 MPLS control plane (IST- PHOSPHORUS) DRAGON (NSF project) OSCARS (EsNet, US) BAR (EGEE) ASON/GMPLS control plane OpenStack (open source, NetworkContainers in particular) D-RAC by Nortel

4. BonFIRE 4 4 BonFIRE: a cloud infrastructure for IoS community ( and beyond ) 6 testbeds distributed across Europe –Permanent: ~320 cores / 30TB –On demand: up to 3k+ cores Heterogeneous Cloud resources (compute, storage and networking) –Seamlessly accessible with a single experiment descriptor –OCCI based API –Application- specific contextualisation for compute resources (VM) –Experiment elasticity TNC2012, Reykjavík, 21-24 May 2012

5. BonFIRE 5 5 Available resources TNC2012, Reykjavík, 21-24 May 2012

6. BonFIRE 6 6 High level (simplified!) architecture TNC2012, Reykjavík, 21-24 May 2012 Portal BonFIRE Broker Cloud Provider BonFIRE API Cloud API (OCCI) Experiment manager Enactor Experiment descriptor Cloud Provider OCCI Resource manager Open Virtual. Format OVF … … Monitoring ID Open Nebula Cells VMWare… ESXi … KVM XEN Policy manager Elasticity rules & engine Security Restf uly

7. BonFIRE 7 7 Three Usage Scenarios General classes of experiment supported by the facility –Scenario 1. Extended cloud scenario: a federated facility with heterogeneous virtualized resources and best-effort Internet interconnectivity –Scenario 2. Cloud with emulated network implications: experimental network emulation platform under full control of the experimenter –Scenario 3. Extended cloud with complex physical network implications: experimental cloud system federated with GÉANT BoD and FEDERICA (collaboration with NOVI) TNC2012, Reykjavík, 21-24 May 2012 BonFIRE site facilityConnecting NREN EPCCJANET HLRSDFN HPLabsJANET IBBTBelNET INRIARENATER PSNCPIONIER

8. BonFIRE 8 8 Cloud-to-Network interface in BonFIRE TNC2012, Reykjavík, 21-24 May 2012 Why? –To allow network-aware experiments with requirements for guaranteed bandwidth (Scenario 3) Network QoS control Advance reservations Solution: Integrate the GÉANT Bandwidth-on-Demand interfaces (AutoBAHN) in the architecture –EPCC-PSNC early deployment pilots EPCC BonFIRE Site PSNC BonFIRE Site Why GÉANT BoD? –Most mature solution in terms of specification, implementation and deployment in the multi-domain environment interconnecting some of the sites –Handles both on-demand and advance reservation requests –AutoBAHN is the reference BoD tech for PSNC and JANET Bonfire selected as usecase for GÉANT BoD service pilot

9. BonFIRE 9 9 Use-case 1 – Shared Site-to-Site BoD TNC2012, Reykjavík, 21-24 May 2012 BonFIRE site ABonFIRE site B NREN AA + GÉANT + NREN BB Experiment 1 traffic flow Experiment 2 traffic flow Shared BoD Network Service A BoD service between two BonFIRE sites shared among different experiments Preliminary setup of network service (non experiment-based) Traffic flows from experiments multiplexed across the logical link Local configuration of the LAN switches/routers at BonFIRE sites for traffic routing and shaping

10. BonFIRE 10 Use-case 2 – Per-experiment BoD TNC2012, Reykjavík, 21-24 May 2012 BonFIRE site ABonFIRE site B NREN AA + GÉANT + NREN BB Experiment 1 traffic flow Experiment 2 traffic flow Experiment 1 BoD Network Service Experiment 2 BoD Network Service A dedicated BoD service between two BonFIRE sites reserved for a single experiment On-demand setup of network service during experiment declaration Network service lifecycle equal to experiment lifecycle Local configuration of the LAN switches/routers at BonFIRE sites for traffic routing

11. BonFIRE 11 AutoBAHN & BonFIRE TNC2012, Reykjavík, 21-24 May 2012 User Access Point (UAP) interface SOAP interface exposed by IDMs to provide access to BoD services BonFIRE as an AutoBAHN client to dynamically request BoD services between BonFIRE sites

12. BonFIRE 12 BoD architecture extensions TNC2012, Reykjavík, 21-24 May 2012 Cloud-to-network adaptor Cloud-to-net IF (Net side) Controlled network BoD Site Link as new type of OCCI resource cloud-to-net IF plugin (client-side) BoD

13. BonFIRE 13 BoD Adaptor key functions TNC2012, Reykjavík, 21-24 May 2012 Interaction with AutoBAHN –Request BoD service reservation –Monitor service status CPE control –Configure egress routers/switches on BonFIRE sites for traffic routing

14. BonFIRE 14 Cloud-to-Network Interface Development/Deployment plans TNC2012, Reykjavík, 21-24 May 2012 First BoD client prototype Early deployment Consolidated prototype Full deployment Aug. 2012 –BoD adaptor prototype integrated into BonFIRE Enactor –Final specification of the BonFIRE cloud to network interface Dec. 2012 –Final prototype fully integrated into BonFIRE architecture –Final design of BonFIRE external interconnection In 2013 Extend deployment to other BonFIRE sites, possibly: –INRIA –IBBT Sept. 2012 Early deployment in EPCC and PSNC sites –Bonfire selected as usecase for GÉANT BoD service pilot –Ready for Open-Call-2 network-aware experiments

15. BonFIRE 15 Cloud-to-network interface in action: experiments from the 2 nd Open Call TNC2012, Reykjavík, 21-24 May 2012 Two Topics on call (deadline Mar 7 th 2012): A)Experiments in Scenarios 1-2-3 (500K€) B)Cloud provider (100K€) 619 K€ EC funding for –4 new experiments –1 cloud provider (multi-cloud facility) 28 project proposals received –22 proposals on Theme A 7 proposals in the shortlist, 4 of which mentioning scenario 3 as of high interest for their research (57%) –Tentative start date: Sept 2012

16. BonFIRE 16 Future steps: mix BoD + FEDERICA resources for BonFIRE experiments TNC2012, Reykjavík, 21-24 May 2012 EPCC & PSNC sites also connected to FEDERICA PoPs –Access to resources from four FEDERICA PoPs (PSNC, DFN, CESNET, GARR) –BonFIRE implementing SFA adaptor to request FEDERICA slices Nice to have –Provide experimenters with mixed virtual + physical network infrastructures

17. Building service testbeds on FIRE Thank you Acknowledgments: G. Landi (Nextworks), M. Giertych/B. Belter (PSNC), K. Kavoussanakis/A. Hume (Univ. Edinburgh – EPCC), J. Jofre, C. Velayos (i2CAT)