18:00:38 <amrith> #startmeeting trove
18:00:39 <openstack> Meeting started Wed Mar  2 18:00:38 2016 UTC and is due to finish in 60 minutes.  The chair is amrith. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:40 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:00:43 <openstack> The meeting name has been set to 'trove'
18:00:54 <atomic77> o
18:01:02 <amrith> ./
18:01:12 <amrith> lets give folks a couple of minutes to trickle in
18:01:19 <johnma> Hello
18:01:21 <mvandijk> ./
18:01:23 <tosky> hi
18:03:42 <amrith> hi atomic77 johnma mvandijk tosky
18:04:09 <dougshelley66> o/
18:04:10 <tellesnobrega> o/
18:04:14 <schang> o/
18:04:28 <amrith> hello dougshelley66 tellesnobrega schang
18:05:04 <amrith> let's get going ...
18:05:22 <amrith> #topic Trove pulse update
18:05:33 <amrith> #link      http://bit.ly/1VQyg00
18:05:46 <amrith> thanks to dougshelley66 for getting this updated
18:05:59 <dougshelley66> np, i'm an excel hack from way back
18:06:11 <amrith> we've seen a couple fewer reviews but also not many new patches as we head towards m-3
18:06:26 <amrith> on the whole, we have a number of features that we should be trying to get merged in the next couple of days
18:06:35 <amrith> so let's see if we can hit that target.
18:06:44 <amrith> otherwise, not much unexpected on this list
18:07:00 <vgnbkr> o/
18:07:13 <pmackinn> o/
18:07:21 <amrith> any other thoughts on the review in the past couple of weeks, we didn't have an updated sheet last week.
18:07:24 <amrith> hi vgnbkr pmackinn
18:07:46 <amrith> #topic Announcements
18:08:15 <amrith> #link http://releases.openstack.org/mitaka/schedule.html
18:08:19 <amrith> I should really update the agenda
18:08:24 <amrith> I keep getting the wrong link
18:09:15 <amrith> we are almost at R-5
18:09:19 <amrith> the Mitaka-3 milestone
18:09:26 <amrith> this is the feature freeze date
18:09:42 <amrith> all client libraries are to be frozen by March 4th
18:10:16 <amrith> Looking at our current list of reviews
18:10:23 <amrith> I see some that are for features
18:10:30 <amrith> and some that are for libraries that we need to get merged
18:11:11 <dougshelley66> yes
18:11:17 <amrith> Does anyone have a merge for trove client that MUST get merged for Mitaka?
18:11:30 <amrith> peterstac, what about https://review.openstack.org/283283
18:11:59 <amrith> that's the only client change that I can see a question about
18:12:14 <amrith> we have several features that we need to get reviewed
18:12:22 <amrith> CouchDB B&$
18:12:26 <amrith> B&R
18:12:32 <amrith> CouchDB Configuration Groups
18:12:35 <amrith> MariaDB Clustering
18:12:39 <amrith> DB2 B&R
18:12:51 <dougshelley66> Cassandra clustering
18:13:00 <dougshelley66> there are 2 vertica featuers
18:13:25 <johnma> do these features need to be merged by the 4th as well?
18:13:37 <amrith> that is the preferred route
18:13:47 <dougshelley66> otherwise we need feature freeze exceptions
18:13:50 <dougshelley66> for each
18:13:51 <amrith> for those that are not merged by 4th, I need to send out requests for FFE
18:13:56 <amrith> one for each FFE
18:14:05 <amrith> so, that's one of the later items on the agenda
18:14:09 <amrith> bt we may as well get there
18:14:17 <amrith> what is the list of things that we'll need FFE's for.
18:14:17 <johnma> ok, sounds good.
18:14:49 <amrith> I don't know what the formal process is but in years past, SlickNik or hub_cap would have sent out the FFE email.
18:15:03 <amrith> So, I'll work with cp16net and make sure that the email goes out
18:15:13 <amrith> but the current situation is that we will need FFE's for all of these.
18:15:19 <dougshelley66> any chance we can get some of them merged to cut down the red-tape?
18:15:25 <amrith> dougshelley66, did module stuff from peterstac get merged?
18:15:33 <amrith> Yes, I would like to get them done before 4th
18:15:44 <dougshelley66> amrith just one of the client pieces
18:15:45 <amrith> could everyone please focus review effort on these chnanges.
18:15:50 <johnma> So Amrith, I did one last year and the person working on the feature needs to request for FFE
18:16:02 <amrith> ok johnma thanks
18:16:26 <amrith> so johnma ... We need a review for 284526
18:16:32 <amrith> https://review.openstack.org/284526
18:16:32 <atomic77> The two pgsql features as well
18:16:36 <peterstac> amrith, no, the module client stuff hasn't merged yet
18:16:41 <amrith> it is the client side of the module management stuff
18:16:46 <amrith> the server side has merged
18:16:52 <amrith> and it would be good to get this merged
18:17:07 <amrith> sorry
18:17:10 <amrith> other way around
18:17:13 <amrith> this is the server side
18:17:15 <dougshelley66> peterstac one of the module mgmt client patches merged, right?
18:17:15 <amrith> the client merged.
18:17:27 <peterstac> amrith, sorry, that's correct, but there is another part that's still forthcoming
18:17:32 <amrith> yes, one of the module management patches merged.
18:17:43 <amrith> peterstac, please get it up for review
18:17:46 <peterstac> (by correct I mean that the troveclient stuff has merged)
18:17:53 <amrith> it'll be hard to make the case for an FFE when the patch isn't in review.
18:18:02 <peterstac> amrith, yes, I'm hoping to have that today or early tomorrow
18:18:18 <amrith> johnma, will you take care of requesting FFE's for your DB2 and CouchDB changes?
18:18:25 <johnma> ok Amrith, I will look into these. So atomic77 can you send me the links for the ones you want reviewed as well
18:18:47 <johnma> for CouchDB Backup & restore, I put out another patch to fix the user backup. So both user and db backup's work now. just need some reviews. I added a new couchdb library for the integration tests and had to add that to the global-requirements. That's why Jenkins is showing -1. I have a +2 on that from dims but waiting for it to be approved.
18:19:08 <johnma> for the remaining ones on our side that needs FFE, I will handle that
18:19:49 <atomic77> amrith https://review.openstack.org/#/c/259167/  - pgsql inc B&R
18:19:56 <johnma> I am hoping the Couchdb backup restore should go in without much problem before the FF date. I will see if I can get the requirements change approved
18:20:18 <amrith> thanks johnma
18:20:43 <atomic77> but it's stuck in a merge conflict that i haven't been able to figure out (due to the in-flight dependencies i had to commit on top of)
18:20:55 <amrith> in terms of priority, cassandra, mariaDB and vertica may be ahead of the list than the pgsql
18:21:03 <amrith> given that pgsql is in merge conflict.
18:21:31 <amrith> so, let's try and get cassandra, mariaDB and vertica merged and get FFE's for the minimal stuff (pgsql)
18:22:00 <amrith> and peterstac will push up the last of the module management changes
18:22:07 <amrith> which we can try to merge or FFE if not.
18:22:12 <amrith> does that sound like a plan?
18:22:22 <dougshelley66> sounds good
18:22:26 <vgnbkr> MariaDB Clustering is patiently waiting for a second +2...
18:22:36 <amrith> vgnbkr, I know ...
18:22:46 <johnma> will look at it vgnbkr
18:23:00 <amrith> anyone else have features that must go in before FFE?
18:23:20 <amrith> I think I've gone through the list.
18:23:32 <amrith> but would like to make sure I haven't missed something
18:23:54 <peterstac> vgnbkr, johnma: I've tested the MariaDB cluster stuff (worked fine) - just haven't had the time to check the code ...
18:24:16 <johnma> thats great peterstac, i will go through the code
18:24:33 <amrith> ok, that's all we have on that subject.
18:24:36 <johnma> I have been having trouble with my env building images, so if testing is good, I can look at the code
18:24:57 <amrith> johnma, we can catch up on #openstack-trove on the issue with images
18:25:05 <amrith> I had some email exchanges with someone on the ML
18:25:06 <johnma> sure
18:25:12 <amrith> and will be updating the doc on making images
18:25:22 <amrith> that talks about setting a bunch of env variables
18:25:31 <amrith> but doesn't tell you what to set them to
18:25:56 <amrith> anyway, on the subject of FFE, mitaka-3 deadline, ... anything else?
18:25:58 <amrith> going once
18:26:02 <johnma> sound good, thanks Amrith
18:26:14 <amrith> going once more
18:26:48 <amrith> #topic Health check on outstanding blueprints and features for Mitaka
18:26:57 <amrith> #link  https://launchpad.net/trove/+milestone/mitaka-3
18:27:18 <amrith> dougshelley66, and I updated many of the bp's yesterday so they should reflect the current status of the various projects.
18:27:38 <amrith> if you look below, there is also a list of bugs that are targeted for m-3
18:27:48 <amrith> if you have a bug assigned to you, please take a look at it
18:27:57 <amrith> if you can get it fixed, that's ideal
18:28:01 <amrith> if not, we still have time
18:28:03 <dougshelley66> amrith we can fix bugs after FF, right?
18:28:10 <amrith> M-3 is NOT the deadline for bug fixes
18:28:15 <dougshelley66> right
18:28:19 <amrith> bug fixes can be committeed all the way through
18:28:29 <amrith> but these bugs were targeted at M-3 earlier
18:28:46 <amrith> But, we don't have a lot more time
18:28:47 <amrith> like 10 days
18:28:56 <amrith> in theory, you should have all bugs done by RC1 date.
18:29:09 <amrith> in practice, sometime before April 4 (R0)
18:29:19 <amrith> so something between 10 and 28 days.
18:29:54 <amrith> That's all I have on that topic. anyone have anything else on it ...
18:30:13 <amrith> #topic Open Discussion
18:30:26 <amrith> anybody have any other topics or subjects they'd like to discuss.
18:30:47 * pmackinn stumps for https://review.openstack.org/#/c/284162/2 it's fedora...what could go wrong?
18:30:56 <atomic77> amrith sorry can i just get clarification - when you say pgsql minimal stuff
18:31:14 <atomic77> you don't mean the features i listed right - we're going to push those to n-release?
18:31:24 <johnma> once the FFE sets in, when is the next deadline to get the features in (assuming they are accepted for FFE)
18:31:36 <amrith> atomic77, I was meaning that we should try and get as many things as possible merged before the deadline
18:31:41 <peterstac> pmackinn, I'll take a look
18:31:43 <amrith> and ask for FFE's for as few things as possible
18:31:50 <amrith> "minimal stuff" was not very clear.
18:31:53 <pmackinn> peterstac, you're a prince
18:32:02 <amrith> I meant "as few FFE's as possible, get them merged before deadline"
18:32:18 <amrith> pmackinn, I will take a look
18:32:34 <pmackinn> amrith, ty
18:32:37 <amrith> So I can test this, may I have a fedora (that is a RedHat, right?)
18:32:57 * pmackinn facepalms
18:33:04 <pmackinn> o/ SlickNik
18:33:39 <amrith> other topics for open discussion
18:33:57 <SlickNik> o/ sorry arriving late
18:34:36 * amrith mumbles ... all it takes is pmackinn to say SlickNik and he shows up, what about the times I said SlickNik?
18:34:50 <amrith> hi SlickNik
18:34:54 <vgnbkr> You have to say it 3 times.
18:35:09 <SlickNik> hi hi
18:35:12 * amrith rubs the lamp and says SlickNik three times
18:35:29 <pmackinn> FFE discussion earlier SlickNik
18:35:40 <amrith> other subjects for Open Discussion
18:35:50 <amrith> well, since SlickNik is here, ...
18:36:05 * SlickNik reads scrollback
18:37:23 <pmackinn> amrith, how do you characterize m-3 bugs? High *must* go in?
18:37:45 <amrith> pmackinn, I didn't mark those
18:37:47 <SlickNik> So the process that teams have followed in the past has been that the person who's requesting the FFE sends a mail out to the -dev mailing list.
18:38:10 <amrith> It is a combination of some that I felt should go in, and maybe some triaging that SlickNik and cp16net did
18:38:47 <pmackinn> amrith, ack, was wondering generally how those are interpreted
18:38:52 <amrith> FYI all, I believe that our current list of reviews for m-3 is https://review.openstack.org/#/q/is:watched+is:open+starredby:amrith
18:38:54 <SlickNik> And then the PTL (after discussion with the release team) can grant FFEs as appropriate.
18:39:21 <amrith> thanks SlickNik, johnma indicated that she had sent email in a previous cycle.
18:40:03 <amrith> and to that list, add the change set that peterstac will submit
18:40:10 <amrith> that's all I had for the meeting
18:40:15 <johnma> thats a pretty clean list amrith :).
18:40:23 <amrith> unless someone else has something else to add, I think we can call this a wrap
18:40:29 <SlickNik> amrith ++ to that list
18:40:47 <amrith> and if you find something missing on the list, please let me know and I'll star it
18:41:03 <johnma> that list is empty
18:41:38 <amrith> johnma, do you mean that the URL I sent is empty?
18:41:45 <pmackinn> indeed
18:41:49 <amrith> huh
18:41:53 <johnma> yes,
18:42:08 <amrith> how about this
18:42:08 <amrith> https://review.openstack.org/#/q/starredby:amrith
18:42:24 <SlickNik> johnma: you may need to sign in
18:42:31 <johnma> very realistic now :)
18:42:34 <amrith> oh, yes
18:42:40 <amrith> have to login
18:42:59 <johnma> works now
18:43:22 <amrith> ok, going once ...
18:43:28 <dougshelley66> amrith there are 3 other patch sets for module mgmt
18:43:29 <dougshelley66> in review
18:43:36 <amrith> dougshelley66, what are they?
18:43:39 <dougshelley66> or it might be 2
18:43:41 <dougshelley66> one sec
18:43:58 <dougshelley66> https://review.openstack.org/284526
18:44:05 <amrith> added that just now
18:44:37 <dougshelley66> sorry it is just one ATM
18:44:38 <peterstac> amrith, you were asking earlier about https://review.openstack.org/#/c/283283/
18:44:59 <amrith> is that m-3 as well peterstac
18:45:02 <amrith> I've starred it
18:45:06 <peterstac> that's a troveclient change that should probably make it in as well (guestlog swift client fix)
18:45:17 <amrith> OK, list updated
18:45:19 <peterstac> yeah, I think it should be
18:45:33 <amrith> OK all: this is the review focus list https://review.openstack.org/#/q/starredby:amrith
18:45:34 <peterstac> (I forgot to put in a bug for it, my bad)
18:45:40 <amrith> as things come up, I'll update this list
18:45:48 <amrith> so if we can use that list to drive reviews for now
18:45:54 <amrith> I think we'll make forward progress quickly
18:47:25 <amrith> ok, if you find other shortcomings with the list, please IRC me
18:47:30 <amrith> #openstack-trove or PM
18:47:35 <amrith> I'll keep the list up to date
18:47:38 <amrith> that's all we've got
18:47:44 <amrith> ok to wrap up this meeting?
18:47:46 <amrith> going once ...
18:48:05 <amrith> going once more
18:48:32 <amrith> thanks folks
18:48:33 <amrith> #endmeeting