Could you give an example of an use-case? Because I think this choice was very much by-design.

I think Reukke will answer himself, but as for me - typical use-case is a small server, acting as all-in-one solution for small linux workgroup. E.g. a router, ldap-authentication server, common files storage and a web site ;). It would be hard to maintain and keep secure, but it's possible.
N.B. Persomally I need mfs client and I'll double check, whether it's enabled in my branch tomorrow...

In T49#766, @mickvav wrote:

I think Reukke will answer himself, but as for me - typical use-case is a small server, acting as all-in-one solution for small linux workgroup. E.g. a router, ldap-authentication server, common files storage and a web site ;). It would be hard to maintain and keep secure, but it's possible.
N.B. Persomally I need nfs client and I'll double check, whether it's enabled in my branch tomorrow...

In T49#768, @mickvav wrote:

In T49#766, @mickvav wrote:

I think Reukke will answer himself, but as for me - typical use-case is a small server, acting as all-in-one solution for small linux workgroup. E.g. a router, ldap-authentication server, common files storage and a web site ;). It would be hard to maintain and keep secure, but it's possible.
N.B. Persomally I need nfs client and I'll double check, whether it's enabled in my branch tomorrow...

Yes, for this situation. The router will be all-in-one solution router for spoke.

I think its outside our scope. vyos is a network appliance. it provides services to transfer network traffic or services essential to transfer traffic (dns, dhcp). nfs does touch this aspect at all. Neighter would a radius service but that would enable pppoe-server or hostapd,... to move traffic. Nfs is not a requirement for any deamon to move traffic. ergo outside thhe scope.

Im strongly against mainlining this. there are more than enough alternatives who can and you are free to roll your own.

edit: This argument isn't persé against a nfs server, but if we do this, why shouldn't we implement a web-based torrent client as well? We should pick a well thought principe to adhere to when it comes to including new daemons or large features.

@EwaldvanGeffen
i will be happy to have ability add nfs/nettalk/cifs
for that type of home appliances, not sure how we should handle such deviations
I believe we should not be restrictive in this matter

@dmbaturin put your 5 cents too, please!

Why would anybody want to use a router as a "small server"? General Linux distributions have everything you need for a small server.

From a service provider view running about 80 vyos routers this is really a bad direction for a router.

There are a lot of things needed in a serious router which is needed to be fixed. If Vyos is evolving towards a generic "small server all inclusive" distro it will not be interesting for people like me to use it as a router.

It may be right for Vyos even if it's not good for me, but it would be nice to know if I need to migrate all my routers to something else. If the project wants to create something other than a good router let people know so we know what we can expect. There are probably not just me which see a clarification of the goal for the Vyos in the future. Should Vyos be a nice to have SOHO router or something which are targeted at datacenters and serviceproviders.

Well, I think that anyone, who really needs some specific feature set, nfs server, samba server, whatever, can make and maintain his own fork of vyos-build and it has (almost) no problem to build a speific iso himself.

@mickvav exactly, we looking to provide some support in that direction
@aopdal, I understand your concerns, but also don't find limiting users as something good,
@UnicronNL ported 1.2 to clearfog pro device, NFS server will be a good addition there for example,
we also talked about SIP functionality, all that Network Functions.
It does not about create multi-purpose distro, more like provide ability to build customized images