Skip to content

Commit

Permalink
fix
Browse files Browse the repository at this point in the history
  • Loading branch information
fstagni committed Oct 7, 2024
1 parent 5f8604a commit 35ea506
Showing 1 changed file with 12 additions and 9 deletions.
21 changes: 12 additions & 9 deletions slides.md
Original file line number Diff line number Diff line change
Expand Up @@ -119,7 +119,8 @@ title: WMS

:: title ::

# WMS: Workload Management System
# WMS
### Workload Management System
- Pull model based on Pilot jobs
- Also "Push" solution for HPCs that do not support pilots (because of limited internet access).
- Will integrate [CWL (Common Workflow Language)](https://www.commonwl.org) as a way of defining jobs (replacing JDL) --> see poster #217
Expand Down Expand Up @@ -159,7 +160,8 @@ titlewidth: is-5

:: title ::

# DMS: Data Management System
# DMS
### Data Management System
It’s about **files**:​ placing, replicating, removing files​

- there are **LFNs** (logical file names) → and users ONLY work with these​
Expand Down Expand Up @@ -194,16 +196,17 @@ title: TS

:: title ::

# Productions and Dataset management
# TS (Transformation System)
### For productions and Dataset management

- A *Data Processing* **transformation** (e.g. Simulation, Merge, DataReconstruction...) creates jobs in the WMS (and re-sumbit them, and destroy them).​
- A *Data Processing* **transformation** (e.g. Simulation, Merge, DataReconstruction...) creates jobs in the WMS (and re-sumbit them if needed, eventually destroy them).​

- A *Data Manipulation* **transformation** replicates, or remove, data from storage elements.

:: content ::

<span class="bg-cyan-100 text-cyan-600 p-4 border-l-6 border-2 border-cyan-400 rounded-lg pl-8 pr-8 w-full block">
The Transformation System (TS) is used to automate common tasks related to production activities. It can handle thousands of productions, millions of files and jobs.
The TS is used to automate common tasks related to production activities. It can handle thousands of productions, millions of files and jobs.
</span>

&nbsp;
Expand Down Expand Up @@ -273,12 +276,12 @@ title: issues
<li> somewhat cumbersome deployment</li>
<li> late on “standards”
<ul class="text-vs mx-auto">
<li> http services</li>
<li> tokens</li>
<li> monitoring</li>
<li> No http services</li>
<li> No tokens</li>
<li> Old monitoring</li>
</ul>
</li>
<li> “old”-ish design (RPC, cron agents…)</li>
<li> “old”-ish design (RPC, "cron" agents…)</li>
<li> not very developer-friendly: rather un-appealing/confusing, especially for new (and young) developers</li>
<li> multi-VO, but was not designed to do so since the beginning</li>
<li> no clear interface to a running DIRAC instance</li>
Expand Down

0 comments on commit 35ea506

Please sign in to comment.