16:00:07 #startmeeting Cinder 16:00:07 Meeting started Wed May 11 16:00:07 2016 UTC and is due to finish in 60 minutes. The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:11 The meeting name has been set to 'cinder' 16:00:15 Hi! 16:00:16 hi 16:00:16 Agenda: https://wiki.openstack.org/wiki/CinderMeetings#Next_meeting 16:00:22 hi 16:00:22 hi 16:00:25 Howdy 16:00:25 hi 16:00:26 Courtesy ping: dulek duncant eharney geguileo winston-d e0ne jungleboyj jgriffith thingee smcginnis hemna xyang tbarron scottda erlon rhedlind jbernard _alastor_ vincent_hou kmartin patrickeast sheel dongwenjuan JaniceLee cFouts Thelo vivekd adrianofr mtanino yuriy_n17 karlamrhein diablo_rojo jay.xu jgregor baumann rajinir 16:00:26 hola 16:00:27 Hello! 16:00:30 hi 16:00:32 smcginnis: thanks 16:00:32 hi 16:00:34 hi all 16:00:38 Happy Wednesday! 16:00:41 hi 16:00:41 hi! 16:00:48 Hello :) 16:01:01 yough 16:01:05 Hey everyone. Looks like a short agenda today. 16:01:09 * smcginnis crosses fingers 16:01:10 Hi 16:01:24 Hello 16:01:27 #topic Announcements 16:01:38 * thingee has a doc appt today. gave update on action stuff in #openstack-cinder 16:01:44 hi 16:01:48 hi 16:01:55 thingee: Thanks! 16:02:05 according to the agenda, it should it a fast meeting, I guess 16:02:11 hi 16:02:17 We are now on week R-21 of the Newton cycle. 16:02:27 #link http://releases.openstack.org/newton/schedule.html Release schedule 16:02:36 Good progress so far I think. 16:02:43 hi 16:02:47 I've been seeing a lot of spec reviews. Keep it up. 16:03:03 Great to get eyes on those so we can get them updated and approved earlier. 16:03:20 #link https://etherpad.openstack.org/p/cinder-spec-review-tracking Spec reviews 16:03:23 #link https://etherpad.openstack.org/p/cinder-spec-review-tracking 16:03:25 :) 16:03:27 ;) 16:03:44 And just a mention... 16:03:49 #link https://bugs.launchpad.net/nova/+bugs?field.status:list=NEW&field.tag=volumes Nova volume bugs 16:04:00 They can always use help triaging and fixing there. 16:04:31 In case anyone missed it, midcycle was (re)set last week. 16:04:55 We are now overlapping with Nova, for better or worse. 16:05:01 smcginnis, probably should update the ML thread ? 16:05:06 We should be able to do a midcycle-to-midcycle link. 16:05:16 hemna: Trying to look that up and type at the same time. ;) 16:05:32 #link https://etherpad.openstack.org/p/newton-cinder-midcycle Midcycle Etherpad 16:06:02 :) 16:06:03 #link http://lists.openstack.org/pipermail/openstack-dev/2016-May/093637.html Midcycle Announcement 16:06:08 There are discounted rooms available, but there is not a block of rooms reserved, so book now! 16:06:23 scottda: Thanks for the reminder. I still need to do that. 16:06:42 Any other announcements I've missed? 16:06:49 maybe I'll just bring a tent and camp at estes Park and commute every day to save on hotel..... 16:06:51 :P 16:06:57 hemna: That sounds good to me. 16:07:01 Also, if you call any other hotel than the one listed, feel free to mention you are with Hewlett-Packard and you might get a discount. 16:07:07 Did that following the last midcycle there. 16:07:14 yah works for me 16:07:36 #topic Open Discussion 16:08:07 I've been seeing lots of CI failures in os-brick CIs 16:08:08 Is tbarron done forcing 10k rebases? 16:08:13 EMC, HP, etc 16:08:15 thingee is working on this, but want to just mention again here that we discussed requiring CI for backup drivers. 16:08:26 hemna: Specifically on OS-brick? 16:08:28 would be nice if we can get those CI's working so we can get some of the os-brick patches to land 16:08:41 smcginnis: +2 on CI for backup drivers 16:08:43 Swanson: done 16:08:48 CI's on the Cinder repo aren't doing so hot either. 16:08:50 dunno, might not be specific to os-brick 16:08:54 hemna: I’ll take a look of EMC ones 16:09:01 xyang, ok thanks 16:09:02 #info CI will become a requirement for backup drivers 16:09:09 I tried issuing rechecks on them this morning 16:09:22 The one issue I see with the backup driver CIs is we really don't have much tempest coverage there right now. 16:09:38 smcginnis: do we know what tests we are going to run for backup CI? 16:09:38 So if someone is looking for something to do, I think our test coverage could be expanded on backups. 16:09:40 tbarron: Excellent. Appreciated and hated all at the same time. 16:09:48 tbarron: So far I think we only have two. 16:10:11 smcginnis: I'll ask our QA team for it. maybe they will be able to contribute on it 16:10:18 tempest.api.volume.admin.test_volumes_backup.VolumesBackupsV[1|2]Test 16:10:20 smcginnis: so I think we should be looking at benefit vs cost here until we have useful tests 16:10:24 e0ne: That would be great. 16:10:34 I haven't looked into the full scope of these tests. 16:10:45 It could very well be they are covering most operations in the one test. 16:10:54 But gut feel is there should be more there. 16:11:05 tbarron: we have to test at least what we have right now 16:11:11 also, most of the drivers are non-vendor-specific 16:11:25 so we'll need to arrange with infra to get them run, right? 16:11:27 We should be testing that backuped data is actually there 16:11:32 tbarron: in such case, they could be tested with infra 16:11:55 tbarron: Yeah, open source solutions should be covered by infra. We will need to look in to that. 16:12:00 geguileo: good point 16:12:23 Backup with encrypted volumes, incremental backups, etc. 16:12:34 Any other topics? 16:12:52 my only point is that this will be a difft flavor CI for the most part than volume drivers, where we're mailing vendors to tell them to implement 16:13:11 tbarron: Yes, true. 16:13:48 except for IBM TSM :) 16:14:13 Google cloud storage will need it as well. 16:14:18 tbarron: What do you mean? 16:15:47 Anything else? 16:15:57 Going once... 16:16:03 Going twice... 16:16:05 <_alastor_> Is there a doc somewhere about this new CI? 16:16:17 _alastor_: Not yet. It is in the works. 16:16:25 I just wanted to mention it here so it's no surprise. 16:16:29 <_alastor_> Ok, glad I haven't missed it 16:16:36 jungleboyj: it's the only vendor backup driver, right? 16:16:37 smcginnis: I've just send them a mail about CI 16:16:44 e0ne: Cool 16:16:58 pleeease, merge https://review.openstack.org/265811 :) 16:17:00 Oh, one other mention. Please run against os-brick patches as well. 16:17:12 Especially if you have a vendor specific connector. 16:17:15 tbarron: There are other vendor backup drivers. 16:17:40 smcginnis: the os-brick CI is not yet required, right? 16:17:41 jungleboyj: i stand corrected then 16:17:47 no updates from April 6th, and it makes my ralated patches chain longer 16:17:50 xyang: Not yet 16:17:52 tbarron:The Google one as well. 16:17:57 But I think we want to get there too. 16:18:13 jungleboyj: they are just a bit player :-) 16:18:18 jungleboyj: point taken 16:18:22 Test all the things! :) 16:18:24 tbarron: :-) 16:18:26 smcginnis: when? Ocata? 16:18:50 xyang: Yeah, probably. That seems like it would be a reasonable timeframe to me. 16:19:14 smcginnis: about the backup driver CI, is the requirement to have one in Newton? 16:19:26 xyang: TBD. 16:19:32 smcginnis: is this deadline are the same for both for os-brick and backups CIs? 16:19:45 xyang: I'm thinking since it's a new requirement, we probably can't make it a hard requirement until O. 16:20:00 e0ne: So probably both O given timing and such. 16:20:02 smcginnis: makes sense 16:20:06 smcginnis: Yeah probably not, though ideally as soon as possible :) 16:20:11 diablo_rojo: +1 16:20:12 Newton is going to be hard for people with backup drivers that don't have a volume driver CI yet 16:20:23 eharney: I agree. 16:20:26 smcginnis: ok. sounds reasonable to me 16:20:47 So I'd like to see vendors aware of it and working toward it in N so that by O we can make it a hard requirement. 16:21:05 smcginnis: I'll prepare a manual how to set up ci for backups. it should be easy done based on cinder 3rd party ci docs 16:21:24 e0ne: That would help a lot! 16:21:39 e0ne: Mike is planning on contact them, so make sure he is aware of anything you write up. 16:21:45 That could be very useful. 16:22:02 smcginnis: ok, thanks 16:22:06 Anything else? 16:22:29 OK, thanks everyone! 16:22:35 smcginnis: Thank you! 16:22:42 #endmeeting