1 / 21

WP1.8 Kick-Off Deployment Testing

This plan outlines the tasks, infrastructure, installation, test execution, and error reporting for the deployment and testing of DILIGENT services. Includes timelines and relevant information.

clairereed
Download Presentation

WP1.8 Kick-Off Deployment Testing

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. WP1.8 Kick-OffDeployment Testing pedro.andrade@cern.ch

  2. Outline • Overview • Tasks • Infrastructure • Installation • Test Execution • Errors Report ETICS Role ?? TCom March 2006 Geneva

  3. Overview DILIGENT Release Candidates Deployment Testing T 1.8.4 Integration and Build T 1.8.1 Errors Repository Development - T 1.2/3/4/5/6.x TCom March 2006 Geneva

  4. Tasks GOAL: Test if DILIGENT services are deployable and can be used TCom March 2006 Geneva

  5. T1.8.4 a DILIGENT Integration Infrastructure Who: CERN What: Plan which resources should be used and what installation configuration must be tested. ETICS ? ? TCom March 2006 Geneva

  6. T1.8.4 b DILIGENT Integration Infrastructure Who: ENG What: Prepare “clean” machines running SLC3. Give access to the other partners that will use these machines. SLC3 TCom March 2006 Geneva

  7. T1.8.4 c DILIGENT Integration Infrastructure Who: CERN What: Install gLite services. Only the actually used gLite services should be installed. WMS R-GMA FTS TCom March 2006 Geneva

  8. T1.8.4 d DILIGENT Integration Infrastructure Who: ENG What: Install 3rd party software. For example: WS-CORE. GT4 GT4 GT4 WMS R-GMA FTS DILIGENT services are made available GT4 TCom March 2006 Geneva

  9. T1.8.4 e DILIGENT Integration Infrastructure Who: ENG What: Deploy DILIGENT services. Several iterations can happen. DILIGENT services should be deployed non-gLite machines ? Keeper Index HNM GT4 GT4 GT4 DIS WMS R-GMA FTS GT4 TCom March 2006 Geneva

  10. T1.8.4 f DILIGENT Integration Infrastructure Who: CERN What: Installation tests run. Created by 4DSOFT and executed by CERN using ETICS. Keeper Index HNM GT4 GT4 GT4 DIS WMS R-GMA FTS GT4 TCom March 2006 Geneva

  11. T1.8.4 g DILIGENT Integration Infrastructure Who: CERN What: Installation errors collection from the tests run in T1.8.4f, from the ETICS build process and from the errors detected in the installation phase. Keeper Index HNM GT4 GT4 GT4 ? DIS WMS R-GMA FTS GT4 TCom March 2006 Geneva

  12. Timeline TCom March 2006 Geneva

  13. Web Application Infrastructure ETICS Infrastructure DILIGENT Infrastructure Web Service DILIGENT Service Via browser Build/Test Artefacts Report DB Project DB gLite Infrastructure NMI Scheduler WNs Clients TCom March 2006 Geneva

  14. Infrastructure DILIGENT Integration Infrastructure DIS Service Index Service Keeper Service Content Service ETICS Infrastructure WMS DPM FTS R-GMA • Two options: • testing inf. • new inf. TCom March 2006 Geneva

  15. Infrastructure • Using testing infrastructure: • DILIGENT and gLite services have to run on different machines • infrastructure have to support 2 VOs: • TEST-DIL: for testing proposes • INT-DIL: for integration proposes • no conflicts can exist at gLite level • same version of gLite is appropriate for both VOs ? • gLite services have to be prepared to support both VOs • need to scratch the machines can be different ! TCom March 2006 Geneva

  16. Infrastructure • Using a new infrastructure: • gLite and DILIGENT services can run on the same machine: • is this closer to the real production scenario ? • is this appropriate ? • is there any limitation against/for ? • Machines needed (for both scenarios) • gLite • between 6 and 8 machines • DILIGENT services ? • how many ? • all in one site… ENG TCom March 2006 Geneva

  17. Installation • Manual installation of all software: • gLite • external software • DILIGENT services • Which versions of gLite and other external software: • we need to clearly define: • DILIGENT RC alfa/beta/final uses: • gLite <x.x> • GT4 <x.x> • etc • in principle, same versions as in the development infrastructure • developers should report this info… how? TCom March 2006 Geneva

  18. Installation • How to deploy the DILIGENT services? We need to identify: • how should the DILIGENT services be deployed: • one per machine • n per machine • which combination of services/machine should be tested ? • the deployment order is important • which is the minimal set of DILIGENT services: • DHN • DIS • etc • For DILIGENT releases beta and final, the installation method must be re-thought. ETICS is planning to provide an automatic installation system… TCom March 2006 Geneva

  19. Tests Execution • Up to now we checked if DILIGENT services were deployable, now we need to test if the same services are usable • ETICS build process: • performs units test on all components • but this is not enough • Simple tests to validate key functionalities are needed • Focused on DILIGENT services, not gLite • 4DSOFT should define and create these tests • ETICS will again be used to execute these tests: • tests should be written according to ETICS requirements TCom March 2006 Geneva

  20. Errors Report • Using the ETICS build process reports, containing: • the build process results • the unit tests results • Using the results of the post-installation tests (also executed by ETICS) • The information to collect should include: • types of errors • reasons for the errors • number of errors • per type • per components • per developer/teams • time to fix • etc TCom March 2006 Geneva

  21. Errors Report • During the project lifetime, all the installation errors information will be collected in a public page to: • help identify critical elements in the development phase • pass this information to developers • is this the official channel ? • what should be used? • A physical report collecting all the “installation errors history” will be delivered at the end of project TCom March 2006 Geneva

More Related