Project Definition
Name
OpenLDAP Upgrade to 2.1
Project Description
Upgrade the version of OpenLDAP running on the ldap.uvm.edu servers to 2.1.x (whatever x is stable) and upgrade the version of RedHat running on the servers to RedHat 9.
Statement of the Problem to be Solved
OpenLDAP 2.0.27 does not work with our calendar product and does not allow for dumping the backend database(s) while the server is actually running.
The LDBM backend also has a significant performance problem because it has a single massive lock that serializes ALL access to the backend database. Therefore, while multiple queries can take place at the same time, a modification must wait for all queries to finish and any queries that come in after the modification request must wait for the modification request to complete.
Sponsor
Computing and Information Technology (CIT)
Costs (one-time)
There is the possibility that we will need to upgrade the existing servers to efficiently run the new backend (BDB). If we have to do that, the expected charges would be:
| Qty | Description | Each | Total |
|---|---|---|---|
| 2 | IBM xSeries x345 | $6,750 | $13,500 |
| 4 | Kingston KTM5037/2G Memory | $786 | $3,144 |
| Total Cost | $16,644 |
Costs (on-going)
Maintenance costs on the machines if purchased.
Benefits
Upgrading to v2.1 of OpenLDAP will get us to the most current version which is receiving the most work.
The locking in the BDB backend is at the entry level instead of locking the entire backend database, this will allow updates to be performed faster, as well as not locking out queries (searches) while updates are being performed.
Dependencies
Performing this project will allow us to move forward with retiring the LDAP server that is dedicated to the UVM calendar server.
Upgrading to using the BDB backend will allow for the development of a live update procedure that doesn't shut down the server every night to install the new database after applying the changes from the authoritative feeds (Banner, HRS, and [hopefully] CatCard).
There is a concern that the current method of updating the LDAP directory by doing a complete replacement of the backend database will not work in OpenLDAP 2.1 because of the new UUID attributes. If that is the case, then this project will have to go on hold until the project to set up live updates is working.
Last modified May 21 2003 12:18 PM