Changes

Jump to navigation Jump to search
241 bytes added ,  22:08, 3 October 2016
Line 10: Line 10:  
=Overview and Objectives=
 
=Overview and Objectives=
   −
The primary objective of this effort is to create Active Directory support on SME 9+ with a focus on simplicity and easy in integration, as is done on many of the other sub-systems on SME Server.  Other distributions with Samba 4 support take the approach of providing a fairly complex front end to Samba 4 with many configuration parameters and options.  Our approach for Samba 4 is to stream line implementation to provide a straight forward and simple set of UI parameters for the administrator to deploy Active Directory in a configuration that will work in most deployments.  Support for the full array of Samba 4 options is provided under the hood in SME Server, but will be available primary from the console.  The SME Server community may decide to create an Advanced Samba server-manager panel to control and configure some of the more advanced features available in Samba 4, but the Core SME Server deployment of Active Directory will remain focused on simplicity.  
+
The primary objective of this effort is to create Active Directory support on SME 9+ with a focus on simplicity and easy integration, as is done on many of the other sub-systems on SME Server.  Other distributions with Samba 4 support take the approach of providing a fairly complex front end to Samba 4 with many configuration parameters and options.  Our approach for Samba 4 is to stream line implementation to provide a straight forward and simple set of UI parameters for the administrator to deploy Active Directory in a configuration that will work in most deployments.  Support for the full array of Samba 4 options is provided under the hood in SME Server, but will be available primary from the console.  The SME Server community may decide to create an Advanced Samba server-manager panel to control and configure some of the more advanced features available in Samba 4, but the Core SME Server deployment of Active Directory will remain focused on simplicity.  
    
Deployment of Samba 4 on SME Server means that many of the authentication mechanisms on SME Server need to change to integrate with Active Directory, therefore this development effort is quite far reaching.
 
Deployment of Samba 4 on SME Server means that many of the authentication mechanisms on SME Server need to change to integrate with Active Directory, therefore this development effort is quite far reaching.
Line 18: Line 18:  
=Current Status=
 
=Current Status=
   −
'''Current Release:'''  Alpha 6
+
'''Current Release:'''  Alpha 7
   −
Samba 4 on SME Server will be provided by way of the package smeserver-samba, which will upgrade and obsolete e-smith-samba.  The current release of Samba 4 on SME Server is available here:  [http://www.leiengineering.com/repository/smeserver/Packages/SME_Server_Samba4/ SME Server Samba 4 Packages]
+
Samba 4 on SME Server will be provided by way of the package smeserver-samba, which will upgrade and obsolete e-smith-samba.  The current release of Samba 4 on SME Server is available here:  [http://www.leiengineering.com/repository/smeserver/Packages/Samba4_Alpha7/ SME Server Samba 4 Packages]
    
These packages are currently not provided by the Koozali buildsys because there is still a fair bit of work to do to integrate this code with existing SME services.  Since Samba 4 on SME Server includes many other sub-systems, inclusion of the Samba 4 code is not being including in current development streams until the code is closer to release so as not to hold up other development activities.  However, this code is available in CVS.
 
These packages are currently not provided by the Koozali buildsys because there is still a fair bit of work to do to integrate this code with existing SME services.  Since Samba 4 on SME Server includes many other sub-systems, inclusion of the Samba 4 code is not being including in current development streams until the code is closer to release so as not to hold up other development activities.  However, this code is available in CVS.
 +
<br>
    
=Samba 4 Packages=
 
=Samba 4 Packages=
Line 33: Line 34:  
=Installation=
 
=Installation=
   −
RPMs for this release can be found here:  [https://www.leiengineering.com/repository/smeserver/Packages/Samba4_Alpha6/ SME Server Samba 4 Packages]
+
RPMs for this release can be found here:  [https://www.leiengineering.com/repository/smeserver/Packages/Samba4_Alpha7/ SME Server Samba 4 Packages]
    
Install Instructions:
 
Install Instructions:
Line 45: Line 46:     
=Change Log / Release Notes=
 
=Change Log / Release Notes=
 +
==Alpha 7==
 +
* Implementation of Samba 4 on SME 10.
 +
* Drop bootstrap-console patch for e-smith-base for provisioning samba 4 from the console.  We'll add this back in later
 +
 
==Alpha 6==
 
==Alpha 6==
 
* Final alpha on SME 9.  Going forward, this code will be moved to the SME 10 alpha release for ongoing development and testing
 
* Final alpha on SME 9.  Going forward, this code will be moved to the SME 10 alpha release for ongoing development and testing
Line 58: Line 63:  
* Update user-modify, user-delete, user-lock events for AD integration
 
* Update user-modify, user-delete, user-lock events for AD integration
 
* Create user-AD-enable and user-AD-disable actions
 
* Create user-AD-enable and user-AD-disable actions
* Extensive clean-up of smb.conf fragments now that we have a working Samba 4 deployment, including default configuration dbase parameters
+
* Extensive clean-up of smb.conf fragments now that we have a working Samba 4 deployment, including default configuration dbase parameters.  This clean-up and enhancement results in a very clean smb.conf file
 
* Update qmail and .qmail template fragments and configuration to pull user data from the Active Directory.  Spam and filtering fragments have been excluded because we have not yet decided how to handle these configuration in the Active Directory
 
* Update qmail and .qmail template fragments and configuration to pull user data from the Active Directory.  Spam and filtering fragments have been excluded because we have not yet decided how to handle these configuration in the Active Directory
 
* Further enhancement and refinement to esmith::AD
 
* Further enhancement and refinement to esmith::AD
board, director
297

edits

Navigation menu