I was thinking about this, and I believe it would require a change to the mtt
client to avoid it. I’m working on a new Python-based version of it, and I’ll
make sure to deal with this there.
In the interim, I’ll have to defer to some old, gray Perl guru to update the
current client
> On Oct 2
Howard,
that has already been raised in
http://www.open-mpi.org/community/lists/mtt-users/2014/10/0820.php
at the end, Christoph claimed he could achieve that with mtt-relay
(but provided no detail on how ...)
You might want to check the full thread and/or ask Christoph directly
Ralph,
IIRC
If you are able to connect (assuming ssh) to the nodes that will execute the
tests, why can’t you simply use an ssh tunnel to contact the IU server ?
George.
> On Oct 23, 2015, at 00:08 , Ralph Castain wrote:
>
> I was thinking about this, and I believe it would require a change to the mtt
I see the issue in the current code:
1. The current code assumes that if you use the MTT database reporter, you can
reach the database. One of the first things it does is ping the server to
ensure that it's reachable. The rationale is that you don't want MTT to run
for a long time and then fi
George,
Then you cannot use https otherwise certificate check will fail,
Note if you have a proxy, you can tunnel to the proxy and that should be fine.
The main drawback is the ssh connection must be active when contacting IU, and
if a batch manager is used, no one knows when that will be needed.
