A Brief introduction into openSUSE MicroOS Desktop, openSUSE's immutable Desktop operating system, and announcing the move of openSUSE MicroOS Desktop (GNOME) from [ALPHA] to [BETA] quality.
[email protected] @sysrich About Myself openSUSE contributor since it began SUSE employee since 2013 Passionate advocate of rolling releases Former Customer (Systems Manager), QA Engineer, openSUSE Board Member & openSUSE Chairperson Currently Linux Distribution Engineer in Future Technology Team focusing on two rolling distributions openSUSE MicroOS – Single Purpose Self Administering OS openSUSE Kubic – MicroOS for Kubernetes & Containers Photographer in spare time
enough Traditional Linux is like a Swiss Army Knife Lots of Services & Features - with increased chances of incompatibilities between services - and increased risk of complex failures
both predictable & immutable. It cannot be altered during runtime. MicroOS is reliable with automated updates and automated recovery from faulty updates. MicroOS is small with only what is needed to run it’s “one job”. Applications/Services are expected to be Containerised or Sandboxed.
both predictable & immutable. It cannot be altered during runtime. SLE Micro is reliable with automated updates and automated recovery from faulty updates. SLE Micro is small with only what is needed to run it’s “one job”. Applications/Services are expected to be Containerised.
a rolling release based on openSUSE Tumbleweed. MicroOS is wholly built, developed, and tested as part of the Tumbleweed release process. Any test failure detected before the release of either Tumbleweed & MicroOS can prevent the release of both distributions. SLE Micro is a regular release based on SUSE Linux Enterprise.
a system should be applied reliably, reproducibly, and reversibly. Transactional Updates are: - Atomic - Either fully applied, or not at all - Applied without impacting the running system
a failure/unwanted behavioural change Immutable: Nothing has changed on disk Rollback is done by booting an old snapshot This can be done as often as wanted
during boot phase Error with new snapshot? Rollback to last known working snapshot Error with already successful booted snapshot? Try reboot, else shutdown services, inform admin Needs access to harddisk
raises some challenges: - Reboot needed to install additional tools - Situation after reboot is different then before Toolbox: - Launches small, privileged container - Root filesystem available below /media/root - zypper to install the necessary tools - Persistent between usages
is MicroOS where the ”one job” is running as a Desktop. MicroOS Desktop provides only a minimal base system with a Desktop Environment and Basic Configuration Tools ONLY. All Applications, Browsers, etc are provided by FlatPaks from FlatHub.
for? It is not for everyone. Your Tumbleweed & Leap Desktops are Safe :) It should be perfect for lazy developers, who no longer want to mess around with their desktop and just ”get stuff done”, especially if they develop around containers. It should also appeal to the same audience now more used to an iOS, Chromebook or Android-like experience where the OS is static, automated & reliable and the Apps are the main thing the user cares about.
should be reliable, predictable & immutable, just like regular MicroOS. MicroOS Desktop should be less customisable than regular openSUSE Tumbleweed/Leap. MicroOS Desktop should be small, but not at the expense of functionality. Printing, Gaming, Media Production and much more should all work. MicroOS Desktop should just work “out of the box”.
20 MicroOS Desktop should be reliable, predictable & immutable, just like regular MicroOS. MicroOS Desktop should be less customisable than regular openSUSE Tumbleweed/Leap. MicroOS Desktop should be small, but not at the expense of functionality. Printing, Gaming, MultiMedia are all valid use cases. MicroOS Desktop should just work “out of the box”.
custom MicroOS config for GNOME Contains ‘mod-firstboot’ which automatically configures flathub per user and installs default applications from flathub PackageKit with txupd and libdnf Now uses libdnf and transactional-updates for updating system RPMs via GNOME Software Uses GNOME Software for installing flatpaks from flathub SELinux by default, tuned btrfs Deploys with SELinux by Default BTRFS now has CoW enabled for /home
20 MicroOS Desktop should be reliable, predictable & immutable, just like regular MicroOS. MicroOS Desktop should be less customisable than regular openSUSE Tumbleweed/Leap. MicroOS Desktop should be small, but not at the expense of functionality. Printing, Gaming, MultiMedia are all valid use cases. MicroOS Desktop should just work “out of the box”.
sysrich
tomoki10
neilsaw
shoheimitani
yoshifumi_ishikura
up1
philipschwarz
maroon1st
mototakatsu
javiergs
xuwei_k
envek
ssssota
addyosmani
jlugia
danielanewman
gr2m
jacobian
aarron
keathley
marcelosomers
smashingmag
kevinliebholz
garrettdimon
denniskardys
![Copyright © SUSE 2021 19 Now in [BETA] Available in](https://files.speakerdeck.com/presentations/8ec89e12aac74e3e80b825c8c20e701f/slide_18.jpg){kind=link}
![Copyright © SUSE 2021 21 Join the Fun [email protected] -](https://files.speakerdeck.com/presentations/8ec89e12aac74e3e80b825c8c20e701f/slide_20.jpg){kind=link}
