Upload
zizi
View
28
Download
3
Embed Size (px)
DESCRIPTION
ETICS and EGEE Testing. Alberto Di Meglio. Summary. EGEE Software Development Organization SA3 Activities Current Testing Status Planned Activities How to expand our involvement. EGEE Software Development. JRA1: Develops software (most of it, but not all) - PowerPoint PPT Presentation
Citation preview
www.eu-etics.org
INFSOM-RI-026753
ETICS and EGEE TestingETICS and EGEE Testing
Alberto Di MeglioAlberto Di Meglio
INFSOM-RI-026753 3nd All-Hands Meeting - Madison 23-25-05-2007 2
Summary
• EGEE Software Development OrganizationEGEE Software Development Organization• SA3 ActivitiesSA3 Activities• Current Testing StatusCurrent Testing Status• Planned ActivitiesPlanned Activities• How to expand our involvementHow to expand our involvement
INFSOM-RI-026753 3nd All-Hands Meeting - Madison 23-25-05-2007 3
EGEE Software Development
• JRA1: Develops software (most of it, but not all)JRA1: Develops software (most of it, but not all)• SA3: Builds, Integrates, Tests, Certifies gLiteSA3: Builds, Integrates, Tests, Certifies gLite• NA4: Supports applications using gLite and develops NA4: Supports applications using gLite and develops
further components and middlewarefurther components and middleware• SA1: manages the EGEE operations and the pre-SA1: manages the EGEE operations and the pre-
production testbedproduction testbed• SA2: provides network support and some software SA2: provides network support and some software
components or testscomponents or tests
INFSOM-RI-026753
SA3
• Activities:Activities:– Builds: done already using ETICS on various platformsBuilds: done already using ETICS on various platforms– Tests: done in various ways both manually and automated, Tests: done in various ways both manually and automated,
using also virtual machines (Xen)using also virtual machines (Xen)– Certification: based on test results pushes patches and releases Certification: based on test results pushes patches and releases
to SA1 pre-production and then productionto SA1 pre-production and then production– Repository: manages the main APT repository used for Repository: manages the main APT repository used for
installationinstallation– Porting: dedicated activity to port code to new platformPorting: dedicated activity to port code to new platform
3nd All-Hands Meeting - Madison 23-25-05-2007 4
INFSOM-RI-026753
SA3 Testing activities
• Collects tests from various sourcesCollects tests from various sources• Gilbert’s testsuiteGilbert’s testsuite• SAM (Site Availability Monitor)SAM (Site Availability Monitor)• Certification testbed: sets of virtual machines with Certification testbed: sets of virtual machines with
preinstalled components, managed using SmartFrog preinstalled components, managed using SmartFrog from HPfrom HP
• Porting: done with a combination of manual builds and Porting: done with a combination of manual builds and automated builds using ETICSautomated builds using ETICS
3nd All-Hands Meeting - Madison 23-25-05-2007 5
INFSOM-RI-026753
Current status of ETICS use
• Used for the buildsUsed for the builds• No tests executed now with ETICSNo tests executed now with ETICS• Some generic agreement in place to port tests from the Some generic agreement in place to port tests from the
Gilbert’s testsuite and from SAM to ETICS, if it can be Gilbert’s testsuite and from SAM to ETICS, if it can be done at 0 effortdone at 0 effort
3nd All-Hands Meeting - Madison 23-25-05-2007 6
INFSOM-RI-026753
Planned activities
• Deployment testing: done in collaboration with JRA1, Deployment testing: done in collaboration with JRA1, based on APT (using the ETICS deployment modules based on APT (using the ETICS deployment modules for httpd and APT in the ETICS Contrib project)for httpd and APT in the ETICS Contrib project)
• Once deployment can be done, start testing the system Once deployment can be done, start testing the system using testsuites run on a UI using a pre-installed using testsuites run on a UI using a pre-installed infrastructure (JRA1 experimental testbed)infrastructure (JRA1 experimental testbed)
• Once this is done, move to parallel deployment and Once this is done, move to parallel deployment and testing). Requires co-scheduling and various test testing). Requires co-scheduling and various test deployment modules (tomcat, mysql, etc)deployment modules (tomcat, mysql, etc)
• After this is demostrated, maybe we can go back to After this is demostrated, maybe we can go back to SA3 and propose to move more testsSA3 and propose to move more tests
3nd All-Hands Meeting - Madison 23-25-05-2007 7
INFSOM-RI-026753
How to expand our involvement
??3nd All-Hands Meeting - Madison 23-25-05-2007 8