Page History

...

Maven offers an improved way to export, configure and build OODT called Archetypes. Archetypes simply put are a way to define templates for projects. Within these project templates we can also will include packaging instructions to conform to the guidelines below to increase the similarity amongst deployments of OODT. Moreover, we will build higher level scripts and configuration to tie the pieces together at the system level. Finally, we will leverage the CAS Install Maven Plugin to take us from our source structure to our deployment structure.

This wiki will be used to capture thoughts, ideas and plans for the first archetypes we develop for OODT. To keep things simple we are going to initially focus on a small number of modules that are typically deployed and configured together. Finally, our goal is to build an 80% solution that works in most cases to get people out of the gates and running with a full OODT solution. We believe this effort will help increase adoption and conformity amongst installations of an already great system that is highly configurable.

Assumptions:

• The initial archetype will export RELEASED versions of OODT
• The initial archetype will export Crawler, FileManager and Workflow Manager ONLY (they will be bundled together and configured to work together)
  • other modules will be added in the future
• FileManager Policy will be read recursively from the components/filemanager/policy directory. This will remove the requirement to make properties updates when additional policy files are added in sub-directories.

...

• Submit INFRA ticket to create a place to put all Maven Central artifacts
• Load/Install artifacts to Maven Central

Commands to Generate an OODT Pipeline

prompt> oodt create -p my-pipeline
prompt> ./my-pipeline/deployment/bin/oodt start
prompt> svn import my-pipline/source http://host_name/svn_dir/repository_name/my-pipline -m "Initial OODT Import"

Default Deployment Structure

In order for the easy installation to work properly we will need to settle on a default project deployment layout structure. Below is our plan of how we want to layout the project deployment when the default project is built. First we will list out an overview, then we can detail each path and what files are going to be saved into each.

/$DEPLOYMENT_BASE_DIR

  /archive
  /bin
  /components
    /crawler
      /bin
      /conf
      /policy
    /filemanager
      /bin
      /conf
      /policy
    /workflowmanager
      /bin
      /conf
      /policy
  /conf
  /staging
  /workflow_out

...

Deployment Path Details

/$PROJECT$DEPLOYMENT_BASE_DIR/bin- This will contain scripts that will manipulate the underlying components. For example all 3 components can be started, stopped and restarted from this directory. At the same time you can also manipulate a single component at a time from this dir also.

...

\_./oodt \[start,stop, restart\]    \[crawler OR filemanager OR workflowmanager\]\_

*/$PROJECT$DEPLOYMENT_BASE_DIR/components - This will contain a single folder for each component.  Initially this will only contain the 3 components we have selected to start this process, but as more components are added they will be added in here.

/$PROJECT$DEPLOYMENT_BASE_DIR/conf - This will contain configuration and properties files which apply to several components. This should (like the bin dir) give users a single directory they can go into to configure the associate components.

...

filemanager

workflowmanager

Default Source Structure

Source Path Details

Future Work

Once the above is complete our thoughts are that the next items to be incorporated are as follows:

...