SPI  Software Process & Infrastructure Project Status http://spi.cern.ch LHCC Review - 23 November 2004 Alberto AIMAR [ema...
Presentation Outline <ul><li>2003 </li></ul><ul><li>Recommendations of previous Review </li></ul><ul><li>2004 </li></ul><u...
Recommendations of 2003 review (I) <ul><li>CVS service </li></ul><ul><ul><li>Move to the IT CVS service as soon as possibl...
Recommendations of 2003 review (II) <ul><li>External Software service </li></ul><ul><ul><li>Transparent decisions making f...
Recommendations of 2003 review (III) <ul><li>Build System and Infrastructure </li></ul><ul><ul><li>Role of a central libra...
SPI Services  (November 2004)   <ul><li>External Software  </li></ul><ul><li>Savannah Project Portal </li></ul><ul><li>Sof...
SPI External Software Service  <ul><li>We install software needed by LCG projects. </li></ul><ul><li>Open Source and Publi...
External Software (II) <ul><li>The platforms supported  </li></ul><ul><ul><li>decided by the Architects Forum that represe...
External Software – http://spi.cern.ch/extsoft
SPI Savannah Portal Service <ul><li>Functionality: </li></ul><ul><ul><li>Bug tracking, Task management Download area, etc ...
Savannah Service – http://savannah.cern.ch
SPI Software Distribution Service <ul><li>Simple solution to use </li></ul><ul><ul><li>local installations (external sites...
Software Distribution – http://spi.cern.ch/lcgsoft
Support of Build and Releases <ul><li>LCG Librarian  </li></ul><ul><ul><li>Started in Summer 2004 </li></ul></ul><ul><ul><...
Software configuration and dependencies <ul><li>XML description to have a simple to parse format </li></ul><ul><ul><li>Bui...
SPI Testing Services <ul><li>Software testing should be an integral part of the software development in the LCG App Area <...
Testing Support – http://spi.cern.ch/testing
Quality Assurance Activities <ul><li>QA Checklist on each Release </li></ul><ul><li>Build the release  </li></ul><ul><li>R...
QA Reports
LCG Policies <ul><li>LCG Policies </li></ul><ul><ul><li>CVS and Build Directory Policy  </li></ul></ul><ul><ul><li>Softwar...
Workbook and Documentation <ul><li>Code documentation activity continues  </li></ul><ul><li>Workbook for SPI </li></ul><ul...
Collaboration with EGEE <ul><li>Collaboration mostly with JRA1 (Middleware) and SA1 (Deployment) with considerable benefit...
Milestones done (I) Certification of external software for the new Linux platform  Done 2004/4/15 Migration of all project...
Milestone done (II) Common build and release solution in LCG App Area  Done 2004/7/1 Validation and test of the external t...
Modified/Late Milestones Appwork evaluation   >>> An XML solution to generate build and dependencies information is being ...
Additional Milestones and Activities in 2004 <ul><li>We have many services running and using all resources assigned, we fo...
Proposed Milestones for 2004 Q4 and 2005 Q1 Definition of use cases and plans for the config/make solution  2004/11/30 New...
Proposed Milestones (II) Independent build and release of partitions of the LCG software   2005/2/28 QA Tests Coverage rep...
Proposed Milestones (III) <ul><li>Further milestones will be defined according to the recommendations of the LHCC review  ...
Summary  <ul><li>SPI provides a set of stable services that fully use the current resources </li></ul><ul><ul><li>Savannah...
Proposed focus for 2005 <ul><li>Continue to automate and centralize the cycle for  software build/test/release/distributio...
BACKUP MATERIAL <ul><li>BACKUP MATERIAL </li></ul>
Resources % Responsible Services Testing Frameworks QA reports, Software distribution  QA reports and Testing Frameworks B...
Summary of actions on 2003 recommendations (I) <ul><li>CVS service to IT </li></ul><ul><ul><li>Passed to IT after validati...
Summary of actions on 2003 recommendations (II) <ul><li>QA activities </li></ul><ul><ul><li>Automated generation of report...
Upcoming SlideShare
Loading in...5
×

Presentation at the LHCC Review

242

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
242
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Presentation at the LHCC Review

  1. 1. SPI Software Process & Infrastructure Project Status http://spi.cern.ch LHCC Review - 23 November 2004 Alberto AIMAR [email_address]
  2. 2. Presentation Outline <ul><li>2003 </li></ul><ul><li>Recommendations of previous Review </li></ul><ul><li>2004 </li></ul><ul><li>Status of the SPI Services </li></ul><ul><ul><li>Actions performed to fulfill the recommendations </li></ul></ul><ul><li>Milestones 2004 </li></ul><ul><li>2005 </li></ul><ul><li>Proposed Milestones </li></ul><ul><li>Summary </li></ul>
  3. 3. Recommendations of 2003 review (I) <ul><li>CVS service </li></ul><ul><ul><li>Move to the IT CVS service as soon as possible </li></ul></ul><ul><ul><li>After testing or features and performance </li></ul></ul><ul><ul><li>Use centrally managed tools </li></ul></ul><ul><li>Savannah portal </li></ul><ul><ul><li>Avoid divergence of CERN customization with mainstream Savannah </li></ul></ul><ul><ul><li>Concerns about scalability </li></ul></ul><ul><li>Documentation and web site </li></ul><ul><ul><li>Website and SPI workbook were praised as good and complete </li></ul></ul><ul><ul><li>Maintain workbook up to date </li></ul></ul><ul><ul><li>Verify that doxygen comments are included in the code </li></ul></ul>
  4. 4. Recommendations of 2003 review (II) <ul><li>External Software service </li></ul><ul><ul><li>Transparent decisions making for provision and maintenance of external software </li></ul></ul><ul><ul><li>Add flexibility to support different structures of installations and maintain the original structures of the tools </li></ul></ul><ul><ul><li>Make available compilation and installation scripts </li></ul></ul><ul><ul><li>Suggest simple QA scripts to validate installations of new versions of external tools </li></ul></ul><ul><li>QA activities </li></ul><ul><ul><li>Work to automate the verification </li></ul></ul><ul><ul><li>Person to be centrally responsible for QA and to chase projects to improve compliance </li></ul></ul>
  5. 5. Recommendations of 2003 review (III) <ul><li>Build System and Infrastructure </li></ul><ul><ul><li>Role of a central librarian </li></ul></ul><ul><ul><li>Common build settings, release procedures </li></ul></ul><ul><ul><li>Share of common build tools not developed within the projects </li></ul></ul><ul><ul><li>Build centrally the software and free developers in projects </li></ul></ul><ul><ul><li>Have prereleases available to the users </li></ul></ul><ul><ul><li>Investigate a config/make solution </li></ul></ul><ul><ul><li>Clarity long term strategy </li></ul></ul><ul><ul><li>Support others build system used by other experiments (CMT) </li></ul></ul><ul><li>Software Distribution </li></ul><ul><ul><li>More interaction with LCG deployment and check existing distribution tools (e.g. pacman) </li></ul></ul><ul><ul><li>Customize distribution by platform and component </li></ul></ul>
  6. 6. SPI Services (November 2004) <ul><li>External Software </li></ul><ul><li>Savannah Project Portal </li></ul><ul><li>Software Librarian, builds and releases </li></ul><ul><li>Testing Frameworks </li></ul><ul><li>QA checklists and reports </li></ul><ul><li>Software Distribution </li></ul><ul><li>LCG Software Configuration </li></ul><ul><li>Development of LCG policies, templates </li></ul><ul><li>Code Documentation (doxygen, lxr, viewcvs) </li></ul><ul><li>Documentation and LCG Workbook </li></ul><ul><li>Actions performed to fulfill the recommendation </li></ul><ul><li>CVS service to IT </li></ul><ul><ul><li>Passed to IT after validation and intensive testing </li></ul></ul><ul><ul><li>We migrated all projects ourselves, no problems </li></ul></ul>
  7. 7. SPI External Software Service <ul><li>We install software needed by LCG projects. </li></ul><ul><li>Open Source and Public Domain software (libraries and tools) </li></ul><ul><li>There are currently 65 different packages , plus others under evaluation. For more than 400 installations </li></ul><ul><li>The LCG projects (SEAL, POOL, PI, Simulation and SPI) propose what to install in agreement with LHC needs </li></ul><ul><li>We also provide configuration for the LCG projects </li></ul><ul><ul><li>A unique AFS location </li></ul></ul><ul><ul><li>Standard structure package_name/version/ platform/package_ content </li></ul></ul><ul><li>We have automated many installations of the external software </li></ul><ul><li>The web site is now automated and generated from the real status of the installations </li></ul><ul><li>Some installations specific to users/experiments needs. </li></ul>
  8. 8. External Software (II) <ul><li>The platforms supported </li></ul><ul><ul><li>decided by the Architects Forum that represents the App. Area projects and LHC experiments </li></ul></ul><ul><ul><li>Linux Red Hat 7.3: rh73_gcc32, rh73_gcc323, rh73_icc80, rh73_ecc80 </li></ul></ul><ul><ul><li>Linux SCL3: slc3_gcc323 </li></ul></ul><ul><ul><li>Windows platforms (Win32): win32_vc71 </li></ul></ul><ul><ul><li>Mac OSX: osx103_gcc33 </li></ul></ul><ul><ul><li>We also provide help (and our scripts) to users that want to build on other platforms (e.g. Suse 9.1, RH 9.0, etc) </li></ul></ul><ul><li>Actions performed to fulfill the recommendation </li></ul><ul><li>External Software service </li></ul><ul><ul><li>Maintain original structure of the installed packages </li></ul></ul><ul><ul><li>Automated installations and making available all installation scripts and tools </li></ul></ul><ul><ul><li>Some tools for which we have verification material we now check the installation, more on the way </li></ul></ul>
  9. 9. External Software – http://spi.cern.ch/extsoft
  10. 10. SPI Savannah Portal Service <ul><li>Functionality: </li></ul><ul><ul><li>Bug tracking, Task management Download area, etc </li></ul></ul><ul><li>The Web portal for LCG software projects </li></ul><ul><li>Customized from GNU (SourceForge as origin) </li></ul><ul><li>Totally web based </li></ul><ul><li>Single entry point to all projects </li></ul><ul><li>Uniform access to project information </li></ul><ul><li>Set up common web infrastructure for a project without coding </li></ul><ul><li>What SPI changed </li></ul><ul><ul><li>installation from GNU, general bug fixing and improvements </li></ul></ul><ul><ul><li>integration with AFS authentication </li></ul></ul><ul><ul><li>Integration with standard services already available </li></ul></ul><ul><li>What SPI does </li></ul><ul><ul><li>administration (project approval) </li></ul></ul><ul><ul><li>maintenance (submitted bugs) </li></ul></ul><ul><ul><li>development (support requests) </li></ul></ul><ul><li>Status </li></ul><ul><ul><li>>110 hosted projects </li></ul></ul><ul><ul><li>>850 registered users </li></ul></ul><ul><li>Users doubled in one year and many features added </li></ul><ul><li>Actions performed to fulfill the recommendation </li></ul><ul><li>Savannah portal </li></ul><ul><ul><li>Collaboration with the open source is established and constant </li></ul></ul><ul><ul><li>We benefit of the fixes of the open source and collaboration with main developers is going very well </li></ul></ul>
  11. 11. Savannah Service – http://savannah.cern.ch
  12. 12. SPI Software Distribution Service <ul><li>Simple solution to use </li></ul><ul><ul><li>local installations (external sites, laptops,...) </li></ul></ul><ul><ul><li>using simplest approach </li></ul></ul><ul><ul><li>python downloader + tar format </li></ul></ul><ul><ul><li>replicate the central AFS tree (in a optimized way) </li></ul></ul><ul><ul><li>package dependency from SCRAM </li></ul></ul><ul><li>We can generate distribution easily from a general description we have </li></ul><ul><li>Looking into pacman as a suitable solution </li></ul><ul><li>Simple tool to install </li></ul><ul><ul><li>successful for users installations </li></ul></ul><ul><ul><li>very easy to use and reliable </li></ul></ul><ul><li>Different use-cases should have different solutions </li></ul><ul><ul><li>Our tool is adequate as a simple solution for LCG Application Area Distribution </li></ul></ul><ul><li>Long-term solutions have being investigated </li></ul><ul><li>Pacman test installation is available </li></ul><ul><li>Actions performed to fulfill the recommendation </li></ul><ul><li>Software distribution </li></ul><ul><ul><li>Binaries: python-based tool and pacman distribution </li></ul></ul><ul><ul><li>Sources: distribution of all external and LCG software and all the SPI tools to build from sources </li></ul></ul><ul><ul><li>We need to improve interaction with Deployment and EGEE. Contacts established but no common solutions adopted </li></ul></ul>
  13. 13. Software Distribution – http://spi.cern.ch/lcgsoft
  14. 14. Support of Build and Releases <ul><li>LCG Librarian </li></ul><ul><ul><li>Started in Summer 2004 </li></ul></ul><ul><ul><li>Working to centralize all build and release tasks </li></ul></ul><ul><ul><li>Task to build the LCG software for all supported platforms </li></ul></ul><ul><ul><li>Coordinate releases and pre-releases with the projects </li></ul></ul><ul><ul><li>Maintain the configuration for the build and for other build systems in (e.g. generate and keep up to date the CMT files of the configurations) </li></ul></ul><ul><li>Actions performed to fulfill the recommendation </li></ul><ul><li>Build System and Infrastructure </li></ul><ul><ul><li>Librarian role filled in June 2004 and very beneficial to centralize this activity </li></ul></ul><ul><ul><li>Developed scripts to centrally do the releases and installations </li></ul></ul><ul><ul><li>We performed the certification of all external and LCG software for SLC3, as test of the automatic installation scripts </li></ul></ul><ul><li>Developing simple tools to automate the build of the LCG software </li></ul><ul><li>Librarians Integration group </li></ul><ul><ul><li>Discuss/agrees the additional needs of the experiments in terms of build and package versions/installations. </li></ul></ul><ul><ul><li>Reports to Architects Forum that defines the general priorities for SPI </li></ul></ul>
  15. 15. Software configuration and dependencies <ul><li>XML description to have a simple to parse format </li></ul><ul><ul><li>Build information </li></ul></ul><ul><ul><li>Dependency description </li></ul></ul><ul><li>Build and install for external packages and LCG software </li></ul><ul><li>Generate the configurations for the build and release systems needed by the users </li></ul><ul><ul><li>LCGCMT support </li></ul></ul><ul><ul><li>Config/make based solution </li></ul></ul><ul><ul><li>SCRAM support </li></ul></ul><ul><li>We don’t want to make one more build and configuration system but generate for the existing ones </li></ul><ul><li>Actions performed to fulfill the recommendation </li></ul><ul><li>Build System and Infrastructure (II) </li></ul><ul><ul><li>Config/make solution is going to be achieved via the XML description files that he had to implement in order to support several tools for build and distribution </li></ul></ul><ul><ul><li>XML description will allow to support several build systems </li></ul></ul><ul><ul><li>Generate and keep up to date configuration files for CMT </li></ul></ul>
  16. 16. SPI Testing Services <ul><li>Software testing should be an integral part of the software development in the LCG App Area </li></ul><ul><li>The goal was to provide something that can be run automatically as often as needed (releases, development, etc) </li></ul><ul><li>SPI provides </li></ul><ul><li>Test frameworks </li></ul><ul><ul><li>CppUnit, Oval </li></ul></ul><ul><ul><li>Qmtest </li></ul></ul><ul><li>Test support </li></ul><ul><li>Test policies </li></ul><ul><li>Test doc </li></ul><ul><li>Different platforms/compilers </li></ul>Integration Tests System Tests Examples Software testing Integration test System test Acceptance test Unit test Software developer Sw-testing team LHC experiments Use in Exp. Work Package Test Automated testing
  17. 17. Testing Support – http://spi.cern.ch/testing
  18. 18. Quality Assurance Activities <ul><li>QA Checklist on each Release </li></ul><ul><li>Build the release </li></ul><ul><li>Run automatic tests </li></ul><ul><li>Statistics </li></ul><ul><ul><li>Test Inventory </li></ul></ul><ul><ul><li>Documentation/Examples Inventory </li></ul></ul><ul><ul><li>Savannah Statistics </li></ul></ul><ul><ul><li>Code Inventory </li></ul></ul><ul><ul><li>Rule Checker , Logiscope </li></ul></ul><ul><li>LCG Policies </li></ul><ul><ul><li>Configuration of a build system </li></ul></ul><ul><ul><li>CVS directory structure </li></ul></ul><ul><li>Well-defined, transparent </li></ul><ul><ul><li>clear rules and checklist of assessed items </li></ul></ul><ul><ul><li>anybody at anytime may see statistics </li></ul></ul><ul><ul><li>create reports themselves </li></ul></ul><ul><ul><li>anybody may contribute </li></ul></ul><ul><li>QA Reports </li></ul><ul><li>Automatic reports </li></ul><ul><ul><li>Generated at every release </li></ul></ul><ul><ul><li>Published on the SPI web site </li></ul></ul><ul><li>Evaluation and usage of external tools continued </li></ul><ul><li>Actions performed to fulfill the recommendation </li></ul><ul><li>QA activities </li></ul><ul><ul><li>Automated generation of reports, a web form is being put in place </li></ul></ul><ul><ul><li>Resources (junior) joined in August 2004, for now no resources for verification of compliance to the QA criteria defined </li></ul></ul><ul><ul><li>No resources for actively verifying QA and testing compliance </li></ul></ul>
  19. 19. QA Reports
  20. 20. LCG Policies <ul><li>LCG Policies </li></ul><ul><ul><li>CVS and Build Directory Policy </li></ul></ul><ul><ul><li>Software Testing Policies </li></ul></ul><ul><ul><li>Version Numbers, Tagging and Release Procedure </li></ul></ul><ul><ul><li>Installation Directory Structure </li></ul></ul><ul><ul><li>Platform string, binary names, debug flags and more </li></ul></ul><ul><li>They are a needed by the projects </li></ul><ul><ul><li>They are defined by the LCG projects, collected by SPI </li></ul></ul><ul><li>If everything is different is too difficult to use and to automate </li></ul><ul><ul><li>compromising on our habits, for project needs </li></ul></ul><ul><ul><li>tell when they are not followed </li></ul></ul><ul><li>First time that this exists at this extent, and that is checked </li></ul>
  21. 21. Workbook and Documentation <ul><li>Code documentation activity continues </li></ul><ul><li>Workbook for SPI </li></ul><ul><li>Repository/policy for the LCG workbooks </li></ul><ul><li>No documentation standards achieved in the field but improvements </li></ul><ul><li>Trying a few solutions (DocBook, Wiki, blog) </li></ul><ul><li>Maybe too early in these heavy development phases </li></ul><ul><li>Actions performed to fulfill the recommendation </li></ul><ul><li>Documentation and website </li></ul><ul><ul><li>Our website is stable and we keep it up to date </li></ul></ul><ul><ul><li>Testing wiki and other systems to simplify writing of documentation from several platforms </li></ul></ul><ul><ul><li>No documentation standard achieved </li></ul></ul>
  22. 22. Collaboration with EGEE <ul><li>Collaboration mostly with JRA1 (Middleware) and SA1 (Deployment) with considerable benefits. For all, I think. </li></ul><ul><li>SPI provides tools for EGEE projects </li></ul><ul><ul><li>Presented in several occasions at all levels and activities </li></ul></ul><ul><li>SPI services used </li></ul><ul><ul><li>Savannah portal used by several activities (Middleware, Deployment, etc). Requested several modifications to the software </li></ul></ul><ul><ul><li>Testing frameworks, all used (QMTest, CppUnit, PyUnit) </li></ul></ul><ul><ul><li>QA reports and metrics are being developed </li></ul></ul><ul><li>SPI services not used </li></ul><ul><ul><li>No external software, no software distribution, no build system </li></ul></ul><ul><li>Few (minor) specific services </li></ul><ul><ul><li>Verification of coding conventions via CodeWizard </li></ul></ul><ul><ul><li>dotProject service for basic planning </li></ul></ul><ul><li>Contribution to SPI: 2 FTEs </li></ul>
  23. 23. Milestones done (I) Certification of external software for the new Linux platform Done 2004/4/15 Migration of all projects to IT CVS service Done 2004/4/1 LCG software librarian in place Done 2004/3/15 Delivery of configuration files also for the CMT build system Done 2004/2/28 QA reporting tools available publicly Done 2004/2/28 Upgrade of the Savannah service and installation of the Gnu open source version Done 2004/2/20 More code standards checks added to the QA reports (via doxygen) Done 2004/1/31 IT CVS service verified and validated by SPI Done 2004/1/31
  24. 24. Milestone done (II) Common build and release solution in LCG App Area Done 2004/7/1 Validation and test of the external tools needed by LCG projects Done 2004/7/1 RH 7.3 gcc 3.2.3 supported Done 2004/5/15 Definition of the EGEE collaboration Done 2004/5/1
  25. 25. Modified/Late Milestones Appwork evaluation >>> An XML solution to generate build and dependencies information is being developed. Late/ Modified 2004/6/15 Convergence plan for the LCG software infrastructure >>> On the way, collaboration well ongoing but the use cases and tools are quite different (development, installations, deployment) Late/ On the way 2004/6/15 RH 7.3 icc 8 supported >>> Mac OSX, SLC3, RH73_gcc323 had priority Late/ Modified 2004/5/31 Documentation standards for workbook and documentation infrastructure in place >>> The project do their documentation and it was not perceived as priority vs resources Late/ On the way 2004/5/15
  26. 26. Additional Milestones and Activities in 2004 <ul><li>We have many services running and using all resources assigned, we follow the AF’s decisions for our priorities and activities </li></ul><ul><li>The certification of the new CERN platform and the adoption first of CEL3 and later of SLC3 required more work than expected </li></ul><ul><ul><li>SPI had to compile and provide several versions of the external packages in order to accommodate the needs of different experiments and to suit their software configurations. </li></ul></ul><ul><li>Support for Mac OSX, SLC3 and RH73_gcc323 were decided as priority </li></ul><ul><ul><li>Delayed the port to other platforms (such as icc 8); </li></ul></ul><ul><li>We had to start defining a simple XML description of build/config info </li></ul><ul><ul><li>This will simplify generation of specific information needed by several external tools (Scram, CMT, pacman, etc) </li></ul></ul><ul><ul><li>Required investing more time that is now saved when a new installation is needed </li></ul></ul><ul><li>EGEE collaboration started successfully </li></ul><ul><ul><li>2 FTE contributed to the SPI project </li></ul></ul><ul><ul><li>SPI was involved in presenting/adapting its existing services. In particular the collaboration is the Middleware (JRA1) and Quality Assurance (JRA2) activities. </li></ul></ul><ul><ul><li>The services involved were Savannah, QA and Testing in particular. </li></ul></ul><ul><li>Savannah service required the implementation of new features to suit LCG and EGEE needs. </li></ul>
  27. 27. Proposed Milestones for 2004 Q4 and 2005 Q1 Definition of use cases and plans for the config/make solution 2004/11/30 New release of Savannah 2004/11/30 Definition of software configuration information in XML OTW 2004/11/20 Definition and implementation of the validation procedures of the installations of the external software OTW 2004/11/15 Pacman cache for binaries of external and LCG packages OTW 2004/11/15 Adapt the QA reports to EGEE QA standards Done 2005/10/31 Naming and coding conventions for EGEE Middleware in the build system Done 2004/10/15
  28. 28. Proposed Milestones (II) Independent build and release of partitions of the LCG software 2005/2/28 QA Tests Coverage reports in production 2005/1/15 Definition of build information in XML 2005/1/15 SPI Librarian performs the releases and pre-releases of the LCG software 2004/12/15 Definition of the products and partitions of the LCG software, for individual partial releases and bug releases 2004/12/15 Sources distribution and build of external and LCG software 2004/12/15 QA reports in production as deliverable of the LCG projects 2004/12/1
  29. 29. Proposed Milestones (III) <ul><li>Further milestones will be defined according to the recommendations of the LHCC review </li></ul>Generate SCRAM build information from XML configuration 2005/2/28 Generate CMT configuration information from XML configuration 2005/2/28 Build LCG software with config/make solution from XML configuration 2005/2/28
  30. 30. Summary <ul><li>SPI provides a set of stable services that fully use the current resources </li></ul><ul><ul><li>Savannah, External Software, Testing Frameworks, Software Distribution, Build and Release, QA Activities </li></ul></ul><ul><li>Resources will be reduced at the end of 2005 and we will not be able to add new activities </li></ul><ul><ul><li>We will maintain and improve the existing ones </li></ul></ul><ul><ul><li>No requests for major new services from LCG, need to adapt or interface to external tools </li></ul></ul><ul><li>We refer to and follow the guidelines of the Architects Forum </li></ul><ul><ul><li>Representing the users and steering our priorities </li></ul></ul><ul><li>Whenever possible we also do help/work for experiments specific needs </li></ul><ul><ul><li>Installations of additional software, interface to their build/distribution systems, add features </li></ul></ul>
  31. 31. Proposed focus for 2005 <ul><li>Continue to automate and centralize the cycle for software build/test/release/distribution </li></ul><ul><li>Provide software that can be installed or downloaded on several platforms using standard tools </li></ul><ul><li>Increase work on the QA and testing activities that was particularly difficult in 2004 </li></ul><ul><li>Focus more on encouraging other areas and projects to use uniform solutions provided </li></ul><ul><li>Further milestones will be defined according to the recommendations of the LHCC review </li></ul>
  32. 32. BACKUP MATERIAL <ul><li>BACKUP MATERIAL </li></ul>
  33. 33. Resources % Responsible Services Testing Frameworks QA reports, Software distribution QA reports and Testing Frameworks Build tools, Software Distribution Documentation, Workbook, Policies, Web LCG Librarian, Build and Configuration Savannah service, bug and devel. portal External software, installation and distrib. 100 J.Benard (8/04) 10 J.Moscicki 10 M.Gallas 100 Y.Patois (4/04) 70 A.Aimar 70 A.Pfeiffer(5/04) 100 Y.Perrin 75 E.Poinsignon
  34. 34. Summary of actions on 2003 recommendations (I) <ul><li>CVS service to IT </li></ul><ul><ul><li>Passed to IT after validation and intensive testing </li></ul></ul><ul><ul><li>We migrated all projects ourselves, no problems </li></ul></ul><ul><li>Savannah portal </li></ul><ul><ul><li>In synch with the open source </li></ul></ul><ul><ul><li>Close collaboration with the main Savane (“re-brand” of the open source) developer </li></ul></ul><ul><li>Documentation and website </li></ul><ul><ul><li>Our website is stable and be keep it up to date </li></ul></ul><ul><ul><li>Testing also “wiki” or other systems to easily allow multiple authorship </li></ul></ul><ul><li>External Software service </li></ul><ul><ul><li>Maintain original structure of the installed packages </li></ul></ul><ul><ul><li>Automated installations and making available all installation scripts and tools </li></ul></ul><ul><ul><li>Some tools for which we have verification material we check them, more on the way </li></ul></ul>
  35. 35. Summary of actions on 2003 recommendations (II) <ul><li>QA activities </li></ul><ul><ul><li>Automated generation of reports, a web form is being put in place </li></ul></ul><ul><ul><li>Resources (junior) joined only in August 2004, for now no resources for verification of compliance to the QA criteria defined. </li></ul></ul><ul><ul><li>No resources for verification of compliance to QA and testing standards </li></ul></ul><ul><li>Build System and Infrastructure </li></ul><ul><ul><li>Librarian role filled in June 2004 and very beneficial to centralize this activity </li></ul></ul><ul><ul><li>Developed scripts to centrally do the releases and installations </li></ul></ul><ul><ul><li>We performed the certification of all external and LCG software for SLC3, as test of the automatic installation scripts </li></ul></ul><ul><ul><li>Config/make solution is going to be achieved via the XML description files that he had to implement in order to support several tools for build and distribution </li></ul></ul><ul><ul><li>XML description will allow to support several build systems </li></ul></ul><ul><ul><li>Generate and keep up to date configuration files for CMT </li></ul></ul><ul><li>Software distribution </li></ul><ul><ul><li>Binaries: python-based and pacman distribution </li></ul></ul><ul><ul><li>Sources: distribution of all external and LCG software and all the SPI tools to build from sources </li></ul></ul><ul><ul><li>Interaction with Deployment and EGEE in this area but not major common solutions adopted </li></ul></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×