Video Recording of openSUSE Conference session which introduced the project

Core Project

MicroOS (and it's Kubernetes focused sister, Kubic) is an exciting distribution that takes much of the cool stuff we're doing in Tumbleweed, adds solutions to the problems of updating a running system, and is becoming the perfect base system for running containers.

But in openSUSE, running server stuff is only half the fun.

Why should servers be the only platform enjoying automatic, atomic, "auto-rollbackable" system updates?

Surely desktop users want to be lazy like server admins also?

Can the tools and approaches implemented in MicroOS help create the desktop distribution of the future?

Let's find out!

This Project will try to build, test, and introduce to the world the 'openSUSE MicroOS Desktop', a desktop focused variant of MicroOS based on Tumbleweed.

Sub Projects (Hackweek 18/19)

BPF powered Tor networking for flatpaks

A BPF program which can we attached to flatpaks (via CGROUP_BPF, "cgroup/skb" section) which will redirect all the egress traffic from the given flatpak to Tor network. Such a program should be trivial to write, but it will be a good alternative for running whole virtualized systems like Tails or Whonix.

openSUSE Flatpaks

in the similar way Fedora is doing that - flatpaks based on OCI images. Those OCI images could be build with kiwi. That approach gives us benefits from flatpak, but at the same time we avoid bundling libraries in each flatpak image, instead we reuse our packaging and good model of handling dependencies globally for all the software.

Hackweek 20

During Hackweek 20 (March 22-26 2021) I'm going to be working again on getting MicroOS Desktop polished and ready for primetime use.

For those interested in joining this Hackweek, I'd recommend watching the following videos to catch up with the Project's current status

Richard talking about MicroOS Generally and the Desktop current status at FOSDEM 2021

Dario talking about how he uses MicroOS Desktop already as his daily driver

Most of the Hackweek will be addressing the problems with the current builds and inventing solutions for the current main sticking points of getting MicroOS's config 'perfect' out of the box, such as configuring Flatpak with Flathub and installing some Flatpaks by default.

People can join the kubic@lists.opensuse.org mailing list to discuss issues asynchronously

We will also be on #microos-desktop on irc.freenode.org to talk to us via chat

And we'll also be on video chat on meet.opensuse.org/MicroOSDesktop as often as we can. Specific 'open hours' may be announced on the MicroOS Twitter Account

Hackweek 20 Results

After Hackweek 20 the GNOME variant of the MicroOS Desktop finally achieved [BETA] status, meaning its now feature complete and ready for most people to use, with the caveat of a small possibility of bugs/issues which will be fixed quickly.

More details can be found on this slide deck

Join this project Leave this project

Looking for hackers with the skills:

opensuse tumbleweed gnome flatpak kiwi obs distribution

This project is part of:

Hack Week 18 Hack Week 19 Hack Week 20 Hack Week 21

Activity

over 2 years ago: PeterMaris12 joined this project.

over 2 years ago: PeterMaris12 liked this project.

over 2 years ago: JonathanKang liked this project.

over 3 years ago: mrohde joined this project.

over 3 years ago: lpalovsky liked this project.

over 3 years ago: markgharvey liked this project.

over 3 years ago: bakano liked this project.

over 3 years ago: bakano disliked this project.

over 3 years ago: bakano liked this project.

over 3 years ago: bdekany liked this project.

over 3 years ago: jblainchristen liked this project.

over 3 years ago: hsehic joined this project.

over 3 years ago: acho liked this project.

over 3 years ago: michals liked this project.

over 3 years ago: radolin liked this project.

over 3 years ago: yfjiang liked this project.

over 3 years ago: salisburyk liked this project.

over 3 years ago: franjsco liked this project.

over 3 years ago: sydsb liked this project.

over 3 years ago: sydsb joined this project.

over 3 years ago: hbarnes joined this project.

over 3 years ago: RBrownSUSE liked this project.

over 4 years ago: aitvaras liked this project.

over 4 years ago: vinzv liked this project.

over 4 years ago: vinzv joined this project.

Comments

almost 5 years ago by mrostecki | Reply

I would like to join that project and propose two "subprojects" I would like to work on:
- A BPF program which can we attached to flatpaks (via CGROUP_BPF, "cgroup/skb" section) which will redirect all the egress traffic from the given flatpak to Tor network. Such a program should be trivial to write, but it will be a good alternative for running whole virtualized systems like Tails or Whonix.
- openSUSE flatpaks - in the similar way Fedora is doing that - flatpaks based on OCI images. Those OCI images could be build with kiwi. That approach gives us benefits from flatpak, but at the same time we avoid bundling libraries in each flatpak image, instead we reuse our packaging and good model of handling dependencies globally for all the software.
- almost 5 years ago by RBrownSUSE | Reply
  
  +1 to both to me..lets do this! :)
