Dependency Challenge

As part of the gLite restructuring process we need to challenge the dependencies of each component.

Developers actions (1)

For each component below the responsible developer should provide:

• the list of ETICS components that are part of it, as extracted from http://lxmrrb3703.cern.ch/rundir/glite_branch_3_1_0_x86_slc_4/reports/reportModules.html For each ETICS component should provide:
  • the list RPMs produced, corresponding to the RPMs listed in the "Artefacts" section of the ETICS logs;
  • the list of build dependencies, corresponding to the content of the "Dependencies" page of the ETICS reports ("B" tag);
  • the list of runtime dependencies, corresponding to the true list of RPMs on which each produced RPM depends. It was pointed out that the runtime dependencies reported in the "Dependencies" page of the ETICS reports ("R" tag) is not reliable as some dependencies are set only on the spec files denerated dynamically during the build phase. Akos suggested a way for generating such list. See in the appendix an example for DM components
• if available the internal analysis already done by the developers.

This is expected to take not more than one week.

Reviewers actions

For each component a reviewer will be appointed. The reviewer should:

• provide a critical analysis of the dependencies;
• contact the responsible developer to get clarifications;
• complement the material provided by the developers with her analysis and produce a short report that represents
  • the work to be done in the time frame of one full week of work of development team, as agreed with the developers;
  • further work that may require more time but that would be important to do in the future. Note that the report should already represent the result of the agreement between reviewer and developer.

This is expected to take not more than two weeks.

Developers actions (2)

At the end of the review the responsible person should report about the status of the implementation of the changes agreed with the reviewer. Just change the icon with in the last column. If additional information is needed a report should be linked in the same column.

This is expected to take not more than three weeks including testing.

Developers actions (3)

During the TCG on 19/9/2007 it has been asked to track the SL4 readiness for these components. Two more columns have been added, one for the server and one for the clients. Client here means all the software that may need to be included in the UI or WN metapackages. The developers have to green-tick the components as soon as they are ready for certification after the implementation of the one-week changes. If the client or the server part of the component doesn't exist simply remove any symbol in that cell.

Dependency challenge status

Component	Priority	Responsible	Developer report	Reviewer	Reviewer Report	Implementation Status	Ready for certification
							Server	Client
WMS	HIGH	Francesco Giacomini	Report	Krzysztof Nienartowicz	Report	Report
WMS-UI	HIGH	Fabrizio Pacini, Alessandro Maraschini	Report	Krzysztof Nienartowicz	Report
Logging&Bookkeeping	HIGH	Ales Krenek	Report	Fabrizio Pacini, Alessandro Maraschini	Report
Job Provenance	low	Ales Krenek	Report	Fabrizio Pacini, Alessandro Maraschini	Report
gLite CE	low	Francesco Prelz	Report	Steve Fisher	Report
BLAH	HIGH	David Rebatto	Report	Steve Fisher	Report
CREAM	HIGH	Massimo Sgaravatto, Paolo Andreetto	Report	Steve Fisher	Report
CEMon	HIGH	Massimo Sgaravatto, Paolo Andreetto	Report	Steve Fisher	Report
DGAS	Medium	Andrea Guarise	Report	Steve Fisher	Report
APEL	HIGH	Dave Kant	Report	Andrea Guarise	Report	Report
R-GMA	Medium	Steve Fisher	Report	Ales Krenek	Report	Report
Service Discovery	Medium	Steve Fisher	Report	Ales Krenek	Report	Report
BDII	HIGH	Laurence Field	Report	Rosario Piro	Report
GIP	HIGH	Laurence Field	Report	Rosario Piro	Report
FTS	HIGH	Gavin McCance, Akos Frohner	Report	Gerben Venekamp	Report
LFC	HIGH	Jean-Philippe Baud, Akos Frohner	Report	Steve Traylen	Report
Hydra	Medium	Akos Frohner	Report	John White	Client + Service
GFAL	HIGH	Remi Mollon, Akos Frohner	Report	Francesco Giacomini	Report	Reply
lcg_utils	HIGH	Remi Mollon, Akos Frohner	Report	Francesco Giacomini	Report	Reply
DPM	HIGH	Jean-Philippe Baud, Akos Frohner	Report	Steve Traylen	Report
EIS-utils	HIGH	Andrea Sciaba'	Report	Francesco Giacomini	Report
EDS	not used	Akos Frohner	Report	John White	Report
SSSS	Medium	Hakon Sagehaug	Report	John White	Report
VOMS	HIGH	Vincenzo Ciaschini	Report	Akos Frohner	Report	Response
VOMS-Admin	HIGH	Andrea Ceccanti	Report	Akos Frohner	Report	Response
G-Pbox	postponed	Vincenzo Ciaschini
glexec	HIGH	Gerben Venekamp	Report	Steve Fisher	Report
LCAS/LCMAPS	HIGH	Oscar Koeroo	Report	Steve Fisher	Report
gJAF	low	Yuri Demchenko, Hakon Sagehaug	Report	Massimo Sgaravatto, Paolo Andreetto	Report
Delegation framework	low	Akos Frohner	Report	Gavin McCance	Report
trustmanager	low	Joni Hahkala	Report	Daniel Kouril	Report
Proxy renewal	HIGH	Daniel Kouril	Report	Gavin McCance	Report
gSOAP plugin	low	Daniel Kouril	Report	John White	Report
CGSI-gSOAP	low	Akos Frohner	Report	John White	Report
util-java	low	Joni Hahkala	Report	Valery Tschopp	Report
Gridsite	HIGH	Andrew McNab	Report	Fabrizio Pacini, Alessandro Maraschini	Report
SLCS	low	Christoph Witzig	Report	Oscar Koeroo	Report

Appendix

find dist/org.glite -name '*.rpm' | while read rpm; do echo ""; echo ""; basename $rpm; rpm -qp $rpm --requires; done | grep -v '^/bin/sh' | grep -v '^rpmlib' >~/glite-data_R_3_1_35_1.runtime.dependencies

Last edit: LaurenceField on 2008-01-21 - 13:23

Maintainer: ClaudioGrandi