EUMETSAT Data Tailor Flavour

This Ansible Playbook configures an existing virtual machine running within the European Weather Cloud (EWC), to equip it with the Data Tailor Standalone and EUMETSAT Data Access Client (EUMDAC).

Functionality

💡 Unlike the Data Tailor Web Services (DTWS), which can be used with EUMDAC or via https://tailor.eumetsat.int, the standalone version is generally faster and does not have limitations such as maximum concurrent jobs or workspace size.

The Data Tailor is a product customization toolbox designed to:

• Enable users to tailor satellite data to their specific needs.
• Offers the ability to subset and aggregate data products across space and time, filter layers, generate quick looks, reproject data onto new coordinate reference systems, and reformat data into widely used Geographic Information System (GIS) formats such as netCDF and GeoTIFF, as well as image formats like JPEG and PNG.
• Customize data from various satellite collections, including METOP, MFG ,MSG, MTG (Meteosat Third Generation) and Sentinel-3.

For more information on capabilities of the Data Tailor, please refer to Data Tailor Standalone Guide on User Portal and for more information about the available products and customizations inside the Data Tailor, please go to Products and Customizations Available in the Data Tailor page.

Prerequisites

💡 This Item is supported by the EWCCLI, and can be deployed, together with a compatible VM, via it. Checkout the EWC User Stories: I want to use the ewccli documentation pages to learn how.

• Install git (version 2.0 or higher )

• Install python (version 3.9 or higher)

• Install ansible (version 2.15 or higher)

• Verify the ssh-https OpenStack Security Group exists in your EWC tenancy

  💡 You may create Security Groups via this EWC Community Hub Item if pre-required ones are missing.

• If you plan to configure an existing VM, ensure it meets the minium requirements before moving on to the Usage section below:

  • VM Image: Ubuntu 24 or 22
  • VM Plan: 4 CPU cores, 16GB RAM, 80GB Disk
  • Network: Private
  • Security Groups: ssh-https
  • Floating IP: Optional (not recommended from a security standpoint)

  Otherwise, provision a new VM with above specifications before continuing (see EWC Getting Started: Provision a VM for details).

Usage

1. Clone the repository

git clone https://github.com/ewcloud/ewc-ansible-playbook-flavours-and-provisioning.git

1.1. Change to the specific Item's subdirectory

cd ewc-ansible-playbook-flavours-and-provisioning/playbooks/eumetsat-data-tailor-flavour

1.2. Checkout an specific Item's version

⚠️ Make sure to replace x.y.z in the command below, with your version of preference.

git checkout x.y.z

2. Download Ansible dependencies

💡 By default, Ansible Roles are installed under the ~/.ansible/roles directory within your working environment.

Download the correct version of the Ansible dependencies, if you haven't done so already:

ansible-galaxy role install --force -r requirements.yml

3. Specify the target host and SSH credentials

Create an inventory file, to specify address/credentials that your local working environment should use to connect to the target VM.

Copy into the file one of the two snippets below, and replace the placeholders (i.e. values enclosed in < > characters):

• Connecting form within the EWC tenancy's network

  # inventory.yml
  ---
  ewcloud:
    hosts:
      target:
        ansible_python_interpreter: auto
        ansible_host: <add the IP address of the target host>
        ansible_ssh_private_key_file: <add the path to local SSH private key file>
        ansible_user: <add the default user according to your chosen VM image>
        ansible_ssh_common_args: -o StrictHostKeyChecking=no
  

OR

• Connecting from outside the EWC tenancy's network

  ⚠️ This requires an SSH Bastion to be already provisioned within your EWC tenancy.

  # inventory.yml
  ---
  ewcloud:
    hosts:
      target:
        ansible_host: <add the IP address of the target host>
        ansible_ssh_user: <add the default user according to your chosen VM image>
        ansible_ssh_private_key_file: <add the path to local SSH private key file>
        ansible_python_interpreter: auto
  
  all:
    vars:
      ansible_ssh_common_args: >-
        -o StrictHostKeyChecking=no
        -o UserKnownHostsFile=/dev/null
        -o ProxyCommand="ssh
                        -o StrictHostKeyChecking=no
                        -o UserKnownHostsFile=/dev/null
                        -o BatchMode=yes
                        -W %h:%p
                        -i <add the path to local SSH private key file>
                        cloud-user@<add the IP address of the ssh bastion>"
  
  

4. Configure and apply the template

• Interactive Mode

  By running the following command, you can trigger an interactive session that prompts you for the necessary user inputs, and then applies changes to your target EWC environment:

  ansible-playbook -i inventory.yml eumetsat-data-tailor-flavour.yml
  

OR

• Non-Interactive Mode

  💡 To learn more about defining variables at runtime, checkout the official Ansible documentation.

  You can also run in non-interactive mode by passing the --extra-vars or -e flag, followed by a map of key-value pairs; one for each and every available input (see inputs section below). For example:

  ansible-playbook \
    -i inventory.yml \
    -e '{
        "data_tailor_env_wipe": "no",
        "data_tailor_env_name": "epct-desktop",
        "conda_installer": "https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-Linux-x86_64.sh",
        "conda_update_base": "false",
        "conda_prefix": "/opt/conda",
        "conda_user": "root"
      }' \
    eumetsat-data-tailor-flavour.yml
  

Inputs

Dependencies

💡 Upon execution, a SBOM (SPDX format) is auto-generated and stored in the VM's file system root directory (see /sbom.json).

Operation

Checkout the following how-to guides to learn about management of the Item after initial setup:

• How to initialize the environment