- almost 5 years ago by mrostecki | Reply
  
  The main job here will be catching egress packets from the given cgroup and redirecting them to localhost:9050 or to whatever port the SOCKS proxy of Tor is listening to.

almost 5 years ago by dfaggioli | Reply

I was wondering, how does one do development, in an environment like this. I mean, the classic dev cycle of a good old (say, for instance) C project where even just to build test it (perhaps with your changes), you'd need to install a bunch of libfoo-devel, libbar-devel, libfoo-bar-devel, etc., which I don't think one wants to install on the "main OS" and, e.g., have to reboot each time that building with a new dependency is necessary. Libvirt, QEMU, Xen could be examples, arbitrarily chosen just because they're the ones I deal with sort of on a daily basis, but I think there may well be others.

My wild guess would be that a "toolbox like" [1] approach could work? That is, having a simple way to spin up a container inside which one can build his project? Dependencies, one would install them inside the container manually, or we can allow for stashing a (or more) "dockerfile(s)" somewhere, that can then be fine-tuned and reused...

If this makes any sort of sense, I would like to join the project with the aim of testing such a workflow, give feedback about it and, hopefully, improve it.

I feel like adding that I have very few experience with MicroOS/Kubic, as well as with containers in general. And although learning new things is indeed the purpose of Hackweek, I'm not sure how far I'll be able to get.

Anyway, let me know what you think. :-)
- almost 5 years ago by fcrozat | Reply
  
  you mean https://kubic.opensuse.org/blog/2019-10-22-toolbox/ ? ;)
  - almost 5 years ago by dfaggioli | Reply
    
    I definitely do mean that! I actually meant to put that very link in my comment... see the "[1]" I have there?
    
    But then I guess I forgot :-) Thanks
