Hello LAM enthusiasts -
I'm working on an application integration between LAM-MPI, LSF, and an EDA applicaiton called "Encounter" from Cadence.
The customer for this integration insists on preventing his users from accessing computational hosts (in an effort to try and force the users into using LSF so that usage metrics pulled from LSF are accurate). This of course causes headaches with the required lamboot process. I have been able to configure a build of LAM MPI v7.1.2 which I can redirect using the environment variable LAMRSH="lsgrun -m" and a few of the "-ssi" boot parameters:
lamboot -v -ssi boot_rsh_no_n 1 -ssi boot_rsh_fast 1 -ssi boot_rsh_no_profile 1 ~/lam.schema
While perusing the documentation (the v7.1.2 installation guide specifically) I ran accross an intriguing note about "promiscuous mode". Pages 31,32 of the guide refer to building the library with the flag "--with-boot-promisc" for the cases where LAM can't know which hosts will be connecting during the boot process. I've searched the rest of the install guide, the user guide, and the archives of this mailing list to try and learn more about what "promiscuous mode" really does and if it would be helpful to me in my situation.
I built a version of the library with this switch (the config.log file included) enabled to see if I could discern a difference. I tried lambooting daemons as one user and running an mpi application as another user (in hopes promiscuity would allow the daemon to connect to my mpirun process) but that fails the same as it does without the --with-boot-promisc enabled.
So if anyone in the community has suggestions for:
1) Getting LAM booted (preferably v6.5.9 rather than 7.1.2 but we'll take what we can get) in a no-login environment
2) Getting additional information about what promiscuous mode is and does
I'd be very grateful. thanks,
chris
|
