페이지 트리

버전 비교

  • 이 줄이 추가되었습니다.
  • 이 줄이 삭제되었습니다.
  • 서식이 변경되었습니다.

...

  • Application and data catalogue portal with compute integration: DIRAC

  • Metadata catalogue for high-level data: DIRACB2Find

  • Metadata catalgue catalogue for low-level data: B2FindDirac

  • Remote compute Compute resources: EISCAT, EGI HTC, EGI Cloud, institutional clouds (e.g. at CSC)

  • Data storage and transfer (antennas→compute/data data→compute centres): B2STAGE

  • User SSO: B2Access and EGI CheckIn and B2Access


No.

User stories

US1

A Any researcher should be able to authenticate within access the EISCAT_3D portal and the browse metadata. The portal grants/denies access to data and processing based on national affiliation. (researchers from EISCAT_3D member states can access the portal).

US2

Authenticated Authorised researchers should be able to browse select the EISCAT_3D data at different levels, query the data and select the data they are interested in for download or for online analysis.

...US3

Authenticated Authorised researchers should be able to browse reference applications in the portal, select an application for use, feed their data in (from US2), visualise or download the analysis result.

...

Step

Description of action

Dependency on 3rd party services (EOSC-hub or other)

UC1

Authentication:

  1. User logs enters into the portal......
  2. Portal directs to SSO
  3. Portal grants authorisation
  1. Portal is running with metadata and file catalogue
  2. EGICheckin <-> B2Access, EISCAT idp

UC2

Data access:

  1. ...

...

Computation:

  1. User selects data
  2. Portal accepts authorisation
  3. Portal directs to data store

  1. Dirac file catalogue
  2. dirac → sso
  3. Dirac

UC3

Computation:

  1. Data selected
  2. Software selected/uploaded
  3. Data staging at HPC
  4. Processing of data
  5. Results presented
  1. Dirac
  2. Dirac → HPC
  3. B2Stage
  4. HPC, VMs
  5. Visualisation, B2drop, B2share



Requirements

Technical Requirements

...

EOSC-hub AAI doesn’t support the Marine IdPEOSC-hub AAI should accept Marine IDsRQ1<Gap service> ….RQ2

Requirement ID

EOSC-hub service

GAP (Yes/No) + description

Requirement description

Source Use Case






ExampleRQ1

EOSC-hub AAI

Yes: Dirac

Dirac interface to EGICheckin

UC1

RQ2VMYes: VMVM for portalUC1
RQ3Data stagingYes: File systemFile storageUC3

RQ4

Cloud Compute

No

Create VMs ia a gateway

UC2

Yes: HPC

Run software

UC3

RQ5PID/DOI serviceYes: RegistryRegistration of collectionUC2,3


Capacity Requirements


EOSC-hub services

Amount of requested resources

Time period

Portal2 VMs30 yrs
Stage2 VMs 10 TB5 yrs
Processing2 VMs 10 cores5 yrs