Roles definition on CopPhil
Roles allow you to access different features of CopPhil cloud, such as JupyterHub.
Roles (access and quota for Edge Services) can be assigned only to an organization (a group of users).
A user can be assigned only to one organization.
If a user exceeds in the usage of one service, the sanctions will be applied to all users assigned to the given organization.
Access roles
eodata
| # | role name | role type | service | description |
|---|---|---|---|---|
| 1 | copphil-registered | access | eodata | Role for all registered users. Can view and download EO data (Data Explorer, Zipper, S3). No access to JupyterLab. |
| 2 | full-access | access | eodata | Role giving rights to view and download additional EO datasets, if there are any. As of 19.12.2024 there are no additional datasets and this role is currently used only by EO Team. |
Note
All members of an organization on CopPhil automatically are assigned the lowest access role, copphil-registered.
Users that aren’t registered to the CopPhil platform are allowed to search for the data, but with no download option.
Quota Roles
eodata
| # | role name |
role type |
service | S3 Endpoint request rate [req/minute] |
Zipper session limit* |
bandwidth limit per connection [MBps] |
monthly transfer rate [TB/month] |
|---|---|---|---|---|---|---|---|
| 1 | eodata-low | quota | eodata | 400 | 1 | 20 | 6 |
| 2 | eodata-medium | quota | eodata | 2000 | 1 | 100 | 50 |
| 3 | eodata-high | quota | eodata | 8000 | 1 | 500 | 100 |
| 4 | eodata-full-access-limits | quota | eodata | 1,000,000 | 1 | 100,000 | 10,000 |
by default will be set to 1 simultaneous download session for each user
Note
By default, lowest quota role will be assigned to users. It can be changed via role request.
JupyterLab Roles
access
| # | role name | role type | service | description |
|---|---|---|---|---|
| 1 | jupyter | access | jupyter | Role giving access to JupyterLab. |
quota
| # | role name |
role type |
service | cores | ram mb |
description |
|---|---|---|---|---|---|---|
| 1 | jupyter-low | quota | low | 2 | 4000 | Low quota Jupyter Service. Consists of 2 cores and 4 GB RAM. |
| 2 | jupyter-high | quota | jupyter | 12 | 32000 | High quota for Jupyter Service. Consists of 12 cores and 32 GB RAM. |
Role jupyter-high role will not be assigned until PhilSA decides that they need it. At present, only jupyter-low role is available in MyServices.
User with role jupyter-high can choose both flavors (low or high).
Logging to JupyterLab without organization
For JupyterLab, you have to request a role. To request a role, you have to first become a member of organization.
You will get a message like this when trying to use JupyterLab without the appropriate role:
Limiting roles
Roles assigned when monthly transfer rate is exceeded.
This role is not available to request in MyServices CopPhil.
| # | role name |
role type |
service | S3 Endpoint request rate [req/minute] |
Zipper session limit* |
bandwidth limit per connection [MBps] |
monthly transfer rate [TB/month] |
|---|---|---|---|---|---|---|---|
| 1 | eodata-access-limited | eodata | 400 | 1 | 1 | 100 |
Requesting another role
New user starts with these roles copphil-registered and eodata-low:
However, the user can get more roles:
For instructions how to upgrade a role, see How to request for roles on CopPhil
What To Do Next
For more on JupyterLab, see Introduction to JupyterLab on CopPhil
To get access to EODATA, How to get credentials to access EODATA on CopPhil
To use EODATA through JupyterLab, see a series of articles Getting started with EO data and Monitoring, analyzing, processing.