Merge pull request #12 from TACC-Cloud/doc_changes

Doc changes for queue defined with -1 example

docs/agave/guides/jobs/aloe-job-changes.rst

@@ -220,6 +220,8 @@ The following table lists all parameters that may be specified in a job submissi
 
 Some parameter types may differ from similar object model types shown above. The former represent types provided by users on input, the latter types used by the Jobs service during job execution.
 
+It should be noted that Aloe is tighter with parameter checking than Agave. Certain "loose" parameters that may have slipped through with Agave will likely cause errors with Aloe. For example, defining queues with some fields having a `-1` value, meaning there would be no limit, worked with Agave. Aloe does not allow negative values and will cause such queue to be dropped from the job submission. 
+
 Parameters required for job submission are marked with an asterisk (*).
 
 +----------------------+-----------+-------------------------------+

docs/agave/guides/jobs/aloe-job-migration.rst

@@ -35,4 +35,4 @@ Some applications are built upon libraries such as the `Agave CLI <https://tacc-
 Workflow Migration
 ------------------
 
-The ultimate validation of the new Jobs service comes when clients can successfully run their complete workflows with the software they normally use.  This client software can include the `CLI <https://tacc-cloud.readthedocs.io/projects/agave/en/latest/agave/tooling/command-line-interface.html>`_, portals, custom scripts, workflow engines, Jupyter Hub, private databases, `Abaco <https://tacc-cloud.readthedocs.io/projects/abaco/en/latest/>`_, etc.  Subtle differences between the old and new Jobs services can lead to problems in unexpected places in the workflow.  It's important that all commonly executed workflows be exercised and validated under the new system **before** production migration.
+The ultimate validation of the new Jobs service comes when clients can successfully run their complete workflows with the software they normally use.  This client software can include the `CLI <https://tacc-cloud.readthedocs.io/projects/agave/en/latest/agave/tooling/command-line-interface.html>`_, portals, custom scripts, workflow engines, Jupyter Hub, private databases, `Abaco <https://tacc-cloud.readthedocs.io/projects/abaco/en/latest/>`_, etc.  Subtle differences between the old and new Jobs services can lead to problems in unexpected places in the workflow. For example, defining queues with some fields having a -1 value, meaning there would be no limit, worked with Agave. Aloe does not allow negative values and will cause such queue to be dropped from the job submission. It's important that all commonly executed workflows be exercised and validated under the new system **before** production migration.