Browse Source

Update project links and package metadata

Change-Id: I7134ade3e8575bee474ce579c0ebd9959d48a2d8
tags/1.3.0^0
Ilya Shakhat 1 week ago
parent
commit
39942a642c
4 changed files with 66 additions and 56 deletions
  1. 2
    2
      README.rst
  2. 51
    51
      doc/source/catalog.rst
  3. 5
    1
      doc/source/contributing.rst
  4. 8
    2
      setup.cfg

+ 2
- 2
README.rst View File

@@ -64,6 +64,6 @@ Links
64 64
 -----
65 65
 * PyPi - https://pypi.org/project/pyshaker/
66 66
 * Docker - https://hub.docker.com/r/performa/shaker/
67
-* Docs - http://pyshaker.readthedocs.io/
68
-* Bugtracker - https://launchpad.net/shaker/
67
+* Docs - https://pyshaker.readthedocs.io/
68
+* Bugtracker - https://launchpad.net/shaker
69 69
 

+ 51
- 51
doc/source/catalog.rst View File

@@ -15,7 +15,7 @@ asks instances to retrieve the metadata. The scenario is used to load metadata
15 15
 processes.
16 16
 
17 17
 To use this scenario specify parameter ``--scenario misc/instance_metadata``.
18
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/misc/instance_metadata.yaml
18
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/misc/instance_metadata.yaml
19 19
 
20 20
 .. _scenario_openstack_l2_cross_az:
21 21
 
@@ -28,7 +28,7 @@ availability zones. The scenario is used to test throughput between `nova` and
28 28
 `vcenter` zones. The traffic goes within the tenant network (L2 domain).
29 29
 
30 30
 To use this scenario specify parameter ``--scenario openstack/cross_az/full_l2``.
31
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/full_l2.yaml
31
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/full_l2.yaml
32 32
 
33 33
 .. _scenario_openstack_l3_east_west_cross_az:
34 34
 
@@ -42,7 +42,7 @@ are in different availability zones. The scenario is used to test throughput
42 42
 between `nova` and `vcenter` zones.
43 43
 
44 44
 To use this scenario specify parameter ``--scenario openstack/cross_az/full_l3_east_west``.
45
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/full_l3_east_west.yaml
45
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/full_l3_east_west.yaml
46 46
 
47 47
 .. _scenario_openstack_l3_north_south_cross_az:
48 48
 
@@ -56,7 +56,7 @@ master and slave instances are in different availability zones. The scenario is
56 56
 used to test throughput between `nova` and `vcenter` zones.
57 57
 
58 58
 To use this scenario specify parameter ``--scenario openstack/cross_az/full_l3_north_south``.
59
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/full_l3_north_south.yaml
59
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/full_l3_north_south.yaml
60 60
 
61 61
 .. _scenario_openstack_l2_cross_az_performance:
62 62
 
@@ -68,7 +68,7 @@ slave instances are in different availability zones. The scenario is used to
68 68
 test throughput between `nova` and `vcenter` zones.
69 69
 
70 70
 To use this scenario specify parameter ``--scenario openstack/cross_az/perf_l2``.
71
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/perf_l2.yaml
71
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/perf_l2.yaml
72 72
 
73 73
 .. _scenario_openstack_l3_east_west_cross_az_performance:
74 74
 
@@ -81,7 +81,7 @@ east-west). The master and slave instances are in different availability zones.
81 81
 The scenario is used to test throughput between `nova` and `vcenter` zones.
82 82
 
83 83
 To use this scenario specify parameter ``--scenario openstack/cross_az/perf_l3_east_west``.
84
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/perf_l3_east_west.yaml
84
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/perf_l3_east_west.yaml
85 85
 
86 86
 .. _scenario_openstack_l3_north_south_cross_az_performance:
87 87
 
@@ -95,7 +95,7 @@ different availability zones. The scenario is used to test throughput between
95 95
 `nova` and `vcenter` zones.
96 96
 
97 97
 To use this scenario specify parameter ``--scenario openstack/cross_az/perf_l3_north_south``.
98
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/perf_l3_north_south.yaml
98
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/perf_l3_north_south.yaml
99 99
 
