performa
/
shaker
Code Issues Proposed changes

Update project links and package metadata 

Change-Id: I7134ade3e8575bee474ce579c0ebd9959d48a2d8
This commit is contained in:
Ilya Shakhat 2019-09-09 11:00:56 +02:00
parent 242992bf9a
commit 39942a642c
4 changed files with 66 additions and 56 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.rst
View File

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

102
doc/source/catalog.rst
View File

@ -15,7 +15,7 @@ asks instances to retrieve the metadata. The scenario is used to load metadata
processes. processes.
To use this scenario specify parameter ``--scenario misc/instance_metadata``. To use this scenario specify parameter ``--scenario misc/instance_metadata``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/misc/instance_metadata.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/misc/instance_metadata.yaml
.. _scenario_openstack_l2_cross_az: .. _scenario_openstack_l2_cross_az:
@ -28,7 +28,7 @@ availability zones. The scenario is used to test throughput between `nova` and
`vcenter` zones. The traffic goes within the tenant network (L2 domain). `vcenter` zones. The traffic goes within the tenant network (L2 domain).
To use this scenario specify parameter ``--scenario openstack/cross_az/full_l2``. To use this scenario specify parameter ``--scenario openstack/cross_az/full_l2``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/full_l2.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/full_l2.yaml
.. _scenario_openstack_l3_east_west_cross_az: .. _scenario_openstack_l3_east_west_cross_az:
@ -42,7 +42,7 @@ are in different availability zones. The scenario is used to test throughput
between `nova` and `vcenter` zones. between `nova` and `vcenter` zones.
To use this scenario specify parameter ``--scenario openstack/cross_az/full_l3_east_west``. To use this scenario specify parameter ``--scenario openstack/cross_az/full_l3_east_west``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/full_l3_east_west.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/full_l3_east_west.yaml
.. _scenario_openstack_l3_north_south_cross_az: .. _scenario_openstack_l3_north_south_cross_az:
@ -56,7 +56,7 @@ master and slave instances are in different availability zones. The scenario is
used to test throughput between `nova` and `vcenter` zones. used to test throughput between `nova` and `vcenter` zones.
To use this scenario specify parameter ``--scenario openstack/cross_az/full_l3_north_south``. To use this scenario specify parameter ``--scenario openstack/cross_az/full_l3_north_south``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/full_l3_north_south.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/full_l3_north_south.yaml
.. _scenario_openstack_l2_cross_az_performance: .. _scenario_openstack_l2_cross_az_performance:
@ -68,7 +68,7 @@ slave instances are in different availability zones. The scenario is used to
test throughput between `nova` and `vcenter` zones. test throughput between `nova` and `vcenter` zones.
To use this scenario specify parameter ``--scenario openstack/cross_az/perf_l2``. To use this scenario specify parameter ``--scenario openstack/cross_az/perf_l2``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/perf_l2.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/perf_l2.yaml
.. _scenario_openstack_l3_east_west_cross_az_performance: .. _scenario_openstack_l3_east_west_cross_az_performance:
@ -81,7 +81,7 @@ east-west). The master and slave instances are in different availability zones.
The scenario is used to test throughput between `nova` and `vcenter` zones. The scenario is used to test throughput between `nova` and `vcenter` zones.
To use this scenario specify parameter ``--scenario openstack/cross_az/perf_l3_east_west``. To use this scenario specify parameter ``--scenario openstack/cross_az/perf_l3_east_west``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/perf_l3_east_west.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/perf_l3_east_west.yaml
.. _scenario_openstack_l3_north_south_cross_az_performance: .. _scenario_openstack_l3_north_south_cross_az_performance:
@ -95,7 +95,7 @@ different availability zones. The scenario is used to test throughput between
`nova` and `vcenter` zones. `nova` and `vcenter` zones.
To use this scenario specify parameter ``--scenario openstack/cross_az/perf_l3_north_south``. To use this scenario specify parameter ``--scenario openstack/cross_az/perf_l3_north_south``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/perf_l3_north_south.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/perf_l3_north_south.yaml
.. _scenario_openstack_l2_cross_az_udp: .. _scenario_openstack_l2_cross_az_udp:
@ -108,7 +108,7 @@ zones. The scenario is used to test throughput between `nova` and `vcenter`
zones. zones.
To use this scenario specify parameter ``--scenario openstack/cross_az/udp_l2``. To use this scenario specify parameter ``--scenario openstack/cross_az/udp_l2``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/udp_l2.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/udp_l2.yaml
.. _scenario_openstack_l2_cross_az_udp_jumbo: .. _scenario_openstack_l2_cross_az_udp_jumbo:
@ -121,7 +121,7 @@ availability zones. The scenario is used to test throughput between `nova` and
`vcenter` zones. `vcenter` zones.
To use this scenario specify parameter ``--scenario openstack/cross_az/udp_l2_mss8950``. To use this scenario specify parameter ``--scenario openstack/cross_az/udp_l2_mss8950``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/udp_l2_mss8950.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/udp_l2_mss8950.yaml
.. _scenario_openstack_l3_east_west_cross_az_udp: .. _scenario_openstack_l3_east_west_cross_az_udp:
@ -135,7 +135,7 @@ instances are in different availability zones. The scenario is used to test
throughput between `nova` and `vcenter` zones. throughput between `nova` and `vcenter` zones.
To use this scenario specify parameter ``--scenario openstack/cross_az/udp_l3_east_west``. To use this scenario specify parameter ``--scenario openstack/cross_az/udp_l3_east_west``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/udp_l3_east_west.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/udp_l3_east_west.yaml
.. _scenario_openstack_l2_dense: .. _scenario_openstack_l2_dense:
@ -146,7 +146,7 @@ node. Instances are plugged into the same tenant network. The traffic goes
within the tenant network (L2 domain). within the tenant network (L2 domain).
To use this scenario specify parameter ``--scenario openstack/dense_l2``. To use this scenario specify parameter ``--scenario openstack/dense_l2``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/dense_l2.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/dense_l2.yaml
.. _scenario_openstack_l3_east_west_dense: .. _scenario_openstack_l3_east_west_dense:
@ -157,7 +157,7 @@ Instances are connected to different tenant networks connected to one router.
The traffic goes from one network to the other (L3 east-west). The traffic goes from one network to the other (L3 east-west).
To use this scenario specify parameter ``--scenario openstack/dense_l3_east_west``. To use this scenario specify parameter ``--scenario openstack/dense_l3_east_west``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/dense_l3_east_west.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/dense_l3_east_west.yaml
.. _scenario_openstack_l3_north_south_dense: .. _scenario_openstack_l3_north_south_dense:
@ -169,7 +169,7 @@ router. Instances in one of networks have floating IPs. The traffic goes from
one network via external network to the other network. one network via external network to the other network.
To use this scenario specify parameter ``--scenario openstack/dense_l3_north_south``. To use this scenario specify parameter ``--scenario openstack/dense_l3_north_south``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/dense_l3_north_south.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/dense_l3_north_south.yaml
.. _scenario_openstack_l3_north_south_dense_to_external_target: .. _scenario_openstack_l3_north_south_dense_to_external_target:
@ -181,7 +181,7 @@ host. The host name needs to be provided as command-line parameter, e.g.
``--matrix "{host: 172.10.1.2}"``. ``--matrix "{host: 172.10.1.2}"``.
To use this scenario specify parameter ``--scenario openstack/external/dense_l3_north_south_no_fip``. To use this scenario specify parameter ``--scenario openstack/external/dense_l3_north_south_no_fip``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/external/dense_l3_north_south_no_fip.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/external/dense_l3_north_south_no_fip.yaml
.. _scenario_openstack_l3_north_south_dense_to_external_target_with_floating_ip: .. _scenario_openstack_l3_north_south_dense_to_external_target_with_floating_ip:
@ -193,7 +193,7 @@ traffic is sent to and from external host. The host name needs to be provided
as command-line parameter, e.g. ``--matrix "{host: 172.10.1.2}"``. as command-line parameter, e.g. ``--matrix "{host: 172.10.1.2}"``.
To use this scenario specify parameter ``--scenario openstack/external/dense_l3_north_south_with_fip``. To use this scenario specify parameter ``--scenario openstack/external/dense_l3_north_south_with_fip``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/external/dense_l3_north_south_with_fip.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/external/dense_l3_north_south_with_fip.yaml
.. _scenario_openstack_l3_north_south_to_external_target: .. _scenario_openstack_l3_north_south_to_external_target:
@ -206,7 +206,7 @@ host (L3 north-south). The host name needs to be provided as command-line
parameter, e.g. ``--matrix "{host: 172.10.1.2}"``. parameter, e.g. ``--matrix "{host: 172.10.1.2}"``.
To use this scenario specify parameter ``--scenario openstack/external/full_l3_north_south_no_fip``. To use this scenario specify parameter ``--scenario openstack/external/full_l3_north_south_no_fip``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/external/full_l3_north_south_no_fip.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/external/full_l3_north_south_no_fip.yaml
.. _scenario_openstack_l3_north_south_to_external_target_with_floating_ip: .. _scenario_openstack_l3_north_south_to_external_target_with_floating_ip:
@ -220,7 +220,7 @@ to be provided as command-line parameter, e.g. ``--matrix "{host:
172.10.1.2}"``. 172.10.1.2}"``.
To use this scenario specify parameter ``--scenario openstack/external/full_l3_north_south_with_fip``. To use this scenario specify parameter ``--scenario openstack/external/full_l3_north_south_with_fip``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/external/full_l3_north_south_with_fip.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/external/full_l3_north_south_with_fip.yaml
.. _scenario_openstack_l3_north_south_performance_to_external_target: .. _scenario_openstack_l3_north_south_performance_to_external_target:
@ -232,7 +232,7 @@ of public iperf3 servers is used, to override this the target host can be
provided as command-line parameter, e.g. ``--matrix "{host: 172.10.1.2}"``. provided as command-line parameter, e.g. ``--matrix "{host: 172.10.1.2}"``.
To use this scenario specify parameter ``--scenario openstack/external/perf_l3_north_south_no_fip``. To use this scenario specify parameter ``--scenario openstack/external/perf_l3_north_south_no_fip``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/external/perf_l3_north_south_no_fip.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/external/perf_l3_north_south_no_fip.yaml
.. _scenario_openstack_l3_north_south_performance_to_external_target_with_floating_ip: .. _scenario_openstack_l3_north_south_performance_to_external_target_with_floating_ip:
@ -245,7 +245,7 @@ this the target host can be provided as command-line parameter, e.g. ``--matrix
"{host: 172.10.1.2}"``. "{host: 172.10.1.2}"``.
To use this scenario specify parameter ``--scenario openstack/external/perf_l3_north_south_with_fip``. To use this scenario specify parameter ``--scenario openstack/external/perf_l3_north_south_with_fip``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/external/perf_l3_north_south_with_fip.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/external/perf_l3_north_south_with_fip.yaml
.. _scenario_openstack_l2: .. _scenario_openstack_l2:
@ -256,7 +256,7 @@ Every instance is hosted on a separate compute node, all available compute
nodes are utilized. The traffic goes within the tenant network (L2 domain). nodes are utilized. The traffic goes within the tenant network (L2 domain).
To use this scenario specify parameter ``--scenario openstack/full_l2``. To use this scenario specify parameter ``--scenario openstack/full_l2``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/full_l2.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/full_l2.yaml
.. _scenario_openstack_l3_east_west: .. _scenario_openstack_l3_east_west:
@ -268,7 +268,7 @@ to one of 2 tenant networks, which plugged into single router. The traffic goes
from one network to the other (L3 east-west). from one network to the other (L3 east-west).
To use this scenario specify parameter ``--scenario openstack/full_l3_east_west``. To use this scenario specify parameter ``--scenario openstack/full_l3_east_west``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/full_l3_east_west.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/full_l3_east_west.yaml
.. _scenario_openstack_l3_north_south: .. _scenario_openstack_l3_north_south:
@ -280,7 +280,7 @@ connected to different routers, master accesses slave by floating ip. The
traffic goes from one network via external network to the other network. traffic goes from one network via external network to the other network.
To use this scenario specify parameter ``--scenario openstack/full_l3_north_south``. To use this scenario specify parameter ``--scenario openstack/full_l3_north_south``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/full_l3_north_south.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/full_l3_north_south.yaml
.. _scenario_openstack_l2_performance: .. _scenario_openstack_l2_performance:
@ -291,7 +291,7 @@ network. Each instance is hosted on a separate compute node. The traffic goes
within the tenant network (L2 domain). within the tenant network (L2 domain).
To use this scenario specify parameter ``--scenario openstack/perf_l2``. To use this scenario specify parameter ``--scenario openstack/perf_l2``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/perf_l2.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/perf_l2.yaml
.. _scenario_openstack_l3_east_west_performance: .. _scenario_openstack_l3_east_west_performance:
@ -303,7 +303,7 @@ plugged into single router. The traffic goes from one network to the other (L3
east-west). east-west).
To use this scenario specify parameter ``--scenario openstack/perf_l3_east_west``. To use this scenario specify parameter ``--scenario openstack/perf_l3_east_west``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/perf_l3_east_west.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/perf_l3_east_west.yaml
.. _scenario_openstack_l3_north_south_performance: .. _scenario_openstack_l3_north_south_performance:
@ -315,7 +315,7 @@ master accesses slave by floating ip. The traffic goes from one network via
external network to the other network. external network to the other network.
To use this scenario specify parameter ``--scenario openstack/perf_l3_north_south``. To use this scenario specify parameter ``--scenario openstack/perf_l3_north_south``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/perf_l3_north_south.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/perf_l3_north_south.yaml
.. _scenario_openstack_l2_qos_performance: .. _scenario_openstack_l2_qos_performance:
@ -327,7 +327,7 @@ within the tenant network (L2 domain). Neutron QoS feature is used to limit
traffic throughput to 10 Mbit/s. traffic throughput to 10 Mbit/s.
To use this scenario specify parameter ``--scenario openstack/qos/perf_l2``. To use this scenario specify parameter ``--scenario openstack/qos/perf_l2``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/qos/perf_l2.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/qos/perf_l2.yaml
.. _scenario_openstack_l2_udp: .. _scenario_openstack_l2_udp:
@ -338,7 +338,7 @@ Every instance is hosted on a separate compute node. The traffic goes within
the tenant network (L2 domain). The load is generated by UDP traffic. the tenant network (L2 domain). The load is generated by UDP traffic.
To use this scenario specify parameter ``--scenario openstack/udp_l2``. To use this scenario specify parameter ``--scenario openstack/udp_l2``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/udp_l2.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/udp_l2.yaml
.. _scenario_openstack_l3_east_west_udp: .. _scenario_openstack_l3_east_west_udp:
@ -350,7 +350,7 @@ plugged into single router. The traffic goes from one network to the other (L3
east-west). The load is generated by UDP traffic. east-west). The load is generated by UDP traffic.
To use this scenario specify parameter ``--scenario openstack/udp_l3_east_west``. To use this scenario specify parameter ``--scenario openstack/udp_l3_east_west``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/udp_l3_east_west.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/udp_l3_east_west.yaml
.. _scenario_openstack_l3_north_south_udp: .. _scenario_openstack_l3_north_south_udp:
@ -362,7 +362,7 @@ accesses slave by floating ip. The traffic goes from one network via external
network to the other network. The load is generated by UDP traffic. network to the other network. The load is generated by UDP traffic.
To use this scenario specify parameter ``--scenario openstack/udp_l3_north_south``. To use this scenario specify parameter ``--scenario openstack/udp_l3_north_south``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/udp_l3_north_south.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/udp_l3_north_south.yaml
.. _scenario_ping: .. _scenario_ping:
@ -375,7 +375,7 @@ The destination host can be overridden by command-line parameter, e.g.
``--matrix "{host: 172.10.1.2}"``. ``--matrix "{host: 172.10.1.2}"``.
To use this scenario specify parameter ``--scenario spot/ping``. To use this scenario specify parameter ``--scenario spot/ping``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/spot/ping.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/spot/ping.yaml
.. _scenario_tcp_bandwidth: .. _scenario_tcp_bandwidth:
@ -388,7 +388,7 @@ destination host can be overridden by command-line parameter, e.g. ``--matrix
"{host: 172.10.1.2}"``. "{host: 172.10.1.2}"``.
To use this scenario specify parameter ``--scenario spot/tcp``. To use this scenario specify parameter ``--scenario spot/tcp``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/spot/tcp.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/spot/tcp.yaml
.. _scenario_udp_bandwidth: .. _scenario_udp_bandwidth:
@ -400,7 +400,7 @@ requires at least 10 000 packets per second. The destination host can be
overridden by command-line parameter, e.g. ``--matrix "{host: 172.10.1.2}"``. overridden by command-line parameter, e.g. ``--matrix "{host: 172.10.1.2}"``.
To use this scenario specify parameter ``--scenario spot/udp``. To use this scenario specify parameter ``--scenario spot/udp``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/spot/udp.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/spot/udp.yaml
.. _scenario_sample_tcp_test_with_advanced_iperf_arguments: .. _scenario_sample_tcp_test_with_advanced_iperf_arguments:
@ -413,7 +413,7 @@ utilized. The traffic goes within the tenant network (L2 domain) and uses
arguments not directly mapped by the iperf executor. arguments not directly mapped by the iperf executor.
To use this scenario specify parameter ``--scenario test/sample_with_advanced_iperf``. To use this scenario specify parameter ``--scenario test/sample_with_advanced_iperf``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/test/sample_with_advanced_iperf.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/test/sample_with_advanced_iperf.yaml
.. _scenario_sample_tcp_test_with_environment_file: .. _scenario_sample_tcp_test_with_environment_file:
@ -425,7 +425,7 @@ instance is hosted on a separate compute node, 1 compute node is utilized. The
traffic goes within the tenant network (L2 domain) traffic goes within the tenant network (L2 domain)
To use this scenario specify parameter ``--scenario test/sample_with_env``. To use this scenario specify parameter ``--scenario test/sample_with_env``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/test/sample_with_env.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/test/sample_with_env.yaml
.. _scenario_sample_tcp_test_with_support_stacks: .. _scenario_sample_tcp_test_with_support_stacks:
@ -439,7 +439,7 @@ separate compute node, 1 compute node is utilized. The traffic goes within the
tenant network (L2 domain) tenant network (L2 domain)
To use this scenario specify parameter ``--scenario test/sample_with_support_stacks``. To use this scenario specify parameter ``--scenario test/sample_with_support_stacks``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/test/sample_with_support_stacks.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/test/sample_with_support_stacks.yaml
.. _scenario_static_agents: .. _scenario_static_agents:
@ -449,7 +449,7 @@ In this scenario Shaker runs tests in spot mode. The scenario can be used for
Shaker integration testing. Shaker integration testing.
To use this scenario specify parameter ``--scenario test/spot``. To use this scenario specify parameter ``--scenario test/spot``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/test/spot.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/test/spot.yaml
.. _scenario_static_agents: .. _scenario_static_agents:
@ -459,7 +459,7 @@ In this scenario Shaker runs tests on pre-deployed static agents. The scenario
can be used for Shaker integration testing. can be used for Shaker integration testing.
To use this scenario specify parameter ``--scenario test/static_agent``. To use this scenario specify parameter ``--scenario test/static_agent``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/test/static_agent.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/test/static_agent.yaml
.. _scenario_paired_static_agents: .. _scenario_paired_static_agents:
@ -469,7 +469,7 @@ In this scenario Shaker runs tests on pre-deployed pair of static agents. The
scenario can be used for Shaker integration testing. scenario can be used for Shaker integration testing.
To use this scenario specify parameter ``--scenario test/static_agents_pair``. To use this scenario specify parameter ``--scenario test/static_agents_pair``.
Scenario source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/test/static_agents_pair.yaml Scenario source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/test/static_agents_pair.yaml
Heat Templates Heat Templates
-------------- --------------
@ -481,7 +481,7 @@ misc/instance_metadata
Heat template creates a new Neutron network, a router to the external network, Heat template creates a new Neutron network, a router to the external network,
plugs instances into this network and assigns floating ips plugs instances into this network and assigns floating ips
Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/misc/instance_metadata.hot Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/misc/instance_metadata.hot
.. _template_openstack_cross_az_l2: .. _template_openstack_cross_az_l2:
@ -491,7 +491,7 @@ This Heat template creates a new Neutron network, a router to the external
network and plugs instances into this new network. All instances are located in network and plugs instances into this new network. All instances are located in
the same L2 domain. the same L2 domain.
Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/l2.hot Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/l2.hot
.. _template_openstack_cross_az_l3_east_west: .. _template_openstack_cross_az_l3_east_west:
@ -500,7 +500,7 @@ openstack/cross_az/l3_east_west
This Heat template creates a pair of networks plugged into the same router. This Heat template creates a pair of networks plugged into the same router.
Master instances and slave instances are connected into different networks. Master instances and slave instances are connected into different networks.
Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/l3_east_west.hot Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/l3_east_west.hot
.. _template_openstack_cross_az_l3_north_south: .. _template_openstack_cross_az_l3_north_south:
@ -510,7 +510,7 @@ This Heat template creates a new Neutron network plus a north_router to the
external network. The template also assigns floating IP addresses to each external network. The template also assigns floating IP addresses to each
instance so they are routable from the external network. instance so they are routable from the external network.
Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/cross_az/l3_north_south.hot Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/cross_az/l3_north_south.hot
.. _template_openstack_external_l3_north_south_no_fip: .. _template_openstack_external_l3_north_south_no_fip:
@ -519,7 +519,7 @@ openstack/external/l3_north_south_no_fip
This Heat template creates a new Neutron network plugged into a router This Heat template creates a new Neutron network plugged into a router
connected to the external network, and boots an instance in that network. connected to the external network, and boots an instance in that network.
Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/external/l3_north_south_no_fip.hot Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/external/l3_north_south_no_fip.hot
.. _template_openstack_external_l3_north_south_with_fip: .. _template_openstack_external_l3_north_south_with_fip:
@ -529,7 +529,7 @@ This Heat template creates a new Neutron network plugged into a router
connected to the external network, and boots an instance in that network. The connected to the external network, and boots an instance in that network. The
instance has floating IP. instance has floating IP.
Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/external/l3_north_south_with_fip.hot Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/external/l3_north_south_with_fip.hot
.. _template_openstack_l2: .. _template_openstack_l2:
@ -539,7 +539,7 @@ This Heat template creates a new Neutron network, a router to the external
network and plugs instances into this new network. All instances are located in network and plugs instances into this new network. All instances are located in
the same L2 domain. the same L2 domain.
Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/l2.hot Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/l2.hot
.. _template_openstack_l3_east_west: .. _template_openstack_l3_east_west:
@ -548,7 +548,7 @@ openstack/l3_east_west
This Heat template creates a pair of networks plugged into the same router. This Heat template creates a pair of networks plugged into the same router.
Master instances and slave instances are connected into different networks. Master instances and slave instances are connected into different networks.
Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/l3_east_west.hot Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/l3_east_west.hot
.. _template_openstack_l3_north_south: .. _template_openstack_l3_north_south:
@ -558,7 +558,7 @@ This Heat template creates a new Neutron network plus a north_router to the
external network. The template also assigns floating IP addresses to each external network. The template also assigns floating IP addresses to each
instance so they are routable from the external network. instance so they are routable from the external network.
Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/l3_north_south.hot Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/l3_north_south.hot
.. _template_openstack_qos_l2_qos: .. _template_openstack_qos_l2_qos:
@ -568,7 +568,7 @@ This Heat template creates a new Neutron network, a router to the external
network and plugs instances into this new network. All instances are located in network and plugs instances into this new network. All instances are located in
the same L2 domain. the same L2 domain.
Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/openstack/qos/l2_qos.hot Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/openstack/qos/l2_qos.hot
.. _template_test_l2_with_env: .. _template_test_l2_with_env:
@ -578,7 +578,7 @@ This Heat template creates a new Neutron network, a router to the external
network and plugs instances into this new network. All instances are located in network and plugs instances into this new network. All instances are located in
the same L2 domain. the same L2 domain.
Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/test/l2_with_env.hot Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/test/l2_with_env.hot
.. _template_test_templates_l2_with_support: .. _template_test_templates_l2_with_support:
@ -589,7 +589,7 @@ network and plugs instances into this new network. All instances are located in
the same L2 domain. The VMs are also connected to support networks that should the same L2 domain. The VMs are also connected to support networks that should
exist before this template is spun up. exist before this template is spun up.
Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/test/templates/l2_with_support.hot Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/test/templates/l2_with_support.hot
.. _template_test_templates_support_network: .. _template_test_templates_support_network:
@ -598,5 +598,5 @@ test/templates/support_network
This Heat template creates a new Neutron network. This is used to demonstrate a This Heat template creates a new Neutron network. This is used to demonstrate a
support stack in Shaker. support stack in Shaker.
Template source is available at: https://github.com/openstack/shaker/blob/master/shaker/scenarios/test/templates/support_network.hot Template source is available at: https://opendev.org/performa/shaker/src/branch/master/shaker/scenarios/test/templates/support_network.hot

6
doc/source/contributing.rst
View File

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

10
setup.cfg
View File

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