Project

General

Profile

Feature #5020

Change condor configuration files order and add a new one

Added by Marco Mambelli over 6 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
Start date:
11/27/2013
Due date:
% Done:

0%

Estimated time:
Stakeholders:
Duration:

Description

Condor RPM has a config file /etc/condor/config.d/00personal_condor.config that interferes with both the frontend and the factory configuration.
In the installation instructions we tell the admin to remove the file but a yum or rpm update that involves condor RPM will bring the file back.

The suggestion is to
1. add a new file overriding all the setting in /etc/condor/config.d/00personal_condor.config, /etc/condor/config.d/00personal_condor.config-override (see below for content) and
2. to change the name of all gwms files to come after other condor configuration files.

Either 1 or 2 are sufficient to solve the problem. Both of them would add more security.

The main problem are
/etc/condor/config.d/00_gwms_general.config (frontend)
/etc/condor/config.d/00_gwms_factory_general.config (factory)
that both come before 00personal_condor.config in lexicographic order.

I would suggest to start gwms configuration file names with 20_gwms, summing 20 to all the numbers, e.g.:
20_gwms_general.config
21_gwms_collectors.config
22_gwms_schedds.config
23_gwms_local.config
31_gwms_secondary_collectors.config
or
20_gwms_factory_general.config
21_gwms_factory_collectors.config
22_gwms_factory_schedds.config
23_gwms_factory_local.config
31_gwms_factory_secondary_collectors.config

Here is the content of 00personal_condor.config-override reflecting line by line the content of 00personal_condor.config
  1. cat /etc/condor/config.d/00personal_condor.config-override
    1. What machine is your central manager?

CONDOR_HOST = $(FULL_HOSTNAME)

  1. Set of confguration to override the personal condor config

COLLECTOR_NAME = ToOverride
START = FALSE
SUSPEND = FALSE
PREEMPT = FALSE
KILL = FALSE
DAEMON_LIST = MASTER

I tested this on a RPM installation with 3.2.2. This will do no harm and protect from the personal rpm config file.
The main interference is that if condor starts a startd, it takes over the jobs, so the most important line in the override is DAEMON_LIST = MASTER,
which is also in both 00_gwms_general.config and 00_gwms_factory_general.config

History

#1 Updated by Igor Sfiligoi over 6 years ago

How would this work when a sysadmin does a you update?
From an existing (old style) RPM.

#2 Updated by Parag Mhashilkar over 6 years ago

  • Target version set to v3_2_x

#3 Updated by Burt Holzman over 6 years ago

  • Assignee set to Marco Mambelli

#4 Updated by Parag Mhashilkar about 5 years ago

  • Target version changed from v3_2_x to v3_2_9

#5 Updated by Marco Mambelli about 5 years ago

The problem went away

The current HTCondor installation (8.2.7 from OSG) has no more 00_personal:

$ls /etc/condor/config.d/
00-restart_peaceful.config  10-batch_gahp_blahp.config

Both those file do not start demons and do not interfere with the GlideinWMS installation.
This does not mean that future packagings of HTCondor will not reintroduce the problem.

The problem is actually there when installing condor.bosco (e.g. on a factory supporting batch submission) that includes "60-campus_factory.config" that starts the campusfactory daemons.
Given the limited case I will update the documentation instructing to remove the file and close this ticket.

#6 Updated by Marco Mambelli almost 5 years ago

  • Status changed from New to Resolved

The documentation has been updated.
There is no need for new config files.

#7 Updated by Parag Mhashilkar almost 5 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF