Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.alexisdurieux
	1	+XWiki.mmorgan

Content

...	...	@@ -5,7 +5,7 @@
5	5	(% style="text-align: justify;" %)
6	6	= Data Proxy =
7	7
8		-The data-proxy allows you to access CSCS Object Swift storage as an authenticated ebrains user without requiring a Fenix account.
	8	+The data proxy allows you to access object storage (Swift) on the Fenix infrastructure as an authenticated EBRAINS user without a Fenix user account.
9	9	)))
10	10	)))
11	11
...	...	@@ -13,32 +13,35 @@
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 CSCS Swift storage.
	16	+The data proxy core is the application that acts as a proxy to the object storage (Swift).
17	17
18	18	(% style="text-align: justify;" %)
19	19	=== Object Storage ===
20	20
	21	+The documentation of Swift object storage can be found here:
21	21
22		-The documentation on the swift object storage can be found here: [[https:~~/~~/docs.openstack.org/swift/pike/admin/objectstorage-intro.html>>https://docs.openstack.org/swift/pike/admin/objectstorage-intro.html]]
	23	+[[https:~~/~~/docs.openstack.org/swift/pike/admin/objectstorage-intro.html>>https://docs.openstack.org/swift/pike/admin/objectstorage-intro.html]]
23	23
24		-
25	25	(% style="text-align: justify;" %)
26	26	=== Authentication ===
27	27
28	28	(% style="text-align: justify;" %)
29		-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
	29	+The Data Proxy authenticates its users with the EBRAINS (Collaboratory) IAM service.
30	30
31	31	(% style="text-align: justify;" %)
32		-=== Bucket system ===
	32	+Prior to the availability of the Data Proxy, EBRAINS users had to request a Fenix user account in order to access object storage capabilities on the Fenix infrastructure. With the Data Proxy, a user only needs to have an EBRAINS account to access the data stored on the same Fenix object storage. Data stored in this way is held in the name of the data proxy service account on Fenix, and the Data Proxy tracks who has access to which data.
33	33
34	34	(% style="text-align: justify;" %)
35		-We use the Collaboratory authorization system for the buckets.
	35	+=== Permissions ===
36	36
37	37	(% style="text-align: justify;" %)
38		-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
	38	+We use the Collaboratory authorization system to manage permissions in the Data Proxy.
39	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	+
40	40	(% border="3" %)
41		-|=(% style="text-align: justify;" %)Collab Right|=(% style="text-align: justify;" %)Available actions on bucket
	44	+|=(% style="text-align: justify;" %)Team permissions of a collab|=(% style="text-align: justify;" %)Available actions on that collab's bucket
42	42	|(% style="text-align:justify" %)Viewer|(% style="text-align:justify" %)Read
43	43	|(% style="text-align:justify" %)Editor|(% style="text-align:justify" %)Create, Read, Update, Delete
44	44	|(% style="text-align:justify" %)Admin|(% style="text-align:justify" %)Create, Read, Update, Delete
...	...	@@ -45,10 +45,14 @@
45	45	|(% style="text-align:justify" %)Not a collab member|(% style="text-align:justify" %)No actions
46	46
47	47	(% class="wikigeneratedid" %)
48		-You can access the buckets in the "Buckets" menu in every collab
	51	+You can access the buckets in the "Bucket" navigation element in every collab.
49	49
50		-=== ===
	53	+=== Collaboratory bucket vs drive ===
51	51
52		-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".
	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.
53	53	)))
54	54	)))