Hello Eric,
if you would like to use simfactory's --remote commands then you can add the first host you have to log in to as a "trampoline" machine in the ini file. Basically you need to have the first host configured as a machine for simfactory (it does not have to be fully functional, just needs to be enough so that you can log into it using "sim login") somewhat similar to how the machine "mars" (in mars.ini) is used by the compute.ini .
Yours, Roland
Hello Eric.
If you have a file named ~/.hostname, Simfactory will use that and it will be the same every time. I use that when running in Docker images, etc.
--Steve
On 02/08/2018 02:13 AM, Frank Loeffler wrote:
On Wed, Feb 07, 2018 at 09:29:16PM -0600, Eric West wrote:
For a bit more background: MSI uses a two step login process. First >> you ssh into a login machine. Then you ssh from there into one of the >> clusters. The machine I eventually reach is named mesabi, and the >> login hosts are named ln000[1-6].
Hi Eric
When taking a look at https://www.msi.umn.edu/content/connecting-hpc-resources
it seems like the login nodes are called 'loginXX' (with X being > digits), and from there you ssh into 'mesabi', but end up on nodes > with hostnames 'lnXXXX' (with X digits again). This suggests a common > file system, in which case you should be able to use a regular > expression like ^ln[0-9]{4}$ in 'aliaspattern' (depending on what > 'hostname' actually returns on those head nodes; you might have to > extend for the fully qualified name).
(Or even more restrictive ^ln000[1-6]$ if you like.)
Frank
Users mailing list Users@einsteintoolkit.org http://lists.einsteintoolkit.org/mailman/listinfo/users