13:00:32 <chaconpiza> #startmeeting monasca
13:00:32 <opendevmeet> Meeting started Tue Sep 28 13:00:32 2021 UTC and is due to finish in 60 minutes.  The chair is chaconpiza. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:32 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:32 <opendevmeet> The meeting name has been set to 'monasca'
13:01:00 <adriancz> HI
13:01:12 <chaconpiza> Hi Adrian
13:01:52 <chaconpiza> Let's start
13:02:06 <chaconpiza> Today we have questions from community members:
13:02:43 <chaconpiza> mensis wrote: "Hi, is there any other way other than permitting monasca-agent linux user root privileges so it can monitor openstack processes (for example, nova-api process is running by nova therefore monasca-agent user can't analyse it due to permission limitations)"
13:05:39 <chaconpiza> So, in our expirience (doploying Monasca with docker-compose) we had the same situation
13:06:17 <adriancz> I think should be possible by changing  permission to files that are required to monitor openstack
13:06:23 <adriancz> but im not sure
13:06:51 <adriancz> I think we try to changed this
13:07:13 <adriancz> I think Michał Piotrkowski was working on this
13:08:04 <chaconpiza> When monasca-agent (running baremetal) in a RedHad OpenStack (OSP 16.1) it was able to get most of the metrics, but not metrics from libvirt, rabbitmq, etc.
13:09:42 <chaconpiza> in OSP 16.1 the OpenStack services are running in containers, to check the space available of those containers we had to execute monasca-agent service as root.
13:09:51 <chaconpiza> I don't see other option
13:11:32 <chaconpiza> I there is a metric based of a file that is only readable by the root, and not even by its group, then there is not other option
13:12:06 <chaconpiza> Next question:
13:12:45 <chaconpiza> jonmills_nasa wrote "Hello Monasca users -- we are having a 500 Server Error while trying to run monasca-api with apache+mod_wsgi.  I'm able to run the monasca-api standalone via gunicorn, but I'd prefer to get it running inside Apache.  This is Wallaby on CentOS 8.4 with python 3.6"
13:14:07 <chaconpiza> I would suggest to jonmills_nasa to see how it is configured in Devstack, I remember that you Adrian migrated gunicorn to apache
13:14:20 <chaconpiza> with the mod_wsgi, right?
13:14:20 <adriancz> yes
13:14:47 <adriancz> we had option to use gunicorn, wsgi or uwsgi
13:15:14 <adriancz> and default option is uwsgi
13:15:28 <adriancz> but i don't know if wsgi is still working
13:15:58 <adriancz> but definitely was possible to run monasca-api with wsgi
13:18:28 <chaconpiza> right... I see, so to clarify: there are 3 options in general: mod_wsgi, uWSGI and Gunicorn.
13:18:55 <chaconpiza> Devstack was migrated from Gunicorn to uWSGI
13:19:54 <chaconpiza> Do we used before mod_wsgi?
13:20:34 <adriancz> i check and mod_wsgi was removed
13:21:04 <adriancz> yes we used wsgi before
13:21:53 <chaconpiza> what you mean with wsgi?  uWSGI or mod_wsgi?
13:22:00 <adriancz> mod_wsgi
13:22:09 <chaconpiza> ok, thanks
13:22:43 <adriancz> wsgi and uwsgi are very similar
13:23:11 <chaconpiza> I was reading that time this introduction to the topic:
13:23:12 <chaconpiza> https://djangodeployment.com/2017/01/02/which-wsgi-server-should-i-use/
13:26:59 <chaconpiza> alright, and the next question
13:27:33 <chaconpiza> furkance wrote: Hi chaconpiza, it's been a very long time but I had a problem with the integration of monasca and cloudkitty, metrics didn't have project ID and therefore cloudkitty couldn't calculate the ratings, I remember u were going to try something, did u have any chance? thanks in advance for your help
13:33:03 <chaconpiza> This question I can't answer until I configure and launch an instance
13:33:35 <chaconpiza> I will try it in our Cluster1, so far there aren't any VM instances
13:33:51 <adriancz> I know nothing about cloudkitty
13:33:55 <adriancz> Ok
13:34:12 <adriancz> maybe there is easier solution with devstack
13:34:46 <adriancz> maybe furkance  have some script to  stack cloudkitty  with monasca
13:36:23 <chaconpiza> Cloudkitty is the module for billing based on cpu consumption, ram, space, etc.
13:36:54 <chaconpiza> he needs to know the Project ID from the libvirt metrics, as far as I remeber
13:38:14 <adriancz> Ok
13:38:42 <adriancz> i possible to add extra information to the metric
13:39:20 <adriancz> but all metric have project_id
13:39:39 <chaconpiza> Yes, I think this is what he is looking for
13:42:33 <chaconpiza> Ok, then for the today topics
13:42:59 <chaconpiza> we have two issues that are related  to each other
13:43:24 <chaconpiza> Devstack deployment with vagrant fails trying to uninstall simplejson
13:44:06 <adriancz> I'm working on thins topic
13:44:46 <chaconpiza> and Monasca-API unittest PY3x fails after an update of simplejson in upper-constrains
13:45:00 <chaconpiza> I'm on this one
13:45:18 <adriancz> problem is that pip is not able to uninstall simlejson in devstack
13:45:30 <adriancz> This well know problem
13:45:56 <adriancz> https://www.edureka.co/community/65075/error-cannot-uninstall-simplejson-not-able-install-ubuntu
13:46:01 <adriancz> https://stackoverflow.com/questions/60635962/while-installing-openstack-on-ubuntu-18-04-i-am-stuck-at-error-cannot-uninstal
13:47:20 <adriancz> Is possible to uninstall simplejson using 'sudo apt-get purge python-simplejson  '
13:48:10 <chaconpiza> did you try to deploy devstack without Monasca? I tried with same error. Using the "bento/ubuntu-20.04" vagrant box
13:48:51 <adriancz> No i didn't try
13:49:35 <chaconpiza> Ok, let's focus on these issues.
13:50:58 <chaconpiza> We got this fix this week: https://review.opendev.org/c/openstack/monasca-agent/+/810115
13:57:15 <chaconpiza> and same for this branch https://review.opendev.org/c/openstack/monasca-agent/+/810371
13:58:25 <chaconpiza> I asked to cherry pick the first one (master branch) to Wallaby, instead of create an independent change
13:58:56 <adriancz> +1
13:58:56 <chaconpiza> If we don't get it, I will send a 2nd patch set as a cherry pick from the original (master branch)
13:59:19 <chaconpiza> Ok, Adrian. Those were all topics for today.
13:59:38 <chaconpiza> We ran out of time.
14:00:01 <chaconpiza> Thanks for coming, see you next week.
14:00:27 <adriancz> Thanks Martin
14:00:34 <adriancz> See you next week
14:00:37 <chaconpiza> #endmeeting