Hi Sanjay,
You will need to add following config options in masakarimonitors.conf under the [api] section.
auth_url password project_name username user_domain_id project_domain_id region
We have added support to install and run following masakari-monitors in the current master planned to available in Train cycle.
1. process monitor 2. instance monitor 3. introspective instance monitor
We are still working on adding support to install and run host monitors using devstack.
Regards, Tushar Patil
________________________________________ From: Sanjay K isanjayk5@gmail.com Sent: Tuesday, April 30, 2019 10:04:21 PM To: Patil, Tushar Cc: openstack-discuss@lists.openstack.org Subject: Re: [devstack][stein][masakari]Using Masakari in multihost devstack stein setup
Hi Tushar, Thanks you for your quick response on this. As I have already included the masakari-monitors plugin in my compute host's local.conf file in devstack, I have the repo present in my VM. Following the steps to set up the conf files and start the necessary masakari monitoring processes from this link https://github.com/openstack/masakari-monitors/blob/master/README.rst I get the same error when I start the 3 monitoring processes (masakari-processmonitor, masakari-hostmonitor, masakari-instancemonitor) -
stack@devstack-:/etc/masakarimonitors$ masakari-processmonitor Traceback (most recent call last): File "/usr/local/bin/masakari-processmonitor", line 10, in <module> sys.exit(main()) File "/usr/local/lib/python2.7/dist-packages/masakarimonitors/cmd/processmonitor.py", line 31, in main config.parse_args(sys.argv) File "/usr/local/lib/python2.7/dist-packages/masakarimonitors/config.py", line 32, in parse_args default_config_files=default_config_files) File "/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py", line 2127, in __call__ self._check_required_opts() File "/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py", line 2865, in _check_required_opts raise RequiredOptError(opt.namehttp://opt.name, group) oslo_config.cfg.RequiredOptError: value required for option auth-url in group [api]
After masakari setup I can file all the required binaries in my /usr/local/bin directory -
$ ls -ltr /usr/local/bin/masakari* -rwxr-xr-x 1 root root 222 Apr 17 01:55 /usr/local/bin/masakari -rwxr-xr-x 1 root root 976 Apr 21 23:41 /usr/local/bin/masakari-processmonitor.sh -rwxr-xr-x 1 root root 918 Apr 21 23:41 /usr/local/bin/masakari-hostmonitor.sh -rwxr-xr-x 1 root root 1854 Apr 29 01:01 /usr/local/bin/masakari-wsgi -rwxr-xr-x 1 root root 158 Apr 29 01:01 /usr/local/bin/masakari-status -rwxr-xr-x 1 root root 158 Apr 29 01:01 /usr/local/bin/masakari-manage -rwxr-xr-x 1 root root 158 Apr 29 01:01 /usr/local/bin/masakari-engine -rwxr-xr-x 1 root root 155 Apr 29 01:01 /usr/local/bin/masakari-api -rwxr-xr-x 1 root root 174 Apr 30 04:34 /usr/local/bin/masakari-processmonitor -rwxr-xr-x 1 root root 188 Apr 30 04:34 /usr/local/bin/masakari-introspectiveinstancemonitor -rwxr-xr-x 1 root root 175 Apr 30 04:34 /usr/local/bin/masakari-instancemonitor -rwxr-xr-x 1 root root 171 Apr 30 04:34 /usr/local/bin/masakari-hostmonitor
Please let me know is there any issue with my masakari setup with devstack and where can I find latest documentation on Masakari for using in devstack.
thanks for your pointer, best regards, Sanjay
On Tue, Apr 30, 2019 at 3:24 AM Patil, Tushar <Tushar.Patil@nttdata.commailto:Tushar.Patil@nttdata.com> wrote: Hi Sanjay,
In case of masakari-processmonitor, it only monitors processes as mentioned in the process_list.yaml which by default monitors libvirt-bin, nova-compute, instancemonitor, hostmonitor and sshd processes.
To test process failure, you should terminate any of the above processes.
In case of instancemonitor, you can shutdown the VM to test whether a notification is sent or not.
I have asked the same question in openstack forum, but not got a single response.
Sorry, I didn't notice your question on forum. I have replied above comment on forum as well.
Regards, Tushar Patil
________________________________________ From: Sanjay K <isanjayk5@gmail.commailto:isanjayk5@gmail.com> Sent: Monday, April 29, 2019 6:18:20 PM To: openstack-discuss@lists.openstack.orgmailto:openstack-discuss@lists.openstack.org Subject: [devstack][stein][masakari]Using Masakari in multihost devstack stein setup
Hi all, I have been trying to setup Masakari in a 3 node setup - 1 controller + 2 computes with minimal openstack services installed using devstack stable/stein version. All these 3 nodes are Ubuntu 16.04 VMs. I have included Masakari plugin in controller's local.conf file and included masakari-monitor in both compute node's local.conf file. I want to test out VM/process failure in my test environment. To do so, when I kill one of the qemu process created for one instance (cirros 256 flavor VMs) on one of the compute with root user login, I did not see any notification under my horizon/instance-ha section for this (I have already created Segments, Hosts under instance-ha in horizon). Also the killed process is not restarted by Masakari.
I have asked the same question in openstack forum, but not got a single response.
masakari-notification-on-process-failurehttps://ask.openstack.org/en/question/121490/masakari-notification-on-process-failure/
Whether any additional services related to Masakari need to be configured on compute hosts to detect failures since I did not find exactly the documentation related inside devstack for this.
Please let me know if I am missing anything my set up. Any helps and pointers are most appreciated.
thank you for your reply.
best regards Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding.