1 / 11

EMI-0

EMI-0. Cristina Aiftimiei (INFN) EMI Release Manager. Outline. EMI-0 Where we were Where we are What has to be done Why so slow Discussion. 2. EMI-0. EMI-0 - ‘exercise’ release : Apply agreed procedures Find–out problems with tools and procedures Goal:

mikasi
Download Presentation

EMI-0

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EMI-0 Cristina Aiftimiei (INFN) EMI Release Manager

  2. Outline • EMI-0 • Where we were • Where we are • What has to be done • Why so slow • Discussion 2

  3. EMI-0 • EMI-0 - ‘exercise’ release : • Apply agreed procedures • Find–out problems with tools and procedures • Goal: • consistent, coherent repository of non-conflicting packages - end of Oct. 2010 High-priority – without it we cannot have EMI-1! 3

  4. Where we were 4 middleware stacks using different tools to manage their release process: issues discussed and solution proposed - Configuration& Integration TaskForce =>Integration & Configuration Guidelines Discussion & decisions taken during EMT meetings

  5. EMI-0 Guidelines use a common build, test and QA system => ETICS Platforms: starting platform - SL5 x86_64 with the following enabled YUM repositories: SL5 X86_64, EPEL 5 x86_64, glite 3.2 X86_64 => new ETICS platform "sl5_x86_64_gcc412EPEL" To be added – SL5(32b), Deb5(32/64b) Packaging: standard on the supported platforms.: rpms (RHEL5), debs (Debian) External dependencies: default versions from OS YUM/APT repositories and EPEL Build Configuration Guidelines: new ”emi” project - all the EMI configurations required to build will be part of this project ETICS project-configuration - "emi_R_0" No .DEFAULT properties No STATIC dependencies – exceptions requested to the EMT upon emergency and approved. Advice – no sub-system properties EMI-0 repository: non conflicting, installable packages + all external components not coming with any of the standard mainstream repositories (OS repos, Fedora, EPEL, etc)

  6. Where we are EMI-0 status: Success rate: 40% success, 60% failure ARC – emi.arc ARGUS – emi.argus dCache – emi.dcache DGAS – emi.dgas InformatinSystem – emi.bdii MPI – emi.mpi UNICORE – emi.unicore VOMS – emi.voms

  7. Where we are (2) Reason of failures: [ERROR] Undefined property 'globus.location' IO error scanning directory /usr/lib64/Pegasus error: log4c.h: No such file or directory -> "-I/usr/lib64/include" "/usr/lib64/mysql" - not found error: ares.h: No such file or directory Undefined property 'vdt_globus_essentials.location' Undefined property 'LCG-DM.location'

  8. What has to be done Fix build failures Have packages (rpms) moved in the EMI repository Install them in the EMI testbed (?) Start building on SL5(32b) & Debian5 (32/64)

  9. Why so slow Defined as “exercise” was treated as “exercise”=less important no clear procedures or not well explained tools not ready (list of dependencies, images, configuration cloning) complexity of changes not well understood (treatment of external dependencies, dependencies on globus (VDT) -> globus-* (EPEL)) Late with EMI-0 -> late with EMI-1

  10. Discussions • Source packages? • Start work & deliver during EMI-1? • Means cleaning of configurations • Only configure && make: • no “—with-*” • no ${*.location} • Questions? 10

  11. Thank you EMI is partially funded by the European Commission under Grant Agreement INFSO-RI-261611 11

More Related