Univention Bugzilla – Bug 32309
Integrate Samba4/Samba3 as system component into App Center
Last modified: 2013-11-19 06:43:07 CET
Via Bug 32301, UCS system components (nagios, dhcp server etc.) will be integrated in the App Center. For Samba4/Samba3, two additional points need to be considered:
(a) As Samba4 needs to be installed along with the S4 connector on a master, can the package dependencies modified in such a way that the S4 connector is automatically installed on a master and not on a slave? One possibility could be to defined a dependency to "s4-connector | slave | member".
(b) As apps will be easily installed and removed, either we need to support the complete removal of Samba4 from a UCS system or we need to block its deinstallation in the App Center.
(a) univention-s4-connector can be installed on several machines. Without special UCR modifications (UCS@school) only the first installation becomes active.
(b) Samba4 removal would require support for a preceeding DC "demote" in a univention-samba4 unjoin script to cleanly remove it from the DRS replication topology. S4-Connector removal would additionally require a mechanism to activate the service on a different samba4 DC in the domain. I guess the admin would need to be asked to select a new S4 Connector provider.
(In reply to Arvid Requate from comment #1)
> (a) univention-s4-connector can be installed on several machines. Without
> special UCR modifications (UCS@school) only the first installation becomes
Yes, but the connector needs cn=admin access at least in a normal setup.
I've removed the dependencies of the univention-samba* packages from the packages_list.py. Thus the autoremove during the samba app center uninstallation should remove the dependencies.
(In reply to Stefan Gohmann from comment #3)
> I've removed the dependencies of the univention-samba* packages from the
> packages_list.py. Thus the autoremove during the samba app center
> uninstallation should remove the dependencies.
That works so far.
I've added README_UNINSTALL files for samba4 and samba4-slave. The files contain a link to the online documentation. That link must be changed to the final docu link. Wait for Bug #32503.
I've changed the s4 connector join script. Before the connector autostart variable was set with ?yes, now it is set with =yes. Of course, only if no other connector host is available.
Ready for the QA.
* What differentiates samba4-slave-4.1 from samba4-4.1, Can't we install univention-s4-connector on a slave?
* For my taste the deinstallation-warning is too soft. At least it passes my "yeah, whatever" filter..
(In reply to Arvid Requate from comment #7)
> * What differentiates samba4-slave-4.1 from samba4-4.1, Can't we install
> univention-s4-connector on a slave?
I don't think we should install a service on a DC slave which is unable to run successfully on that host. What is the problem to have two apps?
Wait until Arvid is back.
The samba packages in univention-installer/installer/package_list.py were simplified during this bug. This reverted changes from Bug#30982. I am not sure if this is important. I just thought I let you know...
* Installation and Deinstallation of Samba4 works on Master and Slave
* Installation and Deinstallation of Samba3 works on Master and Slave
* Changelog Ok.
UCS 3.2 has been released:
If this error occurs again, please use "Clone This Bug".