Issues/things to improve with NS8b1

Feature
4

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

So I have to revert to numbers (as I read all replies - so not referencing my original numbering):

  1. Migration tool indeed shows up today. Didn’t, when I posted yesterday (and after refreshing for possible updates).

  2. About the clarification you want on doc improvement.
    First of all, everything is necessary. No info is “too much info”, as you don’t know who reads it.
    My experience in my position has shown me this much. (I am 25+ years an IT pro and maybe half of them managing IT infrastructure and teams). I like to use the term “stupid proof”.

  3. 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.

  4. 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.

  5. I am very patient. :smiley: I just wanted to know that a rich dashboard is indeed in the roadmap.

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

  7. 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)

  8. 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.

Love how things are starting to be more alive (for the rest of us - surely the dev team was already very active), keep strong as a public beta means a flood of new feedback on things you may have not thought/encountered in closed alpha.

1 Like