What to expect from alpha2?
This release was aimed at replicating all the functionality of 6.7, closely mimicking the behaviour of all features, on a CentOS 7 base.
So I expect that alpha2 will behave well, hopefully a bit better of 6.7 because of the newer base system. And because we smoothed some edges while adapting configurations. As an example, in 6.7, the Services panel reported lsm as stopped with a red color when no multiwan providers were configured, while in 7a2 it’s correctly reported in black color (thanks to systemd).
Also, while adapting configuration templates to newer software in 7 (i.e. http, ssh, etc), we reverted to CentOS defaults for as many variables as possibile. So v7a2 behaviour should be compared to centos 7 more easily.
edit; I installed oC module without installing the file server module so in this case the user profile assumes the file server is installed, therefore Shared Folders (Samba) is preselected though it doesn’t exist.
Feb 12 14:27:53 server89 esmith::event[7598]: Action: /etc/e-smith/events/user-create/S04user-create-unix SUCCESS [0.473427]
Feb 12 14:27:53 server89 esmith::event[7598]: expanding /etc/postfix/aliases
Feb 12 14:27:53 server89 esmith::event[7598]: expanding /etc/postfix/internal_access
Feb 12 14:27:53 server89 esmith::event[7598]: expanding /etc/postfix/virtual
Feb 12 14:27:53 server89 esmith::event[7598]: expanding /etc/postfix/vmailbox
Feb 12 14:27:53 server89 esmith::event[7598]: Action: /etc/e-smith/events/actions/generic_template_expand SUCCESS [0.091748]
Feb 12 14:27:53 server89 esmith::event[7598]: Action: /etc/e-smith/events/user-create/S20nethserver-directory-organization-modify SUCCESS [0.114821]
Feb 12 14:27:54 server89 esmith::event[7598]: Mapping group service failed with NT_STATUS_GROUP_EXISTS
Feb 12 14:27:54 server89 esmith::event[7598]: Failed to map user's unix group `service` in SAM database at /etc/e-smith/events/user-create/S20nethserver-samba-user-create line 85.
Feb 12 14:27:54 server89 esmith::event[7598]: Updated 'user must change password at next logon' for SERVER89\service to yes
Feb 12 14:27:54 server89 esmith::event[7598]: Action: /etc/e-smith/events/user-create/S20nethserver-samba-user-create **FAILED**: 1 [0.488652]
Feb 12 14:27:54 server89 esmith::event[7598]: Action: /etc/e-smith/events/user-create/S25count-active-user-accounts SUCCESS [0.038792]
Feb 12 14:27:54 server89 esmith::event[7598]: Action: /etc/e-smith/events/user-create/S25nethserver-directory-user-modify SUCCESS [0.125924]
Feb 12 14:27:54 server89 esmith::event[7598]: Action: /etc/e-smith/events/user-create/S25nethserver-samba-profile-create SUCCESS [0.052811]
Feb 12 14:27:54 server89 esmith::event[7598]: Action: /etc/e-smith/events/user-create/S30nethserver-mail-account-update SUCCESS [0.175465]
Feb 12 14:27:54 server89 esmith::event[7598]: Action: /etc/e-smith/events/user-create/S30nethserver-mail-postmap-update SUCCESS [0.12345]
Feb 12 14:27:54 server89 esmith::event[7598]: Action: /etc/e-smith/events/user-create/S30nethserver-samba-user-modify SUCCESS [0.11838]
Feb 12 14:27:55 server89 esmith::event[7598]: Action: /etc/e-smith/events/user-create/S40nethserver-directory-password-policy SUCCESS [0.16347]
Feb 12 14:27:55 server89 esmith::event[7598]: Action: /etc/e-smith/events/user-create/S85user-group-modify SUCCESS [0.068672]
Feb 12 14:27:55 server89 esmith::event[7598]: Event: user-create FAILED
Feb 12 14:27:55 server89 httpd: **[ERROR]** Nethgui\System\NethPlatform: process on queue `post-process` exited with code 1: /usr/libexec/nethserver/ptrack -j -s '/var/run/ptrack/acceb66a70616da4bff032eebab14af9.sock' -d '/var/spool/ptrack/8f662105e997a481.dump' -- /usr/bin/sudo -n /sbin/e-smith/signal-event 'user-create' 'service'
ownCloud
Try to access/edit files using ownCloud web interface
Configure a client on a desktop machine and configure the client, make sure files are in sync
both done and working…
… thought… would it be easier on new users to use the server ip instead of hostname/domain in the link on the Application page in the gui? Because the default server name and domain sure isn’t going to work in any browser but a local one, and there is no local one.
Or if there was a check for anything other than the default domain, then we could use that instead.
Configuration backup
Configure a new system with additional modules and execute the configuration backup. Try to restore the backup into another system.
Installed Backup, ownCloud and Email, setup backup pointing to a cifs client, setup user, setup oC client, verified sync, wiped, reinstalled NS7a2, followed the doc http://docs.nethserver.org/en/latest/backup.html#disaster-recovery
initiated Restore Backup from gui Backup (configuration), received error as follows;
Note; the config backup appears successful, from a clean install, all the previous settings were returned, even the backup email notification settings I left default when I setup backup data for the restoration source, once the oC desktop client was restarted, after entering the original user password it resynced fine.
As far as I know, the nameserver option in the kickstart will write the DNS address inside system configuration files.
These files are than used for NameServers property under the dns key.