[openchange][devel] Simplifying the OpenChange setup process

Tue Apr 1 22:44:41 MDT 2014

Yes please, because Samba and Openchange on Zentyal Server 3.4 is not
working out for me at the moment. Samba crashes and Openchange stops
working.

Maybe too much integration with other things... good idea to just to have
samba and openchange by themselves on one box

Good luck and keep the install documentation updated.

Ray

-----Original Message-----
From: devel [mailto:devel-bounces at lists.openchange.org] On Behalf Of Jelmer
Vernooij
Sent: 01 April 2014 07:31 PM
To: devel at lists.openchange.org
Cc: samba-technical at samba.org
Subject: [openchange][devel] Simplifying the OpenChange setup process

At the moment, the process for setting up OpenChange on a new machine is
fairly involved. It requires building and installing the software, and then
various provisioning steps:

 1) Provisioning Samba
 2) Provisioning the OpenChange integration in Samba/AD (schemas, etc)
 3) Editing smb.conf to add the various OpenChange services
 4) Provisioning the OpenChange database
 5) Possibly tweaking the ocsmanager settings, and setting up proxies  for
ocsmanager/tcp_proxy

I'm working on two changes that should help simplify this process, combining
steps 1 through 4:

loadparm_context creation hooks
===============================

loadparm_init() creates a loadparm context and then sets a whole heap of
defaults. These defaults can then be overwritten when a smb.conf file is
loaded that has explicit settings.

I'd like to allow modules to register a hook that gets run at the end of
this function, so they can tweak the default values in lp_ctx.
OpenChange could use this to add its own services to the "server services"
list, something that currently requires manual editing of smb.conf by the
user.

Users will still be able to disable openchange by explicitly setting a
'server services' line, just as they are able to set it at the moment.

hooks for setting up additional schemas in 'samba-tool domain provision'
========================================================================

It should be possible to extend the functionality of the provisioning code
in Samba. In particular I'm thinking of the ability to setup more schemas.

This can be done by allowing a Python file that provides a certain interface
to be dropped in a magic directory somewhere. OpenChange can then install
such a file.

Thoughts?

Jelmer
_______________________________________________
devel mailing list
devel at lists.openchange.org
http://mailman.openchange.org/listinfo/devel

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>email-banner</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
</head>
<body bgcolor="#FFFFFF" leftmargin="0" topmargin="0" marginwidth="0" marginheight="0">
</br>
<a href="http://www.joburgtheatre.com"><img src="http://www.showbusiness.co.za/emailbanner/banner.jpg" width="660" height="165" />
<!-- ImageReady Slices (banner4web.jpg) --><!-- End ImageReady Slices --></a></br>

</body>

</html>