14:02:14 <nikhil_k> #startmeeting Glance 14:02:15 <openstack> Meeting started Thu Oct 9 14:02:14 2014 UTC and is due to finish in 60 minutes. The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:16 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:02:19 <openstack> The meeting name has been set to 'glance' 14:02:21 <TravT> o/ 14:02:27 <rosmaita_> \o 14:02:28 <irina_pov> o/ 14:02:31 <nikhil_k> #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 14:02:32 <ativelkov> o/ 14:02:37 <mfedosin> o/ 14:02:43 <rosmaita_> good crowd today 14:02:54 <flaper87> o/ 14:02:58 <nikhil_k> heh, guess the earlier time works better 14:03:07 <ativelkov> And the agenda seems quite long 14:03:10 <nikhil_k> we've a lot on agenda so, need to rush 14:03:12 <nikhil_k> yesh 14:03:20 <nikhil_k> #topic Juno RC 14:03:46 <nikhil_k> Please see the links and let know if there is anything missing or something that strikes out.. 14:04:02 <nikhil_k> #link https://launchpad.net/glance/+milestone/juno-rc2 14:04:11 <nikhil_k> that is what we've in the rc2 bucket atm 14:04:34 <nikhil_k> unless someone can approve and propose 14:04:36 <nikhil_k> #link https://bugs.launchpad.net/glance/+bug/1378968 14:04:37 <uvirtbot> Launchpad bug 1378968 in glance "Metadef schema column name is a reserved word in MySQL" [Undecided,In progress] 14:05:21 <nikhil_k> Another note on that as a 'learning lesson' for all of us 14:05:33 <nikhil_k> we'd a empty rc1 and too many proposals for rc2 14:05:50 <nikhil_k> that was taken a bit negatively and we got a free run this time 14:06:06 <nikhil_k> please try to take care 14:06:10 <TravT> yeah, a lot of these were all ready for rc1... but I guess we didn't mark them appropriately in launchpad? 14:06:27 <kragniz> nikhil_k: so get fixes merged in sooner for rc1? 14:06:32 <ativelkov> This means we need to plan RC1 in advance next time 14:06:39 <nikhil_k> yeah, we may need to exercise some rc related activites within our team 14:06:53 <nikhil_k> ativelkov: right on 14:06:58 <TravT> +1 14:07:11 <nikhil_k> kragniz: yeah, spread out the fixes into rc1 and rc2 etc 14:07:21 <nikhil_k> so, that important ones go in rc1 14:07:31 <jokke_> Empty RC1 and release directly out of that 14:07:40 <nikhil_k> rc2 would have fixes for some minor bugs or regression like situations 14:08:09 <nikhil_k> finally, wayne's bug 14:08:15 <nikhil_k> he mentioned to me last evening 14:08:37 <nikhil_k> however, it may hard to get it in rc2 unless some review volunteers can help in next few mins 14:09:05 <mclaren> I +2d https://review.openstack.org/#/c/126974/ 14:09:23 <mclaren> It's worth putting in, no? 14:09:23 <nikhil_k> mclaren: awesome! 14:09:29 <nikhil_k> think so 14:09:39 <zhiyan> this time we merged too much patches in rc2 (high rish), next time i will prefer to move those kind of change into next release but rush 14:09:46 <zhiyan> risk* 14:10:08 <nikhil_k> yes, so for these kinds of things.. I feel like we need a bit of planning 14:10:22 <nikhil_k> and co-ordination as we may have more newer members this cycle 14:10:27 <zhiyan> +1, we probably could have a 'official' plan for rc release 14:10:57 <nikhil_k> so with that, I'll let the intos begin 14:10:59 <zhiyan> yes, we need more efforts on review 14:11:03 <nikhil_k> #topic Introductions 14:11:28 <nikhil_k> so, let me do the kick off 14:11:53 <nikhil_k> 'm a software developer working with Rackspace primarily on Glance in the compute engineering team 14:12:33 <nikhil_k> been working on Glance for a bit more than couple of years and have a background in HPC, large scale systems, etc. 14:12:40 * nikhil_k done 14:12:57 <mclaren> HPC? snap! 14:13:27 <nikhil_k> heh 14:13:32 <nikhil_k> no takers? 14:13:37 <jokke_> nikhil_k: 2 years + = new member? 14:13:53 <lakshmiS> soft. engineer working on openstack for the last few years and last 6 months specifically on glance 14:13:58 <nikhil_k> well, I felt like introducing myself to new members 14:13:58 <mfedosin> oh, hpc... in good days i wrote mpi library for java 14:14:16 <TravT> yeah topic says "new members"? are you wanting everybody to intro? 14:14:21 <nikhil_k> sure 14:14:35 <nikhil_k> s/of/for/ 14:14:36 <nikhil_k> typo 14:15:12 <jokke_> how about moving that to #openstack-glance and moving on? Otherwise we'll be sitting here still tomorrow with this agenda ;P 14:15:23 <zhiyan> hehe 14:15:34 <kragniz> jokke_: heh 14:15:38 <kragniz> I like cats and robots 14:15:41 <nikhil_k> sure, then.. kind request for all those were going to log off.. 14:15:43 <kragniz> I'm a 20 year old student from england, currently working for HP 14:15:44 <ativelkov> I would suggest to update a wiki page 14:15:49 * kragniz is new member 14:15:57 <nikhil_k> please be on the other channel after the meeting 14:16:03 <ativelkov> do we have a "team" page at wiki? 14:16:09 <nikhil_k> ativelkov: +1 14:16:16 <mfedosin> ativelkov, +1 14:16:17 <zhiyan> sounds better 14:16:26 <nikhil_k> basically, I feel like new members should be able to say I need a review from core-reviewer 14:16:35 <nikhil_k> whom should I go and ping? 14:16:51 <nikhil_k> important MPs should not sit in the backlog for a long time 14:16:54 <jokke_> +1 14:17:00 <ativelkov> great 14:17:03 <nikhil_k> having some informal energy going is vital 14:17:12 <flaper87> nikhil_k: https://review.openstack.org/#/admin/groups/13,members :D 14:17:24 <nikhil_k> let's distribute these introductions over a few meetings 14:17:27 <flaper87> well, no irc nicks there but 14:17:35 <ativelkov> so, lets have an AI to create a wiki page listing the active contributors and their areas of responsibility 14:17:37 <nikhil_k> and we can hav some creative ideas going 14:17:54 <zhiyan> ativelkov: there have one, top reviewers 14:18:00 <nikhil_k> may be some rap songs by the team members or something that will get them attention 14:18:16 <nikhil_k> moving on 14:18:30 <nikhil_k> #topic Moving to v2 API 14:19:05 <nikhil_k> flaper87: want to take that? 14:19:14 <flaper87> nikhil_k: sure :D 14:19:19 <nikhil_k> :) 14:19:30 <zhiyan> it's indeed a cross-project work/topic, e.g. nova currently doesn't use image-v2. 14:19:35 <flaper87> Basically, I want v1 to die, painfully and slowly but not to slow as to still be part of the kilo release 14:19:46 <flaper87> I think that sums it up 14:19:48 <flaper87> :D 14:19:53 <flaper87> That said, we can't do that yet. 14:20:04 <flaper87> We need to update nova, cinder and probably other services 14:20:10 <zhiyan> but before it, we need enhance test on v2 first 14:20:13 <flaper87> I know arnaud has a spec for nova 14:20:32 <jokke_> flaper87: +1 ! 14:20:35 <flaper87> zhiyan: we can enhance tests but I don't think that's a blocker to make it the default 14:20:49 <kragniz> flaper87: where are the pain points with updating the other services? 14:20:52 <flaper87> BTW, saying "We now recommend v2" doesn't mean everyone needs to move right away 14:21:02 <flaper87> kragniz: saying nova is already painful 14:21:09 <zhiyan> flaper87: imo, it's a blocker. but anyway spec is ok for push progress. 14:21:14 <flaper87> it's lie people saying "Voldemort" in harry potter 14:21:17 <ativelkov> We should have some formal deprecation perios, I think 14:21:27 <flaper87> there will be a deprecation period 14:21:33 <flaper87> the plan is to mark it as deprecated in kilo 14:21:37 <flaper87> then remove it in igloo 14:21:57 <flaper87> again, saying it's deprecate doesn't mean everyone has to migrate right away 14:22:03 <flaper87> that's why there's a deprecation period 14:22:11 <zhiyan> we actually proposed this is in icehouse cycle, but i think most project don't trust v2 is stable enough 14:22:20 <flaper87> I expect many deployments to wait for the first 2 stable kilo releases before doing so 14:22:32 <flaper87> zhiyan: well, f......k that. 14:22:43 <jokke_> +1 14:22:50 <flaper87> if we don't start migrating things they'll never trust v2 14:22:54 <flaper87> and we'll never test it 14:23:02 <zhiyan> still remember preformance issue on v2, which raised in ML 14:23:22 <nikhil_k> so, what are the issues? can we list them ? 14:23:31 <nikhil_k> in glance and for other projects? 14:23:32 <hemanthm_> so, do we backport stuff to v1 during the deprecation period? 14:23:33 <zhiyan> we need a plan, but put test stuff on top imo 14:23:34 <mclaren> one problem is v1 is pretty rock solid :-) 14:23:36 <flaper87> nikhil_k: I'd say lets list them off meeting 14:23:44 <nikhil_k> flaper87: sounds good 14:23:50 <flaper87> hemanthm_: sure, if there are bugs we have to 14:24:07 <zhiyan> mclaren: another reason is that , most proj didn't use new feature which only v2 provided 14:24:07 <rosmaita_> zhiyan: our ui is going to start consuming v2 very soon, we should be able to get some performance numbers 14:24:08 <hemanthm_> flaper87: but not after that I'd guess 14:24:08 <flaper87> my main concern is updating nova 14:24:17 <flaper87> which has a quite outdated and messy code 14:24:19 <flaper87> hemanthm_: right 14:24:20 <zhiyan> rosmaita_: nice 14:24:29 <flaper87> rosmaita_: +2 14:24:34 <rosmaita_> nova is the big one 14:24:39 <mclaren> jaypipes may be a good contact on the nova side for this 14:24:40 <zhiyan> rosmaita_: ify, i resolve some key points 14:24:44 <flaper87> and AFAIK, the spec hasn't been approved yet 14:24:45 <jokke_> Can we have total ff for the v1 already on kilo so no new functionality, only high+ bug fixes? 14:24:45 <zhiyan> resovled 14:24:49 <flaper87> but lets work on that 14:24:56 <nikhil_k> #link https://review.openstack.org/#/c/84887/ 14:25:05 <zhiyan> flaper87: yep , jpipe has concers 14:25:16 <flaper87> zhiyan: sure, lets work on that 14:25:16 <nikhil_k> let's get ball rolling on that one 14:25:28 <flaper87> I need to know if arnoud wants to keep working on it or if I should take 14:25:32 * flaper87 hopes the former :P 14:25:42 <jokke_> zhiyan: I think he needs to start addressing his concerns or work around them then ;) 14:25:50 <zhiyan> of course 14:25:52 <mclaren> nikhil_k: thanks for that link 14:26:07 <nikhil_k> ok, should we move on then? 14:26:08 <zhiyan> actually, i was co-work with arnaud on that idea 14:26:12 <flaper87> I'll be sending an email to the m-l soon about this 14:26:21 <flaper87> I've a draft ready since the begining of juno 14:26:24 <flaper87> :D 14:26:26 <flaper87> that's how much I hate v1 14:26:30 <zhiyan> the initial idea for it is about add zero-copy support in nova 14:26:31 <kragniz> flaper87: haha 14:26:44 <zhiyan> which needs v2 direct iamge location feature 14:27:01 <mclaren> flaper87: jsut bear in mind that more folks may be 'stuck' on v1 than you think (not mentioning names...) 14:27:04 <flaper87> zhiyan: you and me are wroking together on the COW thing so, lets work together on this too 14:27:15 <flaper87> mclaren: yeah :( 14:27:20 <flaper87> mclaren: good point 14:27:24 <nikhil_k> zhiyan: flaper87 : think we should have a meeting soon on the details of this topic 14:27:29 <jokke_> we can keep client support for it? 14:27:39 <flaper87> jokke_: yes 14:27:39 <nikhil_k> listing them out seems like our priority at this point 14:27:45 <TravT> Do we need an etherpad open on this topic to help us track this? e.g.: #link: http://etherpad.openstack.org/p/glance-v2-deprecation 14:27:46 <zhiyan> flaper87: sure thing. those functional patches still in my local env 14:27:59 <nikhil_k> TravT: +1 14:28:02 <rosmaita_> speaking of the client, we should make v2 the default instead of v1 14:28:21 <nikhil_k> thought there was a proposal for that 14:28:28 <mclaren> interesting, would build confidence in v2... 14:28:43 <zhiyan> but frankly i still think we need to enhance v2 test first before change v2 as default 14:28:59 <flaper87> rosmaita_: but we can't if v1 is still the default in the server 14:29:05 <zhiyan> i mean before deprecate v1 14:29:06 <kragniz> zhiyan: where is the v2 testing limited? 14:29:24 <flaper87> zhiyan: that's what Kilo is for 14:29:34 <zhiyan> not strong as project needed, some key api didn't covered by tempest 14:29:37 <flaper87> we'll do the final call in k-3, I think 14:29:37 <mclaren> zhiyan: if you have details on needed v2 tests I may be able to volunteer a QA person 14:29:53 <nikhil_k> mclaren: done :P 14:30:00 <flaper87> mclaren: I like the way you think 14:30:03 <flaper87> muahaha 14:30:04 <zhiyan> mclaren: key one for me, afaik, direct location stuff 14:30:27 <jokke_> flaper87: per default v2 Image API is enabled on the server 14:30:51 <flaper87> jokke_: yeah, I meant to say until we recommend v2 over v1 14:30:52 <mclaren> ok let me chat to the person I have in mind and see if there are spare cycles 14:30:55 <flaper87> bad wording 14:31:08 <zhiyan> sounds good, thanks 14:31:15 <flaper87> nothing else from me 14:31:35 <nikhil_k> let's move on then 14:31:52 <nikhil_k> thanks to TravT for the link for further discussion 14:32:06 <nikhil_k> #topic Glance Summit Topics 14:32:06 <jokke_> flaper87: ok, well that isn't problem in a sense that as the client release cycle is not tied with OS release cycle we can do that in between already ... no need to wait for Kilo to be able to do that 14:32:24 <flaper87> jokke_: yup 14:32:32 <nikhil_k> #link https://etherpad.openstack.org/p/kilo-glance-summit-topics 14:32:49 <jokke_> nikhil_k: I volunteered you to lead my proposal :P 14:32:50 <nikhil_k> seems pretty self-explanatory 14:32:59 * flaper87 still needs to add a design session there 14:33:20 <nikhil_k> thanks to all the hard work! 14:33:23 <zhiyan> flaper87: probably add one for store api stuff 14:33:30 <flaper87> Has anyone seen arnoud? There's something I'd like to gently steal from him 14:33:32 <nikhil_k> am guessing credit goes to TravT again 14:33:51 <flaper87> zhiyan: store api sounds like something we can discuss outside the design session 14:34:01 <zhiyan> why? outside 14:34:20 <nikhil_k> so, let's discuss all the topic next meeting if that's okay 14:34:30 <jokke_> zhiyan: loose quote form you "it's kind of it's own project now" ;)\ 14:34:47 <nikhil_k> if people have cross-project topics please leave a special Note so that it would be easier for me to find 14:34:49 <TravT> Everybody should notice that we have 4 full hours on Friday. 14:34:50 <flaper87> because I don't want to wast 40 mins that could be used for a more interesting session explaining what the API will look like. https://review.openstack.org/#/c/126550/ 14:34:53 <zhiyan> nikhil_k: how many slot for glance this time? 14:34:56 <TravT> that can be open discussion. 14:35:03 <TravT> zhiyan: see top of that etherpad 14:35:04 <mclaren> I think there may be a cross-project session with swift on this spec https://review.openstack.org/#/c/105228/ 14:35:08 <TravT> I put them all in there 14:35:21 <TravT> under "Schedule" 14:35:30 <flaper87> I'd like to talk about image conversion 14:35:36 <flaper87> there's a blueprint for it and no spec 14:35:36 <zhiyan> TravT: got it 14:35:50 <flaper87> arnaud is assigned to that blueprint and I'd like to see if he's working on it or not 14:35:59 <flaper87> Is anyone interested in that topic? 14:36:15 <flaper87> We've gone around it for 2 (or 3) cycles already 14:36:25 <flaper87> now that async tasks are there, it may be a good time to explore that topic further 14:36:29 <nikhil_k> mclaren: mind creating a block in the etherpad. I need to let the decision (or whetever) committee know about cross topics in which GLance needs to be involved 14:36:38 <rosmaita_> flaper87: +1 14:36:48 <mclaren> yes, t hanks, I wasn't sure what the process was! 14:36:51 <nikhil_k> flaper87: +1M 14:36:55 <zhiyan> flaper87: +1 14:36:57 <flaper87> w0000000000000000000000000000000000000000t 14:37:01 * flaper87 writes that down 14:37:17 <flaper87> and don't you dare to steal that slot from me >.> 14:37:28 <nikhil_k> just repeating the same in case someone missed it before:- 14:37:32 <nikhil_k> I need to let the decision (or whetever) committee know about cross topics in which GLance needs to be involved 14:37:37 <nikhil_k> so please add a special note for 14:37:46 <nikhil_k> the cross project topics 14:37:54 <nikhil_k> in the *same* etherpad 14:38:02 <flaper87> nikhil_k: +1 14:38:08 <jokke_> nikhil_k: k 14:39:05 <nikhil_k> think tentative schedule is at http://kilodesignsummit.sched.org/ 14:39:08 <nikhil_k> #link http://kilodesignsummit.sched.org/ 14:39:24 <nikhil_k> next on 14:39:26 <TravT> quick poll, who will be going to the summit? 14:39:31 <jokke_> o/ 14:39:31 <nikhil_k> #topic Volunteers! 14:39:42 <kragniz> o/ 14:39:47 <rosmaita_> o/ 14:40:19 <nikhil_k> ok, let's do the poll on the other channel 14:40:34 <nikhil_k> so, some feedback from the ptl sync meeting 14:40:44 <nikhil_k> seems important so, wanted to bring it up today 14:40:51 <nikhil_k> we need liaisons 14:41:02 * flaper87 was and still is oslo's liaison 14:41:05 <zhiyan> i'd like to support flaper87 do oslo liaisons first, then take it over later 14:41:07 <flaper87> zhiyan: volunteered to help out 14:41:07 <nikhil_k> so, depending on interests - please suggest your names 14:41:14 <mclaren> security? 14:41:17 <flaper87> because, well, ptl happened 14:41:31 <nikhil_k> liaison for security fixes and such 14:41:35 <nikhil_k> an advising member 14:41:39 <ativelkov> o/ 14:41:55 <mclaren> o\ 14:41:58 <nikhil_k> this person does *NOT* need to be a core reviewer 14:42:00 <mclaren> d'oh 14:42:04 <mclaren> lol 14:42:25 <TravT> so who would the person be liaisoning to? 14:42:29 <jokke_> nikhil_k: if core not needed o/ 14:42:40 <nikhil_k> TravT: still in discussion 14:43:00 <ativelkov> oops, my "o/" was to prev ious topic, IRC lagged for some reason 14:43:07 <nikhil_k> however, it's concept that advisory on bugs/fetures and such would be delegated to this person 14:43:15 <nikhil_k> in case of conflict or concerns 14:43:21 <zhiyan> do we really need a liaison for security fixes ? i mean anyone could do it if who familiar that stuff, e.g. particular driver 14:43:35 <nikhil_k> sure 14:43:58 <jokke_> zhiyan: I think there is need to have someone to be added to the private security bugs? 14:44:01 <nikhil_k> this is still in flux atm 14:44:06 <mclaren> I think its partially about taking load off the ptl 14:44:15 <nikhil_k> however, in general think the idea makes sense 14:44:21 <mclaren> so if someone pings nikhil about a potential security issue he can delegate 14:44:25 <TravT> is that like the start of the czar system or something? 14:44:29 <zhiyan> mclaren: +1 14:44:34 <nikhil_k> mclaren: that too and some level of expertise as well 14:44:46 <kragniz> so this is kind of mini-ptl for security? 14:44:47 <nikhil_k> like flaper87 is the best POC for oslo like things 14:44:57 <mclaren> so I can put my hand up 14:45:03 <nikhil_k> great 14:45:05 * flaper87 looks around wondering who flaper87 is 14:45:18 <nikhil_k> we can have more than one I believe 14:45:19 * jokke_ gives flaper87 a mirror 14:45:22 <nikhil_k> we will know 14:45:27 <flaper87> jokke_: LOL 14:45:40 <nikhil_k> if you can please put your name in the *etherpad* 14:45:51 <zhiyan> nikhil_k: i can take oslo one 14:46:00 <nikhil_k> awesome 14:46:04 <nikhil_k> next off 14:46:17 <nikhil_k> #topic Virtual Mini Summit 14:46:22 <nikhil_k> The idea here is 14:46:35 <nikhil_k> to have a video conferencing call with the interested parties 14:46:45 <nikhil_k> to have some prior discussion before the main event 14:46:54 <nikhil_k> it would ideall be one day long 14:47:04 <TravT> +1 I really like that idea 14:47:17 <ativelkov> Good idea, but what about the timezone? :) 14:47:29 <nikhil_k> rackspace has this new vidyo too which can support upto 50 participants 14:47:38 <nikhil_k> tool* 14:47:43 <mclaren> good idea -- would we need a full day? 14:47:47 <nikhil_k> in and out of the company 14:47:48 <TravT> what about 2 half days to better enable better timezones? 14:47:57 <nikhil_k> so, we can decide on the schedule 14:47:57 <zhiyan> nikhil_k: nice, hope it provides good b/w to me 14:48:05 <jokke_> TravT: +1 14:48:06 <nikhil_k> a doodle should help to certain extent I sup 14:48:24 <nikhil_k> zhiyan: we will have to see how it scales ;) 14:48:42 <zhiyan> nikhil_k: your area, enhance it 14:48:44 <nikhil_k> if many people like the idea, I can start prepping for a doodle 14:49:10 <nikhil_k> and think about clsutering the relevant topics according to the timezone convenience 14:49:20 <nikhil_k> can't gurantee that everyone would be in every topic 14:49:25 <nikhil_k> however, we can try out best! 14:49:26 <zhiyan> nods 14:49:30 <flaper87> +1 14:49:53 <jokke_> nikhil_k: does that vid conf tool support recording? 14:50:00 <nikhil_k> great... if anyone has concerns please send me a pm 14:50:08 <nikhil_k> jokke_: dunnao, will ask 14:50:12 <kragniz> jokke_: one person could just record it if it doesn't 14:50:48 <nikhil_k> #action (nikhil) see if vidyo supports recording or may be find an alternative way to record 14:50:48 <jokke_> kragniz: tru ... would just trust more if it can be done natively 14:51:13 <nikhil_k> 9 mins to go 14:51:16 <nikhil_k> so moving one 14:51:28 <nikhil_k> #topic left over items 14:51:40 <nikhil_k> seems like we rushed in our previous meeting too 14:51:53 <nikhil_k> so, if anyone had any important things to bring up soon-ish 14:51:59 <nikhil_k> good place to do so.. 14:52:19 <mclaren> community images? 14:52:24 <nikhil_k> next one 14:52:31 <nikhil_k> we will move one then 14:52:34 <zhiyan> +1 7 14:52:48 <nikhil_k> #topic community images 14:52:54 <kragniz> okay, so it seems people are vaguely happy with the current spec 14:53:06 <kragniz> the main question is whether or not to have in-band discovery of the community images 14:53:11 <nikhil_k> rosmaita__: we are discussin community images 14:53:27 <rosmaita__> got netsplit or something 14:53:42 <mclaren> I think using the same mechanism as other shared images makes sense 14:53:54 <mclaren> rosmaita__: thanks for your feedback again 14:54:01 <rosmaita__> did we discuss visibility yet? 14:54:06 <nikhil_k> nope 14:54:09 <kragniz> rosmaita__: not yet 14:54:29 <kragniz> rosmaita__: any more thoughts on that? 14:54:31 <rosmaita__> here's my thought about discoverability 14:54:41 <rosmaita__> kragniz's spec allows you to find community images by GET /v2/images?visibility=community 14:54:47 <rosmaita__> mclaren is worried that this may actually conflict with some use cases for community images 14:54:55 <rosmaita__> his use case is a provider wants to deprecate a 'public' image, but does not want to delete it because it could break, e.g., rebuilds 14:55:01 <rosmaita__> so the provider could make it a community image and if you already know the UUID, you can still use the image 14:55:14 <rosmaita__> but you couldn't discover it, so random people who really don't need to use the image, won't find it 14:55:26 <rosmaita__> which is an interesting use case but i like discoverability is good, and i wonder whether community images is the proper thing for this use case the real idea is to enable self-service one-to-all sharing and maybe the deprecation use case should be handled separately? what do other people think? 14:55:40 <mclaren> rosmaita__: I'm ok with just reusing the existing shared image discoverability 14:55:44 <jokke_> rosmaita__: +1 14:55:52 <rosmaita__> ok 14:55:54 <mclaren> GET /v2/images?visibility=shared 14:56:03 <mclaren> shows all shared images community or not 14:56:09 <mclaren> no client changes needed 14:56:22 <mclaren> (first pass) 14:56:40 <mclaren> if you need to distinguish we could do a second pass (which would need a client change) 14:56:53 <mclaren> GET /v2/images?visibility=shared&is_community=<True|False> 14:56:58 <rosmaita__> how would you handle the member_status -- pending by default? 14:57:11 <rosmaita__> the problem is that you don't need to be a member of a community image 14:57:18 <jokke_> mclaren: Wouldn't that be bit rough for the users having used to have their small group of images visible as shared and now getting spammed vith community they wanted it or not? 14:57:21 <mclaren> consistent with existing shared images -- yes 14:57:49 <mclaren> jokke_: no. see my comment on a second pass 14:57:49 <rosmaita__> so now we have 2 non-property property filters! 14:58:15 <jokke_> mclaren: saw that just after <enter> 14:58:20 <nikhil_k> ok, sorry to interrupt 14:58:35 <nikhil_k> I need to take a quick poll which may help with this too 14:58:52 <rosmaita__> maybe need to move to ML to follow up? 14:58:54 <rosmaita__> or to openstack-glance channel 14:58:58 <nikhil_k> sounds good 14:59:07 <nikhil_k> #topic second glance meeting during the week 14:59:09 <mclaren> I'm good to chat now if you're able 14:59:18 <jokke_> nikhil_k: we're out of time 14:59:19 <kragniz> rosmaita__: #openstack-glance 14:59:23 <nikhil_k> idea is to have a second no more than 30-35 mins meeting during the week 14:59:38 <nikhil_k> please send your response to me on the other channel 14:59:42 <zhiyan> what kind of meeting? 14:59:42 <rosmaita_> kragniz: mclaren: yep 14:59:52 <nikhil_k> lets go there 14:59:56 <zhiyan> times up 14:59:58 <nikhil_k> #endmeeting