Can I safely move my simple setup to NS8 b1?

Can I ask something specific for my case?
My home server consists of UNRAID and a VM with NS7.
It serves both as my personal “production” and test bed.
I have installed various modules, but the one module I actually need to be working from day one, is migrate my mail and using webtop (or other web client?).
My mail has few accounts (so I also use LDAP provider and I need to migrate my users), uses smarthost for outgoing mail (which I think is a requirement for NS8 for now) and gets email using a IMAPS connectors.

(everything else to implement in NS8 will be a bonus - I don’t even need to migrate it)

  1. Can I safely move my simple setup to NS8b1? (although I will probably wait until b2 to be honest) Which means a separate VM I guess (and changing my port forwarding etc.).
    Again: Move my few users and email setup AND current mailbox contents and re-implement a web mail interface.

  2. In what state will this migration leave my NS7 setup? (asking for security reasons) In other words aside from reverting port forwarding and having lost possible new mail while NS7 was offline, can it be brought back to production?

  3. Future betas and final will need further migrations or actual in-place updates (over NS8b)?

Add to above:

  • Migration tool doesn’t seem to be available yet.

  • I know probably you guys will not answer this directly, but is there a suggested image (distro) to use? Or to maybe have an answer, are there parameters that can help us choose one image over another? Like more complete or smaller footprint choices? Which is which? Is there any that is more tested?

I don’t think there’s a practical difference among Alma/Rocky/CentOS. I’m pretty sure Oracle Linux 9 can also be used, but they don’t endorse that. I do recall hearing that Debian 11 had an old-ish version of some important package (podman, perhaps?), which would tend to make it less favored. With any of the RHEL variants, a minimal install is all you need.

I am asking about the prebuilt images (that will run on KVM).

Possible differentiating factors:

  • Smallest storage footprint?
  • Smallest memory footprint?
  • Richest-non-NS8 functionality (from start)?
  • Most NS8 tested distro?
  • Easiest to admin distro?

Would be nice to know.
Remember that one of NS “selling” points, is to be able to implement specific services without the deepest knowledge of the underlying system (because else, someone would argue, that NS is not needed and everything can be manually configured by an experienced Linux admin).
So such a table would be a great asset.

Ah, then in that case I’m afraid I can’t help–though I’d still be surprised if there were any significant difference (in storage, memory, non-NS8 functionality, or administration) among Alma/Rocky/CentOS, as they’re all pretty much the same distro.

1 Like

Indeed they are - my question about those three extends beyond NS8. :smiley:
They seem more like “I want to make my own thing” than make actual difference.

Seeing that NS8 team actually suggests 3 RHEL based distros and a single Debian, I tend to think they actually want us to use an RHEL based solution. :smiley: So one is “kind of” out already.

Note that my original questions remain. :slight_smile:

Surely you remember the CentOS 8 debacle, where RedHat without warning pissed away the trust they’d bought when they took over the CentOS project, and changed what had for many years been a stable, LTS server distro to a “rolling release” model. Lots of people saw a need for an EL-compatible LTS server distro, whence came both Alma and Rocky (Oracle Linux had already been around for a number of years)–so that’s arguably a reason to avoid CentOS. But among the three, AFAIK, preferences would be more based on philosophy than on any technical difference.

1 Like

Yes of course I remember that (which probably further limits my choices to Rocky and Alma), but I am saying this for those two builds.
This is an interesting read for some:
Rocky Linux vs. AlmaLinux {the Differences} (phoenixnap.com)

BTW I selected Rocky for my tests.

BUT my original 3 questions (and the point of the thread) remain.
(although I now know about #2 probably - seems every service migrated “disables” it from NS7 side)

1 Like

Hi @NLS

And the main reason for virtualization is also the fact that you can easily make a full backup - and restore that after migration… (As a saftey measure!)…

My 2 cents
Andy

Thank you for testing Nick!

It’s not a requirement. You need it only if you want to receive mails from the server from apps and you do not have the mail server installed and configured.

IMAP connector is still not available.

Wise choice: wait the rc for a production server :slight_smile:
Except of IMAP connectors, the other things on your server should already work.

It will be attached to cluster until the migration ends.

can it be brought back to production?

Yes.

We do not still know if we are going to have an in-place upgrade.

It is, I can see from the software center:

I know probably you guys will not answer this directly, but is there a suggested image (distro) to use?

I’d go for a RHEL-based for now.

We probably will support only RHEL-based distro for the Enterprise part (we already have know how).

Nailed it. Still, Debian 12 (scheduled for June) should be a solid base.

1 Like

Thanks for the reply Giacomo!

I hope IMAP (or even POP?) connectors come soon enough (b2?).

Indeed I saw the Migration tool TODAY. At the time of my posting, after several refreshes on available updates etc., it was nowhere to be seen.

Keep up the good work.

So my new questions I guess are:

  1. When is next beta.
  2. What is the schedule for email connectors? :stuck_out_tongue:

Probably July as I wrote in the announcement :slight_smile:

1 Like

My hope is never: they are always source of problems for the support team.
I really would like to drop that feature. :innocent:

Still, we have listed it under “To future releases” list: Trello
I’m quite sure that such feature will not be on next beta.

1 Like

OK thanks.

It is vital to some of us.

1 Like