Hi Venkat,
Thanks for your question.
In TC002 Yaml file, you can easily find it consists of two sections.
One is “Scenarios”, the other is “Context”.
“Contexts” section is the description of pre-condition of testing. As
TC002.yaml shown, you can configure the image, flavor , name ,affinity and
network of Test VM(servers), with this section, you will get a pre-condition
env for Testing. Yardstick will automatic setup the stack which are described
in this section. In fact, yardstick use convert this section to heat template
and setup the VMs by heat-client (Meanwhile, yardstick can support to convert
this section to Kubernetes template to setup containers).
Go back to your question1, Two VMs are configured by keyword “servers”. And
“flavor ” will determine how many vCPU, how much memory for test VMs . As
“yardstick-flavor” is a basic flavor which will be automatically created when
you run command “yardstick env prepare”. “yardstick-flavor” is “ 1 vCPU 1G
RAM,3G Disk”,
[cid:image001.png@01D342AA.D08D6FC0]
Moreover, you can configure your specific flavor as below, yardstick will setup
the stack for you.
[cid:image002.png@01D342AC.E5A302B0]
Regarding to Question 2
“Scenarios” section is the description of testing step, you can orchestrate
the complex testing step through orchestrate scenarios.
Each scenario will do one testing step, In one scenario , you can configure
the type of scenario(operation) , runner type and SLA of the scenario..
For TC002, We only have one step , that is Ping from host VM to target VM. In
this step, we also have some detail operation implement ( such as ssh to VM,
ping from VM1 to VM2. Get the latency, verify the SLA, report the result.)
If you want to get this detail implement , you can check with the scenario.py
file. For Ping scenario, you can find it[1] in yardstick repo ( yardstick /
yardstick / benchmark / scenarios / networking / ping.py)
Additional. Some basic concept of yardstick framework. You can find it in user
guide chapter 3.2.2 [2], And we will to improve the developer guide for
developers soon. Thanks for your question again.
Hope that would help for you understand yardstick framework.
[1]
https://github.com/opnfv/yardstick/blob/stable/danube/yardstick/benchmark/scenarios/networking/ping.py
[2]
https://docs.opnfv.org/en/stable-danube/submodules/yardstick/docs/testing/user/userguide/03-architecture.html#concept
Regards,
Kubi
发件人: vven...@codeaurora.org [mailto:vven...@codeaurora.org]
发送时间: 2017年10月11日 15:37
收件人: chenjiankun <chenjiank...@huawei.com>; Gaoliang (kubi)
<jean.gaoli...@huawei.com>; kristian.h...@gmail.com;
opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] [yardstick] Yardstick test case details
Hi Jack/Kubi/Kristian and yardstick developers,
It would be grateful if you could please let me know on details to explore on
the test cases for a specific test case say TC002
(https://github.com/opnfv/yardstick/blob/stable/danube/tests/opnfv/test_cases/opnfv_yardstick_tc002.yaml)?
I understand the parameters but I would like to understand how yardstick
executes like what are the parameters for two VMs, how many vCPUs, how much
memory ?
In summary, would like to understand the exact execution details/internal
commands of the test case, please point me to the source details in the
yardstick repo.
Appreciate your help.
Thanks
-Venkat
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
