EOSC Beyond Workshops: Definition of EOSC Nodes and their federation, requirements for EOSC Core services from a use case perspective and integration activities.

10 Jun 2024, 10:00 → 12 Jun 2024, 18:00 Europe/Warsaw

303 (ACC Cyfronet AGH)

Main points:

1. Conceptual and Technical Definition: Develop an EOSC Node technical description based on the workshop findings. This includes identifying possible types of nodes, their organizational structure, architecture, and functional scope.
2. Dependencies and Federation Concept: Sketch the initial dependencies between the potential nodes and define the concept of the EOSC Nodes Federation. This involves identifying potential federated services and possible node integration.
3. Core Service Requirements: Outline the requirements for core services from the potential nodes and other relevant stakeholders. This may include input for the specification of EOSC Core services adapters, etc.

---

Event Location:

Academic Computer Centre Cyfronet AGH

Nawojki 11 st., 30-950 Kraków

Floor 3, Room 303

Accommodation

Participants are responsible for organising and financing their own accommodation.

Hotels near AGH UST:

Hotel POLONEZ ul. Reymonta 15, 30-059 Kraków Tel: +48 122928294, +48 126341954 Email: recepcja@hotel-polonez.pl Antica Residence ul. Czarnowiejska 76, 30-054 Kraków Tel: +48 126312350 Email: recepcja@anticaresidence.pl Campanile Krakow South ul. Profesora Stanisława Łojasiewicza 2, 30-348 Kraków Tel: +48 12 3783793 Email: reception.krakow.south@campanile.com Hyatt Place Krakow Al. 3 Maja 47a, 30-062 Kraków Tel: +48 12 354 1234

Hotel Krupnicza ul. Krupnicza 30, 31-123 Kraków Tel: +48 690 624 267 Email: info@krupniczahotel.pl Leonardo Boutique Hotel ul. Świętej Gertrudy 12, 31-048 Kraków Tel: +48 12 2959100, +48 22 3462800 Grand Ascot ul. Józefa Szujskiego 4, 31-123 Kraków Tel: +48 12 446 76 00 Email: rezerwacja@grandascot.pl Amber Boutique Hotels ul. Garbarska 8-10, 31-131 Kraków Tel: +48 12 421 06 06 Email: office@hotel-amber.pl

Travel

Ticket prices, timetables, and city transport maps are available at www.mpk.krakow.pl. Timetables and connections can also be checked at jakdojade.pl.

Travel from the Main Station

Starting stops:

• Dworzec Główny Zachód - stop near Galeria Krakowska
• Teatr Słowackiego – tram stop
• Dworzec Główny Wschód - stop near MDA bus station

Stops near AGH UST:

• Czarnowiejska – bus stop
• AGH / UR – bus stop
• Plac Inwalidów – tram stop, access to AGH UST via Krakowski Park

Travel from the airport

Train travel:

• Starting station: Kraków Airport
• Destination station: Kraków Główny
• Travel time: 17 minutes
• Approximate ticket cost: 17.00 PLN

Local Attractions

Information on tourist attractions and current offerings can be found using:

• The Kraków City Internet Platform.
• Promotional brochures of Krakow in PDF format.
• Krakow's MUST SEE

Monday, 10 June

11:30 Registration + Coffee

Conceptual and Technical Definition of an EOSC Node

