fix

fstagni · Oct 17, 2024 · 7ad5f8d · 7ad5f8d
1 parent 165e96b
commit 7ad5f8d
Showing 1 changed file with 88 additions and 61 deletions.
diff --git a/slides.md b/slides.md
@@ -275,33 +275,34 @@ Implemented using `ExtJS`, and fully custom Python "bindings"
 
 ---
 layout: top-title-two-cols
-align: c-lm-lm
+align: l-lm-lt
 color: gray-light
 title: world
 ---
 
-<StickyNote color="gray-light" textAlign="center" width="260px" title="DIRAC needs to follow these trends" v-drag="[350,380,320,100]">
-What is the best way to achieve that? Can we do it within the current framework?
+<StickyNote color="gray-light" textAlign="center" width="260px" title="Dirac should follow these trends" v-drag="[550,380,320,100]">
+What is the best way to achieve keep up with these trends? Can we do it within the current framework?
 </StickyNote>
 
 
 :: title ::
 
-# Few topics of interest from the technology world around us
+## Technology trends
 
 :: left ::
 
-## tech trends
+You authenticate with an external "Identity provider":
+
+<img src="/public/images/idp_login.png" alt="idp_login" width="220"/>
 
-- You authenticate with an external "Identity provider":
+For authorization purposes you are using tokens everywhere:
 
-![](/public/images/idp_login.png)
+<img src="/public/images/google_token.png" alt="google_token" width="350"/>
 
-- For authorization purposes you are using tokens everywhere:
 
-![](/public/images/google_token.png)
+:: right ::
 
-- (Nicely documented) REST APIs are a de-facto standard:
+(Nicely documented) REST APIs are a de-facto standard:
 
 ```sh
 # "get a tag" from github
@@ -313,25 +314,82 @@ curl -L \
   https://api.github.com/repos/OWNER/REPO/git/tags/TAG_SHA
 ```
 
-:: right ::
+---
+layout: top-title
+align: lm
+color: gray-light
+title: wlcg
+---
+
+<StickyNote color="gray-light" textAlign="center" width="260px" title="Dirac needs to follow these recommendations" v-drag="[570,380,320,120]">
+What is the best way to achieve keep up with these recommendations? Can we do it within the current framework?
+</StickyNote>
+
+
+:: title ::
+
+## Recommendations from WLCG, EGI, etc.
 
-## WLCG, EGI
 
-**Community management**
-- VOMS (Virtual Organization Membership Service) has been, for many years, a de-facto standard
+:: content ::
+
+- VOMS (Virtual Organization Membership Service) has been, for many years, a de-facto standard for **community management**
   - it issues VOMS proxies ("short" certificates)
   - Outside of WLCG and EGI, proxies are not a thing
-- There are new Identity Providers delivering tokens instead of proxies
+- --> There are new Identity Providers delivering tokens instead of proxies
+
+&nbsp;
 
 In this conference:
 
-<a href="https://indico.cern.ch/event/1338689/contributions/6010716/" class="text-blue-600 hover:underline">WLCG transition from X.509 to Tokens: Progress and Outlook</a></li>
-<a href="https://indico.cern.ch/event/1338689/contributions/6011018/" class="text-blue-600 hover:underline">CMS Token Transition</a></li>
-<a href="https://indico.cern.ch/event/1338689/contributions/6011022/" class="text-blue-600 hover:underline">
-Fermilab’s Transition to Token Authentication</a></li>
+- <a href="https://indico.cern.ch/event/1338689/contributions/6010716/" class="text-blue-600 hover:underline">WLCG transition from X.509 to Tokens: Progress and Outlook</a>
+- <a href="https://indico.cern.ch/event/1338689/contributions/6011018/" class="text-blue-600 hover:underline">CMS Token Transition</a>
+- <a href="https://indico.cern.ch/event/1338689/contributions/6011022/" class="text-blue-600 hover:underline">Fermilab's Transition to Token Authentication</a>
+
+
+
+---
+layout: top-title-two-cols
+color: gray-light
+align: c-rt-lt
+title: requirements
+---
+
+<StickyNote color="gray-light" textAlign="center" width="260px" title="Developers and maintainers requirements" v-drag="[350,300,320,100]">
+Easy to test (will make it easier to code), but also modern, fun, and accessible to new developers
+</StickyNote>
+
+<StickyNote color="amber-light" textAlign="center" width="260px" title="Paramount requirement" v-drag="[350,420,290,70]">
+We need to ensure business continuity
+</StickyNote>
+
+
+
+:: title ::
+
+# Minimal Requirements
+
+:: left ::
+
+## Communities/Users requirements
+
+Ease of use, including ease of access
+
+Fast and responsive interfaces
+
+Scalable and flexible
+
+:: right ::
+
+## Administrator requirements
 
+Ease of installation and update
 
+Up-to-date documentation
 
+Clear confguration
+
+Ready-to-use dashboards
 
 
 ---
@@ -367,49 +425,19 @@ title: issues
 
 ---
 layout: section
-color: cyan-light
---- 
-
-## DiracX,  the neXt DIRAC incarnation
-
-
----
-layout: top-title-two-cols
-color: gray-light
-align: c-rt-lt
-title: requirements
+color: lime-light
 ---
 
-<StickyNote color="gray-light" textAlign="center" width="260px" title="Developers and maintainers requirements" v-drag="[350,380,320,100]">
-Easy to test (will make it easier to code), but also modern, fun, and accessible to new developers
-</StickyNote>
-
-
-:: title ::
+## We decided that the best of satisfying the requirements was to code a new Dirac
 
-# Minimal Requirements
 
-:: left ::
-
-## Communities/Users requirements
-
-Ease of use, including ease of access
-
-Fast and responsive interfaces
-
-Scalable and flexible
-
-:: right ::
-
-## Administrator requirements
-
-Ease of installation and update
-
-Up-to-date documentation
+---
+layout: section
+color: cyan-light
+--- 
 
-Clear confguration
+## DiracX,  the neXt DIRAC incarnation
 
-Ready-to-use dashboards
 
 ---
 layout: side-title
@@ -431,7 +459,7 @@ title: DiracX
 - Standards-based
 
 <AdmonitionType type='important' >
-Still DIRAC, in terms of functionalities.
+Still Dirac, in terms of functionalities.
 </AdmonitionType>
 
 
@@ -806,7 +834,7 @@ Extension "Gubbins" provided for reference
 ---
 layout: side-title
 color: gray-light
-title: architecture
+title: Architecture
 align: cm-lm
 titlewidth: is-3
 ---
@@ -932,7 +960,8 @@ title: summary
 :: right ::
 
 ### DiracX is in active development
-- Foundations are there, the first release will soon be here
+- We are rewriting the code, but we are keeping Dirac
+- The first release will soon be here
 - DiracX will live together with DIRAC v9 for a while
 - DiracX will ease the interoperability with Rucio and/or any other tool out there
     - DiracX will still have the Data Management part, but its Workload Management functionalities will come first
@@ -1061,5 +1090,3 @@ Q/A
 - What did you use to make these slides?
 
 --> [slidev](https://sli.dev/) with [neversink theme](https://gureckis.github.io/slidev-theme-neversink)
-
-