<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Hi,<div><br></div><div>I checked that both of the methods you propose work well.<br></div><div>After I add 'should_delete_outdated_entities' function to InstanceDriver, it took about 10 minutes to clear the old Instance. <br></div><div>And I added two sentences you said to Nova-cpu.conf, so the vitrage collector get notifications well.<br></div><div><br></div><div>Thank you for your help.</div><div><br></div><div>Best regards,</div><div>Won</div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">2018년 11월 22일 (목) 오후 9:35, Ifat Afek <<a href="mailto:ifatafekn@gmail.com">ifatafekn@gmail.com</a>>님이 작성:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Hi,<div><br></div><div>A deleted instance should be removed from Vitrage in one of two ways:</div><div>1. By reacting to a notification from Nova</div><div>2. If no notification is received, then after a while the instance vertex in Vitrage is considered "outdated" and is deleted</div><div><br></div><div>Regarding #1, it is clear from your logs that you don't get notifications from Nova on the second compute.</div><div>Do you have on one of your nodes, in addition to nova.conf, also a nova-cpu.conf? if so, please make the same change in this file:</div><div><br></div><div><p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman"">notification_topics =
notifications,vitrage_notifications</p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Times New Roman"">notification_driver =
messagingv2</p></div><div><br></div><div>And please make sure to restart nova compute service on that node.</div><div><br></div><div>Regarding #2, as a second-best solution, the instances should be deleted from the graph after not being updated for a while. </div><div>I realized that we have a bug in this area and I will push a fix to gerrit later today. In the meantime, you can add to </div><div>InstanceDriver class the following function:<br></div><div><br></div><div><div> @staticmethod</div><div> def should_delete_outdated_entities():</div><div> return True</div></div><div><br></div><div>Let me know if it solved your problem,<br></div><div>Ifat</div><div><br></div><div><br><div class="gmail_quote"><div dir="ltr">On Wed, Nov 21, 2018 at 1:50 PM Won <<a href="mailto:wjstk16@gmail.com" target="_blank">wjstk16@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">I attached four log files. <br></div><div dir="ltr"><div dir="ltr">I collected the logs from about 17:14 to 17:42. I created an instance of 'deltesting3' at 17:17. 7minutes later, at 17:24, the entity graph showed the dentesting3 and vitrage colletor and graph logs are appeared.</div><div dir="ltr">When creating an instance in ubuntu server, it appears immediately in the entity graph and logs, but when creating an instance in computer1 (multi node), it appears about 5~10 minutes later.</div><div dir="ltr">I deleted an instance of 'deltesting3' around 17:26.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div></div><div>After ~20minutes, there was only Apigateway. Does it make sense? did you delete the instances on ubuntu, in addition to deltesting?</div></blockquote><div><br></div><div>I only deleted 'deltesting'. After that, only the logs from 'apigateway' and 'kube-master' were collected. But other instances were working well. I don't know why only two instances are collected in the log.<br></div><div>NOV 19 In this log, 'agigateway' and 'kube-master' were continuously collected in a short period of time, but other instances were sometimes collected in long periods.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>In any case, I would expect to see the instances deleted from the graph at this stage, since they were not returned by get_all.</div><div>Can you please send me the log of vitrage-graph at the same time (Nov 15, 16:35-17:10)?</div></blockquote><div><br></div><div>Information 'deldtesting3' that has already been deleted continues to be collected in vitrage-graph.service.<br></div><div><br></div></div></div></div></div></div></div></blockquote></div></div></div></div></div></div>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>