extended provision-backend

[Oliver Liebel]

hi andrew,

here are the improvements to provision/provision-backend
and all necessary diffs:

(first apologize that i have attached "normal" diffs,
but i still did not had the time, to get closer into the git-stuff.
please push the changes to the master.)



andrews patches:
- all integrated

slapd/slaptest:
- slaptest-path is not needed any more (slapd -Ttest is used instead)
and is therefore removed.
- slapd-path must be given when openldap-backend is chosen. is also used
for olc-conversion (see above)

running slapd-daemon:
- system is pre-checked if another instance of slapd is running on
system before starting it
- if no other slapd is running, slapdcommand_prov starts slapd (ldapi
only) for final provision
- after startup is verified, if slapd is up an listening on s4's ldapi_uri

help:
- complete slapd-commandline (to start slapd manual after final
provision is done) is stored
under paths.ldapdir/slapd_command_file.txt  (depending on setup type, it
includes real
ldap://fqhn if olc and/or mmr was chosen, so slapd can be run after
provision
just with copy an paste that string, only port must be set manually)
- extended help messages to make things more clear

after final provision finished:
- first is checked, if slapd is still running, listening to s4s ldapi_uri
- then slapd (with pid from paths.ldapdir/slapd.pid) will be terminated
(proper termination is re-checked)
- stored slapd-commandline is displayed to show the right syntax to
start slapd manually (except port )

howto:
- added a little howto (file: howto-ol-backend-s4.txt), including
all ol-configure-options and setup-types (static/olc, standalone/mmr)


todo:
- full merge of provision and provision-backend, maybe in this way:
with ol-backend, you only have to run (final) provision.
slapd-path and other ol-specific-parameters has to be given.
"backend-"prov is run first internally if any ol-param is given (slapd
started auto),
then "final-"prov (fully transparent to the user), after that slapd is
terminated.

but thats a lot more work, and the structure of provision.py maybe has
to be reorganized
in big parts. at the moment i dont have the time to, maybe in a few weeks.
but for now, it think the simplification of this setup-type is one step
forward on the road.


greetings,
oliver








-------------- next part --------------
A non-text attachment was scrubbed...
Name: provision.py.diff
Type: text/x-patch
Size: 13908 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20090805/aa210bf4/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: provision-backend.diff
Type: text/x-patch
Size: 2236 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20090805/aa210bf4/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Samba4.pm.diff
Type: text/x-patch
Size: 926 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20090805/aa210bf4/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: secrets_sasl_ldap.ldif.diff
Type: text/x-patch
Size: 256 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20090805/aa210bf4/attachment-0003.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: slapd.conf.diff
Type: text/x-patch
Size: 1666 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20090805/aa210bf4/attachment-0004.bin>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: howto-ol-backend-s4.txt
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20090805/aa210bf4/attachment.txt>