[execnet-dev] Multihopping execnet connections

[Ronny Pfannschmidt]

Recent execnet gatways can be bootstraped via another gateway

so
>>> group = execnet.Group()
>>> a = group.makegateway('ssh=a//id=a')
>>> b = group.makegateway('ssh=b//via=a')

should do the trick 

On Wednesday, October 22, 2014 11:29:28 PM CEST, Prasanna Mulgaonkar wrote:
> I am trying to use execnet for a monitoring application where 
> one server (say A) needs to reach into another (say C) and 
> execute some python code.  This works just fine using execnet, 
> and the fact that it is a zero footprint mechanism means that 
> (other than python) C does not have to have anything else 
> preconfigured on it.
>
> Occasionally I see situations where there is no direct 
> connectivity from A to C, and one needs to hop through some 
> gateway device (say B), where B simply serves as a relay for any 
> channels coming from A or C. To do this, I send over a python 
> module from A to B which then opens another gateway to C.
>
> However, this solution requires that B have execnet installed.
>
> Is there any way that execnet can bootstrap itself onto the 
> intermediate machine B? I can open SSH to B, I have root on B if 
> I need to (which means I can install execnet if it does not 
> exist). But the ideal solution would be to send execnet itself 
> as a module, or at least the key parts of it over the channel 
> from A to B.
>
> Pointers much appreciated.
>
> --prasanna