BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-us-2026//speaker//KA7E3Q
BEGIN:VTIMEZONE
TZID:EST
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T070000Z
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T080000Z
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T030000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-devconf-us-2026-EWG9CL@pretalx.devconf.info
DTSTART;TZID=EST:20260924T152000
DTEND;TZID=EST:20260924T164000
DESCRIPTION:Device Mapper is the invisible engine under your LVM volumes\, 
 your dm-crypt containers\, your thin pools\, and your multipath setup.\n\n
 You quite likely use it every day. But do you know it?\n\nThis is the one 
 where we open the bonnet: we'll cover dmsetup power moves — the low-leve
 l commands that let you inspect\, manipulate\, and sometimes terrify your 
 storage stack in ways the higher-level tools don't expose.\n\nWe'll dive i
 nto dmstats\, the criminally underused performance measurement framework t
 hat lets you track I/O at per-region\, per-object granularity and actually
  answer the question "where is my storage bottleneck?" And we'll look at d
 mpy\, a Python automation library that lets you drive all of this programm
 atically without shelling out to dmsetup like it's 2003.\n\nThe workshop w
 ill provide practical\, useful\, hands-on exercises that users can try out
  right away using provided VM images/KS files.\n\nNo prerequisites beyond 
 basic system admin skills.
DTSTAMP:20260727T165145Z
LOCATION:107 (Capacity 20)
SUMMARY:Everything You Always Wanted to Know About Device Mapper (But Were 
 Afraid to Ask) - Neal Gompa\, bmr.southpaw
URL:https://pretalx.devconf.info/devconf-us-2026/talk/EWG9CL/
END:VEVENT
BEGIN:VEVENT
UID:pretalx-devconf-us-2026-UFLDJZ@pretalx.devconf.info
DTSTART;TZID=EST:20260925T131000
DTEND;TZID=EST:20260925T134500
DESCRIPTION:Within openSUSE\, transactional systems\, based on btrfs snapsh
 otting are offered\, through the MicroOS product.\n\nTransactional systems
  offer a middle ground between Fedora Atomics\, and their image based upda
 ting\, and read-only filesystems and Traditional Fedora\, with it's read/w
 rite filesystems\, as they can be configured to do either\, offering great
  flexibility.\n\nIn a read-only context\, transactional Fedora offers a mi
 nimal system\, and workloads are handled through podman or docker containe
 rs\, for server usage.   On the desktop\, toolbox\, distrobox\, flatpaks\,
  and potentially other application delivery mechanisms can be used\, while
  still providing the possibility of local modifications to the read-only f
 ilesystem\, for things that just make sense to be delivered via RPM.\n\nIn
  a read-write context\, Transactional systems offer Atomic updating\, offe
 ring the possibility of more reliable updating\, more stable systems over 
 time\, and the ability to "rollback" snapshots\, in case of issues. or for
  troubleshooting purposes.\n\nThis talk will discuss the basic ideas behin
 d Transactional Updates\, how they're used in openSUSE\, and what it takes
  to bring them to Fedora.
DTSTAMP:20260727T165145Z
LOCATION:Hewitt Boardroom (Capacity 35)
SUMMARY:Transactional Systems\, in the Fedora Ecosystem - Neal Gompa\, Shaw
 n W Dunn
URL:https://pretalx.devconf.info/devconf-us-2026/talk/UFLDJZ/
END:VEVENT
END:VCALENDAR