+1. That sounds like a great addition.

Python on the other end is a good match as Python is often used as a 
glue language for driving scientific code.

Could this module be used to implement a scientific workflow system like 
Kepler or Taverna?

One thing that many systems appear to lack is distributed authorisation 
(and accounting). Would a GeoServer client be able to specify their own, 
for example, oauth2 provider, to permit access to an arbitrary compute 
resource? Or do you anticipate that all compute resources are configured 
by the GeoServer owner?

Kind regards,
Ben.

On 16/02/16 23:07, Andrea Aime wrote:
> Hi,
> on behalf of Alessio I would like to propose a new community module that
> allows
> GeoServer WPS to discover, run and monitor processes running on one or more
> remote machines.
>
> This setup is popular in scenarios where one has long lived and resource
> hungry processes that
> require a dedicated machine to run (e.g., some large satellite imagery
> processes,
> simulation or weather models, that can take hours and chew a lot of of
> memory per run),
> as well as the "dockerization" trend in which algorithm providers are
> simply shipping a
> docker container fully setup with the executable to be run and its specific
> environment
> (in scientific apps that can be _very_ specific), which regardless of the
> physical setup, effectively
> makes it run on a separate node.
>
> The module is easier to explain with a picture:
>
> [image: Inline image 1]
>
> Basically on the GeoServer side we have a custom process factory that
> discovers and exposes
> processes, on the other end we have some support to describe and execute
> the processes, and
> in the middle we have a XMPP server acting as the network protocol, plus
> eventual file system sharing
> for large inputs/outputs.
>
> XMPP was chosen as a suitable cross language communication mechanism,
> indeed, while the
> GeoServer module is pure java (pull request in preparation here:
> https://github.com/geosolutions-it/geoserver/tree/wps-remote),
> while the reference implementation of the other end is python based instead:
> https://github.com/geosolutions-it/wps-remote-backend-XMPP
>
> We'd like to contribute the GeoServer module, along with docs, as a
> community one, and if possible
> add the reference python implementation as a new repository in the
> https://github.com/geoserver/ organization,
> to stress its open status and encourage more people to take part.
>
> As this is a community module there is no feature freeze rush, but I guess
> it would be nice to
> have it in anyways in order to add it to the beta announcement
>
> Feedback welcomed
>
> Cheers
> Andrea
>
>
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
>
>
>
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>

-- 
Ben Caradoc-Davies <[email protected]>
Director
Transient Software Limited <http://transient.nz/>
New Zealand

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to