CE Maintenance

This topic is for issues with running pilots on the site, making sure that dirac submits pilots to each available site.

Adding new CEs to the Configuration Service

In the CE2CS agent e-mail, there is something like:

CE: hepgrid97.ph.liv.ac.uk, GOCDB Name: UKI-NORTHGRID-LIV-HEP
SystemName: ScientificSL, SystemVersion: Carbon, SystemRelease: 6.3
hepgrid97.ph.liv.ac.uk:8443/cream-pbs-long Production

dirac-admin-add-site DIRACSiteName UKI-NORTHGRID-LIV-HEP hepgrid97.ph.liv.ac.uk

The first block gives the new queue properties, and the command below gives a way to register that CE in the CS. If the corresponding site DOES NOT exist in the CS, the command can be used. If it does, the CE must simply be added to the list of CEs in /Resources/Sites/GRID/SITE/CE. The CE2CS will take care of adding and updating the corresponding sections later.

Note

One thing to remember: the info provided comes from the BDII, and that proved to be inconsistent in the past many times. In particular, some CEs are not allowing in fact the ILC VO despite the advertisement in the BDII. Checking the SiteDirector and the TaskQueueDirector can help find those (unauthorized credentials errors). Also, the CE2CS does not remove old CEs that were removed so keep an eye at the EGI DOWNTIMES mails as they usually advertise the final removal of CEs.

Keeping CEs running

• Have a look at the emails from the CE2CS agent. If the OS changes, make sure the dirac system knows what platform this corresponds to. Check this in the CS /Resources/Computing/OSCompatibility
• Check the SiteDirector, TaskQueueDirector, Matcher for error messages
• Check the EGI Emails about decomissioning of CEs or queues

-- AndreSailer - 2015-01-29