Questions on openSUSE Leap Micro and the repository setup
Hello everyone, I recently had some time to try out Leap Micro 5.3 and got a little confused on its intention. My idea was to setup a Uyuni server on this machine, but during the initial preparation I found that the repository setup is quite different to Leap 15.4 and openSUSE MicroOS. openSUSE MicroOS is basically Tumbleweed with a special btrfs subvolume setup to get the read-only root filesystem. But the repositories are the same as on Tumbleweed. Leap Micro 5.3 has separate repositories, and lots of other repositories are missing compared to a standard 15.4 installation. My guess would be that the reason behind this is to get a really "micro" system. But I was missing several of the packages that I normally install on the host, even if all the actual workloads are in containers or Kubernetes etc. Things like postfix, tcpdump, nmap. Sure, I can run them some of them inside containers (think toolbox), but for debugging I prefer to have them on the host. I have not yet tried out what happens if I install openSUSE Leap 15.4 with the "transactional server" selection, if this would be more in line with the setup I am used to (or spoiled by :-) ) from MicroOS. And I did not try out what happens if I add back all of the normal Leap 15.4 repositories. Felt like a good way to get nice and very subtle errors due to slight changes in some packages... As Uyuni did not yet support installation on Leap Micro / SLE Micro I just switched to a normal Leap installation. So not an urgent issue. I read the 5.2 release notes and the ones from SLE Micro 5.3, but I failed to find a clarification on the repository setup. I personally like the microOS approach of having the full flexibility and full list of packages and was looking forward to getting the same experience with a more "stable" set of packages (aka far less updates to download :-) ). Maybe the Leap 15.4 transactional-server installation is more what I am looking for? Thanks in advance, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
On Sun, Mar 19, Johannes Kastl wrote:
I recently had some time to try out Leap Micro 5.3 and got a little confused on its intention.
Leap Micro 5.3 is the openSUSE variant of SLE Micro 5.3, it is not MicroOS based on openSUSE Leap.
Sure, I can run them some of them inside containers (think toolbox), but for debugging I prefer to have them on the host.
SLE Micro is only a container host OS, so yes, you have to run them in containers. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nuernberg, Germany Managing Director: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman (HRB 36809, AG Nürnberg)
Hi Thorsten, On 20.03.23 at 07:40 Thorsten Kukuk wrote:
On Sun, Mar 19, Johannes Kastl wrote:
I recently had some time to try out Leap Micro 5.3 and got a little confused on its intention.
Leap Micro 5.3 is the openSUSE variant of SLE Micro 5.3, it is not MicroOS based on openSUSE Leap.
SLE Micro is based on a subset of packages from SLE, I guess. And I guess that Leap Micro is using the same set of packages. I was hoping that Leap Micro extends the package set from SLE Micro, just like Leap extends the base set from SLE. As that does not seem to be the case: Is there a way to get a MicroOS-like experience based on Leap? Would the "transactional-server" installation option achieve that? I guess I'll have to give it a spin. :-) Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
Hi, On Mon, Mar 20, Johannes Kastl wrote:
Hi Thorsten,
On 20.03.23 at 07:40 Thorsten Kukuk wrote:
On Sun, Mar 19, Johannes Kastl wrote:
I recently had some time to try out Leap Micro 5.3 and got a little confused on its intention.
Leap Micro 5.3 is the openSUSE variant of SLE Micro 5.3, it is not MicroOS based on openSUSE Leap.
SLE Micro is based on a subset of packages from SLE, I guess.
There is a huge overlap, but SLE Micro is not a subset.
And I guess that Leap Micro is using the same set of packages.
Leap Micro is using the same setup of packages as SLE Micro, correct.
I was hoping that Leap Micro extends the package set from SLE Micro, just like Leap extends the base set from SLE.
As that does not seem to be the case: Is there a way to get a MicroOS-like experience based on Leap? Would the "transactional-server" installation option achieve that?
I don't use openSUSE Leap nor the "transactional-server" system role, so I don't know. With openSUSE MicroOS I use the original ;) in the original configuration as Container Host OS. We use that even for our big, fat team server since several years as Virtualisation Host in a mission critical environment. There is absolute no need to use Leap Micro, quite the opposite. MicroOS is much better tested and maintained then Leap Micro ;) Thorsten
I guess I'll have to give it a spin. :-)
Kind Regards, Johannes
-- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de
B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
-- Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nuernberg, Germany Managing Director: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman (HRB 36809, AG Nürnberg)
On 20.03.23 at 10:45 Thorsten Kukuk wrote:
With openSUSE MicroOS I use the original ;) in the original configuration as Container Host OS. We use that even for our big, fat team server since several years as Virtualisation Host in a mission critical environment. There is absolute no need to use Leap Micro, quite the opposite. MicroOS is much better tested and maintained then Leap Micro ;)
No need to tell me, large parts of my private infrastructure run flawlessly on MicroOS. It is just that sometimes people are scared by the large number and frequency of updates. So having the same setup with the same advantages, but with less frequent updates, would be nice for some people. And (maybe, YMMV and IMHO) more interesting for many users that Leap Micro from what I understood. Thanks for taking the time to reply, Thorsten. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
On Mon, 2023-03-20 at 09:51 +0100, Johannes Kastl wrote:
As that does not seem to be the case: Is there a way to get a MicroOS-like experience based on Leap? Would the "transactional-server" installation option achieve that?
I'm not sure what you mean with MicroOS-like experience, but I'm running a couple of transactional Leap servers next to MicroOS and that's just nice. They update themselves over night (if there are updates available), you can do snapshot rollback (never had to do that there) and you get all packages from Leap (as opposed to Leap Micro). My Hetzner Server runs as transactional Leap server since (IIRC 15.1), updates itself automatically over night and even system upgrades were no pain. If it breaks, you can just rollback to the old snapshot. I guess that's what you mean with MicroOS-like experience, and yes, that works nicely for any transactional servers on openSUSE.
I guess I'll have to give it a spin. :-)
Go for it! Best, Felix
On 20.03.23 at 11:51 Felix Niederwanger wrote:
On Mon, 2023-03-20 at 09:51 +0100, Johannes Kastl wrote:
I'm not sure what you mean with MicroOS-like experience, but I'm running a couple of transactional Leap servers next to MicroOS and that's just nice. They update themselves over night (if there are updates available), you can do snapshot rollback (never had to do that there) and you get all packages from Leap (as opposed to Leap Micro).
That is exactly what I meant.
I guess that's what you mean with MicroOS-like experience, and yes, that works nicely for any transactional servers on openSUSE.
Thanks for the feedback, that was what I was looking for. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
participants (3)
-
Felix Niederwanger -
Johannes Kastl -
Thorsten Kukuk