DOC: Added documentation changes to reflect the addtion of the OAR scheduler plugin

Author: demianw

CHANGES

@@ -1,5 +1,7 @@
 Next Release
 ============
+
+* ENH: Added an OAR scheduler plugin (https://github.com/nipy/nipype/pull/1259)
 * API: Default model level for the bedpostx workflow has been set to "2" following FSL 5.0.9 lead
 * ENH: New interfaces for interacting with AWS S3: S3DataSink and S3DataGrabber (https://github.com/nipy/nipype/pull/1201)
 

doc/users/plugins.rst

@@ -9,7 +9,7 @@ available plugins allow local and distributed execution of workflows and
 debugging. Each available plugin is described below.
 
 Current plugins are available for Linear, Multiprocessing, IPython_ distributed
-processing platforms and for direct processing on SGE_, PBS_, HTCondor_, LSF_, and SLURM_. We
+processing platforms and for direct processing on SGE_, PBS_, HTCondor_, LSF_, OAR_, and SLURM_. We
 anticipate future plugins for the Soma_ workflow.
 
 .. note::
@@ -276,6 +276,34 @@ for all nodes could look like this::
                          wrapper_args=shim_args)
         )
 
+OAR
+---
+
+In order to use nipype with OAR_ you simply need to call::
+
+       workflow.run(plugin='OAR')
+
+Optional arguments::
+
+  template: custom template file to use
+  oar_args: any other command line args to be passed to qsub.
+  max_jobname_len: (PBS only) maximum length of the job name.  Default 15.
+
+For example, the following snippet executes the workflow on myqueue with
+a custom template::
+
+       workflow.run(plugin='oar',
+          plugin_args=dict(template='mytemplate.sh', oarsub_args='-q myqueue')
+
+In addition to overall workflow configuration, you can use node level
+configuration for OAR::
+
+    node.plugin_args = {'oarsub_args': '-l "nodes=1/cores=3"'}
+
+this would apply only to the node and is useful in situations, where a
+particular node might use more resources than other nodes in a workflow.
+
+
 ``qsub`` emulation
 ~~~~~~~~~~~~~~~~~~