Date: Thu, 28 Mar 2024 06:09:48 -0500 (CDT) Message-ID: <702410393.102.1711624188394@os-confluence.ncsa.illinois.edu> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_101_1760570790.1711624188393" ------=_Part_101_1760570790.1711624188393 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This page is to discuss and explore the possible ideas for Cyber= integrator for BrownDog. From this discussion, we will derive the tangible = tasks for BrownDog.
Discussion points:
Table of Contents
The medici extraction service is able= to execute CI workflow as a extractor. The CI workflow will be queued at e= xtractor event bus.
The polyglot will be run by using CI workflow to have reproducibility.= p>
This is on-demand execution of CI workflow different from extractor idea= . The user will see the possible CI workflow to execute on the dataset on t= he dataset page.
Tight integration of CI and Medici. Ci will use the Medici as a metadata= and dataset storage. It may requires to remove "Spring" framework and adop= ting other "injection" mechanism.
CI workflow will have a step that execute other workflow such as Kepler,= or Galaxy.