14:00:19 <nikhil_k_> #startmeeting Glance
14:00:20 <openstack> Meeting started Thu Apr 30 14:00:19 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k_. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:21 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:22 <nikhil_k_> :-)
14:00:24 <kragniz> o/
14:00:24 <openstack> The meeting name has been set to 'glance'
14:00:27 <nikhil_k_> Welcome all!
14:00:28 <ivasilevskaya> o/
14:00:31 <bpoulos> o/
14:01:00 <flaper87> o/
14:01:08 <mfedosin> o/
14:01:14 <rosmaita> o/
14:01:20 <nikhil_k_> Looks like we have a decent turnout.
14:01:24 <nikhil_k_> Let's get started
14:01:28 <nikhil_k_> #topic Kilo tagged.
14:01:33 <pkoniszewski> o/
14:01:55 <nikhil_k_> Kilo was tagged a few mins back. You may see an email soon.
14:02:05 <mclaren> o/
14:02:16 <flaper87> w00000t, tags tags tags
14:02:19 <jokke_> o/
14:02:25 <lakshmiS> o/
14:02:28 <cpallares> o/
14:02:37 <jokke_> \\o \o/ o// o/7 for kilotags
14:02:40 <nikhil_k_> Any bugs/fixes need to be backported to stable/kilo and bring it to stable crew's attn ie Erno, Flavio, Zhi Yan and Nikhil (for Glance)
14:03:00 <kragniz> nikhil_k_: this is the final release tag, right?
14:03:00 <nikhil_k_> The rules are more stringent so please keep that in mind.
14:03:05 <nikhil_k_> yep
14:03:07 <sigmavirus24> o/
14:03:39 <sigmavirus24> nikhil_k_: And that's the stable team for glance_store too, correct?
14:03:51 <nikhil_k_> Correct sigmavirus24
14:03:55 <nikhil_k_> and for py-client
14:04:17 <sigmavirus24> right
14:04:21 <sigmavirus24> :thumbsup:
14:04:34 <nikhil_k_> There may be members from global stable team but these are POCs for Glance stuff.
14:04:54 * flaper87 wishes GH emojis would render in weechat
14:05:00 <nikhil_k_> :-)
14:05:02 <sigmavirus24> flaper87: make it so
14:05:10 <sigmavirus24> flaper87: you could write a rust extension to do that
14:05:11 <nikhil_k_> irssi?
14:05:20 <flaper87> lol
14:05:30 <jokke_> nikhil_k_: doesn't render them either :P
14:05:33 <nikhil_k_> Anyways, questions?
14:05:33 <sigmavirus24> nikhil_k_: you'd have to write that in perl ;)
14:05:43 * kragniz is glad it doesn't
14:05:46 <nikhil_k_> :P
14:05:54 <flaper87> none from me
14:06:04 <jokke_> me neither
14:06:23 <nikhil_k_> perl + UX ?= not like, dislike
14:06:40 <nikhil_k_> Thanks
14:06:46 <nikhil_k_> #topic Pre Summit discussions.
14:06:58 <nikhil_k_> #link https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg51762.html
14:07:47 <nikhil_k_> Please read that if you did miss the note. We have a (very) early session planned on May 7th. That will likely overlap with meeting slot so no meeting next week.
14:08:05 <nikhil_k_> I will send out a note on ML once things are confirmed timewise.
14:09:06 <nikhil_k_> #action (everyone): Please suggest ideas that absolutely need to be discussed on 7th. Add them here: #link https://etherpad.openstack.org/p/liberty-glance-virtual-mini-summit
14:09:47 <nikhil_k_> If you see
14:09:52 <nikhil_k_> #link https://etherpad.openstack.org/p/liberty-glance-summit-topics
14:10:32 <nikhil_k_> The topic "The direction of the Glance project" would most definitely be adjusted in the main event's schedule. So, I think we can discuss it later (on 12th or 13th).
14:11:05 <nikhil_k_> For 7th, I would suggest topics that we think that may or may not be appropriate for main event.
14:11:20 <nikhil_k_> But ideas are welcome.
14:11:55 <nikhil_k_> Can we get some vote on the time schedule?
14:12:43 <nikhil_k_> #startvote pre-summit sync on 7th from 1400UTC-180UTC
14:12:44 <openstack> Unable to parse vote topic and options.
14:12:52 <nikhil_k_> #startvote pre-summit sync on 7th from 1400UTC to 180UTC
14:12:53 <openstack> Unable to parse vote topic and options.
14:13:13 <nikhil_k_> Ok, let's vote without the bot
14:13:39 <nikhil_k_> Who is against it?
14:13:51 <mclaren> nikhil_k_: are we sure we need three days? (Sorry if that's already been discussed/decided)
14:13:51 <mfedosin> 1800, not 180 there
14:14:08 <marekd> Topics for May 7th would be the ones *not* discussed at the summit?
14:14:09 <nikhil_k_> mfedosin: yes, thanks
14:14:10 <mfedosin> 1800UTC and bot will be fine :)
14:14:18 <sigmavirus24> nikhil_k_: I'm not against it
14:14:22 <nikhil_k_> mclaren: we do not. I was hoping that we wrap it up on 7th and 12th
14:14:32 <mclaren> ah, ok, thanks
14:14:38 <nikhil_k_> 13th is more of an alternative to 12th
14:15:03 <mclaren> ah, gotcha, thanks
14:15:10 <nikhil_k_> Since summit is close around that time, we need to be alittle mindful of people's other obligations. That was mostly it.
14:15:30 <nikhil_k_> thanks sigmavirus24
14:15:53 <nikhil_k_> Ok, looks like plan for 7th sounds positive.
14:16:03 <flaper87> sounds good to me
14:16:12 <jokke_> the 7th might be doable, The last week before summit might not be so
14:16:15 <mclaren> nikhil_k_: do we want to reach out to the mongodb folks? See if they're interested in a session?
14:16:17 <TravT> FYI, here's a link for timezone conversion http://everytimezone.com/#2015-5-7,120,cn3
14:16:19 <nikhil_k_> Please do add your name in the list if not already.
14:16:31 <marekd> nikhil_k_: Topics for May 7th would be the ones *not* discussed at the summit?
14:16:35 <nikhil_k_> Thanks TravT , will add to etherpad.
14:16:55 <sigmavirus24> marekd: I believe so
14:17:01 <nikhil_k_> marekd: they would be the ones that are trying to make it to the main event
14:17:25 <nikhil_k_> depending on the outcome of the conversations we would decide if to add to schedule or not
14:17:54 <marekd> sigmavirus24: nikhil_k_: ok, and 12th? just a continuation, or some pre-summit discussions, as there will be no spot for them during the summit, right?
14:17:58 <nikhil_k_> Sometimes, we have split sessions where two different topics share a session
14:18:07 <marekd> nikhil_k_: yep
14:18:25 <nikhil_k_> right
14:18:30 <nikhil_k_> 12th -> just a continuation, or some pre-summit discussions,
14:18:50 <nikhil_k_> but they will/may have sessions that would also be discussed in the summit
14:18:57 <marekd> nikhil_k_: gotit
14:20:17 <nikhil_k_> Moving on
14:20:22 <marekd> any option for may 6th, then? I might have a topic (added it to the etherpad) but it's unlikely i will be available next thursday
14:20:39 <marekd> i will be on May 12, on the other hand.
14:20:57 <nikhil_k_> #topic Open Discussion
14:21:15 <nikhil_k_> marekd: I would encourage to discuss that now if possible (or something related to it)
14:21:58 <nikhil_k_> This is the open discussion slot that you can freely use. If it looks positive then I will try my best to accomodate it. Rescheduling to 6th is expensive operation and I would like to avoid it.
14:22:12 <marekd> nikhil_k_: ok, so let's not reschedule.
14:23:01 <mclaren> mfedosin: Re Trusts: I talked with Duncan Thomas from cinder. He looked at it and concluded it was doable(for cinder backup to swift), but never got around to actually doing anything
14:23:36 <mfedosin> I think I can do it in glance
14:23:53 <mfedosin> I'm going to make a spec and discuss it with you guys
14:24:10 <mclaren> There was a small bit of push back from keystone as trusts were not necesarily designed exactly for this use, but keystone admitted there was no real alternative IIUC
14:24:22 <mclaren> mfedosin: cool, loop me in
14:24:39 <mclaren> when you say you think you can do it, 'it' is trusts or some other mechanism?
14:24:43 <mfedosin> yes, sure
14:24:55 <mfedosin> trusts, of course
14:25:42 <mclaren> ok, I'll try to get Duncan to look at the spec, although he's hard to shepherd sometimes :-)
14:26:37 <mfedosin> mclaren, okay, thank you and Duncan :)
14:26:45 <mclaren> np
14:27:54 <marekd> Hi, so usually i hang out with the keystone folks, where i was focusing on identity federation in OpenStack. Since this is in a good shape i think there is a good moment to expand to other sevices.
14:28:30 <marekd> One of the first non-keystone service could be glance, and an idea for 'intercloud image sharing'
14:28:43 <marekd> I added the topic here: https://etherpad.openstack.org/p/liberty-glance-summit-topics (last one) few hours ago
14:28:51 <marekd> so you likely haven't seen it yet.
14:29:27 <mclaren> marekd sounds interesting
14:30:08 <mclaren> I know folks are doing this already with some fairly hacky methods
14:30:35 <marekd> mclaren: there is a side-project built on top of glance, glint.
14:30:55 <jokke_> There was a talk about one implementation @ Paris Summit, but haven't heard about that since
14:31:02 <mclaren> marekd: yes, I remember from one of the summits University of Somewhere (Vancouver?)
14:31:04 <jokke_> marekd: that was it I think
14:31:11 <marekd> mclaren: Victoria
14:31:12 <nikhil_k_> UBC
14:31:27 <TravT> i thought CERN also showed something
14:31:39 <jokke_> TravT: same guys IIRC
14:31:45 <marekd> TravT: not in this topic
14:31:53 <mclaren> https://www.openstack.org/vote-paris/presentation/glint-image-distribution-current-developments
14:32:12 <TravT> yeah, that's it
14:33:36 <marekd> still, glint relies on a concept of service accounts
14:33:54 <marekd> i would like to followup and try to use federation
14:34:44 <mclaren> sounds much better, I was a bit frightened by what they were doing credentials wise
14:34:57 <marekd> this would be somewhat identity part you guys probably don't care that much, but i feel there would be some glance work on that too. I added some use-cases at the bottom of my proposal in the etherpad
14:35:29 <nikhil_k_> Sounds pretty interesting to me.
14:35:39 <marekd> nikhil_k_: great to hear that.
14:35:51 <nikhil_k_> mclaren: I think the glint use case seemed tied up to small single type of image.
14:36:10 <nikhil_k_> Something that did not have prop data.
14:36:15 <mclaren> nikhil_k_: ok
14:36:46 <mclaren> just got Thierry's mail that Kilo is released \o/
14:36:49 <marekd> I think the architecture i am thinking about would be 'an appstore' like. So, one public cloud publishes some artifact (image, heat template) and others subscribe for some version of that (say always the newest)
14:36:57 <nikhil_k_> (nice)
14:37:21 <jokke_> so the glint use case was that they get donated overflow resources from different cloud providers and they wanted to have up to date specific small image for their workload available on those clouds
14:38:05 <nikhil_k_> right, and something that supported research on high perf data without affecting kernel performance
14:38:46 <nikhil_k_> marekd: That sounds good. I think there may be _some_ overlap with what the community images followed by image marketplace feature of Glance
14:39:07 <marekd> nikhil_k_: what do you mean?
14:39:09 <nikhil_k_> Just want to make sure that we do not have two implmentations for a single use case
14:39:51 <nikhil_k_> marekd: So the idea looks like a publisher + consumer model for certain type of images, right?
14:40:10 <marekd> nikhil_k_: yes
14:40:11 <nikhil_k_> Regulated by multi-tenancy?
14:40:13 <marekd> kind of
14:40:49 <nikhil_k_> The can be borrwed a little bit from the image-sharing concept that already exists today.
14:41:09 <marekd> image-sharing in glance? From the user perspecive - yes.
14:41:10 <nikhil_k_> We are trying to extend it to _really_ publish some images.
14:41:37 <marekd> nikhil_k_: but still  within one deployment of the cloud, right?
14:42:03 <nikhil_k_> yes, right. Glance is region specific deployment (one DC == one universe)
14:42:20 <nikhil_k_> at least typically
14:42:32 <marekd> i could probably help making it publishable across trusted clouds
14:42:50 <marekd> with some policy/limiting applies of course
14:43:13 <nikhil_k_> The issue with federation of Glance is uuid collision. Although, that sounds rare, it actually happens in real world cases :-)
14:43:56 <nikhil_k_> But yes, let's discuss this more. As not concerns were raised.
14:44:04 <nikhil_k_> not many*
14:44:06 <marekd> nikhil_k_: in federation you can freely draw a bold line in between the clouds
14:44:22 <nikhil_k_> sure :-)
14:44:48 <marekd> nikhil_k_: so, i wouldn't subscribe on  uuids, rather...names, as crazy as it may sound.
14:44:51 <marekd> or versions.
14:45:23 <nikhil_k_> ok.
14:45:48 <marekd> e.g i always want to be notified/have available image of the newest cernVM image
14:46:13 <marekd> i trust cern, i am collaborating with them, and they now what and when needs to be published
14:46:21 <marekd> they will take care of patching the image
14:46:34 <marekd> i simply donated some spare cycles
14:46:57 <nikhil_k_> gotcha
14:47:11 <marekd> and the same may happen in commercial world
14:47:33 <nikhil_k_> While we get ideas on the board, I want to quickly check if anyone else has somethign to discuss...
14:48:29 <jokke_> future of v1
14:48:40 <rosmaita> jokke_: v1 must die!
14:48:45 <nikhil_k_> ok, that looks important
14:49:01 <nikhil_k_> marekd: Do you mind we catch up on this on May12/13 if possible?
14:49:03 <jokke_> can we finally make the call to deprecate it so there will be pressure to move the projects depending on it to v2?
14:49:15 <marekd> nikhil_k_: of course!
14:49:19 <nikhil_k_> marekd: thanks.
14:50:12 <nikhil_k_> So, some folks pinged and sigmavirus24 yesterday on how difficult this v1, v2, tasks stuff is becoming. DefCore suggests v2. So, let's do it. Unless someone raised a red flag in the next 4 weeks.
14:50:19 <nikhil_k_> me and*
14:50:37 <nikhil_k_> s/rasied/raises/
14:50:51 <sigmavirus24> :thumbsup: from me
14:51:08 <nikhil_k_> oh, I think kragniz was there too.
14:51:17 * jokke_ is more than happy to sacrifice some spare time to propose the change ;)
14:52:24 <jokke_> rosmaita: and I hope that death is extremely painful ;D
14:53:26 <nikhil_k_> Anything else?
14:54:28 <nikhil_k_> If not, thanks all!
14:54:36 <kragniz> thanks
14:54:45 <sigmavirus24> Thanks
14:54:54 <mfedosin> thanks, see you next week
14:54:57 <nikhil_k_> #endmeeting