BEGIN:VCALENDAR
X-LOTUS-CHARSET:UTF-8
VERSION:2.0
PRODID:ZMS-Berlin
BEGIN:VTIMEZONE
TZID:Europe/Berlin
X-LIC-LOCATION:Europe/Berlin
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19700329T020000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19701025T030000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
END:VTIMEZONE
METHOD:REQUEST
BEGIN:VEVENT
UID:ics.terminsysteme.de1766051603
DTSTAMP:20251218T105323
CLASS:PUBLIC
DTSTART;TZID=Europe/Berlin:20260130T110000
DTEND;TZID=Europe/Berlin:20260130T120000
LOCATION:https://bbb.cloudandheat.com/rooms/a6x-ubv-eje-uuv/join
SUMMARY:ALASCA Tech-Talk #32: How to build an SCS-compliant cloud environment for the benefit of the ALASCA community
DESCRIPTION:In January, we are happy to invite you to the following ALASCA Tech-Talk: \n\nHow to build an SCS-compliant cloud environment for the benefit of the ALASCA community\n\nMatthias Büchse (ALASCA FOCIS)\n\nWith ALASCA FOCIS, we want to publicly establish the viability of open solutions through case studies we do in cooperation with relevant parties. Case in point: ALASCA founding member C&H recently set up a new SCS-compliant OpenStack cluster, donating big parts to the ALASCA community to work on the ALASCA stack, to host Gitlab runners, and other things.\n\nWe accompanied this installation, providing advice regarding SCS compliance, and we observed the process in order to prepare comprehensive documentation.\n\nIn this talk, I will show how this installation was done (in particular with respect to SCS compliance), how the ALASCA stack enables this installation, what services are already available, and how to apply for resources on this environment.\n\n---\ngenerated by https://www.terminsysteme.de/ics
END:VEVENT
END:VCALENDAR