I’ll try: i simply won’t use a spoon to open a can.
If a Hypervisor is needed, i will use it. If a container approach is needed, i will use it.
Currently, NethServer is neither both of that. And i think is quite useless and out of focus put above NethServer the whole stack of containers or hypervisor, only to have “only one server”.
It were proposed a module for managing KVM virtualization above NethServer, but AFAIK is not available any more, even if KVM is already available as support on CentOS.
NethServer can do a lot of things, currently “one man band” installation for a office or a small company, but the real “core” of nethserver is the template management.
All the functionalities are coming from well known packages of linux (postfix, samba, dovecot, sieve, squid, dhcpd, dnsmasq, shorewall), free version of projects/products (nTOP, NextCloud, Mattermost) and a stack of tools for using other products (FreePBX for accessing and managing asterisk).
Don’t get me wrong, it’s a hell of job to keep pieces together, but when a piece will fall (shorewall) unless a new and… sufficiently easy piece to integrate will be considered, the feature will fall, expecially if there will be not updates or support from the customers.
Customers wants solutions; well, containers or hypervisor on top if NethServer IMVHO is calling for problems, not solutions.
NethServer 8 will substitute modules with containers? As already stated before, some modules are perfect for becaming containers (webtop, unifi management , MatterMost, even Asterisk), some others not.
And also: who’s willing to have a server without IPv6 management and support, as next generation?
No. CentOS is already supporting it not an answer, CentOS supports IPv6 at least since 6.x (don’t know even if 5.x had it). I mean… IPv6 was available in Windows XP buddies. The demonified and use like a scarecrow from most of sensed users of this community.