uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lou DeGenaro (JIRA)" <...@uima.apache.org>
Subject [jira] [Reopened] (UIMA-5634) DUCC Orchestrator (OR) populate DB with Job and Managed Reservation specifications
Date Wed, 07 Feb 2018 13:53:00 GMT

     [ https://issues.apache.org/jira/browse/UIMA-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lou DeGenaro reopened UIMA-5634:
--------------------------------

If ducc.database.host == "–disabled–" then use filesystem for specifications.

> DUCC Orchestrator (OR) populate DB with Job and Managed Reservation specifications
> ----------------------------------------------------------------------------------
>
>                 Key: UIMA-5634
>                 URL: https://issues.apache.org/jira/browse/UIMA-5634
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>            Priority: Major
>             Fix For: 2.2.2-Ducc
>
>
> Presently, Job and Managed Reservation specifications are kept in "user" space, that
is in the file system in the user's log directory.  
> The Command Line Interface (CLI) should no longer write these specifications to the file
system, but rather when submitted to the Orchestrator (OR) they should be persisted in the
DB for later retrieval.  This accomplishes 2 desirable outcomes: 
> 1. The specification persists after the user purges his/her log directory
> 2. The specification is available to the Web Server (ducc-mon) when there is no shared
file system



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message