Enabling Grids for Escienc E g Lite Build

Enabling Grids for E-scienc. E g. Lite Build Programme and Multi-Platform Support Presenter: Location: Date: Time: Eamonn Kenny Ataturk Hall, EGEE’ 08 24 th September 2008 16: 50 -17: 10 www. eu-egee. org EGEE-III INFSO-RI-222667 EGEE and g. Lite are registered trademarks

Overview Enabling Grids for E-scienc. E • • g. Lite Restructuring Node Builds Description Different Branches (Integration, Development, PPS) Integration Dashboard Results Multi-Platform Support Platform Independence Going Forward… EGEE-III INFSO-RI-222667

g. Lite Restructuring Enabling Grids for E-scienc. E Previous Work in EGEE-II: - Summary of the code changes done in the g. Lite restructuring: https: //edms. cern. ch/document/887077/1 - Investing a small amount of effort in restructuring saves time in deployment related issues later on Good work done so far: - Reduced entanglement of server/clients - In some cases, clear separation of functions into metapackages (APIs, cli, interfaces) Possible Areas of Improvement: - Build client side without server side in ETICS - Platform independent EGEE-III INFSO-RI-222667

Node Builds Enabling Grids for E-scienc. E Client Nodes: glite-WN, glite-UI Server Nodes: glite-RB, glite-LB, … • Move from monolithic builds to ‘per node’ builds. • Allows developers and integrators to focus on the parts that can be released while deferring problematic parts of the build, speeding up the release cycle. • Development, build, certification and post-production more tightly coupled since meta-package creation is automated. • Less work in moving and sustaining a node type for a new platform type. Description prepared by SA 3 and ETICS: https: //twiki. cern. ch/twiki/bin/view/EGEE/Node. Type. Builds. Etics EGEE-III INFSO-RI-222667

Proposed Branch Separation Enabling Grids for E-scienc. E Proposal, not proven as of yet EGEE-III INFSO-RI-222667

Branch Usage Enabling Grids for E-scienc. E Integration Branch: glite_branch_3_1_0 • Software configurations locked. Results can be regression tested. Proven to work. • This is one full project build resulting in the generation of many RPMs, tarballs, SRPMs and debs packages. • Packages picked up by SA 3 to create meta-packages. Development Branch: glite_branch_3_1_0_dev • Allow JRA 1 to quickly input changes in the build using this development branch. • Locking is not enforced allowing SA 3 to change configurations for new platforms (assisting JRA 1). • Focussed comparisons of nodes differences is easier to visualize (for EMT, JRA 1, SA 3). EGEE-III INFSO-RI-222667

Branch Usage (2) Enabling Grids for E-scienc. E PPS Branch: glite_branch_3_1_0_pps • Takes the development branch when ready to move to certification. Configurations will be locked. • Patches added by SA 3 to the PPS branch. • Accounting records for all nodes will be recorded in ETICS. First Tests: glite-WN_branch_3_1_0_1_dev • glite-WN meta-package to be produced for SL 5 x 86/x 86_64. • comparison with SL 4 x 86/x 86_64 easier to follow. • glite-UI SL 5 x 86/x 86_64 should be easy to produced on top of this. EGEE-III INFSO-RI-222667

Node Builds (initial work) Enabling Grids for E-scienc. E EGEE-III INFSO-RI-222667

Multi-Platform Support Enabling Grids for E-scienc. E EGEE-III INFSO-RI-222667

ETICS and Platform Independence Enabling Grids for E-scienc. E • ETICS contains: ${libdir}=lib/lib 64, ${platform. Arch}=i 386/x 86_64/amd 64. • RPMs can use: %{_libdir}, %{_arch}. • Moved so far: VOMS, gridsite to platform independent configurations. ETICS in many cases only needs a default configuration per component. • More issues will appear when moving to Unix platforms. Use: FHS and LSB for ETICS/middleware. • Separate software into configure, compile, install and package (ETICS does a lot of packaging for you). • ETICS needs to be independent of ‘internal dependencies’. New client will help here. EGEE-III INFSO-RI-222667

Going Forward… Enabling Grids for E-scienc. E • Contact us regarding changing configurations, development branch changes. • More to be done to have server/client side CODE and BUILD separation. • Node separation benefits to multi-platform support need to be proven. • EGI/NGI considerations are necessary. Going forward we want other partners in the project to be able to pick up on new platform support. EGEE-III INFSO-RI-222667