- almost 5 years ago by mrostecki | Reply
  
  That's an interesting problem to solve and I was also thinking about it, but didn't come up with any solution.
  
  But yes, working on something "toolbox like" based on podman and container images sounds like a good approach to me.
  - almost 5 years ago by fcrozat | Reply
    
    This would have also the good approach of developers being able to use either MicroOS Desktop or Fedora Silverblue in the same way, without the need to learn something new for our solution.
    
    almost 5 years ago by dfaggioli | Reply
    
    Yep, indeed. Basically, this: "Toolbox: using Silverblue for development - Debarshi Ray - Flock 2019" ( https://www.youtube.com/watch?v=BGXs0W6NRBM )
    
    Edit Comment 4328
    
    # A First Level Header ## A Second Level Header Use one asterisk to *emphasize* Use two asterisks for **strong emphasis** - Use hyphens - for unordereed - lists This is an [link to example.com](http://example.com/) This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png) This is a user link @hans This is a project link hw#some-cool-title
    
    More Complex Markdown Help
    
    Formatting Help
    
    Edit
    
    Preview
    
    Yep, indeed. Basically, this: "Toolbox: using Silverblue for development - Debarshi Ray - Flock 2019" ( https://www.youtube.com/watch?v=BGXs0W6NRBM )
    
    Reply to dfaggioli
    
    Yep, indeed. Basically, this: "Toolbox: using Silverblue for development - Debarshi Ray - Flock 2019" ( https://www.youtube.com/watch?v=BGXs0W6NRBM )
    
    # A First Level Header ## A Second Level Header Use one asterisk to *emphasize* Use two asterisks for **strong emphasis** - Use hyphens - for unordereed - lists This is an [link to example.com](http://example.com/) This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png) This is a user link @hans This is a project link hw#some-cool-title
    
    More Complex Markdown Help
    
    Formatting Help
    
    Edit
    
    Preview
  - almost 5 years ago by dfaggioli | Reply
    
    Ok. So I guess I'm actually joining, I will look into how toolbox actually works and see if I can come up with something similar (but different! :-D)
    
    almost 5 years ago by mrostecki | Reply
    
    Can't we actually use toolbox and contribute to it if you are not going to find any big disadvantages of that project? It's under "containers" organization on Github - https://github.com/containers/toolbox, so IMO we shouldn't consider it to be a "Red Hat project" - SUSE contributes to various github.com/containers projects too. It seems to use podman and it doesn't seem to depend on (rpm-)ostree, so it should work on openSUSE just fine.
    
    almost 5 years ago by dfaggioli | Reply
    
    Sure, I'm fine trying that and see if I can make it work for us. Definitely
    
    Edit Comment 4338
    
    # A First Level Header ## A Second Level Header Use one asterisk to *emphasize* Use two asterisks for **strong emphasis** - Use hyphens - for unordereed - lists This is an [link to example.com](http://example.com/) This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png) This is a user link @hans This is a project link hw#some-cool-title
    
    More Complex Markdown Help
    
    Formatting Help
    
    Edit
    
    Preview
    
    Sure, I'm fine trying that and see if I can make it work for us. Definitely
    
    Reply to dfaggioli
    
    Sure, I'm fine trying that and see if I can make it work for us. Definitely
    
    # A First Level Header ## A Second Level Header Use one asterisk to *emphasize* Use two asterisks for **strong emphasis** - Use hyphens - for unordereed - lists This is an [link to example.com](http://example.com/) This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png) This is a user link @hans This is a project link hw#some-cool-title
    
    More Complex Markdown Help
    
    Formatting Help
    
    Edit
    
    Preview
    
    Edit Comment 4330
    
    # A First Level Header ## A Second Level Header Use one asterisk to *emphasize* Use two asterisks for **strong emphasis** - Use hyphens - for unordereed - lists This is an [link to example.com](http://example.com/) This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png) This is a user link @hans This is a project link hw#some-cool-title
    
    More Complex Markdown Help
    
    Formatting Help
    
    Edit
    
    Preview
    
    Can't we actually use toolbox and contribute to it if you are not going to find any big disadvantages of that project? It's under "containers" organization on Github - https://github.com/containers/toolbox, so IMO we shouldn't consider it to be a "Red Hat project" - SUSE contributes to various github.com/containers projects too. It seems to use podman and it doesn't seem to depend on (rpm-)ostree, so it should work on openSUSE just fine.
    
    Reply to mrostecki
    
    Can't we actually use toolbox and contribute to it if you are not going to find any big disadvantages of that project? It's under "containers" organization on Github - https://github.com/containers/toolbox, so IMO we shouldn't consider it to be a "Red Hat project" - SUSE contributes to various github.com/containers projects too. It seems to use podman and it doesn't seem to depend on (rpm-)ostree, so it should work on openSUSE just fine.
    
    # A First Level Header ## A Second Level Header Use one asterisk to *emphasize* Use two asterisks for **strong emphasis** - Use hyphens - for unordereed - lists This is an [link to example.com](http://example.com/) This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png) This is a user link @hans This is a project link hw#some-cool-title
    
    More Complex Markdown Help
    
    Formatting Help
    
    Edit
    
    Preview
    
    almost 5 years ago by mrostecki | Reply
    
    Maybe we could start contribution with having the openSUSE image in images/ directory ;)
    
    Edit Comment 4332
    
    # A First Level Header ## A Second Level Header Use one asterisk to *emphasize* Use two asterisks for **strong emphasis** - Use hyphens - for unordereed - lists This is an [link to example.com](http://example.com/) This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png) This is a user link @hans This is a project link hw#some-cool-title
    
    More Complex Markdown Help
    
    Formatting Help
    
    Edit
    
    Preview
    
    Maybe we could start contribution with having the openSUSE image in images/ directory ;)
    
    Reply to mrostecki
    
    Maybe we could start contribution with having the openSUSE image in images/ directory ;)
    
    # A First Level Header ## A Second Level Header Use one asterisk to *emphasize* Use two asterisks for **strong emphasis** - Use hyphens - for unordereed - lists This is an [link to example.com](http://example.com/) This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png) This is a user link @hans This is a project link hw#some-cool-title
    
    More Complex Markdown Help
    
    Formatting Help
    
    Edit
    
    Preview
    
    almost 5 years ago by mrostecki | Reply
    
    On the other hand, seems like there is a huge rewrite in Go pending https://github.com/containers/toolbox/pull/318
    
    almost 5 years ago by RBrownSUSE | Reply
    
    Our toolbox we already have is already better than most other distros toolboxes..it does everything I'd ever want (except one thing..which I will fix one day) but hey if others want to look at it I dont object :)
    
    Edit Comment 4418
    
    # A First Level Header ## A Second Level Header Use one asterisk to *emphasize* Use two asterisks for **strong emphasis** - Use hyphens - for unordereed - lists This is an [link to example.com](http://example.com/) This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png) This is a user link @hans This is a project link hw#some-cool-title
    
    More Complex Markdown Help
    
    Formatting Help
    
    Edit
    
    Preview
    
    Our toolbox we already have is already better than most other distros toolboxes..it does everything I'd ever want (except one thing..which I will fix one day) but hey if others want to look at it I dont object :)
    
    Reply to RBrownSUSE
    
    Our toolbox we already have is already better than most other distros toolboxes..it does everything I'd ever want (except one thing..which I will fix one day) but hey if others want to look at it I dont object :)
    
    # A First Level Header ## A Second Level Header Use one asterisk to *emphasize* Use two asterisks for **strong emphasis** - Use hyphens - for unordereed - lists This is an [link to example.com](http://example.com/) This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png) This is a user link @hans This is a project link hw#some-cool-title
    
    More Complex Markdown Help
    
    Formatting Help
    
    Edit
    
    Preview
    
    Edit Comment 4334
    
    # A First Level Header ## A Second Level Header Use one asterisk to *emphasize* Use two asterisks for **strong emphasis** - Use hyphens - for unordereed - lists This is an [link to example.com](http://example.com/) This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png) This is a user link @hans This is a project link hw#some-cool-title
    
    More Complex Markdown Help
    
    Formatting Help
    
    Edit
    
    Preview
    
    On the other hand, seems like there is a huge rewrite in Go pending https://github.com/containers/toolbox/pull/318
    
    Reply to mrostecki
    
    On the other hand, seems like there is a huge rewrite in Go pending https://github.com/containers/toolbox/pull/318
    
    # A First Level Header ## A Second Level Header Use one asterisk to *emphasize* Use two asterisks for **strong emphasis** - Use hyphens - for unordereed - lists This is an [link to example.com](http://example.com/) This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png) This is a user link @hans This is a project link hw#some-cool-title
    
    More Complex Markdown Help
    
    Formatting Help
    
    Edit
    
    Preview

