Chapter 6. Quick Start

PoD Quick Start:

  1. Initialize PoD environment: Section 7.1, “Environment”
  2. Start PoD server: Section 7.2, “Server”
  3. Submit PoD workers to start dynamic PROOF cluster: Section 7.3, “Job Manager”
  4. Check status of dynamic PROOF cluster: Section 7.4, “PROOF workers”
  5. Use the PROOF cluster for an analysis: Section 7.6, “Analysis”
  6. Restart PoD workers (if cluster needs to be reloaded): Section 7.3, “Job Manager”
  7. Stop PoD server: Section 7.7, “How to shut down PoD”

The following is the example to illustrate the Quick Start. We use PoD with the SSH plug-in to setup our PROOF cluster on the bunch of the machines, which are described in the pod_ssh.cfg configuration file.

Detailed descriptions of the commands and of the configuration file can be found in the Chapter 10, Command-line interface.

PoD Environment:



The current implementation of the SSH plug-in requires users to have a public key access (or password less) to destination remote hosts (worker nodes).

Starting the cluster:

pod-server start
pod-server status
pod-ssh -c pod_ssh.cfg submit
pod-ssh status
pod-info -n
pod-info -l

The Dynamic PROOF cluster is ready to perform user's analysis code...

[Important]Remote Environment

With SSH plug-in it is very often the case, that PoD can't start workers, because xproofd/ROOT is not in the PATH on worker nodes. If your PoD job fails, just after submission it shows DONE status. You may want to check the remote log files see the section called “Examples” from the worker nodes and if it says that there are problems to start xproofd, then you need to customize environment on WNs. This could happen since with a batch SSH login in some systems you don't get your /etc/profile script called (login script) and there is no environment variables, like for normal login users. To solve this issue, users either can specify the full path to desired ROOT version on the worker nodes in the PoD.cfg or just use Section 5.2, “User's environment on workers”. The last one is very much advisable.

If needed we can restart it:

pod-ssh clean
pod-ssh submit
pod-ssh status
pod-info -n

And finally, lets shut down out PoD(PROOF) cluster:

pod-server stop
pod-ssh clean
pod-ssh status