OpenDS 1.0 Milestone 1 has been promoted.

Opends LogoThe OpenDS project reached a new step towards the release of its final 1.0 release yesterday. After an intensive period of tests, the OpenDS 1.0.0-build012 has been promoted as OpenDS 1.0 Milestone 1.

OpenDS 1.0 Milestone 1 delivers a full LDAPv3 compliant server supporting many standard and work-in-progress extensions, with access controls, multi-master replication and much more. It has been intensively tested by a dedicated team. It is accompanied with a snapshot of the user documentation. You can read the release notes for additional details.

Now that OpenDS 1.0 Milestone 1 is done, we’re focusing our efforts on the last remaining features and on stressing the server for its reliability and stability. We’re aiming at releasing OpenDS 1.0 in May.

We’re also starting discussion on the roadmap and the features that the OpenDS community would like to see in OpenDS 2.0. If you have feedback or ideas, please join us on our next OpenDS monthly conference call on Tuesday March 4th 2008, 9m PST, 5pm GMT, 6pm CET (details have been posted on the OpenDS mailing lists). Or leave me a comment…

Technorati Tags: , , , ,

OpenDS 1.0.0-build012 is now available

We have just uploaded OpenDS 1.0.0-build012, built from revision 3883 of our source tree, to our promoted builds folder. The direct link to download the core server is:

The direct link to download the DSML gateway is:

We have also updated the archive that may be used to install OpenDS via Java Web Start. You may launch that using the URL, or visit for more information.

Detailed information about this build is available at

Beware of one limitation: Upgrade/revert can not be supported for this build due to a flag day introduced between build-011 and build-012.