100 100
 .. _scenario_openstack_l2_cross_az_udp:
101 101
 
@@ -108,7 +108,7 @@ zones. The scenario is used to test throughput between `nova` and `vcenter`
108 108
 zones.
109 109
 
110 110
 To use this scenario specify parameter ``--scenario openstack/cross_az/udp_l2``.
111
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/udp_l2.yaml
111
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/udp_l2.yaml
112 112
 
113 113
 .. _scenario_openstack_l2_cross_az_udp_jumbo:
114 114
 
@@ -121,7 +121,7 @@ availability zones. The scenario is used to test throughput between `nova` and
121 121
 `vcenter` zones.
122 122
 
123 123
 To use this scenario specify parameter ``--scenario openstack/cross_az/udp_l2_mss8950``.
124
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/udp_l2_mss8950.yaml
124
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/udp_l2_mss8950.yaml
125 125
 
126 126
 .. _scenario_openstack_l3_east_west_cross_az_udp:
127 127
 
@@ -135,7 +135,7 @@ instances are in different availability zones. The scenario is used to test
135 135
 throughput between `nova` and `vcenter` zones.
136 136
 
137 137
 To use this scenario specify parameter ``--scenario openstack/cross_az/udp_l3_east_west``.
138
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/udp_l3_east_west.yaml
138
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/udp_l3_east_west.yaml
139 139
 
140 140
 .. _scenario_openstack_l2_dense:
141 141
 
@@ -146,7 +146,7 @@ node. Instances are plugged into the same tenant network. The traffic goes
146 146
 within the tenant network (L2 domain).
147 147
 
148 148
 To use this scenario specify parameter ``--scenario openstack/dense_l2``.
149
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/dense_l2.yaml
149
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/dense_l2.yaml
150 150
 
151 151
 .. _scenario_openstack_l3_east_west_dense:
152 152
 
@@ -157,7 +157,7 @@ Instances are connected to different tenant networks connected to one router.
157 157
 The traffic goes from one network to the other (L3 east-west).
158 158
 
159 159
 To use this scenario specify parameter ``--scenario openstack/dense_l3_east_west``.
160
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/dense_l3_east_west.yaml
160
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/dense_l3_east_west.yaml
161 161
 
162 162
 .. _scenario_openstack_l3_north_south_dense:
163 163
 
@@ -169,7 +169,7 @@ router. Instances in one of networks have floating IPs. The traffic goes from
169 169
 one network via external network to the other network.
170 170
 
171 171
 To use this scenario specify parameter ``--scenario openstack/dense_l3_north_south``.
172
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/dense_l3_north_south.yaml
172
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/dense_l3_north_south.yaml
173 173
 
174 174
 .. _scenario_openstack_l3_north_south_dense_to_external_target:
175 175
 
@@ -181,7 +181,7 @@ host. The host name needs to be provided as command-line parameter, e.g.
181 181
 ``--matrix "{host: 172.10.1.2}"``.
182 182
 
183 183
 To use this scenario specify parameter ``--scenario openstack/external/dense_l3_north_south_no_fip``.
184
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/external/dense_l3_north_south_no_fip.yaml
184
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/external/dense_l3_north_south_no_fip.yaml
185 185
 
186 186
 .. _scenario_openstack_l3_north_south_dense_to_external_target_with_floating_ip:
187 187
 
@@ -193,7 +193,7 @@ traffic is sent to and from external host. The host name needs to be provided
193 193
 as command-line parameter, e.g. ``--matrix "{host: 172.10.1.2}"``.
194 194
 
195 195
 To use this scenario specify parameter ``--scenario openstack/external/dense_l3_north_south_with_fip``.
196
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/external/dense_l3_north_south_with_fip.yaml
196
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/external/dense_l3_north_south_with_fip.yaml
197 197
 
198 198
 .. _scenario_openstack_l3_north_south_to_external_target:
199 199
 
@@ -206,7 +206,7 @@ host (L3 north-south). The host name needs to be provided as command-line
206 206
 parameter, e.g. ``--matrix "{host: 172.10.1.2}"``.
207 207
 
208 208
 To use this scenario specify parameter ``--scenario openstack/external/full_l3_north_south_no_fip``.
