---
# System prepended metadata

title: DIEM notes

---

# DIEM notes

## Current planning

Division of labor:

- ST would handle OOD & process management
- NL would handle Kubernetes
- PHL and HF would handle the OOD apps
- TP is willing to navigate Aalto

## Risks

- It's just too much
- **Technology just doesn't work**
- We get stuck in G3 & G4
- We get too much other work
- We can't get anyone to host the scaled up version

## Fallback plans

- Azure for hosting
- Stand-alone n8n for students as a pilot, if we can't get a proper app system

## Current timeline

- Jukka has a surgery beginning of March
- till early/Mid-February: investigation of possible blockers/ways to go on
- early/mid-February: presenting plans for individual steps and decide on how to go on
- End of February: deciding on things, building the platform
- Mid-March: system is running and we can test the MVP

## Required features

- Orchestrating service (n8n or similar)
- Vector database (qdrant - persistant) + reset functionality 
- Links to Aalto LLMs (possibly set up rom the platform)
- Persistent storage (and upload functionality)

## Current steps

- Get everyone a sa-account
- Get VMs from ITS
    - diem-ai.org.aalto.fi (for OOD)
    - diem-k8s-controller.org.aalto.fi
    - diem-k8s-worker.org.aalto.fi
- ST:
    - Create a version group around this
- NL:
    - Investigate Kubernetes
    - https://minikube.sigs.k8s.io/docs/
    - Have a meeting with ST, TP and Markus about k8s
    - TP Comment: 
        - Create a basic setup that can be linked to OOD (maybe quick look into OOD requirements, i.e. what rights does the OOD controller need). 
        - Inform yourself about network policies (namespace separation), but don't worry to much about implementing those
- ST:
    - Have a meeting with Ivan about OOD
    - Ask about authentication things from CS IT
- PHL & HF:
    - HF explain how OOD apps work to PHL, ask TP or ST to join if needed
        - TP comment: Important distinction between Slurm ood apps and kube ood apps 
            - kube does NOT have links to persistant storage unless explicitly generating pvcs for them
            - management of persistent volume claims
    - Investigate n8n
    - Figure out a setup where you can run docker / podman containers on your preferred dev platform (laptop / RSE VM)
    - OOD kubernetes apps docs
- TP:
    - Getting VMs 
- Everyone:
    - Fill in forms and get sa accounts for the VMs  

## Existing resources 

- [Project plan](https://docs.google.com/document/d/1BIWVg3KS7CCBG9OjwvBJHVwH8RJQs--1vrJRxhW2pE8/edit?tab=t.0#heading=h.ltz2mcigxnpg)
- [System description](https://docs.google.com/document/d/1FOJkB8QSNS4an70my_3lTvLh2WU_ufbjJ1ZkZjhsZTY/edit?tab=t.0)
- Triton Ansible setup: [ood-ansible](https://github.com/AaltoSciComp/ood-ansible/tree/master/tasks)
- CS IT kubernetes OOD configs [open-ondemand-misc-files](https://version.aalto.fi/gitlab/CS-IT/open-ondemand-misc-files)
- Possible [n8n](https://n8n.io/)
- [Jukka's MVP (minimum viable product)](https://version.aalto.fi/gitlab/jaluoma/n8n-mvp)
- [OOD kubernetes apps](https://osc.github.io/ood-documentation/latest/installation/resource-manager/kubernetes.html#open-ondemand-apps-in-a-kubernetes-cluster)

## People we can ask for help

- Ivan for OnDemand setup
- Markus from CS for Kubernetes & Kubernetes + OOD
- Sami about k8s
- TP & ST about OOD apps
- Jukka about what is needed by the apps