15:00:43 <witek> #startmeeting monasca
15:00:44 <openstack> Meeting started Wed Apr 18 15:00:43 2018 UTC and is due to finish in 60 minutes.  The chair is witek. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:45 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:48 <openstack> The meeting name has been set to 'monasca'
15:01:05 <witek> Hello everyone!
15:01:06 <amofakhar> Hello
15:01:08 <jgrassler> Hello
15:01:09 <Dobroslaw> Hi
15:01:11 <cbellucci> hello
15:01:11 <haruki> hello
15:01:11 <koji> hi
15:01:36 <witek> agenda for today: https://etherpad.openstack.org/p/monasca-team-meeting-agenda
15:01:46 <witek> with larger font ;)
15:02:08 <amofakhar> yeah looks better
15:02:26 <witek> yes, we're not that young anymore ;P
15:02:45 <amofakhar> :)
15:02:51 <witek> #topic building Docker images
15:03:26 <witek> there were some discussions about the spec last week
15:03:37 <witek> https://review.openstack.org/538937
15:04:06 <witek> one point which I would like to discuss is the Python version
15:04:15 <Dobroslaw> Yep, in comments to spec I got some questions about building images with Python 2 or Python 3
15:04:43 <Dobroslaw> The problems for now: not all Monasca parts works with Python 3
15:05:28 <witek> monasca-api and monasca-agent being worked on though
15:05:31 <amofakhar> But there is a plan to update all to work with python 3
15:05:37 <Dobroslaw> Also OpenStack Python version is 3.5 but official for this one are built on old Alpine 3.4
15:05:51 <Dobroslaw> Newer Python 3.6 is build with Alpine 3.7
15:06:19 <Dobroslaw> Yes, what would be best approach here?
15:06:49 <Dobroslaw> Using only Python 3 and wait for rest of the services to be updated to works with it?
15:07:17 <Dobroslaw> Or build all services supporting py3 with py3 and rest build with py2?
15:08:09 <Dobroslaw> Build all services with py2 and py3 (so two containers per service, highest maintenance cost)?
15:08:10 <amofakhar> I say, Py3 and wait
15:08:24 <witek> does anyone explicitly need python 2 images?
15:08:48 <Dobroslaw> That's also my preference
15:09:51 <witek> Dobroslaw: currently Alpine 3.6 is used in monasca-docker
15:10:01 <witek> which Python version is it?
15:10:10 <Dobroslaw> 2.7.14
15:10:44 <Dobroslaw> official py2 images have also Alpine 3.7 versions
15:11:14 <Dobroslaw> Looks like they stopped building Python 3.5 with newer Alpine
15:12:41 <witek> my preference would also be to decide for one version only
15:13:05 <witek> and I hope the porting work will be finished soon
15:13:13 <witek> I mean Python porting
15:14:12 <Dobroslaw> Yes, that would give us least amount of maintenance
15:14:32 <witek> so, if nobody has objections, I would propose to build only Python3 images as part of this effort
15:14:45 <amofakhar> +1
15:15:23 <Dobroslaw> +1
15:15:27 <witek> anything else to discuss about this spec?
15:15:38 <Dobroslaw> Python 3.5 or 3.6?
15:16:52 <amofakhar> I read that some packages break in 3.6
15:17:02 <Dobroslaw> Hmmm, would be bad
15:17:03 <amofakhar> and it needs to install them from github
15:17:51 <witek> most OpenStack CI jobs run with 3.5
15:18:08 <amofakhar> yes its recommended to use 3.5
15:19:22 <Dobroslaw> Anyone else have comments about this?
15:19:49 <Dobroslaw> If not I think safest way will be starting with Python 3.5
15:20:07 <amofakhar> Agree
15:20:13 <witek> fine
15:20:15 <Dobroslaw> And when they are working then we could try changing to 3.6 and test stability
15:20:33 <Dobroslaw> OK
15:21:03 <witek> anything else?
15:21:12 <Dobroslaw> not for now
15:21:16 <Dobroslaw> thank you
15:21:22 <witek> thanks for the comments in review
15:21:34 <witek> #topic reviews
15:21:43 <witek> https://review.openstack.org/#/c/546956/8
15:22:03 <amofakhar> I pushed a new commit
15:22:21 <witek> that's for oslo.policy implemetation
15:22:21 <amofakhar> so please review again
15:22:26 <amofakhar> yes
15:22:42 <witek> thanks for the code
15:22:50 <amofakhar> np
15:23:07 <amofakhar> nothing more
15:23:20 <witek> have you changed anything else apart from configuration?
15:23:57 <amofakhar> no just security.py is came back and its used for policy
15:24:29 <witek> thanks, so backwards compatibility should be remained
15:24:37 <amofakhar> yes
15:25:10 <witek> any other reviews which need attention?
15:25:46 <amofakhar> https://review.openstack.org/#/c/560334/
15:26:31 <amofakhar> pep8 for monasca-ui
15:27:19 <Dobroslaw> Looks good to me and it was working previously in devstack
15:28:07 <amofakhar> Dobroslaw: you had a comment and its done now
15:28:21 <witek> just +2'd
15:28:27 <amofakhar> thanks
15:28:35 <Dobroslaw> Ugh, I don't have password to Ubuntu One at home... If no one merge it today I'll do it tomorrow
15:28:51 <Dobroslaw> yes, thank you
15:28:59 <witek> we've got the problem with the new requirements-check job in monasca-notification
15:29:16 <witek> because jira library is not in global-requirements
15:29:25 <witek> I've proposed adding it
15:29:36 <witek> https://review.openstack.org/562151
15:29:56 <witek> till now looks good :)
15:30:43 <witek> other reviews?
15:30:59 <aagate> https://review.openstack.org/#/c/557844/
15:31:25 <aagate> monasca-transform docs update is ready for review
15:31:35 <witek> great, thanks for that
15:32:18 <amofakhar> what is the problem with monasca-log-api tempest ?
15:32:18 <aagate> also https://review.openstack.org/#/c/561371/ (update to devstack plugin for monasca-transform)
15:33:09 <witek> tempest tests should actually be moved to the new repo
15:33:31 <witek> but if you prefer to fix them first, it's fine
15:34:21 <witek> amofakhar: I'm not sure, it seems to be random
15:35:48 <witek> feel free to look up our progress board
15:35:51 <witek> https://storyboard.openstack.org/#!/board/60
15:36:03 <witek> and add or update the tasks
15:36:57 <witek> we had some progress on Python 3 changes last week
15:37:29 <witek> #topic dates
15:37:36 <haruki> > Topic Jira: sorry for late, concerning about Jira requirement, I''ll check your patch because I have experience to test Jira notification
15:38:07 <witek> the change is for the requirements repository
15:38:22 <witek> adding jira to global requirements
15:38:57 <witek> what could be tested are min, max supported versions
15:40:11 <witek> Rocky-1 milestone: April 19
15:40:16 <witek> that's tomorrow
15:40:28 <witek> I'll tag all the repos
15:41:11 <witek> from other news I got update from Stefano that he got approval for Vancouver
15:41:20 <Dobroslaw> great
15:41:45 <witek> yes, that's fantastic
15:42:10 <amofakhar> good news
15:42:43 <witek> OK, if there are no other topics, I'll be wrapping up
15:43:13 <jgrassler> Just a small update on https://storyboard.openstack.org/#!/story/2001654
15:43:38 <witek> go ahead
15:44:00 <jgrassler> I added a few tasks now and I'll probably submit a first draft review for 14339 (migrations for all MySQL script revisions) this week
15:44:11 <witek> great
15:44:19 <amofakhar> great
15:44:29 <jgrassler> I'm almost done aligning the first SQL script revision with its corresponding migration...
15:44:30 <witek> I'll update the board
15:44:34 <jgrassler> 4/19 tables left :-)
15:44:49 <jgrassler> Doesn't that happen automatically once I submit the review?
15:45:08 <jgrassler> Also, here's a sneak preview: https://github.com/jgrassler/monasca-api/tree/alembic
15:45:24 <joadavis> The story will be updated automatically, but the kanban style board needs some manual motion
15:45:28 <jgrassler> (plenty of rough edges left, but you can see where it's going)
15:45:28 <witek> the tasks have to be added to the worklist first
15:45:43 <jgrassler> Ah, ok
15:45:44 <witek> and than the card can be moved along
15:46:01 <witek> the task status gets updated automagically
15:46:59 <haruki> For Pockey, if there is guys who would like to translate monasca-ui in your language (excluding English), I recommend to add patch in Zanata, for Rockey.
15:48:07 <haruki> For Rocky, sorry...
15:48:55 <witek> jgrassler: what's the path to alembic code in monasca-api?
15:49:27 <witek> haruki: I've seen some German translations
15:50:13 <jgrassler> witek: it's in monasca_api/db/
15:50:45 <witek> thanks
15:51:07 <koji> let me ask a small question about https://review.openstack.org/#/c/560334/
15:51:22 <koji> why did it change the max line length?
15:51:50 <witek> we agreed to be pep8 conform
15:52:00 <amofakhar> because we agreed on it
15:52:01 <witek> and use 100 chars max line length
15:52:31 <koji> thanks, so discussed previous meeting
15:53:09 <witek> yes, I guess before Easter
15:53:48 <koji> i got it
15:54:08 <witek> OK, thank you everyone for joining today
15:54:18 <amofakhar> Thank you too
15:54:19 <witek> and see you next week
15:54:25 <amofakhar> good bye
15:54:26 <Dobroslaw> Thank you
15:54:28 <witek> bye
15:54:29 <haruki> thanks, too. see you
15:54:30 <koji> thanks
15:54:31 <Dobroslaw> bye
15:54:37 <aagate> Thank you bye
15:54:50 <witek> #endmeeting