b71fd4bef4
Following commit makes enhancements to the keystone handling inside monasca-agent: * using generic password approach that abstracts from underlying keystone version thus allows agent to be used seamlessly with either v2.0 or v3. The only relevant part is the set of parameters that one needs to supply to either monasca-reconfigure or agent.yaml configuration file * using keystone discovery - it simply means that agent will no longer enforce particular keystone version but will allow keystoneauth to pick the best match for given environment Extra: * extracted methods get_session and get_client utilize an aproach presented above and can be used outside of monasca_agent.common.keystone inside checks or detection plugins * make imports to import only modules instead specific objects * removed some redundant methods Story: 2000995 Task: 4191 Needed-By: I579f6bcd5975a32af2a255be41c9b6c4043fa1dc Needed-By: Ifee5b88ccb632222310aafb1081ecb9c9d085150 Change-Id: Iec97e50089ed31ae7ad8244b37cec128817871a5 |
||
---|---|---|
.. | ||
checks_d | ||
detection | ||
__init__.py | ||
common.py | ||
README.md | ||
test_aggregator.py | ||
test_checks_utils.py | ||
test_config.py | ||
test_keystone.py | ||
test_metrics.py | ||
test_modify_config.py | ||
test_process.py | ||
test_service_plugin.py | ||
test_services_check.py | ||
test-agent.yaml |
Tests for the mon agent.
Run with nosestests -w tests
For many tests to work an agent.yaml must be in either /etc/monasca/agent/agent.yaml or in the working directory.
Many tests require specific applications enabled in order for the test to run, these are skipped by default. See https://nose.readthedocs.org/en/latest/plugins/skip.html for details.