16:00:06 <smcginnis> #startmeeting Cinder
16:00:06 <openstack> Meeting started Wed Mar 29 16:00:06 2017 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:07 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:09 <openstack> The meeting name has been set to 'cinder'
16:00:15 <smcginnis> dulek duncant eharney geguileo winston-d e0ne jungleboyj jgriffith thingee smcginnis hemna xyang1 tbarron scottda erlon rhedlind jbernard _alastor_ bluex karthikp_ 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 watanabe.isao,tommylikehu mdovgal ildikov wxy
16:00:19 <e0ne> hi
16:00:20 <mdovgal> hi
16:00:21 <smcginnis> viks ketonne abishop sivn breitz
16:00:23 <jungleboyj> o/
16:00:23 <tommylikehu_> hello
16:00:24 <smcginnis> Hey everyone
16:00:24 <rajinir> o/
16:00:29 <tbarron> hi
16:00:29 <wxy|> hello
16:00:31 <viks> o/
16:00:35 <bluex> hi
16:00:36 <xyang2> hi
16:00:36 <geguileo> hi!
16:00:37 <patrickeast> Hi
16:00:48 <paul-andreraymon> quit
16:01:09 <diablo_rojo> Hello :)
16:01:09 <smcginnis> #topic Announcements
16:01:17 <smcginnis> #link https://etherpad.openstack.org/p/cinder-spec-review-tracking Review focus
16:01:20 <rarora> hi
16:01:46 <smcginnis> I've made a pass through the new drivers. Most are not ready, but some are really close. I think the Veritas one was almost there.
16:01:53 <smcginnis> So some attention on those would be great.
16:01:53 <kaisers_> Hi
16:02:04 <smcginnis> #link http://lists.openstack.org/pipermail/openstack-dev/2017-March/114656.html Bugsmash info
16:02:15 <smcginnis> There is another bugsmash event announced.
16:02:21 <viks> :)
16:02:28 <smcginnis> I was able to attend last time and thought it was very useful.
16:02:37 <tommylikehu_> +1
16:02:43 <smcginnis> Would be great if we can get some core attention on those reviews.
16:02:52 <smcginnis> I know it would really help.
16:03:09 <diablo_rojo> smcginnis, what are our bug stats?
16:03:23 <smcginnis> diablo_rojo: We have bugs. :P
16:03:32 <smcginnis> http://cinderstats-dellstorage.rhcloud.com/
16:03:38 <diablo_rojo> smcginnis, lol and here I thought we were perfect
16:03:42 <smcginnis> ;)
16:03:52 <smcginnis> Some bug info in that link ^
16:04:04 <smcginnis> I really should take a pass through cleaning up in launchpad again.
16:04:16 <tommylikehu_> btw, suzhou city is a best place if anyone would like to get to know the chinese traditional architecture :)
16:04:20 <jungleboyj> smcginnis:  Will there be a way to know which patches are coming out of the bug smash?
16:04:29 <bswartz> .o/
16:04:30 <jungleboyj> smcginnis: So we can help out there if we aren't at the event?
16:04:41 <_alastor_> o/
16:04:46 <smcginnis> jungleboyj: There is an etherpad we can post that shows what's being worked on.
16:04:50 <diablo_rojo> We could make a list of things we want people to look at/work on. I think we have done that before?
16:05:10 <smcginnis> diablo_rojo: That would be useful!
16:05:17 <smcginnis> And a great way to focus some attention.
16:05:35 <smcginnis> There will be more info as it gets closer, but just wanted to mention the event here.
16:05:42 <jungleboyj> Sounds like a good idea.  Have anyone willing to put that together?
16:06:03 <diablo_rojo> jungleboyj, could do it at the forum
16:06:07 <diablo_rojo> since the event is after that
16:06:14 <smcginnis> Don't need any responses immediately, but it would be great if we had a docs liason.
16:06:17 <jungleboyj> diablo_rojo:  ++  Good idea.
16:06:27 <smcginnis> That's defaulted to me, but honestly I've been doing a crap job of it.
16:06:40 <diablo_rojo> jungleboyj, thanks :)
16:06:44 <jungleboyj> smcginnis: I was wondering about that the other day.
16:06:50 <smcginnis> Just need someone to attend (or read the logs) of the docs meetings and make sure we are aware of doc needs for Cinder.
16:07:15 <smcginnis> Stable/Newton branch moves to security only fixes April 6
16:07:23 <jungleboyj> If you are over worked there smcginnis  I can try to take it on.  Lets talk later.
16:07:38 <smcginnis> jungleboyj: Yep, later's good.
16:08:05 <smcginnis> With the change from the 6 month cadence with Ocata, that made Newton go a little beyond the new release.
16:08:13 <diablo_rojo> jungleboyj, I think we are all a little overworked ;)
16:08:22 <smcginnis> That now will be changing to the more resticted backport phase.
16:08:46 <smcginnis> So just an FYI in case you had anything you wanted to backport. Now's the time.
16:09:04 <smcginnis> And hopefully one final announcement - I'll be on vacation next week.
16:09:12 <tommylikehu_> how long
16:09:16 <diablo_rojo> smcginnis, have fun in Japan :)
16:09:18 <smcginnis> I'll likely check in from time to time, but I will definitely not be around as much as usual.
16:09:29 <viks> :O
16:09:35 <smcginnis> I should be back online by the 10th.
16:09:37 <jungleboyj> If people need help getting stable backports through, let me know.
16:09:51 <tommylikehu_> thanks, jungleboyj
16:09:54 <smcginnis> Though probably busy on other things for a little bit at the beginning of that week.
16:09:58 <bswartz> +1 for vacations
16:10:03 <jungleboyj> tommylikehu_:  No problem.
16:10:04 <smcginnis> ;)
16:10:11 <smcginnis> OK...
16:10:14 <jungleboyj> I will also be out but planning to check in from time to time.
16:10:20 <smcginnis> #topic Using exception in 'user message'
16:10:24 <smcginnis> tommylikehu_: All yours
16:10:31 <tommylikehu_> thanks
16:10:32 <smcginnis> #link https://review.openstack.org/#/c/448384/
16:10:41 <tommylikehu_> I had this idea when I try to add more useage of user messages. I found it a little unclean to add more async task error details
16:11:04 <tommylikehu_> this is the initial patch when I add more use messages
16:11:05 <tommylikehu_> https://review.openstack.org/#/c/447975/1/cinder/volume/manager.py
16:11:30 <tommylikehu_> I think we try to get more detail error messages with detecting the exception type
16:11:57 <smcginnis> So the one thing I don't like about this is these user messages are meant for users.
16:12:12 <smcginnis> And exceptions have internal detail that really should not be shown to users.
16:12:22 <smcginnis> But I like the idea of getting more detail in the user messages.
16:12:41 <eharney> isn't this just generating more specific messages based on which exception, but not passing exception info to the user?
16:12:42 <tommylikehu_> we can fix this by building the relationship from exception to uesr messages
16:12:59 <tommylikehu_> eharney: yes
16:13:05 <e0ne> smcginnis: +1, good point
16:13:09 <tommylikehu_> https://review.openstack.org/#/c/448384/
16:13:20 <smcginnis> OK, in that case I think it's good. Just don't want tracebacks in end user messages.
16:13:34 * smcginnis needs to review the patch yet so should probably shut up
16:13:55 <tommylikehu_> this idea has a disadvantage that we could lose the message ids
16:14:41 <jungleboyj> smcginnis:  +2 .  But I think tommylikehu_  is headed in the right direction trying to get users a better idea of what has happened with an exception.
16:15:25 <smcginnis> +1
16:15:36 <smcginnis> I think we want the message IDs though.
16:16:06 <jungleboyj> smcginnis:  How are those used?
16:16:10 <eharney> want them where?
16:16:20 <smcginnis> Returned
16:16:21 <tommylikehu_> smcginnis: there is another solution that we can keep the relationship from exception class to message ids
16:16:39 <eharney> you don't have to return them, you can query for messages related to the object (snapshot id)
16:16:41 <smcginnis> I think the plan was to have the message IDs be useful in being able to google the ID to get more info.
16:17:23 <smcginnis> ameade: I don't suppose you are around?
16:17:40 <tommylikehu_> upper user could take advantage of these message ids
16:18:05 <tommylikehu_> to track what exactly happened during the async tasks
16:18:09 <xyang2> I thought the original proposal was to eventually show the messages in horizon
16:18:19 <smcginnis> tommylikehu_: Thanks, I'll take a look through that so I stop making assumptions. :)
16:18:20 <eharney> xyang2: that is being worked on
16:18:28 <xyang2> eharney: ok
16:18:42 <tommylikehu_> smcginnis: ok
16:18:51 <eharney> at any rate, just firing a message like this code does and doing nothing else is a large improvement
16:18:55 <jungleboyj> smcginnis: Oh, IBM had added those internally.  Yeah, if we had them documented and googleable, that would be good.
16:18:58 <smcginnis> tommylikehu_: Thanks for bringing it up here.
16:19:20 <smcginnis> tommylikehu_: Anything else we should discuss? Or just need people to review?
16:19:38 <tommylikehu_> smcginnis: yes, gather more reviews
16:19:40 <tommylikehu_> :)
16:19:45 <smcginnis> tommylikehu_: OK, thanks!
16:19:48 * eharney is glad to see work continuing in this area
16:19:52 <smcginnis> #topic Veritas HyperScale cinder driver update
16:19:54 <tommylikehu_> and hope we could decide which way to go
16:19:55 <smcginnis> eharney: Me too.
16:19:56 <jungleboyj> eharney:  Agreed.
16:19:59 <viks> ih
16:20:04 <smcginnis> viks: Hey
16:20:09 <viks> is running stable http://ci-watch.tintri.com/project?project=cinder
16:20:24 <viks> all the review comments till date are addressed https://review.openstack.org/#/c/382097/
16:20:38 <viks> :)
16:20:47 <viks> suggest next actions
16:20:50 <viks> also
16:21:01 <viks> Seeking some attension on review of our OS-brick at:https://review.openstack.org/#/c/442754/
16:21:10 <viks> We have started work on CI for OS-brick, just wanted to know if CI a gating factor for os-brick?
16:21:27 <viks> hushh...
16:22:05 <e0ne> viks: I'll review both of them tomorrow
16:22:14 <viks> great :)
16:22:29 <smcginnis> viks: We strongly encourage CI on os-brick if you have a connector there. But we have not enforced a strict policy on it.
16:22:32 <smcginnis> Yet.
16:22:34 <jungleboyj> viks: I will take a look as well.
16:23:10 <viks> if reviews are done and addressed with running CI...we will try for Pike 1 milestone :)
16:23:27 <smcginnis> viks: Seems like it's on a good track to be able to get in by then.
16:23:30 <viks> Thanks smcginnis :)
16:23:42 <jungleboyj> :-)
16:23:42 <viks> :)
16:23:51 <jungleboyj> Look at all the smiling people.
16:23:55 <smcginnis> #topic Open discussion
16:23:56 <smcginnis> :)
16:23:56 <viks> thanks jungleboys
16:24:05 <smcginnis> Anything else?
16:24:17 <wxy|> about https://review.openstack.org/#/c/444734/ I want to know if it's in the right direction.
16:24:19 <eharney> i broke the LIO CI job yesterday, i have a patch up to try to fix it now
16:24:20 <smcginnis> We have over 30 minutes to bike shed on something. :)
16:24:26 <wxy|> do we need it?
16:24:34 <eharney> it should be testing w/ barbican once that works
16:24:35 <smcginnis> eharney: Link?
16:24:51 <eharney> smcginnis: https://review.openstack.org/#/c/451443/
16:25:13 <smcginnis> eharney: Thanks
16:25:18 <bswartz> obviously the bike shed should be painted white
16:25:27 <smcginnis> :)
16:25:44 <smcginnis> wxy|: I think so. I'll try to take a look this afternoon.
16:25:51 <diablo_rojo> smcginnis, bikeshed on who's going to be at dockercon?
16:26:18 <wxy|> smcginnis: thanks, if so, I'll complete it later.
16:26:44 <Swanson> wxy|, was looking for that the other day. Seems like a good thing to have.
16:26:49 <smcginnis> diablo_rojo: Oh, sure. But that reminds me. Can we get a rough idea of who is actually going to be at the Summit?
16:27:01 <jungleboyj> o/
16:27:05 <bswartz> s/Summit/Forum/
16:27:05 <eharney> o/
16:27:12 <diablo_rojo> \o/
16:27:21 <smcginnis> o/
16:27:22 <blancos> Patrole (#link https://review.openstack.org/#/q/project:openstack/patrole) is an RBAC testing framework within QA. We're currently working on setting up project-specific gates, and we were wondering if Cinder was interested in one
16:27:28 <smcginnis> bswartz: Fine> :P
16:27:42 <_alastor_> o/
16:27:44 <bswartz> don't blame me, I'm not the one who changed the name
16:27:51 <jungleboyj> scottda:  and hemna  as well.
16:28:08 <smcginnis> blancos: Any more background info about what it is?
16:28:13 <kaisers_> Probably o/
16:28:24 <patrickeast> o/
16:28:27 <blancos> smcginnis Sure!
16:28:54 <bluex> Some comments on HA races prevention blueprint would be welcome - https://review.openstack.org/#/c/429947/
16:29:05 <blancos> Basically, we test individual policies from the policy.json (in Cinder's case, although our framework also works with oslo policy checker and code defaults) to make sure that each policy is being enforced correctly
16:29:44 <smcginnis> blancos: Oh nice. Yes, that sounds like it would be a good thing to have for Cinder.
16:30:17 <jungleboyj> smcginnis:  ++
16:30:28 <smcginnis> I know we've had issues there.
16:30:48 <xyang2> o/
16:30:56 <smcginnis> blancos: So are you offering to add a job for Cinder? Or letting us know we can do that if we want? :)
16:31:10 <xyang2> me too
16:31:19 <blancos> smcginnis We're currently gauging interest from the projects we have tests for.
16:31:21 <jungleboyj> xyang2:  You are lagging today.  ;-)
16:31:33 <blancos> smcginnis We'd be happy to add it
16:31:41 <smcginnis> blancos: Well, could us interested. ;)
16:31:43 <smcginnis> blancos: Thanks!
16:31:49 <smcginnis> *count
16:31:57 <xyang2> jungleboy: I couldn't see my typing:)
16:32:11 <blancos> smcginnis Sure. We'll let you know when the gates are ready to go
16:32:15 <jungleboyj> xyang2:  Neither could we.  :-(
16:32:27 <smcginnis> jungleboyj, xyang2: Hah!
16:32:37 <xyang2> :)
16:32:46 <smcginnis> blancos: Cool, will be nice to see what that shows.
16:33:02 <smcginnis> Looks like at least a good core turn out for the Summit/Forum.
16:33:07 <smcginnis> Glad to see that.
16:33:34 <smcginnis> Anyone have anything else?
16:34:14 <smcginnis> OK, thanks everyone!
16:34:20 <jungleboyj> Thanks!
16:34:20 <mdovgal> thank you
16:34:24 <viks> thanks
16:34:25 <diablo_rojo> Thanks smcginnis  :)
16:34:25 <kaisers_> Thanks
16:34:28 <smcginnis> #endmeeting