ispman/docs UPGRADING,1.3,1.4

Update of /cvsroot/ispman/ispman/docs
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv19447/docs

Modified Files:
	UPGRADING 
Log Message:
changed upgrade instructions

Index: UPGRADING
===================================================================
RCS file: /cvsroot/ispman/ispman/docs/UPGRADING,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- UPGRADING	5 Jun 2004 12:45:19 -0000	1.3
+++ UPGRADING	20 Jun 2004 17:30:47 -0000	1.4
@@ -1,93 +1,128 @@
-These instructions are for people upgrading from 0.8.5 to 0.9
+Upgrade Instructions
+====================
 
-*) Backup everything
+Note:   Depending on which ispman version you are running, the
+        following may work more or less smooth for you.
+        If you encounter any trouble, please report any errors together with
+        as much information you have to
+        ispman-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, so we can improve the
+        upgrade process.
 
-*) Make sure that you have backed up everything
 
-*) If possible try this install on a separate machine, althoug
-   I had always only production machines to upgrade
+Disclaimer:
+Upgrading is a delicate process which can harm your data. Be sure to
+have a recent backup to recover your installation. If possible try
+upgrading on a testsystem first.
 
-*) type ./configure
 
-*) type make ispman
+Prepare for upgrade
+===================
 
-*) now have a look at the generated ldif files in 
-   tmp/ldif/*.ldif
-   They look ok?
+Do the normal preparation after you acquired the update via tarball or
+cvs (see INSTALL for more info):
 
+So this will be something like
+-> ./configure
+-> make ispman
 
-*)  Did you backup your LDAP data?
-    If not. Do it now.
-    stop the ldapserver.
-    run 
-    slapcat > ldap.backup.ldif  (this is your data from the server)
-    also backup the directory where your ldapfiles are.
-    For example.
-    tar -cvf ldap.bakup.tar /etc/openldap /var/lib/ldap
+This will generate the following files among other things:
 
+tmp/conf/ispman.conf:
+        Your new ispman.conf based on your existing config data.
 
-*) see the generated slapd.conf file in tmp/conf
-   If you want, copy this file to your slapd.conf or edit 
-   your slapd.conf accordingly.
+tmp/ldif/ispman.ldif:
+        This is the basic LDAP DIT for ispman.
+        Though, most of this should already exist in your LDAP, it may
+        contain additional entries (e.g. confVars) that are not
+        present yet.
 
-*) Make sure that your ldap.conf looks like tmp/conf/ldap.conf or 
-    copy it to your ldap.conf
+tmp/conf/schema/*:
+        Updated schema files.
 
-*)  copy the 
-    tmp/schema/dnszone.schema, 
-    tmp/conf/schema/proftpd.schema  and 
-    tmp/schema/ispman.schema 
-    
-    to 
-    
-    where you have rest of your schemas and include them in your slapd.conf
+tmp/conf/ldap.conf:
+tmp/conf/sldap.conf:
+        example config files for openldap
 
-    You need the following schemas
-    core.schema
-    cosine.schema
-    nis.schema
-    misc.schema
-    inetorgperson.schema
-    dnszone.schema
-    proftpd.schema
-    ispman.schema
 
-*)  Once your slapd.conf is ok and all schema's are included, restart your 
-    ldap server. Make sure that the ldap server started ok. 
-    If it doesnt start or give errors, try to see what is wrong and don't continue 
-    unless you fix the problems.
 
+Migrate your LDAP data
+======================
+Dump your ispman data to some temporary LDIF file:
+e.g. -> /opt/ispman/bin/ispman.ldifdump -f /tmp/myispman.ldif
 
-*)  Now load the newly generate LDIF file to your server.
-    you can use the scripts/upgrade_from_ldif.pl script.
-    This will only add the branches are records that are missing.
-    It will not overwrite or remove anything.
-    
-    run the following command.
-    scripts/upgrade_from_ldif.pl tmp/ldif/ispman.ldif     
-    
-    This sould give you tons or "Entry already exists" errors but you may ignore them
-    
+Now use "ldifupdate" to check and migrate your ispman data.
+-> ./scripts/ldifupdate -i /tmp/myispman.ldif -o /tmp/changes.ldif -m modify
 
-    
-*)   run 
-     make install_ispman_common and 
-     make install_ispman_web
-     This will copy the data
-     
-*)   Note: The ISPMan Admin interface (the interface that you have had been using with 0.8.x) 
-     does not require mod_ldap any more.
-     Instead ISPMan does its own authentification and allow you to logout without closing the 
-     browser session. So if you have any authentification rules set for the ispman directory, 
-     please remove them.
-     
-*)   Read the rest of the Quickstart.txt for more info.
-     Read carefully the section about Control-panel.
-     
+This reads your data from the generated LDIF (myispman.ldif) and
+checks it against some migration/validity rules.
+You will be informed about any necessary changes, which will be
+written to a new file (changes.ldif). 
+When using "-m modify" this file will only contain the changes, which
+is probably what you want.
 
+In case ldifupdate warns you about some missing defaults, you need to
+adjust some defaults at the beginning of that script.
+-> vi ./scripts/ldifupdate
+
+
+
+Apply config/schema changes
+===========================
+Compare your openldap configs (slapd.conf, ldap.conf) against the new
+generated versions.
+Apply any necessary changes introduced by the new files.
+
+Copy the new schema files
+        tmp/schema/dnszone.schema,
+        tmp/conf/schema/proftpd.schema
+        tmp/schema/ispman.schema 
+to your openldap schema directory.
+
+Check that your slapd.conf contains at least the following schemas:
+        core.schema
+        cosine.schema
+        nis.schema
+        misc.schema
+        inetorgperson.schema
+        dnszone.schema
+        proftpd.schema
+        ispman.schema
+
+
+Once your slapd.conf is ok and all schema's are included, restart your
+ldap server. Make sure that the ldap server started ok. If it doesn't
+start or give errors, try to see what is wrong and don't continue
+unless you fix the problems.
+
+
+
+Import new ISPMan data
+======================
+Now load the new LDIF files to your LDAP server.
+
+* use upgrade_from_ldif.pl script to load the generated ispman.ldif:
+-> scripts/upgrade_from_ldif.pl tmp/ldif/ispman.ldif 
+
+This will only add branches and records that are missing (no delete or
+overwrite), so just ignore any warnings about already existing
+entries.
+
+* apply the changes from ldifupdate (/tmp/changes.ldif from above)    
+-> ldapmodify -x -h <ldaphost> -D <binddn> -w <bindpw> -f /tmp/changes.ldif
+
+This is probably the most elegant way to do this, because it will just
+change what is needed. No big-time export/import.
+
+
+Install ISPMan update
+=====================
+Finish the update with the rest of the normal install procedure    
+-> make install_ispman_common
+-> make install_ispman_web
+
+
+For additional info read INSTALL
 
-     
-Read Quickstart.txt for more --
 
     
     



-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND