Open Stack

Hi Vu Tan,

I'm trying to install Masakari using source code to reproduce the issue.
If I hit the same issue as yours, I will troubleshoot this issue and let you know the solution or will update you what steps I have followed to bring up Masakari services successfully.

Regards,
Tushar Patil

________________________________________
From: Vu Tan <vungoctan252 at gmail.com>
Sent: Monday, July 22, 2019 12:33 PM
To: Gaëtan Trellu
Cc: Patil, Tushar; openstack-discuss at lists.openstack.org
Subject: Re: [masakari] how to install masakari on centos 7

Hi Patil,
May I know when the proper document for masakari is released ? I have configured conf file in controller and compute node, it seems running but it is not running as it should be, a lots of error in logs, here is a sample log:

2.7/site-packages/oslo_config/cfg.py:3024
2019-07-19 10:25:26.360 7745 DEBUG oslo_service.service [-] bindir                         = /usr/local/bin log_opt_values /usr/lib/
python2.7/site-packages/oslo_config/cfg.py:3024
2019-07-19 18:46:21.291 7770 ERROR masakari   File "/usr/lib/python2.7/site-packages/oslo_service/service.py", line 65, in _is_daemo
n
2019-07-19 18:46:21.291 7770 ERROR masakari     is_daemon = os.getpgrp() != os.tcgetpgrp(sys.stdout.fileno())
2019-07-19 18:46:21.291 7770 ERROR masakari OSError: [Errno 5] Input/output error
2019-07-19 18:46:21.291 7770 ERROR masakari
2019-07-19 18:46:21.300 7745 CRITICAL masakari [-] Unhandled error: OSError: [Errno 5] Input/output error
2019-07-19 18:46:21.300 7745 ERROR masakari Traceback (most recent call last):
2019-07-19 18:46:21.300 7745 ERROR masakari   File "/usr/bin/masakari-api", line 10, in <module>

I dont know if it is missing package or wrong configuration


On Thu, Jul 11, 2019 at 6:14 PM Gaëtan Trellu <gaetan.trellu at incloudus.com<mailto:gaetan.trellu at incloudus.com>> wrote:
You will have to enable the debit, debug = true and check the APi log.

Did you try to use the openstack CLi ?

Gaetan

On Jul 11, 2019 12:32 AM, Vu Tan <vungoctan252 at gmail.com<mailto:vungoctan252 at gmail.com>> wrote:
I know it's just a warning, just take a look at this image:
[image.png]
it's just hang there forever, and in the log show what I have shown to you

On Wed, Jul 10, 2019 at 8:07 PM Gaëtan Trellu <gaetan.trellu at incloudus.com<mailto:gaetan.trellu at incloudus.com>> wrote:
This is just a warning, not an error.

On Jul 10, 2019 3:12 AM, Vu Tan <vungoctan252 at gmail.com<mailto:vungoctan252 at gmail.com>> wrote:
Hi Gaetan,
I follow you the guide you gave me, but the problem still persist, can you please take a look at my configuration to see what is wrong or what is missing in my config ?
the error:
2019-07-10 14:08:46.876 17292 WARNING keystonemiddleware._common.config [-] The option "__file__" in conf is not known to auth_token
2019-07-10 14:08:46.876 17292 WARNING keystonemiddleware._common.config [-] The option "here" in conf is not known to auth_token
2019-07-10 14:08:46.882 17292 WARNING keystonemiddleware.auth_token [-] AuthToken middleware is set with keystone_authtoken.service_

the config:

[DEFAULT]
enabled_apis = masakari_api
log_dir = /var/log/kolla/masakari
state_path = /var/lib/masakari
os_user_domain_name = default
os_project_domain_name = default
os_privileged_user_tenant = service
os_privileged_user_auth_url = http://controller:5000/v3
os_privileged_user_name = nova
os_privileged_user_password = P at ssword
masakari_api_listen = controller
masakari_api_listen_port = 15868
debug = False
auth_strategy=keystone

[wsgi]
# The paste configuration file path
api_paste_config = /etc/masakari/api-paste.ini

[keystone_authtoken]
www_authenticate_uri = http://controller:5000
auth_url = http://controller:5000
auth_type = password
project_domain_id = default
project_domain_name = default
user_domain_name = default
user_domain_id = default
project_name = service
username = masakari
password = P at ssword
region_name = RegionOne

[oslo_middleware]
enable_proxy_headers_parsing = True

