Hello,
We are running a (small) number of OpenLDAP instances with v2.4.58.
There is a single master and 4 syncrepl consumers (all on CentOS 7 boxes), all running with back-mdb.
We are planning our migration from 2.4 to 2.5.x
My question: Would it be OK if we migrate our master server to 2.5.latest, and leave consumers to 2.4.58 for a while? Would any implications be expected?
Or it is strongly suggested to shutdown all the servers, migrate to 2.5 in parallel and then restart?
(Obviously, the latter approach is more demanding in admin and maintenance planning.)
Finally: Is there a script or other way to check possible config incompatibilities with 2.5.x (in order to avoid surprises)?
(Note: Our master uses cn=config, while consumers still use slapd.conf.)
I will appreciate your advice.
Thanks, Nick.
--On Wednesday, June 2, 2021 12:23 PM +0300 Nick Milas nick@eurobjects.com wrote:
Hello,
We are running a (small) number of OpenLDAP instances with v2.4.58.
There is a single master and 4 syncrepl consumers (all on CentOS 7 boxes), all running with back-mdb.
We are planning our migration from 2.4 to 2.5.x
My question: Would it be OK if we migrate our master server to 2.5.latest, and leave consumers to 2.4.58 for a while? Would any implications be expected?
I would wait for 2.5.5. Other than that, replication is a protocol level bit, so it works between 2.4 and 2.5 w/o issue.
Finally: Is there a script or other way to check possible config incompatibilities with 2.5.x (in order to avoid surprises)?
Have you read the upgrade appendix of the admin guide?
https://www.openldap.org/doc/admin25/appendix-upgrading.html
Regards, Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
On Wed, Jun 02, 2021 at 11:23:00 +0300, Nick Milas wrote:
There is a single master and 4 syncrepl consumers (all on CentOS 7 boxes), all running with back-mdb.
We are planning our migration from 2.4 to 2.5.x
My question: Would it be OK if we migrate our master server to 2.5.latest, and leave consumers to 2.4.58 for a while? Would any implications be expected?
What we're planning to do is not to upgrade in-place, but to add new servers with OpenLDAP 2.5, let them replicate from the current 2.4 environment, and move over service IP's one by one. Eventually we'll make one of the 2.5's the active master (also via a service IP), and decomission the 2.4 environment.
(We'll be moving from CentOS 6 to 7 at the same time, but even without the OS factor, I'd rather migrate than upgrade in-place.)
Geert
openldap-technical@openldap.org
-
Geert Hendrickx -
Nick Milas -
Quanah Gibson-Mount