13:00:25 <chaconpiza> #startmeeting monasca
13:00:27 <openstack> Meeting started Tue Jun 30 13:00:25 2020 UTC and is due to finish in 60 minutes.  The chair is chaconpiza. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:29 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:31 <openstack> The meeting name has been set to 'monasca'
13:00:39 <chaconpiza> Hi everyone
13:00:41 <witek> hi
13:00:46 <mbindlish> hi
13:00:56 <chaconpiza> Hello Witek
13:00:59 <chaconpiza> Hello Manik
13:01:12 <chaconpiza> The agenda as usual https://etherpad.opendev.org/p/monasca-team-meeting-agenda
13:01:38 <dougsz> hello all
13:01:47 <chaconpiza> Hello Doug
13:01:56 <chaconpiza> Let's start
13:02:16 <chaconpiza> This week a new version of monasca-agent was release
13:02:17 <Wasaac> o/
13:02:28 <chaconpiza> Based on Ussuri release
13:02:32 <chaconpiza> Hello Isaac
13:02:48 <chaconpiza> https://review.opendev.org/#/c/737933/
13:03:10 <dougsz> Thanks to all who helped with the bugfix and the new release
13:03:42 <chaconpiza> As well, we had an email with a question answered by Doug
13:04:33 <chaconpiza> The questions was if is possible to remove data from influx after some entity is removed
13:04:51 <chaconpiza> in an automatic way
13:05:49 <chaconpiza> I remember that Joseph have created a Story about it. To remove the data from influxdb after some server is removed, am I right?
13:06:17 <dougsz> hmm, sounds familiar
13:06:22 <witek> yes, there was some request going in that direction
13:07:36 <witek> he should be reading the notes, but I can also just ping him and ask if he can dig out some context around it
13:08:33 <chaconpiza> ok, thanks
13:08:40 <chaconpiza> Manik, would you like to start with an introduction about how you or your team use/deploy/enjoy Monasca?
13:08:55 <mbindlish> yeah, sure
13:09:03 <chaconpiza> #topic mbindlish introduction
13:09:18 <mbindlish> We are divide in 3 teams
13:09:29 <mbindlish> Team 1 is taking care of NFVI
13:09:56 <mbindlish> We are in team2 which is providing openstack services on top of it
13:10:09 <mbindlish> Team3 is deploying VNFs over it
13:10:48 <mbindlish> So we have responsiblities like adding more and more useful services of openstack w.r.t telecom
13:11:23 <mbindlish> Some of people from my team are working on Octavia, barbican, gnocchi and many other services.
13:12:07 <mbindlish> I am working on monasca as I have earlier some experience in a PoC in my last organization(NEC) that was for automated fault management
13:12:34 <mbindlish> Witek will be aware about that, he had as session for that thing with Akhil
13:12:54 <mbindlish> I am deploying monasca here in kubernetes and helm charts
13:13:13 <mbindlish> and using ceilometer to collect the data
13:13:22 <mbindlish> So, I am working on Ceilosca
13:14:03 <mbindlish> Integrating this with existing infra and with other existing openstack services
13:14:49 <chaconpiza> Are you working with the upstream repository of Ceilosca?
13:14:51 <witek> mbindlish was working on extending webhook notifier and integrating it with Tacker, right?
13:15:07 <mbindlish> @chaconpiza not on upstream yet
13:15:18 <mbindlish> Right witek
13:15:50 <chaconpiza> Then, are you working from a fork of Ceilosca?
13:16:33 <mbindlish> We have taken radhat containers of ceilometer and added the monasca publisher by taking refrence from Ceilosca
13:17:03 <mbindlish> But for monasca, we have docker.io containers as in monasca-docker(github)
13:18:03 <witek> which company do you work for now?
13:18:05 <mbindlish> We are actually working on Queens release on base setup of openstack and I have used ceilometer and monasca from train
13:18:21 <mbindlish> Working for Orange Business services from June 2019
13:18:36 <witek> nice
13:19:06 <witek> do you have some custom plugins for monasca-agent?
13:19:30 <mbindlish> We are not using monasca agent instead using ceilometer
13:19:32 <witek> or integrate with Prometheus exporters?
13:19:38 <witek> I see
13:19:56 <dougsz> So it is only for billing?
13:20:24 <mbindlish> For now it is for billing
13:20:38 <dougsz> How many VMs out of interest?
13:20:42 <mbindlish> Next plan is for monasca-anlaytics as well
13:21:08 <witek> the project is not maintained
13:21:26 <witek> I could give you reference to the guys who worked on it
13:21:30 <mbindlish> @dougsz For deveploment purpose we have around 7-8 vms only
13:21:47 <mbindlish> @witek, thanks, that would be really hepful
13:22:02 <mbindlish> I was trying devstack for monasca-analytics but it was failing
13:22:07 <dougsz> I see, so small at the moment
13:22:43 <mbindlish> I am in last phase of implementing ceilosca. Stucked in alarming part
13:23:15 <mbindlish> All services are running, alarm-definition was created successfully but alarm is not occuring
13:23:37 <mbindlish> metrics are coming from image.size, cpu
13:24:08 <chaconpiza> Are you in the correct Tenant/Project?
13:24:17 <mbindlish> yes
13:24:58 <chaconpiza> Other thing to check is the time synchronization
13:25:37 <mbindlish> In polling it was 60 and in pipeline it was 30
13:25:46 <mbindlish> I will check that part too
13:26:17 <mbindlish> where I can see in code, how alarming condition is occuring, just after alarm-definition creation?
13:26:36 <mbindlish> I was about to start checking in : https://github.com/openstack/monasca-api/blob/master/monasca_api/v2/reference/alarms.py
13:26:53 <mbindlish> Pls suggest on it
13:27:00 <dougsz> +1 for time sync check on all nodes hosting storm
13:27:59 <mbindlish> Is it neccesary to hav monasca-threshold, storm services installed for alarming?
13:28:08 <chaconpiza> Yes
13:28:08 <dougsz> yeah
13:28:32 <mbindlish> ok, that is missing from my side.
13:28:50 <dougsz> :D
13:28:51 <chaconpiza> Monasca-threshold  uses Storm as the core
13:28:51 <mbindlish> +1
13:29:31 <mbindlish> I was thinking only monasca-api will do so with monasca-alarming service
13:30:26 <mbindlish> So that was a brief from my side.
13:30:44 <chaconpiza> Thanks Manik, last question from my side. Where are you located?
13:30:57 <mbindlish> Gurgaon, India
13:31:02 <chaconpiza> cool
13:31:29 <chaconpiza> Ok, lets continue with next topic
13:31:49 <chaconpiza> #topic Monasca Victoria Priorities
13:32:39 <chaconpiza> I have granted perms as owner to Doug,Adrian and Witek: https://storyboard.openstack.org/#!/board/217
13:33:04 <witek> +1, now I can add cards
13:33:11 <chaconpiza> please check it is ok
13:33:32 <chaconpiza> Wasaac, let me know if you requires it too
13:34:13 <chaconpiza> I have sent a change to monasca-specs with the priorities
13:34:13 <chaconpiza> https://review.opendev.org/#/c/738596/
13:34:52 <chaconpiza> Zuul failed, I will check the reason.
13:35:20 <witek> thanks chaconpiza
13:36:42 <chaconpiza> Feel free to send a patchset in case you want to extend the details of the tasks
13:37:19 <chaconpiza> #topic AOB
13:38:02 <witek> dougsz: has there been any progress on HA setup for InfluxDB in Kolla?
13:38:02 <chaconpiza> I am struggling with the deployment of RedHat OSP16 (Based on Train) "All-in-one"
13:38:41 <witek> chaconpiza: switch to Kolla ;)
13:39:22 <chaconpiza> Actually the new  official "All-in-one" from Redhat isn't anymore based on Packstack
13:39:29 <chaconpiza> but in TripleO
13:39:46 <chaconpiza> with the services in containers
13:40:02 <chaconpiza> using podman instead of docker
13:40:48 <chaconpiza> I succeeded with the deployment in a server without web proxy
13:41:03 <chaconpiza> But stucked in servers under proxy :(
13:42:15 <dougsz> witek: I pushed a patch for consumer groups today, not sure if it's working yet :)
13:43:32 <chaconpiza> dougsz, when you deploy under a proxy, which are the measurements you are taking about?  I set proxy settings on /etc/environment
13:45:06 <dougsz> sorry, not sure I follow
13:46:35 <chaconpiza> Ok, np.
13:47:01 <chaconpiza> Let's close the meeting if there are not more topics for today.
13:47:24 <chaconpiza> Thanks again Manik for the introduction of your duties
13:47:54 <witek> mbindlish: thanks a lot, don't hesitate to ask if help needed
13:47:56 <mbindlish> Thanks for inviting me :)
13:48:04 <dougsz> +1
13:48:05 <mbindlish> Sure :)
13:48:17 <chaconpiza> See you next week, bye.
13:48:29 <witek> thanks everyone, bye
13:48:35 <mbindlish> +1
13:48:38 <mbindlish> bye
13:48:41 <dougsz> bye all
13:48:47 <chaconpiza> #endmeeting