Within this repository you can find the RS Add-ons the for the Sentinel-1 mission. Each RS-Add-on contains a mission specific workflow that can be deployed on its own and adding the processing preparation as well as the scientific processor that processes the satellite data.
The following figure provides an overview about how the different RS Add-ons are chained into each other when all are deployed:
The S1 AIOP processor consumes EDRS Sessions are producing L0 Segment files from it. The S1 ASP is using these segments to produce L0 Slices from it.
The following individual processing chains are available:
For more information, please consult https://sentinels.copernicus.eu/web/sentinel/missions/sentinel-1
Please note that each of the RS Add-ons are using a generic set of microservices. The available configuration parameters are not described in the RS Add-on directly, but can be found in a common documentation that is applicable for all the RS add-ons listed above. Please consult it in order to learn what configuraton parameters are available.
In order to work properly the RS Add-ons are requiring a few dependencies that needs to be deployed before hands.
Infrastructure Layer
COPRS are using a set of technologies that are utilized by the components. E.g. Kafka, Elasticsearch and MongoDB needs to be available. This infrastructure layer needs to be installed first. For more information on its installation, please consult this repository.
RS Core Components The chain itself will not work without other RS Core components. At least the a Ingestion Chain (for retrieving inputs) and Metadata Extraction (for extracting metadata) needs to be deployed to the cluster. It is also highly recommended to deploy the DLQ as well for a proper error handling.
You can find more information and installation instructions in this repository.
In order to build all the RS add-ons contained in this repository, please execute the following script from inside the repository:
./build_all.sh <target_dir> <version>
The placeholder <target_dir>
shall point to the location where you want to put the generated RS add-ons, e.g. /tmp/rs-addons
. When the generation had been performed successfully, you can find the ZIPs containing the RS Add-ons at that location.
The placeholder <version>
defines the version that shall be added to the RS Add-ons when being generated e.g. 1.2.3
.
Be aware that this script will just ensure that the RS Add-ons are build. In order to rebuild the docker images that contains the CFI and the RS add-on servces needed to operate them, please consult this instruction.
Each RS Add-on contains a description about the services for the specific processing chain that shall be deployed into the cluster as well as a reference to the docker images that shall be used and a factory default configuration.
In order to deploy a RS Add-on the Ansible scripts from the infrastructure repository can be used. The following Add-Ons are available for deployment:
ansible-playbook deploy-rs-addon.yaml \
-i inventory/mycluster/hosts.ini \
-e rs_addon_location=https://artifactory.coprs.esa-copernicus.eu/artifactory/rs-zip-private/rs-addons/s1/RS_ADDON_S1-L0ASP_<VERSION>.zip \
-e stream_name=S1_L0ASP
ansible-playbook deploy-rs-addon.yaml \
-i inventory/mycluster/hosts.ini \
-e rs_addon_location=https://artifactory.coprs.esa-copernicus.eu/artifactory/rs-zip-private/rs-addons/s1/RS_ADDON_S1-L0AIOP_<VERSION>.zip \
-e stream_name=S1_L0AIOP
ansible-playbook deploy-rs-addon.yaml \
-i inventory/mycluster/hosts.ini \
-e rs_addon_location=https://artifactory.coprs.esa-copernicus.eu/artifactory/rs-zip-private/rs-addons/s1/RS_ADDON_S1-L1_<VERSION>.zip \
-e stream_name=S1_L1
ansible-playbook deploy-rs-addon.yaml \
-i inventory/mycluster/hosts.ini \
-e rs_addon_location=https://artifactory.coprs.esa-copernicus.eu/artifactory/rs-zip-private/rs-addons/s1/RS_ADDON_S1-L2_<VERSION>.zip \
-e stream_name=S1_L2
For further information on using the deployment script, please consult its manual.
Abbreviation | Definition |
---|---|
AIOP | All-In-One-Processor |
ASP | Assembling Slicing Processor |
COPRS | Copernicus Reference System |
CPU | Central Processing Unit |
DB | Database |
EDRS | European Data Relay Satellite |
IPF | Instrument Processing Facility |
L0 | Level-0 |
L1 | Level-1 |
L2 | Level-2 |
RAM | Random Access Memory |
RS | Reference System |
S1 | Sentinel-1 |
SCDF | Spring Cloud Dataflow |
SpEL | Sprint Expression Language |
OBS | Object Storage |
This project is funded by the EU and ESA.