[Pywps-dev] process discovery

[Luí­s de Sousa]

Tom,

I am not sure I entirely understand this. What do you mean by "mapping endpoints"?


PyWPS-4 is now just a library, or an API, if you will. It is totally insulated from web server aspects. On a first glance, these scalability issues must be solved at application level.

Cheers,

Luís


-------- Original Message --------
Subject: Re: [Pywps-dev] process discovery
Local Time: 2 August 2016 10:58 PM
UTC Time: 2 August 2016 20:58
From: tomkralidis at gmail.com
To: pywps-dev at lists.osgeo.org

All: as per today's PSC meeting bringing this thread up again.

Per below, a great feature of PyWPS 3 is multi-tenancy against
a single deployment. For example, I can have a single WSGI
wrapper along with environ['PYWPS_CFG'] and
environ['PYWPS_PROCESSES'] as part of the process.

This, in combination with mapping endpoints to environment
variables allows PyWPS to scale with 1..n WPS endpoints which
use the same single WSGI wrapper. One can have 1000 PyWPS
configuration files and this approach scales accordingly. As
well, one can scale processes on a single server with the same
approach.

Unless I am mistaken (which is quite possible) it appears that
PyWPS master/moving forward to PyWPS 4 requires that a
simple wrapper explicitly define processes [1].

Is there another way to accomplish the pluggable features
of PyWPS 3 currently?


[1] https://github.com/geopython/pywps-demo/blob/master/demo.py#L60


>>
>> -------- Original Message --------
>> Subject: [Pywps-dev] process discovery
>> Local Time: March 4, 2016 1:20 AM
>> UTC Time: March 4, 2016 1:20 AM
>> From: tomkralidis at gmail.com
>> To: pywps-dev at lists.osgeo.org
>>
>> Hi all: I'm setting up http://demo.pywps.org as a demo space to
>> serve PyWPS instances as required. The goal here is a minimal
>> configuration (assuming a PyWPS install), along with some Apache
>> setup.
>>
>> In PyWPS 3, there was functionality to define a PYWPS_PROCESSES
>> environment variable. There was also the ability to define this in the
>> PyWPS
>> config. Looks like this is not available in master branch
>> anymore.
>>
>> Any plans on adding this back in the codebase? The value here is being
>> able to deploy a single WPS (in my case WSGI) wrapper which operates
>> against multiple configurations and processes setups driven by a given
>> endpoint.
>>
>> Or is there another/better way to acheive this?
>>
>> ..Tom
>> _______________________________________________
>> pywps-dev mailing list
>> pywps-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/pywps-dev
>>
>>
>
_______________________________________________
pywps-dev mailing list
pywps-dev at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pywps-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pywps-dev/attachments/20160803/391b70c7/attachment.html>