zenodoopen

Job workload data and transaction logs for the eBlocBroker

* What is eBlocBroker? eBlocBroker is a blockchain based autonomous computational resource broker. * Job workload data and transaction logs for the eBlocBroker This repository contains job workload data and test results for the paper titled:  "eBlocBroker: A Blockchain Based Autonomous Computational Resource Broker". eBlocBroker and its driver programs are available from the following GitHub repository: <a href="https://github.com/ebloc/ebloc-broker">https://github.com/ebloc/ebloc-broker</a>. We first deployed our eBlocBroker contract on bloxberg. Then we tested eBlocBroker and the robustness of our Python scripts that allow provider and requester nodes to interact with each other through eBlocBroker and cloud storage services using two types of synthetic CPU workloads explained as follows: <ol> <li>This workload helps to test running source code in combination with already cached and not cached datasets on the provider. As the   source code, the <a href="https://dl.acm.org/doi/abs/10.1145/3330481">cppr</a> (colored parallel rush-relabel algorithm) is used, which runs with additional datasets. Three cppr processes run one after another with different randomly selected datasets. All four providers have the same 12 medium-size datasets, of which only 3 distinct ones from each other have lower prices. Two data files are the provider’s registered data, and one is from the requester’s local storage.</li> <li>The <a href="https://www.nas.nasa.gov/software/npb.html">NAS Parallel Benchmarks</a>, a small group of programs targeting the performance evaluation of parallel supercomputers. One of the NAS serialized benchmarks in Class B (Block Tridiagonal solver, Scalar Pentadiagonal solver, Unstructured Adaptive mesh, and Lower-Upper Gauss-Seidel solver) is selected randomly. Since providers’ prices are the same, the calculated cost for NAS jobs will be the same for all providers.</li> </ol> In the test, our helper Python script maintains one hundred synthetic requesters within the requester node continually submit the following chosen workload randomly for 14 hours and 30 minutes. This record provides logs of clusters and clients, results of the submitted jobs on each cluster that is either completed of failed and their gained and returned fees, logs of the submitted jobs and their transaction hashes, and Slurm's job submission information, which are generated by the Driver programs. ** Transactions are taken from bloxberg (<a href="https://blockexplorer.bloxberg.org">https://blockexplorer.bloxberg.org</a>) - Transactions deployed on the eBlocBroker Smart Contract: <a href="https://blockexplorer.bloxberg.org/address/0xa0Fac3232234478E6A0d4d5564ed239c956A21f0/transactions">https://blockexplorer.bloxberg.org/address/0xa0Fac3232234478E6A0d4d5564ed239c956A21f0/transactions</a> - <a href="https://blockexplorer.bloxberg.org/address/0x29e613B04125c16db3f3613563bFdd0BA24Cb629/transactions">Transactions of the provider0_0x29e613B04125c16db3f3613563bFdd0BA24Cb629</a> - <a href="https://blockexplorer.bloxberg.org/address/0x1926b36af775e1312fdebcc46303ecae50d945af/transactions">Transactions of the provider1_0x1926b36af775e1312fdebcc46303ecae50d945af</a> - <a href="https://blockexplorer.bloxberg.org/address/0x4934a70Ba8c1C3aCFA72E809118BDd9048563A24/transactions">Transactions of the provider2_0x4934a70Ba8c1C3aCFA72E809118BDd9048563A24</a>   - <a href="https://blockexplorer.bloxberg.org/address/0x51e2b36469cdbf58863db70cc38652da84d20c67/transactions">Transactions of the provider3_0x51e2b36469cdbf58863db70cc38652da84d20c67</a>   * Files Each provider contains eudat, gdrive, ipfs, and ipfs_gpg folders that contains the patch results that obtained from the named cloud storage. $ tree -L 2 . ├── README.org ├── base_test_eblocbroker │   ├── NPB3.3-SER_source_code │   ├── README.md │   ├── _cppr │   ├── cppr │   ├── cppr_example.sh │   ├── datasets │   ├── run_cppr │   ├── setup.sh │   └── test_data ├── check_list.org ├── provider0_0x29e613B04125c16db3f3613563bFdd0BA24Cb629 │   ├── ebloc-broker │   ├── eudat │   ├── gdrive │   ├── ipfs │   ├── ipfs_gpg │   ├── jobs_info_0x29e613b04125c16db3f3613563bfdd0ba24cb629.out │   ├── result_ipfs_hashes.txt │   ├── transactions_0x29e613B04125c16db3f3613563bFdd0BA24Cb629.csv │   └── watch_0x29e613b04125c16db3f3613563bfdd0ba24cb629.out ├── provider1_0x1926b36af775e1312fdebcc46303ecae50d945af │   ├── ebloc-broker │   ├── eudat │   ├── gdrive │   ├── ipfs │   ├── ipfs_gpg │   ├── jobs_info_0x1926b36af775e1312fdebcc46303ecae50d945af.out │   ├── result_ipfs_hashes.txt │   ├── transactions_0x1926b36af775e1312fdebcc46303ecae50d945af.csv │   └── watch_0x1926b36af775e1312fdebcc46303ecae50d945af.out ├── provider2_0x4934a70Ba8c1C3aCFA72E809118BDd9048563A24 │   ├── ebloc-broker │   ├── eudat │   ├── ipfs │   ├── ipfs_gpg │   ├── jobs_info_0x4934a70ba8c1c3acfa72e809118bdd9048563a24.out │   ├── result_ipfs_hashes.txt │   ├── transactions_0x4934a70Ba8c1C3aCFA72E809118BDd9048563A24.csv │   └── watch_0x4934a70ba8c1c3acfa72e809118bdd9048563a24.out ├── provider3_0x51e2b36469cdbf58863db70cc38652da84d20c67 │   ├── ebloc-broker │   ├── eudat │   ├── gdrive │   ├── ipfs │   ├── ipfs_gpg │   ├── jobs_info_0x51e2b36469cdbf58863db70cc38652da84d20c67.out │   ├── result_ipfs_hashes.txt │   ├── transactions_0x51e2b36469cdbf58863db70cc38652da84d20c67.csv │   └── watch_0x51e2b36469cdbf58863db70cc38652da84d20c67.out ├── requesters │   ├── ebloc-broker-logs │   └── gdrive └── transactions_contract_0xa0Fac3232234478E6A0d4d5564ed239c956A21f0.csv

ShareScore

40/100

Overall dataset sharing score

Score breakdown

These five areas show where the dataset supports — or may limit — practical reuse.

Stewardship: 8
Harmonization: 4
Access: 16
Reuse readiness: 8
Engagement: 4

Topics

Blockchain, Ethereum, Smart contracts, Cloud computing, Cost model, Resource broker