The vm-config file lists the scripts that should be run to start up each node. For nodes that are not listed in vm-config, a default start up routine is provided in the types file.
Suppose we decide to place our runtime daemons on the service nodes according to following table, and that yod processes will run only on the two nodes on which the MOMs are running.
| if-0.n-6.r-3 | bebopd |
| if-0.n-4.r-3 | PBS server and scheduler |
| if-0.n-2.r-3 | PBS MOM |
| if-0.n-0.r-3 | PBS MOM |
The vm-config file lines for these service nodes would look like this:
# # Bebopd if-0.n-6.r-3:ptl-config= ... user-env=bebopd+pbs pbs-env=bebopd-support-only # PBS server/scheduler if-0.n-4.r-3:ptl-config= ... pbs-env=scheduler pbs-env=server # PBS MOM nodes if-0.n-0.r-3:ptl-config= ... pbs-env=mom user-env=yod-support if-0.n-2.r-3:ptl-config= ... pbs-env=mom user-env=yod-support
The config script invokes the scripts listed in vm-config with the argument start and followed by the arguments named in the vm-config file.
The ... indicates several other scripts were left out that would normally be run. For example, any scripts that mount file systems should be executed before user-env and pbs-env. See the vm-config file on a running Cplant VM, or in the source code repository in /top/scripts/etc.in, for an example.
The ptl-config script starts the Cplant message passing modules. These must be running before any portals processes are started.