Watcher contains an internal model of your cluster topology, including
instances and compute nodes.

When no notifications are enabled, that model is updated periodically
based on your configuration:

[watcher_cluster_data_model_collectors.baremetal]
period = 3600

[watcher_cluster_data_model_collectors.compute]
period = 3600

[watcher_cluster_data_model_collectors.storage]
period = 3600

In your case it's being updated every hour, while you are running your
audit every minute so it will very easily hit issues because the model
is out of date. Even if not getting that error, you may get unexpected
results.

On improvement you can do is to decrease the period to something close
to your interval. You could i.e. use

--interval 120 and set:

[watcher_cluster_data_model_collectors.baremetal]
period = 120

[watcher_cluster_data_model_collectors.compute]
period = 120

[watcher_cluster_data_model_collectors.storage]
period = 120


Alternatively to that schedule-based clustermodel sync, watcher has the ability 
to synchronize the model based on nova notification events. i.e. when a new vm 
is created, deleted, etc... nova can send a notification message into a queue 
and watcher consumes it and update the model. For that you need to enable 
notifications both in nova and watcher side. In watcher you need to set:

[oslo_messaging_notifications]
driver = messagingv2
transport_url = <url for notifications messaging broker>

I'd also recomend to set in [DEFAULT] section:

notification_level =

Note you also need to configure oslo_messaging_notifications in nova
service.

Usually, a recommendation is to use separated messaging broker instance
different to the one for RPCs between services.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2131043

Title:
  watcher decision engine fails when evaluating previously migrated
  instance

To manage notifications about this bug go to:
https://bugs.launchpad.net/watcher/+bug/2131043/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to