EUMETSAT S3 Mount Flavour

✅ Supports instances on both the ECMWF and the EUMETSAT compute sites of the EWC.

This Ansible Playbook configures a virtual machine existing within the European Weather Cloud (EWC), enabling to access remote public EUMETSAT data buckets as if they were stored on a local disk.

Features

• Self-service access to EUMETSAT data publicly available within the EWC (no credentials required)
• Strict file permissions for mounted directories under the /mnt directory
• Boot-safe design; does not block boot on S3 outage

Prerequisites

⚠️ Only Ubuntu version 24 and 22, or RockyLinux versions 9 or 8 supported due to constrains imposed by dependencies.

• Install git (version 2.0 or higher )
• Install python (version 3.9 or higher)
• Install ansible (version 2.15 or higher)
• If you plan to configure an existing VM, then skip to the Usage section below
• If you have not yet provisioned a VM, it is required to do so. You may choose one of the following approaches:

  • A) Provision a new VM via UI:

    • Create an SSH keypair (see Creating the keys section of the EWC documentation)
    • Import the SSH public key into Morpheus (see Adding the keys in Morpheus section of the EWC documentation)
    • Provision a new VM through the web portal (see Provision a new Instance - Web section of the EWC) documentation

    OR

  • B) Provision a new VM via CLI:

    • Create an SSH keypair (see Creating the keys section of the EWC documentation)
    • Add you SSH public key to OpenStack (see Import SSH Key section of the EWC documentation).
    • Provision a new VM via the OpenStack CLI (see How to create a VM using the OpenStack CLI section of the EWC documentation)

    OR

  • C) Deploy this template, together with a new VM, via the EWCCLI

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 playbooks/eumetsat-s3-mount-flavour

1.2. (Optional) 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 -r requirements.yml

3. Specify the target host and SSH credentials

Create an inventory file to specify address/credentials that Ansible should use to reach the virtual machine you wish to configure:

# inventory.yml
---
ewcloud:
  hosts:
    eumetsat_s3_mount:
      ansible_python_interpreter: /usr/bin/python3
      ansible_host: <add the IPV4 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=accept-new

4. Configure and apply the template

4.1. 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 \
  -e '{
      "vfs_cache_mode":"writes",
      "vfs_cache_max_size":"512Mi"
    }' \
  eumetsat-s3-mount-flavour.yml

4.2. 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 eumetsat-s3-mount-flavour.yml

Inputs

💡 To learn more about the valid input values and their performance implications, checkout the rclone official documentation