15:10:05 #startmeeting Zaqar 15:10:06 Meeting started Mon Aug 25 15:10:05 2014 UTC and is due to finish in 60 minutes. The chair is flaper87. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:10:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:10:09 The meeting name has been set to 'zaqar' 15:10:13 #topic Roll Call 15:10:15 o/ 15:10:18 o/ 15:10:47 kgriffs: ? 15:10:52 malini ? 15:11:33 #topic Get rid of the config samples 15:11:45 This is today's agenda: 15:11:48 #link https://wiki.openstack.org/wiki/Meetings/Marconi#Agenda 15:11:54 damn, we need to rename that page 15:12:02 I think today's meeting is going to be quite short 15:12:11 o/ 15:12:18 malini1: hey there :) 15:12:27 yeah there are several wiki pages with references to Marconi... we will have to organize a renamewiki-rock-day 15:12:54 There were no action items last week 15:13:00 so we can get right to the meeting agenda 15:13:04 #topic Get rid of the config samples 15:13:10 so, I wanted to bring that up 15:13:25 there were some discussions in the mailing list about projects willing to get rid of config samples 15:13:31 I'd like to propose the same for Zaqar 15:13:40 keeping the config sample updated is a pain 15:13:48 and it's actually not reaaaaaaaaaaaaaaaaaaaaaally useful 15:14:03 Instead, we should provide a reliable way to generate it 15:14:16 seems like the generator script still has a bug on freebsd/osx 15:14:26 otherwise, I would be fine not checking in the sample 15:14:35 kgriffs: oh, that's a good point. I updated it the other day 15:14:40 did you try it recently? 15:14:44 we shud make sure to generate them in a painless way..generating sample for some of the projects gives me nightmares 15:14:47 iirc, it didn't parse command line args correctly 15:15:16 kgriffs: is this something you can put in your lowest-prio list ? 15:15:16 flaper87: i haven't tried in the past few days... vkmc have you? 15:15:28 I don't have OSx so I can't test it 15:15:44 Lets help fixing this script on OSx and then get rid of this sample 15:15:56 sounds like a plan 15:16:04 awesome 15:16:25 any other comment on this topic? 15:16:39 I don's have OS X either :/ 15:16:51 it works ok in GNU/Linux though 15:17:05 flaper87: did you sync the updated script from oslo incubator already? 15:17:53 kgriffs: mmh, I did but there were no changes now that I think about it 15:17:57 kgriffs: https://review.openstack.org/#/c/116275/ 15:18:02 #link https://review.openstack.org/#/c/116275/ 15:18:07 that patch fixed the config generator 15:18:22 kk 15:19:00 ok, moving on 15:19:06 #topic Juno Status 15:19:17 before moving to the next big topic, lets go through this 15:19:20 #link https://launchpad.net/zaqar/+milestone/juno-3 15:19:43 we're not in bad shape, although there are some blueprints that need some love 15:19:54 #link https://blueprints.launchpad.net/zaqar/+spec/threat-model 15:20:11 kgriffs: is that something you can take care of this week? 15:20:42 Just a note, I'd like to get all (most of) those blueprints implemented by the end of this week (mid of next) 15:21:00 I don't mean to put any preasure but I think it's important for the graduation request 15:21:08 (which is the next big topic of this meeting) 15:21:58 flaper87: yes, I should be able to get to that. If we have to, we can slip it... it isn't really a code deliverable, and I don't anticipate finding any major vulnerabilities, so I could do it after the milestone closes if need be 15:22:12 vkmc: do you think we can move this to Needs Review? https://blueprints.launchpad.net/zaqar/+spec/document-config-options 15:22:23 kgriffs: cool, so that can happen even after the code freeze 15:22:43 right 15:23:01 flaper87, I'm changing the way of generating the config tables to use the automated tools that use the docs team 15:23:18 kgriffs: awesome, lets leave it there 15:23:19 annegentle give it a look and asked me to do that 15:23:27 vkmc: how much do you think is left to do there? 15:23:34 malini1: thoughts about this one? https://blueprints.launchpad.net/zaqar/+spec/api-v1.1-functional-tests 15:23:43 nothing much but it's not ready to get a extensive review 15:24:03 it will be later today and I'll change the status of the bp 15:24:06 flaper87: Alex has already done most (and probably all )of it 15:24:31 It needs to be DRYd up, but that can happen as part of the testing-redux bp we have 15:24:32 malini1: cool, I'll mark it as implemented 15:24:47 malini1: +1 15:24:47 Do we need Tempest tests for v1.1 ? 15:24:53 vkmc: awesome, thanks a lot! 15:25:00 flaper87, np 15:25:05 malini1: yes, we should move v1.0 to v1.1 probably 15:25:23 flaper87: when should that happen? 15:26:00 malini1: oh well, I don't think it's high-prio. it'd be nice to have them before Juno is released, though. 15:26:12 v1.0 is still our officially released version 15:26:15 and that's covered 15:26:33 cool 15:27:05 Those are the doubts I had. Thank you all for working hard on this. 15:27:17 Other than that, I wanted to ask everyone to dedicate more time to reviews: https://review.openstack.org/#/q/status:open+project:openstack/zaqar,n,z 15:27:39 if the blueprints you were taking care of are done or close to done, consider dedicating extra time to review. 15:28:02 We need to review the redis work, patches that target blueprints and critical bugs. I'll prepare a priority list of patches 15:28:10 flaper87: what about api-v1.1-response-document-changes? i probably missed its discussion( 15:28:22 but until that list is done, please, go through that list and review 15:28:53 AAzza: we didn't discussed it. Since you just took over it, I thought that you needed more time. Do you have any extra feedback on it? 15:29:37 #link https://blueprints.launchpad.net/zaqar/+spec/api-v1.1-response-document-changes 15:30:01 flaper87: not really, i think i will propose several patches in next few days, and then clarify other points 15:30:17 To be fair, pretty much everything we have under review has high priority 15:30:19 :/ 15:30:31 AAzza: awesome, thanks for working on that! 15:30:49 anything else? 15:31:06 #topic Graduation 15:31:16 DRUMBS PLEASE! 15:31:31 DRUMB DRUMB 15:31:40 It is that time of the cycle, we need to vote on whether we want to go for it or not. 15:31:48 #link https://etherpad.openstack.org/p/marconi-graduation 15:31:56 #link https://launchpad.net/zaqar/+milestone/juno-3 15:32:06 Before we vote, I'd like to say a couple of things 15:32:31 I have some thoughts too 15:32:34 1. We're in better shape than last time. This in terms of gate jobs, API stability, integration with the community, communication and things 15:32:53 2. Our current documentation is getting way better, which we didn't have last time 15:33:21 3. The number of use-cases keep growing and people interested in Zaqar are putting preassure on us to graduate 15:33:59 There are still things community/software wise that need love, though. The graduation process won't be easy but I don't think we'll need to withdraw it this time 15:34:01 :P 15:34:04 at least that :D 15:34:06 kgriffs: go ahead 15:34:34 so, the last big thing that hasn't landed yet that I think would be a legitimate reason for our request to be denied 15:34:37 Redis driver 15:34:44 (AGPL haters will be haters) 15:35:09 kgriffs: +1 +1 +1 +1 15:35:17 +1 15:35:19 second thing is that I think we ought to get the thumbs up from 2-3 TC members BEFORE going for it 15:35:27 kgriffs: +1 15:35:39 we need somebody to advocate why we should graduate 15:35:43 if we can't get a couple people to say "yeah, you look good" then we might as well not even apply 15:36:09 The graduation request must be sent this week 15:36:19 If my maths are correct 15:36:37 I'll contact folks and get feedback 15:36:41 We also need to publish the benchmark numbers prior to that 15:36:46 We can sync again on Wednesday 15:37:03 malini1: good point 15:37:05 malini1: thanks for the reminder. I almost forgot that was my third thing 15:37:10 so, that is tied up with redis 15:37:22 shall I publish some rough mongodb-only numbers today? 15:37:30 kgriffs: that'd be good 15:37:30 We should also get the tempest job going again before the grad request 15:37:35 second thing is I think prashanth is traveling this week? 15:37:46 Lets start with something, we can publish the rest later 15:38:10 I haven't seen him around today, if he's traveling, we may have to update his patch ourselves 15:38:28 kgriffs: you could also download his patch and use if for the tests 15:38:32 before it lands 15:38:42 I am pretty sure he is going to be gone all week...so yeah, i was going to ask if you guys think it would be cool for me to take over his patch and land it 15:39:02 flaper87: I could do that, but I'd want to fix that race condition in any case 15:39:09 kgriffs: I'd say go for it 15:39:22 OK. 15:39:30 #action kgriffs to land redis patch 15:39:45 ok, it seems we're not ready to vote but, lets do a show hands voting 15:39:48 #action kgriffs to publish rough benchmark numbers, more later with redis numbers 15:40:28 Assuming we get good feedback from 2 or 3 TC members and the bench results are out. Do you think we should try to graduate? Vote yes/no 15:40:31 Yes 15:40:40 Yes 15:40:42 yes 15:41:26 kgriffs: AAzza ? 15:41:36 and the redis patch lands 15:41:38 yes 15:41:50 * flaper87 was giving the redis thing for granted 15:41:52 :P 15:42:00 AAzza: ? 15:42:01 hmm, yes 15:42:08 hmmm? 15:42:20 AAzza: should we have covered something else? 15:42:21 ok, cool! We can do a final vote in the channel before the end of this week. 15:42:21 what will be if we fail? 15:42:32 AAzza: we remain incubated 15:42:43 for another development cycle 15:42:47 * flaper87 hopes 15:42:49 :P 15:43:04 sad panda 15:43:09 Too many things happening in OpenStack lately, The future is cloudy 15:43:30 ok, moving on! 15:43:36 #topic Open Discussion 15:43:59 Sorry for rushing the meeting a bit, I've some, quite delicate, personal matters to take care of in 10mins 15:44:07 Before I leave, I wanted to say: 15:45:00 1. The OPW internship has ended. I'd like to thank AAzza for her amazing job and contributions. I'm really happy with all your work, reviews and support. I hope you'll stick around and keep contributing to the project 15:45:54 2. GSoC has also ended. vkmc I don't think we can thank enough all the things you've done in these last months. Thanks for all your efforts, hard work, contributions. Thanks for helping newcomers and for sticking around with us 15:46:11 Both your contributions are really appreciated and you both did an amazing job. 15:46:35 flaper87: thanks, you all are so friendly and nice , so i definitely will be with zaqar and openstack in the future :) 15:47:03 I'd like to second that. Can't say enough how much we've appreciated your contributions, vkmc and AAzza (and prashanth!) 15:47:30 kgriffs, flaper87, thanks :) I'm glad that I had the opportunity to work with the Zaqar team and looking forward to do more, stronger, contributions 15:48:13 * flaper87 was saving prashanth thanks for when he'd be around :D 15:48:24 but yeah, thanks a lot prashanth for that great new driver you've given us :D 15:48:28 :) 15:48:38 ok, that's it from me folks 15:48:40 in case he reads the log. :p 15:48:48 kgriffs: well thought :D 15:48:48 rock on 15:48:58 anything else you'd like to discuss? 15:49:34 I'm good. anyone else? 15:49:43 none from me 15:49:43 ok, thank you all! Lets keep the hard work up and focus on reviews! :D 15:49:56 #endmeeting