15:01:06 <rhochmuth> #startmeeting monasca
15:01:08 <openstack> Meeting started Wed Jan 11 15:01:06 2017 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:09 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:12 <openstack> The meeting name has been set to 'monasca'
15:01:12 <rhochmuth> o/
15:01:15 <rbak> o/
15:01:20 <hosanai> o/
15:01:23 <rhochmuth> https://etherpad.openstack.org/p/monasca-team-meeting-agenda
15:01:34 <shinya_kwbt> o/
15:01:45 <rhochmuth> hi everyone
15:01:47 <tomasztrebski> o/
15:01:53 <tomasztrebski> yolo ;)
15:01:58 <rhochmuth> i was running a little late
15:02:01 <rhochmuth> but i made it
15:02:04 <witek> hello
15:02:20 <rhochmuth> looks like a few items on the agenda
15:02:22 <rhochmuth> 1.	https://review.openstack.org/#/c/406511/ - See Tomasz's comments and how to proceed ?
15:02:22 <rhochmuth> 2.	https://review.openstack.org/#/c/418598/ - Enable Log Management via specific policy
15:02:22 <rhochmuth> 3.	Postgresql-based CI -> tempests running ;-)
15:02:22 <rhochmuth> 1.	https://review.openstack.org/#/c/356403/
15:02:22 <rhochmuth> 2.	https://review.openstack.org/#/c/418271/
15:02:35 <millerthomasj> o/
15:02:57 <rhochmuth> #topic https://review.openstack.org/#/c/406511/
15:04:13 <bklei> o\
15:04:21 <tomasztrebski> yeah, so this entry is mine but apart from the question to you to read and put your opinion there, nothing in particular that could be added
15:04:37 <rhochmuth> i think i'm ok with merging this change
15:04:43 <rhochmuth> i don't want to hold anyone back
15:04:54 <rhochmuth> and i'm not aware of anyone using the mongo plugin
15:05:09 <tomasztrebski> do you think filling a bug is in order ?
15:05:48 <rhochmuth> sure a bug would be in order
15:05:54 <rhochmuth> it wouldn't hurt
15:06:09 <rhochmuth> and would allow us to track this
15:06:30 <tomasztrebski> ok, so that would be all about that, if Joe is fine about it too, we can merge that
15:06:50 <rhochmuth> i'll add a +1, and let whoever wants to merge it take it from there
15:07:00 <tomasztrebski> kk
15:07:30 <rhochmuth> #topic https://review.openstack.org/#/c/418598/
15:08:24 <rhochmuth> i'm reading the review for the first time
15:08:34 <millerthomasj> I work with rbak and bklei, I need this change to be able to allow access to log management with or without grafana also being enabled
15:09:10 <rhochmuth> who are rbak and bklei
15:09:17 <bklei> :)
15:09:41 <tomasztrebski> millerthomasj: you saw my comment about doing exact same thing for grafana ?
15:10:10 <millerthomasj> yes, the way grafana is enabled already allows us to set a different policy in our policy.json with no issue
15:10:35 <rhochmuth> i'll defer to tomasz and witek
15:10:46 <witek> lgtm
15:11:27 <tomasztrebski> oh...wonder how this works without this one
15:11:42 <tomasztrebski> but since this is possible, i guess lgtm as well
15:12:07 <rhochmuth> does devstack continue to work?
15:12:08 <millerthomasj> my real problem is the default admin_required for us is already set to a role for monasca-admin...i want to create a new role for logs_admin
15:12:29 <millerthomasj> the change i proposed doesn't change the default behavior since it defaults to admin_required
15:12:46 <tomasztrebski> rhochmuth: dont know, did not really had time to install that and see for myself if it works
15:13:16 <rhochmuth> millerthomasj: did you run in devstack?
15:13:48 <millerthomasj> i did not, i ran tests in our development environment here at TWC/Charter
15:14:12 <millerthomasj> i can run the devstack tests also
15:14:23 <rhochmuth> millerthomasj: thanks
15:14:36 <rhochmuth> i don't think the tests will be impacted
15:15:05 <rhochmuth> but, just wondering if devstack comes up with logging/kibana
15:15:21 <rhochmuth> i guess i shoudl say works with kibana still
15:15:26 <tomasztrebski> it does, through monasca-log-api
15:15:32 <tomasztrebski> devstack plugin
15:15:32 <witek> you should enable monasca-log-api plugin and test manually
15:16:02 <tomasztrebski> see here: https://github.com/openstack/monasca-log-api/blob/master/devstack/Vagrantfile#L104
15:16:10 <millerthomasj> will do
15:16:14 <rhochmuth> thx
15:16:27 <witek> thanks
15:16:49 <rhochmuth> after done, then please add a comment to the review and tomasz, witek and i will get merged
15:17:02 <rhochmuth> i think
15:17:06 <tomasztrebski> ]:->
15:17:15 <tomasztrebski> sure thing :)
15:17:29 <rhochmuth> #topic Postgresql-based CI -> tempests running ;-)
15:17:40 <tomasztrebski> yeah, that's from me
15:18:02 <tomasztrebski> I had some surprise when I saw that under postgresql tempest are failing with authorization issues
15:18:06 <tomasztrebski> but work on mysql
15:18:28 <rhochmuth> that is a surprise to me too
15:18:38 <tomasztrebski> luckily enough this change put me on right track: https://review.openstack.org/#/c/409584/
15:18:53 <tomasztrebski> I created a follow up: https://review.openstack.org/#/c/418271
15:19:19 <rhochmuth> so, we need to merge, https://review.openstack.org/#/c/409584/
15:19:30 <rhochmuth> it was merged, never mind
15:19:35 <tomasztrebski> as it turned out there were some other issues with tempest configuration monasca-api plugin has been providing, so after fixing that and putting postgresql on top of that
15:19:43 <tomasztrebski> tempests finally kicked off
15:19:55 <tomasztrebski> they are failling which is not that unexpected I guess
15:20:06 <tomasztrebski> but I think that's a story for another change or changes
15:20:53 <tomasztrebski> btw: sorry for lot of noise in mailbox and all those notifications, tried to remove reviewers until I fixed that but couldn't remove them all
15:21:14 <rhochmuth> so, you would like, https://review.openstack.org/#/c/418271/5, merged
15:21:46 <rhochmuth> then https://review.openstack.org/#/c/356403/
15:22:09 <rhochmuth> is that the sequence
15:22:17 <tomasztrebski> yes, that's the sequence
15:22:32 <tomasztrebski> + the next step, that would be the best
15:22:41 <tomasztrebski> *steps actually
15:23:33 <tomasztrebski> not to mention that python looks fairly good with only 4 failed tests, but java is totally different story
15:23:35 <tomasztrebski> check here: http://logs.openstack.org/03/356403/75/experimental/gate-tempest-dsvm-monasca-java-postgresql-full-ubuntu-xenial-nv/8754d8f/logs/testr_results.html.gz
15:23:38 <rhochmuth> ok, i'm assuming the zuul will come back soon, but i added a +1 to your tempest review
15:24:57 <rhochmuth> so there is either code or test to resolve
15:25:57 <tomasztrebski> ok, but what should we do next, should we move gates from experimantal to just NV (but that would kick those 2 gates for all changes that wouldn't actually fixed that) or should we start fixing that and when we have decent (100%) success rate move to NV or even voting stage ?
15:26:40 <tomasztrebski> and if there would be any help from the community with it ?
15:26:41 <rhochmuth> i would prefer the latter
15:27:26 <rhochmuth> do you think this is a test problem or problm in the postgres code
15:28:05 <tomasztrebski> no idea at this point
15:28:07 <tomasztrebski> sorry
15:29:05 <rhochmuth> is there anymore to discuss on this topic then?
15:29:28 <rhochmuth> just wondering if what i said is ok or if you prefer moving to nv status
15:30:45 <tomasztrebski> I'd certainly like to know Craig's opinion on that topic, not really sure if he's here but he was the one who brought up the idea of CI with Postgres
15:31:32 <rhochmuth> he doesnt' usually attend the weekly meeting
15:31:47 <rhochmuth> but i'll ping him thius morning
15:31:55 <tomasztrebski> naughty...naughty....
15:32:02 <rhochmuth> and get back to you
15:32:08 <tomasztrebski> thx
15:32:28 <tomasztrebski> ok, from my side that's all
15:32:33 <rhochmuth> so, does that cover all the topics from the agenda then
15:33:03 <rhochmuth> #topic misc
15:33:06 <tomasztrebski> any news on storyboard ?
15:33:21 <rhochmuth> storyboard didn't go well
15:33:44 <tomasztrebski> :(
15:34:01 <rhochmuth> steve followed up with the infra team
15:34:27 <rhochmuth> it doesnt' look like it is really ready for prime-time usage by us
15:34:50 <rhochmuth> so, currently we aren't going to use ut
15:35:05 <rhochmuth> steve will submit his bp through the normal process
15:35:16 <rhochmuth> as well as document his plans in the wiki
15:35:30 <rhochmuth> and we'll start working with him on designs/reviews
15:36:56 <rhochmuth> i should point out that there are a lot of reveiws to catch-up on
15:37:21 <rhochmuth> hpe was a bit busy/distracted on other things, but we are going to try and catch-up a bit
15:37:34 <rhochmuth> it would be great if others could do the same
15:37:53 <tomasztrebski> we do try, but at least fo Fujitsu that's the same story :/
15:38:02 <rhochmuth> understand
15:39:05 <rhochmuth> i think that is all i have, but for reviews that we think need to get addressed, we'll update with some comments
15:39:53 <rhochmuth> unless anyone has anything else, then i guess i'll close the meeting
15:40:12 <tomasztrebski> there is one thing, that was actually the question to monasca coming from this change that I think is worth putting here: https://review.openstack.org/#/c/418308/
15:40:39 <tomasztrebski> comment from Tony
15:40:59 <rhochmuth> thatnks for point out
15:41:17 <diablo_rojo_phon> hey rhochmuth you mentioned storyboard? If it has all the things Monasca needs you can definitely migrate there.
15:41:27 <witek> any news about kafka-python?
15:42:01 <rhochmuth> diablo_rojo_phon: interesting
15:42:17 <diablo_rojo_phon> rhochmuth: or if there are things missing I'd love to hear what they are so I can help get them implemented :)
15:42:23 <rhochmuth> the impression we got was that migration might be difficult
15:42:57 <rhochmuth> here is the summary that i got
15:42:59 <rhochmuth> - They don't want to duplicate projects across trackers, so Monasca would have to migrate away from Launchpad
15:42:59 <rhochmuth> - There are scripts to migrate existing issues, but they may have, quote, "be a little bitrotted"
15:43:00 <rhochmuth> - Requires change to the project Puppet config, #openstack-infra is the place to ask for more details
15:43:00 <rhochmuth> - For issues shared with other projects, those projects are required to migrate to Storyboard at same time
15:43:03 <diablo_rojo_phon> rhochmuth: For some projects dependent on others yes, but not for everyone.
15:43:46 <diablo_rojo_phon> Right, your last point is what is stopping most projects at this point I believe.
15:44:00 <rhochmuth> i see
15:44:16 <diablo_rojo_phon> The scripts to migrate might be a little out of date, but it shouldn't be that hard to get them up to snuff :)
15:44:29 <rhochmuth> although, i don't think we have many issues shared with other projects
15:44:31 <fungi> the bitrot in the migration scripts is just because nobody has requested a migration in a while. that's certainly solvable
15:44:47 <diablo_rojo_phon> Thanks fungi :)
15:44:55 <rhochmuth> thx fungi
15:45:16 <rhochmuth> so, what do you suggest then
15:45:20 <fungi> it's just that storyboard's featureset and data model have changed slightly since the last time we migrated anything, so we'd want to do some tests on storyboard-dev to make sure importing still works
15:46:12 <fungi> and if monasca wants to migrate from lp to sb, we can up the priority on whipping the migration script back into shape (or it may turn out to still work just fine)
15:46:21 <diablo_rojo_phon> I can talk to Zara about getting that on the agenda today for the stoeyboard meeting and circle back around to you rhochmuth about getting Monasca moved.
15:46:32 <diablo_rojo_phon> *storyboard
15:46:46 <rhochmuth> it sounds good to me
15:46:52 <diablo_rojo_phon> Sweet :)
15:47:06 <rhochmuth> i think we had a little of the deer in the headlights syndrome
15:47:28 <rhochmuth> but, if you are willing to go through that work for us, then i think we are game
15:47:29 <diablo_rojo_phon> rhochmuth: you're not the only ones so no worries
15:47:34 <rhochmuth> witek tomasz ???
15:47:38 <tomasztrebski> +1
15:47:40 <tomasztrebski> :P
15:47:45 <diablo_rojo_phon> Excellent
15:47:48 <rhochmuth> bklei?
15:48:07 <bklei> sorry -- got distracted, reading back
15:48:33 <rhochmuth> looks like we might be able to migrate to storyboard after all
15:48:43 <bklei> i'm in full support of that!
15:48:49 <rhochmuth> thx
15:48:52 <witek> me too
15:48:58 <rhochmuth> i think we've got a quorum then
15:49:17 <tomasztrebski> witek: what about kafka-python ?
15:49:23 <rhochmuth> diablo_rojo_phon: thx, looks like we are reay to migrate
15:49:45 <rhochmuth> if you and fungi can help
15:49:54 <rhochmuth> everyone want to move
15:49:56 <diablo_rojo_phon> rhochmuth: Cool, if you wanna join the storyboard meeting I can send you the info, otherwise Ill ping you after.
15:50:11 <rhochmuth> is that meeting tomorrow?
15:50:12 <witek> oslo.messaging wants to uncap the version which is problematic for us
15:51:08 <tomasztrebski> aaah, that would move the client version to the one which supports newer kafka what they likely need
15:51:17 <tomasztrebski> ?
15:51:41 <fungi> rhochmuth: today at 19:00 utc in #openstack-meeting
15:52:12 <fungi> #link http://eavesdrop.openstack.org/#StoryBoard_Meeting
15:52:46 <rhochmuth> thx fungi, i'll try and make it, but might have a conflict today
15:52:48 <rhochmuth> will try
15:53:26 <tomasztrebski> witek: if they do this, we will have to update the devstack to roll on with newer kafka and all that
15:53:38 <rhochmuth> so, the last i talked to joe keen, he still had concerns
15:53:45 <rhochmuth> with the newer kafka client
15:53:54 <tomasztrebski> + they will several changes from requirements bot
15:54:12 <tomasztrebski> *will be
15:54:21 <rhochmuth> the simple consumer/producer that we use is "deprecated" in that library
15:54:48 <tomasztrebski> well both monasca-api and monasca-log-api would be affected
15:55:01 <rhochmuth> and we can't use the async, unless we change our code
15:55:16 <tomasztrebski> not really sure if monasca-notification and monasca-persister uses monasca-common and in result kafka-python
15:55:22 <rhochmuth> and it is more than just a trivial change if we want to have guaranteed message delivery
15:55:42 <rhochmuth> however, we were also very interested in the confluent library and moving to that
15:55:50 <rhochmuth> which also is only async
15:56:09 <tomasztrebski> yeah, about that...I could find any free time to continue checking on it...
15:56:22 <tomasztrebski> got some code saved somewhere and that's it
15:56:54 <rhochmuth> so, my preference was to switch to the confluent library
15:57:01 <rhochmuth> then that woiuld remove the dependency
15:57:12 <rhochmuth> but in the short-term, i don't have any great ideas
15:57:43 <rhochmuth> moving to a deprecated part of a library by bumping to the latest version in the library seems somewhat risky too
15:57:55 <rhochmuth> although that would free up oslo for making progress
15:58:04 <rhochmuth> on the library that they want to use
15:58:24 <rhochmuth> i'll have to check-in with joe again
15:58:44 <tomasztrebski> in the end, if they would manage to put their functionality into kafka, that would be beneficial for all
15:59:02 <rhochmuth> not sure i understand that
15:59:07 <rhochmuth> statement
15:59:11 <tomasztrebski> maybe not directly to us, I mean
15:59:39 <rhochmuth> i'll check in with joe
15:59:47 <witek> rhochmuth: thanks
15:59:49 <rhochmuth> and will try and attend storyboard later
15:59:57 <rhochmuth> have to close meeting down now
16:00:00 <rhochmuth> thanks everyone
16:00:26 <tomasztrebski> vye
16:00:29 <rhochmuth> #endmeeting