For those doing AI/ML on the European Weather Cloud, we have published a number of templates to help you set up the necessary software stacks to run your favourite workloads. You may apply those onto an existing instance, and combine them as needed.  This is part of the EWC Automation templates.

The stacks currently part of this collection are:

...

You can also install those directly with Ansible, for example as part of your existing Infrastructure as Code (IaC) or CI/CD pipelines.

You may run Ansible on the same instance or anywhere else from where you can connect to your instance via SSH, such as another instance in the same private network, or from your own computer if your instance can be reached over SSH. We will refer to this as your seed platform. You will need at least git and python available to follow these steps.

1. On your seed platform, clone the https://github.com/ewcloud/ewc-ecmwf-ai-stacks:
   

   No Format
   git clone https://github.com/ewcloud/ewc-ecmwf-ai-stacks.git cd ewc-ecmwf-ai-stacks

2. If you don't have Ansible installed, you may install it with pip:
   

   No Format
   pip install --user -r requirements.txt

   or if you prefer to do it in a virtual environment:
   

   No Format
   python3 -m venv ansible-venv source ansible-venv/bin/activate pip install -r requirements.txt

3. Install the necessary Ansible roles that are going to be used by the playbooks:
   

   No Format
   ansible-galaxy role install -r requirements.yml roles/

4. If you don't have it already, define your Ansible inventory. The simplest approach would be to create a file called inventory, on the same directory where the plabooks are, containing the fully qualified domain name (FQDN) or IP address used to connect to the instance from your seed platform. If running on the same instance, you may use localhost.
5. Apply the desired playbook with ansible-playbook:
   

   No Format
   ansible-playbook -i inventory playbookname.yml

   You may pass additional options to ansible-playbook, such as:
   • -v for verbose output
   • -K for asking sudo password, if your user does not have password-less sudo privileges on the target instance.
   • -u yourremoteuser if Ansible needs to use a specific user account to connect to the target instance.
   • -e var=value for add-hoc customisation of playbook variables to customise your installation.

...

...

Advanced: How to use your custom Ansible playbook using provided Ansible roles

...