almost 5 years ago by RBrownSUSE | Reply

Hi all - anyone working on this project, I'm hanging out in #microos-desktop on irc.freenode.org now - we should use that to coordinate/chat :)

almost 5 years ago by RBrownSUSE | Reply

Current Steps In Progress at Time of Writing:
- Submit new skelcd-control-MicroOS to YaST>Factory
- Submit new microos-patterns to Factory
- Ensure product builds media with new patterns-microos-[gnome|kde]-desktop patterns
At this point MicroOS ISO's should have both a KDE and GNOME system role in 'Alpha' status

Steps that must be accomplished to reach 'Beta'
- Some openQA testing
- Basic working functionality like logging in, application installation, etc
Steps to remove the ugly 'Alpha' or 'Beta' flag from the installation
- openQA testing for boot, login, application installation and some apps running
- No unexpected reboots/sensible rebootmgr configuration
- Notification to the user when a reboot is required
- almost 5 years ago by RBrownSUSE | Reply
  
  Steps to remove the ugly 'Alpha' or 'Beta' flag from the installation
  - Both KDE and GNOME should have an optimised package list from the hacked together examples right now
- almost 5 years ago by RBrownSUSE | Reply
  Current Steps In Progress at Time of Writing:
  
  Submit new skelcd-control-MicroOS to YaST>Factory
  
  Submit new microos-patterns to Factory
  
  Ensure product builds media with new patterns-microos-[gnome|kde]-desktop patterns
  https://build.opensuse.org/request/show/773663 https://build.opensuse.org/request/show/773664 https://build.opensuse.org/request/show/773665
  
  Above is all otw to Factory, to be staged and adjusted there

almost 5 years ago by Cbran | Reply

Could someone show me around this?

almost 5 years ago by dfaggioli | Reply

Update from me: - we're discussing (in opensuse-kubic@opensuse.org) whether/how to change our toolbox image in order for it to fulfill the requirements of https://github.com/containers/toolbox - Thorsted has pushed some of those changes to devel:kubic:containers (see: https://build.opensuse.org/package/rdiff/devel:kubic:containers/opensuse-toolbox-image?linkrev=base&rev=7 ) - I've worked on making our toolbox a little bit more comfortable to use for development: https://github.com/dfaggioli/microos-toolbox/tree/user-mode https://github.com/kubic-project/microos-toolbox/pull/2

