A deployment wrapper script has been prepared for a ‘processing’ deployment - that is focused on the ADES and the deployment/execution of processing jobs.
deploy/processing/processing achieves this by appropriate configuration of the environment variables, before launching the eoepca.sh deployment script. The deployment configuration is captured in the file
The processing deployment applies the following configuration:
- Assumes a private deployment - i.e. no external-facing IP/ingress, and hence no TLS
To configure an external-facing deployment with TLS protection, then see section Public Deployment
- No TLS for service ingress endpoints
- Services deployed:
- ADES for processing
- Minio for S3 object storage
- ADES stage-out to Minio
- Open ingress are enabled for unauthenticated access to ADES service
- Other eoepca services not deployed
Deployment is initiated by invoking the script…
The ADES service is accessed at the endpoint
ades-open.<domain> - e.g.
Example Requests -
deploy/samples/requests/processing/snuggs.http has been prepared with sample requests for OGC API Processes operations:
- List Processes
- Deploy Process
- Get Process Details
- Execute Process
- Get Job Status
- Get Job Results
NOTE that the first requests in the file provide optional calls to obtain a user ID token (
authenticate) - to be used in the case that protected (not ‘open’) endpoints are deployed.
snuggs.http describes the HTTP requests for the ADES OGC API Processes endpoint, and is designed for use with the Visual Studio Code (vscode) extension REST Client. Install in vscode with
ext install humao.rest-client.
@domain can be configured at the top of the file.
In the default configuration, the processing results are pushed to the Minio S3 object storage - at the endpoint
minio-console.<domain> - e.g.
http://minio-console.192.168.49.2.nip.io - with default credentials
The outputs are pushed as a static STAC catalogue to a path that includes the unique job ID.