DIRAC3 Rollout Check List

This page intends to define the steps to be carried out before being able to replace DIRAC2 with DIRAC3 for routine production. In particular emphasis is set on the dependencies of components.

The first table defines a set of icons (that can be completed) for indicating the status of each task. If needed complementary explanations can be added after the tasks table, with it possible an anchor and a link in the table (see for example task 0).

Tick mark	Description
	Critical because no manpower
	To do, manpower assigned
	Under design
	Implementing
	Under test
	Done, checked

The date is that expected for the completion of the work. When completed, it is the actual date of completion.

Task ID	Task description	Depends on	Assigned to	Completion date	Status
0	Validation
0.1	Simulation	1.1.1,		start on 07/14
0.2	Reconstruction
0.3	Stripping
0.4	Analysis
1	Job workflow and modules
1.1	Workflows		Joel
1.1.1	Simulation workflow	1.2, 1.3	Joel
1.1.2	Reconstruction workflow	1.2, 1.3, 1.4	Joel
1.2.3	Stripping workflow	1.2, 1.3, 1.4	Joel
1.2	Output upload		Joel
1.2.1	File upload module	2.1, 2.3.2, 5.2	Joel
1.2.2	Logfile upload	2.1	Joel
1.2.3	Bookkeeping module (old)	2.1	Joel
1.2.4	Bookkeeping module (new)	2.1, 6.1	Joel
1.2.5	Check destination for all files		Joel
1.3	CheckLogfile modules		Joel
1.3.1	AnalyseLogfile		Joel
1.4	File status report		Joel
1.4.1	ProcessingDB report API		Andrei
1.4.2	Replica report API		Andrew
1.5	Job Monitoring		Joel
1.5.1	Application Status is not to be overwritten after an Application Error is reported		Joel
2	!VOBox
2.1	RequestDB		Andrew
2.1.1	Client API for requests		Andrew
2.1.2	Request DB service		Andrew
2.2	VOBox agents
2.2.1	Request Forwarding Agent	5.1	Andrew	09-07-08
2.2.1	Transfer agent	5.1	Andrew
2.2.2	DISET agent		Andrew
2.2.3	File Registration agent		Andrew
2.2.4	File Removal agent		Andrew
2.3	VOBox installation		Raja
2.3.1	VOBox installed	2.2	Raja
2.3.2	VOBox registered in CS	2.3.1	Raja
3	WMS		Andrei, Stuart
3.1	General
3.1.1	Matching with priority		Stuart
3.1.2	SAM jobs handling		Stuart
3.1.3	Generic pilots framework	7.3.1	Stuart, Andrei
3.2	Optimisers		Stuart
3.2.1	Uses LFC replica status (by default)		Andrew
3.2.2	Get ancestor files (new BK)	6.3	Stuart
3.3	Stager		Stuart
3.3.1	Problematic files report		Stuart
3.3	Job failure agent		?
4	Production DB		Stuart
4.1	Use LFC replica status		Stuart
5	DMS
5.1	Transfer DB		Andrew
5.1.1	Transfer DB service		Andrew
5.1.2	Transfer monitoring		Andrew
5.1.3	Transfer report to integrity DB	5.2.1	Andrew
5.2	Integrity DB		Andrew
5.2.1	Integrity DB service		Andrew
5.2.2	Integrity DB population agents		Andrew
5.2.3	Integrity DB resolution agents		Andrew
5.2	SE destination selection API		Andrei
6	New Bookkeeping		Zoltan
6.1	BK production service
6.2	BK manager		Zoltan
6.2.1	BK monitoring		Zoltan
6.3	BK client API		Zoltan
6.4	BK migration		Elisa
6.5	BK translation agent		Zoltan
7	Sites Configuration
7.1	Storage		Andrew
7.1.1	All STD available and published		Andrew
7.1.2	SEs in DIRAC CS		Andrew
7.1.3	SE reports to SAM		Roberto
7.1.4	Storage usage reports generated		Andrew
7.2	Computing Elements
7.2.1	CEs in CS		Vladimir
7.2.2	SAM jobs submission	3.1.2	Joel
7.2.3	DIRAC mask handling		Vladimir
7.3	VO administration
7.3.1	Generic pilot role advertised		Roberto
7.3.2	Operations crew in DIRAC authorisation		??
8	Operational verifications
8.1	Data Management
8.1.1	Selection of output SE as expected	5.2	Joel
8.1.2	File upload OK (failover)		Joel
8.1.2	Output files LFN according to convention		Joel
8.1.3	LFC registration OK (failover)		Joel
8.1.4	Old BK registration OK (old convention)		Joel
8.1.5	New BK registration OK (new convention)		Joel
8.1.6	Logfile upload OK (failover)		Joel
8.1.7	Shared Area Status		Joel
8.1.8	Combined software installation		Joel
8.2	Production tools
8.2.1	Correct definition of input for processing		Stuart
8.2.2	Ancestor retrieval for stripping		Stuart
9	Framework
9.1	Proxy Handling		Adria/Ricardo
9.2	Duplicated entries in logging info		Stuart

Complementary information

Please try and keep the same order as in the table above, add an anchor an a link in the table if needed

Validating jobs

This is the ultimate validation that each type of job can tun. Of course the dependency of these is on most of the other items below.

Generic Pilots Framework

This implies the definition of the pilot role in VOMS, the attribution of this role to either a personal or host DN. It also involves handling the case when some sites would not accept receiving generic pilots. In this case user pilots should be submitted.

-- PhilippeCharpentier - 03 Jul 2008