EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI Middleware updates Peter Solagna – EGI.eu OMB – 16/07/ /3/2016 1

EGI-InSPIRE RI Summary Security support of dCache Evolution of the UMD worflows Future of the Torque-Server component 10/3/2016 2

EGI-InSPIRE RI dCache SHA-2 support Expected dCache releases with SHA-2 support: dCache  UMD-3 –Bug fix release solving the SSL issue of previous versions –Release from the PT 16 July –Release in the EMI repositories between 22 and 29 July –Release in UMD after middle August dCache  UMD-2 –Release from PT 30 July –Not known the expected release date in the EMI repositories and therefore in UMD –dCache v2.2.2 has not been tested as extensively as v2.6.5, developers suggest to deploy the second

EGI-InSPIRE RI dCache security support Security support of dCache has been extended until September Until there a SHA-2 enabled version is available in UMD, there will not be alarms from midmon related to dCache –Probably the dCache probes will be turned in critical at the end of August Sites must upgrade to a SHA-2 enabled version before the end of September

EGI-InSPIRE RI StoRM security support StoRM EMI-1 (v and older) ended security support on July 15 Sites must upgrade before August 31 Alarms have been re-activated on Monday New issue related to storm New issue –PT is evaluating the problem, if confirmed an extension for the EMI-1 support will be asked

EGI-InSPIRE RI Next UMD releases Next UMD-2 and UMD-3 updates have the target to release the dCache updates –Complete the SHA-2 support in UMD UMD-3 update: second half of August UMD-2 update: end of August

EGI-InSPIRE RI Extension of the software provisioning process Several PTs are releasing in EPEL as primary repository Release in EMI comes usually weeks after the transition to EPEL stable Discussions within URT to start the software provisioning from EPEL testing –Staged rollout in parallel with the EPEL testing –Product teams are willing to wait for the EGI green light before moving the products to EPEL stable UMD repositories are still needed More control on the releases Protection from other EPEL upgrades Metapackages or additional packages not in EPEL The new process will allow to reduce the delay between PT release and UMD release

EGI-InSPIRE RI Questions about UMD? Before moving to Torque

EGI-InSPIRE RI Torque in EPEL The owner of Torque in EPEL declared he ‘orphaned’ the package. –EPEL package database reports Torque as ‘owned’owned –Torque will remain available in the EPEL6(&5) repository Last release available in EPEL Latest release available from Adaptive Computing (considering the 2.5.* major release) –Torque will not be available in EPEL7 Maui rpms are available in the UMD and EMI 3 rd party repository –Last update dated back in 2011

EGI-InSPIRE RI Torque-server-config support status Torque server config provides: –Dependencies with torque and maui rpms –Configuration modules glite-yaim-torque-server glite-yaim-torque-utils –Includes the info-system bits INFN will not support all the components of Torque-server-config –glite-yaim-torque-utils is supported as part of the CREAM-TORQUE module (it will be supported)

EGI-InSPIRE RI Future of Torque in EGI Torque will be available in EPEL5 and EPEL6 –Maui in the UMD and EMI repositories Deploying Torque in the same machine as CREAM will not change Stand alone installation of torque: –Torque-server-config had no updates but in EMI-2 to update the maui dependencies –The last release continues to be available in the EMI and UMD repositories –As long as there is no need to change torque dependencies it will do the work (torque is not changing in EPEL) Similar situation for the WN modules