Issues/things to improve with NS8b1

[giacomo (Giacomo Sanchietti)]

@NLS

Irrelevant thing: I don’t know how you make those smart quotes in this forum software. You do it manually?

here you are How do I quote someone? - support - Discourse Meta

@NLS

So, if you ask me, Cockpit (that seems to manage the actual “backbone” OS, outside NS boundaries), has to be pre-installed and not be enabled manually AND used to manage actual basic setup for pre-built images at least. This because, ok if you add NS8 on an existing Linux setup, hostname, IP and such are already configured, but with prebuilt images an “elementary admin” way would be nice. OR make sure to have a “first-run” script, to force user to supply required information.

@NLS

About the clarification you want on doc improvement.

I agree, but I’m too inside the project: I hope someone less involved could help on it!

@NLS

So, if you ask me, Cockpit (that seems to manage the actual “backbone” OS, outside NS boundaries), has to be pre-installed and not be enabled manually AND used to manage actual basic setup for pre-built images at least. This because, ok if you add NS8 on an existing Linux setup, hostname, IP and such are already configured, but with prebuilt images an “elementary admin” way would be nice. OR make sure to have a “first-run” script, to force user to supply required information.

I do not want Cockpit on my installation! Too much unused deps: to do basi network stuff the CLI is enough for most sysadmin.
The problem here is: I fear that we add Cockpit we should also support stuff about the distro …

@NLS

I think for pre-built images, an admin user has to be pre-configured in OS level (NOT root) and share same password in shell login, Cockpit and Cluster Manager.
IIRC in shell and Cockpit I needed to use root and Cluster Manager used admin.

This is wrong from a security perspective: admin and root are different users and should remain the same. root manages the OS, admin manages the cluster.
You are still free to create an administrative user for the cluster called root, but IMHO it’s a bad practice.

@NLS

Backup to local provider is hardly my idea. NS7 does it, so I expect to be available again.

Fair enough: we already have the card Trello, I just expanded it a bit.

@NLS

Not sure where you answer in the other post about why smart-host needs its own “main” config section (also was like that in NS7), instead of being a tiny part of mail subsystem configuration. Is it because it is also needed, possibly for report emails? (even if no mail module is installed)

It’s needed by the app. Example: you have a server with only Nextcloud installed, Nextcloud needs to deliver mail to user for share links.
The smart host config is propagated to all installed app (Nextcloud, Mattermost, etc).

@NLS

I have no idea of the inline doc of the migration tool, as I haven’t run it yet. But whatever is in there, should be in the offline docs too and people know what to expect in all migration cases (and issues). It is vital, given the sensitivity of the process.

You’re right, we have it: NethServer 7 migration — NS8 documentation
Still, we can expand it!