915badc7d1
Currently a model of the cluster is constructed every time a strategy is executed, which will not scale in production or in larger environments. If Watcher intends to be used by larger envirionments it needs a more robust way to construct and maintain a model of the cluster. An in-memory cache of this model can be built up and kept fresh via notifications from services of interest in addition to periodic syncing logic. Co-Authored-By: Vincent FRANCOISE <Vincent.FRANCOISE@b-com.com> Change-Id: I338b1169049c80638c5229648c6f26ed39a9b622 |
||
---|---|---|
.. | ||
class_diagram_efficacy_indicator.png | ||
class_diagram_goal_from_strategy.png | ||
class_diagram_plugin_parameters.png | ||
get_goal_from_strategy_class_diagram.png | ||
get_goal_from_strategy_sync_sequence_diagram.png | ||
scoring-engine-in-the-cloud.png | ||
scoring-engine-inside-decision-engine.png | ||
scoring-engine-inside-scoring-module.png | ||
scoring-module-deployment.png | ||
sequence_diagram_cluster_objects_wrapper_get_latest_model.png | ||
sequence_diagram_cluster_objects_wrapper_notification.png | ||
sequence_diagram_cluster_objects_wrapper_sync.png | ||
sequence_diagram_plugin_parameters_generate_config.png | ||
sequence_diagram_plugin_parameters_load_plugin_parameters.png | ||
Watcher_Actions_Management_Functional_Need.png | ||
Watcher_Actions_Management_Functional_Need.svg |