1
21.1 Legacy Series / Re: Is OPNsense stable or not? Is it really production safe or not?
« on: March 13, 2021, 10:50:15 am »
This was quite enlightening the answers I got here.
I never knew that there where 2 versions of OPNsense.
I always thought you could buy a business support subscription on top of the version you can download from the main opnsense.org website.
The website gives the impression that there is only one version of OPNsense.
So if I understand correctly:
One is the default version that is not stable/reliable and production ripe you can find on the main page of https://www.opnsense.org/
And the other version is a stable version called the business version which is more stable because it only gets save updates and upgrades that won't break anything I guess.
The one you can download from the main opnsense.org website I consider that unstable and I even want to slap a testing label on it when you compare it to how other BSD like and Linux distributions handle it all.
This should be expressed on the main website that this is a testing branch rather than a stable branch version to keep users from big surprises that there firewall, there main gate to the internet, is at risk of breaking down due to updates and or upgrades.
Calling it "production¨ isn't that a bit misleading?
You can name it like that because its constant work in progress, but at least tell your users that it is a testing/unstable branch and that they should expect bugs that might break your firewall/internet gateway on a regular basis and that it should be considered as unreliable.
The name production means (to me) being stable, reliable, code mature, ripe for live production environments.
And on what part of your network you want stability and reliability? Right, your gateway to the internet!
Now I am a (sometimes grumpy) old fart and have seen and used lots of distributions through the years since the 90's. But when the other distributions call something stable and reliable they mean it and you can expect that the code is mature enough to be used live in production situations and relied on.
I never knew that there where 2 versions of OPNsense.
I always thought you could buy a business support subscription on top of the version you can download from the main opnsense.org website.
The website gives the impression that there is only one version of OPNsense.
So if I understand correctly:
One is the default version that is not stable/reliable and production ripe you can find on the main page of https://www.opnsense.org/
And the other version is a stable version called the business version which is more stable because it only gets save updates and upgrades that won't break anything I guess.
The one you can download from the main opnsense.org website I consider that unstable and I even want to slap a testing label on it when you compare it to how other BSD like and Linux distributions handle it all.
This should be expressed on the main website that this is a testing branch rather than a stable branch version to keep users from big surprises that there firewall, there main gate to the internet, is at risk of breaking down due to updates and or upgrades.
Calling it "production¨ isn't that a bit misleading?
You can name it like that because its constant work in progress, but at least tell your users that it is a testing/unstable branch and that they should expect bugs that might break your firewall/internet gateway on a regular basis and that it should be considered as unreliable.
The name production means (to me) being stable, reliable, code mature, ripe for live production environments.
A system that is stable and reliable enough that you can count on not to break every month due to updates/upgrades?Is it stable or not? Is it really production safe or not?
So what's our point of reference.
And on what part of your network you want stability and reliability? Right, your gateway to the internet!
Now I am a (sometimes grumpy) old fart and have seen and used lots of distributions through the years since the 90's. But when the other distributions call something stable and reliable they mean it and you can expect that the code is mature enough to be used live in production situations and relied on.