EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI EGI IPv6 Report for HEPiX CERN October 5, 2012 CERN 1

EGI-InSPIRE RI Outline 1.EGI goals w.r.t. IPv6 2.Current stand of Testbed Infrastructure 3.Preliminary Testing Results 4.Plans for next weeks/months 2

EGI-InSPIRE RI EGI goals for IPv6

EGI-InSPIRE RI Goals for EGI w.r.t. IPv6 Obviously, IPv4-only nodes cannot talk to IPv6-only nodes without protocol translation at some level Wherever possible, Dual Stack should be pursued So far, protocol translation mechanisms have not been taken into consideration No solution provided for the integration of IPv6-only resources in an IPv4 Grid Therefore our goals so far are: –1. Ensure switching on IPv6 does not break functionality provided using IPv4 in a Dual Stack approach (IPv4 to IPv4 in the presence of also the IPv6 stack) –2. Demonstrate we can use the Grid using IPv6 using EMI/UMD middleware IPv6-only grid clients can connect to IPv6-only grid servers The same grid middleware could then be used in an IPv4 environment and in an IPv6 environment

EGI-InSPIRE RI Goals translated in practice Assess the overall IPv6 status w.r.t. IPv6 compliance of –The grid middleware –The required operational services and tools –Report all sources of problems to EGI and Technology providers –I.e. measure how far are we from IPv6-compliant middleware –For all EGI-related middleware families ( Globus IGE, ARC, gLite, UNICORE, dCache) UMD released components Check/ Verify that switching on IPv6 does not break IPv4 provided functionality –This is however less than half of our goals: we still need IPv4 addresses/nodes Test EMI / UMD middleware components and verify that –They can be deployed ( installed and configured OK ) –They work using IPv4-only, IPv6-only and Dual Stack

EGI-InSPIRE RI IPv6-only resources Integrate IPv4-only resources and IPv6-only resources in a unique functional pool ? Not really. Including IPv6-only resources in the EGI Grid (mostly IPv4) would imply protocol translation –To merge IPv6 and IPv4 resources, there are IPv4 / IPv6 translation mechanisms available and possible gateway approaches, but the majority of them –Introduce an overhead w.r.t. grid functionality to be provided –Often represent a single point of failure in a Grid distributed architecture –Do not scale easily Realistically achievable (at least to start with) is to be able to have a network- agnostic middleware, external dependencies and operational tools enabling us to implement an IPv4-infrastructure and an IPv6-infrastructure  Being able to provide 2 separate Grid pillars / resource-sets Functional IPv4-IPv6 integration out of our scope so far However, we should not be far at all from an IPv6-compliant middleware –however no one has certified what is being provided w.r.t. IPv6 compliance – various spreads problems are likely to be there

EGI-InSPIRE RI IPv6 assessment strategy EGI strategy for assessing IPv6 compliance very down-to- earth We plan to produce –Detailed Test reports where CLI commands are tested in 4 network config for Client and Server –A Summary Matrix reporting “OK”, or “Not working” for 4 network configurations: A) Client and Server both in Dual Stack B) Client in IPv6-only, Server in Dual Stack C) Server in IPv6-only. Client in Dual Stack D) Client and Server both in IPv6-only –An overall initial IPv6 assessment table for services summarizing also possible issues related to installation, configuration, smoke tests, basic functional tests, for each Grid service

EGI-InSPIRE RI Goals of EGI IPv6 testbed 1.Allow general purpose testing of UMD components using the IPv6 protocol 2.Enable specific IPv6 test campaigns on selected UMD components or required external dependencies 3.Provide an hands-on IPv6 testbed for possible IPv6 tutorials for the EGI site administrators community, both on IPv6 in general and IPv6 Security 4.Enable IPv6 testing of specific applications relevant to the EGI UCB / User Community 5.Allow the IPv6 testing of EGI-Inspire JRA1 Operational Tools components 6.Provide support and exploit synergies for the EGI Federated Clouds task force w.r.t. IPv6 ( to be defined, just started) 7.Complement the work done by the HEPiX IPv6 WG, focusing on the middleware

EGI-InSPIRE RI Current Status of testbed and recent achievements

EGI-InSPIRE RI IPv6 Testbed Resources Many new Grid services installed at GARR, ARNES, FZU, GRNET Overall, ~ 15 servers deploying ARC and gLite services

EGI-InSPIRE RI Current Strategy We decided to start focusing on Site Computing and InfoSys resources –To be complementary to HEPiX First full cycles of installation / configuration / smoke testing will be reported by single test reports Detailed test reports being produced: ARC CE, CREAM CE, DPM-SE Wiki based reporting and documenting : Refer to Test reports on

EGI-InSPIRE RI Already identified issues Certification Authorities related files are not reachable ( CA-files, CRLs..) –How do I set up the Grid nodes and the User/Sites/Grid Security Infrastructure ? Some external dependencies are not IPv6 compliant or compiled without the required options We do not have a 100 % clear picture of what should be the expected degree of IPv6 compliance of all UMD middleware families and components –Would help guiding us to verify things Sites are a bit reluctant to enable IPv6 (if not really needed) given lower level of security control / LAN protection expertise

EGI-InSPIRE RI How we decided to report Global IPv6 assessment table including installation, configuration, smoke test for each services – includes logs/references Specific Client/Server summary table for 4 Network Configuration Detailed Test Teports for each service : log of command outcomes (in the 4 configurations)

EGI-InSPIRE RI Client/Server IPvX stack: Test Categories A) Dual Stack on Client and Server B) IPv6-only Client; Dual Stack Server C) IPv6-only Server, Dual Stack Client D) IPv6-only on both Client and Server 14

EGI-InSPIRE RI Preliminary Testing results 15

EGI-InSPIRE RI CREAM CE test Torque CREAM CE installed and configured –IPv6-only installation OK Test to be finalized IPv6-only client : OK Issues with Torque : job stuck in the queue Preliminary outcome on

EGI-InSPIRE RI DPM SE test DPM-SE installed at GARR –IPv6-only installation to be tested still Basic tests for some initial functionality carried out Upgraded MySQL : 5.1  5.5 Tests be finalized Preliminary results on 17

EGI-InSPIRE RI ARC ARC CE tests –See slides from Barbara Krasovec / ARNES at EGI Technical Forum

EGI-InSPIRE RI Other m/w products UNICORE tests started at KIT –Limited feedback received so far dCache – positive feedback got today –Start actual testing ? IGE Globus – just basic contacts –Not aware of any actual progress 19

EGI-InSPIRE RI Plans for next weeks

EGI-InSPIRE RI Next steps Complete tests of CREAM CE, DPM SE Torque/MAUI requires digging into the issue –Start assessing all issues related to LRMS systems Move on for UNICORE, IGE Globus and d-Cache Start collaboration with EGI-Inspire JRA1 on operations tools Pursue functional integration of testbed services with EMI and HEPiX –Provide support information for sites to deploy site BDII / site EMIR

EGI-InSPIRE RI Towards a global IPv6 testbed ? First required steps to build a global, extended, cross-initiative IPv6 testbed have been carried out Top BDII in place –Top BDII condfig file: BDII condfig file: Support for 3 Vos available on many services –net.egi.eu –ipv6.hepix.org –testers.eu-emi.eu

EGI-InSPIRE RI References EGI Network Support coordination: ( ) EGI IPv6 IPv4 address report Contact: