<configuration> <plugins> <framework_definitions> <framework_definition>/path/to/CustomFWD1/xml</framework_definition> <framework_definition>/path/to/CustomFWD2/xml</framework_definition> </framework_definitions> </plugins> ... <configuration>
node1 # role: head role: compute node2 # role: compute node3 # implicitly assumed to be a compute node node4 #node5
- boot - Provides software imaging / provisioning capabilities.
- compute - Is a compute resource (mutually exclusive with).enhanced
- enhanced - Provides enhanced compute resources, for example, contains additional memory (mutually exclusive with compute).
- external - Provides an external network interface.
- head - Alias for the union of boot, external, job_schedule, login, network_address, and storage.
- job_schedule - Provides resource manager / job scheduling capabilities.
- login - Is an interactive login system.
- network_address - Provides network address to the cluster, for example, DHCP.
- storage - Provides network storage to the cluster, like NFS.
node1 # subcluster: eth node2 # subcluster: eth node3 # subcluster: eth node4 # subcluster: eth node5 # subcluster: ib node6 # subcluster: ib node7 # subcluster: ib node8 # subcluster: ib
Ignore subclusters when running cluster data providers. That is, cluster data providers will span subclusters. The default is not to span subclusters.
- through the environment by running:
- ‘export CLCK_TURN_OFF_ENV_PROPAGATION=true’
- through turning it off in clck.xml (or whichever configuration file is used)
- or by running with the ‘-e’ flag
<collector> <extension>mpi.so</extension> </collector>
- unixUses POSIX advisory locks when locking the database. Note that the implementation of POSIX advisory locks on some filesystems, for example, NFS, is incomplete and/or buggy. This value should usually only be selected when the database is located on a local filesystem. unix-dotfile - Uses dot-file locking when locking the database. This value usually works around filesystem implementation issues related to POSIX advisory locks. This is the default value
- unix-exclObtains and holds an exclusive lock on the database file. All concurrent database operations will be prevented while the lock is held. This value may help in the event of database errors during data collection of if collected data is missing from the database
- unix-noneNo locking is used. This option should only be used if there is a guarantee that only a single writer will modify the database at any given time. Otherwise, this value can easily result in database corruption if two or more processes are writing to the database concurrently.