Open Stack

Honjo,

Assuming the masakari instance monitor is up and running,
What is the actual USE CASE / TEST CASE for demonstrating instance monitoring ?

e.g. is it ?

·         launch a VM

·         ps -ef | fgrep qemu        // to find the qemu process containing the running VM

·         kill -9 <qemu-pid>

·

·         Logs ?

o    will there be any logs from instance monitor that it detected a failure ?

·

·         instance-monitor will report VM failure to masakari-engine

·         masakari-engine

o    Logs ?

§  will  there be any logs from masakari-engine that it received notification of failure ?

o    then will masakari-engine make the appropriate NOVA calls to recover the VM ?


let me know if this is correct,
Greg.



From: Greg Waines <Greg.Waines at windriver.com>
Reply-To: "openstack-dev at lists.openstack.org" <openstack-dev at lists.openstack.org>
Date: Monday, December 11, 2017 at 7:17 AM
To: "openstack-dev at lists.openstack.org" <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [masakari] problems starting up masakari instance monitoring in devstack @ master

thanks Honjo,

I’ll try this out now.

I’m assuming that it is ok to start ONLY the instance-monitor if that’s all i want to test.
Is that correct ?

In that case, following the instructions you pointed me at,
I would do the following:

·         setup devstack

o   i.e. with ‘enable_plugin masakari git://git.openstack.org/openstack/masakari’

·

·         ( don’t need corosync and pacemaker )

·

·         install & startup client

o   cd

o   git clone https://github.com/openstack/python-masakariclient.git

o   cd python-masakariclient

o   sudo python setup.py build

o   sudo python setup.py install

·

·         install & startup instance monitor

o   cd

o   git clone https://github.com/openstack/masakari-monitors.git

o   sudo mkdir /etc/masakarimonitors

o   cd masakari-monitors

o   sudo python setup.py build

o   sudo python setup.py install

o

o   sudo masakari-instancemonitor &

Is this correct ?

Greg.




From: Rikimaru Honjo <honjo.rikimaru at po.ntt-tx.co.jp>
Reply-To: "openstack-dev at lists.openstack.org" <openstack-dev at lists.openstack.org>
Date: Thursday, December 7, 2017 at 12:24 AM
To: "openstack-dev at lists.openstack.org" <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [masakari] problems starting up masakari instance monitoring in devstack @ master

Hello Greg,

I forgot to tell you.

Please use process_list.yaml instead of proc.list.sample.

On 2017/12/07 14:03, Rikimaru Honjo wrote:
Hello Greg,
Please use masakarimonitors.conf instead of hostmonitor.conf and processmonitor.conf.
You can generate it by "tox -egenconfig".
hostmonitor.conf and processmonitor.conf are used for monitors implemented by shell script.
masakarimonitors.conf is a configuration file for monitors implemented by python that you installed.
And, we are preparing setting guides.
Please see it if you are good.
masakari:
https://review.openstack.org/#/c/489570/
masakari-monitors:
https://review.openstack.org/#/c/489095/
Best regards,
On 2017/12/06 22:48, Waines, Greg wrote:
I am just getting started working with masakari.
I am working on master.

I have setup Masakari in Devstack (see details at end of email) ... which starts up masakari-engine and masakari-api processes.

I have git cloned the masakari-monitors and started them up (roughly) following the instructions at https://github.com/openstack/masakari-monitors .
Specifically:
# install & startup monitors
cd
git clone https://github.com/openstack/masakari-monitors.git
cd masakari-monitors
sudo python setup.py install
cd
sudo mkdir /etc/masakarimonitors
sudo cp ~/masakari-monitors/etc/masakarimonitors/hostmonitor.conf.sample /etc/masakarimonitors/hostmonitor.conf
sudo cp ~/masakari-monitors/etc/masakarimonitors/processmonitor.conf.sample /etc/masakarimonitors/processmonitor.conf
sudo cp ~/masakari-monitors/etc/masakarimonitors/proc.list.sample /etc/masakarimonitors/proc.list
cd ~/masakari-monitors/masakarimonitors/cmd
sudo masakari-processmonitor.sh /etc/masakarimonitors/processmonitor.conf /etc/masakarimonitors/proc.list &
sudo masakari-hostmonitor.sh /etc/masakarimonitors/hostmonitor.conf &
sudo /usr/bin/python ./instancemonitor.py &

However the instancemonitor.py starts and exits ... and does not appear to start any process(es) ... with no error messages and no log file.

Is this the correct way to startup masakari instance monitoring ?

Greg.




My Masakari setup in Devstack

sudo useradd -s /bin/bash -d /opt/stack -m stack
echo "stack ALL=(ALL) NOPASSWD: ALL" | sudo tee /etc/sudoers.d/stack
sudo su - stack

git clone https://github.com/openstack-dev/devstack
cd devstack

                                                 local.conf file:
[[local|localrc]]
ADMIN_PASSWORD=admin
DATABASE_PASSWORD=admin
RABBIT_PASSWORD=admin
SERVICE_PASSWORD=admin
# setup Neutron services
disable_service n-net
enable_service q-svc
enable_service q-agt
enable_service q-dhcp
enable_service q-l3
enable_service q-meta
# ceilometer
enable_plugin ceilometer https://git.openstack.org/openstack/ceilometer
enable_plugin aodh https://git.openstack.org/openstack/aodh
# heat
enable_plugin heat https://git.openstack.org/openstack/heat
# vitrage
enable_plugin vitrage https://git.openstack.org/openstack/vitrage
enable_plugin vitrage-dashboard https://git.openstack.org/openstack/vitrage-dashboard
# masakari
enable_plugin masakari git://git.openstack.org/openstack/masakari


./stack.sh





__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org<mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


--
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
Rikimaru Honjo
E-mail:honjo.rikimaru at po.ntt-tx.co.jp<mailto:honjo.rikimaru at po.ntt-tx.co.jp>


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org<mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171211/8083ceb5/attachment.html>