209
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/external/full_l3_north_south_no_fip.yaml
209
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/external/full_l3_north_south_no_fip.yaml
210 210
 
211 211
 .. _scenario_openstack_l3_north_south_to_external_target_with_floating_ip:
212 212
 
@@ -220,7 +220,7 @@ to be provided as command-line parameter, e.g. ``--matrix "{host:
220 220
 172.10.1.2}"``.
221 221
 
222 222
 To use this scenario specify parameter ``--scenario openstack/external/full_l3_north_south_with_fip``.
223
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/external/full_l3_north_south_with_fip.yaml
223
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/external/full_l3_north_south_with_fip.yaml
224 224
 
225 225
 .. _scenario_openstack_l3_north_south_performance_to_external_target:
226 226
 
@@ -232,7 +232,7 @@ of public iperf3 servers is used, to override this the target host can be
232 232
 provided as command-line parameter, e.g. ``--matrix "{host: 172.10.1.2}"``.
233 233
 
234 234
 To use this scenario specify parameter ``--scenario openstack/external/perf_l3_north_south_no_fip``.
235
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/external/perf_l3_north_south_no_fip.yaml
235
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/external/perf_l3_north_south_no_fip.yaml
236 236
 
237 237
 .. _scenario_openstack_l3_north_south_performance_to_external_target_with_floating_ip:
238 238
 
@@ -245,7 +245,7 @@ this the target host can be provided as command-line parameter, e.g. ``--matrix
245 245
 "{host: 172.10.1.2}"``.
246 246
 
247 247
 To use this scenario specify parameter ``--scenario openstack/external/perf_l3_north_south_with_fip``.
248
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/external/perf_l3_north_south_with_fip.yaml
248
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/external/perf_l3_north_south_with_fip.yaml
249 249
 
250 250
 .. _scenario_openstack_l2:
251 251
 
@@ -256,7 +256,7 @@ Every instance is hosted on a separate compute node, all available compute
256 256
 nodes are utilized. The traffic goes within the tenant network (L2 domain).
257 257
 
258 258
 To use this scenario specify parameter ``--scenario openstack/full_l2``.
259
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/full_l2.yaml
259
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/full_l2.yaml
260 260
 
261 261
 .. _scenario_openstack_l3_east_west:
262 262
 
@@ -268,7 +268,7 @@ to one of 2 tenant networks, which plugged into single router. The traffic goes
268 268
 from one network to the other (L3 east-west).
269 269
 
270 270
 To use this scenario specify parameter ``--scenario openstack/full_l3_east_west``.
271
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/full_l3_east_west.yaml
271
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/full_l3_east_west.yaml
272 272
 
273 273
 .. _scenario_openstack_l3_north_south:
274 274
 
@@ -280,7 +280,7 @@ connected to different routers, master accesses slave by floating ip. The
280 280
 traffic goes from one network via external network to the other network.
281 281
 
282 282
 To use this scenario specify parameter ``--scenario openstack/full_l3_north_south``.
283
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/full_l3_north_south.yaml
283
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/full_l3_north_south.yaml
284 284
 
285 285
 .. _scenario_openstack_l2_performance:
286 286
 
@@ -291,7 +291,7 @@ network. Each instance is hosted on a separate compute node. The traffic goes
291 291
 within the tenant network (L2 domain).
292 292
 
293 293
 To use this scenario specify parameter ``--scenario openstack/perf_l2``.
294
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/perf_l2.yaml
294
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/perf_l2.yaml
295 295
 
296 296
 .. _scenario_openstack_l3_east_west_performance:
297 297
 
@@ -303,7 +303,7 @@ plugged into single router. The traffic goes from one network to the other (L3
303 303
 east-west).
304 304
 
305 305
 To use this scenario specify parameter ``--scenario openstack/perf_l3_east_west``.
306
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/perf_l3_east_west.yaml
306
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/perf_l3_east_west.yaml
307 307
 
308 308
 .. _scenario_openstack_l3_north_south_performance:
309 309
 
@@ -315,7 +315,7 @@ master accesses slave by floating ip. The traffic goes from one network via
315 315
 external network to the other network.
316 316
 
317 317
 To use this scenario specify parameter ``--scenario openstack/perf_l3_north_south``.
318
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/perf_l3_north_south.yaml
318
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/perf_l3_north_south.yaml
319 319
 
320 320
 .. _scenario_openstack_l2_qos_performance:
321 321
 
@@ -327,7 +327,7 @@ within the tenant network (L2 domain). Neutron QoS feature is used to limit
327 327
 traffic throughput to 10 Mbit/s.
328 328
 
329 329
 To use this scenario specify parameter ``--scenario openstack/qos/perf_l2``.
330
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/qos/perf_l2.yaml
330
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/qos/perf_l2.yaml
331 331
 
332 332
 .. _scenario_openstack_l2_udp:
333 333
 
@@ -338,7 +338,7 @@ Every instance is hosted on a separate compute node. The traffic goes within
338 338
 the tenant network (L2 domain). The load is generated by UDP traffic.
339 339
 
340 340
 To use this scenario specify parameter ``--scenario openstack/udp_l2``.
341
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/udp_l2.yaml
341
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/udp_l2.yaml
342 342
 
343 343
 .. _scenario_openstack_l3_east_west_udp:
344 344
 
@@ -350,7 +350,7 @@ plugged into single router. The traffic goes from one network to the other (L3
350 350
 east-west). The load is generated by UDP traffic.
351 351
 
352 352
 To use this scenario specify parameter ``--scenario openstack/udp_l3_east_west``.
353
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/udp_l3_east_west.yaml
353
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/udp_l3_east_west.yaml
354 354
 
355 355
 .. _scenario_openstack_l3_north_south_udp:
356 356
 
@@ -362,7 +362,7 @@ accesses slave by floating ip. The traffic goes from one network via external
362 362
 network to the other network. The load is generated by UDP traffic.
363 363
 
364 364
 To use this scenario specify parameter ``--scenario openstack/udp_l3_north_south``.
365
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/udp_l3_north_south.yaml
365
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/udp_l3_north_south.yaml
366 366
 
367 367
 .. _scenario_ping:
368 368
 
@@ -375,7 +375,7 @@ The destination host can be overridden by command-line parameter, e.g.
375 375
 ``--matrix "{host: 172.10.1.2}"``.
376 376
 
377 377
 To use this scenario specify parameter ``--scenario spot/ping``.
378
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/spot/ping.yaml
378
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/spot/ping.yaml
379 379
 
380 380
 .. _scenario_tcp_bandwidth:
381 381
 
@@ -388,7 +388,7 @@ destination host can be overridden by command-line parameter, e.g. ``--matrix
388 388
 "{host: 172.10.1.2}"``.
389 389
 
390 390
 To use this scenario specify parameter ``--scenario spot/tcp``.
391
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/spot/tcp.yaml
391
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/spot/tcp.yaml
392 392
 
393 393
 .. _scenario_udp_bandwidth:
394 394
 
@@ -400,7 +400,7 @@ requires at least 10 000 packets per second. The destination host can be
400 400
 overridden by command-line parameter, e.g. ``--matrix "{host: 172.10.1.2}"``.
401 401
 
402 402
 To use this scenario specify parameter ``--scenario spot/udp``.
403
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/spot/udp.yaml
403
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/spot/udp.yaml
404 404
 
405 405
 .. _scenario_sample_tcp_test_with_advanced_iperf_arguments:
406 406
 
@@ -413,7 +413,7 @@ utilized. The traffic goes within the tenant network (L2 domain) and uses
413 413
 arguments not directly mapped by the iperf executor.
414 414
 
415 415
 To use this scenario specify parameter ``--scenario test/sample_with_advanced_iperf``.
416
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/test/sample_with_advanced_iperf.yaml
416
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/test/sample_with_advanced_iperf.yaml
417 417
 
418 418
 .. _scenario_sample_tcp_test_with_environment_file:
419 419
 
@@ -425,7 +425,7 @@ instance is hosted on a separate compute node, 1 compute node is utilized. The
425 425
 traffic goes within the tenant network (L2 domain)
426 426
 
427 427
 To use this scenario specify parameter ``--scenario test/sample_with_env``.
