Hi, Carlos
According to the data collected by @Wenjuan, it seems when the test fails,
most time is consumed by the inspector api disable_compute_host[1]
if event_type == 'compute.host.down':
inspector.disable_compute_host(hostname)
I checked the source code and it looks it will iterate through the server
list to set them to error state. So I wonder if it is related to the total
number of server in the test environment.
Could you please provide the log in apex environment so we can dig further
to find out the root cause?
BTW: as @Tomi pointed out, the inspector should be topology aware, knowing
all VM's on the host, so I think we may create the server list
in initialization phase and use the saved list when processing
`compute.host.down` event. This will be a better emulation of real
inspector.
[1] https://git.opnfv.org/cgit/doctor/tree/tests/inspector.py#n63
On Fri, Sep 9, 2016 at 7:15 PM Souville, Bertrand <
souvi...@docomolab-euro.com> wrote:
> My understanding is that Fuel team/experts are now investigating the
> issue. Let’s give them few more days…
>
>
>
> Bertrand
>
>
>
> *From:* Carlos Goncalves [mailto:carlos.goncal...@neclab.eu]
> *Sent:* Friday, September 09, 2016 11:06 AM
> *To:* dong.wenj...@zte.com.cn; Souville, Bertrand <
> souvi...@docomolab-euro.com>; r-m...@cq.jp.nec.com; tomi.juvo...@nokia.com;
> Kunzmann, Gerald <kunzm...@docomolab-euro.com>
> *Cc:* opnfv-tech-discuss@lists.opnfv.org
> *Subject:* RE: [opnfv-tech-discuss] [doctor] For the issue about the
> notification time is large than 1S
>
>
>
> 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:* dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn
> <dong.wenj...@zte.com.cn>]
> *Sent:* 09 September 2016 07:00
> *To:* Carlos Goncalves; souvi...@docomolab-euro.com; r-m...@cq.jp.nec.com;
> tomi.juvo...@nokia.com; kunzm...@docomolab-euro.com
> *Cc:* opnfv-tech-discuss@lists.opnfv.org
> *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
>
>
> [image: image003.jpg]
>
> [image: image004.jpg]
> 上海市浦东新区碧波路889号中兴通讯D3
> D3, ZTE, No. 889, Bibo Rd.
> T: +86 021 85922 M: +86 13661996389
> E: dong.wenj...@zte.com.cn
> www.ztedevice.com
>
>
> _______________________________________________
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
_______________________________________________
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
