What to expect in NS8?

Feature
41

As you stated…

And IMVHO developers should care a lot more about the community value, work, and test, because every yikes not found from the community will hit Nethesis’ QC and customers.

It’s an opinion, so… a bias par se? :person_shrugging:
You as person, developer and enthusiast have your own bias, due to technical costrain, budget, management decision and the team needs to follow.
Are my posts unfair about the situation? I hope not, and I hope that the community will emphasize that if they are, but also… do my opinions have to comply Nethesis managament and developer team decisions? I don’t think so, I’m “only” me, providing opinion… and founding elements that leads me to that.

The only “technical” reason is “no longer shorewall”. This lead to a replacement choice.
That lead to three options:

  • pick up shorewall project, revamp it if necessary and follow the development
  • write something that fit the same shoes
  • pick something existing that could fit same shoes

First two options are not viable probably for budget reasons, from this seat; feel free to deny.
Third option was the one choosen and fun fact… there are not a lot of modern enough firewall linux distros fitting the boxes already sold or currently buyable.

Now, compared to the level of tools provided from shorewall/NS7, OpenWRT is a step back, also in system footprint and disk usage. But is a step back in functionality .
Also, the necessary removal of the firewall option from the server install is a step back in functionality too.

It’s also technically necessary for the container approach? Yes. The factual technical reason is here. But everything reported before stands.

Again… I try to explain what I find wrong. I can simply say “that sucks”, or do a everytime refrain about “the best way to deploy is”… And both IMVHO are… wrong.

Project provided by Nethesis has until there proven solid, reliable, with some hiccups and whoops

but the job done from developers has been until NS7 great. Will be with Container Overlord 1.x? I cannot tell, but I trust your commitment and capabilities.

However… lots of persons delivered criticism and “that won’t work in the same old way” claims.
As staten before from other persons, leaving the adoption is still an option, but deying, deflecting and hype-pumping… is really a good way for keeping people on that? IDK.

I personally do separated devices for network and server, possible on different hardware. Many reasons are behind this preference, but… it’s me, not everyone else. So that should not bother me that much.
But what I found proper, common sense, viable, the right way to do things may or may not be interesting to the community, so it’s useless to countless times repeat that on most posts. I tried several times to provide a “do a better analysis” approach in some support threads, but what does fit me is only an example, not the best way to do things for all people.

This is the meaning behind

I am aware cannot steer the project, the ship already left the pier.
I also cannot change the current path of IT world. I’m not Microsoft, I’m aware of that (and even Microsoft IMVHO can’t do that).
I do things my way, so this means that other ways are… possible and viable to other people.
It’s simply stating the truth… what I find pleasant or not it’s irrelevant.

Probably the percentage of leaving adopters will be vastly compensated from other bigger adopters, at least as revenue standpoint. I hope that this will give room to Nethesis for increase resources on bugcheck and QC. Because for the route of Container Overlord (formerly known as NS8) lots of persons not willing to create a “one server cluster” are gonna leave. Because one server cluster is a overheaded cluster, without the advantages of the cluster…

5 Likes
42

Yes this is the situation, aren’t they two good reasons to make it as is? Did you see alternatives?

43

@pike i think if we give it abit of time for NS8 to mature, all comments and sentiments of the community included there should be some paths to have everyone if not most users from NS7 be fatoed in and their needs met in one way or another.

sometime things might not be exactly as you want them to be, but the provided method might endup being even more better than the other methods.

1 Like
44

Most probably, yes. The problem seems to be with the fact that CentOS 7 support ends middle of next year, and NS7 users will be forced to switch to something else.
Will 8 months from now on be enough for NS8 to implement all the missing features, and become a mature, proven solution that “just works” (and if it does not, can be debugged/fixed easily), as it is the case for NS7 today? And will there be enough time left for the users of NS7 to prepare and run a proper migration?
Given the state of NS8 today, I think doubts are justified. It seems like there will be a solution for early adaptors willing to take some trouble, and that can accept some missing features. But for more conservative users, or those needing the still-missing features, the migration path looks pretty risky right now.

1 Like
45

Hi @jaywalker,

You express my doubts in a concise way much better than me.

Michel-André

46

I have seen container based solutions work and do wonders and some magic that standard server deployment would never dream of, while i am not the develope rof Nethserver, but as a Software developer myself and as a systems solutions architect, i beleive i would say yes.

with regards to ease of use and ease of debugging etc, of this one, i am also alittle bit sceptical tbh, thats why most of my ran ton the community has been around administrative aspects and functions as opposed to dev related issues, when it comes to building and getting anything new implemented that i believe can be done, but as a solution, i also required the “just works” for nethserver

regarding this matter, i pointed out one aspect, for a huge numbe rof users, i am sure the deep features and integrations in NS might not really be required immediately, but the apps in Software center, if we can get all the apps that were previously available, as well as the communiity apps, then for the most apps, would be pissble to migrate a huge numbers of users.

regarding the hardcore features, only the developers can answer that with utmost precision.

As i have seen here in the community as well as on the Trello boards,

I believe the main aim is to have all features y the time we hit release, then the others will be added as time goes by. so in ost cased all users will be factored in in terms of migration.

right now, SURE,

when the Release candidate release : NOT AT ALL

47

Let’s all not forget, back in the old days we had MANY MANY more developers in the community and versions and modules matured fast. Today I only know of Nethesis team, @stephdl and @mrmarkuz and please correct me if I am wrong. So not only the product is changing, also the audience.

4 Likes
48

Here we are

3 Likes
49

Which content filter do you use in OPNsense, am I looking for something like UfdbGuard? Thanks in advance for your attention.