Found it at https://github.com/openstack/vitrage/blob/master/vitrage/entity_graph/consistency/consistency_enforcer.py#L58
Thanks, Nofar. On Tue, Aug 16, 2016 at 3:09 PM Schnider, Nofar (EXT - IL) < [email protected]> wrote: > Hi Yujun, > > I think you will find what you are looking for in > “consistency_enforcer.py”. > > Hope it helps. > > > > > > *Nofar Schnider* > > Senior Software Engineer > > Applications & Analytics, Nokia > > 16 Atir Yeda > > Kfar Saba, Israel 44643 > > M: +972 52 4326023 > > F: +972 9 793 3036 > > [image: download] > > > > *From:* Yujun Zhang [mailto:[email protected]] > *Sent:* Monday, August 15, 2016 8:49 AM > *To:* OpenStack Development Mailing List (not for usage questions) < > [email protected]>; Rosensweig, Elisha (Nokia - IL) < > [email protected]> > > > *Subject:* Re: [openstack-dev] [vitrage] scenario evaluator not enabled > by default > > > > Thanks for the expanation, Elisha. I understand the design now. > > > > But I could not find the statement which enables the evaluator after > initial phase. > > > > Could you help to point it out? > > -- > > Yujun > > > > On Thu, Aug 11, 2016 at 11:42 PM Rosensweig, Elisha (Nokia - IL) < > [email protected]> wrote: > > This is on purpose. > > When Vitrage is started, it first runs a "consistency" round where it gets > all the resources from its datasources and inserts them into the entity > graph. Once this initial phase is over, the evaluator is run over all the > entity graph to check for meaningful patterns based on it's templates. > > The reason for this process is to avoid too much churn during the initial > phase when Vitrage comes up. With so many changes done to the entity graph, > it's best to wait for the initial collection phase to finish and then to do > the analysis. > > Elisha > > > From: Yujun Zhang [mailto:[email protected]] > > Sent: Thursday, August 11, 2016 5:49 PM > > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [vitrage] scenario evaluator not enabled by > default > > > > Sorry for having put a url from forked repo. It should be > https://github.com/openstack/vitrage/commit/bdba10cb71b2fa3744e4178494fa860303ae0bbe#diff> > -6f1a277a2f6e9a567b38d646f19728bcL36 > > > But the content is the same > > -- > > Yujun > > > On Thu, Aug 11, 2016 at 10:43 PM Yujun Zhang <[email protected]> > wrote: > > It seems the scenario evaluator is not enabled when vitrage is started > in devstack installer. > > > > I dig a bit in the history, it seems the default value for the evaluator > is changed from True to False > in a history commit [1]. > > > > Is it breaking the starting of evaluator or I have missed some steps to > enable it explictily? > > > > - [1] > https://github.com/openzero-zte/vitrage/commit/bdba10cb71b2fa3744e4178494fa860303ae0bbe#diff- > 6f1a277a2f6e9a567b38d646f19728bcL36 > > > -- > > Yujun > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
