[
https://issues.apache.org/jira/browse/UIMA-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16224989#comment-16224989
]
Lou DeGenaro commented on UIMA-5634:
------------------------------------
CLI: CliBase, DuccJobSubmit, DuccManagedReservationSubmit
The CLI now decides to write the specification to the file system only when
environment variable DUCC_SAVE_SPECIFICATION is present. Nominally this is not
the case. But if present, the resulting files created are not used by DUCC but
are for user convenience only. Further, the Properties file that is sent to
the OR is enhanced to include a list of properties that were specified by the
user. This information is later utilized by the WS when displaying the
specification tab.
-----
Database: DbCreate, DbDuccWorks
The database support s new table "duccworks", comprising primary key: type {
Job, ManagedReservation} + DuccId. There is one data column comprising the
specification in JSON format representing the specification: { map: system: {
k1:v1, k2:v2,... }, user: { k1:v1, k2:v2,... } }
DbCreate change comprises comments only. Other tables are created by
DUCC_POST_INSTALL using DbCreate. However, for migration purposes this new
table is create by the OR (if not already present) at boot time.
DbDuccWorks provides method to create the duccworks table, and upsert and fetch
specifications.
-----
DUCC Book
The DUCC Book documentation is revised to describe the use of
<security-dir>/.ducc/db.access for controlling access to the Job and Managed
Reservation specifications via ducc-mon.
-----
Orchestrator: OrchestratorComponent
The OR is updated to create the duccworks table if not already existing, and to
save Job and Managed Reservation specifications when submitted.
-----
Transport: SpecificationProperties
Add new field to hold the list of user specified properties, and convenience
methods to add, delete, and interrogate same.
-----
WS: DuccHandler, HandlersHelper, HelperSpecifications
DuccHandler is modified to employ helper classes to fetch Job & Managed
Reservations specifications.
HelperSpecifications provides methods to get Job & Managed Reservation
specification where ever they may be, in DB or file system
HandlerHelper provides accessibility check of file db.access with respect to
requester and owner.
> 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
> 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
(v6.4.14#64029)