Main goal: Nodes’ typology definition + Areas of nodes description (what needs to be defined to have a full concept of a node
Outcome: common template to define a pilot EOSC Node (based on the areas of description)

Convener: Roksana Wilk (ACC Cyfronet AGH)

1 'Who is who' round table and workshop goals and objectives

Hands-on: Round table and the introductory slides on the current view on EOSC Nodes Federation.

2 What do we need to define a node? Node's description areas. (node typology, stakeholders, offering, RoP, architecture, business models etc.)

Hands-on: Common discussion on the pre-defined list of possible areas of description for an EOSC Node
Conceptual and Technical Definition of an EOSC Node:
What do we need to define a node? Node's description areas. (node typology, stakeholders, offering, RoP, architecture, business models etc.)

14:00 Lunch

3 EOSC Node's stakeholder typology, node's offering typology.

Hands-on: Split into 4 groups and work with the boards diving into the details of selected description areas. After one round of working in the groups per board - common discussion and summary of a possible way to describe chosen areas - > delivery of a template to describe a node.

16:20 Coffe Break

4 EOSC Node's typology and possible technical architecture (Minimum Viable Node technical architecture). Final remarks and summary documentation.

Hands-on: Split into 4 groups and work with the boards diving into the details of selected description areas. After one round of working in the groups per board - common discussion and summary of a possible way to describe chosen areas - > delivery of a template to describe a node.

20:00 Dinner out - MIĘDZYMIASTOWA Restaurant, Rynek Główny 34

Tuesday, 11 June

09:30 Registration + Coffee

Use cases definition

Main goal: Pilot Nodes classification and specification, integration roadmap

Outcome: definition of the pilot EOSC Node (according to the template), integration use cases (node-node) + integrations matrix (node - federation capability / service), and roadmap.

Conveners: Marta Gutierrez (EGI), Roksana Wilk (ACC Cyfronet AGH)

5 Technical descriptions of the Pilot EOSC Node according to the common template from day 1 (Instruct-ERIC, LifeWatch,, NI4OS, e-INFRA CZ, NFDI, ENVRI)

Hands-on: Working with the EOSC Node template inserted into the dedicated Google doc.

11:50 Coffee Break

6 Technical descriptions of the Pilot EOSC Node according to the common template from day 1 (CNB-CSIC, ENES, MetroFood-RI, CESSDA, EGI, PaN, FC4E)

Hands-on: Working with the EOSC Node template inserted into the dedicated Google doc.

14:00 Lunch

Integration use cases

Main goal: Pilot Nodes classification and specification, integration roadmap

Outcome: definition of the pilot EOSC Node (according to the template), integration use cases (node-node) + integrations matrix (node - federation capability / service), and roadmap.

Conveners: Marta Gutierrez (EGI), Roksana Wilk (ACC Cyfronet AGH)

7 Integrations with the EOSC Core and horizontal services (of the EU Node) and potential scaling scenarios using e-Infra nodes such as the EGI Node (which federating services will be integrated in what scope and for what resources)

Integration matrix per use case (pilot Node) with timeline build on top of it. Seeking for the scenarios of scaling up with the EGI Node.
Start with one showcase (ENES) and then everyone works with their own material (online - google doc).

16:20 Coffee Break

8 Integrations with the federating services and horizontal (of the EU Node) and potential scaling scenarios using e-Infra nodes such as the EGI Node (which Core services will be integrated in what scope and for what resources)

Integration matrix per use case (pilot Node) with timeline build on top of it. Seeking for the scenarios of scaling up with the EGI Node.
Start with one showcase (ENES) and then everyone works with their own material (online - google doc).

Wednesday, 12 June

09:30 Registration + Coffee

EOSC Node Federation

Goal: understand the connections between the nodes and possible integrations, extract the requirements for CORE (federating) services based on the integration plan

Outcome: Federation network for EOSC Beyond use cases, requirements for core (federating) services.

Convener: Marta Gutierrez (EGI)

9 Possible integrations and dependencies between Pilot EOSC Nodes (from EOSC Beyond and others gathered in the workshops)

‘Use case x Use case’ matrix where we mark possible integrations and express which federating services (who is the giver, who is the taker) might be the ground for it.

12:30 Coffee Break

Requirements for EOSC Core Services

Goal: understand the connections between the nodes and possible integrations, extract the requirements for CORE (federating) services based on the integration plan

Outcome: Federation network for EOSC Beyond use cases, requirements for core (federating) services.

Convener: Katarzyna Lechowska-Winiarz (ACC Cyfronet AGH)

10 Provider Portal, Service Monitoring, Service Accounting, Research Products Accounting

1. (40 mins max)
Mural for user stories per use case, everyone working on their own user stories (3-4 most important user stories in around 10 groups)
2. (as long as needed)
Short intro of all gathered user stories. One registered user story will work as a showcase.Then, 3-4 groups working on their own user stories. As a result, user stories should be splitted into high-level requirements for EOSC Core and available (horizontal) services from other candidate Nodes
3. (depending on the time given)
Requirement gathering via a dedicated spreadsheet. After polishing it will be moved to jira.

14:00 Lunch

11 AAI, Marketplace, Resource Catalogue, Order Management, Helpdesk, PiD Service

1. (40 mins max)
Mural for user stories per use case, everyone working on their own user stories (3-4 most important user stories in around 10 groups)
2. (as long as needed)
Short intro of all gathered user stories. One registered user story will work as a showcase.Then, 3-4 groups working on their own user stories. As a result, user stories should be splitted into high-level requirements for EOSC Core and available (horizontal) services from other candidate Nodes
3. (depending on the time given)
Requirement gathering via a dedicated spreadsheet. After polishing it will be moved to jira.

16:20 Coffee Break