almost 5 years ago by dfaggioli | Reply

[Sorry for posting this twice, but the previous comment I wrote is barely readable! :-/]

Update from me:
- we're discussing (on opensuse-kubic-AT-opensuse-DOT-org) whether / how to change our toolbox image in order for it to fulfill the requirements of containers/toolbox
- Thorsten has pushed some of those changes to devel:kubic:containers already (see: here)
- I've worked on making our toolbox a little bit more comfortable to use for development:
  - dfaggioli/microos-toolbox:user-mode
  - kubic-project/microos-toolbox:pull/2

over 3 years ago by RBrownSUSE | Reply

Hackweek 20 went well, briefest summary is currently on twitter, and will be included in the Lightning talks on Friday

https://twitter.com/sysrich/status/1375443718132613120

Description

Get the Enlightenment stack + X...

New openSUSE-welcome by lkocman

Project Description

Let's revisit our exi...

YQPkg - Bringing the Single Package Selection Back to Life by shundhammer

tl;dr

Rip out the high-level YQPackageSele...

Update Haskell ecosystem in Tumbleweed to GHC-9.10.x by psimons

Description

We are currently at GHC-9.8.x...

Description

We are currently at GHC-9.8.x...

gnome

Write a shell extension for GNOME by tdz

Description

I usually do kernel and syste...

obs

Bootstrap openSUSE on LoongArch by glaubitz

Description

LoongArch is a new architectu...

Git CI to automate the creation of product definition by gyribeiro

Description

Automate the creation of produc...

Core Project

Sub Projects (Hackweek 18/19)

BPF powered Tor networking for flatpaks

openSUSE Flatpaks

Hackweek 20

Hackweek 20 Results

Looking for hackers with the skills:

This project is part of:

Activity

Comments

almost 5 years ago by mrostecki | Reply

almost 5 years ago by RBrownSUSE | Reply

almost 5 years ago by mrostecki | Reply

almost 5 years ago by dfaggioli | Reply

almost 5 years ago by fcrozat | Reply

almost 5 years ago by dfaggioli | Reply

almost 5 years ago by mrostecki | Reply

almost 5 years ago by fcrozat | Reply

almost 5 years ago by dfaggioli | Reply

almost 5 years ago by dfaggioli | Reply

almost 5 years ago by mrostecki | Reply

almost 5 years ago by dfaggioli | Reply

almost 5 years ago by mrostecki | Reply

almost 5 years ago by mrostecki | Reply

almost 5 years ago by RBrownSUSE | Reply

almost 5 years ago by RBrownSUSE | Reply

almost 5 years ago by RBrownSUSE | Reply

almost 5 years ago by RBrownSUSE | Reply

almost 5 years ago by RBrownSUSE | Reply

almost 5 years ago by Cbran | Reply

almost 5 years ago by dfaggioli | Reply

almost 5 years ago by dfaggioli | Reply

over 3 years ago by RBrownSUSE | Reply

Similar Projects

opensuse

Create openSUSE images for Arm/RISC-V boards by avicenzi

Enlightenment in Leap 16 by simotek

Description

New openSUSE-welcome by lkocman

Project Description

YQPkg - Bringing the Single Package Selection Back to Life by shundhammer

tl;dr

Update Haskell ecosystem in Tumbleweed to GHC-9.10.x by psimons

Description

tumbleweed

Tumbleweed on Mars-CM (RISC-V board) by ph03nix

Update Haskell ecosystem in Tumbleweed to GHC-9.10.x by psimons

Description

gnome

Write a shell extension for GNOME by tdz

Description

obs

Bootstrap openSUSE on LoongArch by glaubitz

Description

Git CI to automate the creation of product definition by gyribeiro

Description

Fix RSpec tests in order to replace the ruby-ldap rubygem in OBS by enavarro_suse

Description

Automation of ABI compatibility checks by ateixeira

Description

Research openqa-trigger-from-obs and openqa-trigger-from-ibs-plugin by qwang

Description

distribution

Switch software-o-o to parse repomd data by hennevogel

Testing and adding GNU/Linux distributions on Uyuni by juliogonzalezgil

Explore simple and distro indipendent declarative Linux starting on Tumbleweed or Arch Linux by janvhs

Description