Job workload data and transaction logs for the eBlocBroker

<strong>* What is eBlocBroker?</strong> eBlocBroker is a blockchain based autonomous computational resource broker. <strong>* Job workload data and transaction logs for the eBlocBroker</strong> This repository contains job workload data and test results for the paper titled: <em>"eBlocBroker: A Blockchain Based Autonomous Computational Resource Broker"</em>. eBlocBroker and its driver programs are available from the following GitHub repository: https://github.com/ebloc/ebloc-broker. 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: 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 cppr (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. The NAS Parallel Benchmarks, 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. 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. <strong>** Transactions are taken from bloxberg (https://blockexplorer.bloxberg.org)</strong> - Transactions deployed on the eBlocBroker Smart Contract:<br> https://blockexplorer.bloxberg.org/address/0xa0Fac3232234478E6A0d4d5564ed239c956A21f0/transactions - Transactions of the <em>provider0_0x29e613B04125c16db3f3613563bFdd0BA24Cb629</em><br> <em>- </em>Transactions of the <em>provider1_0x1926b36af775e1312fdebcc46303ecae50d945af</em><br> - Transactions of the<em> provider2_0x4934a70Ba8c1C3aCFA72E809118BDd9048563A24</em> <br> - Transactions of the <em>provider3_0x51e2b36469cdbf58863db70cc38652da84d20c67</em> <strong>* Files</strong> Each provider contains <em>eudat, gdrive, ipfs, and ipfs_gpg </em>folders that contains the patch results that obtained from the named cloud storage. $ tree -L 2 .<br> ├── README.org<br> ├── base_test_eblocbroker<br> │ ├── NPB3.3-SER_source_code<br> │ ├── README.md<br> │ ├── _cppr<br> │ ├── cppr<br> │ ├── cppr_example.sh<br> │ ├── datasets<br> │ ├── run_cppr<br> │ ├── setup.sh<br> │ └── test_data<br> ├── check_list.org<br> ├── provider0_0x29e613B04125c16db3f3613563bFdd0BA24Cb629<br> │ ├── ebloc-broker<br> │ ├── eudat<br> │ ├── gdrive<br> │ ├── ipfs<br> │ ├── ipfs_gpg<br> │ ├── jobs_info_0x29e613b04125c16db3f3613563bfdd0ba24cb629.out<br> │ ├── result_ipfs_hashes.txt<br> │ ├── transactions_0x29e613B04125c16db3f3613563bFdd0BA24Cb629.csv<br> │ └── watch_0x29e613b04125c16db3f3613563bfdd0ba24cb629.out<br> ├── provider1_0x1926b36af775e1312fdebcc46303ecae50d945af<br> │ ├── ebloc-broker<br> │ ├── eudat<br> │ ├── gdrive<br> │ ├── ipfs<br> │ ├── ipfs_gpg<br> │ ├── jobs_info_0x1926b36af775e1312fdebcc46303ecae50d945af.out<br> │ ├── result_ipfs_hashes.txt<br> │ ├── transactions_0x1926b36af775e1312fdebcc46303ecae50d945af.csv<br> │ └── watch_0x1926b36af775e1312fdebcc46303ecae50d945af.out<br> ├── provider2_0x4934a70Ba8c1C3aCFA72E809118BDd9048563A24<br> │ ├── ebloc-broker<br> │ ├── eudat<br> │ ├── ipfs<br> │ ├── ipfs_gpg<br> │ ├── jobs_info_0x4934a70ba8c1c3acfa72e809118bdd9048563a24.out<br> │ ├── result_ipfs_hashes.txt<br> │ ├── transactions_0x4934a70Ba8c1C3aCFA72E809118BDd9048563A24.csv<br> │ └── watch_0x4934a70ba8c1c3acfa72e809118bdd9048563a24.out<br> ├── provider3_0x51e2b36469cdbf58863db70cc38652da84d20c67<br> │ ├── ebloc-broker<br> │ ├── eudat<br> │ ├── gdrive<br> │ ├── ipfs<br> │ ├── ipfs_gpg<br> │ ├── jobs_info_0x51e2b36469cdbf58863db70cc38652da84d20c67.out<br> │ ├── result_ipfs_hashes.txt<br> │ ├── transactions_0x51e2b36469cdbf58863db70cc38652da84d20c67.csv<br> │ └── watch_0x51e2b36469cdbf58863db70cc38652da84d20c67.out<br> ├── requesters<br> │ ├── ebloc-broker-logs<br> │ └── gdrive<br> └── transactions_contract_0xa0Fac3232234478E6A0d4d5564ed239c956A21f0.csv