08:29:24 <kubi> #startmeeting Yardstick work meeting
08:29:24 <collabot`> Meeting started Mon May 16 08:29:24 2016 UTC.  The chair is kubi. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:29:24 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
08:29:24 <collabot`> The meeting name has been set to 'yardstick_work_meeting'
08:29:40 <kubi> #info Kubi
08:29:46 <Jing> #info Jing
08:29:50 <Mingjiang6> #info Mingjiang
08:29:58 <jasperchiu> #QiuJuan
08:30:29 <FedericoRessi> #info Federico
08:30:47 <kubi> jasperchiu: please add #info in front of your name
08:31:07 <jasperchiu> #info QiuJuan
08:31:20 <kubi> #topic plugfest
08:31:48 <kubi> #info several integrations done, Yardstick and Functest launched successfully
08:31:54 <qwebirc35364> #info Kanglin
08:32:50 <kubi> #topic enhanced HA framework
08:33:17 <kubi> jasperchiu: Could you give us a brief intro about your enhanced HA framework
08:33:26 <jasperchiu> sure
08:33:33 <jasperchiu> https://etherpad.opnfv.org/p/yardstick-ha-new-framework-demo
08:33:54 <jasperchiu> first, could you guys open this link and have a quick look
08:34:00 <jasperchiu> ?
08:34:01 <kubi> yes
08:34:21 <jasperchiu> ok, let's have a look at this yaml file.
08:35:03 <kubi> do you want to discuss it on the etherpad?
08:35:12 <jasperchiu> actually this is a scenario script file in which you could get the whole steps in the script.
08:36:21 <Mingjiang6> i can see there are steps listed in the yaml.
08:36:34 <jasperchiu> I could give a brief intro per the yaml file
08:36:50 <jasperchiu> exactly
08:37:07 <jasperchiu> and you could have a look at the options section
08:37:23 <jasperchiu> we have defined all of the resources that will be involved in the scenario.
08:38:17 <jasperchiu> in our new framework, they are "attackers","monitors","operations","result_checker"
08:38:47 <jasperchiu> both "attackers" and "monitors" are the resources in the pervious yardstick HA module
08:38:57 <kubi> "operations","result_checker" are new modules
08:39:09 <jasperchiu> exactly
08:39:47 <jasperchiu> then I'd like to introduce what is an operation?
08:39:50 <kubi> #info In enhanced framework, there are "attackers","monitors","operations","result_checker"
08:40:13 <kubi> jasperchiu:  yes, go ahead
08:41:07 <jasperchiu> we define an operation as an action for preparing some preliminary steps.
08:41:47 <kubi> #info operation is defined as an action for preparing some preliminary step
08:41:59 <jasperchiu> compared with an attacker, we know, attacker is used to do some inject action to the system.
08:42:36 <jasperchiu> but operation is some normal action which would not impair the system.
08:43:35 <jasperchiu> as for result_checker, you could consider it to be something like a conditional breakpoint.
08:43:55 <jasperchiu> in the result_checker, there must be an expected value that you want to check.
08:44:53 <kubi> oh, i see, that will make HA framework more flexible, you can do more operation as you want without modify the scenario.py.  what we need to do is modify "steps"
08:44:55 <jasperchiu> and you could different condition to check the expected value, we have defined "eq","gt","lt","gt_eq","lt_eq","in"
08:45:37 <jasperchiu> exactly
08:46:06 <kubi> #info in the result_checker, there must be an expected value that you want to check. "eq","gt","lt","gt_eq","lt_eq","in" have been pre-defined.
08:46:15 <kubi> jasperchiu: great!
08:46:21 <Yaoguang_Wang> hi, guys, i have a question: will the enhanced framework be released in Colorado?
08:46:25 <jasperchiu> when coming a new scenario, the most ideal behaviour is just add a new yaml file
08:47:01 <kubi> jasperchiu:  yes, you are right, good design
08:47:39 <jasperchiu> you just need define your resources,context/target system (nodes),steps
08:48:13 <kubi> Yaoguang_Wang:  we need to give a priority after we clarify what we need to do for the enhanced framework
08:48:54 <Yaoguang_Wang> kubi: Good job, thanks
08:49:15 <kubi> Yaoguang_Wang:  please let me know if you have interest in the enhanced HA framework
08:49:48 <kubi> jasperchiu: thank you for your great intro.
08:49:56 <kubi> any comments?
08:50:01 <jasperchiu> you are welcome
08:51:21 <kubi> ok, jasperchiu , thank you again
08:51:24 <kubi> #topic Push Yardstick test result On ZTE pod to Yardstick influxDB
08:51:55 <kubi> Wendy_:  ping
08:52:57 <kubi> #info Mingjiang has answered Zhihui's question. Zhihui please check it.
08:53:20 <Wendy_> zte-pod1 is out of work.
08:53:58 <kubi> ok, i see, please let us know if you have any update about your pod
08:54:08 <Mingjiang6> jasperchiu: i think the pre-defined operations and steps are very helpful to simplify the scenario definition.
08:54:08 <kubi> zhihui_wu: hi
08:54:26 <zhihui_wu> zte-pod1 is out of work. So I can build a successful yardstick jenkins job.
08:54:37 <zhihui_wu> I can not build a successful yardstick jenkins job.
08:54:47 <jasperchiu> Mingjiang6:thank you
08:54:47 <zhihui_wu> sorry for a miss spell
08:55:31 <kubi> that's ok, please let us know if you have any question about yardstick
08:56:11 <kubi> #info due to zte-pod1 is out of work, there is no successful yardstick jenkins job.
08:56:28 <kubi> #topic JIRA status
08:56:57 <kubi> zhihui_wu:  i saw you create a new JIRA YARDSTICK-263
08:57:56 <kubi> zhihui_wu: what will you for it?
08:58:04 <zhihui_wu> I am working on solving this problem. I will feedback the result to you. Many thanks for you and Mingjiang's support.
08:58:37 <kubi> zhihui_wu: what will you do for it?
09:00:00 <Mingjiang6> #link https://gerrit.opnfv.org/gerrit/#/c/14191/
09:00:07 <kubi> #topic others
09:00:23 <Mingjiang6> please help to review "
09:00:23 <Mingjiang6> OPNFV_YARDSTICK_TC043_Latency_between_NFVI_nodes_measurements
09:00:23 <Mingjiang6> "
09:00:40 <kubi> #action all please review patch https://gerrit.opnfv.org/gerrit/#/c/14191/
09:01:19 <kubi> anything else?
09:02:01 <kubi> #endmeeting