Timeline
⭐ = Milestone
By date
| Date | Next date | |||
|---|---|---|---|---|
| 🟩 in use | MinK8s | 2026-07-24 | – | works, we can use it to simply setup minimal a testcluster Being Part of running testsetups |
| 🔵 in Erprobung | Beispielseite — alle Frontmatter-Felder | 2026-07-21 | 2026-09-01 | freier Zusatztext — erscheint als Zeile in der Status-Box Beispiel für den nächsten Schritt — dieser Text erscheint in der Admonition |
| 🚧 draft | Daily transfer toggle test | 2026-07-21 | – | Started Daily Transfer Demo Workload |
| 🚧 draft | Datenkuratierung für lokale Edge KI Workstations | 2026-07-20 | 2026-07-28 | Demand from a research group at a north bavarian univ. of apllied Science. Discussing with |
| confirmed | Current description of scope | 2026-07-20 | – | current – scope refined due to project progress |
| 🔵 Active in daily dev and test | ⭐ Production via gitops only | 2026-05-26 | 2026-08-03 | In kube3-project considered as design goal and state of the art. Use and learn in daily dev operations |
| 🟩 stable | ⭐ Meilenstein 1 — Erfüllungsbericht — M1 – Erfüllungsbericht | 2026-05-26 | – | Mai 2026 in gemeinsamen Zwischenbericht enthalten |
| 🔵 first-real-tests | Scenario 1 Syncthing 3 -Node | 2026-05-19 | – | dvelopping tests with real data |
| ⏳ paused | Kube3 Testbed | 2026-05-19 | 2026-08-01 | test if available |
| 🟢 tested | Syncthing — Overview | 2026-05-16 | – | syncthing seems to be for a long time very mature in operations. Seems to have good paths looking architecutral and technical aspects |
| 🔵 first-test | Syncthing — Encrypted Relay Node | 2026-05-16 | – | long term testing, seems to work |
| 🔵 first-test | Syncthing — Hot Spare / Secondary Node | 2026-05-16 | – | currently in testing with real data |
| 🔵 first-test | Syncthing — Config Backup | 2026-05-16 | – | included in Daily Transfer Test id_tf5-7hp1 |
| ✅ erledigt | Ask People ... | 2026-04-01 | – | interviewed people with running instances from different universities, users, it-department stuff, largescale providers |
| paused | Cluster RRZE | 2026-03-05 | – | tried transfer as failover for lrz cluster waiting |
| 🟩 stable | Cluster LRZ | 2026-02-05 | – | Testing customer workloads started |
| ✅ done | ⭐ Kickoff Workshop wih B1 2025 about architecture | 2025-11-01 | – | interviewed people with running instances from different universities, users, it-department staff, largescale providers |
By status
🔵 Active in daily dev and test
| Date | Next date | ||
|---|---|---|---|
| Production via gitops only | 2026-05-26 | 2026-08-03 | In kube3-project considered as design goal and state of the art. Use and learn in daily dev operations |
confirmed
| Date | Next date | ||
|---|---|---|---|
| Current description of scope | 2026-07-20 | – | current – scope refined due to project progress |
✅ done
| Date | Next date | ||
|---|---|---|---|
| Kickoff Workshop wih B1 2025 about architecture | 2025-11-01 | – | interviewed people with running instances from different universities, users, it-department staff, largescale providers |
🚧 draft
| Date | Next date | ||
|---|---|---|---|
| Datenkuratierung für lokale Edge KI Workstations | 2026-07-20 | 2026-07-28 | Demand from a research group at a north bavarian univ. of apllied Science. Discussing with |
| Daily transfer toggle test | 2026-07-21 | – | Started Daily Transfer Demo Workload |
✅ erledigt
| Date | Next date | ||
|---|---|---|---|
| Ask People ... | 2026-04-01 | – | interviewed people with running instances from different universities, users, it-department stuff, largescale providers |
🔵 first-real-tests
| Date | Next date | ||
|---|---|---|---|
| Scenario 1 Syncthing 3 -Node | 2026-05-19 | – | dvelopping tests with real data |
🔵 first-test
| Date | Next date | ||
|---|---|---|---|
| Syncthing — Encrypted Relay Node | 2026-05-16 | – | long term testing, seems to work |
| Syncthing — Hot Spare / Secondary Node | 2026-05-16 | – | currently in testing with real data |
| Syncthing — Config Backup | 2026-05-16 | – | included in Daily Transfer Test id_tf5-7hp1 |
🔵 in Erprobung
| Date | Next date | ||
|---|---|---|---|
| Beispielseite — alle Frontmatter-Felder | 2026-07-21 | 2026-09-01 | freier Zusatztext — erscheint als Zeile in der Status-Box Beispiel für den nächsten Schritt — dieser Text erscheint in der Admonition |
🟩 in use
| Date | Next date | ||
|---|---|---|---|
| MinK8s | 2026-07-24 | – | works, we can use it to simply setup minimal a testcluster Being Part of running testsetups |
paused
| Date | Next date | ||
|---|---|---|---|
| Cluster RRZE | 2026-03-05 | – | tried transfer as failover for lrz cluster waiting |
| Kube3 Testbed | 2026-05-19 | 2026-08-01 | test if available |
🟩 stable
| Date | Next date | ||
|---|---|---|---|
| Cluster LRZ | 2026-02-05 | – | Testing customer workloads started |
| Meilenstein 1 — Erfüllungsbericht | 2026-05-26 | – | Mai 2026 in gemeinsamen Zwischenbericht enthalten |
🟢 tested
| Date | Next date | ||
|---|---|---|---|
| Syncthing — Overview | 2026-05-16 | – | syncthing seems to be for a long time very mature in operations. Seems to have good paths looking architecutral and technical aspects |
Status legend
Values are free text EMOJI word — the emoji sets the color. Recommended:
| Status | Meaning |
|---|---|
🚧 draft |
draft, content incomplete |
🔵 first-test |
first run done, not all scenarios covered |
🟢 tested |
all planned scenarios verified |
🟩 stable |
confirmed across environments/time |
⏳ paused |
paused / waiting (incl. external) |
🟠 at risk |
might fail |
🟥 misplanned |
planning turned out wrong |
❌ discarded |
discarded / abandoned |
✅ done |
completed one-off event (e.g. workshop) |
❓ unclear |
unclear, assessment open |
Entries keep their timeline/milestone row regardless of status — even
🟠 at risk, 🟥 misplanned or ❌ discarded; only removing visibility
takes a page off the site.
tfamue · v2026-05-19 · Export created: 2026-07-28 12:15 UTC