428
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/test/sample_with_env.yaml
428
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/test/sample_with_env.yaml
429 429
 
430 430
 .. _scenario_sample_tcp_test_with_support_stacks:
431 431
 
@@ -439,7 +439,7 @@ separate compute node, 1 compute node is utilized. The traffic goes within the
439 439
 tenant network (L2 domain)
440 440
 
441 441
 To use this scenario specify parameter ``--scenario test/sample_with_support_stacks``.
442
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/test/sample_with_support_stacks.yaml
442
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/test/sample_with_support_stacks.yaml
443 443
 
444 444
 .. _scenario_static_agents:
445 445
 
@@ -449,7 +449,7 @@ In this scenario Shaker runs tests in spot mode. The scenario can be used for
449 449
 Shaker integration testing.
450 450
 
451 451
 To use this scenario specify parameter ``--scenario test/spot``.
452
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/test/spot.yaml
452
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/test/spot.yaml
453 453
 
454 454
 .. _scenario_static_agents:
455 455
 
@@ -459,7 +459,7 @@ In this scenario Shaker runs tests on pre-deployed static agents. The scenario
459 459
 can be used for Shaker integration testing.
460 460
 
461 461
 To use this scenario specify parameter ``--scenario test/static_agent``.
462
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/test/static_agent.yaml
462
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/test/static_agent.yaml
463 463
 
464 464
 .. _scenario_paired_static_agents:
465 465
 
@@ -469,7 +469,7 @@ In this scenario Shaker runs tests on pre-deployed pair of static agents. The
469 469
 scenario can be used for Shaker integration testing.
470 470
 
471 471
 To use this scenario specify parameter ``--scenario test/static_agents_pair``.
472
-Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/test/static_agents_pair.yaml
472
+Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/test/static_agents_pair.yaml
473 473
 
474 474
 Heat Templates
475 475
 --------------
@@ -481,7 +481,7 @@ misc/instance_metadata
481 481
 Heat template creates a new Neutron network, a router to the external network,
482 482
 plugs instances into this network and assigns floating ips
483 483
 
484
-Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/misc/instance_metadata.hot
484
+Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/misc/instance_metadata.hot
485 485
 
486 486
 .. _template_openstack_cross_az_l2:
487 487
 
@@ -491,7 +491,7 @@ This Heat template creates a new Neutron network, a router to the external
491 491
 network and plugs instances into this new network. All instances are located in
492 492
 the same L2 domain.
493 493
 
494
-Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/l2.hot
494
+Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/l2.hot
495 495
 
496 496
 .. _template_openstack_cross_az_l3_east_west:
497 497
 
@@ -500,7 +500,7 @@ openstack/cross_az/l3_east_west
500 500
 This Heat template creates a pair of networks plugged into the same router.
501 501
 Master instances and slave instances are connected into different networks.
502 502
 
503
-Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/l3_east_west.hot
503
+Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/l3_east_west.hot
504 504
 
505 505
 .. _template_openstack_cross_az_l3_north_south:
506 506
 
@@ -510,7 +510,7 @@ This Heat template creates a new Neutron network plus a north_router to the
510 510
 external network. The template also assigns floating IP addresses to each
511 511
 instance so they are routable from the external network.
512 512
 
513
-Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/l3_north_south.hot
513
+Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/l3_north_south.hot
514 514
 
515 515
 .. _template_openstack_external_l3_north_south_no_fip:
516 516
 
@@ -519,7 +519,7 @@ openstack/external/l3_north_south_no_fip
519 519
 This Heat template creates a new Neutron network plugged into a router
520 520
 connected to the external network, and boots an instance in that network.
521 521
 
522
-Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/external/l3_north_south_no_fip.hot
522
+Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/external/l3_north_south_no_fip.hot
523 523
 
524 524
 .. _template_openstack_external_l3_north_south_with_fip:
525 525
 
@@ -529,7 +529,7 @@ This Heat template creates a new Neutron network plugged into a router
529 529
 connected to the external network, and boots an instance in that network. The
530 530
 instance has floating IP.
531 531
 
532
-Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/external/l3_north_south_with_fip.hot
532
+Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/external/l3_north_south_with_fip.hot
533 533
 
