-
Notifications
You must be signed in to change notification settings - Fork 1
SciCumulus Components
SciCumulus Components
SCC consists of four components, as follows: SciCumulus Setup, SciCumulus Core, SciCumulus Starter and SciCumulus Query Processor. These components are presented in more detail in the next sections.
-
SciCumulus Setup (SCSetup): This component is responsible for the insertion and removal of the conceptual workflows in the provenance database. SC Setup represents activities, relations and attributes in those relations in a conceptual model. The conceptual workflow removal not only does delete the conceptual data but also all registers from the workflow execution (management data of workflow execution and domain-specific data stored in the relations). The information about the workflow execution, domain-specific data and performance data are produced by the invocation of the SciCumulus Core.
-
SciCumulus Core (SCCore): This component allows to execute conceptual workflow that was already stored by the SC Setup in the provenance database. The conceptual activities are instantiated according to the specified data in the input relations. SCCore defines each instance of an activity, which consists of tuples of one or more input relations, as activation. Activation is established according to three steps: instrumentation of the programs according to the input data consumed by activation, invocation of the instrumented programs and extraction of output data. During the workflow execution, SCC also supports provenance query processing. In this case, SciCumulus Query Processor is responsible for running these queries.
-
SciCumulus Query Processor (SCQP): It is responsible for the query processing in the provenance database. The access to the provenance database is different according to the HPC environment informed by the user in a configuration file, which will be presented further.
-
SciCumulus Starter (SCStarter): SCStarter allows for users to model and submit data-centric workflows to a HPC environment. SC Starter sends service requests for other components (SCSetup, SCCore and SCQP) deployed in the HPC environments, such as insert a conceptual workflow in database, execute a specific stored workflow or monitor a workflow execution.