Migration from 2.3.1 to 2.4

[Jeroen van Meeuwen]

On Monday, September 17, 2012 09:57:03 PM Christian Tardif wrote:
> Interesting. For Kolab 3, I can't afford upgrading to a beta version, as
> this is a production server which needs to be up and running at all
> times (other than maintenance windows, though).

That is completely understandable, ...

> Regarding the upgrade path, the LDAP migration isn't documented at all.
> Nothing can be done, if no LDAP migration occur, isn't it?
> 

The people that write this documentation (i.e. yours sincerely) make up and 
test these procedures on their own systems.

I happen to be able to spawn VMs and provision them with demo data that allows 
me to go through some upgrade paces, but it only represents a feasible path 
for the one scenario.

You wouldn't be able to spawn a VM and see what, between ldapsearches against 
your Kolab 2.3 server, and ldapadds against your Kolab 3.0 server, would need 
to happen to migrate your LDAP data, would you?

It'd be much appreciated if some people could attempt such a thing and see 
what they have to do to get it all in good shape.

For the sake of argument, I've attached a little script I've used to test 
upgrades with.

Kind regards,

Jeroen van Meeuwen

--
Systems Architect

Kolab Systems AG
Zürich, Switzerland

e: vanmeeuwen at kolabsys.com
t: +41 43 501 66 91
m: +44 74 2516 3817
w: http://kolabsys.com

pgp: 0x9342BF08
-------------- next part --------------
#!/bin/bash

kolab2host="kolab2.example.org"
bind2dn="cn=manager,cn=internal,dc=example,dc=org"
bind2pw="somepassword"

kolab3host="192.168.122.13"
bind3dn="cn=Directory Manager"
bind3pw="somepassword"

resetpw="somepassword"

ldap_opts="-x -h ${kolab2host} -D '${bind2dn}' -w '${bind2pw}' -b dc=example,dc=org -s one"
ldap_sopts="${ldap_opts} -LLL (objectclass=kolabinetorgperson)"

ldapsearch ${ldap_sopts} | \
    sed \
        -r \
        -e 's/uid=(.*)@example\.org,/uid=\1,/g' \
        -e 's/uid=([^,]*),dc=example,dc=org/uid=\1,ou=People,dc=example,dc=org/g' \
        -e 's/^uid: (.*)@example\.org/uid: \1/g' \
        -e '/^kolabHomeServer:/d' \
        -e '/^cyrus-userquota:/d' \
        -e '/^kolabFreeBusyFuture:/d' \
        -e '/^c:/d' \
        -e "s/^userPassword.*/userPassword: ${resetpw}/g" | \
            ldapadd -x -h ${kolab3host} -D "${bind3dn}" -w "${bind3pw}" -c
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/users/attachments/20120918/4adf7f0c/attachment.sig>