-
Notifications
You must be signed in to change notification settings - Fork 5
Home
▶️ ADES Preparation (this page)- ⏬ Deploy and Configure the ADES
- ⏬ Connecting the ADES
- ⏬ Deploy an Application
- ⏬ Submit a Processing Job
The ADES is the main component to deploy.
The ADES is packaged and delivered as a Docker container.
You can either
👷♀️ Build and deploy your own ADES
or
🚢 Use the latest release version available on Docker Hub as eoepca/proc-ades:latest
In this guide, we assume using a locally packaged ADES so we will refer to proc-ades:latest as the docker image. Please substitute with your image tag.
The ADES is the WPS front-end and the workflow executor back-end but it uses a cluster to submit the workflow for the actual execution. The ADES currently supports Kubernetes API to provision virtual machine (aka pods) for the processing execution.
The present guide assumes you have a Kubernetes cluster configured and running to use properly ADES processing functionnalities. If you already have a Kubernetes cluster ready, go directly to the next section for configuring the ADES
If you do not have a kubernetes cluster, please follow the Minikube Setup Guide for installing and configuring a Minikube cluster locally.
The present guide assumes you have an S3 compatible object storage where the ADES will store the results of the workflow processing execution. If you do not have one, please follow the MinIO Quickstart Guide for installing and configuring a MinIO standalone server which is a lightweight S3 compatible object storage, optimal for testing and early development.
⏭️ Next step: Deploy and Configure the ADES