[database]
connection = mysql+pymysql://masakari:P@ssword@controller/masakari



On Tue, Jul 9, 2019 at 10:25 PM Vu Tan <vungoctan252 at gmail.com<mailto:vungoctan252 at gmail.com>> wrote:
Thank Patil Tushar, I hope it will be available soon

On Tue, Jul 9, 2019 at 8:18 AM Patil, Tushar <Tushar.Patil at nttdata.com<mailto:Tushar.Patil at nttdata.com>> wrote:
Hi Vu and Gaetan,

Gaetan, thank you for helping out Vu in setting up masakari-monitors service.

As a masakari team ,we have noticed there is a need to add proper documentation to help the community run Masakari services in their environment. We are working on adding proper documentation in this 'Train' cycle.

Will send an email on this mailing list once the patches are uploaded on the gerrit so that you can give your feedback on the same.

If you have any trouble in setting up Masakari, please let us know on this mailing list or join the bi-weekly IRC Masakari meeting on the #openstack-meeting IRC channel. The next meeting will be held on 16th July 2019 @0400 UTC.

Regards,
Tushar Patil

________________________________________
From: Vu Tan <vungoctan252 at gmail.com<mailto:vungoctan252 at gmail.com>>
Sent: Monday, July 8, 2019 11:21:16 PM
To: Gaëtan Trellu
Cc: openstack-discuss at lists.openstack.org<mailto:openstack-discuss at lists.openstack.org>
Subject: Re: [masakari] how to install masakari on centos 7

Hi Gaetan,
Thanks for pinpoint this out, silly me that did not notice the simple "error InterpreterNotFound: python3". Thanks a lot, I appreciate it

On Mon, Jul 8, 2019 at 9:15 PM <gaetan.trellu at incloudus.com<mailto:gaetan.trellu at incloudus.com><mailto:gaetan.trellu at incloudus.com<mailto:gaetan.trellu at incloudus.com>>> wrote:
Vu Tan,

About "auth_token" error, you need "os_privileged_user_*" options into
your masakari.conf for the API.
As mentioned previously please have a look here to have an example of
configuration working (for me at least):

- masakari.conf:
https://review.opendev.org/#/c/615715/42/ansible/roles/masakari/templates/masakari.conf.j2
- masakari-monitor.conf:
https://review.opendev.org/#/c/615715/42/ansible/roles/masakari/templates/masakari-monitors.conf.j2

About your tox issue make sure you have Python3 installed.

Gaëtan

On 2019-07-08 06:08, Vu Tan wrote:

