Bdii2CSAgent
The Bdii2CSAgent performs checking BDII for availability of CE resources for a given or any configured VO. It detects resources not yet present in the CS and notifies the administrators. For the CEs already present in the CS, the agent is updating if necessary settings which were changed in the BDII recently
The following options can be set for the Bdii2CSAgent.
Bdii2CSAgent
{
#Time between cycles in seconds
PollingTime = 14400
BannedCEs =
# Only treat these sites
SelectedSites =
# Process Computing Elements
ProcessCEs = yes
# Mail Notifications options
MailTo =
MailFrom =
VirtualOrganization =
# Flag to turn to False if you want this agent to write in the CS
DryRun = True
# Host to query, must include port
Host = cclcgtopbdii01.in2p3.fr:2170
# If True, add single core queues for each Multi Core Queue and set
# RequiredTag=MultiProcessor for those
InjectSingleCoreQueues = False
}
- class DIRAC.ConfigurationSystem.Agent.Bdii2CSAgent.Bdii2CSAgent(*args, **kwargs)
Bases:
AgentModule
- __init__(*args, **kwargs)
Defines default parameters
- am_Enabled()
- am_checkStopAgentFile()
- am_createStopAgentFile()
- am_getControlDirectory()
- am_getCyclesDone()
- am_getMaxCycles()
- am_getModuleParam(optionName)
- am_getOption(optionName, defaultValue=None)
Gets an option from the agent’s configuration section. The section will be a subsection of the /Systems section in the CS.
- am_getPollingTime()
- am_getShifterProxyLocation()
- am_getStopAgentFile()
- am_getWatchdogTime()
- am_getWorkDirectory()
- am_go()
- am_initialize(*initArgs)
Common initialization for all the agents.
This is executed every time an agent (re)starts. This is called by the AgentReactor, should not be overridden.
- am_removeStopAgentFile()
- am_secureCall(functor, args=(), name=False)
- am_setModuleParam(optionName, value)
- am_setOption(optionName, value)
- am_stopExecution()
- beginExecution()
- endExecution()
- execute()
General agent execution method
- finalize()
- initialize()
Gets run paramaters from the configuration