YAIM module feature list

General features

YAIM packages

• Description: In order to be able to build packages with ETICS in a portable way, we need to get rid of rpm specific commands. For more information visit the YAIM developers guide, Makefile and ETICS
• Action:
  • In case you have created man pages, change in your Makefile any reference to RPM_BUILD_ROOT and use the ${prefix}/share/man/man1 path instead.
  • For each YAIM configuration in ETICS, please, update the following items:
    • Remove from the Build commands the packaging and prepublish commands.
    • Add in the Build commands the install command with make install prefix=${prefix}

• Affected YAIM modules: All.

YAIM version

• Description: Check this link.
• Action: Follow the steps described in the previous link.
• Affected YAIM modules: All.

edgusers

• Description: Check this link.
• Action: Use the variables describing the user and group names and don't hardcode these names on your functions. Moreover, make sure that in case you run config_edgusers, you call this function at the beginning of your function list since many functions rely on the users created there.
• Affected YAIM modules: All the yaim modules using any of the users in edgusers.conf.

%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.

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.

Return 0

• Description: All YAIM functions should return 0 at the end as succesful exit code.
• Affected YAIM modules: All.

New functions

Patch #1672 : config_gip_service_release

• 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 : config_vomsdir

• 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 : config_gridview_se

• 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).

Patch #1278 : config_info_service_<node-type>

• 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.

-- MariaALANDESPRADILLO - 05 Aug 2008