IIRC mtt-relay is not only a proxy (squid can do that too). mtt results can be manually copied from a cluster behind a firewall, and then mtt-relay can “upload” these results to mtt.open-MPI.org
My 0.02US$ Gilles On Saturday, September 15, 2018, Jeff Squyres (jsquyres) via devel < devel@lists.open-mpi.org> wrote: > It's for environments where MTT is run where it can't reach the greater > internet (or, at least, it can't POST to the greater internet). You run > the mtt-relay on a machine that is reachable by your machines running MTT, > and it works as a relay to mtt.open-mpi.org so that you can submit your > MTT results. > > It might actually be fairly protocol agnostic, IIRC (been a while since > I've looked at that code). > > > > > On Sep 14, 2018, at 11:23 AM, Ralph H Castain <r...@open-mpi.org> wrote: > > > > Afraid I’m not familiar with that script - what does it do? > > > > > >> On Sep 14, 2018, at 7:46 AM, Christoph Niethammer <nietham...@hlrs.de> > wrote: > >> > >> Works for the installation at HLRS. > >> > >> Short note/question: I am using the mtt-relay script. This is written > in perl. Is there a python based replacement? > >> > >> Best > >> Christoph Niethammer > >> > >> ----- Mensaje original ----- > >> De: "Open MPI Developers" <devel@lists.open-mpi.org> > >> Para: "Open MPI Developers" <devel@lists.open-mpi.org> > >> CC: "Jeff Squyres" <jsquy...@cisco.com> > >> Enviados: Martes, 11 de Septiembre 2018 20:37:40 > >> Asunto: Re: [OMPI devel] MTT Perl client > >> > >> Works for me. > >> > >>> On Sep 11, 2018, at 12:35 PM, Ralph H Castain <r...@open-mpi.org> > wrote: > >>> > >>> Hi folks > >>> > >>> Per today’s telecon, I have moved the Perl MTT client into its own > repository: https://github.com/open-mpi/mtt-legacy. All the Python client > code has been removed from that repo. > >>> > >>> The original MTT repo remains at https://github.com/open-mpi/mtt. I > have a PR to remove all the Perl client code and associated libs/modules > from that repo. We won’t commit it until people have had a chance to switch > to the mtt-legacy repo and verify that things still work for them. > >>> > >>> Please let us know if mtt-legacy is okay or has a problem. > >>> > >>> Thanks > >>> Ralph > >>> > >>> _______________________________________________ > >>> devel mailing list > >>> devel@lists.open-mpi.org > >>> https://lists.open-mpi.org/mailman/listinfo/devel > >> > >> > >> -- > >> Jeff Squyres > >> jsquy...@cisco.com > >> > >> _______________________________________________ > >> devel mailing list > >> devel@lists.open-mpi.org > >> https://lists.open-mpi.org/mailman/listinfo/devel > >> _______________________________________________ > >> devel mailing list > >> devel@lists.open-mpi.org > >> https://lists.open-mpi.org/mailman/listinfo/devel > > > > _______________________________________________ > > devel mailing list > > devel@lists.open-mpi.org > > https://lists.open-mpi.org/mailman/listinfo/devel > > > -- > Jeff Squyres > jsquy...@cisco.com > > _______________________________________________ > devel mailing list > devel@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/devel
_______________________________________________ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
