Interesting play - basically they will offer generic enterprise-grade Linux support, with a not-so-veiled view to slowly replace existing installations (typically RHEL or CentOS, both explicitly namechecked) with SuSE, leveraging "SuSE Manager".
It's clearly a reaction to the civil war in the RedHat world.
SUSE has offered some level of support for RHEL/CentOS for a long time. They’ve had various programs over the years, long before this, to support customers who are on RHEL but might migrate to SLES.
The specific SKUs and details change from time to time, but it’s not really a new thing. As a trailing competitor, it’s a reasonable thing to do.
SuSE's bread and butter is professional services. They don't care what software you use, as long as you pay SuSE to consult on it.
From a practical perspective: I wouldn't use them. Their acquisition of Rancher was/is terrible. I literally couldn't give them my money without one of those stupid sales calls. Their website doesn't even have a working contact form; I had to go to their Slack to get some random engineer's attention. I'm told by colleagues that they ignore your (paid) support tickets. I have worked for enough pain-in-the-ass enterprises that I will avoid them at all costs.
Interesting… my experience has been the opposite, except for getting support. I prefer being able to get the product for free immediately and then chat about support later. It’s why we use Rancher, because it takes 20min to set up with Helm, vs like Tanzu where you have to have. an entire call and licensing and accounts to even download anything. Or D2iQ where you need to fumble with getting everything set up for a while with the sales and technical people.
Rancher has been great for me with around 200 clusters. They don’t support temporary creds for IAM stuff, so I have to provision EKS clusters on my own.
We pay for paid support and have very little problems getting them on the phone, but it is generally a consulting firm that ends up helping.
It appears you have content blocking enabled. To use all the features of this site, use a non-private window, or turn off content blocking for this site.
I'm considering trying SuSE MicroOS as a desktop for a while. Any thoughts? I tried suse for a few weeks about a quarter century ago then went back to slackware, so I have no relevant experience.
At work we traditionally have almost only SLES servers with some Oracle Linux and RHEL ones.
In the last months we gained a few more RHEL servers, which I needed to provide updates for. Our servers don't have internet connection so some sort of mirror server is required. For SUSE we use their free-of-cost RMT (and the older SMT) mirror services.
For RHEL something like this doesn't seem to exist or looks a little kludgy. So I bought some licenses for SLL:
* there where still some "repo errors" when changing from RHEL to SLL on a existing server
* I opened a support ticket, there was no finger pointing to RedHat and one or two weeks later the issue was resolved :)
Didn't realize witnessing a market leader flex their strength and have it backfire so badly would be so cathartic. Wish it would happen to other businesses more often.
SUSE gets an ex-Red Hat CEO and decides to offer support for RHEL. Interesting. Seems RHEL is still the gold standard of commercial support ;) DISCLAIMER: I’m a 18 year Red Hatter and know the SUSE CEO since many years.
SUSE does not offer support for RHEL but for their own RHEL clone (SLL, formerly and still internally SLES ES). This product has existed for a long long time.
The catch with switching from RHEL to SUSE (or Ubuntu, or whatever), is what does your vendor support?
Big fancy medical records software at the hospital? It used to run on either RHEL or CentOS. They stopped supporting 8. They won't do stream. You only have to buy one Red Hat License (unless you want to run CentOS 7.9 for the next 11-12 months), and it's tiny in comparison to what the actual software license and support costs, and we won't even get into the hardware that you're required to buy.
This is why I try to avoid healthcare and banking etc. Too much legacy vendor stuff which is hard to modernise. This whole "supported distro" stuff wouldn't matter if they just packaged their software in the shape of a container, even with container persistence. No more "required" distros. They would probably still have some CPU feature requirements and maybe a kernel version support range.
DHH interacted with a reseller and not directly with SUSE… We have our issues (as does any company selling enterprise support) but this is not an accurate representation.
Everyone can fork gcc and glibc, they are fully open source. In any case the question remains why one would want to... there are alternatives for both of 'em (musl/dietlibc for glibc, llvm for gcc).
As long as you keep to the POSIX/C/C++ standards and don't use vendor-specific attributes (or at least abstract them away via macros), you shouldn't run into issues using another kernel, libc or compiler.
[+] [-] toyg|2 years ago|reply
Interesting play - basically they will offer generic enterprise-grade Linux support, with a not-so-veiled view to slowly replace existing installations (typically RHEL or CentOS, both explicitly namechecked) with SuSE, leveraging "SuSE Manager".
It's clearly a reaction to the civil war in the RedHat world.
[+] [-] jzb|2 years ago|reply
The specific SKUs and details change from time to time, but it’s not really a new thing. As a trailing competitor, it’s a reasonable thing to do.
[+] [-] carlosrg|2 years ago|reply
The date of the announcement is January 2022 so it can't be that.
[+] [-] 0xbadcafebee|2 years ago|reply
From a practical perspective: I wouldn't use them. Their acquisition of Rancher was/is terrible. I literally couldn't give them my money without one of those stupid sales calls. Their website doesn't even have a working contact form; I had to go to their Slack to get some random engineer's attention. I'm told by colleagues that they ignore your (paid) support tickets. I have worked for enough pain-in-the-ass enterprises that I will avoid them at all costs.
[+] [-] hhh|2 years ago|reply
Rancher has been great for me with around 200 clusters. They don’t support temporary creds for IAM stuff, so I have to provision EKS clusters on my own.
We pay for paid support and have very little problems getting them on the phone, but it is generally a consulting firm that ends up helping.
[+] [-] itpcc|2 years ago|reply
Yeah... No need to fear of vendor lock-in huh?
[+] [-] c_r_w|2 years ago|reply
[+] [-] yonatan8070|2 years ago|reply
[+] [-] thesuperbigfrog|2 years ago|reply
SUSE may be a viable alternative depending on the workload requirements and cost. RHEL's push could be Red Hat's loss.
“The more you tighten your grip, the more systems will slip through your fingers.”
[+] [-] vbezhenar|2 years ago|reply
[+] [-] krylon|2 years ago|reply
But SuSE Linux was my first Linux distro, an for the past couple of years[0], I've been a happy openSUSE user, so I'm not that cynical.
[0] I still have the box with the CDs and manuals sitting on my bookshelf. :-)
EDIT: Forgot a word.
[+] [-] galangalalgol|2 years ago|reply
[+] [-] jonsger|2 years ago|reply
In the last months we gained a few more RHEL servers, which I needed to provide updates for. Our servers don't have internet connection so some sort of mirror server is required. For SUSE we use their free-of-cost RMT (and the older SMT) mirror services.
For RHEL something like this doesn't seem to exist or looks a little kludgy. So I bought some licenses for SLL: * there where still some "repo errors" when changing from RHEL to SLL on a existing server * I opened a support ticket, there was no finger pointing to RedHat and one or two weeks later the issue was resolved :)
I would say it's at least worth a try.
[+] [-] candiddevmike|2 years ago|reply
[+] [-] jacooper|2 years ago|reply
[+] [-] ilyt|2 years ago|reply
[+] [-] SoftTalker|2 years ago|reply
[+] [-] jwildeboer|2 years ago|reply
[+] [-] zxspectrum1982|2 years ago|reply
[+] [-] yankcrime|2 years ago|reply
[+] [-] bluedino|2 years ago|reply
Big fancy medical records software at the hospital? It used to run on either RHEL or CentOS. They stopped supporting 8. They won't do stream. You only have to buy one Red Hat License (unless you want to run CentOS 7.9 for the next 11-12 months), and it's tiny in comparison to what the actual software license and support costs, and we won't even get into the hardware that you're required to buy.
[+] [-] thesuperbigfrog|2 years ago|reply
Will your vendor be buying RHEL to develop their product?
Anyone developing products for RHEL will now need to buy RHEL licenses unless Rocky Linux / Alma Linux are able to maintain 100% compatibility.
This will probably make the RHEL ecosystem more expensive for everyone using it.
[+] [-] oneplane|2 years ago|reply
[+] [-] EwanToo|2 years ago|reply
[+] [-] Animats|2 years ago|reply
[+] [-] nerdo|2 years ago|reply
[+] [-] agracey|2 years ago|reply
[+] [-] sylware|2 years ago|reply
[+] [-] mschuster91|2 years ago|reply
As long as you keep to the POSIX/C/C++ standards and don't use vendor-specific attributes (or at least abstract them away via macros), you shouldn't run into issues using another kernel, libc or compiler.
[+] [-] photonbeam|2 years ago|reply
[+] [-] jmclnx|2 years ago|reply
https://news.ycombinator.com/item?id=36573872