Go to file
Sumit Jamgade b620081714 Allow using file to override metric map
Override the metric map of each datasource as soon as it is created by
the manager. This override comes from a file whose path is provided by
a setting in config file.

Loading at creation time allows the correct datasource be used when
get_backend is called, this allows loading a datasource whose metric
names get updated outside the watcher's codebase.

The function 'load_metric_map' returns empty-dict in any error case.
Also in case the file is empty where safe_load is unable finds any
yaml documents, it will return None. [1]

Some minor refactoring in the test_manager file for readability and
added tests for file load and metric override.

1 - https://pyyaml.org/wiki/PyYAMLDocumentation

Change-Id: I1df16245f4c7dfd34066f3ab0553cd67154faa58
Implements: blueprint file-based-metric-map
2019-05-20 10:28:00 +02:00
2019-01-24 16:01:19 +08:00
2017-12-11 15:19:10 +03:00
2018-02-14 16:45:13 +09:00
2018-10-29 08:45:32 +00:00
2019-04-19 19:40:45 +00:00
2015-06-04 15:27:57 +02:00
2018-07-10 15:38:50 +07:00
2019-04-30 16:02:32 +08:00
2015-06-04 15:27:57 +02:00
2017-04-07 10:55:59 +08:00
2018-02-28 03:58:07 +00:00
2015-06-04 15:27:57 +02:00
2019-04-23 13:20:10 +02:00
2019-05-09 11:14:40 -04:00
2019-04-16 16:24:53 +08:00
2017-03-07 02:08:03 +00:00
2019-05-09 11:14:40 -04:00

Team and repository tags

image

Watcher

OpenStack Watcher provides a flexible and scalable resource optimization service for multi-tenant OpenStack-based clouds. Watcher provides a robust framework to realize a wide range of cloud optimization goals, including the reduction of data center operating costs, increased system performance via intelligent virtual machine migration, increased energy efficiency and more!

Description
Resource optimization service for OpenStack.
Readme 34 MiB
Languages
Python 99.7%
Shell 0.3%