Age | Commit message (Collapse) | Author | Files | Lines |
|
New parameter is added to shell script to delete data for VMs either from
input file or all.
Added disk images removal as per new input parameter.
JIRA: YARDSTICK-1123
Change-Id: I8d2cee4a3a7ad7147f4d59303bab656d80370221
Signed-off-by: Stepan Andrushko <stepanx.andrushko@intel.com>
|
|
|
|
|
|
Added MessagingProducer base class. A class implementing this base class
can send a cast message using the MQ service installed in the Yardstick
jumphost (RabbitMQ by default, other MQ could be implemented). The producer
will send messages to an specific topic.
Added MessagingConsumer base class. A class implementing this base class
will be able to receive any message sent by a MessagingPorducer class
publishing messages in the topic subscribed.
By default both Producer and Consumer "fanout" is True. That means every
Consumer will create a fanout Queue attached to the MQ Exchange topic. All
Consumers attached to this topic will receive the message sent by the
Producer [1].
Added Payload base class. To send data through the message queue service,
a Payload derived object should be created. This base class allows to
define the attributes container in the class, convert the object to a dict
and retrieve the object from a dict.
Added a new library, "oslo.messaging", to implement the RPC client and
server.
[1]http://blog.thedigitalcatonline.com/blog/2013/08/21/some-tips-about-amqp-direct-exchanges/
JIRA: YARDSTICK-1074
Change-Id: I63932b5fb3de2bdc1270fc83295630a2a349e2a6
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
1. simplify the attack to be one interface
2. move monitor step before attack
3. update rst doc to match
JIRA: YARDSTICK-1120
Change-Id: Icfa21d58e7ccdbeaca8a9a1a3098cceb21c981c3
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
|
|
|
|
Bug fix in script "build_yardstick_image.yml", to
- Use option "-a" to list all used loop devices, to be more compatible.
- Ignore the error and continue, if the debug command failed.
JIRA: YARDSTICK-1121
Change-Id: I24aaebb2ffe3107ca5c619401725aa8c8e1af295
Signed-off-by: ting wu <ting.wu@enea.com>
|
|
JIRA: YARDSTICK-1110
To match OpenStack Pike release, we upgrade novaclient from 7.1.1 to 9.1.1.
And the client interface has changed, it no longer has nova_client.images attribute.
So I use shade instead. Later will change all same issue.
Change-Id: Ie4f54069d4346e44e2ad925439930504b945cbad
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
|
|
Update collectd version to 5.8 as it's the latest stable
and supports GCC 7
JIRA: YARDSTICK-1114
Change-Id: I9147b7277d87047eda729664d5ee3e8ab2c145af
Signed-off-by: John O Loughlin <john.oloughlin@intel.com>
|
|
|
|
Add support for dpdk 17.05. Add option to dpdk scripts
to download dpdk 17.08 17.11 and 18.02. These are currently
unsupported due to prox build issues.
JIRA: YARDSTICK-1113
Change-Id: I585566364a4d1f04a696439af96c50c0e9d38033
Signed-off-by: John O Loughlin <john.oloughlin@intel.com>
|
|
JIRA: YARDSTICK-1117
This bug will cause the error in running unixbench.
"no such file named ./run"
So we have to fix it.
Change-Id: I141fcb5567fbb0e3df97aee677cb946a25a9788e
Signed-off-by: liyin <liyin11@huawei.com>
|
|
JIRA: YARDSTICK-1109
Change-Id: Ic61a63099c3d2d4af5fa5634299e4b2946d53eaf
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
(cherry picked from commit 3b1316647b50bc3bbb1eb6216aa07fd4dff34edf)
|
|
Fixes: 18546b4f
Change-Id: I51fcb48e790ff7c57273a3f6712ccb2b9bc4aa32
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
(cherry picked from commit ead90064d12be552bd334828d41ffffa75fad01b)
|
|
Fixes: 18546b4f
Change-Id: I51fcb48e790ff7c57273a3f6712ccb2b9bc4aa32
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Ia2dfc6c4def8e71e36747b8f27cbf22700f676b1
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
(cherry picked from commit 161f7d676b4404a5445681a7871e086b751fdafc)
|
|
Change-Id: Ia2dfc6c4def8e71e36747b8f27cbf22700f676b1
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
Uses literalinclude directive instead of having a copy of the file content in documentation.
This means that any update to this file is detected, and the most up-to-date content is used.
If a testcase is updated, the updates wil be picked up.
The examples used are ones that are tested reqularly.
JIRA: YARDSTICK-1066
Change-Id: I15d967eb04d1e6f4348683d8746fa9989dceda94
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
* Add a new chapter: operation which shows how to use Yardstick and
how to create test cases
* Include details on how to reuse and keep VNFs between testcases
JIRA: YARDSTICK-885
JIRA: YARDSTICK-886
Change-Id: I365152e8812427a3c54259adbc18d5ddb216d775
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
* Increment the numbering on chapters
* Fix some of the changes flagged by doc8
Change-Id: Ie03d165297671dfd50b9de339612cdc8bf00b988
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
JIRA: YARDSTICK-1109
Change-Id: Ic61a63099c3d2d4af5fa5634299e4b2946d53eaf
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
JIRA: YARDSTICK-1108
We add this test case in ovs_dpdk-ha and ovs_dpdk-noha testsuites
also add image build into load_images script
Change-Id: I2b0c6b106dd98c3693df18dba46259ff8ef0a76e
Signed-off-by: liyin <liyin11@huawei.com>
|
|
|
|
|
|
|
|
atexit handler calls terminate_all after the regular python execution
path, and it looks like the traceback stack is None somehow.
In this context log.debug("", exc_info=True) doesn't work
it prints out NoneType on Python3 and
causes other problems on Python2.7
remove the exc_info=True from the logging call
JIRA: YARDSTICK-1107
Change-Id: Ida0a0ced7ff5e017e2f8608880e3bb531724af95
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
New scenarios from wiki: https://wiki.opnfv.org/display/SWREL/Fraser+Scenario+Statu
Change-Id: Ifd6e45e73be2bbb99743aa3f4981d22899aab92a
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
|
|
In both Standalone contexts, SR-IOV and DPDK, the tool provisioning must
be removed. If the tool, "dpdk-devbind.py", is not in the VNF, the test
should fail because this tool should be provided during the provisioning,
not during the test execution.
JIRA: YARDSTICK-1092
Change-Id: I212c1303fd655f151e9c0efc29aad97fe6d71d1c
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
RabbitMQ service added in [1] is not correctly installed and initialized:
- There is an error during the installation process ("\" character
missing).
- In the installation script, the service needs to be started first.
- In the container installation, the service needs to be started via
supervisor.
[1]https://gerrit.opnfv.org/gerrit/#/c/53597/
JIRA: YARDSTICK-1103
Change-Id: Iade3d6ce4b522e6f576af71b7afe5559081f7929
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
|
|
|
|
If the Task raised an exception we currently hide it
and replace it with RuntimeError. This is bad.
If an exception occured, then we don't have a result so
re-raise the original exception.
Or we could log the traceback and raise RuntimeError, but
that doesn't seem to be a good idea.
Sample traceback after re-raising original. Without this patch the ValueError is only written
to _write_error_data
2018-03-25 22:57:56,511 yardstick.benchmark.contexts.node node.py:85 DEBUG BareMetals: []
2018-03-25 22:57:56,511 yardstick.benchmark.contexts.node node.py:89 DEBUG Env: {}
2018-03-25 22:57:56,511 yardstick.cmd.commands.task task.py:57 INFO Task FAILED
Traceback (most recent call last):
File "/home/rbbratta/yardstick-upstream/yardstick/yardstick/cmd/commands/task.py", line 54, in do_start
result = Task().start(param, **kwargs)
File "/home/rbbratta/yardstick-upstream/yardstick/yardstick/benchmark/core/task.py", line 103, in start
task_args_fnames)
File "/home/rbbratta/yardstick-upstream/yardstick/yardstick/benchmark/core/task.py", line 321, in _parse_tasks
task_args_fnames[i]
File "/home/rbbratta/yardstick-upstream/yardstick/yardstick/benchmark/core/task.py", line 558, in parse_task
context.init(cfg_attrs)
File "/home/rbbratta/yardstick-upstream/yardstick/yardstick/benchmark/contexts/heat.py", line 131, in init
server = Server(name, self, server_attrs)
File "/home/rbbratta/yardstick-upstream/yardstick/yardstick/benchmark/contexts/model.py", line 210, in __init__
(name, p))
ValueError: server 'trafficgen_1', placement 'pgrp2' is invalid
2018-03-25 22:57:56,512 yardstick.cmd.commands.task task.py:62 INFO Task FAILED
2018-03-25 22:57:56,662 yardstick.benchmark.runners.base base.py:124 DEBUG Terminating all runners
NoneType
JIRA: YARDSTICK-1102
Change-Id: I7e6fa41fc1d36f6d438a1602ab60cb41ffbee1e9
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
We need to see what Heat failures occured
so that we can debug CI failures.
The only way to do this seems to be to use the
private event_utils.get_events function to
query for all failures
Also since we had a failure go ahead and dump the
Heat template that failed.
Sample output:
2018-03-25 23:50:08,765 [INFO] yardstick.orchestrator.heat heat.py:629 Creating stack 'yardstick-460ed969' START
2018-03-25 23:50:21,932 [ERROR] yardstick.orchestrator.heat heat.py:644 Resource CREATE failed: BadRequest: resources.yardstick-460ed969-xe1: Invalid input for operation: physical_network 'nosuch' unknown for flat provider network.
Neutron server returns request_ids: ['req-6f981f1e-a9e2-4114-af84-1ee528aed51b']
2018-03-25 23:50:21,933 [ERROR] yardstick.orchestrator.heat heat.py:644 BadRequest: resources.yardstick-460ed969-xe1: Invalid input for operation: physical_network 'nosuch' unknown for flat provider network.
Neutron server returns request_ids: ['req-6f981f1e-a9e2-4114-af84-1ee528aed51b']
2018-03-25 23:50:21,972 [ERROR] yardstick.orchestrator.heat heat.py:645 {'description': '\n'
'All referred generated resources are prefixed with the '
'template\n'
'name (i.e. yardstick-460ed969).\n',
'heat_template_version': '2013-05-23',
'outputs': {'trafficgen_1.yardstick-460ed969': {'description': 'VM UUID',
'value': {'get_resource': 'trafficgen_1.yardstick-460ed969'}},
'trafficgen_1.yardstick-460ed969-fip': {'description': 'floating '
'ip '
JIRA: YARDSTICK-998
Change-Id: Ia8f4e5ba7e280fb9086519680d5ee90a2b442e6b
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
Rename create_secgroup_rule with create_security_group_rule.
Function create_security_group_rule now uses shade client.
JIRA: YARDSTICK-890
Change-Id: Ie0ebac67a281e55dc95c0e3e33ba43de80aba9ec
Signed-off-by: Shobhi Jain <shobhi.jain@intel.com>
|
|
|
|
|
|
|
|
Function delete_floating_ip now uses shade client.
JIRA: YARDSTICK-890
Change-Id: I960630926b664266afbe7be00bb1352243b41be0
Signed-off-by: Shobhi Jain <shobhi.jain@intel.com>
|
|
|
|
|
|
|