Original source: https://input.scs.community/scs-operator-hackathon#.

Yaook SCS Operator Hackathon

When: 2026-02-26
Where: Hamburg, Berliner Bogen - S-Bahn stop Berliner Tor

Goals

• understanding the technical SCS-IaaS compliance requirements
• translating these requirements into actionable items for Yaook devs & admins
• automating these AIs in the form of a Yaook Operator

Requirements/Preparations

see <2026-02-26 Briefing for developers.md> (archived)

Signup

Please sign up here: https://scs-hackathon.dsecurecloud.de/dataport/scs-hackathon/

Timetable

2026-02-25

• ca. 20:00 Get-Together at "Altes Mädchen" - limited space, only with registration! Lagerstraße 28b, 20357 Hamburg

2026-02-26

WLAN

SSID: „HBC Gast” - Passwort: ichbingastimhbc

Dev track

• 09:00 Check-In and coffee
• 09:15 Welcome & organizational information
• 09:30 Intro to Yaook Operator dev process (Stefan)
• 09:50 Warm-up: Run your own tempest operator (archived) and have it execute a minimal test suite
• 10:15 Intro to SCS-IaaS & what is needed to get Yaook there (Matthias)
• 10:45 Break-out session: Small groups make a plan how to automate specific features
• 11:30 Presentation & discussion of solutions
• 12:00 Lunch (Pizza sponsored by Dataport)
• 13:00 Break-out session: Groups write (pseudo) code/charts for their features
• 15:00 Snack break
• 16:00 Presentation of results, next steps, feedback
• 17:00 Push it to prod, end of Hackathon

Policy & politics track

Barcamp / LightningTalks / Round table / Networking corner

For all guests who are not explicitly participating in code development for the operator we are organizing a separate track in the context of the open-infra spirit.

Lightning talk offers (please add your short-talk topic) * The fairytale of digital sovereign clouds or how I stopped worrying and instead care for Interoperability - could include an AMA SCS (@fkr) *

Official representatives confirmed to be present:

• Matthias Büchse, project lead FOCIS and coordinator of SCS Special Interest Group Standardization & Certification
• Daniel Gerber, Deputy Chairman of the Board of Directors @ Open Source Business Alliance
• ALASCA members: UhuruTec, Cloud&Heat
• Yaook project reps
• Felix Kronlage-Dammers, Forum SCS-Standards / SCS Project Board

Know-how

SCS

ALASCA Tech Talk that covered SCS-IaaS compliant Yaook: https://youtu.be/fd1j0XtgY8Q?t=1377

Friedrichs findings/instructions for Yaook SCS compliance (archived)

Specific topics that result from that:

• Ensure mandatory services are running, esp. Octavia and s3
  • rough S3/Swift on Yaook instructions (archived) which lead to the idea of an Object Storage Operator
• Ensure volume backup is available
  • Open bugfix for ceph-based volumes: https://gitlab.com/yaook/operator/-/merge_requests/3145/
  • https://gitlab.com/uhurutec/stack/ustack/-/compare/devel...cinder-backup?from_project_id=60988506
• Meta: How to manage OpenStack resources in K8s (Yaook-managed (such as KeystoneEndpoint) vs https://k-orc.cloud/ vs ?)
  • Pad for brainstorming & notes (archived)
  • Ensure mandatory flavor configuration
    • special cases: SSD ephemeral storage (SCS-...s), crowded-core (SCS-_L-...) flavors are correctly scheduled
  • Ensure mandatory image availability
    • moving target
• Ensure Domain Manager role is available
• Run recurring OpenStack Powered Compute Tempest tests
  • Pad for brainstorming & notes (archived)
  • example TempestJob with all ~270 OPC test cases
  • bring your Tempest configs! We need to figure out how to generate a working one, which many ppl report to be a frustrating experience.
  • OSISM config template
  • uStack TempestJob and config example
• Run recurring SCS Compliance Check
  • Pad for brainstorming & notes (archived)
  • Friedrich previously drafted an ad-hoc yaookctl extension for that, might suffice to see how it can be done (todo: non-admin user)
    • nix shell git+https://gitlab.com/toothstone/yaookctl
    • yaookctl openstack scs-check
  • How is the result exported?
    • What about manual checks, such as the Tempest test results?
• Stretch goal: How to handle SCS-IaaS versions

Yaook

• How-to-Yaook-Operator (recently added): in Yaook docs ↦ collect feedback
• Yaook Operator template at https://gitlab.com/yaook/operator/-/commits/operator-template

Location

• Berliner Bogen
• 20-50 participants max
• room(s) can be divided

Hotels nearby:

• https://www.superbude.com/buchen/st-georg/
• https://www.ihg.com/holidayinn/hotels/de/de/hamburg/hamef/hoteldetail
• https://www.wyndhamhotels.com/de-de/super-8/hamburg-germany/super-8-hamburg-mitte/overview