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/ma... - masakari-monitor.conf: https://review.opendev.org/#/c/615715/42/ansible/roles/masakari/templates/ma... 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@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@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@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 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@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@gmail.com> wrote:
VU TAN <VUNGOCTAN252@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@ssword
[database] connection = mysql+pymysql://masakari:P@ssword@controller/masakari
