As a side note a clear statement on deprecated/replaced packages, and migration between them might be helpful when the final version is released, extending the present release notes.
Upgrade from v6.x to v7, and maintenance period of current packages (this might already been answered somewhere).
This will fill the gaps on common questions like, for instance,
Let’s start with it: restore a backup set of ns6 on ns7.
Luckily, there are more similarites than differences. Most of the modules are 1-1 upgrade. I’d like to discuss about how to cope with differences!
The File server/Shared folders module received the biggest changes, and present the following issues:
Authenticated access to shared folders. If the account provider is LDAP, authentication cannot work: Active Directory is required.
Web access to shared folders. In ns7, web access is provided by a new package, nethserver-virtualhosts. Shared folders are accessible only as Samba shares (also SFTP and NFS soon - yes, this is another story).
retain nethserver-directory as ns6 (LDAP provider) after restore
If needed, perform an additional, separate, step: upgrade to nethserver-dc
The upgrade is technically possible because the ns6 LDAP backup contains the Samba SAM DB data.
About 2, there could be different solutions, depending on how a particular shared folder is used. Possible scenarios that come to mind:
The shared folder was the virtual host web root: http://vhost.tld
The shared folder was a path in a particular virtual host http://vhost.tld/ibayaliasname
The shared folder was available from ANY virtual host (global): http://192.168.1.1/ibayaliasname, http://vhost.tld/ibayaliasname …
HTTP Basic Authentication was required
Custom filesystem permissions are set
(…did I miss something?)
It’s hard to catch them all. Let’s see some possible approaches:
Run a special upgrade script that generates a backward-compatible Apache .conf file and place it under /etc/httpd/conf.d/. If filesystem permissions allow it, Apache can still serve contents from shared folders.
Run a special “Upgrade to virtual host” action to “Shared Folders”, something like:
I feel the “Upgrade to virtual host” action would cover a lot of upgrade requirements. It’s missing scenario 3. Because of it, a generated .conf file is still necessary.
We just implemented the described behavior of 1, 2 and 3.
Shared folder available from ANY virtual host (global) are migrated to a new special virtual host named default.
yes i do a quick test in past week-end, on my mail server+ file server
but i have no notes written
i remember two problem:
restore of apps seemed ok, but it seems to have some preblem on mail:
mail was restored in /var/lib/nethserver/vmail/user
instead of /var/lib/nethserver/vmail/user@test.net
so reading mail from roundcube give me only emty mailboxes
i use fetchmail on 6.8, where there was the General Tab to disable fetchmail,
with getmail ther is no such option, so at the end of restore all the
account in getmail was fully enabled. But i wanted to check if the restore was all good before
re-enable getmail… in short: i miss an option to quickly disable getmail…
i hope to have some time soon to retest well the procedure