CE Certification Testbed

1
CE Certification Testbed

• Marcin Radecki
• CE ROC Meeting
• Athens, Greece
• 21th April 2005

2
Agenda

• Motivation
• Architecture and Actors
• Infrastructure Implementation
• Current Status
• Nearest Plans

3
Motivation

• To allow the people from CE community easily
  integrate their software into EGEE-like grids
• provide EGEE-compliant infrastructure to develop,
  install and test the software
• prepare the software for being integrated into
  production-level infrastructure
• provide help and guidance in the above tasks

4
Architecture and Actors

• Testbed Infrastructure
• a minimal, fully functional Grid consisting at
  least three sites plus dedicated RB, BDII,...
• CE Software repository
• testing tool suite
• Certification Team
• maintains the infrastructure
• helps to get the software ready on the Testbed
• provides automatic software tests
• Software Developer
• collaborates with Certif. Team in order to
  prepare software packages
• tests the software functionality/stability on the
  Testbed

5
Infrastructure Implementation

• User access
• Through local UI
• Through VOCE virtual organization (RB selection)
• Two ways of installing the CE software
• System space
• The software is packaged with the help of the
  site administrator and then put to the
  repository. Next, sites automatically updates.
• User space
• The software is installed in VO_ltvonamegt_SW_DIR
  directory by taking advantage of glogin, gsiftp
  and ssh

Site A
Software Repository
Site B
Site C
Certification Team
6
Current Status

• Infrastructure
• three sites involved (LCG 2_3_0)
• CYFRONET CEUI, SE, 2WN, BDII, RB
• CESNET CE, SE, 25WN (in shared mode)
• GUP CE, SE, 2WN
• CE software RPM repository at CYFRONET
• apt/yum compliant
• Read/Write access for local certification teams
• CE Software installed
• OCM-G application monitoring system - 3 RPM
  packages
• GLOGIN certificate-based shell access
• MPICH-P4 (tested at CYFRONET)
• G-PM in progress
• Flood application ongoing migration, will not
  be packaged
• Data Access Optimization postponed

7
Nearest Plans

• Packaging
• split ce-soft catch-all package into ce-wn-soft,
  ce-ce-soft, ce-se-soft, etc.
• automate package installation on sites, e.g. cron
  job
• create an RPM package containing global
  ce-related settings
• Tests
• adapt SFT for certification testbed, volunteers
  needed
• Users
• VOCE support
• Documentation
• draft latex document almost ready
• http//grid.cyfronet.pl/egee/tiki-download_file.ph
  p?fileId25

8
Migrating CE Software to Production Grid

• OCM-G and Glogin products (4 RPM packages) seems
  to be matured for migration to production
• For migration
• can reuse already existing SW repository and
  settings (just rebuildrename catch-all packages)
• need to add full yaim support (volunteers?)
• ... we should agree on that
• Problem
• Each 3 months new LCG release 3 weeks update
  time schedule
• Proposed solution install CE-specific software
  on a add-on basis