14:01:14 <flaper87> #startmeeting Glance
14:01:14 <openstack> Meeting started Thu Nov 19 14:01:14 2015 UTC and is due to finish in 60 minutes.  The chair is flaper87. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:15 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:17 <dhellmann> o/
14:01:18 <openstack> The meeting name has been set to 'glance'
14:01:34 <flaper87> welcome everyone
14:01:40 <mfedosin_> o/
14:01:40 <Jokke_> o/
14:01:43 <flaper87> hope you've had a great week since our last meeting!
14:01:46 <mclaren> o/
14:01:50 <rosmaita> o/
14:01:53 <flaper87> #topic Agenda
14:01:59 <abhishekk> o/
14:02:03 <flaper87> #link https://etherpad.openstack.org/p/glance-team-meeting-agenda
14:02:09 <flaper87> That's our agenda for today
14:02:18 <flaper87> It's short, feel free to add more topics at the bottom
14:02:30 <flaper87> #topic Specs recently approved (flaper87)
14:02:38 <flaper87> we've merged 2 specs since our last meeting
14:02:47 <flaper87> #link https://review.openstack.org/#/c/229878/
14:02:55 <flaper87> That's Glance's trusts support
14:03:03 <flaper87> mfedosin_: and kairat are going to work on that
14:03:09 <flaper87> Thank you both!
14:03:12 <flaper87> The patches are up already
14:03:17 <mfedosin_> welcome :)
14:03:19 <flaper87> and those can be reviewed
14:03:26 <flaper87> Remember this should not impact API v1
14:03:32 <flaper87> That was discussed last week
14:03:40 <flaper87> This is a v2 only change
14:03:54 <flaper87> #link https://review.openstack.org/#/c/183363/
14:04:00 <flaper87> That's a cinder driver for glance_store
14:04:12 <flaper87> The proposal is detailed enough to undersand how this would work
14:04:20 <flaper87> I believe the code for this is up already as well
14:04:32 <flaper87> and I'm quite excited about it (hope you're as well)
14:04:32 <flaper87> :D
14:04:39 <flaper87> this has been a long standing request
14:04:44 <Jokke_> ++
14:04:47 <flaper87> Zhi Yan started the work there
14:04:54 <flaper87> and I'm happy that someone is taking this over
14:04:58 <Jokke_> it has been lingering too long in a state that it's not really usable
14:05:02 <flaper87> and that we now have os-brick to implement this properly
14:05:28 <flaper87> There are some bits that could be improved in the future (oslo-rootwrap) but lets not get stuck there for now
14:05:51 <flaper87> We'll have to sync with cinder folks for this and I'd like to thank all the cinder folks that provided reviews there
14:05:58 <flaper87> I'll send an email to -dev about this
14:06:10 <flaper87> We could use extra reviews from them there
14:06:19 <flaper87> anyway, moving on
14:06:31 <flaper87> #topic Recent releases (flaper87)
14:06:43 <flaper87> #link http://docs.openstack.org/developer/python-glanceclient/#id1
14:06:47 <flaper87> That's glanceclient 1.2.0
14:07:10 <flaper87> The release contains quite some enhancements and it also contains a patch required for the work mfedosin_ and sudipto are doing in Nova
14:07:13 <flaper87> (version listing)
14:07:25 <flaper87> #link https://pypi.python.org/pypi/python-glanceclient/0.17.3
14:07:28 <bunting> o/
14:07:39 <flaper87> That's a 0.17.3 release for our stable branches
14:07:51 <flaper87> it contains mostly bugfixes and it caps the required requests version
14:07:54 <Jokke_> stable/kilo to be exact
14:08:00 <flaper87> that fixes an issue that was breaking the gate as well
14:08:01 <flaper87> Jokke_: ++
14:08:19 <flaper87> Jokke_: am I missing something in this topic?
14:08:40 <flaper87> also, thanks to Jokke_ for leading the releases
14:08:48 <flaper87> awesome job!
14:08:54 <Jokke_> I think that's it ... haven't got anyone yet coming to kill us so might be that we didn't break anything tis time around
14:09:03 <flaper87> great!
14:09:14 <flaper87> Keep an eye on gates and mailing list in case something breaks
14:09:21 <Jokke_> ++
14:09:46 <flaper87> if something breaks, before engaging, remember to give that person coffee and muffins to help with the situation
14:09:49 <flaper87> :D
14:09:51 <flaper87> and gummybears
14:09:54 <flaper87> those always work
14:10:01 <flaper87> at least with me
14:10:03 <flaper87> :P
14:10:13 <flaper87> anyway, Jokke_ thanks again
14:10:14 <flaper87> moving on
14:10:19 <flaper87> #topic Glance Bugs/Review squash (flaper87)
14:10:21 * nikhil sneaks in
14:10:35 <flaper87> Last week we mentioned doing a REview/bug squash day
14:10:45 <flaper87> I sent an email to te mailing list
14:10:51 <flaper87> (I can get the link, sorry I don't have it handy)
14:11:07 <flaper87> and the link contained a doodle poll to pick a day between Tomorrow and next monday
14:11:26 <flaper87> Most of the folks voted for next monday so, the review/bug squash day will be on Monday November 23rd
14:11:31 <Jokke_> #link http://doodle.com/poll/mt7hwswtmcvmetdn
14:11:38 <flaper87> I'll work on an etherpad that we can go through
14:11:40 <flaper87> Jokke_: danke
14:11:41 <sabari> *finally makes it to a meeting*
14:11:45 <flaper87> sabari: <3
14:11:53 <sabari> :)
14:11:56 * flaper87 hugs sabari and gives him a cup of coffee
14:12:13 <sabari> *thanks I sure need a coffee now*
14:12:15 <sabari> :D
14:12:20 <flaper87> On monday, each one will work in his/her TZ (obviously)
14:12:34 <flaper87> The goal is to go through a list of bugs and reviews to triage/review them
14:12:48 <flaper87> You can pick whatever you prefer but I'd recommend having a balance between them
14:12:57 <flaper87> Especially if you're in the glance bug team
14:13:21 <flaper87> if you don't have it already
14:13:27 <flaper87> Here's the link to the glance dashboard
14:13:31 <flaper87> #link https://bitly.com/glance-dashboard
14:13:44 <Jokke_> and please do not set priority (apart from wishlist) unless you can actually confirm the bug
14:13:49 <flaper87> I normally update it to reflect latest changes in our process. Last change was to include a priorities section
14:13:55 <flaper87> Jokke_: ++
14:14:15 <flaper87> ok, any questions? doubts?
14:14:22 <flaper87> suggestions?
14:14:24 <mclaren> ah so it includes the priorities ones now - nice
14:14:24 <flaper87> rage?
14:14:37 <flaper87> mclaren: :)
14:14:52 <flaper87> speaking of which, for those to be included, the review needs to have a tag
14:15:07 <flaper87> MitakaPriority
14:15:13 <flaper87> That in the commit message
14:15:17 <sabari> ^ I was about to ask that :)
14:15:28 <flaper87> I went with that because the topic gets overridden when ppl work in branches
14:15:42 * flaper87 is sooooo looking forward to have hashtags in gerrit
14:15:53 <flaper87> That way I can start tweeting on gerrit properly
14:15:56 * flaper87 ducks
14:16:04 <flaper87> jokes apart, that'll be super useful for this
14:16:23 <flaper87> for now, if you see a review that is part of the priorities list, require the committer to apply: MitakaPriority
14:16:29 <flaper87> in the commit message
14:16:53 <flaper87> example
14:16:55 <flaper87> #link https://review.openstack.org/#/c/197388/
14:16:57 <mfedosin_> are trusts commits affected?
14:17:26 <flaper87> mfedosin_: nope
14:17:48 <flaper87> I guess, for mitaka, it'll be mostly image import process
14:17:58 <mfedosin> what about our commits in Nova?
14:17:58 <flaper87> and nova stuff that is required in the client/server
14:18:28 <mfedosin> I think the flag is not required there as well
14:18:37 <flaper87> Those need to be communicated manually, I guess
14:18:39 <flaper87> oh no
14:18:43 <flaper87> this is glance only
14:18:50 <flaper87> the commits in nova fall into nova's process
14:19:22 <flaper87> ok, moving on unless there are further questions
14:19:37 <flaper87> #topic Review Bugs
14:19:49 <flaper87> #link https://bugs.launchpad.net/glance/+bug/1447322 (abhishekk)
14:19:49 <openstack> Launchpad bug 1447322 in Glance "Attempting to reactivate a queued image returns a 403" [Undecided,New]
14:19:53 <abhishekk> hi, this is related to Attempting to reactivate a queued image returns a 403
14:20:08 <abhishekk> what is appropriate return code 400 or 409?
14:20:24 <flaper87> abhishekk: have we talked to the API-WG about this?
14:20:44 <abhishekk> flaper87: not sure
14:20:54 <flaper87> abhishekk: lets do that, then
14:21:04 <abhishekk> flaper87: ok
14:21:06 <flaper87> I'd recommend joining their IRC channel and bring this up there too
14:21:08 <nikhil> actually we did
14:21:15 <flaper87> nikhil: oh, awesome
14:21:15 <nikhil> when this was first implemented
14:21:35 <nikhil> and had a big rants from both sides
14:21:48 <nikhil> the thing is we are working on the "status" of an image
14:22:02 <nikhil> it's an internal entity to the project that has been given API access
14:22:04 <flaper87> mmh, unfortunately, I see this as a breaking change anyway
14:22:06 <nikhil> so it's not a resource
14:22:23 <flaper87> we'd be changing the way we respond and that's considered a breaking change
14:22:30 <Jokke_> I think 400 or 403 would be the correct on at that abhishekk
14:22:40 <nikhil> so, reactivating is a forbidden operation on non-approved states
14:22:59 <nikhil> Jokke_: I disagree
14:23:00 <flaper87> makes sense to me
14:23:11 <abhishekk> nikhil: thanks for the update
14:23:26 <abhishekk> so we can mark this bug as wont' fix
14:23:27 <nikhil> oops, I read it as 409
14:23:31 <nikhil> Jokke_: sorry
14:23:31 * flaper87 gives nikhil the weekly memory badge
14:23:39 <nikhil> :P
14:23:51 <flaper87> I guess we can mark this as invalid
14:24:01 <flaper87> nikhil: want the honors ?
14:24:06 <flaper87> you have more context
14:24:07 <Jokke_> but yeah if the current is something else than 500, won't fix is probably the apropriate thing to do :(
14:24:23 <flaper87> Jokke_: won't fix ++
14:24:28 <nikhil> Jokke_: but I don't think 400 is applicable
14:24:33 <nikhil> flaper87: surely :)
14:24:41 <flaper87> nikhil: coolio
14:25:07 <flaper87> #link 'show' method for 'members' is not implemented in v1 api https://github.com/openstack/glance/blob/master/glance/api/v1/router.py#L91 (mfedosin)
14:25:10 <mclaren> what do you get if you try to change the status of an image currently? (eg via v1) does anyone know?
14:25:31 <Jokke_> nikhil: yeah it's not perhaps really the right one as we do understand the request we're just not willing to fulfil it
14:25:48 <flaper87> mfedosin: ?
14:25:49 <mfedosin> it's a strange thing we found out today
14:26:03 <flaper87> mmh, I think the same v1 policy applies here
14:26:08 <flaper87> I'd rather not implement it
14:26:16 <nikhil> Jokke_: yeah..
14:26:17 <flaper87> and request people to move to v2 if they really needed
14:26:18 <mfedosin> currently in v1 api it's stated that there is 'show' method for members
14:26:57 <mfedosin> so, yeah. it was my question
14:27:09 <mfedosin> should we implement it, because it's required in v1 api
14:27:13 <mfedosin> ?
14:27:20 <flaper87> apparently no one is using it since it's not implemented and not reported
14:27:25 <flaper87> what do you mean w/ it's required?
14:27:27 <rosmaita> flaper87: ++
14:27:41 <Jokke_> mfedosin: where about? not in the api ref at least http://developer.openstack.org/api-ref-image-v1.html
14:27:42 <mfedosin> (I got it from customers, which use Grizzly)
14:27:49 <nikhil> mclaren: I will check
14:28:01 <flaper87> jeeez, grizzly
14:28:13 <flaper87> at least it's not essex *cough* mclaren *cough*
14:28:17 <flaper87> :D
14:28:21 <mclaren> nikhil: HTTPForbidden I think
14:29:01 <mfedosin> GET /v1/images/​{image_id}​ Show image details and image binary
14:29:02 <mclaren> so 403 also
14:29:06 <flaper87> mfedosin: what error is it throwing now?
14:29:17 <flaper87> mclaren: erm, lets talk about that after the meeting, pls :)
14:29:24 <flaper87> we've moved on
14:29:28 <mfedosin> now there is 405 error
14:29:33 <flaper87> ... to another topic
14:29:44 <mfedosin> okay, let's not implement it
14:29:47 <flaper87> mfedosin: ok, I guess it can stay like that
14:29:51 <flaper87> unless someone disagrees
14:29:57 <flaper87> like *STRONGLY* disagrees
14:30:00 <flaper87> :D
14:30:16 <Jokke_> It's funny that we don't have it, but I'm in favor keeping it that way :P
14:30:31 <nikhil> mclaren: confirmed in the code, it's what you said so, 403
14:30:53 <flaper87> ok, so, lets keep it that way
14:31:04 <flaper87> mfedosin: it'd be cool if you could file a bug and then mark it as won't fix
14:31:11 <flaper87> just to keep a record/reference for future reporters
14:31:40 <flaper87> mfedosin: can you do that? Otherwise I'll do it
14:31:49 <mfedosin> flaper87: I will do
14:32:01 <flaper87> awesome
14:32:16 <flaper87> ok, there are no other topics so, open discussion
14:32:20 <flaper87> #topic Open Discussion
14:32:27 <flaper87> 3... 2... 1... GOOOOOOOOOOOOOOOO
14:32:47 <Jokke_> so forgot one thing around bug day
14:33:26 * rosmaita is dying with anticipation
14:33:46 <nikhil> flaper87: I got feedback on the import stuff from IBM groups
14:33:50 <flaper87> rosmaita: lol
14:33:52 <Jokke_> Please tag the bugs you think would fit to the https://wiki.openstack.org/wiki/StableBranch Appropriate Fixes description with liberty-backport-potential
14:34:25 <flaper87> Jokke_: I think we're missing a chapter about bug triage in our how to contribute guidelines
14:34:29 <flaper87> I wrote the blueprints part
14:34:38 <flaper87> who wants to help with the bug part of it?
14:35:03 <flaper87> #link https://review.openstack.org/#/c/234653/
14:35:08 <flaper87> that's the blueprints guideline
14:35:09 <flaper87> nikhil: AWESOME!
14:35:12 <Jokke_> we'll get to those either at Monday or later during the week and see if they fit to picture with the stable-maint group :)
14:35:16 <flaper87> nikhil: is that something you can report on the spec?
14:35:19 <mclaren> nikhil: I'm interested
14:35:28 <flaper87> There are still some critical discussions happening there
14:35:28 <Jokke_> nikhil: shoot
14:35:40 <nikhil> surely, I will update the spec
14:35:47 <nikhil> oops, comment *
14:35:48 <flaper87> nikhil: AWESOME
14:35:58 <flaper87> feel free to share here but I'd love to have that on the spec as well
14:36:11 <flaper87> just to make sure other folks not attending the meeting can read it
14:36:16 <mclaren> I made a spec update I'd love some feedback on
14:36:23 <flaper87> I'll read
14:36:29 <nikhil> ack
14:36:36 <flaper87> mclaren: did you address comments from the last PS?
14:36:50 <flaper87> s/last/previous/
14:36:54 <nikhil> so, there are different groups and people want a few common things
14:37:45 <mclaren> flaper87: I'm wondering if it's possible to do something simpler -- without the persistent bikeshed
14:37:59 <nikhil> 1) upload using direct-url (copy-from in v1, in v2 it's a bit icky but import does that)
14:38:01 <mclaren> comment is around line 213
14:38:28 <flaper87> mclaren: is that your update to the spec?
14:38:46 <flaper87> I'll read and comment
14:39:01 <flaper87> mclaren: ah so, you just commented, ok
14:39:03 <mclaren> yes, thanks. Feel free to beat me up if its horrendous
14:39:25 * flaper87 takes his baseball bat
14:39:33 <mclaren> hang on, no bats!
14:39:43 <flaper87> mclaren: thanks for trying to think of simpler ways to do this
14:39:47 * Jokke_ hands over box of 6" nails and hammer to flaper87
14:39:51 <nikhil> 2) OVA like support
14:40:06 * flaper87 does a ninja jump and goes after mclaren
14:40:16 <mclaren> nikhil: I think a number of people are interested in 'copy-from' type support/will be very interestd when v1 goes away.
14:40:26 <flaper87> yeah
14:40:38 <flaper87> and #2 is interesting as we've had feedback fro just one group so far
14:40:40 <nikhil> https://imgur.com/gallery/2YZjYLk
14:40:43 <flaper87> it's good to know that there's more interest
14:40:48 <flaper87> we still have a spec up for review
14:40:52 <flaper87> wonder if it's been updated
14:41:10 <nikhil> I guess not
14:41:21 <Jokke_> nikhil: I commented that to spec already, but I'm bit afraid ... There was huge pressure from Inter ref that ova stuff just before release (just like the cycle before) and haven't heard anything back since the exclusion due to the freeze and this planning
14:41:26 <nikhil> I think that not being in priorities made then not interested
14:41:31 <nikhil> yet
14:41:32 <mclaren> *hopefully* the import spec will facilitate OVA stuff
14:41:44 <rosmaita> mclaren: ++
14:41:54 <flaper87> yeah
14:41:59 <flaper87> ah, since it's open discussion
14:42:01 <flaper87> #link https://review.openstack.org/#/c/245897/
14:42:07 <flaper87> I've applied those 2 tags to glance
14:42:20 <flaper87> The patches haven't merged BUT I'd love some +1s from other folks in the team
14:42:31 <bunting> There is also a spec-lite about moving metadefs into sub-commands
14:42:38 <bunting> #link https://bugs.launchpad.net/python-glanceclient/+bug/1489534
14:42:38 <openstack> Launchpad bug 1489534 in python-glanceclient "Move metadef commands to sub-commands" [Wishlist,In progress] - Assigned to Niall Bunting (niall-bunting)
14:42:39 <Jokke_> mclaren: That's why I'm extremely dissapointed that they haven't been involved in any ways in this discussion
14:42:54 <rosmaita> Jokke_: ++
14:42:55 <nikhil> yeah, I am not sure. I have only gotted the name OVA as feedback but I will ask more. If it's full fledged OVA then it's unlikely to have as image. we nees artifacts for that or no? what do you all think?
14:42:55 <flaper87> I, obviously, left rolling-upgrades as the only thing that can roll is glance down a hill when trying to do rolling upgrades
14:43:06 <Jokke_> I don't want to end up to situation where it becomes urgent week before freeze again
14:43:19 <flaper87> left rolling-upgrades out*
14:43:26 <flaper87> Jokke_: ++
14:43:44 <flaper87> Again, we've a priorities list to focus on, other things will have to be pushed by the interested parties
14:43:51 <flaper87> and those things will be evaluated accordingly
14:43:56 <flaper87> in a case-by-case basis
14:43:57 <nikhil> mclaren: ha, I created a tag called lite-spec for the store :P
14:44:19 <nikhil> https://bugs.launchpad.net/glance-store/+bugs?field.tag=lite-spec
14:44:33 <nikhil> I will change it to spec-lite, don't worry
14:44:38 <nikhil> just fyi
14:44:44 <flaper87> man, the import spec has 89 comments
14:45:05 <flaper87> ok
14:45:13 <flaper87> anything else we want to talk about?
14:45:20 <mfedosin> yup
14:45:23 <flaper87> otherwise, we can call it a meeting
14:45:25 <flaper87> mfedosin: go
14:45:27 <nikhil> Jokke_: yeah, I think we should avoid that impl for Mitaka if we do decide to impl import related changes
14:45:32 <mfedosin> 2 things
14:45:42 <mfedosin> first one about glare api version
14:46:07 <mfedosin> should it be 0.1 while it's in experimental state?
14:46:17 <mfedosin> and 1.0 when it's stable
14:46:24 <Jokke_> mfedosin: sounds reasonable
14:46:38 <mfedosin> or it can be 1.0 from the beginning
14:46:49 <mfedosin> I would prefer 0.1
14:46:56 <mfedosin> what do you think?
14:47:03 <Jokke_> mfedosin: is the plan to release it as experimental still in M?
14:47:08 <mclaren> no reason not to go with 0.1?
14:47:20 <flaper87> 0.1 sounds good
14:47:26 <Jokke_> it's easy to bump at any point of the cycle anyways
14:47:30 <flaper87> mclaren: do we already have patches for that split ?
14:47:36 <flaper87> ops
14:47:38 <flaper87> mfedosin: ^
14:47:55 <mfedosin> kairat made a patch that removes current implementation
14:48:02 <mfedosin> I have to write a spec for that
14:48:05 <flaper87> mmh, why removing it and not moving it ?
14:48:13 <mfedosin> good question :)
14:48:18 <flaper87> I saw the patch and I was confused
14:48:22 <nikhil> I thought we decided to not remove in Monday's meeting
14:48:23 <flaper87> I'd rather have it moved
14:48:34 <mclaren> what's the latest with glare? Is it intended to be mainly for other services storing things or will it be a full public api in time? (I'm a bit out of touch there, sorry)
14:48:34 <Jokke_> flaper87: because moving to versionedObject requires pretty much full rewrite :(
14:48:38 <mfedosin> I want to get the answer as you
14:48:38 <flaper87> and that was my feeling from the summit to
14:48:40 <nikhil> moving makes sense, removing and adding is confusing
14:48:59 <flaper87> Jokke_: sure but we should move it to the glare package and then they can remove the parts that need to be removed
14:49:01 <flaper87> I guess
14:49:07 <flaper87> I just don't want to loose history
14:49:11 <nikhil> mclaren: semi-public api
14:49:17 <flaper87> as in removing everything and then having everything added again
14:49:28 <flaper87> nikhil: ++ on moving
14:49:36 <flaper87> mfedosin: do you have a link to the review?
14:49:40 <Jokke_> flaper87: I hear ya, that was my first question as well :D
14:49:40 <flaper87> I remember seeing it
14:49:59 <mfedosin> https://review.openstack.org/#/c/241265/
14:50:02 <mfedosin> this one
14:50:06 <nikhil> we need to wait on Alex then
14:50:21 <mfedosin> he's running around
14:50:32 <mfedosin> but I can't catch him :)
14:50:37 <mfedosin> to talk about it
14:51:07 <flaper87> there, -2'd
14:51:08 <mfedosin> I will begin with 'moving' spec
14:51:12 <flaper87> :D
14:51:15 <Jokke_> mfedosin: setup tripwire
14:51:22 <nikhil> flaper87: I agree that we don't need a mini-summit however, it would be good to get a early video conf for such discussions
14:51:42 <flaper87> nikhil: yeah, that we'll have. We need that for the image import part too
14:51:43 <nikhil> for 1. import 2. glare
14:51:49 <nikhil> cool
14:51:51 <flaper87> I think I forgot to mention this in my summary
14:51:59 <flaper87> we actually talked about a video conf at some point
14:52:05 <flaper87> sorry about that
14:52:09 <flaper87> and thanks for bringing this up
14:53:01 <mfedosin> another question is about .mailmap
14:53:10 <mfedosin> do we need it in our repo?
14:53:13 <Jokke_> is there any reason to keep that?
14:53:25 <mfedosin> https://github.com/openstack/glance/blob/master/.mailmap
14:53:27 <nikhil> it was used earlier
14:53:34 <flaper87> I don't really care, I know there was a reason to have it
14:53:38 <flaper87> we can sync with infra about this
14:53:39 <nikhil> and I doubt if anyone cares now
14:53:43 <Jokke_> nikhil: is there, not was there :P
14:53:48 <flaper87> and get a feeling of what other folks are doing
14:53:55 <flaper87> but I'd be all for removing it
14:53:56 <Jokke_> flaper87: ++
14:53:58 <flaper87> lsat update was 2014
14:54:04 <nikhil> Jokke_: dark ages :)
14:54:10 <mfedosin> .mailmap exists in all repos, like Nova, Keystone etc
14:54:20 <mfedosin> and all of them outdated
14:54:23 <flaper87> mfedosin: have those been updated?
14:54:25 <flaper87> :D
14:54:38 <Jokke_> can we be for once community leader if it's not used by anything anymore?
14:54:45 <mfedosin> so we can begin with ML message
14:54:55 <mfedosin> create a bug
14:55:00 <Jokke_> ++
14:55:03 <mfedosin> and remove it from all repos
14:55:08 <flaper87> Jokke_: I don't mind as long as infra gives ok
14:55:24 <flaper87> I don't think it's being used elsewhere BUT assume makes an #!$@#$ between U and ME
14:55:25 <Jokke_> flaper87: yeah, as long as it's not used
14:55:26 <flaper87> ;)
14:55:44 <nikhil> I think gerrit takes care of things so, not really useful
14:55:45 <mfedosin> I will send a message today if you don't mind :)
14:55:54 <flaper87> mfedosin: go for it
14:55:56 <Jokke_> mfedosin: go for it
14:55:58 <flaper87> and thanks for doing that
14:56:03 <Jokke_> tag [infra]
14:56:04 <flaper87> Jokke_: OUT OF MY MIND
14:56:07 <flaper87> jeeez
14:56:25 <mfedosin> :D
14:56:25 <Jokke_> :D
14:56:27 * flaper87 can't have privacy anymore
14:56:28 <flaper87> :P
14:56:43 <flaper87> ok, we're running out of time
14:56:56 <Jokke_> any last wishes?
14:57:05 <flaper87> world peace ?
14:57:09 <nikhil> flaper87: one quick clarification. is there a reason someone shouldn't propose support for hierarchal multi-tenancy support?
14:57:45 <nikhil> though, with keystone still cleaning up it wouldn't be until N
14:57:46 <flaper87> nikhil: oh mmh, I don't think there is. It depends on what will be required to have that support, I guess
14:57:58 <flaper87> nikhil: thought so
14:58:04 <flaper87> an early spec would be cool anyway
14:58:08 <flaper87> it gives time to clearing things up
14:58:13 <nikhil> ok, thanks. ack.
14:58:14 <flaper87> and for better discussions
14:58:31 <flaper87> coolio
14:58:35 <flaper87> That's all folks!
14:58:38 <flaper87> thanks for attending
14:58:40 <mclaren> thanks
14:58:40 <Jokke_> Thanks all
14:58:47 <mfedosin> thanks!
14:58:47 <flaper87> have a great day, weekend and week until our next meeting
14:58:51 <abhishekk> thank you
14:58:54 <flaper87> Break glance and blame mclaren
14:58:59 <Jokke_> Don't forget Monday!
14:59:01 <flaper87> #endmeeting