Development of Apache OODT

How we keep OODT alive and kicking

Like many open source projects, Apache OODT is continually being developed and improved upon by its devoted team members.

Version 0.6 has been released and is available for download and use. This is a mid-sized release and it is recommended that all users of 0.5 upgrade immediately to 0.6. The 0.6 release addresses 69 issues from our JIRA management system. The release includes full support for the PEAR packaging system for PHP, including the delivery of several PHP PEAR libraries for OODT's file manager. In addition, this release marks the beginnings of several Google Summer of Code projects including the ability to use Ganglia as a resource monitoring system and an all CXF based CAS-product web app. In addition, Apache OODT 0.6 now successfully builds with Maven3. The Apache OODT OPSUI got a facelift in its default skin, new CAS-PGE input file writers based on templates have been added, support for running CAS-PGE in Cygwin on Windows has landed, and overall the OODT RADIX installer has been significantly improved.

Version 0.5 has been released and is available for download and use. This is a mid-sized release and it is recommended that all users of 0.4 upgrade immediately to 0.5. The 0.5 release addresses 61 issues from our JIRA management system. The release includes various ingestion and curation-related improvements to our File Manager system including a lenient Lucene-based catalog that allows the ingestion of arbitrary metadata; improvements to our Solr-based indexing system to dump File Manager metadata from arbitrary catalog backends to Solr; and improvements to our Curator JAX-RS web application system. In addition, several bugs related to the PushPull remote file retrieval system and bugs related to various tools including the ExpImpCatalog tool were fixed. Finally the release marks a complete improvement of the WEngine workflow system. CAS-PGE, crawler, workflow manager and resource manager can now all be used together, in a forwards (Wengine/Workflow2) and backwards compatible way. Early WEngine features including explicit support for branch and bounds in policy, inheritable configuration, global workflow conditions, task-level timeouts and post conditions, are now all supported.

Version 0.4 has been released and is available for download and use. This is a major release that includes 168 fixed issues in JIRA and is now the major recommended release of OODT to be using. One major note is that the updates to the workflow manager (described in OODT-215) are not yet fully complete. Instead of waiting for them to finish, we rolled this release and are recommending users to stay on the 0.3 version of the workflow manager, cas-pge, and the crawler components. All other components should be upgraded to their 0.4 counterparts. A complete list of changes can be found here. Grab your copy from the Download page today.

Version 0.3 has been released and is available for download and use. This is the second release from the team as a Top Level Project and includes several bug fixes and enhancements, over 50 issues were closed during this release cycle. A complete list of changes can be found here. Grab your copy from the Download page today.

The Apache OODT community is proud to present version 0.2 for download and use. This is the first release from the team as a Top Level Project, which demonstrates our commitment to continuous improvement. Be sure to visit the Download page to get a copy for yourself.

The OODT Team has graduated from the Incubator and we are pleased to inform you that our code is available for download. We've developed a roadmap outlining future releases, including the first release under Apache aegis: 0.1-incubating, which we hope to offer for download shortly. Of course, there's nothing stopping an early adopter from grabbing the source and building it him or herself.

Build Details

The majority of the components of OODT is written in Java, while the Agility component is written in Python. Knowledge of both is nice, though.

Each component of the Java build is controlled by Maven. However, there is also a top-level project object model that orchestrates building all of the OODT components. Maven is not used for the Agility component; being Python, it takes advantage of the traditional Python Distutils enhanced by Distribute.

Testing

While we may not fully subscribe to the idea that "untested code is broken code", we do strive to include a lot of automated unit and functional testing. Apache OODT has its own Jenkins continuous integration server that runs nightly, and automatically after each commit.