[Pywps-dev] Dynamic IPs for polling and results requests.

[Matthieu Melcot]

Hi Luis,

Thanks for this answer.

It is indeed not easy to keep trace of the ports/IP in our architecture 
since the cluster and the up and down of the WPS Servers is quite 
dynamic (managed by Mesos) and undeterministic.

I wonder if PyWPS 4 would provide a better support for that kind of 
questions...

Another way was to 'hook' at the WSGI level, in order to catch the 
calling messages, and update the wpsserver.conf with a 'sed' accordingly...
But I didn't succeed to get this information in the messages coming into 
the WSGI application...

Regards,

Matthieu



On 10/17/2016 12:04 PM, Luí­s de Sousa wrote:
> Hi Matthieu,
>
> Unfortunately, this is not possible with the configuration files. It 
> is possible to tweak the PyWPS code to behave in that way, but this 
> might not be the simplest way.
>
> My advice is to give a name to that server and keep the entry up to 
> date in your DNS. That is likely the simplest way of running a PyWPS 
> server with a dynamic IP.
>
> Regards,
>
> Luís
>
>
>
>> -------- Original Message --------
>> Subject: [Pywps-dev] Dynamic IPs for polling and results requests.
>> Local Time: 17 October 2016 11:22 AM
>> UTC Time: 17 October 2016 09:22
>> From: matthieu.melcot at spaceapplications.com
>> To: pywps-dev at lists.osgeo.org
>>
>> Hello,
>>
>> I'm using PyWPS 3.2.4 that I containerized into Docker Containers to run
>> into Mesos Marathon.
>>
>> The external IP's and ports of my WPS Servers are therefore dynamic for
>> being assigned by the Marathon framework.
>>
>> I am able to send a GetCapabilities or Execute requests to these
>> distributed WPS Servers in the Cluster since I know the 'public' IPs and
>> ports. However the XML documents sent back to the client by the PyWPS
>> servers contain 'polling' and 'results' IPs refering to the values set
>> in 'pywps.cfg' (and not the IP and port used by the client to
>> communicate with the server).
>>
>> For example:
>> [wps]
>>
>> ...
>> serveraddress=http://172.16.10.40
>> ...
>>
>> [wps]
>> ...
>> serveraddress=http://172.16.10.40/wps/wpsoutputs/
>> ...
>>
>> Thus, the problem arise once it gets to poll for the end of the 
>> execution.
>>
>> How can I configure PyWPS to force it to provides polling and results
>> URLs on the same public URLs that the client request?
>>
>> Matthieu
>> _______________________________________________
>> pywps-dev mailing list
>> pywps-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/pywps-dev
>

-- 
Matthieu Melcot
Software Engineer

Space Applications Services NV/SA
Leuvensesteenweg 325, 1932 Zaventem, Belgium
Direct: +32-(0)2-416.05.35
Main: +32-(0)2-721.54.84 Fax: +32-(0)2-721.54.44
www.spaceapplications.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pywps-dev/attachments/20161017/d0edf71e/attachment.html>