OpenLDAP 2.5 packaging status

[Quanah Gibson-Mount]

--On Sunday, May 30, 2021 12:06 PM -0700 Ryan Tandy <ryan at nardis.ca> wrote:

> These are the major upgrade issues that need to be handled:
>
> - older installs still running the bdb, hdb, or shell backends: need to
> convert bdb/hdb to mdb on upgrade, don't know what to do with shell.
> Migration to mdb needs some heuristics to guess an appropriate   mapsize.

In my experience of migrations, an MDB database has always been smaller 
than the equivalent size of the BDB based database, excluding the __XX map 
files.  I.e., the size of *.bdb should be larger than the result mdb db. 
Of course, the point of the mapsize it to set it very large, not try and 
guess some value close to what the DB size would be.  Generally on other 
migrations I've gone with at least the amount of freespace on the 
partition, if not the partition size.

I'd also note that 2.5 MDB databases are not compatible with 2.4 databases, 
so they still require an export/import on migration.  Guessing you've done 
that, but didn't see that listed.

> - installs with the ppolicy schema loaded: it is now compiled into the
> ppolicy module instead of being a configured schema, so the old schema
> needs to be removed from the config on upgrade, otherwise the
> compiled-in and configured schemas could conflict

Should be able to exclude it as part of a slapcat of the config database? 
(See the -a option).

--Quanah

--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>