... | ... | @@ -15,12 +15,12 @@ For example: |
|
|
EUDATAuthZ("$userNameClient#$rodsZoneClient", *cmd, *args, *response);
|
|
|
}
|
|
|
}
|
|
|
The above code, placed in /_etc/irods/core.re_, will enforce the permission to execute external commands according to the assertions defined in the file _authZ.map.json_ described [here](https://github.com/EUDAT-B2SAFE/B2SAFE-core/wiki/Python-script-configuration).
|
|
|
By default the B2SAFE relies on this mechanism to filter the access to the python client for the operations related to the PIDs creation, update and delete. It is possible, for performance reasons (https://github.com/EUDAT-B2SAFE/B2SAFE-core/wiki/Documentation#performance), to disable it, setting the parameter _authzEnabled_ to "false" in the [_local.re_][1].
|
|
|
The above code, placed in /_etc/irods/core.re_, will enforce the permission to execute external commands according to the assertions defined in the file _authZ.map.json_ described [here](https://gitlab.eudat.eu/b2safe/B2SAFE-core/-/wikis/Python-script-configuration).
|
|
|
By default the B2SAFE relies on this mechanism to filter the access to the python client for the operations related to the PIDs creation, update and delete. It is possible, for performance reasons (https://gitlab.eudat.eu/b2safe/B2SAFE-core/-/wikis/Documentation#performance), to disable it, setting the parameter _authzEnabled_ to "false" in the [_local.re_][1].
|
|
|
|
|
|
## [Best Practices](https://github.com/EUDAT-B2SAFE/B2SAFE-core/wiki/Best-Practices)
|
|
|
## [Best Practices](https://gitlab.eudat.eu/b2safe/B2SAFE-core/-/wikis/Best-Practices)
|
|
|
|
|
|
## [Typical workflows](https://github.com/EUDAT-B2SAFE/B2SAFE-core/wiki/Workflows)
|
|
|
## [Typical workflows](https://gitlab.eudat.eu/b2safe/B2SAFE-core/-/wikis/Workflows)
|
|
|
|
|
|
## Performance
|
|
|
We can distinguish roughly two main tasks that have an impact on the performance: the data transfer and the PID registration. The former is heavily influenced by the bandwidth available for the transfer, the computing power available for the checksum calculation, which is mandatory to spot data corruption, the number and the average size of the objects and the back-end storage speed in terms of read and write operations.
|
... | ... | @@ -47,8 +47,8 @@ Therefore while it does not make sense here to provide figures for the data tran |
|
|
The current PID registry system in EUDAT is based on the [HANDLE system version 8](https://www.handle.net/download_hnr.html) (HSv8). And B2SAFE relies on the [B2HANDLE library][2] to interact with it:
|
|
|
|
|
|
- install b2handle library
|
|
|
- create private/public keys, certificates and interacts with the PID registry administrator to get the public key uploaded (see [here](https://github.com/EUDAT-B2SAFE/B2SAFE-core/blob/master/install.txt))
|
|
|
- see the configuration of the credentials [here](https://github.com/EUDAT-B2SAFE/B2SAFE-core/wiki/Python-script-configuration)
|
|
|
- create private/public keys, certificates and interacts with the PID registry administrator to get the public key uploaded (see [here](https://gitlab.eudat.eu/b2safe/B2SAFE-core/-/blob/master/install_centos7.md) and [here](https://gitlab.eudat.eu/b2safe/B2SAFE-core/-/blob/master/install_other.txt))
|
|
|
- see the configuration of the credentials [here](https://gitlab.eudat.eu/b2safe/B2SAFE-core/-/wikis/Python-script-configuration)
|
|
|
|
|
|
- test _epicclient2.py_:
|
|
|
```
|
... | ... | @@ -60,5 +60,5 @@ Experimental features |
|
|
---------------
|
|
|
### [Metadata management](https://github.com/EUDAT-B2SAFE/B2SAFE-metadata/wiki)
|
|
|
|
|
|
[1]: https://github.com/EUDAT-B2SAFE/B2SAFE-core/wiki/Rule-set-configuration "local.re"
|
|
|
[1]: https://gitlab.eudat.eu/b2safe/B2SAFE-core/-/wikis/Rule-set-configuration "local.re"
|
|
|
[2]: https://github.com/EUDAT-B2SAFE/B2HANDLE/releases/latest "B2HANDLE library" |
|
|
\ No newline at end of file |