Re: [OMPI devel] MTT Perl client

2018-09-18 Thread Ralph H Castain
Are we good to go with this changeover? If so, I’ll delete the Perl client from 
the main MTT repo.

> On Sep 14, 2018, at 10:06 AM, Jeff Squyres (jsquyres) via devel 
>  wrote:
> 
> On Sep 14, 2018, at 12:37 PM, Gilles Gouaillardet 
>  wrote:
>> 
>> IIRC mtt-relay is not only a proxy (squid can do that too).
> 
> Probably true.  IIRC, I think mtt-relay was meant to be a 
> dirt-stupid-but-focused-to-just-one-destination relay.
> 
>> 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
> 
> Yes, but then a human has to be involved, which kinda defeats at least one of 
> the goals of MTT.  Using mtt-relay allowed MTT to still function in an 
> automated fashion.
> 
> FWIW, it may not be necessary to convert mtt-relay to python (IIRC that it's 
> protocol agnostic, but like I said: it's been quite a while since I've looked 
> at that code).  It was pretty small and straightforward.  It could also just 
> stay in mtt-legacy.
> 
> -- 
> 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

Re: [OMPI devel] MTT Perl client

2018-09-14 Thread Jeff Squyres (jsquyres) via devel
On Sep 14, 2018, at 12:37 PM, Gilles Gouaillardet 
 wrote:
> 
> IIRC mtt-relay is not only a proxy (squid can do that too).

Probably true.  IIRC, I think mtt-relay was meant to be a 
dirt-stupid-but-focused-to-just-one-destination relay.

> 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

Yes, but then a human has to be involved, which kinda defeats at least one of 
the goals of MTT.  Using mtt-relay allowed MTT to still function in an 
automated fashion.

FWIW, it may not be necessary to convert mtt-relay to python (IIRC that it's 
protocol agnostic, but like I said: it's been quite a while since I've looked 
at that code).  It was pretty small and straightforward.  It could also just 
stay in mtt-legacy.

-- 
Jeff Squyres
jsquy...@cisco.com

___
devel mailing list
devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/devel

Re: [OMPI devel] MTT Perl client

2018-09-14 Thread Gilles Gouaillardet
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  wrote:
> >
> > Afraid I’m not familiar with that script - what does it do?
> >
> >
> >> On Sep 14, 2018, at 7:46 AM, Christoph Niethammer 
> 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" 
> >> Para: "Open MPI Developers" 
> >> CC: "Jeff Squyres" 
> >> 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 
> 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

Re: [OMPI devel] MTT Perl client

2018-09-14 Thread Ralph H Castain
I very much doubt that there is a Python equivalent yet.

> On Sep 14, 2018, at 9:23 AM, Jeff Squyres (jsquyres) via devel 
>  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  wrote:
>> 
>> Afraid I’m not familiar with that script - what does it do?
>> 
>> 
>>> On Sep 14, 2018, at 7:46 AM, Christoph Niethammer  
>>> 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" 
>>> Para: "Open MPI Developers" 
>>> CC: "Jeff Squyres" 
>>> 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  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

Re: [OMPI devel] MTT Perl client

2018-09-14 Thread Jeff Squyres (jsquyres) via devel
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  wrote:
> 
> Afraid I’m not familiar with that script - what does it do?
> 
> 
>> On Sep 14, 2018, at 7:46 AM, Christoph Niethammer  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" 
>> Para: "Open MPI Developers" 
>> CC: "Jeff Squyres" 
>> 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  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

Re: [OMPI devel] MTT Perl client

2018-09-14 Thread Ralph H Castain
Afraid I’m not familiar with that script - what does it do?


> On Sep 14, 2018, at 7:46 AM, Christoph Niethammer  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" 
> Para: "Open MPI Developers" 
> CC: "Jeff Squyres" 
> 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  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

Re: [OMPI devel] MTT Perl client

2018-09-14 Thread Christoph Niethammer
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" 
Para: "Open MPI Developers" 
CC: "Jeff Squyres" 
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  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

Re: [OMPI devel] MTT Perl client

2018-09-11 Thread Jeff Squyres (jsquyres) via devel
Works for me.

> On Sep 11, 2018, at 12:35 PM, Ralph H Castain  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