3ffd576b79
From openstacksdk version 0.11.1 onwards, there is no way you can add service to the connection. Hence we need to monkey _find_service_filter_class method from sdk to allow to point to thee correct service filter class from masakariclient. Solution provided here is not going to work in sdk 0.9.19 and 0.10.0 versions. Because service descriptor is not supported in 0.9.19 and 0.10.0 sdk versions and profile parameter doesn't work correctly during connection initialization. Also solution provided here is not going to work in sdk 0.13.0 and above, it will still fails with below error "'Connection' object has no attribute 'ha'" this is because 'Connection' object expecting instance_ha not ha Co-Author: tpatil <tushar.vitthal.patil@gmail.com> Change-Id: Ic10d1b380abc8b3b6cc38015c9c3bf4ab7705a0c Depends-On: I24ec493f3333a5b3f6bfed9395c921fb28500065 Closes-Bug: #1779752 |
||
|---|---|---|
| doc/source | ||
| etc/masakarimonitors | ||
| masakarimonitors | ||
| releasenotes | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .testr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MANIFEST.in | ||
| README.rst | ||
| babel.cfg | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
masakari-monitors
Monitors for Masakari
Monitors for Masakari provides Virtual Machine High Availability (VMHA) service for OpenStack clouds by automatically detecting the failure events such as VM process down, provisioning process down, and nova-compute host failure. If it detect the events, it sends notifications to the masakari-api.
Original version of Masakari: https://github.com/ntt-sic/masakari
Tokyo Summit Session: https://www.youtube.com/watch?v=BmjNKceW_9A
Monitors for Masakari is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
- Free software: Apache license
- Documentation: http://docs.openstack.org/developer/masakari-monitors
- Source: http://git.openstack.org/cgit/openstack/masakari-monitors
- Bugs: http://bugs.launchpad.net/masakari-monitors
Configure masakari-monitors
Clone masakari using:
$ git clone https://github.com/openstack/masakari-monitors.gitCreate masakarimonitors directory in /etc/.
Run setup.py from masakari-monitors:
$ sudo python setup.py installCopy masakarimonitors.conf and process_list.yaml files from masakari-monitors/etc/ to /etc/masakarimonitors folder and make necessary changes to the masakarimonitors.conf and process_list.yaml files. To generate the sample masakarimonitors.conf file, run the following command from the top level of the masakari-monitors directory:
$ tox -egenconfigTo run masakari-processmonitor, masakari-hostmonitor and masakari-instancemonitor simply use following binary:
$ masakari-processmonitor $ masakari-hostmonitor $ masakari-instancemonitor
If you are intend to use bash scripts of masakari-processmonitor and masakari-hostmonitor, use following steps to install them. However, those bash shell scripts are deprecated as of the Ocata release and will be removed in the Queens release. Use above masakari-hostmonitors implemented in python instead.
Clone masakari using:
$ git clone https://github.com/openstack/masakari-monitors.gitCreate masakarimonitors directory in /etc/.
Remove '.sample' from files hostmonitor.conf.sample, processmonitor.conf.sample and proc.list.sample which exist at masakari-monitors/etc/.
Copy hostmonitor.conf, processmonitor.conf and proc.list files from masakari-monitors/etc/ to /etc/masakarimonitors folder and make necessary changes to the hostmonitor.conf, processmonitor.conf and proc.list files.
To run bash scripts of masakari-processmonitor and masakari-hostmonitor simply use following binary:
$ masakari-processmonitor.sh /etc/masakarimonitors/processmonitor.conf /etc/masakarimonitors/proc.list $ masakari-hostmonitor.sh /etc/masakarimonitors/hostmonitor.conf
Features
- TODO