Wednesday, 2019-02-13

*** openstackgerrit has quit IRC00:52
*** spsurya has joined #openstack-monasca03:55
akhil_jainHi! Can anyone help me with multi-node installation using devstack, what should we disable on compute nodes and is there any other specific setting? Any help would be great. Thanks!05:07
Dobroslawakhil_jain: devstack is only for development07:18
Dobroslawcould you tell us what end result you are expecting?07:18
akhil_jainDobroslaw: hi! thanks for quick response. actually i want to monitor host and when its down. need to evacuate vm.07:19
akhil_jainso can you share how you achieve multi node env setup. any doc is there for that?07:20
akhil_jainFYI, I am working on Tacker-Monasca-Congress integration07:21
akhil_jainDobroslaw:07:24
Dobroslawakhil_jain: sorry, I'm mostly working with single node installation07:24
Dobroslawit's possible to install Monasca with Kolla but I'm not sure if it support multi node, dougsz will know more about this07:24
Dobroslawalso pandy was creating multi node installations with Docker Swarm using docker images from https://github.com/monasca/monasca-docker07:24
Dobroslawbut I don't know if he created any documents about this07:25
Dobroslawthere is also https://github.com/monasca/monasca-helm but I never used it and don't know how it's working07:25
akhil_jainoh! okay, single node is working fine for me as well. need to setup multi node env. thanks for reference. i will go through them07:26
*** witek has joined #openstack-monasca07:41
Dobroslawakhil_jain: well, if single node is fine then devstack in https://github.com/openstack/monasca-api/tree/master/devstack should be fine to07:45
akhil_jainDobroslaw: yes i am already having single node setup. requirement is of multi node only07:46
*** chaconpiza has quit IRC08:31
*** chaconpiza has joined #openstack-monasca08:46
*** dougsz has joined #openstack-monasca09:07
*** openstackgerrit has joined #openstack-monasca09:54
openstackgerritMichaƂ Piotrowski proposed openstack/monasca-agent master: Update log level classification info  https://review.openstack.org/63612409:54
*** aagate has quit IRC09:55
openstackgerritAdrian Czarnecki proposed openstack/monasca-api master: [WIP] Improve coverage  https://review.openstack.org/63271811:47
*** dougsz has quit IRC12:18
*** dougsz has joined #openstack-monasca12:59
*** hosanai has joined #openstack-monasca14:49
witekCourtesy Monasca meeting reminder in #openstack-monasca: witek, jayahn,iurygregory,ezpz,igorn,haad,sc,joadavis, akiraY,tobiajo,dougsz_,fouadben, amofakhar, aagate, haruki,kaiokmo,pandiyan,charana,guilhermesp,chaconpiza,toabctl14:57
chaconpizaHi14:59
dougszhello all15:00
toabctlhi15:01
witek#startmeeting monasca15:01
openstackMeeting started Wed Feb 13 15:01:54 2019 UTC and is due to finish in 60 minutes.  The chair is witek. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
joadavishello15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: monasca)"15:01
openstackThe meeting name has been set to 'monasca'15:01
witekhi everyone15:02
Dobroslawhello15:02
toabctlhi15:02
hosanaihi15:02
witekthe agenda for today as usual here:15:02
witekhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:02
witekcould we start with merging APIs?15:03
chaconpizasure15:03
witek#topic merge APIs15:03
*** openstack changes topic to "merge APIs (Meeting topic: monasca)"15:03
chaconpizaHi, regarding the Merge Monasca APIs. In the spec is written that the monasca-common dependency can be removed from the monasca-api. We are wondering where should end up the kafka-client code, since it is being used by other modules like monasca-persister.15:03
dougszGood point - would be nice to remove that kafka client code!15:04
witekthe spec says that API relevant code should be moved15:04
witekif we remove Kafka code, we have to implement it in every component15:05
witekor make a dependency to API15:05
dougszWhat about the work to remove the forked client?15:06
dougszI suppose in the longer term we will use an external client library?15:06
witekI have picked up consumer implementation with confluent client again15:06
witekstill, some wrapper around it would be useful15:07
chaconpizaI see, so the monasca-api will continue importing from monasca-common the kafka-client lib.15:07
witekcorresponding to the modules in https://github.com/openstack/monasca-common/blob/master/monasca_common/kafka/15:08
dougszAh - I had imagined that all the monasca components would just add the external Kafka library to their requirements. I didn't think about a wrapper. Could that be it's own library?15:08
witekanother alternative would be add this wrappers to individual components directly if it simplifies things15:10
dougszyes, i'd hope it'll be pretty light weight, so that could be simpler.15:11
witekyes, new Kafka code should be simplier15:12
witekdo we have other shared code which would still live in monasca-common?15:12
chaconpizaI don't think so15:13
chaconpizaA yes...15:13
chaconpizathe alarm expression parser15:13
chaconpizait is being used in monasca-ui as well15:13
witekapi and UI?15:14
dougszThinking about adding the wrapper to each project, it scares me a little bit, given that there could be quite a few projects using it, it could easily diverge.15:14
chaconpizathe code was copied from api to common to allow UI to used it15:15
chaconpizahttps://github.com/openstack/monasca-common/commit/086b9efcaf1c64693a2083dc3ef6115de7ae7b3015:15
witekI'd say then, let's leave the other parts in monasca-common for now and finish API work first15:16
dougszSounds sensible.15:16
joadavis+115:17
Dobroslaw+115:17
witekchaconpiza: ?15:17
chaconpiza+115:18
witek:) nice, thanks15:18
dougszAnd thanks for doing the work :)15:18
witekhow is the progress by the way?15:18
chaconpizaSo far Adrian and me are extending the coverage for api and common15:19
witekcool, please ping us for reviews15:20
chaconpizathanks15:20
witeksrwilkers: are you around?15:20
srwilkershey witek15:20
srwilkersgot a bit of a late start today15:20
srwilkersi'm around15:20
witekhi15:20
witekcan we update shortly on OSH?15:21
srwilkershello :)15:21
srwilkerssure15:21
witek#topic openstack-helm15:21
*** openstack changes topic to "openstack-helm (Meeting topic: monasca)"15:21
witekI have just copied the charts from monasca-helm repo to openstack-helm-addons15:21
witekhttps://review.openstack.org/63659715:21
srwilkersnice - i saw that this morning15:22
Dobroslawbig...15:22
joadaviswow, that is a lot of yaml15:22
witekthe idea is to adopt that code to OSH standards and eventually move to OSH repo15:22
witekit is copied one to one from monasca-helm15:23
witeksrwilkers: could you point us how you would like the code to look like?15:24
srwilkersyep :) to get the linting jobs happy to get it ready for the initial merge, we'll need to mark the directories coming in with the chart as irrelevant files here: https://github.com/openstack/openstack-helm-addons/blob/master/.zuul.yaml#L16 and here: https://github.com/openstack/openstack-helm-addons/blob/master/.zuul.yaml#L2415:24
srwilkerssure, i'll attempt to without getting too much into the weeds on it15:24
witekcool, thanks15:25
srwilkersi'll pick on glance, as it's my favorite one to pick on: https://github.com/openstack/openstack-helm/tree/master/glance/templates15:25
srwilkersyou'll see we have various templates for things like the db-init job, the db-sync job, the ks-user job, etc15:26
srwilkerswe'll need to massage the various charts coming in with monasca to adopt those types of standards.  things like zookeeper and influxdb are obviously going to be different15:26
srwilkersbut at least for the monasca components themselves, we'd want them to use the same sort of patterns and standards where applicable so the user experience of the chart matches the other openstack services15:27
srwilkersi need to revisit our documentation as well, as this was documented somewhere once upon a time.  if it's not anymore, i'll work to get it updated to provide a clear footing to get things moving in the right direction15:28
witekgreat, any help and pointers to docs very appreciated15:29
srwilkersim personally excited to get this rolling, as monitoring tools have a special place in my heart15:29
witek:)15:29
srwilkersof course -- i'll give a shout here when i've got the doc situation sorted out15:29
srwilkersand feel free to ping me anytime for questions/help/pointers/whatever15:29
witekthat's our valentin's day present :)15:29
srwilkersit's a great one :D15:30
srwilkersi'm being summoned to stand up :)15:30
witek:)15:30
witekthanks srwilkers15:31
witekalso if anyone wants to help in that effort, very welcome15:31
joadavisI'd like to, just bogged down with other things15:32
joadaviszookeeper has been a thorn in my side this week.  As such, I'll mention we should move the helm charts to 3.4.13 from 3.4.10 which I see in the values.yaml15:32
witeksrwilkers: one more question, I guess we can stay with our Alpine images, at least for the start, right?15:33
witekjoadavis: I think that should not be a problem, thanks for the pointer15:34
witekwe can clarify later, let's move on15:35
witek#topic reviews15:35
*** openstack changes topic to "reviews (Meeting topic: monasca)"15:35
witekhttps://review.openstack.org/#/c/622361/15:36
joadavislooks ready for workflow approval15:37
witekthere are two things in this review: using monasca_db command in DevStack and fix in sub_alarm table definition15:37
witekin Python 3 we had a problem with String type15:39
witekhttps://review.openstack.org/#/c/63437915:39
witekthis one sets up a standard release notes job15:39
joadavisit looked good, I just didn't workflow it to give others a chance to review (trying to stick to at least having two reviews before merging)15:40
witekthe output can be checked here: http://logs.openstack.org/79/634379/1/check/build-openstack-releasenotes/d4f9c11/html/15:40
witekhttps://review.openstack.org/#/c/634922/15:41
witekthat's a trivial fix in default configuration value15:41
witekhttps://review.openstack.org/#/c/633194/15:42
witekI have given -1 on that one because I'm not sure if it works correctly15:43
joadavisglad you tested that15:43
witekthe enumeration values are still initialized with sql script: email, webhook and pagerduty15:43
*** mohankumar has joined #openstack-monasca15:44
witekon the other hand, in notification configuration all plugins are enabled15:44
witekper default15:44
witekthere is logic which should sync these during the start of the service15:45
witekfor some reason it doesn't work, but I'm not sure why15:45
witekthere are many more reviews from Thomas:15:47
witekhttps://review.openstack.org/#/q/projects:openstack/monasca+is:open+owner:%22Thomas+Bechtold%2215:47
witekmainly clean-up for oslo.config15:48
witekhttps://review.openstack.org/#/c/636150/15:48
witekFix alarm-definition-list in Python 315:48
witekthanks dougsz15:49
dougsznp15:49
witekdid you look more at client code in terms of Python 3 support?15:49
dougszI ran away15:50
witekhaha15:50
dougszI'm sure it won't take too long, just need to find the time.15:50
witekdougsz: chaconpiza: do you think it's something where piotrowskim could help?15:51
openstackgerritMerged openstack/monasca-notification master: Configure releasenotes job  https://review.openstack.org/63437915:51
witeksorry, I meant Dobroslaw, not dougsz15:51
Dobroslawjep, could be another task for him15:52
chaconpizaThere are more small task related to the hacking lib15:52
joadavisyes, several repos could use a hacking lib review15:52
chaconpizahttps://storyboard.openstack.org/#!/story/200493015:52
witekthe last two reviews from the list:15:53
witekhttps://review.openstack.org/#/c/636150/15:53
witekups15:53
witekhttps://review.openstack.org/#/q/status:open++branch:master+topic:policy-names15:53
witekthese ones are about updating the policy names to OpenStack conventions15:54
witekthe reviews have been up for a while now already15:55
witeksome more reviews?15:55
witek#topic open stage15:56
*** openstack changes topic to "open stage (Meeting topic: monasca)"15:56
DobroslawJust short info about https://github.com/monasca/monasca-docker15:56
DobroslawLooks like it's no longer possible to build monasca-api15:56
DobroslawProblem is that it's using really old PR for building https://review.openstack.org/#/c/41716315:56
Dobroslawand newer version of prometheus_client is incompatible anymore with this code15:56
DobroslawI'm trying to push changes to build Docker in zuul but zuul don't like me...15:56
witekshouldn't we use new master branch code?15:58
openstackgerritMerged openstack/monasca-notification master: Replace notification.conf with monasca-notification.conf  https://review.openstack.org/63316315:59
Dobroslawthe thing is this code is used to push some metrics to monasca-sidecar and I never properly looked into what it used for...15:59
witekI have to jump to another meeting now15:59
witekthank you everyone for joining16:00
Dobroslawthank you16:00
witekand for the productive meeting16:00
joadavisthanks16:00
witekthanks16:00
dougszthanks all16:00
witekbye16:00
Dobroslawbye16:00
chaconpizathanks, bye16:00
witek#endmeeting16:00
*** openstack changes topic to "OpenStack Monitoring as a Service | https://wiki.openstack.org/wiki/Monasca"16:00
openstackMeeting ended Wed Feb 13 16:00:25 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2019/monasca.2019-02-13-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2019/monasca.2019-02-13-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2019/monasca.2019-02-13-15.01.log.html16:00
witekDobroslaw: can you ping timothyb89 ?16:02
*** hosanai has quit IRC16:02
Dobroslawyea16:02
openstackgerritMerged openstack/monasca-persister master: Fix default alarm_state_history_driver value  https://review.openstack.org/63492216:35
*** aagate has joined #openstack-monasca16:59
openstackgerritWitold Bedyk proposed openstack/monasca-common master: Updated policy names  https://review.openstack.org/61372117:43
*** mohankumar has quit IRC17:44
*** dougsz has quit IRC17:58
*** witek has quit IRC18:12
openstackgerritMerged openstack/monasca-common master: Prepare one zuul docker job for all services  https://review.openstack.org/63208719:19
*** witek has joined #openstack-monasca20:53
*** aagate has quit IRC21:17
*** witek has quit IRC21:24
*** openstackgerrit has quit IRC22:22

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!