Tuesday, 2020-06-30

*** chaconpiza has quit IRC02:36
*** coreycb has quit IRC02:36
*** chaconpiza has joined #openstack-monasca02:38
*** coreycb has joined #openstack-monasca02:38
*** vishalmanchanda has joined #openstack-monasca04:41
*** witek has joined #openstack-monasca06:39
*** zijlboot has joined #openstack-monasca06:41
*** k_mouza has joined #openstack-monasca07:29
*** dougsz has joined #openstack-monasca07:30
*** zijlboot_ has joined #openstack-monasca07:42
*** zijlboot has quit IRC07:45
*** nikparasyr has joined #openstack-monasca08:24
*** zijlboot_ has quit IRC09:26
*** zijlboot has joined #openstack-monasca09:26
*** zijlboot has quit IRC10:55
*** zijlboot has joined #openstack-monasca10:56
dougsznikparasyr: Did you manage to get any further with the multi-node InfluxDB change? Do you mind if I push a commit based on your work to Kolla Ansible?11:08
dougszI'm working on the Monasca CI there and I can test it on a multi-node deploy there.11:08
dougszI will add you as co-author on the commit if you can share your email address11:09
dougszUnless you would like to push the change and do it the other way around11:09
*** zijlboot has quit IRC12:14
*** zijlboot has joined #openstack-monasca12:14
nikparasyr@dougsz: havent had time this week. on friday i upgraded monasca to train but i noticed the problem is still in place. havent had time to troubleshoot more. you can include me12:25
nikparasyre-mail is nik.parasyr@protonmail.com12:26
*** mbindlish has joined #openstack-monasca12:31
openstackgerritMartin Chacon Piza proposed openstack/monasca-specs master: Add Victoria release cycle priorities  https://review.opendev.org/73859612:47
dougsznikparasyr: https://review.opendev.org/#/c/738585/12:48
dougszFeel free to push changes to it if you spot anything - the CI job in the commit above isn't working yet, but we can use it to verify we have complete InfluxDB replicas12:49
chaconpizaCourtesy Monasca meeting reminder in #openstack-monasca: witek,jayahn,iurygregory,ezpz,igorn,haad,sc,joadavis, akiraY,tobiajo,dougsz,fouadben, amofakhar, haru5ny (haruki),kaiokmo,pandiyan,guilhermesp,chaconpiza,hosanai,Wasaac,bandorf,mbindlish,nikparasyr12:51
chaconpiza#startmeeting monasca13:00
openstackMeeting 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: monasca)"13:00
openstackThe meeting name has been set to 'monasca'13:00
chaconpizaHi everyone13:00
witekhi13:00
mbindlishhi13:00
chaconpizaHello Witek13:00
chaconpizaHello Manik13:00
chaconpizaThe agenda as usual https://etherpad.opendev.org/p/monasca-team-meeting-agenda13:01
dougszhello all13:01
chaconpizaHello Doug13:01
chaconpizaLet's start13:01
chaconpizaThis week a new version of monasca-agent was release13:02
Wasaaco/13:02
chaconpizaBased on Ussuri release13:02
chaconpizaHello Isaac13:02
chaconpizahttps://review.opendev.org/#/c/737933/13:02
dougszThanks to all who helped with the bugfix and the new release13:03
chaconpizaAs well, we had an email with a question answered by Doug13:03
chaconpizaThe questions was if is possible to remove data from influx after some entity is removed13:04
chaconpizain an automatic way13:04
chaconpizaI remember that Joseph have created a Story about it. To remove the data from influxdb after some server is removed, am I right?13:05
dougszhmm, sounds familiar13:06
witekyes, there was some request going in that direction13:06
witekhe should be reading the notes, but I can also just ping him and ask if he can dig out some context around it13:07
chaconpizaok, thanks13:08
chaconpizaManik, would you like to start with an introduction about how you or your team use/deploy/enjoy Monasca?13:08
mbindlishyeah, sure13:08
chaconpiza#topic mbindlish introduction13:09
*** openstack changes topic to "mbindlish introduction (Meeting topic: monasca)"13:09
mbindlishWe are divide in 3 teams13:09
mbindlishTeam 1 is taking care of NFVI13:09
mbindlishWe are in team2 which is providing openstack services on top of it13:09
mbindlishTeam3 is deploying VNFs over it13:10
mbindlishSo we have responsiblities like adding more and more useful services of openstack w.r.t telecom13:10
mbindlishSome of people from my team are working on Octavia, barbican, gnocchi and many other services.13:11
mbindlishI am working on monasca as I have earlier some experience in a PoC in my last organization(NEC) that was for automated fault management13:12
mbindlishWitek will be aware about that, he had as session for that thing with Akhil13:12
mbindlishI am deploying monasca here in kubernetes and helm charts13:12
mbindlishand using ceilometer to collect the data13:13
mbindlishSo, I am working on Ceilosca13:13
mbindlishIntegrating this with existing infra and with other existing openstack services13:14
chaconpizaAre you working with the upstream repository of Ceilosca?13:14
witekmbindlish was working on extending webhook notifier and integrating it with Tacker, right?13:14
mbindlish@chaconpiza not on upstream yet13:15
mbindlishRight witek13:15
chaconpizaThen, are you working from a fork of Ceilosca?13:15
mbindlishWe have taken radhat containers of ceilometer and added the monasca publisher by taking refrence from Ceilosca13:16
mbindlishBut for monasca, we have docker.io containers as in monasca-docker(github)13:17
witekwhich company do you work for now?13:18
mbindlishWe are actually working on Queens release on base setup of openstack and I have used ceilometer and monasca from train13:18
mbindlishWorking for Orange Business services from June 201913:18
witeknice13:18
witekdo you have some custom plugins for monasca-agent?13:19
mbindlishWe are not using monasca agent instead using ceilometer13:19
witekor integrate with Prometheus exporters?13:19
witekI see13:19
dougszSo it is only for billing?13:19
mbindlishFor now it is for billing13:20
dougszHow many VMs out of interest?13:20
mbindlishNext plan is for monasca-anlaytics as well13:20
witekthe project is not maintained13:21
witekI could give you reference to the guys who worked on it13:21
mbindlish@dougsz For deveploment purpose we have around 7-8 vms only13:21
mbindlish@witek, thanks, that would be really hepful13:21
mbindlishI was trying devstack for monasca-analytics but it was failing13:22
dougszI see, so small at the moment13:22
mbindlishI am in last phase of implementing ceilosca. Stucked in alarming part13:22
mbindlishAll services are running, alarm-definition was created successfully but alarm is not occuring13:23
mbindlishmetrics are coming from image.size, cpu13:23
chaconpizaAre you in the correct Tenant/Project?13:24
mbindlishyes13:24
chaconpizaOther thing to check is the time synchronization13:24
mbindlishIn polling it was 60 and in pipeline it was 3013:25
mbindlishI will check that part too13:25
mbindlishwhere I can see in code, how alarming condition is occuring, just after alarm-definition creation?13:26
mbindlishI was about to start checking in : https://github.com/openstack/monasca-api/blob/master/monasca_api/v2/reference/alarms.py13:26
mbindlishPls suggest on it13:26
dougsz+1 for time sync check on all nodes hosting storm13:27
mbindlishIs it neccesary to hav monasca-threshold, storm services installed for alarming?13:27
chaconpizaYes13:28
dougszyeah13:28
mbindlishok, that is missing from my side.13:28
dougsz:D13:28
chaconpizaMonasca-threshold  uses Storm as the core13:28
mbindlish+113:28
mbindlishI was thinking only monasca-api will do so with monasca-alarming service13:29
mbindlishSo that was a brief from my side.13:30
chaconpizaThanks Manik, last question from my side. Where are you located?13:30
mbindlishGurgaon, India13:30
chaconpizacool13:31
chaconpizaOk, lets continue with next topic13:31
chaconpiza#topic Monasca Victoria Priorities13:31
*** openstack changes topic to "Monasca Victoria Priorities (Meeting topic: monasca)"13:31
chaconpizaI have granted perms as owner to Doug,Adrian and Witek: https://storyboard.openstack.org/#!/board/21713:32
witek+1, now I can add cards13:33
chaconpizaplease check it is ok13:33
chaconpizaWasaac, let me know if you requires it too13:33
chaconpizaI have sent a change to monasca-specs with the priorities13:34
chaconpizahttps://review.opendev.org/#/c/738596/13:34
chaconpizaZuul failed, I will check the reason.13:34
witekthanks chaconpiza13:35
chaconpizaFeel free to send a patchset in case you want to extend the details of the tasks13:36
chaconpiza#topic AOB13:37
*** openstack changes topic to "AOB (Meeting topic: monasca)"13:37
witekdougsz: has there been any progress on HA setup for InfluxDB in Kolla?13:38
chaconpizaI am struggling with the deployment of RedHat OSP16 (Based on Train) "All-in-one"13:38
witekchaconpiza: switch to Kolla ;)13:38
chaconpizaActually the new  official "All-in-one" from Redhat isn't anymore based on Packstack13:39
chaconpizabut in TripleO13:39
chaconpizawith the services in containers13:39
chaconpizausing podman instead of docker13:40
chaconpizaI succeeded with the deployment in a server without web proxy13:40
chaconpizaBut stucked in servers under proxy :(13:41
dougszwitek: I pushed a patch for consumer groups today, not sure if it's working yet :)13:42
chaconpizadougsz, when you deploy under a proxy, which are the measurements you are taking about?  I set proxy settings on /etc/environment13:43
dougszsorry, not sure I follow13:45
chaconpizaOk, np.13:46
chaconpizaLet's close the meeting if there are not more topics for today.13:47
chaconpizaThanks again Manik for the introduction of your duties13:47
witekmbindlish: thanks a lot, don't hesitate to ask if help needed13:47
mbindlishThanks for inviting me :)13:47
dougsz+113:48
mbindlishSure :)13:48
chaconpizaSee you next week, bye.13:48
witekthanks everyone, bye13:48
mbindlish+113:48
mbindlishbye13:48
dougszbye all13:48
chaconpiza#endmeeting13:48
*** openstack changes topic to "OpenStack Monitoring as a Service | https://wiki.openstack.org/wiki/Monasca"13:48
openstackMeeting ended Tue Jun 30 13:48:47 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2020/monasca.2020-06-30-13.00.html13:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2020/monasca.2020-06-30-13.00.txt13:48
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2020/monasca.2020-06-30-13.00.log.html13:48
nikparasyrdougsz: i made a comment on the PR. dont know if i was on time. looks good to me but we probably can parametrize the influxdb ip to use based on whether its single or multi-node deployment. g2g now as its a "farewell" party to a collegue14:15
dougsznikparasyr: sounds sensible - it won't merge for some some time so no rush! thanks!14:16
*** nikparasyr has left #openstack-monasca14:38
*** k_mouza has quit IRC14:47
*** k_mouza has joined #openstack-monasca14:56
*** vishalmanchanda has quit IRC15:30
*** witek has quit IRC15:33
*** witek_ has joined #openstack-monasca16:32
*** dougsz has quit IRC16:32
*** zijlboot_ has joined #openstack-monasca16:57
*** zijlboot has quit IRC17:00
*** zijlboot_ has quit IRC17:02
*** k_mouza has quit IRC17:18
*** zijlboot has joined #openstack-monasca17:30
*** zijlboot has quit IRC17:33
*** zijlboot has joined #openstack-monasca17:34
*** witek_ has quit IRC17:37
*** zijlboot has quit IRC17:38
*** mbindlish has quit IRC17:51
-openstackstatus- NOTICE: Due to a flood of connections from random prefixes, we have temporarily blocked all AS4837 (China Unicom) source addresses from access to the Git service at opendev.org while we investigate further options.18:23
*** zijlboot has joined #openstack-monasca18:56
*** viks____ has quit IRC19:22
*** zijlboot has quit IRC20:51
*** zijlboot has joined #openstack-monasca20:52
*** zijlboot has quit IRC20:56
*** zijlboot has joined #openstack-monasca21:48
*** zijlboot has quit IRC21:49
*** zijlboot has joined #openstack-monasca21:51
*** piotrowskim has quit IRC22:22

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!