16:01:20 #startmeeting CInder 16:01:22 Meeting started Wed Sep 14 16:01:20 2016 UTC and is due to finish in 60 minutes. The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:24 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:27 The meeting name has been set to 'cinder' 16:01:34 CInder 16:01:36 hey! 16:01:38 Hello. 16:01:38 Swanson: :P 16:01:42 hi 16:01:42 hi 16:01:43 Hello :) 16:01:44 Can't type this week. 16:01:45 .o/ 16:01:47 ping dulek duncant eharney geguileo winston-d e0ne jungleboyj jgriffith thingee smcginnis hemna xyang1 tbarron scottda erlon rhedlind jbernard _alastor_ bluex patrickeast dongwenjuan JaniceLee cFouts Thelo vivekd adrianofr mtanino yuriy_n17 karlamrhein diablo_rojo jay.xu jgregor baumann rajinir wilson-l reduxio wanghao thrawn01 chris_morrell stevemar watanabe.isao,tommylike.hu 16:01:50 Hello! 16:01:55 hi 16:01:56 hi 16:01:57 hi 16:02:01 howdy 16:02:04 hi 16:02:06 o/ 16:02:08 Hey 16:02:11 Hello all 16:02:13 Hey 16:02:33 #topic Announcements 16:02:40 yough 16:02:52 RC1 deadline is here. 16:03:02 I'll submit the request tomorrow. 16:03:13 There's a few things I would like to try to get in before then. 16:03:36 I think I only have until tomorrow afternoon though. Then we will have to look at an RC2. 16:04:04 Which is pretty much inevitable, but good to limit what goes in there. ;) 16:04:12 smcginnis: do we have a list of issues for RC1? 16:04:30 e0ne: Bugs are targeted for RC1. 16:04:44 I can create an RC2 milestone so we can target things to that as well. 16:04:47 smcginnis: thanks! I'll take a look on reviews tomorrow morning 16:04:52 e0ne: Thanks! 16:05:04 It's also hard string freeze after this point. 16:05:19 So we need to be more strict about allowing translatable string changes through. 16:05:31 #link https://launchpad.net/cinder/+milestone/newton-rc1 16:05:45 4 more patches. :) 16:05:50 I'd rather have a bug fixed than have a properly translated error. 16:05:53 dulek: Thanks! 16:06:01 o/ 16:06:06 OK, forward looking now. 16:06:11 We need to plan for the design summit. 16:06:25 The final design summit at that. :] 16:06:41 bleh 16:06:48 #info Start thinking of design summit topics 16:06:54 #link https://etherpad.openstack.org/p/ocata-cinder-designsummit-planning Planning etherpad 16:06:57 o/ 16:07:15 Please feel free to add any and all topics to that etherpad. 16:07:28 We have 4 fishbowls and 4 working rooms. 16:07:36 One less wr than last time. 16:07:52 Also the meetup on Friday is compressed, so rather than a full day we just have half a day. 16:08:08 So if you havent already booked travel, please try to stick around through the whole day. 16:08:12 which means half a day for beer. 16:08:16 ;) 16:08:19 hemna +1 16:08:31 smcginnis: is the space allocation official? 16:08:33 smcginnis: the friday meetup is in the afternoon, right 16:08:44 bswartz: Good point. These are proposed allocations. 16:08:51 This could potentially change. 16:08:52 hi 16:08:58 xyang2: Yes, I believe so. 16:09:00 hemna: +1 16:09:00 hemna: +@ 16:09:02 * tbarron sneaks into the last row 16:09:04 hemna: +2 16:09:19 * jungleboyj is distracted by tbarron's late arrival. ;-) 16:09:21 Given how meetup went in Austin, half a day may actually be a good idea. 16:09:37 dulek: I agree. I think that should be fine. 16:09:45 We're usually kind of toast by that point anyway. 16:10:09 #topic Proprietary libs for drivers 16:10:13 dulek: ++ 16:10:33 So last week we started discussing the use of "third party" code in Cinder. 16:10:43 #link https://etherpad.openstack.org/p/cinder-brick-driver-externals Tracking etherpad 16:10:59 I think this is actually going to be a broader cross project discussion at the summit. 16:11:12 good 16:11:28 Some good research in that etherpad. I didn't really get as much time as I wanted to look through our drivers. 16:11:37 Agreed. Good to get broad agreement on this. 16:11:46 smcginnis: I'll be surprised if the list is so short:) 16:11:59 fwiw, the brick connectors aren't using proprietary 3rd party python libraries 16:12:10 I think bottom line, we probably aren't going to make any policy changes right now until we have that cross project discussion. 16:12:10 they are using proprietary binaries that they call out 16:12:13 hemna: OK, good! 16:12:46 so, it still doesn't work unless the deployer installs those tools 16:12:54 xyang2: I am surprised it is that short. 16:12:54 sad 16:12:58 so it still hurts helion, redhat, etc 16:12:59 GPL binaries != proprietary though (I didn't get time to investigate them all) 16:13:08 We'll probably need to clearly define what's OK (compiled vs scripted/interpreted) as well as just general requirements for some systems. 16:13:09 I think we need to make distinction on libs that need to be imported and other things that does not need to be imported 16:13:16 DuncanT, yah, it's really only 3 of em 16:13:21 DuncanT: Oh good, you're here. 16:13:31 jungleboyj: that can't be a complete list 16:13:32 I'm sure the list is longer than that, it seems to be a work in progress 16:13:41 smcginnis: for a while, yes 16:13:47 Yes, I think that list is just a start. 16:14:19 So for the purposes of this meeting I think for now it's just awareness. If anyone has time to spend looking into this, please update that etherpad with anything you find. 16:14:20 If anybody knows the answer for their driver (including library) then it's worth adding 16:14:29 We're just at the data collection stage for this. 16:14:35 DuncanT: +1 16:15:04 I won't take up too much time on this today since we still need to gather data. 16:15:15 #topic Testing the upcoming release 16:15:18 scottda: Hey 16:15:27 DuncanT: the dependencies of the NetApp driver are going to be complicated to explain, because they're optional 16:15:28 hi 16:15:43 I was noticing that dulek was testing upgrades... 16:15:43 smcginnis: We are actively working the XIV issue. Just FYI. 16:15:46 #link https://etherpad.openstack.org/p/cinder-newton-testing Test area tracking 16:15:49 jungleboyj: Thanks 16:16:14 and I thought "This is great. Someone should do things like test stuff .." 16:16:16 * dulek tested that they're almost in a working state. ;) 16:16:27 scottda: ;) 16:16:30 But we never really know what is being tested, and by whom. We just hope. 16:16:40 Fair statement I think. 16:16:51 the right time to test stuff is actually the last 2 weeks... 16:17:00 So, maybe at some point (even earlier in the release) we should document what should be tested, and whom might be doing it. 16:17:03 if you're testing at this point you're a bit late to the game 16:17:12 Not sure how much we can still do for Newton, but if we can get some focus on areas that would be good. 16:17:19 bswartz: Right,i just got the idea a bit late... 16:17:34 One of the things I would like to see for Ocata is having it be more testing and stabilization focused. 16:17:49 so maybe for O release, we just think about things that aren't covered will in automated testing, or we know is falling into the gaps.. 16:17:57 So if I'm still PTL, I'll adopt this etherpad idea for O so we can try to get some good coverage. 16:18:02 smcginnis: ++ to that idea. 16:18:15 smcginnis, +1 16:18:16 smcginnis: the shortness of Ocata might make that an absolute necessity 16:18:18 Was that a thinly-veiled campaign promise? 16:18:27 bswartz: Yeah, that's what I'm thinking. 16:18:27 thinly ? 16:18:36 If elected, I promise to... :) 16:18:54 Will you promise us free testing? 16:18:59 smcginnis, how big are your hands? do you have pneumonia? 16:19:10 jseiler_: A ham in every oven. 16:19:11 * bswartz rofl 16:19:29 :) 16:19:30 Anyway, there's the etherpad. It is a bit late to talk about testing at this point. But it seemed like a good idea to start tracking this stuff. Like we would probably be doing at our own companies.. 16:19:47 scottda: +1 Thanks for bringing that up. 16:19:53 Mmmm, not had ham for ages 16:20:00 np. Thanks. 16:20:02 DuncanT: Hah! 16:20:18 smcginnis: NOOOOO!!! They never keep their promises. ;-) 16:20:32 :) 16:20:47 #topic Major RPC API version bumps 16:20:56 dulek: You're up 16:21:32 Okay, so you've probably noticed all these FIXME(dulek): Remove in RPC API 3.0. 16:21:56 I like how that reads, FIXME(dulek) :) 16:22:04 ;> 16:22:16 In early Newton we've got rid of them by bumping major RPC API versions of all RPC APIs. 16:22:32 This is a quite big change, with some risk. 16:22:59 What are the risks? 16:23:02 dulek: Some risk, but it should be fairly obvious if we messed it up right away, right? 16:23:36 smcginnis, DuncanT: Exactly, that wouldn't be 100% tested in the gate 16:23:51 And manual testing sometimes fails. ;) 16:24:01 If anyone is very bugged by all of these compatibility shims, then I can work to get changes bumping major versions up before a release tomorrow. 16:24:26 dulek: Any reason to wait? 16:24:46 Dulek: given we're likely to need others, having since examples around isn't necessarily bad 16:24:48 But I thought that if Ocata is a short cycle, then we can live a few more months with these shims still in place and get that done in Ocata. 16:25:13 Got to go, sorry 16:25:27 dulek: why bumping the RPC API version so late has lower risk? 16:25:43 DuncanT: Thanks! 16:25:54 bump it early in the O cycle and see what happens 16:26:20 hemna, dulek: If there's some concern about doing this, that might be the right answer. 16:26:24 smcginnis: Major RPC version bump is a change that anyone upgrading trunk-to-trunk needs to upgrade to before going further, so they're a little unconvinient for operators. 16:26:28 hemna: Agreed. 16:26:37 Then we can have the whole (limited) cycle to find issues. 16:26:51 yah that makes sense to me 16:26:51 Sounds like a good plan to me 16:26:55 hemna: Early O won't actually work. ;) 16:27:11 Let me find the actual change from late Mitaka and early Newton. 16:27:16 I agree. 16:27:18 uhh ? 16:27:26 Some documented shims are not the end of the world. 16:27:41 dulek: Why not? 16:27:42 hemna: That's late Mitaka: https://review.openstack.org/#/c/283072/ 16:28:04 hemna: It complicates the manager code - manager can handle both 1.x and 2.0 16:28:23 And this is early Newton change: https://review.openstack.org/#/c/297699/ 16:28:39 so we are now setting ourselves up for only allowing these types of changes right at the end of the release?! 16:28:43 !! 16:28:44 hemna: Error: "!" is not a valid command. 16:28:48 :) 16:28:53 no really...!! 16:28:55 :) 16:29:05 :) 16:29:05 anyway, this scares me 16:29:10 This one actually cleans everything up, so Newton development is free of the technical debt of compatibility stuff. 16:29:26 I think !! should be a bot macro to paste a table flip. 16:29:30 hemna: Weeeell, I've just did it like Nova does with n-cpu. 16:29:33 smcginnis, :) 16:29:34 smcginnis: ++ 16:29:53 !! 16:29:54 jungleboyj: Error: "!" is not a valid command. 16:30:00 A barfight ensues 16:30:04 They're doing same thing in RC target week. 16:30:17 :( 16:30:30 (that's why their release is on "Thursday evening, Dan Smith time" ;)) 16:30:37 dulek: So when do you think is the best for us to do this? Right before RC1? Or as part of an RC2? 16:31:18 RC2 can never happen, so if we really want to clean up technical debt now, we should do it in RC1. 16:31:34 RC2 can never happen? 16:32:05 smcginnis: If there are no high or critical issues, then why would it? :P 16:32:22 smcginnis: it's possible we never need an RC2 16:32:26 smcginnis: perfect world 16:32:38 dulek: I think we've almost always done an RC2 (or RC3) due to last minute requirement changes, translation strings, etc. 16:33:01 jgriffith: Nah, perfect world we just cut the final branch and move on. :P 16:33:11 sun comes up every day for billions of years. eventually you expect it. there'll be an rc2. 16:33:12 smcginnis: dulek FWIW I'm not comfortable bumping major number during RC releases 16:33:27 My point was - you can see doing the change is constrained, a little difficult and Nova also isn't doing them always. So if we're fine with the presence of compatibility shims through Ocata, I would do it a release later. 16:33:31 Swanson: tomorrow could be *the* dark day 16:33:38 jgriffith, +1 16:33:50 that stuff shouldn't be done at that stage of the release 16:34:03 jgriffith: That is a dark though. 16:34:04 way too much risk IMHO 16:34:06 *thought 16:34:35 dulek: how much do we gain from doing the bump now? 16:34:35 smcginnis: https://storyboard.openstack.org/#!/story/2000726 16:34:39 I still doesn't understand why we want to merge such risky patch after feature freeze 16:34:49 dulek: I mean... how much esier is it going to make my life? 16:34:51 s/doesn't/don't 16:34:52 hemna: sounds odd to me a major version bump needs to happen so late in the cycle rather than in the beginning 16:35:20 xyang2, +1 16:35:36 jgriffith: Getting rid of these https://github.com/openstack/cinder/blob/f6c20ed00b9febaea42ac34d2988c1cf6c883b10/cinder/scheduler/rpcapi.py#L111-L114 16:35:54 bswartz: LOL! That's awesome! 16:36:06 dulek: I do kinda like that 16:36:09 +1 for waiting until ocata for major version bump 16:36:10 dulek: getting rid of those 16:36:18 lol 16:36:34 xyang1, hemna: If we're doing it at the beginning, then we need to live with manager accepting 2.x *and* 3.x through the release. 16:36:51 dulek: and if it's the very first change in Ocata, we add some complication to any potential backporting right? 16:36:54 xyang1, hemna: As people will upgrade Newton->Ocata. 16:36:56 dulek, I think that's far less risky 16:37:13 bswartz: Nice! I like that I was the example. 16:37:17 dulek: ok, you've convinced me 16:37:32 dulek: my vote is submit the patch today or tomorrow. :) 16:38:02 "we need to live with manager accepting 2.x *and* 3.x through the release" Today or tomorrow would be my vote if this is the case. 16:38:28 smcginnis: That's only if we would do it early in Ocata. ;) 16:38:43 dulek: Right. So I'm saying to avoid that, let's do it now. 16:39:03 so I was concerned about a bump like that during RC, but I'm less concerned with that than dealing with the burden of multiple version monkey biz for another full release 16:39:11 smcginnis: Okay, I'll work double time to get the patches up. 16:39:13 jgriffith: +1 16:39:19 phew 16:39:22 :) 16:39:28 dulek: Thank you! :) 16:39:37 Well, then I'm glad I've asked for opinion of you all! Thank you! 16:39:41 I guess, do we eat a turd sandwich now or for 6 months.... 16:39:51 hemna: I get your point too... but I'd rather make this horse trade honestly. 16:39:53 hemna: Nice. 16:39:54 sucks either way. 16:39:59 hemna: Hah, one way to put it. :) 16:40:08 hemna: nahh... it's going to go beautifully without a hitch 16:40:24 jgriffith, we are quoting you on that one! :P 16:40:38 we need to break the cycle of "half in half out" in so many places 16:40:39 hemna: He does have horses to trade! 16:40:45 objects, rpc, api-versions etc 16:40:49 everything is "half" 16:40:53 BTW some info: https://wiki.openstack.org/wiki/RpcMajorVersionUpdates#Mixed_version_environments_.28nova-compute.29 16:41:01 jgriffith: Fix it all in Ocata! :) 16:41:10 smcginnis: I'd love that 16:41:35 dulek: OK, anything else? 16:41:47 smcginnis: READ MY LIPS... "NO NEW FEATURES" 16:41:53 :) 16:41:56 smcginnis: No, thank you. Link above is for anyone willing to understand the topic better. :) 16:41:58 most of you probably aren't even old enough to know what I'm quoting there 16:42:03 jgriffith: +1! 16:42:05 dulek: do we need another major bump at the end of next release? 16:42:05 dulek, is this going to be a recurring theme every release? 16:42:12 jgriffith: Does that mean I get to start a Star Wars program? 16:42:13 A Broken campaign promise? 16:42:22 jgriffith, heh 16:42:26 smcginnis: ha! Yayyy for history! 16:42:40 Yay for being old! :D 16:42:47 smcginnis: it has it's perks 16:42:49 xyang1, hemna: Depends on how much compatibility code we're introducing. I don't see a reason to do that if we have one or two shims in rpcapi and manager. 16:42:51 smcginnis, as long as the laser beams are installed on sharks. 16:42:55 jgriffith: True! 16:43:02 hemna: ;) 16:43:12 #topic Open discussion 16:43:29 smcginnis: I love lasers! 16:43:38 hemna: I found this (for Friday) http://www.driftwoodjournals.com/10-best-craft-beer-bars-in-barcelona-an-inside-guide/ 16:43:47 jungleboyj: Just don't point them in your good eye. oO 16:43:52 hemna, xyang1: It's likeā€¦ Backwards compatibility is hard only if we're changing. ;)_ 16:43:53 bswartz, now that's an important topic 16:44:11 bswartz: Always working on the things that really count! :D 16:44:15 bswartz Nice work. 16:44:17 Ooooh, someone told me there's one huge multitap pub in Barcelona. 16:44:21 dulek: ok, thanks:) 16:44:54 Anything else for today? 16:45:01 bswartz: Nice! Good sign they have that. Won't be stuck with Wine like in Paris. :-) 16:45:05 man, a city in europe that actually has beer. 16:45:12 bswartz: This is also promising: http://www.ratebeer.com/p/biercab-barcelona/38780/ ;) 16:45:21 hemna: We should go to Germany next time. 16:45:29 smcginnis, +1 16:45:40 Next Design Summit is in Akron, Ohio 16:45:46 hemna: Gdansk or Wroclaw works too if you'll happen to be in Poland. ;) 16:45:52 scottda: Akron? I thought it was Atlanta? 16:45:58 PTG 16:46:08 I was joking. I didn't know it was even decided. 16:46:15 scottda, just as long as it's not in Utah...no alcohol on Sundays. 16:46:16 Yeah its Atlanta 16:46:20 scottda: Hah! Yeah, I think I heard Atlanta is set. 16:46:23 scottda: Pennsylvania I tihnk 16:46:29 crap, really back to Atlanta ? 16:46:44 hemna: at least it is February 16:46:46 Yep. Atlanta for the first PTG 16:46:54 hemna: it will be in February though so not quite as hot 16:46:59 ah ok 16:47:00 easy to fly there, just don't try to drive 16:47:01 wait... what? 16:47:01 xyang2: Isn't it snowing there in February? 16:47:08 once you are there 16:47:12 dulek: no 16:47:14 didn't realize ya'll were being serious 16:47:18 Atlanta had the worst summit food 16:47:19 * jgriffith comes out from under his rock 16:47:20 dulek: it is a warm place 16:47:29 jgriffith: http://www.openstack.org/ptg/ 16:47:39 thanks bswartz 16:47:40 damn, where have I been 16:47:45 xyang2: Oh, pretty great then, I was scared by a conference in winter. :) 16:47:48 hemna: oh, we need how many hands to hold bowls? 16:48:19 xyang2, exactly 16:48:25 *Sigh* Atlanta. 16:48:39 Hey, I didn't think it was _that_ bad. :) 16:48:41 dulek, If it was in MN in February, that would be cause for concern. 16:48:43 hemna: It was terrible. 16:48:57 smcginnis: time to lose some weight:) 16:49:12 smcginnis: it is so hot there, and we don't have enough food to eat 16:49:14 diablo_rojo: It would be good for character building. 16:49:17 I don't see Atlanta on that page 16:49:24 xyang2: I think I did at that summit. I was walking a few miles a day back and forth to my hotel. :) 16:49:27 I guess it's just not announced? 16:49:29 hemna: start at the top 16:49:34 they should have picked FL 16:49:34 :) 16:49:43 hemna, tweeted a week or so ago I think 16:49:44 +1 for Florida 16:49:51 OK, I think we're past the point of productivity. Thanks everyone! 16:49:51 bswartz, reading is hard.... 16:49:52 smcginnis: Up and down hills. It was good exercise. 16:49:52 https://www.openstack.org/ptg/ 16:49:55 hemna: http://lists.openstack.org/pipermail/openstack-dev/2016-September/102981.html 16:49:57 The Zika summit 16:50:03 Poor Duncan was in the ghetto. 16:50:06 smcginnis, LOL 16:50:08 smcginnis, :) 16:50:09 florida? So you can die and show up on the FloridaMan twitter feed? 16:50:18 #endmeeting