BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-cz-2026//talk//9ZXF3X
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-devconf-cz-2026-9ZXF3X@pretalx.devconf.info
DTSTART;TZID=CET:20260619T110000
DTEND;TZID=CET:20260619T113500
DESCRIPTION:Traditionally\, managing a fleet of machines meant being at the
  mercy of whatever your package provider published. Foreman and Katello ch
 anged that by giving you a way to curate\, filter\, and control exactly wh
 at and when hits your servers. Now\, image-mode takes that one step furthe
 r: instead of managing a shifting list of packages on a live system\, you
 ’re building\, versioning\, and deploying the entire OS as a single\, im
 mutable unit with your application baked in.\n\nIn this session\, I’ll b
 reak down the practical differences between traditional package-mode and t
 his new image-mode approach. We’ll look at how Foreman and Katello let y
 ou leverage the best of both worlds from image building to management of r
 unning systems.
DTSTAMP:20260430T125109Z
LOCATION:E112 (capacity 156)
SUMMARY:Foreman\, Katello and bootable containers - Adam Růžička
URL:https://pretalx.devconf.info/devconf-cz-2026/talk/9ZXF3X/
END:VEVENT
END:VCALENDAR