534 534
 .. _template_openstack_l2:
535 535
 
@@ -539,7 +539,7 @@ This Heat template creates a new Neutron network, a router to the external
539 539
 network and plugs instances into this new network. All instances are located in
540 540
 the same L2 domain.
541 541
 
542
-Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/l2.hot
542
+Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/l2.hot
543 543
 
544 544
 .. _template_openstack_l3_east_west:
545 545
 
@@ -548,7 +548,7 @@ openstack/l3_east_west
548 548
 This Heat template creates a pair of networks plugged into the same router.
549 549
 Master instances and slave instances are connected into different networks.
550 550
 
551
-Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/l3_east_west.hot
551
+Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/l3_east_west.hot
552 552
 
553 553
 .. _template_openstack_l3_north_south:
554 554
 
@@ -558,7 +558,7 @@ This Heat template creates a new Neutron network plus a north_router to the
558 558
 external network. The template also assigns floating IP addresses to each
559 559
 instance so they are routable from the external network.
560 560
 
561
-Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/l3_north_south.hot
561
+Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/l3_north_south.hot
562 562
 
563 563
 .. _template_openstack_qos_l2_qos:
564 564
 
@@ -568,7 +568,7 @@ This Heat template creates a new Neutron network, a router to the external
568 568
 network and plugs instances into this new network. All instances are located in
569 569
 the same L2 domain.
570 570
 
571
-Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/qos/l2_qos.hot
571
+Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/qos/l2_qos.hot
572 572
 
573 573
 .. _template_test_l2_with_env:
574 574
 
@@ -578,7 +578,7 @@ This Heat template creates a new Neutron network, a router to the external
578 578
 network and plugs instances into this new network. All instances are located in
579 579
 the same L2 domain.
580 580
 
581
-Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/test/l2_with_env.hot
581
+Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/test/l2_with_env.hot
582 582
 
583 583
 .. _template_test_templates_l2_with_support:
584 584
 
@@ -589,7 +589,7 @@ network and plugs instances into this new network. All instances are located in
589 589
 the same L2 domain. The VMs are also connected to support networks that should
590 590
 exist before this template is spun up.
591 591
 
592
-Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/test/templates/l2_with_support.hot
592
+Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/test/templates/l2_with_support.hot
593 593
 
594 594
 .. _template_test_templates_support_network:
595 595
 
@@ -598,5 +598,5 @@ test/templates/support_network
598 598
 This Heat template creates a new Neutron network. This is used to demonstrate a
599 599
 support stack in Shaker.
600 600
 
601
-Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/test/templates/support_network.hot
601
+Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/test/templates/support_network.hot
602 602
 

+ 5
- 1
doc/source/contributing.rst View File

@@ -75,5 +75,9 @@ Once those steps have been completed, changes to OpenStack should be submitted f
75 75
 
76 76
    https://docs.openstack.org/infra/manual/developers.html#development-workflow
77 77
 
78
-Pull requests submitted through GitHub will be ignored.
78
+Note that the primary repo is https://opendev.org/performa/shaker/
79
+Repos located at GitHub are mirrors and may be out of sync.
79 80
 
81
+Project bug tracker is Launchpad:
82
+
83
+   https://launchpad.net/shaker

+ 8
- 2
setup.cfg View File

@@ -3,9 +3,15 @@ name = pyshaker
3 3
 summary = Distributed data-plane performance testing tool
4 4
 description-file =
5 5
     README.rst
6
+description-content-type = text/x-rst; charset=UTF-8
6 7
 author = OpenStack
7
-author-email = openstack-discuss@lists.openstack.org
8
-home-page = https://www.openstack.org/
8
+author_email = openstack-discuss@lists.openstack.org
9
+url = https://pyshaker.readthedocs.io/
10
+download_url = https://pypi.org/project/pyshaker/
11
+project_urls =
12
+    Bug Tracker = https://launchpad.net/shaker
13
+    Documentation = https://pyshaker.readthedocs.io/
14
+    Source Code = https://opendev.org/performa/shaker
9 15
 classifier =
10 16
     Environment :: OpenStack
11 17
     Intended Audience :: Developers

Loading…
Cancel
Save