As I’ve already commented in the patch you submitted to Gerrit [1]: no, we should not extend the accepted max notification time from 1s to anything higher than that.
Currently our Doctor tests are passing in Apex in all available PODs as well as local environments (e.g. devstack). For Apex, the notification time is around 250ms which is much lower than the max 1 second. If we cannot get it green light in any other scenario/installer, we don’t claim any support. Carlos [1] https://gerrit.opnfv.org/gerrit/#/c/20627 From: [email protected] [mailto:[email protected]] Sent: 09 September 2016 07:00 To: Carlos Goncalves; [email protected]; [email protected]; [email protected]; [email protected] Cc: [email protected] Subject: [opnfv-tech-discuss] [doctor] For the issue about the notification time is large than 1S Hi doctors, For the issue about the notification time is large than 1S. I check the log and find out that from the inspector received the event to nova-api begin to handle the reset_state is taken up most of the time, about over 80%. For example, the total notification time is 2.26s, the process of inspector takes 1.983s. In the test inspector script, we find all the VM under all telant, and then set all the VM states as error. As we need to improve the performance,but it can not be handle in a short time. Shall we extned 1S to 3S or change back to no failed to notification time calculation to let functest green? Meanwhile doing the performance improvement, then change it back? Any suggestions will be welcome. Thank you~ BR, dwj 董文娟 Wenjuan Dong 控制器四部 / 无线产品 Controller Dept Ⅳ. / Wireless Product Operation [icon] [logo] 上海市浦东新区碧波路889号中兴通讯D3 D3, ZTE, No. 889, Bibo Rd. T: +86 021 85922 M: +86 13661996389 E: [email protected]<mailto:[email protected]> www.ztedevice.com<http://www.ztedevice.com/>
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
