Wednesday, 2019-09-25

« Tuesday, 2019-09-24 Index Thursday, 2019-09-26 »
openstackgerritpengyuesheng proposed openstack/python-monascaclient master: Update the constraints url  https://review.opendev.org/68451606:14
*** pcaruana has joined #openstack-monasca06:42
*** witek has joined #openstack-monasca07:37
openstackgerritArseni Lipinski proposed openstack/monasca-kibana-plugin master: [WIP] Upgrade monasca-kibana-plugin for Elkstack update  https://review.opendev.org/68007507:41
witekadriancz, chaconpiza, arseni-lipinski, brtknr, Wasaac, sum12: could you please add your availability for the planning meeting for the next release?07:47
witekhttp://lists.openstack.org/pipermail/openstack-discuss/2019-September/009533.html07:47
brtknrwitek: thanks will do07:48
witekthanks brtknr07:48
chaconpizaHi, done07:54
witekthanks Martin07:56
*** ivve has joined #openstack-monasca08:01
witekadriancz, Dobroslaw: is https://review.opendev.org/649298 good to go?08:10
openstackgerritArseni Lipinski proposed openstack/monasca-kibana-plugin master: [WIP] Upgrade monasca-kibana-plugin for Elkstack update  https://review.opendev.org/68007508:40
openstackgerritAdrian Czarnecki proposed openstack/monasca-api master: Merge log-api and api  https://review.opendev.org/65124908:52
openstackgerritAdrian Czarnecki proposed openstack/monasca-api master: Update devstack plugin to support new api  https://review.opendev.org/67226308:53
openstackgerritOpenStack Release Bot proposed openstack/monasca-events-api master: Update master for stable/train  https://review.opendev.org/68464209:05
openstackgerritOpenStack Release Bot proposed openstack/monasca-log-api master: Update master for stable/train  https://review.opendev.org/68465509:14
Dobroslawwitek: yes, it's ok to merge09:25
witekthanks, W+109:25
openstackgerritMerged openstack/monasca-thresh master: Create Docker image and build in Zuul for Monasca-Thresh  https://review.opendev.org/64929809:36
openstackgerritAdrian Czarnecki proposed openstack/monasca-tempest-plugin master: Fix test_should_reject_if_wrong_content_type test  https://review.opendev.org/68141909:47
openstackgerritMerged openstack/monasca-thresh master: Push Docker image to Docker Hub from Zuul  https://review.opendev.org/67587210:06
openstackgerritArseni Lipinski proposed openstack/monasca-kibana-plugin master: [NO SUBMIT] Add mkp header for testing purposes  https://review.opendev.org/68468610:18
*** pcaruana has quit IRC10:23
*** pcaruana has joined #openstack-monasca10:36
*** witek has quit IRC10:57
*** witek has joined #openstack-monasca11:40
openstackgerritAdrian Czarnecki proposed openstack/monasca-api master: Merge log-api and api  https://review.opendev.org/65124911:49
arseni-lipinskidone12:03
arseni-lipinski(release planning)12:04
openstackgerritDobroslaw Zybort proposed openstack/monasca-agent master: Push Docker image to Docker Hub from Zuul  https://review.opendev.org/68472412:14
*** witek has quit IRC12:16
*** witek has joined #openstack-monasca12:20
witekDobroslaw: Docker image building on stable/train branch fails for monasca-agent12:26
witekhttps://review.opendev.org/68463812:27
witekbut passes for log-api12:27
witekhttps://review.opendev.org/68465312:27
Dobroslawshit, looks like https://opendev.org/openstack/requirements/ still don't have stable/train branch12:28
witekwe could wait for that, what confuses me is that the job works for log-api12:29
witekDobroslaw: I think setting new URL for UPPER_CONSTRAINTS_FILE could help12:34
witekhttps://review.opendev.org/68463912:34
openstackgerritMerged openstack/monasca-log-api master: Update master for stable/train  https://review.opendev.org/68465512:40
*** witek has quit IRC13:08
Dobroslawwitek: looks like that log-api wasn't updated with proper branch link...13:13
*** witek has joined #openstack-monasca13:22
openstackgerritDobroslaw Zybort proposed openstack/monasca-log-api master: Change repository links usage in Dockerfile and build image  https://review.opendev.org/68474913:24
Dobroslawwitek: looks like that log-api wasn't updated with proper branch link13:24
witekDobroslaw: I think https://releases.openstack.org/constraints/upper/master is the preferred location13:26
witekused everywhere in tox files13:26
witekplease note that https://releases.openstack.org/constraints/upper/train resolves even before the branch in requirements repo is cut13:28
openstackgerritMerged openstack/monasca-agent master: Push Docker image to Docker Hub from Zuul  https://review.opendev.org/68472413:39
Dobroslawwitek: will looks into it tomorrow13:57
*** sgrasley has joined #openstack-monasca13:59
witekDobroslaw: cool, thanks14:00
openstackgerritDobroslaw Zybort proposed openstack/monasca-log-api master: Change repository links usage in Dockerfile and build image  https://review.opendev.org/68474914:05
*** chaconpiza has quit IRC14:06
Dobroslawwitek: I think it should be fixed now14:07
Dobroslawthx for this idea14:08
Dobroslawwould be nice to update all other images same way but I'm not sure if will have time tomorrow for that14:09
witekCourtesy 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,toabctl,hosanai,Wasaac,brtknr14:54
brtknro/ witek14:54
scyo14:54
witekhi14:54
witekwe still have 5 mins14:54
scit's enought to click on "Workflow + 1" button ;-)14:56
openstackgerritMerged openstack/monasca-ui master: Add content-type field and change link in dashboard  https://review.opendev.org/67460114:58
scwhat I was telling you?14:59
witek:)15:00
scI'm on the mission of clearing the priority patches list15:00
witek+115:00
witeklet's start15:00
witek#startmeeting monasca15:00
openstackMeeting started Wed Sep 25 15:00: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:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
Dobroslawhi15:01
witekhello brtknr, sc, Dobroslaw15:01
brtknrtthello15:01
witekthe agenda is very light today:15:02
witekhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:02
witekso please add topics if you have some15:02
witek#topic Release candidate for Train15:02
brtknrdb per tenant15:02
*** openstack changes topic to "Release candidate for Train (Meeting topic: monasca)"15:02
witekbrtknr: added to the etherpad15:03
brtknrwitek: thanks for adding :)15:03
witekthe release team has created patches for releasing all the remaining repositories15:03
scwhat do we have to do?15:04
witekrelease liaison or PTL has to confirm these15:05
witekmost of the changes have been merged already15:05
scanything we are missing to merge?15:05
sctomorrow I'll be available most of the day15:05
witekalso, stable/train branches have been cut with these releases15:05
witekI15:05
witekI've kept api and notification on hold as it would be good to include last changes from these repos in Train15:06
witekI'm referring to:15:07
witekhttps://review.opendev.org/65124915:07
witekhttps://review.opendev.org/67481215:07
scthere was a good reason why I didn't do +2 W+115:08
DobroslawAdrian is quite happy with merging apis change15:09
witekDobroslaw: have you been testing this change, I've seen your +1 on older PS15:11
witek?15:11
Dobroslawunfortunately lately no...15:11
witeklet's try to push these two in the next days15:12
witekI'll have to cut the branch next week latest15:12
witekTrain release schedule is available here:15:13
witekhttps://releases.openstack.org/train/schedule.html15:13
witekwith final release on 16 October 201915:13
brtknris there any possibility of incorporating db per tenant changes?15:14
witekchecking15:15
witekthe change in release repo hasn't merged yet15:16
witeklet's talk about it in a minute15:16
brtknrokay15:17
witekare there any questions about release schedule?15:17
witek#topic Ussuri planning meeting15:18
*** openstack changes topic to "Ussuri planning meeting (Meeting topic: monasca)"15:18
witekthanks a lot for filling in the survey15:18
witekhttps://doodle.com/poll/ugxr89tqmkfwa5r715:18
witekcurrently, Oct 16-17 seem to be the best days15:19
witekif nothing changes, I'll post to the list with these two days15:20
witekand we can start collecting topics and features for the next cycle15:21
*** openstackgerrit has quit IRC15:21
witekI'll update the etherpad for that15:21
witekdo these dates work for everyone?15:22
scthey work for me15:22
witeknice15:22
witek#topic InfluxDB database per tenant15:23
*** openstack changes topic to "InfluxDB database per tenant (Meeting topic: monasca)"15:23
witekhttps://review.opendev.org/#/q/status:open++branch:master+topic:story/200633115:23
witekbrtknr: I've reviewed the persister change today15:24
witekhave you evaluated the impact on write throughput?15:24
brtknrwitek: yes I saw, dougsz is not here atm, I haven't suffered much from write performance, mostly read... this change is to mostly mitigate that15:25
brtknrbut i can see this being a problem where there are large number of projects all posting metrics to the same database15:25
brtknrwitek: do you have a suggestion for a method to measure write throughput?15:27
witekthere are some scripts available in https://github.com/monasca/monasca-perf15:28
witekbut I'm not sure how relevant they are, many might be obsolete15:29
*** pcaruana has quit IRC15:30
brtknrwitek: so you're mostly okay with the migration tool and the read side of things?15:32
witekI've started with the persister, the code is clean and nice, I'm only worried about increasing number of requests to InfluxDB15:33
witekI'll think about it a little longer15:34
witeklet me get back to it tomorrow15:34
brtknris it feasible to have lots of kafka topics?15:34
brtknre.g. one per tenant?15:35
witekI think it might be a good approach, but we'd have to introduce management of Kafka topics15:36
brtknrin a single tenant case, the perfomance is the same as before... when there are two tenants, the perforance will depend on how interleaved the activity is15:36
brtknrmore interleaved, less performant15:36
witekwould your change affect performance with option `db_per_tenant` disabled?15:37
brtknrwitek: with db_per_tenant disabled, it will be the same outcome as before15:38
brtknrwitek: actually, i am wrong there15:39
brtknrIt would be a simple change to revert to former behaviour when db_per_tenant is disabled15:40
witekyes, see you point15:40
witeklet me get back to it tomorrow15:40
witekanother question, how important is it for you to include in stable/train branch?15:41
brtknrwe are keen to get it in but not if you dont think its quite ready15:43
brtknrwe were aiming for stable/train15:43
witekare you building from official stable releases, or have some downstream process for building deliveries?15:45
*** ivve has quit IRC15:45
witekif you strongly rely on stable/train release I'd try to push it in15:45
witekanyway, I've blocked cutting the release for now15:48
witeklet's get back to it tomorrow15:48
witekdo we have any other topics for today?15:50
joadavisNot much from me, just my list of long running topics.15:50
witekgo on, we have 10 minutes :)15:51
joadavisI recently looked at monasca events listener again.  The ceilometer events code may not be very suitable for our use, so I started looking at vitrage for an example15:51
joadavisbasing something on the current version of oslo_messaging is likely the best option15:52
witekDobroslaw, adriancz: do you remember if we had some prototype code for events agent?15:52
DobroslawI remember only api part15:53
Dobroslawdon't know about agent15:54
witekapi is merged, but I think we also had some code created during investigation, not sure of that though15:54
brtknrwitek: sorry, I meant to answer earlier... we mostly use upstream releases, we'd usually rather not maintain our own downstream process.15:54
joadavisbrtknr: that is a good approach. :)15:55
witekjoadavis: do we need to update the spec15:55
witekbrtknr: thanks15:55
joadavisso far the spec is ok.  If we get a prototype we can adjust the spec to match15:56
joadavisI'd like to work more on it, but have a lot of other things with higher priority15:56
joadavis(and likely should bump the monasca-ceilometer publisher submission to ceilometer first)15:57
witeklet's prepare some material about events agent for the planning meeting, so that we can prioritize it for the next cycle15:59
witekI have to wrap up, thanks for joining and the discussion16:00
joadavisthanks all16:00
witeksee you next week, 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 Sep 25 16:00:38 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-09-25-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2019/monasca.2019-09-25-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2019/monasca.2019-09-25-15.00.log.html16:00
Dobroslawbye16:02
*** ivve has joined #openstack-monasca16:53
*** witek has quit IRC17:07
*** sgrasley has quit IRC17:36
*** ivve has quit IRC23:28
« Tuesday, 2019-09-24 Index Thursday, 2019-09-26 »

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