80 likes | 183 Vues
Overview of SA3 activities, current testing status, planned activities, and strategies for expanding involvement in the EGEE project. Includes details on ETICS use, testing activities, and future deployment testing plans.
E N D
ETICS and EGEE Testing Alberto Di Meglio
Summary • EGEE Software Development Organization • SA3 Activities • Current Testing Status • Planned Activities • How to expand our involvement 3nd All-Hands Meeting - Madison 23-25-05-2007
EGEE Software Development • JRA1: Develops software (most of it, but not all) • SA3: Builds, Integrates, Tests, Certifies gLite • NA4: Supports applications using gLite and develops further components and middleware • SA1: manages the EGEE operations and the pre-production testbed • SA2: provides network support and some software components or tests 3nd All-Hands Meeting - Madison 23-25-05-2007
SA3 • Activities: • Builds: done already using ETICS on various platforms • Tests: done in various ways both manually and automated, using also virtual machines (Xen) • Certification: based on test results pushes patches and releases to SA1 pre-production and then production • Repository: manages the main APT repository used for installation • Porting: dedicated activity to port code to new platform 3nd All-Hands Meeting - Madison 23-25-05-2007
SA3 Testing activities • Collects tests from various sources • Gilbert’s testsuite • SAM (Site Availability Monitor) • Certification testbed: sets of virtual machines with preinstalled components, managed using SmartFrog from HP • Porting: done with a combination of manual builds and automated builds using ETICS 3nd All-Hands Meeting - Madison 23-25-05-2007
Current status of ETICS use • Used for the builds • No tests executed now with ETICS • Some generic agreement in place to port tests from the Gilbert’s testsuite and from SAM to ETICS, if it can be done at 0 effort 3nd All-Hands Meeting - Madison 23-25-05-2007
Planned activities • Deployment testing: done in collaboration with JRA1, based on APT (using the ETICS deployment modules for httpd and APT in the ETICS Contrib project) • Once deployment can be done, start testing the system using testsuites run on a UI using a pre-installed infrastructure (JRA1 experimental testbed) • Once this is done, move to parallel deployment and testing). Requires co-scheduling and various test deployment modules (tomcat, mysql, etc) • After this is demostrated, maybe we can go back to SA3 and propose to move more tests 3nd All-Hands Meeting - Madison 23-25-05-2007
How to expand our involvement ? 3nd All-Hands Meeting - Madison 23-25-05-2007