> Hi Gaetan,
> I try to generate config file by using this command tox -egenconfig on
> top level of masakari but the output is error, is this masakari still
> in beta version ?
> [root at compute1 masakari-monitors]# tox -egenconfig
> genconfig create: /root/masakari-monitors/.tox/genconfig
> ERROR: InterpreterNotFound: python3
> _____________________________________________________________ summary
> ______________________________________________________________
> ERROR:  genconfig: InterpreterNotFound: python3
>
> On Mon, Jul 8, 2019 at 3:24 PM Vu Tan <vungoctan252 at gmail.com<mailto:vungoctan252 at gmail.com><mailto:vungoctan252 at gmail.com<mailto:vungoctan252 at gmail.com>>> wrote:
> Hi,
> Thanks a lot for your reply, I install pacemaker/corosync,
> masakari-api, maskari-engine on controller node, and I run masakari-api
> with this command: masakari-api, but I dont know whether the process is
> running like that or is it just hang there, here is what it shows when
> I run the command, I leave it there for a while but it does not change
> anything :
> [root at controller masakari]# masakari-api
> 2019-07-08 15:21:09.946 30250 INFO masakari.api.openstack [-] Loaded
> extensions: ['extensions', 'notifications', 'os-hosts', 'segments',
> 'versions']
> 2019-07-08 15:21:09.955 30250 WARNING keystonemiddleware._common.config
> [-] The option "__file__" in conf is not known to auth_token
> 2019-07-08 15:21:09.955 30250 WARNING keystonemiddleware._common.config
> [-] The option "here" in conf is not known to auth_token
> 2019-07-08 15:21:09.960 30250 WARNING keystonemiddleware.auth_token [-]
> AuthToken middleware is set with
> keystone_authtoken.service_token_roles_required set to False. This is
> backwards compatible but deprecated behaviour. Please set this to True.
> 2019-07-08 15:21:09.974 30250 INFO masakari.wsgi [-] masakari_api
> listening on 127.0.0.1:15868<http://127.0.0.1:15868><http://127.0.0.1:15868>
> 2019-07-08 15:21:09.975 30250 INFO oslo_service.service [-] Starting 4
> workers
> 2019-07-08 15:21:09.984 30274 INFO masakari.masakari_api.wsgi.server
> [-] (30274) wsgi starting up on http://127.0.0.1:15868
> 2019-07-08 15:21:09.985 30275 INFO masakari.masakari_api.wsgi.server
> [-] (30275) wsgi starting up on http://127.0.0.1:15868
> 2019-07-08 15:21:09.992 30277 INFO masakari.masakari_api.wsgi.server
> [-] (30277) wsgi starting up on http://127.0.0.1:15868
> 2019-07-08 15:21:09.994 30276 INFO masakari.masakari_api.wsgi.server
> [-] (30276) wsgi starting up on http://127.0.0.1:15868
>
> On Sun, Jul 7, 2019 at 7:37 PM Gaëtan Trellu
> <gaetan.trellu at incloudus.com<mailto:gaetan.trellu at incloudus.com><mailto:gaetan.trellu at incloudus.com<mailto:gaetan.trellu at incloudus.com>>> wrote:
>
> Hi Vu Tan,
>
> Masakari documentation doesn't really exist... I had to figured some
> stuff by myself to make it works into Kolla project.
>
> On controller nodes you need:
>
> - pacemaker
> - corosync
> - masakari-api (openstack/masakari repository)
> - masakari- engine (openstack/masakari repository)
>
> On compute nodes you need:
>
> - pacemaker-remote (integrated to pacemaker cluster as a resource)
> - masakari- hostmonitor (openstack/masakari-monitor repository)
> - masakari-instancemonitor (openstack/masakari-monitor repository)
> - masakari-processmonitor (openstack/masakari-monitor repository)
>
> For masakari-hostmonitor, the service needs to have access to systemctl
> command (make sure you are not using sysvinit).
>
> For masakari-monitor, the masakari-monitor.conf is a bit different, you
> will have to configure the [api] section properly.
>
> RabbitMQ needs to be configured (as transport_url) on masakari-api and
> masakari-engine too.
>
> Please check this review[1], you will have masakari.conf and
> masakari-monitor.conf configuration examples.
>
> [1] https://review.opendev.org/#/c/615715
>
> Gaëtan
>
> On Jul 7, 2019 12:08 AM, Vu Tan <vungoctan252 at gmail.com<mailto:vungoctan252 at gmail.com><mailto:vungoctan252 at gmail.com<mailto:vungoctan252 at gmail.com>>> wrote:
>
> VU TAN <VUNGOCTAN252 at GMAIL.COM<mailto:VUNGOCTAN252 at GMAIL.COM><mailto:VUNGOCTAN252 at GMAIL.COM<mailto:VUNGOCTAN252 at GMAIL.COM>>>
>
> 10:30 AM (35 minutes ago)
>
> to openstack-discuss
>
> Sorry, I resend this email because I realized that I lacked of prefix
> on this email's subject
>
> Hi,
>
> I would like to use Masakari and I'm having trouble finding a step by
> step or other documentation to get started with. Which part should be
> installed on controller, which is should be on compute, and what is the
> prerequisite to install masakari, I have installed corosync and
> pacemaker on compute and controller nodes, , what else do I need to do
> ?  step I have done so far:
> - installed corosync/pacemaker
> - install masakari on compute node on this github repo:
> https://github.com/openstack/masakari
> - add masakari in to mariadb
> here is my configuration file of masakari.conf, do you mind to take a
> look at it, if I have misconfigured anything?
>
> [DEFAULT]
> enabled_apis = masakari_api
>
> # Enable to specify listening IP other than default
> masakari_api_listen = controller
> # Enable to specify port other than default
> masakari_api_listen_port = 15868
> debug = False
> auth_strategy=keystone
>
> [wsgi]
> # The paste configuration file path
> api_paste_config = /etc/masakari/api-paste.ini
>
> [keystone_authtoken]
> www_authenticate_uri = http://controller:5000
> auth_url = http://controller:5000
> auth_type = password
> project_domain_id = default
> user_domain_id = default
> project_name = service
> username = masakari
> password = P at ssword
>
> [database]
> connection = mysql+pymysql://masakari:P@ssword@controller/masakari
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.