This repository has been archived by the owner on Feb 8, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 11
/
README
146 lines (119 loc) · 5.58 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
Copyright: (c) 2020 - 2021 Seagate Technology LLC and/or its its Affiliates,
All Rights Reserved
1. Build MIO library
Uncompress the source code package.
Run the following steps to build MIO library and examples.
(1) ./autogen.sh
(2) ./configure
if you install Motr rpms in a customized directory such as your home
directory or build Motr from source, run configure like this
./configure --with-libmotr=libmotr_directory --with-motr-headers=motr_headers_directory
if you have Motr source and want to build MIO with the source code, run
configure as below:
./configure --with-motr-src=motr_source_directory
(3) make
2. Run MIO examples
MIO source code is shipped with varied examples.
mio_rw_threads starts specified number of READ/WRITE threads. WRITE threads
create MIO objects and write data to them, and then inform the READ trheads
to read the written objects. READ threads will verify the data fetched from
objects.
Run mio_rw_threads following the steps below:
(1) Start Motr (follow the Cortx-motr instruction)
(2) cd tests
MIO provides a sample configuration file mio_config.yaml in this directory.
Edit mio_config.yaml to reflect Motr configurations in your system:
(a) replace the Motr client local address, MOTR_INST_ADDR, to yours.
(b) replace MOTR_HA_ADDR with your HA address.
(c) MOTR_PROFILE and MOTR_PROCESS_FID (usually no need to change these 2 parameters)
(d) replace the MOTR_USER_GROUP with the Motr user group in your system.
(e) To turn on ADDB for telemetry data generation, set MIO_TELEMETRY_STORE to
ADDB.
Methods to get the above parameters:
(a) hctl motr status
(b) checkout /etc/motr/sys-*/conf.xc to search strings for M0_CST_HA
(c) if your system is shipped with Motr sample apps, run
motr-sample-app-dir/scripts/c0appzrcgen
(3) add your account to Motr group then run mio_rw_thread
or run it as root
sudo ../examples/mio_rw_threads -s 4096 -c 1 -n 10 -t 1 -y ./mio_config.yaml -o 1:12346800
Usage of mio_rw_thread
-o, --object FID Starting object ID
-n, --nr_objs INT The number of objects
-s, --block-size INT block size in bytes or with suffix b/k/m/g/K/M/G
-c, --block-count INT number of blocks written to an object with suffix b/k/m/g/K/M/G
-t, --threads Number of threads
-y, --mio_conf MIO YAML configuration file
-h, --help shows this help text and exit
All MIO examples use 2 uint64_t to represent an object ID.
(4) MIO also provides with test scripts to test basic functionalities.
Run the scripts as root or users of Motr group as above.
sudo ./mio_run_tests.sh
(5) Quick Tests on Sage platform
>>cd gitlab/mio/
>>git pull
>>./autogen.sh
>>./configure
>>make
>>cd tests/
>>motraddr.sh --mio > mio_config.yaml
>> ../examples/mio_rw_threads -s 4096 -c 1 -n 10 -t 1 -y ./mio_config.yaml -o 1:12346800
a:12346800 7750c5e4c1549d15bdbc9690587f0c8b 7750c5e4c1549d15bdbc9690587f0c8b
9:12346800 cf99430f1feb3b7fa3eb03e396fc509a cf99430f1feb3b7fa3eb03e396fc509a
8:12346800 f22766e0ae86c0d0777747835b749390 f22766e0ae86c0d0777747835b749390
7:12346800 23ba669b5ac4478682f273a13f5db5d6 23ba669b5ac4478682f273a13f5db5d6
6:12346800 528f642a32ef56c36f987049ac42e46c 528f642a32ef56c36f987049ac42e46c
5:12346800 d8b5aea301d4e653e7ebd610fcf56a2f d8b5aea301d4e653e7ebd610fcf56a2f
4:12346800 d6f35954ae4a33961d1e8809000f4d59 d6f35954ae4a33961d1e8809000f4d59
3:12346800 e302c06452fd87119c996fa911373894 e302c06452fd87119c996fa911373894
2:12346800 a133a792799f49fe7807c34fc25d393c a133a792799f49fe7807c34fc25d393c
1:12346800 f3a95aeb5b0005ca305999bac7a75577 f3a95aeb5b0005ca305999bac7a75577
[Final Report] Objects TODO: 10 Completed: 10 Failed: 0 Matched: 10
#
# m0composite
# needed for composite object tests. needs to be runs only once.
# run it anyway and ignore failures.
#
>>motraddr.sh --exp > out.txt
>>cat out.txt
# umanesan1 client-22
# Bash shell export format
export CLIENT_LADDR="172.18.1.22@o2ib:12345:4:8"
export CLIENT_HA_ADDR="172.18.1.21@o2ib:12345:1:1"
export CLIENT_PROFILE="0x7000000000000001:0x4dc"
export CLIENT_PROC_FID="0x7200000000000001:0x151"
>>source ./out.txt
>>m0composite "$CLIENT_LADDR" "$CLIENT_HA_ADDR" "$CLIENT_PROFILE" "$CLIENT_PROC_FID"
motr[26256]: 7bd0 ERROR [dix/req.c:794:dix_idxop_meta_update_ast_cb] All items are failed
motr[26256]: 5bd0 ERROR [dix/req.c:794:dix_idxop_meta_update_ast_cb] All items are failed
>>motraddr.sh --mio > mio_config_p1.yaml
>>motraddr.sh --mio > mio_config_p2.yaml
>>motraddr.sh --mio > mio_config_p3.yaml
>>cat *.yaml | grep MOTR_INST_ADDR
MOTR_INST_ADDR: 172.18.1.22@o2ib:12345:4:10
MOTR_INST_ADDR: 172.18.1.22@o2ib:12345:4:14
MOTR_INST_ADDR: 172.18.1.22@o2ib:12345:4:3
MOTR_INST_ADDR: 172.18.1.22@o2ib:12345:4:8
>>../examples/mio_comp_obj_example -o 1:123456 -y ./mio_config.yaml
>>./mio_run_tests.sh
/home/users/jusers/umanesan1/sage/gitlab/mio/tests
/home/users/jusers/umanesan1/sage/gitlab/mio
/home/users/jusers/umanesan1/sage/gitlab/mio/examples/
MIO tests start:
Test log will be stored in /home/users/jusers/umanesan1/sage/gitlab/mio/tests/mio_test_sandbox_2021-01-06-12-48-22/mio_test_2021-01-06-12-48-22.log.
[T1] Object creation and deletion tests
io_create_delete_test: passed
[T2] Object IO tests
io_test_with_sizes_of_multi_4KB: passed
io_test_with_sizes_of_multi_non_4KB: passed
io_test_in_async: passed
io_test_obj_rw_with_lock: passed
io_test_with_multi_threads: passed
io_test_with_multi_procs: passed
[T3] KVS tests
kvs_create_query_delete_test: passed
[T4] Composite object tests
comp_obj_test: passed
[T5] Object hint tests
obj_hint_test: passed
mio_run_tests: test status: SUCCESS