Hi List,
we're currently running OpenLDAP 2.3.34 with BDB 4.5.20p2 for the backend in production (Solaris 8, 2 million reads per day). This combination has run fine and stable for almost a year. Apart from syncrepl we're not using any special features/overlays.
Now the platform to which that OpenLDAP setup belongs is rebuilt (Solaris 10) and I have an opportunity to carry out some lifecycle but wonder if I should remain at 2.3.34 or upgrade to 2.3.41 or even 2.4.9.
A pro would defnitely be to reach a later OpenLDAP version without having to do the upgrade with the pressure of a productive environment. The con which makes me hesitate is that it's currently running very well - and, never change a winning team...
How would you proceed in that situation and why ?
Thanks for your thoughts
Christoph
On Sun, May 18, 2008 at 3:05 PM, openldap.lists@frei-family.ch wrote:
How would you proceed in that situation and why ?
Running exclusively on 2.3 on FreeBSD, my approach would be to rebuild the boxes with 2.3 series for the master and build the replicas on 2.4 for testing. Since there are several schema changes between the two versions, it could be a good idea to test this first.
2.4 had some quite good publicity and should definitely considered but I am not sure I'd be trustful enough to run the master on it yet. Again, not having used 2.4 apart from a failed migration, I don't know a lot about it but my approach is that it is always easier to migrate one server later than 20.
Steph
--On Tuesday, May 20, 2008 2:42 PM +0100 FRLinux frlinux@gmail.com wrote:
On Sun, May 18, 2008 at 3:05 PM, openldap.lists@frei-family.ch wrote:
How would you proceed in that situation and why ?
Running exclusively on 2.3 on FreeBSD, my approach would be to rebuild the boxes with 2.3 series for the master and build the replicas on 2.4 for testing. Since there are several schema changes between the two versions, it could be a good idea to test this first.
2.4 had some quite good publicity and should definitely considered but I am not sure I'd be trustful enough to run the master on it yet. Again, not having used 2.4 apart from a failed migration, I don't know a lot about it but my approach is that it is always easier to migrate one server later than 20.
I'd wait for 2.4.10 before doing any migration.
I will also note that patch level releases are generally safe to move from (i.e., 2.3.34->2.3.42 (coming soon)).
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
On Sun, 18 May 2008, openldap.lists@frei-family.ch wrote:
Now the platform to which that OpenLDAP setup belongs is rebuilt (Solaris 10) and I have an opportunity to carry out some lifecycle but wonder if I should remain at 2.3.34 or upgrade to 2.3.41 or even 2.4.9.
Look at the list of bugs that were fixed between 2.3.34 and 2.3.41, and ask yourself whether you can live with them.
Dave Horsfall wrote:
On Sun, 18 May 2008, openldap.lists@frei-family.ch wrote:
Now the platform to which that OpenLDAP setup belongs is rebuilt (Solaris 10) and I have an opportunity to carry out some lifecycle but wonder if I should remain at 2.3.34 or upgrade to 2.3.41 or even 2.4.9.
Look at the list of bugs that were fixed between 2.3.34 and 2.3.41,
As stated by Quanah 2.3.42 is ready for release. So the list is some items longer now.
At the moment I'd only consider migrating to 2.4.x for production if new features are needed. Some tweaking of slapd.conf might be required during migration.
Ciao, Michael.
On Wed, 21 May 2008, Michael Ströder wrote:
At the moment I'd only consider migrating to 2.4.x for production if new features are needed. Some tweaking of slapd.conf might be required during migration.
Agreed; we run 2.4 clients because of a timeout that we needed, but the servers are still 2.3. The installation method is...interesting...
Dave Horsfall wrote:
On Wed, 21 May 2008, Michael Ströder wrote:
At the moment I'd only consider migrating to 2.4.x for production if new features are needed. Some tweaking of slapd.conf might be required during migration.
Agreed; we run 2.4 clients because of a timeout that we needed, but the servers are still 2.3. The installation method is...interesting...
Care to expand in "interesting"?
On Mon, 26 May 2008, Gavin Henry wrote:
Agreed; we run 2.4 clients because of a timeout that we needed, but the servers are still 2.3. The installation method is...interesting...
Care to expand in "interesting"?
The 2.4 client installs into its own path, which comes ahead of /usr/local and so on; the 2.3 server installs into the default location. The tricky bit is that the client is part of our source control and distribution procedure (not to mention getting the shared libraries to be recognised; FreeBSD 4 and 6/7 do it in different ways, and Ubuntu does it in yet another way).
The idea is to protect us from an unexpected 2.3 client getting installed as part of a requirement of some other package.
When 2.4 gets marked as STABLE then I'll move to it and incorporate it under our scheme as well.
-- Dave
<quote who="Dave Horsfall">
On Mon, 26 May 2008, Gavin Henry wrote:
Agreed; we run 2.4 clients because of a timeout that we needed, but the servers are still 2.3. The installation method is...interesting...
Care to expand in "interesting"?
The 2.4 client installs into its own path, which comes ahead of /usr/local and so on; the 2.3 server installs into the default location. The tricky bit is that the client is part of our source control and distribution procedure (not to mention getting the shared libraries to be recognised; FreeBSD 4 and 6/7 do it in different ways, and Ubuntu does it in yet another way).
The idea is to protect us from an unexpected 2.3 client getting installed as part of a requirement of some other package.
When 2.4 gets marked as STABLE then I'll move to it and incorporate it under our scheme as well.
Ah, ok. Understood. Can't you manage package reqs/overrides with FreeBSD pkg manager? Anyway, a bit OT now.
openldap-software@openldap.org
-
Dave Horsfall -
FRLinux -
Gavin Henry -
Gavin Henry -
Michael Ströder -
openldap.lists＠frei-family.ch -
Quanah Gibson-Mount