1 / 10

WP2

WP2. Capacity Expansion at Infrastructure Level. WP2 – Capacity Expansion at Infrastructure Level. Manpower Distribution: | CSIC | LIP | KIT | PSNC | CESNET | IISAS | CYFRONET | INCD | |------|-----|-----|------|--------|-------|----------|------|

halia
Download Presentation

WP2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WP2 Capacity Expansion at Infrastructure Level

  2. WP2 – Capacity Expansion at Infrastructure Level • Manpower Distribution: • | CSIC | LIP | KIT | PSNC | CESNET | IISAS | CYFRONET | INCD | • |------|-----|-----|------|--------|-------|----------|------| • | 54 | 13 | 37 | 25 | 10 | 20 | 30 | 27 | • Main Goal: • Integrate [topical|national] infrastructures/repositories with EOSC core services • For this to happen we need to • Have a list of the repositories to enable • Identify the EOSC Core Services required • And which of those we have to operate ourselves • Identify which services are required to be added to the sites • And how to integrate at the site • Integrate it all :) • Tasks: • 2.1: [CYFRONET, Roksana]: Integration with EOSC core services • 2.2: [CSIC, Mario]: Integration on the technical standards level • 2.3: [KIT, Uros/Marcus/Valentin]: Technical integration on the policy level • 2.4: [IISAS/CSIC, Fernando]: Integration of National Research Data Repositories • Deliverables: • We managed to reduce the amount of deliverables, and now only have this: • D5 / D2.1 [KIT, M7]: Roadmap for the integration • D6 / D2.2 [CSIC, M15]: Intermediate report on integration efforts • D7 / D2.3 [IISAS, M29]: Final report on EOSC integration

  3. The general WP2 operation • 2.1 EOSC Core Services • Derive a list of EOSC/DEEP services that are required • Central / Site-Level • 2.2 Define the communication standards (data transfer / job submission / container instantiation, ...) • Some overlap with 2.1 • 2.3: Consulting / Overview for Policies: • Support admins / management in choosing the right policies • Make sure the right policies are known by the right people • Check if policies are in place • 2.4 / WP4: Identify repositories / use cases: • Ordered list (“pilots”) • DANS (Gerard), Digital CSIC (Isabel Bernal), PSNC Agriculture (tba), KIT/LSDF (Marcus)

  4. The general WP2 mission • Identify initial repositories • Identify the target infrastructure

  5. WP2.3 – Technical integration on the policy level • Making sure that the AARC AAI Policies are put in place • We have a specialist from AARC (uros.stevanovic@kit.edu) booked for this • Technical integration: • <=> Make sure that the technical requirements of the policies can be implemented • Example: SIRTFI (Security Incident Response Trust Framework) • Emergency Contact • Audit logs • Suspension of suspicious accounts • ... • Example: GDPR • Privacy Policy • Data Processor • ...

  6. Tools • Mailinglist: wp2-eosc-synergy@listas.csic.es • Trello: https://trello.com/b/JWLi25TC/eosc-synergy • Add links to documents • Documents can either be in OwnCloud, github or google • Make sure people own their tasks • Add tags • Chat • Rather not • Videocalls: • One per Task (weekly) • One for Task-Leads and me (weekly, preferably short after the Tasks)

  7. Material for Task Leaders • Workpackage Manpower • 2.1: [CYFRONET, Roksana]: Integration with EOSC core services • | CSIC | LIP | KIT | PSNC | CYFRONET | • |------|-----|-----|------|----------| • | 18 | 5 | 15 | 15 | 20 | • 2.2: [CSIC, Alvaro]: Integration on the technical standards level • | CSIC | LIP | CYFRONET | INCD | • |------|-----|----------|------| • | 16 | 5 | 5 | 10 | • 2.3: [KIT, Uros/Marcus/Valentin]: Technical integration on the policy level • | CSIC | KIT | PSNC | CESNET | IISAS | INCD | • |------|-----|------|--------|-------|------| • | 12 | 15 | 5 | 5 | 5 | 10 | • 2.4 [IISAS/CSIC, Fernando]: Integration of National Research Data Repositories • | CSIC | LIP | KIT | PSNC | CESNET | IISAS | CYFRONET | INCD | • |------|-----|-----|------|--------|-------|----------|------| • | 8 | 3 | 7 | 5 | 5 | 15 | 5 | 7 |

  8. Next Steps • Task Leaders: • Find your Team! • Report to me, which institutions are not contributing • Arrange time and date for a short weekly call (max 30 minutes) • Find your goals / Start working

  9. Task 2.3 Technical integration on the policy level

  10. T2.3 Technical integration on the policy level • What the hell does that mean • Policy: We mean policies from the AARC background. I.e.: • SIRTFI, SNCTFI, GDPR, REFEDS RAF, REFEDS R&S, AARC-G[0-9]*3 • All these policies have technical implications • T2.3 will make sure that • Technical requirements from polices are known and understood • Implementations do not contradict the policies • Help with organisational measures, required by the policies • This Task is notabout • Access policies (why can who access which file) • Who is involved? • 2.3: [KIT, Uros/Marcus/Valentin]: Technical integration on the policy level • | CSIC | KIT | PSNC | CESNET | IISAS | INCD | • |------|-----|------|--------|-------|------| • | 12 | 15 | 5 | 5 | 5 | 10 |

More Related