diff --git a/slides.md b/slides.md index b62f46f..391c231 100644 --- a/slides.md +++ b/slides.md @@ -280,23 +280,26 @@ color: gray-light title: world --- - -What is the best way to achieve that? Can we do it within the current framework? + +What is the best way to achieve keep up with these trends? Can we do it within the current framework? :: title :: -# Few topics of interest from the technology world around us +## Few topics of interest from the technology world around us :: left :: -## tech trends +**tech trends** - You authenticate with an external "Identity provider": ![](/public/images/idp_login.png) + +:: right :: + - For authorization purposes you are using tokens everywhere: ![](/public/images/google_token.png) @@ -306,31 +309,40 @@ What is the best way to achieve that? Can we do it within the current framework? ```sh # "get a tag" from github -curl -L \ - -H "Accept: application/vnd.github+json" \ - -H "Authorization: Bearer " \ - -H "X-GitHub-Api-Version: 2022-11-28" \ - https://api.github.com/repos/OWNER/REPO/git/tags/TAG_SHA +curl -L -H "Accept: application/vnd.github+json" -H "Authorization: Bearer " -H "X-GitHub-Api-Version: 2022-11-28" https://api.github.com/repos/OWNER/REPO/git/tags/TAG_SHA ``` -:: right :: +--- +layout: top-title +align: lm +color: gray-light +title: world +--- + + +What is the best way to achieve keep up with these trends? Can we do it within the current framework? + -## WLCG, EGI -**Community management** -- VOMS (Virtual Organization Membership Service) has been, for many years, a de-facto standard +:: title :: + +## Few topics of interest from the technology world around us /2 + + +:: content :: + +**WLCG, EGI, etc.** + +- 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 In this conference: -WLCG transition from X.509 to Tokens: Progress and Outlook -CMS Token Transition - -Fermilab’s Transition to Token Authentication - - +WLCG transition from X.509 to Tokens: Progress and Outlook< +CMS Token Transition +Fermilab's Transition to Token Authentication @@ -380,10 +392,15 @@ align: c-rt-lt title: requirements --- - + Easy to test (will make it easier to code), but also modern, fun, and accessible to new developers + +We need to ensure business continuity + + + :: title :: @@ -806,7 +823,7 @@ Extension "Gubbins" provided for reference --- layout: side-title color: gray-light -title: architecture +title: Architecture align: cm-lm titlewidth: is-3 --- @@ -932,7 +949,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