15:00:51 <witek> #startmeeting monasca
15:00:52 <openstack> Meeting started Wed Apr 24 15:00:51 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:54 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:56 <openstack> The meeting name has been set to 'monasca'
15:01:05 <witek> hi dougsz
15:01:07 <witek> hi joadavis
15:01:19 <haru5ny> hi
15:01:28 <witek> hi haru5ny and koji_n
15:01:31 <koji_n> hello
15:01:36 <hosanai> hi
15:01:56 <witek> nice attendance today, hello hosanai
15:02:13 <witek> the agenda at usual place:
15:02:16 <witek> https://etherpad.openstack.org/p/monasca-team-meeting-agenda
15:02:22 <Fdaisuke_> Hi,
15:02:27 <witek> hi Fdaisuke_
15:02:52 <witek> let's start with reviews
15:02:58 <witek> #topic reviews
15:03:09 <witek> https://review.opendev.org/#/c/652267/
15:03:33 <joadavis> Thanks for the approval.
15:03:48 <joadavis> Will be backporting it soon
15:04:06 <joadavis> I'm confused though why Zuul gave it a -2 verify when all the tests listed have passed
15:04:07 <witek> gate pipeline failed
15:04:31 <witek> there was a problem with legacy-tempest-dsvm-monasca-transform-python-functional job
15:04:34 <joadavis> may have to start over with a full recheck (I do miss the reverify functionality)
15:04:51 <dougsz> Didn't even know about reverify!
15:05:26 <joadavis> it used to work (so I still try it sometimes) but I think it was dropped a couple Zuul versions ago
15:06:03 <witek> anything else on that one?
15:06:18 <joadavis> nope, will add you as a reviewer on the cherry picks
15:06:26 <witek> ok
15:06:28 <witek> thanks
15:06:44 <witek> https://review.opendev.org/#/c/654940/
15:07:51 <joadavis> good catch on that one dougsz
15:08:02 <witek> have you tested it in Queens?
15:08:11 <joadavis> Is it needed for Rocky and Stein also?
15:08:26 <dougsz> Not so much a catch :) we saw the issue in production a recent queens deploy
15:08:35 <dougsz> *in a
15:09:07 <dougsz> I think it may be in Rocky already
15:09:48 <dougsz> I will check
15:09:52 <joadavis> oh, right, I see the date for the master commit was May 2018
15:09:53 <witek> merged on May 10, 2018
15:10:00 <joadavis> :)
15:10:52 <witek> any other reviews need attention?
15:11:33 <witek> #topic PTG planning
15:11:41 <dougsz> ^witek:  worked in queens when I manually applied it
15:12:13 <witek> dougsz: thanks, will have a look after the meeting
15:12:40 <witek> the etherpad for PTG planning is here:
15:12:45 <witek> https://etherpad.openstack.org/p/monasca-ptg-train
15:13:18 <witek> we'll have sessions on Friday and Saturday
15:13:24 <witek> 9-17 MDT
15:14:18 <witek> I'll try to sort the topics to the straw-man agenda in the next days
15:14:46 <witek> dougsz: do you know at which times you will be available?
15:15:26 <dougsz> I think morning MDT will be OK
15:16:04 <witek> thanks
15:16:29 <witek> we will also discuss integration with Vitrage in self-healing session on Thursday
15:17:36 <witek> please add the topics, ideas or feature requests to the etherpad
15:18:11 <witek> I guess, we should skip the IRC meeting next week
15:18:55 <dougsz> 👍
15:19:13 <witek> I will also add the GoToMeeting invitation
15:19:54 <dougsz> thanks witek
15:21:47 <witek> we have couple Monasca sessions in schedule:
15:22:09 <witek> * Scaling should be easy and automatic: Heat and Monasca
15:22:26 <witek> * Monasca - Project Update
15:22:32 <witek> * Monasca - Project Onboarding
15:22:40 <witek> * Policy-Driven Fault Management of NFV Eco System
15:22:51 <witek> * Monitoring and Analyzing your OpenStack Cloud
15:23:07 <witek> * Monasca and 25,000+ Instances in Production - User Story
15:24:11 <witek> anything else for the planning?
15:24:59 <witek> do we want to have dinner together?
15:25:13 <joadavis> Sounds fun
15:25:21 <hosanai> Sounds great
15:26:12 <witek> I'll send a doodle for planning then
15:26:36 <witek> perhaps we could collect some restaurant ideas in etherpad
15:27:51 <hosanai> OK, i will add Blue Moon Brewery :)
15:28:04 <witek> sounds nice :)
15:28:33 <dougsz> Now I am jealous
15:29:31 <witek> #topic Pike extended maintanance
15:30:43 <witek> we have two changes releasing and tagging the repos on Pike branches before entering extended maintenance phase
15:31:16 <witek> unfortunately it seems we haven't releases new versions on Pike for a while now
15:31:32 <witek> and we have syntax errors in Readme files
15:31:32 <joadavis> Is there a brief description of what "extended maintenance" means?
15:32:59 <witek> I think that's full explanation:
15:33:01 <witek> https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html
15:33:23 <joadavis> thanks
15:34:15 <witek> the section "end of life" describes the relevant
15:35:41 <joadavis> Ah, so the branch won't be deleted.  That is good for allowing bug fixes
15:36:00 <witek> anyway, it would be good to fix the syntax errors in Readme files to allow creating `pike-em` tagging
15:36:12 <joadavis> For the README files, do you have a list of which ones?
15:37:36 <joadavis> I see one pending in https://review.opendev.org/#/q/project:%22%255Eopenstack/mon.*%22+branch:stable/pike
15:38:20 <witek> should be possible to extract such list for CI job logs
15:38:22 <witek> http://logs.openstack.org/55/652855/3/check/openstack-tox-validate/5f86565/job-output.txt.gz
15:39:55 <witek> yes, cherry-picking from newer branches will probably be the easiest
15:41:16 <witek> #topic Cross-project liaisons
15:41:36 <witek> the Stein cycle has started
15:42:09 <witek> and I would like to ask if anyone would be interested to take over some of cross-project liaison functions
15:42:38 <witek> the most important Release Management one
15:43:52 <witek> for the First Contact SIG we have Cristiano as the liaison, but he'd be happy to hand it over to someone who works with code
15:44:22 <witek> so please let me know, if you would like to step in
15:45:09 <witek> that's all from me
15:45:22 <witek> do we have anything else for today?
15:46:00 <joadavis> I had a quick question about supporting tools
15:46:18 <joadavis> I wrote a bit of code to fix a rare problem we encountered in Cassandra
15:46:53 <joadavis> It should not happen (but did more than once).  I had a couple options - one is to keep it an an internal tool for our company.
15:47:08 <joadavis> but I also wonder if I should publish it in case someone else in the community hits it
15:47:35 <joadavis> would it be appropriate to create in the monasca-persister repo a tools/ directory and add it there?
15:48:24 <joadavis> Another alternative would be to add it to a monasca wiki somewhere
15:49:04 <witek> what is the tool doing?
15:50:29 <witek> I think wiki is not the right place
15:51:14 <witek> we could add it to the persister repo or somewhere in monasca GitHub organisation
15:51:20 <joadavis> in this case, Cassandra is missing the metric_id and created_at timestamp for some rows (again, should not happen). The tool finds the rows and recreates the metric_id (which is a hash based on other values, so that is possible)
15:52:49 <dougsz> Hmm, I haven't used Cassandra myself, but didn't someone add a patch for multiple data centres + Cassandra the other day, perhaps they may find it useful
15:53:12 <joadavis> If we had other tools I'd look for a space in monasca-common or even a new monasca-tools repo, but this is just a one edge case tool.
15:54:06 <witek> yes, I think a directory in monasca-persister repo is a good place
15:54:36 <joadavis> If monasca-persister/monasca_persister/tools is not an objectionable name, then I'll put up a commit for review
15:55:32 <witek> do you want to deliver it with rpm package?
15:55:33 <joadavis> I have the tool in a 'recreate-metric-id' subdirectory there
15:56:46 <joadavis> I didn't want to complicate our code base with the tool by adding it to the package.  I do hope this is a short-lived tool, as I hope to find a root cause for the missing values and eliminate it.
15:58:20 <witek> I think if you place it in monasca_persister module, it will be included both in PyPI and rpm package
15:58:38 <witek> not sure, if that's intended
15:59:08 <witek> anyway, we can discuss it in review
15:59:30 <joadavis> And i won't be offended if the review is rejected. :)
16:00:11 <witek> time to close the meeting
16:00:20 <witek> see you next week in Denver
16:00:41 <haru5ny> bye, thank you
16:00:43 <koji_n> thx
16:00:45 <witek> #endmeeting