Changes for page Data Proxy & Human Data Gateway
Last modified by alexisdurieux on 2022/03/25 08:38
From version 20.1
edited by mmorgan
on 2021/04/12 16:58
on 2021/04/12 16:58
Change comment:
There is no comment for this version
To version 14.1
edited by alexisdurieux
on 2021/04/06 14:45
on 2021/04/06 14:45
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
-
Objects (1 modified, 0 added, 2 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. mmorgan1 +XWiki.alexisdurieux - Content
-
... ... @@ -5,7 +5,7 @@ 5 5 (% style="text-align: justify;" %) 6 6 = Data Proxy = 7 7 8 - The data proxy allows youto access objectstorage (Swift)onthe Fenix infrastructureas anauthenticated EBRAINS user without a Fenix user account.8 +Functional documentation 9 9 ))) 10 10 ))) 11 11 ... ... @@ -13,35 +13,25 @@ 13 13 ((( 14 14 ((( 15 15 (% style="text-align: justify;" %) 16 -The data proxy core is the application that acts as a proxy to the object storage(Swift).16 +The data proxy core is the application that acts as a proxy to the CSCS Swift storage. 17 17 18 18 (% style="text-align: justify;" %) 19 -=== ObjectStorage===19 +==== Authentication ==== 20 20 21 -The documentation of Swift object storage can be found here: 22 - 23 -[[https:~~/~~/docs.openstack.org/swift/pike/admin/objectstorage-intro.html>>https://docs.openstack.org/swift/pike/admin/objectstorage-intro.html]] 24 - 25 25 (% style="text-align: justify;" %) 26 - ===Authentication===22 +The application itself is connected to the CSCS storage. The user is authenticated against the data-proxy application using authorization headers. The user is then authenticated against the EBRAINS platform. That means the user only needs to have an EBRAINS account to access the data proxy and the Swift storage capabilities 27 27 28 28 (% style="text-align: justify;" %) 29 - TheData Proxy authenticates itsuserswith theEBRAINS (Collaboratory) IAM service.25 +=== Bucket system === 30 30 31 31 (% style="text-align: justify;" %) 32 - Prior to theavailability of the Data Proxy, EBRAINSusershadto requesta Fenix user account in order toaccess object storage capabilitieson the Fenix infrastructure. With the Data Proxy,aser only needstohave an EBRAINS account to access the data stored on the same Fenix object storage. Data storedinthiswayisheld inthenameofthe data proxy serviceaccounton Fenix, and theData Proxy tracks who has accessto which data.28 +We use the Collaboratory authorization system for the buckets. 33 33 34 34 (% style="text-align: justify;" %) 35 - ===Permissions===31 +For every collab, it is possible to access a Swift container as a user. The action the user can perform on the buckets depend on the rights the user has in the collab 36 36 37 -(% style="text-align: justify;" %) 38 -We use the Collaboratory authorization system to manage permissions in the Data Proxy. 39 - 40 -(% style="text-align: justify;" %) 41 -A Swift object container can be associated to each collab. Object containers are also known as "buckets" to avoid confusion with other containers (e.g. Docker containers). An EBRAINS user can perform the following actions on a bucket depending on the user's permissions (as defined by the collab's Team) in the collab associated with the bucket. 42 - 43 43 (% border="3" %) 44 -|=(% style="text-align: justify;" %) Team permissions of a collab|=(% style="text-align: justify;" %)Available actions onthat collab's bucket34 +|=(% style="text-align: justify;" %)Collab Right|=(% style="text-align: justify;" %)Available actions on bucket 45 45 |(% style="text-align:justify" %)Viewer|(% style="text-align:justify" %)Read 46 46 |(% style="text-align:justify" %)Editor|(% style="text-align:justify" %)Create, Read, Update, Delete 47 47 |(% style="text-align:justify" %)Admin|(% style="text-align:justify" %)Create, Read, Update, Delete ... ... @@ -48,14 +48,11 @@ 48 48 |(% style="text-align:justify" %)Not a collab member|(% style="text-align:justify" %)No actions 49 49 50 50 (% class="wikigeneratedid" %) 51 -You can access the buckets in the "Bucket" navigation elementin every collab.41 +You can access the buckets in the "Buckets" menu in every collab 52 52 53 -=== Collaboratory bucket vs drive === 43 +(% class="wikigeneratedid" %) 44 +=== === 54 54 55 -A collab offers 2 main locations to store files: a drive and a bucket. The drive offers more advanced features like recognition of file formats (Office, Markdown, PDF) with applications specific to each, simplified version control, smart links. The bucket on the other hand offers larger storage capacity and better bandwidth. The bucket is recommended for datasets (brain scans, EEG, derived data) and videos (including for streaming). 56 - 57 -=== API === 58 - 59 -The API is self-documented using Swagger UI. You can access it here: [[https:~~/~~/data-proxy.ebrains.eu/api/docs>>https://data-proxy.ebrains.eu/api/docs]] or in the [[API Documentation>>doc:API Documentation]] wiki page of this collab. 46 +The API is self-documentated using Swagger UI. You can access it here: [[https:~~/~~/data-proxy.ebrains.eu/api/docs>>https://data-proxy.ebrains.eu/api/docs]] or in the "API Documentation". 60 60 ))) 61 61 )))
- Screenshot_2021-01-06 FastAPI - Swagger UI.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.alexisdurieux - Size
-
... ... @@ -1,0 +1,1 @@ 1 +38.4 KB - Content
- Collaboratory.Apps.Collab.Code.CollabClass[0]
-
- Public
-
... ... @@ -1,1 +1,1 @@ 1 - Yes1 +No
- XWiki.XWikiRights[3]
-
- Allow/Deny
-
... ... @@ -1,1 +1,0 @@ 1 -Allow - Levels
-
... ... @@ -1,1 +1,0 @@ 1 -view - Users
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.XWikiGuest
- XWiki.XWikiRights[4]
-
- Allow/Deny
-
... ... @@ -1,1 +1,0 @@ 1 -Allow - Groups
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.XWikiAllGroup - Levels
-
... ... @@ -1,1 +1,0 @@ 1 -view