YAIM acceptance criteria

If you are certifying a YAIM patch, please, take into account the following list to know whether the relevant YAIM modules are implementing the listed items.

%config(noreplace) for node-info.d/ files in the spec file

• Description: RPM spec files have a macro, %config, that is used to mark config files so that edits to config files won't get lost during a subsequent upgrade. Without this, the config files from an upgrade would tend to overrite the edited files from the previous version. This is the case for node-info.d files that are modified sometimes by site admins to include their own functions. To preserve the modified node-info.d files, it's necessary to use the %config macro.
• Action: In the spec file of the YAIM module, the node-info.d files should be defined as %config(noreplace).
• Affected YAIM modules: All.

Patch #1672 : New function

• Description: Services can now publish the gLite version they are running with a new info provider called glite-info-provider-release. There is a new function in YAIM, config_gip_service_release, that does the necessary configuration actions.
• Action: config_gip_service_release should be added in the function list of the affected configuration targets.
• 3.1 glite-yaim-core version: 4.0.3-13
• Affected YAIM modules: All the YAIM modules whose configuration targets are configuring the gip.

Bug #29906 : New function

• Description: Due to a vulnerability issue in VOMS, the way trusted VOMS servers are specified in the vomsdir directory had to change. The vomsdir directory normally contains the host certificate files of the trusted VOMS servers. But now the new config_vomsdir function creates the vomsdir directory with a set of subdirectories per supported VO, that contain a .lsc file per supported VOMS server. The .lsc file contains the DN of the VOMS server host certificate and the CA DN that has signed the certificate. Once this new structure is in place, the host certificate file of the VOMS server, if still present in vomsdir, will be ignored.
• Action: config_vomsdir should be added in the function list of the affected configuration targets.
• 3.1 glite-yaim-core version: 4.0.3-6
• Affected YAIM modules: clients (ui, wn, vobox), lcg-ce, wms, lb, rb, lfc (mysql and oracle), dcache (admin gdbm, admin postgres and pool), se classic and dpm (disk, mysql and oracle).

Patch #1190 : New function

• Description: To publish the Gridftp transfer records directly into Gridview we need to configure the Gridview client on the SEs. In order to do this, a new variable is needed to set the location and filename of the gridftp server logfile on the different types of SEs. The new function config_gridview_se implements the necessary configuration actions to do this.
• Actions: config_gridview_se should be added in the function list of the affected configuration targets.
• 3.1 glite-yaim-core version: 4.0.3-8
• Affected YAIM modules: dcache (admin gdbm, admin postgres and pool), se classic and dpm (disk, mysql and oracle).

MAN pages

• Description: All the YAIM modules should provide man pages describing how to configure each configuration target provided in the module. For a template, please check the Developers guide.
• Affected YAIM modules: All.

Function headers

• Description: All the YAIM functions should contain a header describing what the function does. This is very important to maintain documentation like the functions dictionary. For a template, please check the Developers guide.
• Affected YAIM modules: All.

Specific variables

• Description: site-info.def variables that are specific to the configuration of a node type will be distributed from now on under the services/ directory of the corresponding YAIM module and not in site-info.def file in yaim core.
• Affected YAIM modules: All.

Location of YAIM /services directory

• Description: YAIM directory /services should be distributed in /opt/yaim/examples/siteinfo/services/.
• Affected YAIM modules: All.

Patch #1278 : New function

• Description: There's a new info provider that will generate the GlueService attributes. This info provider has been written by Stephen Burke and it's available for a set of services: LB, WMS, VOBOX, BDII, dcache, DPM and MyProxy.
• Actions: config_info_service_<node-type> should be created for each service and added in the function list of the affected configuration targets.
• Affected YAIM modules: All.

For more information please check the config_info_service YAIM wiki.

Acceptance criteria status table

This table was finished on 18/01/2008. Information about particular nodes may have been updated later. The date of the last update can be checked in the node specific cell. The yaim module rpm column contains either the version of the yaim module used to check the acceptance criteria for the first time or the latest Savannah patch where the acceptance criteria has been included in the yaim module.

