i understand that ldap is a protocol but it occurred to me that a database change (where tables and the like might be different and slapd version dependent) might need to be a sitewide thing, not a server by server thing (meaning the 2.4 servers, once the "database" is mirrored from the master server, might not understand the new format?). ---
Regards,
Kevin Martin
On Thu, Aug 19, 2021 at 12:31 PM Quanah Gibson-Mount quanah@symas.com wrote:
--On Thursday, August 19, 2021 1:23 PM -0500 kevin martin ktmdms@gmail.com wrote:
if I have multiple slapd servers running 2.4 can I update my master server to 2.5 with the new format and will the 2.4 mirrors be able to handle the new format or is it an all or nothing upgrade of all servers at once?
LDAP is a protocol, the internal change to the MDB database structure is immaterial.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
--On Thursday, August 19, 2021 1:35 PM -0500 kevin martin ktmdms@gmail.com wrote:
i understand that ldap is a protocol but it occurred to me that a database change (where tables and the like might be different and slapd version dependent) might need to be a sitewide thing, not a server by server thing (meaning the 2.4 servers, once the "database" is mirrored from the master server, might not understand the new format?).
The only limitation would be that you could not mdb_copy a 2.5 database and run that under a 2.4 slapd. Since it's purely internal, the replication protocol has no "knowledge" of it, and it would not appear in an LDIF created by slapcat.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
Hi!
It might get interesting if you sync cn=config, however.
Regards, Ulrich
kevin martin ktmdms@gmail.com schrieb am 19.08.2021 um 19:35 in Nachricht
CACyJYa0osTHiWKR8vM7H_0okE+A-WpL14fg56g3uZ6OCAmHbuw@mail.gmail.com:
i understand that ldap is a protocol but it occurred to me that a database change (where tables and the like might be different and slapd version dependent) might need to be a sitewide thing, not a server by server thing (meaning the 2.4 servers, once the "database" is mirrored from the master server, might not understand the new format?).
Regards,
Kevin Martin
On Thu, Aug 19, 2021 at 12:31 PM Quanah Gibson-Mount quanah@symas.com wrote:
--On Thursday, August 19, 2021 1:23 PM -0500 kevin martin ktmdms@gmail.com wrote:
if I have multiple slapd servers running 2.4 can I update my master server to 2.5 with the new format and will the 2.4 mirrors be able to handle the new format or is it an all or nothing upgrade of all servers at once?
LDAP is a protocol, the internal change to the MDB database structure is immaterial.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
--On Friday, August 20, 2021 10:05 AM +0200 Ulrich Windl Ulrich.Windl@rz.uni-regensburg.de wrote:
Hi!
It might get interesting if you sync cn=config, however.
cn=config uses back-ldif not back-mdb, and even if it was using back-mdb, it still wouldn't matter for the internal format change to back-mdb.
I would also note that there are critical problems with cn=config replication in 2.4 so people shouldn't be doing that anyway. The issues we know of were fixed in 2.5, so that's the first release where I'd consider replication of cn=config.
However, there are likely incompatibilities between 2.4 and 2.5 for cn=config replication. The fact that 2.5's ppolicy no longer uses a schema file for example. But again, people should not be using cn=config replication in 2.4.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
openldap-technical@openldap.org
-
kevin martin -
Quanah Gibson-Mount -
Ulrich Windl