16:00:01 <smcginnis> #startmeeting Cinder
16:00:02 <openstack> Meeting started Wed Jan 13 16:00:01 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:04 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:06 <openstack> The meeting name has been set to 'cinder'
16:00:10 <thingee> o/
16:00:12 <eharney> hi
16:00:13 <smcginnis> Courtesy ping: dulek duncant eharney geguileo winston-d e0ne jungleboyj jgriffith thingee smcginnis hemna xyang tbarron scottda erlon rhedlind vincent_hou kmartin patrickeast sheel
16:00:16 <scottda> hi
16:00:17 <jseiler> hi
16:00:17 <mriedem> o/
16:00:20 <hemna> hi
16:00:20 <yhayashi> hi
16:00:22 <Yogi1> hi
16:00:23 <mtanino> o/
16:00:23 <jgregor> Hello
16:00:23 <geguileo> smcginnis: Thanks
16:00:25 <geguileo> Hi
16:00:26 <erlon> hi
16:00:29 <e0ne> hi
16:00:32 <smcginnis> geguileo: ;)
16:00:34 <DuncanT> Hi
16:00:37 <sheel> Hi everyone..
16:00:44 <claudiub> o/
16:00:45 <jungleboyj> Hello.
16:00:49 <kmartin> hi
16:00:50 <smcginnis> Nice, looks like a good turnout today. :)
16:00:51 <diablo_rojo> Hello :)
16:00:55 <bardia> hi
16:00:57 <smcginnis> #topic Announcements
16:01:09 <xyang1> hi
16:01:11 <flip214> hi
16:01:13 <jungleboyj> At least a turnout.  :-)
16:01:33 <smcginnis> Reviewers, please take a look at the spec tracking/review priority etherpad.
16:01:39 <smcginnis> #link Spec tracking https://etherpad.openstack.org/p/mitaka-cinder-spec-review-tracking
16:01:47 <smcginnis> Some good progress there.
16:02:19 <smcginnis> #info Bugstats: Cinder-462, cinderclient-36, os-brick-13
16:02:23 <dulek> o/
16:02:28 <thingee> Would like to mention the cross-project spec liaison group is coming together. I'm assuming diablo_rojo would be representing cinder https://review.openstack.org/#/c/266072/
16:02:33 <smcginnis> Those numbers just seem to hold steady.
16:02:43 <diablo_rojo> thingee: Correct
16:02:56 <smcginnis> thingee: Thanks! Yep, she's volunteered. :)
16:03:33 <smcginnis> Forward looking to the agenda, but please take a peek at the midcycle planning:
16:03:38 <smcginnis> #link Midcycle planning https://etherpad.openstack.org/p/mitaka-cinder-midcycle
16:04:03 <smcginnis> Add your info if you are going, and make sure to add any topics a little ways down the page.
16:04:30 <smcginnis> We have a nova<>cinder time reserved Wednesday morning Raleigh time, Wednesday evening Bristol UK.
16:04:45 <hemna> great
16:04:50 <mriedem> what time is that wed night in bristol?
16:05:00 <smcginnis> scottda will have more to say about that shortly.
16:05:14 <scottda> Exact time is not set yet
16:05:15 <smcginnis> mriedem: I'm not sure if we locked down a specific time.
16:05:16 <thingee> Mitaka 2 is jan 19-21
16:05:38 <e0ne> we'll get TheJulia from Ironic there too
16:05:39 <smcginnis> I'll check with johnthetubaguy later, unless someone else beats me to it.
16:05:49 <mriedem> sure, just should be before 5pm :)
16:05:53 <mriedem> else we'll be pub crawling
16:05:58 <smcginnis> #info M-2 coming up January 19
16:05:59 <hemna> :)
16:06:12 <smcginnis> mriedem: Fair point! :)
16:06:27 <smcginnis> Make sure folks are aware of the deadline with M-2.
16:06:27 <jungleboyj> mriedem: Hmmm, Cinder isn't the only group that does that?  ;-)
16:06:33 <thingee> Jan 31 longer delays with gate ci testing
16:06:50 <smcginnis> thingee: Very good point. Don't wait until the end!!!
16:07:00 <thingee> Due to sunsetting of a public cloud that infra uses
16:07:15 <thingee> all this and more on the dev digest http://www.openstack.org/blog/2016/01/openstack-developer-mailing-list-digest-20160108/
16:07:31 <dulek> thingee: Ah, right in the M-3 period… :(
16:07:31 <smcginnis> #link Infra changes https://etherpad.openstack.org/p/mitaka-cinder-midcycle
16:07:35 <smcginnis> thingee: Thanks!
16:07:58 <smcginnis> diablo_rojo: Want to cover a little cross-project stuff?
16:08:06 <johnthetubaguy> mriedem: smcginnis: I hadn't picked the time yet, good point, when did you folks want to start? lets pick then? (+1 for before 5pm!)
16:08:10 <diablo_rojo> smcginnis: Yeah sure.
16:08:17 <diablo_rojo> #link The Women of OpenStack are looking for mentors. Technical and Career both. If you are interested, here is the link:  https://docs.google.com/forms/d/1YQITea0ygvusZAeRdR6jL1VUfaNcZTCr2UqHTFSsxR4/viewform?c=0&w=1
16:08:18 <smcginnis> diablo_rojo: OK, hold a sec.
16:08:26 <smcginnis> diablo_rojo: Sorry. :)
16:08:31 <diablo_rojo> smcginnis: No worries :0
16:08:32 <Swanson> hello
16:08:34 <diablo_rojo> :)
16:08:38 <smcginnis> johnthetubaguy: Looking up the time difference now.
16:08:46 <rhedlind> 5 hours
16:08:47 <mriedem> we could sort out that time thing after the meeting...
16:08:54 <mriedem> doens't take 500 people to sort that out
16:09:09 <scottda> johnthetubaguy: I wanted to address the lack of items to discuss with NOva. This is on today's agenda. So let's wait a bit on setting time...
16:09:10 <smcginnis> mriedem: Just a quick look, but yeah.
16:09:31 <smcginnis> johnthetubaguy: Probably do something like 9 AM EST then. But we can sort that out later I guess.
16:09:34 <mriedem> it's 4pm in bristol at 11am in RTP
16:09:43 <smcginnis> johnthetubaguy: Don't want to make you guys stay late.
16:09:45 <mriedem> yeah, so 9am RTP and 2 pm bristol
16:09:59 <johnthetubaguy> yeah, that works
16:10:02 <johnthetubaguy> lets do that
16:10:03 <smcginnis> OK, tentative schedule 9am/2pm.
16:10:11 <smcginnis> johnthetubaguy: Perfect. Thanks John.
16:10:16 <mriedem> ahem
16:10:34 <smcginnis> diablo_rojo: OK, sorry. Please go ahead.
16:10:54 <diablo_rojo> Cool. As I was saying :) The Women of OpenStack are looking to build up the community and help newcomers get more integrated. So if you are interested please fill out the google form.
16:11:10 <diablo_rojo> #link Mentor sign up  https://docs.google.com/forms/d/1YQITea0ygvusZAeRdR6jL1VUfaNcZTCr2UqHTFSsxR4/viewform?c=0&w=1
16:11:23 <smcginnis> diablo_rojo: Day before the summit official starts?
16:11:40 <hemna> anyone can mentor?
16:11:44 <thingee> hemna: yes
16:11:52 <smcginnis> hemna: Not you though. :P
16:11:54 <smcginnis> jk
16:11:56 <hemna> :)
16:12:04 <hemna> lead by bad example!
16:12:09 <smcginnis> hah
16:12:23 <hemna> speaking of pub crawls....
16:12:26 <diablo_rojo> Other things from the cross project meeting, Cinder will need to choose an API liason
16:12:32 <jungleboyj> hemna: +2
16:12:41 <diablo_rojo> other wise it will default to our fearless leader smcginnis :)
16:12:54 <thingee> https://review.openstack.org/#/c/266072/
16:13:05 <smcginnis> I'm OK with it, but if someone is interested in doing it that would be great.
16:13:21 <diablo_rojo> There has been a little bit of discussion in the ML about it
16:13:28 <diablo_rojo> #link http://lists.openstack.org/pipermail/openstack-dev/2016-January/083927.html
16:13:28 <smcginnis> #link Cross project spec team https://review.openstack.org/#/c/266072/
16:14:11 <smcginnis> diablo_rojo: Cool, anything else to cover?
16:14:16 <diablo_rojo> Yes
16:14:18 <diablo_rojo> sorry
16:14:23 <diablo_rojo> lots of links
16:14:42 <diablo_rojo> There are three notable specs that are out there right now that should get checked out:
16:14:50 <diablo_rojo> https://review.openstack.org/#/c/243348/  https://review.openstack.org/#/c/236712/  https://review.openstack.org/#/c/226157/
16:15:03 <diablo_rojo> Thanks thingee for pointing them out :)
16:15:24 <diablo_rojo> So if cores could go take a look at those at some point and review, that would be most helpful.
16:15:45 <thingee> the first deprecates our cli in favor of openstack client
16:15:48 <smcginnis> Yeah, all of those could use some feedback and at least broader awareness.
16:16:02 <thingee> which is something that has been agreed on at previous summits I believe in cross-project sessions that is
16:16:25 <hemna> oofa
16:16:32 <smcginnis> OK, folks take a look.
16:16:35 <thingee> I would say the last one more applies to people here, which is talking about our backwards compatibility for libraries
16:16:38 <thingee> hemna: ^
16:16:44 <hemna> so that's cool, but that also means we are going to have to start working on 2 clients at the same time.
16:16:47 <hemna> fwiw
16:16:59 <jungleboyj> Oy
16:17:01 <hemna> features, fixes, etc
16:17:15 <thingee> shouldn't do new features to the old cli
16:17:17 <mriedem> right
16:17:21 <mriedem> only python API fixes
16:17:30 <smcginnis> I'm sure we could talk about these three the whole hour, so I'm going to move on. ;)
16:17:33 <smcginnis> diablo_rojo: Anything else?
16:17:34 <mriedem> b/c nova still uses the cinderclient python api
16:17:38 <thingee> smcginnis: yes please
16:17:41 <diablo_rojo> One more thing :)
16:17:45 <hemna> yah, we can't just stop working on cinderclient
16:17:48 <hemna> that's not going to work
16:17:51 * thingee puts on top hat and tap dances off stage
16:17:56 <smcginnis> :)
16:18:12 <hemna> mriedem, horizon also
16:18:29 <diablo_rojo> There are still more details to come, but there will be a Hackathon on Feb 29th and basically what is being asked is just that we compile a list of bugs for people to take a look at and then review things as quickly as possible.
16:18:40 <smcginnis> Oh yeah!
16:18:45 <smcginnis> I wanted to make sure to mention that.
16:18:57 <diablo_rojo> smcginnis: And no we can't just give the whole list of bugs ;)
16:18:58 <smcginnis> Kind of a global bug day.
16:19:06 <smcginnis> diablo_rojo: Aww man
16:19:16 <diablo_rojo> smcginnis:  Right, it came out of the China Hackathon?
16:19:28 <smcginnis> I believe so, led by Huawei.
16:19:37 <diablo_rojo> smcginnis: Yes, that sounds right.
16:19:51 <smcginnis> So if anyone is interested in doing some quick bug skimming...
16:19:51 <winston-d> I heard it was 2nd March ~ 4th March.
16:20:03 <patrickeast> Any links or anything for it?
16:20:56 <smcginnis> If anyone can scan through the bugs and start tagging ones that look like good candidates, that would be great.
16:20:56 <diablo_rojo> No links yet, I can go back through the logs and see who was working on organizing it though.
16:20:56 <smcginnis> winston-d: That sounds right.
16:20:56 <diablo_rojo> patrickeast: Just more of a general heads up right now, but I will send you stuff when I find it :)
16:21:05 <smcginnis> OK, we better get moving.
16:21:13 <diablo_rojo> Okay, now I'm done :)
16:21:16 <smcginnis> #topic Virtual Meeting with Nova during mid-cycle
16:21:22 <jungleboyj> We can maybe spend a little time at the mid-cycle organizing bugs for that?
16:21:24 <scottda> Hi
16:21:24 <smcginnis> scottda: Hey
16:21:31 <smcginnis> jungleboyj: Good idea!
16:21:40 * jungleboyj adds it to the agenda
16:21:45 <scottda> So, as mentioned above, we've a virtual meeting with Nova during the mid-cycle scheduled.
16:22:09 <scottda> But, so far, there is nothing on our mid-cycle etherpad that merits a cross-service discussion.
16:22:23 <mriedem> nova has things
16:22:30 <scottda> I'm thinking we should have some concrete items on the agenda that need to be discussed.
16:22:37 <scottda> mriedem: OK. multi-attach?
16:22:38 * jungleboyj has an item to add
16:22:41 <mriedem> https://etherpad.openstack.org/p/mitaka-nova-midcycle
16:22:45 <mriedem> see the cinder section in there
16:22:54 <mriedem> mostly right now it's privsep in os-brick and multiattach
16:23:05 <smcginnis> scottda: The few topics we do have on the etherpad are mostly nova related.
16:23:11 <mriedem> L47
16:23:17 <scottda> Cool. I'm just trying to get folks to think about this and put them on the agenda
16:23:24 <smcginnis> #link nova midcycle https://etherpad.openstack.org/p/mitaka-nova-midcycle
16:23:34 <flip214> scottda: the DRBD transport touches both Cinder and Nova... Is that a point to discuss, or is that too small a detail?
16:23:34 <smcginnis> #link cinder midcycle https://etherpad.openstack.org/p/mitaka-cinder-midcycle
16:24:06 <scottda> It's worth discussing things that require agreement, or sharing of info, or are contentious
16:24:15 <hemna> so I spoke with gus last week about privsep and he was blocked
16:24:35 <hemna> I think I was able to help him move forward at least in theory with privsep -> os-brick
16:24:41 <flip214> well, "agreement" as in +2, yeah ;)
16:25:06 <scottda> So I'd like to firm up an agenda next week so we are prepared to use the time wisely
16:25:15 <smcginnis> scottda: +1
16:25:18 <hemna> but I still think it will be a miracle to get privsep full implemented for os-brick in M.
16:25:25 <scottda> that's it. We can move on.
16:25:38 <smcginnis> hemna: I will be very surprised if it does. :{
16:25:41 <smcginnis> scottda: Thanks!
16:25:43 <e0ne> hemna: please, ping me if you need any help on this
16:25:54 <smcginnis> #topic Nested Quota enforcement issue
16:25:59 <smcginnis> mc_nair: Hey
16:26:02 <mc_nair> hey
16:26:11 <mc_nair> while looking into https://bugs.launchpad.net/cinder/+bug/1531502, we noticed that we can't actually enforce child default quota values because we can't grab parent_project_id as part of something like the create volume flow (because user may not be an admin)
16:26:12 <openstack> Launchpad bug 1531502 in Cinder "Child project's default quota not enforced" [High,New] - Assigned to Ryan McNair (rdmcnair)
16:26:26 <mc_nair> I talked with raildo and we were thinking of listening for the keystone project create event notification and explicitly creating a cinder quota for the new project at that point
16:26:44 <mc_nair> if anyone has feedback on the suggested approach / comments about the problem it’d be much appreciated
16:27:02 <dulek> mc_nair: Do we have parent_project_id in the context?
16:27:03 <raildo> hey :)
16:27:09 <hemna> rm -rf quotas
16:27:13 <mc_nair> dulek: no, we don't
16:27:15 <e0ne> :)
16:27:19 <DuncanT> mc_nair: Too fragile - events can get lost
16:27:37 <dulek> mc_nair: Shouldn't it be there?
16:27:39 <mc_nair> DuncanT: that's what I was worried about, so that's good to know
16:27:43 <DuncanT> mc_nair: This whole nested quotas thing has been a disaster, I'd honestly be tempted to say pull it and rethink
16:27:44 <smcginnis> Yeah, seems like there's got to be a better way.
16:27:48 <raildo> dulek: no, we have a token size issue, and for now, we can't add more information directly on the context.
16:28:05 <eharney> yeah, the event notification idea doesn't sound like the right route
16:28:27 <mc_nair> good to know
16:28:28 <DuncanT> Event notification, even if it was reliable, is still racy. Nak
16:29:16 <smcginnis> Anyone know a route mc_nair can look in to for this?
16:29:24 <mc_nair> so then if we're not able to add parent_project_id to the token I guess we're stuck with busted child quota default vals until we rethink things?
16:29:34 <smcginnis> Or should we add this as a topic to the midcycle to rethink nested quotas?
16:29:35 <dulek> mc_nair: Isn't Nova implementing nested quotas in this release?
16:29:50 <mc_nair> dulek: yea, but they're going to hit the same problem with their current approach
16:29:51 <jungleboyj> mc_nair: Have we verified that it isn't agreeable to add the parent_project_id to the token?
16:29:54 <dulek> Or any other project? We probably share same problems.
16:30:01 <raildo> dulek: we have some patches, very similar with the cinder implementation, it is in code review
16:30:02 <dulek> mc_nair: So -1 the approach. ;)
16:30:38 <mc_nair> jungleboyj: well raildo was saying there's a limit to the info you can add to the token and right now Keystone won't let anything else be added to it
16:30:46 <mc_nair> dulek: will do :)
16:30:46 <raildo> we can try talk with the keystone guys, to explain why we need the parent_id on the token, and maybe we can propose it
16:30:52 <jungleboyj> mc_nair: Boooo.
16:30:59 <jungleboyj> mc_nair: Ok, thanks for chasing that idea.
16:31:01 <DuncanT> smcginnis: I think adding it to the midcycle agenda is worthwhile, it's currently a mess, and shouldn't, in hindsight, have been merged as is
16:31:23 <smcginnis> DuncanT: It does sound like it could use some more discussion at least.
16:31:29 <smcginnis> I'll add that.
16:31:41 <DuncanT> mc_nair: Or just let a normal user get their parent project id from keystone, and we'll ask keystone when we need it
16:32:07 <DuncanT> mc_nair: The status quo of needing admin is daft
16:32:14 <dulek> DuncanT: +1
16:32:25 <jungleboyj> smcginnis: +2 Thanks.  This is high priority for us to get addressed.
16:32:38 <DuncanT> mc_nair: We do have the concept of a service user that could probably be used, but that feels ugly
16:33:07 <raildo> DuncanT: ++ I think that use the service user would be easier to fix the problem
16:33:11 <mc_nair> DuncanT: alright, yea will chase that as well.  Letting non-admin retrieve parent would work assuming we could work that through keystone
16:33:36 <smcginnis> mc_nair: Awesome. Enough to go on for now?
16:33:48 <mc_nair> smcginnis: yes sir - thanks for the info everyone
16:33:52 <smcginnis> mc_nair: Thanks!
16:33:54 <DuncanT> mc_nair: Adding it to the token removes the need for an extra callout to keystone though, so would be very preferable
16:33:59 <smcginnis> #topic Summary Messages to be displayed for success/failure in cinder operations
16:34:04 <smcginnis> sheel: You're up.
16:34:13 <sheel> smcginnis:yes
16:34:16 <sheel> i am there
16:34:32 <sheel> hi everyone
16:34:36 <sheel> Its regarding https://blueprints.launchpad.net/cinder/+spec/summarymessage
16:34:48 <sheel> where i am propsing to display error messages in details atleast to admin
16:35:04 <sheel> When someone performs some operation like create volume, delete volume etc, if operation fails - user gets no specific information about why operation failed...just operation status is updated and shown as failed... One need to debug logs and other details to find the issue.
16:35:10 <eharney> i feel like this needs to be tied into the async error reporting proposal that's been floating for a while now
16:35:27 <jungleboyj> eharney: ++
16:35:30 <eharney> the overall idea is right, but we've already looked into this a bit
16:35:34 <DuncanT> eharney: ++
16:35:35 <smcginnis> eharney: Is there a spec out there for that, or has that just been talked about?
16:35:41 <eharney> i think discussion about that is listed for the midcycle
16:35:45 <eharney> smcginnis: there was a spec a while ago
16:35:50 <eharney> not sure there has been an active one recently
16:36:11 <eharney> but it's a feature i'm quite interested in getting, so maybe we'll figure out at the midcycle what needs to happen to get that rolling again
16:36:34 <smcginnis> eharney: This seems like a cross project thing.
16:36:39 <smcginnis> Not that cinder can't lead it.
16:36:44 <eharney> ehh
16:36:53 <jungleboyj> smcginnis: That has been discussed in the cross project meetings before.
16:36:59 <eharney> the discussion started going that way before, i think, and we ended up kinda fizzling out and not doing anything
16:37:05 <eharney> IMO we need to just implement it and then see where it goes
16:37:16 <smcginnis> eharney: Fair point. :)
16:37:29 <eharney> because it's not something that couldn't be spread and adapted over time to other projects
16:37:38 <johnthetubaguy> Nova has "instance actions" to help report async errors, if that helps?
16:37:41 <smcginnis> Might be good to get something in cinder, then use that as an example for other projects that need to do async error reporting.
16:37:52 <johnthetubaguy> but thats a REST API, rather than an async API
16:37:58 <jungleboyj> eharney: Yeah, we need to do something.  :-)
16:38:01 <DuncanT> johnthetubaguy: That just shows the last error though, doesn't it?
16:38:18 <johnthetubaguy> DuncanT: no, shows previous actions, and there previous errors, based on request-id, I believe
16:38:35 <DuncanT> johnthetubaguy: Ah, ok, thanks, I'll go look
16:38:41 <smcginnis> johnthetubaguy: Sounds like what we need. Thanks!
16:39:00 <johnthetubaguy> so it does have some issues we keep wanting to fix
16:39:09 <johnthetubaguy> it doesn't really tell the users when something is finished
16:39:10 <johnthetubaguy> http://developer.openstack.org/api-ref-compute-v2.1.html#os-instance-actions-v2.1
16:39:30 <smcginnis> sheel: So something to look into ^^
16:39:37 <johnthetubaguy> but, yeah, it might help with ideas
16:39:41 <sheel> smcginnis : sure, i will follow up
16:39:47 <eharney> i'll be sure it's listed for the midcycle, ameade was on the list to attend i think, so we can kick things off there
16:39:49 <johnthetubaguy> alaski is a good contact to chat with about that
16:40:10 <mtanino> https://etherpad.openstack.org/p/kilo-cinder-async-reporting this one?
16:40:14 <smcginnis> johnthetubaguy: If we can all work on one pattern that would be good.
16:40:21 <hemna> smcginnis, +1
16:40:27 <ameade> o/
16:40:28 <ameade> lol
16:40:34 <ameade> in the manila midcycle atm
16:40:36 <eharney> mtanino: yes
16:40:52 <johnthetubaguy> smcginnis: +1 something for the API WG guidlines
16:41:21 <smcginnis> #link Past discussion https://etherpad.openstack.org/p/kilo-cinder-async-reporting
16:41:21 <erlon> ameade: where did it got? I mean why it didn't go further?
16:41:28 <ameade> i can share my thoughts around async error reporting
16:41:34 <smcginnis> #link Nova approach http://developer.openstack.org/api-ref-compute-v2.1.html#os-instance-actions-v2.1
16:41:40 <ameade> erlon: nobody implemented it, I haven't had the bandwidth
16:41:49 <erlon> ameade: hmm
16:41:53 <ameade> i think it's the single most important feature of openstack atm
16:41:57 <ameade> for*
16:42:09 <erlon> sheel: :)
16:42:29 <sheel> erlon: so I can take this BP ahead
16:42:51 <sheel> smcginnis : right?
16:43:14 <erlon> sheel: +1
16:43:23 <smcginnis> sheel: That would be great! We could definitely use this.
16:43:34 <smcginnis> sheel: Anything else at the moment?
16:43:36 <eharney> i'll see what kind of bandwidth exists here to help on this, i'd like to if i can
16:43:42 <ameade> lets talk about it at the midcycle, i will be there
16:43:47 <smcginnis> ameade: +1
16:43:48 <eharney> ameade: yes
16:43:51 <ameade> would love for folks to commit to working on it
16:43:53 <sheel> smcginnis : thank you, please approve BP
16:44:07 <smcginnis> sheel: Will do. :)
16:44:15 <sheel> eharney: sure, we will work together...
16:44:26 <smcginnis> #topic Open Discussion
16:44:28 <sheel> eharney : thanks for extended help and your interest
16:44:31 <erlon> o/
16:44:36 <smcginnis> Vincent put an item on the agenda, but he's not here.
16:44:38 <erlon> Just one thing I'd like to raise. We need some help to review this (Hitachi) driver, to make it ready for M2.
16:44:43 <mtanino> sheel: I'm interested in this too :)
16:44:45 <smcginnis> I'll just say, congrats Vincent.
16:44:47 <smcginnis> :)
16:44:50 <erlon> https://review.openstack.org/#/c/255239/
16:45:03 <sheel> mtanino: sure
16:45:20 <smcginnis> erlon: You want to talk about that one?
16:45:45 <erlon> smcginnis: you gave a quick review, if you have a change and review it trougly
16:45:56 <smcginnis> erlon: Will do.
16:45:58 * jungleboyj laughing
16:46:06 <jungleboyj> Hadn't seen that he put that on the agenda.
16:46:16 <smcginnis> jungleboyj: Pretty funny. :)
16:46:24 <jungleboyj> Yeah, Vincent is now in RTP and is very excited to be in the US time zone and able to work in real time.
16:46:25 <mtanino> oh! congrat Vincent.
16:46:27 <erlon> smcginnis: so, its a refactory, big,  but need more core reviews
16:46:33 <smcginnis> erlon: That blueprint was a little misleading that it doesn't really call out there is a new driver as part of that.
16:46:38 <eharney> welcome to the area Vincent :)
16:46:46 <sheel> congrats Vincent. :)
16:46:49 <jungleboyj> He will be at the midcycle and be able to get back on the Storwize patches.
16:46:56 <claudiub> hi. just a small request. If you could review the cinder windows drivers refactor with os-win patch, I'd greatly appreciate it. :) https://review.openstack.org/#/c/243565/10
16:47:10 <kmartin> erlon, the Hitachi HBSD2 CI is failing on it
16:47:17 <smcginnis> claudiub: Tab opened...
16:47:22 <claudiub> it would be great if it could make it into M-2. :)
16:47:22 <eharney> claudiub: i've had that one on my radar, will try to take a look soon
16:47:34 <flip214> I would like to ask for a bit of review bandwidth for the DRBD transport - if the Cinder side was merged, I think it's easier to get the Nova side in. https://review.openstack.org/#/c/259973/9
16:47:35 <patrickeast> oh, i have something to bring up
16:47:39 <erlon> kmartin: yes, we are working on it, but folks can still review while we get that stable
16:47:41 <claudiub> great, thanks folks. :)
16:47:42 <flip214> (Even if that is just a copy of an existing driver)
16:47:43 <patrickeast> is there any interest in turning on the image cache for the cinder gate w/ lvm?
16:48:08 <smcginnis> patrickeast: Seems like we should for coverage.
16:48:11 <smcginnis> IMO
16:48:14 <patrickeast> yea
16:48:19 <eharney> patrickeast: probably good in some capacity, but i assume we'd need jobs with and without it?
16:48:32 <jungleboyj> patrickeast: Seems like a good idea.
16:48:33 <patrickeast> i turned it on in the pure ci after it got broken from some object changes
16:48:39 <patrickeast> eharney: yea probably
16:48:44 <smcginnis> eharney: Before it's cached it will be without it, right? So we kind of get coverage for both?
16:49:04 <patrickeast> smcginnis: true, but the code paths are a tiny bit different
16:49:11 <smcginnis> patrickeast: True
16:49:16 <eharney> smcginnis: i dunno, just thinking about rooting out issues related to glance interaction etc
16:49:24 <patrickeast> imo its probably better with it turned on vs turned off as far as total coverage of code
16:49:24 <smcginnis> eharney: Yeah, fair point.
16:49:26 <patrickeast> but still a gap
16:49:35 * smcginnis tends to cut corners on testing
16:49:40 <smcginnis> :}
16:49:54 <jungleboyj> smcginnis: Should strike that from the record.
16:50:09 <eharney> we could do something like turn it on for the LIO/thin job and leave it on for the tgt/thick job, since that split already exists
16:50:10 <smcginnis> jungleboyj: Yeah, I probably should have stated that. :D
16:50:12 <eharney> not sure
16:50:33 <jungleboyj> Oh no, followed by a Freudian Slip!
16:50:39 * smcginnis tends to look for ways to safely cut corners on testing
16:50:50 <smcginnis> jungleboyj: How's that> ^^ :)
16:50:52 <eharney> leave it off*
16:51:13 <patrickeast> so maybe for now i'll put something on my backlog to get the devstack changes or plugin pulled into the official repos so we could turn it on
16:51:18 <smcginnis> eharney: That seems reasonable.
16:51:19 <patrickeast> and once thats ready we can figure out where to enable it
16:51:31 <smcginnis> patrickeast: That would be awesome.
16:51:41 <eharney> patrickeast: sounds good
16:52:07 <smcginnis> 8 minutes
16:52:14 <smcginnis> Any other topics to cover?
16:52:16 <jungleboyj> eharney: Sounds like a good plan.
16:52:31 <diablo_rojo> patrickeast: Looks like nikhil is the primary contact for information thus far for the Hackathon. Looks like jroll and rockyg may also have info on it maybe.
16:52:44 <patrickeast> diablo_rojo: cool, thanks!
16:52:51 <diablo_rojo> patrickeast: No problem :)
16:52:59 <jungleboyj> Just FYI, I think we are looking at doing Thunderbirds for dinner on Thursday night.
16:53:14 <smcginnis> Oh, some specs could use some reviews. Too late for many, but I think there are a few that could still make it in M.
16:53:28 <diablo_rojo> jungleboyj: Should I add that to the etherpad?
16:53:41 <jungleboyj> diablo_rojo: Sure.  That would be good.
16:54:32 <smcginnis> Wednesday is still open for any companie that want to bribe^D^D^D^D^Dfeed us.
16:54:45 <jungleboyj> bwah ha ha!
16:54:53 <smcginnis> Totally joking
16:55:11 <Swanson> smcginnis, technically I think I have to report you to the dell ethics committee.
16:55:13 <kmartin> can PTLs be impeached?
16:55:18 <smcginnis> Hahah
16:55:27 <flip214> smcginnis: careful with the mushroom food.
16:55:27 <scottda> Too bad Dell just spent all their money...
16:55:29 <smcginnis> I'm getting myself in all kinds of trouble today. :)
16:55:42 <sheel> smcginnis: sorry to cut into
16:55:45 <smcginnis> scottda: Hah!
16:55:47 <diablo_rojo> scottda: +1
16:55:50 <smcginnis> sheel: Please do.
16:55:53 <sheel> smcginnis: could you please review https://review.openstack.org/#/c/265820/
16:56:05 <sheel> final +2 left for merge
16:56:16 <sheel> sorry, I know you have already got too many requests :(
16:56:28 <Swanson> scottda, Dell spent ALL the money.
16:56:40 <smcginnis> sheel: Will take a look.
16:56:44 <eharney> sheel: i'll review that one, i started on it the other day
16:56:52 <eharney> something about it looked odd to me, need to check it
16:56:55 <smcginnis> OK, I think we past the point of any productivity a while back Thanks everyone.
16:56:58 <sheel> eharney : thats great.. thank you very much
16:57:04 <rhedlind> question. I have some changes to make to my driver still. what's the deadline to get them into gerrit? do we have that on a page somewhere?
16:57:11 <sheel> smcginnis: thank you
16:57:18 <jungleboyj> Good meeting.  Thanks everyone!
16:57:30 <smcginnis> rhedlind: M-3 for changes.
16:57:33 <smcginnis> #endmeeting