Live data from Hacker News

OpenSUSE MicroOS

microos.opensuse.org

1–10 of 35 posts

Re: OpenSUSE MicroOS

#3

This sounds neat, but the system requirements seem a little odd. Minimum 20 GB of disk space for a stripped down Linux distro?

That is what I was thinking, a very heavy "micro" instance.

I am curious what exactly this is envisioned for. Running micro services do not require such things and the system requirements are so heavy, it would need more hardware to run that just running them all in a normal distro.

I never jumped on the container bandwagon since it seems like it adds overhead for very little gain that can't be done with much lighter solution.

Re: OpenSUSE MicroOS

#4

This sounds neat, but the system requirements seem a little odd. Minimum 20 GB of disk space for a stripped down Linux distro?

The space is probably required for btrfs snapshots and to keep the last "good" image around in case a rollback is needed.

Re: OpenSUSE MicroOS

#5
post #4

This sounds neat, but the system requirements seem a little odd. Minimum 20 GB of disk space for a stripped down Linux distro?

The space is probably required for btrfs snapshots and to keep the last "good" image around in case a rollback is needed.

You're most probably right. I run my system on a 20gb btrfs partition and I have run into issues before where I ran out of space because of one big binary file that was in every snapshot.

Re: OpenSUSE MicroOS

#6
post #3

This sounds neat, but the system requirements seem a little odd. Minimum 20 GB of disk space for a stripped down Linux distro?

That is what I was thinking, a very heavy "micro" instance. I am curious what exactly this is envisioned for. Running micro services do not require such things and the system requirements are so heavy, it would need more hardware to run that just running them all in a normal distro. I never jumped on the container bandwagon since it seems like it adds overhead for very little gain that can't be done with much lighter…

JeOS is the SUSE OS for small footprint virtualized environments.

I'm not too sure what niche MicroOS is supposed to fill that JeOS and the full-weight Leap don't already cover.

MicroOS just seems to be answer to RedHat's Silverblue, but with no clear use case in the SUSE/openSUSE product lineup. It makes some sense as a tech demo for an immutable OS, but not much sense as an operational product.

Re: OpenSUSE MicroOS

#7
This is awesome work on the part of the openSuse team! I have always liked the steady improvement openSuse and SuseEL have made over the last 5 years or so. While they are sort of the underdog still (just look at their numbers compared to RH), the fact that at least we have an alternative to RHEL in SEL for when companies require support contracts, is a huge benefit to users. I try not to talk about Canonical for... reasons.

As for microOS, I hope that SEL takes it up with a supported version, as I think this sort of "heres a small, minimal OS suited well to being treated as cattle" approach still has lots of mindshare to capture (soorry alpine, I'll stick to gnuland!), and a large part of that mindshare is in corporations. Although, that said, I do find myself pondering nix and guix a lot more lately than just minimal installs. For some cases I know it's a bad idea, but I have settled on rolling release being the better update model for linux when not stopped by business requirements, and the more minimal the install the less likelyhood of rolling release versions having issues, plus that sort of thing should be caught in testing right? Cool stuff, gonna have to give this a space in my vps list.

Re: OpenSUSE MicroOS

#9
post #8

Love it, I just not gone use anything with BTRFS. Any chance I can get the same with ZFS instead?

> just not gone use anything with BTRFS.

Why? (Legitimately asking, I haven't played around much with using different filesystems.)

Re: OpenSUSE MicroOS

#10
post #3

Earlier quoted context omitted.

That is what I was thinking, a very heavy "micro" instance. I am curious what exactly this is envisioned for. Running micro services do not require such things and the system requirements are so heavy, it would need more hardware to run that just running them all in a normal distro. I never jumped on the container bandwagon since it seems like it adds overhead for very little gain that can't be done with much lighter…

JeOS is the SUSE OS for small footprint virtualized environments. I'm not too sure what niche MicroOS is supposed to fill that JeOS and the full-weight Leap don't already cover. MicroOS just seems to be answer to RedHat's Silverblue, but with no clear use case in the SUSE/openSUSE product lineup. It makes some sense as a tech demo for an immutable OS, but not much sense as an operational product.

JeOS it's a striped down version of a full blown linux bistro. Think Like RH,Centos. Can be used as a VM os or for anything else.

MicroOS it's a cloud OS linux, more like: CoreOS, RancherOS, AtomicOS. I think it's a default choose for Kubernetes environments.

I've been using JeOS for k8s hosts of Rancher environments since RancherOS was deprecated and I'm glad that they finally released a cloud OS like MicroOS. In case of k8s upgrades, rollbacks and upgrades need to me minimised as much as possible. This OS allow to have all of that in a breeze since it's all based on static images.

Post reply on HN