Major changes incorporated since OpenDS 1.0.0-build011 include:

  • Revision 3818 (Issue #2825) — Fix an issue in which the dsconfig command output the incorrect information when listing properties in interactive mode.
  • Revision 3819 (Issue #2901) — Fix a compilation issue with
  • Revision 3820 (Issue #2894) — Fix an issue that caused disabling a privilege not to work correctly for unauthenticated clients.
  • Revision 3821 (Issue #2413) — Add the –certnickname option to the ldappasswordmodify command so that users can specify a certificate.
  • Revision 3824 (Issue #2902) — Fix an issue that caused the stop-ds -R command to restart the server with a client JVM.
  • Revision 3826 (Issue #2865) — Add a ds-cfg-key-wrapping-transformation property to enable providers that do not have the current default "RSA/ECB/OAEPWITHSHA-1ANDMGF1PADDING" to specify one in the configuration.
  • Revision 3828 (Issue #1459) — Fix an issue that was causing an error when replacing the userCertificate attribute.
  • Revision 3832 (Issue #2249) — Fix an issue that caused some attributes to be in pending mode after running setup with secure arguments.
  • Revision 3833 (Issue #2910) — Fix an issue that caused a Java exception when an incorrect admin DN was specified during the uninstall process.
  • Revision 3849 (Issue #2885) — Repair the window mechanism from a replication server to an LDAP server.
  • Revision 3851 (Issue #2931) — Ensure that nested groups are reloaded after an import.
  • Revision 3852 (Issue #2924) — Change the setup so that the root user password is no longer visible in the setup log.
  • Revision 3853 (Issue #2130) — Add support for internationalization of CLI usage.
  • Revision 3854 (Issue #2922) — Fix a problem that caused error messages from the setup command to return the incorrect property name.
  • Revision 3855 (Issue #2923) — Fix an issue that caused a null pointer exception if a null value was provided for the key store pin.
  • Revision 3859 (Issue #2919) — Fix a problem that caused the translation of version-related properties to generate an error.
  • Revision 3860 (Issue #2918) — Use standard output to display the usage and update the return codes of the status-panel command.
  • Revision 3863 (Issue #2925) — Relax the required status of the digest-uri directive to maintain compatibility/interoperability with legacy client implementations.
  • Revision 3867 (Issue #2921) — Ensure that CLI error messages retain the case of argument names as provided by the user.
  • Revision 3869 (Issue #2911) — Fix an issue that prevented the dsreplication command from clearing all the change logs.
  • Revision 3870 (Issue #2652) — Add support for the -t, –stopTime options in the stop-ds command so that the command can be executed as a task.
  • Revision 3873 (Issues #2813 and #2578) — Make DN string representations more user-friendly when they contain non-ASCII characters.
  • Revision 3874 — Improve error logging on monitor data.
  • Revision 3878 (Issue #2877) — Fix an issue that allowed more than one LDAP connection handler to be configured with the same port.
  • Revision 3881 (Issues #2906 and #2909) — Fix a problem that prevented indexed searches from returning a referral if the base entry was a referral entry.
  • Revision 3883 — Improvements to replication monitoring.

Technorati Tags: , , , , , ,

A completely new stack…

A couple of days ago, a "tweet" by SuperPat piqued my interest : OpenSolaris Developer Preview 2 running on Virtual Box on Mac OS X 10.5.2…

So I decided to try it as I’ve just updated my MacBook Pro to Mac OS X 10.5.2

I first downloaded and installed VirtualBox for OS X (beta 3, Intel Macs only).

I started VirtualBox and created my first New Virtual Machine, for Solaris, 1GB of memory, self expanding disk of 20GB.

Picture 7

I downloaded the Open Solaris Developer Preview 2 iso image and mounted it on the Virtual Machine:

Picture 16

I started the virtual machine, starting the live image of Open Solaris. When it’s started, double click on the Install OpenSolaris icon and follow the installation wizard (it’s so simple and straightforward now, congratulation to the OpenSolaris installer team):

Picture 2

Rebooted the virtual machine and voila…

Picture 12

Well, almost ! In order to get the network access to work, I followed the instructions from Alan and added the pcn driver on OpenSolaris.

And finally, I could install OpenDS with the QuickSetup.jnlp file and start doing serious work 😉

Picture 15

Really, I don’t think it could have been much simpler and quicker to install that complete stack on a machine. And you don’t need Mac OS X to do it too… All you need is VirtualBox, OpenSolaris and OpenDS, all of them are based on open source projects and freely available.

Technorati Tags: , , , , , ,

OpenDS 1.0.0-build011 is now available

We have uploaded OpenDS 1.0.0-build011, built from revision 3813 of our source tree, to our promoted builds folder. The direct link to download the core server is:

The direct link to download the DSML gateway is:

We have also updated the archive that may be used to install OpenDS via Java Web Start. You may launch that using the URL, or visit for more information.

Detailed information about this build is available at

Beware of one limitation:

1. Upgrade/revert can not be supported due to an incompatibility introduced between build-010 and build-011.

Major changes incorporated since OpenDS 1.0.0-build010 include:

  • Revision 3661 (Issue #2446) — Add a default ordering index for the ds-sync-hist attribute. This index is required for replication.
  • Revision 3664 (Issue #2814) — Fix an issue that caused dsreplication enable to fail when a user attempted to enable replication between a server with a global administrator and a server with no global administrator.
  • Revision 3666 (Issue #2640) — Add support for installation from RPM packages.
  • Revision 3669 — Add support to the administration framework for retrieving an internationalized description of the constraints applicable to an aggregation property.
  • Revision 3670 (Issue #2805) — Fix an issue in which changes to the replication purge delay parameter were not taken into account until after the server was restarted.
  • Revision 3671 (Issue #2823) — Fix an issue that was causing the replication heartbeat monitor thread to die suddenly.
  • Revisions 3674 & 3675 (Issue #2806) — Avoid using the class within the org.opends.server.util.RuntimeInformation class (which broke compatability with the IBM JDK on AIX).
  • Revision 3680 (Issue #2830) — Improvements to the build "test" target. This change modifies the "test" target so that it is as lightweight as possible but forgiving for first-time users.
  • Revision 3686 (Issue #2499) — Remove the option to use nanosecond etime resolution as a JVM property. It is now a global configuration property (etime-resolution).
  • Revision 3687 (Issue #2811) — Make dsreplication enable and dsreplication disable symmetric. When the last replicated suffix is disabled, replication on cn=schema and cn=admin data are also disabled and the registration information is updated.
  • Revision 3689 (Issue #2004) — Automatically generate HTML-based configuration documentation.
  • Revision 3695 (Issue #1288) — Make the number of listener threads for synchronization configurable.
  • Revision 3700 (Issue #2822) — Update the permissions of the root file of the installation so that files such as the configuration file are read-protected.
  • Revision 3703 (Issue #2499) — Additional enhancements to the ability to use nanosecond etime resolution.
  • Revision 3706 (Issue #2855) — Include a reference to the log file created by the setup in the event that the user requires more information than what is displayed.
  • Revision 3708 (Issues #2831 and #1948) — Change the local DB backend configuration so that the db-directory and import-temp-directory properties now name a parent directory within which a sub-directory is created having the same name as the backend-id. This simplifies configuration and reduces the risk of name collisions.
  • Revision 3709 (Issue #2850) — Fix a problem that was causing the server to hang after several abandons.
  • Revision 3714 (Issue #2861) — Fix an error in the logger configuration manager that was causing duplicate log messages.
  • Revision 3715 (Issue #2862) — Fix an error that was causing the online backup to consider errors as warnings.
  • Revision 3720 (Issue #1302) — Change the connection algorithm of an LDAP server so that each LDAP server chooses the replication server that is most up to date regarding changes received across the topology.
  • Revision 3727 — Fix an issue that was causing exception errors when running an import on an empty backend.
  • Revision 3735 — Fix an issue that caused LDAP connections to be performed on the local host, even if a specific listen-address was specified in the config.ldif file.
  • Revision 3738 (Issue #2602) — Index definition is no longer required to change an object’s configuration. A severe warning is now logged in the error log instead of preventing the configuration change.
  • Revision 3740 (Issue #2781) — Fix an unchecked exception during database transaction by updating the JE to version 3.2.70.
  • Revision 3743 (Issue #2863) — Fix an issue that caused processes to continue running when all replication servers were stopped simultaneously.
  • Revision 3745 (Issue #2353) — Improve the error handling in logger retention policy enforcement.
  • Revision 3755 (Issue #2872) — Simplify and improve the usage of the dsjavaproperties command.
  • Revision 3773 (Issue #2232) — Log a message when the back end is taken offline.
  • Revision 3774 (Issue #2358) — Add progress information to the verify-index command.
  • Revision 3786 (Issue #2870) — Provide the ability for the status and dsreplication status commands to show replication monitoring.
  • Revision 3801 (Issue #2887) — Fix an issue that was causing the status command to exit with 0 despite connection errors being reported. Now, if there is an error reading the configuration, a specific error code is returned.
  • Revision 3806 (Issue #2772) — Change the logging mechanism so that, if the preload value is set, the following items are logged automatically: the backend being preloaded, its individual databases as they are being preloaded, completion or interruption status and interruption reason.
  • Revision 3810 (Issue #2820) — Fix an issue in which an uncaught deadlock exception caused a fatal replication failure.
  • Revision 3812 (Issue #2598) — Provide the ability to monitor replication globally.

Technorati Tags: , , , , ,