lamgrow(1)

1LAMGROW(1)                       LAM COMMANDS                       LAMGROW(1)
2
3
4

NAME

6       lamgrow - Extend a LAM multicomputer.
7

SYNTAX

9       lamgrow  [-hvd]  [-cpu  <num>] [-n <nodeid>] [-no-schedule] [-ssi <key>
10              <value>] <hostname>
11

OPTIONS

13       -cpu <num>    Indicate how many CPUs are available to LAM  on  the  new
14                     node.
15
16       -d            Turn on debugging output.  This implies -v.
17
18       -h            Print useful information on this command.
19
20       -n <nodeid>   Assign this ID to the new node.
21
22       -no-schedule  Indicate  that  C  and  N expansion in mpirun and lamexec
23                     should not schedule on this node.
24
25       -ssi <key> <value>
26                     Send arguments to various SSI  modules.   See  the  "SSI"
27                     section, below.
28
29       -v            Be verbose.
30
31       <hostname>    Extend LAM with this host.
32

DESCRIPTION

34       An  existing  LAM universe, initiated by lamboot(1), can be enlarged to
35       include more nodes with lamgrow.  One new node is added for each  invo‐
36       cation.  At a minimum, the host name that will run the new node is giv‐
37       en on the command line.  If a different userid is  required  to  access
38       the  host,  it  is specified with the appropriate boot SSI options (see
39       lamssi_boot(7)).
40
41       The new node can be assigned any unused, non-negative  identifier.   If
42       no  identifier is specified, the highest node identifier in the current
43       LAM universe plus one is used.  Note  that  lamboot(1)  always  assigns
44       node identifiers consecutively from 0.
45
46       lamgrow can be run from any node in the current LAM universe.  Specifi‐
47       cally -- it cannot be run from the intended new host.  Two  invocations
48       of lamgrow should not run concurrently, and the command attempts to de‐
49       tect this situation. The name of the host specified in  lamgrow  should
50       not  be the one which is already present in the user's LAM universe and
51       the command attempts to detect this situation too.
52
53       Resource managers will be the most common user of lamgrow.  When  hosts
54       become idle and a user has expressed a desire to the manager that extra
55       cycles should be exploited, the manager could invoke lamgrow  and  then
56       launch the specified application process(es) on the new node.
57

EXAMPLES

59       lamgrow -v newhost
60           Start  LAM  on  newhost  and  add  it to the existing LAM universe.
61           Choose the next available node identifier and report  about  impor‐
62           tant steps as they are done.
63
64       lamgrow -n 30 newhost
65           Start LAM on newhost with node ID 30 and add it to the existing LAM
66           universe.  Operate silently.
67

FILES

69       laminstalldir/etc/lam-conf.lamd   default configuration  file  for  LAM
70                                         nodes,  where  "laminstalldir" is the
71                                         directory  where  LAM/MPI   was   in‐
72                                         stalled.
73

BUGS

75       It is not currently possible to specify a configuration file other than
76       lam-conf.lamd on the remote node, even though  this  is  possible  with
77       lamboot.
78