Full OpenDS adoption questionnaire responses from Dominic Cleal of CDO², provider of CDOVaR.net.
Date : October 2008
Can you tell us more about your company ?
CDO2 is a provider of innovative pricing and risk technologies, including our CDOVaR.net platform for structured credit products. The platform runs on the Sun Network.com utility, which allows users to transparently harness grid computing to manage their complex portfolios. The company was founded on the belief that all financial organisations should have access to the latest pricing models and enterprise technology, irrespective of their size or trading volume.
Can you tell us about the application, site, or service in which you have adopted OpenDS?
We are using OpenDS as part of the CDOVaR.net pricing and risk platform for structured credit products. The platform incorporates a number of industry leading pricing models, market data and reference data and is hosted by Sun Microsystems on Network.com. OpenDS is one of the components that is used for the authentication and authorisation of users.
How and when did you first find out about OpenDS?
OpenDS came up while researching for a replacement Java-based LDAP server, primarily to reduce our dependence on native code. Originally we came across it before the 1.0 release and then started trialling it after the release had been made.
Did you go through an evaluation process before selecting OpenDS? If so, can you tell us a little bit about the process and results?
We trialled OpenDS as a straight replacement for our existing LDAP product for a while in our staging systems. Its feature set allowed us to make significant improvements in how we deployed systems and used the directory service, which made it a clear improvement over existing setup. We found OpenDS much simpler to deploy to a new environment, with far less dependencies and far easier to configure out of the box.
What specific version of OpenDS are you using?
Currently the stable 1.0 release.
On what operating system do you run OpenDS? Do you use the same OS for both development and production deployment?
We currently use Solaris 10 for the majority of our production and development environments. Along with other services, we make use of both Solaris zones and ZFS to ensure stability and security for our customers.
On what hardware platform do you run OpenDS? Do you use the same platform for both development and production deployment?
Primarily we are using Sun x64 servers for production and development, though SPARC is also a viable option for us as OpenDS is platform-independent.
Have you purchased a OpenDS license? If not, have you though about doing so and do you know it includes access to patches and sustaining releases (more details from http://wikis.sun.com/display/sunopends)?
We haven't purchased a licence and rely on the open source nature of the product. We don't consider our reliance on the product strong enough to need the extra support.
What specific features of OpenDS are you using?
We use the virtual attributes and plugins to ease management of users and groups and consider the out of the box SSL support excellent.
What do you like most about OpenDS?
As OpenDS is written in Java, it gives us full platform-independence, so we aren't constrained to particular architectures and allows us to deploy to new environments for development and testing. The documentation, including the wiki is comprehensive and nicely centralised, especially considering the age of the project.
What would you most like to see improved in OpenDS?
We'd like to see further growth in the community more than anything, as this will ensure the product will mature and remain well-supported.
Does your application also use a database? If so, which one?
No, though we make use of JavaSpaces in our platform.
Are there any figures about the scale of your adoption which you would like to share (such as how much traffic is being handled, how many entries are stored in OpenDS, how many servers are used)?
Our deployment consists of a single OpenDS instance hosted in our high-availability environment.
How has OpenDS performed since your application/service went live? Have you run into any production issues which you would attribute to OpenDS?
OpenDS has lived up to our expectations and has performed flawlessly so far.
Would you recommend OpenDS to others? Why?
We would definitely recommend OpenDS, as the OpenDS team has been very supportive and it's clear that Sun and the OpenDS team have a strong roadmap for the project's future.
How does OpenDS figure in your future plans?
We may use OpenDS for storing more data about our services and as we deploy to new environments, we may begin using the replication functionality.
How would your describe your participation in the OpenDS project (e.g. user only, submitter of bug reports and RFEs, developer who has contributed code)?
Primarily a user and very occasional bug reporter.
Is there anything else you think would be of interest in a story about your OpenDS adoption?