18:00:47 #startmeeting Trove 18:00:48 Meeting started Wed Feb 8 18:00:47 2017 UTC and is due to finish in 60 minutes. The chair is johnma. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:49 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:51 The meeting name has been set to 'trove' 18:01:07 o/ 18:02:18 hello songjian 18:02:47 hello johnma 18:03:19 o/ 18:03:30 Hi trevormc 18:03:47 will wait for an additional minute or so 18:04:31 amrith if travelling this week and next 18:05:02 o/ 18:05:16 hi peterstac, how are you 18:05:28 hi johnma, I'm good - yourself? 18:05:52 doing good peterstac - the same old 18:06:01 yep :) 18:06:35 alright, I guess we can get started. 18:07:28 #info amrith cut rc-1 last Sunday and it looks like it failed due to some issues with the trovestack work 18:08:40 but that was sorted and changes merged on master and stable/ocata but it looks like the proposal bot changes need to get merged: https://review.openstack.org/#/c/429419/1 18:08:57 anyways we now have a stable/ocata branch and master is open for Pike 18:09:23 apart from that I don't have any other announcements. 18:09:35 I will open this up for any open discussions 18:10:15 does anyone have any changesets that needs review 18:10:16 I did a little bit of digging into bugs this morning and thought of two I wanted to bring up 18:10:48 peterstac: I will test the module-reapply patch today and review it. I just havent gotten a chance to test it 18:10:55 ok, thx 18:10:59 sure trevormc 18:11:25 #link https://bugs.launchpad.net/trove/+bug/1656317 18:11:25 Launchpad bug 1656317 in OpenStack DBaaS (Trove) "Remove XML support for Trove API" [Undecided,Confirmed] - Assigned to Shaik Apsar (sa709c) 18:11:43 I'm not sure if we need the application/xml as the default for our api requests but I thought we aren't allowed that anymore based on this link 18:11:56 #link https://review.openstack.org/#/c/68333/ 18:13:33 https://github.com/openstack/trove/blob/master/trove/common/base_wsgi.py#L295 is what I'm referring to, do we use that for something else? 18:14:22 and the bug you mentioned above is to reinstate xml support? 18:14:40 no the opposite, Remove XML support 18:17:52 I know our trove/integration directory has xml files and that may be why we use it. I just wasn't sure. 18:18:20 maybe push up a test changereq and see what the gate says? 18:18:25 yeah ok 18:18:44 so I have another bug I wanted to raise 18:18:47 it might work, but it also might require more changes ;) 18:18:59 :( 18:19:05 oh ok. I am not sure if that is used anywhere else. You could go ahead and put out a patchset for review 18:19:16 #link https://bugs.launchpad.net/trove/+bug/1578666 18:19:16 Launchpad bug 1578666 in OpenStack DBaaS (Trove) "Strong password policies enforced in Mysql will break replication" [Undecided,New] - Assigned to Simon Chang (changsimon) 18:19:59 After installing the plugin here and using it I faced in error from mysql for weak passwords. I don't think this error is propagated to the user 18:20:57 I tried running a trove create and I ran into errors but I was just wondering if anyone else has experience with this plugin 18:21:20 Here is the error that I received from mysql 18:21:23 #link http://paste.openstack.org/show/598126 18:22:03 what plugin trevormc? 18:22:12 #link https://dev.mysql.com/doc/refman/5.6/en/validate-password-plugin-installation.html 18:22:17 I know Simon did some work in that regards (adding a mechanism so that the default passwords would be 'strong') 18:22:39 I thought that got pushed US, but maybe it's still on the queue :( 18:22:50 yeah I didn't see any changes from Simon 18:23:18 I'll check with him next time I see him :) 18:23:34 it doesn't look like a change from simon was pushed upstream 18:23:50 thanks, that is all for bugs. Although I have another topic I wanted to bring up. 18:24:03 sure, go ahead 18:24:49 Has anyone here ran a fortify scan on trove? It shows security issues, a lot of which are false positivies. I just wanted to hear thoughts on pursuing changes related to those 18:25:38 I haven't tried that. what kind of security issues? 18:25:44 One in particular is logging passwords in the debug log and try catch pass cases 18:25:52 we have support for running bandit 18:26:06 not sure how that compares to fortify 18:26:19 but it also reveals a bunch of false-positives :) 18:26:47 yeah bandit and fortify have some overlap, I just want to say I have a report handy. I'm going to be pursuing some changes where possible. 18:28:09 that sounds fine trevormc. 18:28:14 I'd be interested in looking at bandit too, where is that supported? 18:28:48 I haven't used bandit personally, I've only heard about the overlap by word of mouth 18:28:50 I believe you can run it through tox 18:29:01 oh nice 18:29:24 'tox bandit' 18:29:36 ok thats all I had. Thanks for the info, and I'd like to follow up on the mysql password validation plugin 18:29:57 expect a patch soon for the xml stuff too, I'm not sure if Shaik wants to do that or not. 18:31:16 sounds good trevormc 18:31:32 thanks. anything else? 18:31:44 Just about the Redis stuff 18:31:57 you have a link handy peterstac 18:32:15 #link https://review.openstack.org/#/c/416361/ 18:32:22 The Redis stuff is breaking because version 3.2.6 has new config options that we need to deal with 18:32:44 the above changereq switches to using a compiled redis 18:33:15 but even if we stay with the PPA, it's now pulling down 3.2.6 be default so we'd have to make the code changes at least 18:33:42 aah ok. let me do this today as well. 18:33:46 (and to have Newton pass, it'd probably need to be backported) 18:35:12 trevormc: I will on Remove XML support for Trove API 18:35:27 Hi ShaikApsar, thanks for the update 18:39:42 that's all I had :) 18:40:58 so when we create trove cluster what version should we use? I've only used 3.0 :( 18:41:09 for redis 18:42:24 I am so sorry. I got disconnected from my IRC client 18:42:40 ahh I see it's 3.2.6, I should look at the patch first :) 18:43:30 hi mariamjohn, it was quiet for the most part 18:43:51 ok, so #action for me 18:43:56 the other choice would be to pin the version to 3.0.7 18:44:06 #action 1: review redis patchset 18:44:20 might be a quicker solution (and easier to backport) 18:44:46 #action 2: look to backport this to stable/newton and stable/ocata, right peterstac 18:46:27 #action 3: review module-reapply patchset 18:47:21 anything else peterstac, trevormc,songjian 18:47:33 nothing here 18:47:47 nothing 18:47:53 nothing too much. Thanks mariamjohn 18:48:46 awesome. thank you for joining today's meeting. I will try to get these done today and in case anything else comes up, feel free to ping me on IRC 18:49:05 \o 18:49:17 have a great rest of the day. 18:50:04 I dont think I can end this meeting from a different client 18:50:19 #endmeeting 18:50:34 yeah nothing happened :) 18:50:59 maybe change your nick to johnma? 18:51:15 idk how it works 18:51:25 tried it 18:51:39 restarting my other laptop 18:54:28 #endmeeting