Choose timezone
Your profile timezone:
Powered by Indico
v3.3.5
Einladungslink https://desy.zoom.us/j/61470809359
ID 614 7080 9359
Kenncode 834675
Teilnehmer:
- Kilian
- Christian Tacke (GSI)
- Michael Zacharias (Heidelberg)
- Christoph Wissing (DESY)
- Rouven Spreckels (GSI)
- Michael Wigard (Uni Muenster)
- Alessandro Montanari (LSW)
- Ramin (Heidelberg)
- Christopher Huhn (GSI)
- Guenter Duckeck (Muenchen)
- Harry Enke (AIP)
- Hermann Hessling (HTW)
TOP1:
Documents
Doc1: TA2
Document from TA2 workshop:
https://syncandshare.desy.de/index.php/s/LKQgLA8nsCkYGCP
AAI capabilities
AAI group based key
work with data which are not public
need to be in corresponding group
only weakly supported in Helmholtz AAI
always have to talk back to central AAI
In Indigo IAM this works
by encoding permissions into tokens
Unity is the base for Helmholtz AAI
we want to request this from Unity
to be implemented
should be aligned with requirements
document
DOC2: AAI Req document
AAI Requirements Document:
https://results.punch4nfdi.de/?md=/docs/Documents/aai-requirements.md
main content included
comparison done
content of Doc1 is already included in Doc2
discussion with NFDI group
preparation of a development
request which reflects this kind
of request
DOC3:
Feature Request Document:
https://docs.google.com/document/d/14NII7zyh5ytnicTPmcOtwx-Jr9fAoDTiUTkU4nXDun0/edit#heading=h.sc34ezl7ielq
Sander agreed to be primary contact
Kilian will verify with Sander and MH
question about money
all 3 wishes will be forwarded
but hierarchical request
paid request will then be submitted
well spent money
since AAI will go in that direction
anyway
TOP NFDI architecture approval
Indigo IAM interaction should be
driven by PUNCH4NFDI
==> should be listed as sub bullet
as point 2
agree except of bullet point 2
what about EOSC AAI ?
Is there an implemented EOSC AAI ?
EGI Checkin exist
==> to be clarified
seems to work for EOSC portal
maybe only authentication part
authorisation part works to ?
==> have closer look
TOP 3:
inter ta meeting about physics tools
went very well and very good discussions also with Christian from OSSR
will continue to develop Physics tools
the 2 things complement each other
things should be made more user friendly
good and needed, deliverable itself can be finalised very soon
continue developing physics tools after that
what about d-ta6-wp4-5 (Karim)
works already as a repository for softwares
with this tool we fullfill this deliverable
with deliverable D-TA6-WP4-4 this is a different issue
D-TA6-WP4-5 software platform fullfilled by Physics tools
small team to extent and develop
plan exists and will be followed
discussion yesterday clarified things
Physics tools is an extended search engine
bio tools do way more than physics tools
we can not use it as bio tools
would suggest to find a better name for Physics tools
not suggesting to be a tool for everything
domain name and logo: name can be changed
if we find a better name we can rename
no better name so far
TA6 people should think about better name
open to extend Physics tools so that it does more than being
a search engine
how to sustain this development and maintain it ?
software should always written the way that other people can take over
if people want to join they should contact ta6 actively
maintenance is an issue which is important for all services
this is part of the general service approval process
Physics tools: 3 python scripts and 1 php scripts (complete web site)
combined less than 1000 lines of code
DB is about 50 MBs scaling up to 300 MBs
MySQL DB in 4 tables
really small project
source code will be uploaded to gitlab
everybody else can upload and modify
source code is only one thing
but running and maintaining the web server is another issue
this comes also with approving the service
in worse case contract can be paid by individual person
TOP software
ROOT is already available in many forms
as a docker container can be provided
what is needed in addition ?
couple of workflows with all details as representation
if there is a specific case with involving ROOT this can be placed
as an example with instructions how to use it
providing container with ROOT software is one thing
what about corresponding storage ?
there is no clear path we have to operate on case space
refer user to somewhere and run on your own
short discussion round with Joe and Guenter how to fullfill this request
document examples could be a way to go.
CPU on low level with general service can easily be run
AOB:
none
next week TA6 WP1 invitation will follow