sbanszky/EU-startup
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Micro–DC/training.toon

Browse Source
This commit is contained in:
sbanszky
2025-12-05 12:14:50 +00:00
parent 148525e807
commit 6a5151418d
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
Micro–DC/training.toon
View File

@@ -50,7 +50,7 @@ scenario_prompt:
description: > description: >
A structured narrative (like a guided lab + playbook) that walks a A structured narrative (like a guided lab + playbook) that walks a
team from powered-off hardware to a running, GitOps-managed platform team from powered-off hardware to a running, GitOps-managed platform
in **7–10 stages**, mapping to the deployment_runbook phases. Each in **7-10 stages**, mapping to the deployment_runbook phases. Each
stage should include learning objectives, inputs, concrete actions stage should include learning objectives, inputs, concrete actions
(as Git commits / pipeline runs), and observable outcomes. (as Git commits / pipeline runs), and observable outcomes.
- id: "D2" - id: "D2"
@@ -68,14 +68,14 @@ scenario_prompt:
- id: "D4" - id: "D4"
name: "Sovereignty & Compliance Labs" name: "Sovereignty & Compliance Labs"
description: > description: >
2–3 hands-on micro-labs embedded in the scenario focusing on data 2-3 hands-on micro-labs embedded in the scenario focusing on data
residency, classification, and admin-access controls (e.g. fixing a residency, classification, and admin-access controls (e.g. fixing a
non-compliant backup policy, tightening access to critical sovereign non-compliant backup policy, tightening access to critical sovereign
namespaces). namespaces).
- id: "D5" - id: "D5"
name: "Observability & SLO Labs" name: "Observability & SLO Labs"
description: > description: >
1–2 exercises where trainees define SLOs (e.g. control-plane 1-2 exercises where trainees define SLOs (e.g. control-plane
availability, GPU job wait time), wire telemetry into dashboards, availability, GPU job wait time), wire telemetry into dashboards,
and respond to a simulated incident or drift event. and respond to a simulated incident or drift event.
- id: "D6" - id: "D6"
@@ -90,7 +90,7 @@ scenario_prompt:
required_elements: required_elements:
- "Short story of the first site going live (choose one: EU-PAR-FR01 or EU-FRA-DE01)." - "Short story of the first site going live (choose one: EU-PAR-FR01 or EU-FRA-DE01)."
- "Constraints: regulatory regime, scale assumptions, target use cases." - "Constraints: regulatory regime, scale assumptions, target use cases."
- "Key learning outcomes for the training cohort (3–7 bullets)." - "Key learning outcomes for the training cohort (3-7 bullets)."
stages: stages:
mapping_to_runbook_phases: mapping_to_runbook_phases:
- from_phase: 0 - from_phase: 0
@@ -125,7 +125,7 @@ scenario_prompt:
- "Bakes in sovereignty, GDPR, and sustainability rather than treating them as afterthoughts." - "Bakes in sovereignty, GDPR, and sustainability rather than treating them as afterthoughts."
- "Provides at least 3 concrete examples of policies preventing bad changes." - "Provides at least 3 concrete examples of policies preventing bad changes."
- "Provides at least 2 concrete examples of SLOs and corresponding telemetry signals." - "Provides at least 2 concrete examples of SLOs and corresponding telemetry signals."
- "Addresses limitations and risks (LR1–LR4) with explicit training hooks." - "Addresses limitations and risks (LR1-LR4) with explicit training hooks."
reference_blueprint_template: reference_blueprint_template:
description: > description: >