페이지 이력

EOSC-hub AAI

B2DROP

Can be a central service; no need for local installation. User has no interface to B2DROP filesystem; currently user log in to jupyter with username and password. Files automatically moved to B2DROP without user intervention.

GAP: Need to integrate AAI to B2DROP . For training purposes, consider using a proxy user for training purposes.

Need to be able to write directly to B2DROP (via mount point inaccessible to users), or have the workflow copy data in using NextCloud OpenCloudMesh API.

Will require separate instances for training and production

UC4

Publishing files from an ECAS workspace to B2DROP will not require the user to log in to B2DROP separately. Aside from selecting files to publish and a destination folder, the user should also not be asked for additional information (e.g. metadata).

B2DROP must be able to understand and accept IAM security tokens provided by ECAS.

Possibly additional detail questions to clarify wrt session management (transparent authentication, selecting destination folder, initiating and confirming transfer as one seamless workflow).

GAP - UNSURE -

If data is moved using OpenCloudMesh, the security needs

to be considered. NextCloud website recommends using SSL since

user information is passed in plain text. Need to check how B2DROP

is configured.

GAP - NO (if RQ2 is satified), YES (otherwise)

Enable users to push files to B2SHARE. If RQ2 works

there is no gap to deal with as the bridge exists. Unless RQ2

works, then beed to integrate AAI to B2SHARE

GAP - UNCLEAR

Data publishing and data ingest. Allows contacting multiple communities.

GAP - UNCLEAR

Both input data and published derived data must be assigned a PID.

For third-party users to access provenance information, B2SHARE and

possibly also B2DROP need to support recording of minimal provenance

information, possibly organized via B2HANDLE profiles.