configuration target	yaim module rpm	%config	config_gip_service_release (available >= yaim-core 4.0.3-9)	config_vomsdir	config_gridview_se	man pages	function headers	specific variables
3.1 ui	glite-yaim-core-4.0.3-6 glite-yaim-clients-4.0.1-1	Failed	-	Failed	-	Failed	OK except: config_gsissh config_workload_manager_client	NA
3.1 wn	glite-yaim-core-4.0.3-6 glite-yaim-clients-4.0.1-1	Failed	-	Failed	-	Failed	See ui	NA
3.1 bdii_top	glite-yaim-core-4.0.3-6 glite-yaim-bdii-4.0.1-6	Failed	Failed	-	-	Failed	OK	NA
3.1 bdii_site	glite-yaim-core-4.0.3-6 glite-yaim-bdii-4.0.1-6	Failed	Failed	-	-	Failed	See bdii_top	NA
3.1 torque_server	glite-yaim-core-4.0.3-6 glite-yaim-torque-server-4.0.1-4	Failed	-	-	-	Failed	OK	NA
3.1 torque_utils	glite-yaim-core-4.0.3-6 glite-yaim-torque-utils-4.0.2-1	Failed	-	-	-	Failed	OK	NA
3.1 torque_client	glite-yaim-core-4.0.3-6 glite-yaim-torque-client-4.0.1-1	Failed	-	-	-	Failed	OK	NA
3.0 rb	glite-yaim-core-4.0.3-6 glite-yaim-rb-4.0.1-1	Failed	Failed	Failed	-	Failed	OK	NA
3.1 lcg-ce (28/01/2008)	Patch #1661	OK	Failed	OK	-	OK	OK	OK
3.0 mon (30/01/2008)	Patch #1537	OK	-	-	-	OK	OK	OK
3.0 e2emonit	glite-yaim-core-4.0.3-6 glite-yaim-e2emonit-4.0.1-1.noarch.rpm	Failed	Failed	-	-	Failed	OK	NA
3.1 vobox	glite-yaim-core-4.0.3-6 glite-yaim-clients-4.0.2-7	Failed	Failed	Failed	-	Failed	see ui	NA
3.1 myproxy (12/02/2008)	Patch #1682	OK	OK	-	-	OK	OK	OK
3.1 se classic (04/02/2008)	Patch #1576	OK	OK	OK	OK	OK	OK	OK
3.1 amga (30/01/2008)	Patch #1472	Failed	-	-	-	Failed	OK	NA
3.1 ftm	glite-yaim-fts-4.0.6-2 glite-yaim-core-4.0.3-6	Failed	-	-	-	Failed	Failed for all the functionsi	NA
3.1 dpm mysql	glite-yaim-core-4.0.3-6 glite-yaim-dpm-4.0.0-9	OK	Failed	Failed	Failed	OK	Failed all except config_gip_dpm	NA
3.1 dpm disk	glite-yaim-dpm-4.0.0-11 glite-yaim-core-4.0.3-6	OK	Failed	Failed	-	OK	see dpm mysql	NA
3.1 lfc mysql	glite-yaim-lfc-4.0.0-10 glite-yaim-core-4.0.3-6	OK	OK	Failed	-	OK	Failed for all functions	NA
3.1 lfc oracle	glite-yaim-core-4.0.3-6 glite-yaim-lfc-4.0.0-10	OK	OK	Failed	-	OK	see lfc mysql	NA
3.1 wms (30/01/2008)	Patch #1612	Failed	Failed	Failed	-	Failed	Failed for all except: config_condor_wms	OK
3.1 lb	glite-yaim-core-4.0.3-6 glite-yaim-lb-4.0.1-2	Failed	Failed	Failed	-	Failed	Failed for all except: config_jobmon	NA
3.0 dcache pool (30/01/2008)	glite-yaim-core-4.0.0-12 glite-yaim-dcache-4.0.0-2	Failed	Failed	Failed	Failed	Failed	Failed	NA
3.0 dcache admin postgres (30/01/2008)	glite-yaim-core-4.0.3-6 glite-yaim-dcache-4.0.0-2	Failed	Failed	Failed	Failed	Failed	Failed	NA
3.0 dcache admin gdbm (30/01/2008)	glite-yaim-dcache-4.0.0-2 glite-yaim-core-4.0.3-6	Failed	Failed	Failed	Failed	Failed	Failed	NA
3.0 fts2	glite-yaim-core-4.0.0-12 glite-yaim-fts-4.0.0-7	It's in services/ but not in node-info.d	Failed	-	-	Failed	Failed	NA
3.0 fta2	glite-yaim-core-4.0.0-12 glite-yaim-fts-4.0.0-7	It's in services/ but not in node-info.d	Failed	-	-	Failed	Failed	NA
condor utils (30/01/2008)	Patch #1522	Failed	-	-	-	Failed	OK	OK
sge-utils (30/01/2008)	Patch #1474	OK	-	-	-	OK	OK	OK
mpi	glite-yaim-mpi-0.1.6-3	OK	-	-	-	OK	OK	NA