Tuesday, 2016-11-15

*** walharthi has quit IRC00:16
*** walharthi has joined #openstack-glance00:33
*** walharthi has quit IRC00:45
*** catintheroof has quit IRC00:47
*** catintheroof has joined #openstack-glance00:48
*** catintheroof has quit IRC00:52
*** rrecio_ has quit IRC00:53
*** haplo37 has quit IRC01:20
*** haplo37 has joined #openstack-glance01:25
*** tsymanczyk has quit IRC01:34
*** lujinluo has joined #openstack-glance01:49
*** markvoelker has quit IRC01:50
*** kfox1111 is now known as kfox1111_away01:51
*** markvoelker has joined #openstack-glance02:19
*** mnaser has quit IRC02:24
openstackgerritmelissaml proposed openstack/glance-specs: Fix a typo in artifact-repository.rst  https://review.openstack.org/39748202:26
*** walharthi has joined #openstack-glance02:35
*** namnh has joined #openstack-glance02:37
*** mnaser has joined #openstack-glance02:37
*** namnh has quit IRC02:40
*** namnh has joined #openstack-glance02:40
*** links has joined #openstack-glance02:49
*** bkopilov_ has quit IRC02:57
*** namnh has quit IRC03:04
*** jamielennox is now known as jamielennox|away03:07
*** GB21 has joined #openstack-glance03:08
*** GB21 has quit IRC03:19
*** jamielennox|away is now known as jamielennox03:21
*** TravT has joined #openstack-glance03:25
*** TravT has quit IRC03:27
*** TravT_ has joined #openstack-glance03:27
*** TravT_ has quit IRC03:27
*** TravT has joined #openstack-glance03:28
*** TravT has quit IRC03:33
*** udesale has joined #openstack-glance03:42
*** nicolasbock has quit IRC03:54
*** TravT has joined #openstack-glance03:57
*** TravT has quit IRC04:08
*** TravT has joined #openstack-glance04:08
*** TravT has quit IRC04:09
*** TravT has joined #openstack-glance04:09
*** jamielennox is now known as jamielennox|away04:15
*** TravT has quit IRC04:15
*** jamielennox|away is now known as jamielennox04:17
*** bkopilov_ has joined #openstack-glance04:17
*** groen692 has joined #openstack-glance04:33
*** prateek has joined #openstack-glance04:38
*** jamielennox is now known as jamielennox|away04:40
*** ratailor has joined #openstack-glance05:00
*** jamielennox|away is now known as jamielennox05:03
*** groen692 has quit IRC05:08
*** walharthi has quit IRC05:17
*** pdeore has joined #openstack-glance05:23
*** bhagyashris has quit IRC05:56
*** lujinluo has quit IRC06:15
*** lujinluo has joined #openstack-glance07:12
*** bhagyashris has joined #openstack-glance07:17
*** tshefi has joined #openstack-glance07:22
*** rcernin has quit IRC07:23
*** belmoreira has joined #openstack-glance07:32
*** rvasilets___ has joined #openstack-glance07:36
*** exploreshaifali has joined #openstack-glance07:38
openstackgerritJaspreet Singh Rawel proposed openstack/python-glanceclient: Null value of image property name should not allowed  https://review.openstack.org/39608407:54
openstackgerritJaspreet Singh Rawel proposed openstack/python-glanceclient: Show disk format vhdx in help  https://review.openstack.org/39555908:08
*** pcaruana has joined #openstack-glance08:22
*** e0ne has joined #openstack-glance08:24
*** e0ne has quit IRC08:25
*** zul has quit IRC08:33
*** zul has joined #openstack-glance08:44
*** markvoelker has quit IRC08:49
*** lujinluo has quit IRC08:59
*** zzzeek has quit IRC09:00
*** zzzeek has joined #openstack-glance09:00
*** lin_yang has quit IRC09:13
*** mvk has quit IRC09:13
*** mvk has joined #openstack-glance09:15
*** openstackgerrit has quit IRC09:18
*** openstackgerrit has joined #openstack-glance09:18
*** clsacramento has joined #openstack-glance09:21
*** rvasilets___ has quit IRC09:38
*** udesale has quit IRC09:45
*** markvoelker has joined #openstack-glance09:49
*** markvoelker has quit IRC09:55
*** udesale has joined #openstack-glance09:56
*** exploreshaifali has quit IRC10:10
*** e0ne has joined #openstack-glance10:19
*** udesale has quit IRC10:53
*** foutatoro has joined #openstack-glance11:04
foutatoroHi all, I would like to know how to disable cloud-init config at the launch of instances in order to get them ready as fast as possible?11:13
*** mvk has quit IRC11:16
*** houming has joined #openstack-glance11:40
*** pdeore has quit IRC11:42
*** nicolasbock has joined #openstack-glance11:42
*** links has quit IRC11:43
*** foutatoro has quit IRC11:45
*** smatzek has joined #openstack-glance11:47
*** mvk has joined #openstack-glance11:47
*** smatzek has quit IRC11:49
*** houming has quit IRC11:49
*** markvoelker has joined #openstack-glance11:51
*** markvoelker has quit IRC11:55
*** abhishek_k has joined #openstack-glance12:02
*** catintheroof has joined #openstack-glance12:28
*** bkopilov_ has quit IRC12:31
*** walharthi has joined #openstack-glance12:50
*** walharthi has quit IRC12:54
*** e0ne has quit IRC12:56
*** e0ne has joined #openstack-glance12:56
*** pdeore has joined #openstack-glance12:59
*** ducttape_ has joined #openstack-glance13:08
*** ratailor has quit IRC13:12
*** pdeore has quit IRC13:12
*** edmondsw has joined #openstack-glance13:18
*** walharthi has joined #openstack-glance13:22
*** croelandt has joined #openstack-glance13:28
*** markvoelker has joined #openstack-glance13:28
*** prateek has quit IRC13:34
*** ducttape_ has quit IRC13:35
*** ducttape_ has joined #openstack-glance13:35
*** ducttape_ has quit IRC13:40
openstackgerritmelissaml proposed openstack/glance-specs: Fix a typo in artifact-repository.rst  https://review.openstack.org/39748213:55
*** prateek has joined #openstack-glance14:00
*** udesale has joined #openstack-glance14:00
croelandtjokke_: don't we have a meeting now?14:05
rosmaitacroelandt: i think i was going to re-start next week after O-114:07
rosmaitabut, i'm here, so we can meet anyway14:08
croelandtoh right14:08
croelandtok, I only read half of my mails14:08
croelandtgood, I have a ton of stuff on the way right now :D14:08
rosmaitathat's ok, i;m way behind14:08
rosmaitaok, let's meet next week, is 14:00 UTC still good for you?14:09
openstackgerritMerged openstack/glance-specs: Fix a typo in artifact-repository.rst  https://review.openstack.org/39748214:09
*** jaosorior has joined #openstack-glance14:11
*** ducttape_ has joined #openstack-glance14:13
*** pcaruana has quit IRC14:13
*** ducttape_ has quit IRC14:18
croelandtrosmaita: yep, ok with me14:29
*** bkopilov_ has joined #openstack-glance14:29
rosmaitacroelandt: ok, cool14:32
*** jaosorior has quit IRC14:36
*** ducttape_ has joined #openstack-glance14:40
*** ducttape_ has quit IRC14:52
*** groen692 has joined #openstack-glance14:54
*** udesale has quit IRC14:54
*** walharth_ has joined #openstack-glance14:57
*** walharthi has quit IRC14:58
*** exploreshaifali has joined #openstack-glance14:58
*** ducttape_ has joined #openstack-glance15:01
*** jdillaman1 has quit IRC15:05
*** groen693 has joined #openstack-glance15:05
*** groen692 has quit IRC15:06
*** groen693 is now known as groen69215:06
*** prateek has quit IRC15:07
*** exploreshaifali has quit IRC15:10
*** jdillaman has joined #openstack-glance15:10
sigmavirusrosmaita: I've got our ducks in a row: https://review.openstack.org/39779315:24
openstackgerritTomislav Sukser proposed openstack/glance: IPv6 fix in Glance for malformed URLs.  https://review.openstack.org/39779415:24
openstackgerritTomislav Sukser proposed openstack/glance: IPv6 fix in Glance for malformed URLs.  https://review.openstack.org/39779715:29
openstackgerritHemanth Makkapati proposed openstack/glance: Port Glance Migrations to Alembic  https://review.openstack.org/38295815:30
rosmaitasigmavirus: ty15:33
rosmaitajokke_: when you have a minute, can you let me know what you think of my reply to you on https://review.openstack.org/#/c/396919/1 ?  Thanks!15:48
*** openstackgerrit has quit IRC15:48
*** openstackgerrit has joined #openstack-glance15:48
*** tsymanczyk has joined #openstack-glance15:49
tsymanczykjokke_ : could you please clarify your last comment on this patchset? https://review.openstack.org/#/c/369110/ "Now when the translation files are not touched anymore that is my only major concern about this change."? I fixed that yesterday, as far as I know. What is it that you still don't like? The .po aren't touched anymore.15:51
sigmavirustsymanczyk: jokke_'s concerns are on rosmaita's spec update (dealing with "shared" being the default15:51
tsymanczyksigmavirus : that part of his comment, sure. i'm just confused about the quoted part.15:52
openstackgerritHemanth Makkapati proposed openstack/glance: Testing changes required with Alembic move  https://review.openstack.org/39740915:52
tsymanczykit reads to me as if i did not fix the translation files correctly15:52
rosmaitatsymanczyk: i think he means he's fine with what you have now15:52
rosmaitaexcept that he disagrees about the 'shared' as default15:52
tsymanczykok. just making sure there's nothing waiting on me.15:53
*** rrecio_ has joined #openstack-glance15:53
sigmavirusI interpret that the same as rosmaita15:53
rosmaitatsymanczyk: thanks for checking15:53
rosmaitasigmavirus: thanks for the confirmation!15:54
sigmavirustsymanczyk: I'll stop the world and wait on you15:54
rosmaitaisn't that a song from the 80s?15:54
* sigmavirus butchers songs for jokes15:54
tsymanczykokay yeah, if "when" were "that" i can read it the same.15:54
sigmavirusrosmaita: winner winner turkey dinner!15:54
rosmaitaok, for the bonus ... the band is "Translator" ?15:54
sigmavirusUh15:55
rosmaitanope, modern english15:55
sigmavirusyeah15:55
sigmavirusthat's what I thought (modern english)15:55
sigmavirusrosmaita: well you lost the stuffing15:55
sigmavirusbut here's a turkey!15:55
* sigmavirus throws raw turkey at rosmaita 15:55
* rosmaita catches salmonella15:55
* rosmaita is no longer optimistic about anything after last week15:56
*** jdillaman has quit IRC15:56
sigmavirusrosmaita: one of my oregon trail characters dies of salmonella15:56
rosmaitatsymanczyk: let me know what you think of my proposal, last comment on https://review.openstack.org/#/c/39691915:58
rosmaitai mean what you think conceptually, i don't mean i'm going to ask you to do it15:58
*** TravT has joined #openstack-glance15:58
rosmaitamy proposal would be to merge what's in your current patch in O-1, and then follow up with the suggested change for O-215:59
*** nicolasbock has quit IRC16:01
*** pcaruana has joined #openstack-glance16:02
*** jdillaman has joined #openstack-glance16:05
tsymanczykrosmaita : remind me, please. in the current codebase if you filter on visibility=private does it only give you private visilibility / nothing shared? and visibility=shared only gives you shared / nothing private?16:05
*** nicolasbock has joined #openstack-glance16:05
rosmaitatsymanczyk: i believe that visibility=private gives you all the images you own, so if you are the image owner of shared images (that is, images that you are sharing *out* to other users), those images will show up in the response16:08
rosmaitabut if you are an image consumer, the images shared with you will *not* show up in a visibility=private request16:08
rosmaitaif you select visiblity=shared, you only get images that are shared with you (currently)16:09
tsymanczykrosmaita : so would it be valid for me to (speciously) make the exact same opposite argument against the current codebase? where i could spend hours and hours adding members to a bunch of my images, do an image list, and be horrified to see that they're all "still private"?16:09
rosmaitaand that are accepted16:09
openstackgerritTomislav Sukser proposed openstack/glance: IPv6 fix in Glance for malformed URLs.  https://review.openstack.org/39494616:10
rosmaitatsymanczyk: i think that's right, that's why some people have filed bugs about visibility==shared not showing up in an image response16:10
tsymanczykrosmaita : i think your proposed solution would be a fine one (for someone else to implement :) ). the complication you point out with private visibility doesn't concern me since if a person is using that filter, they must already be aware of the changeset from the release notes or other. and if they're already aware of it and the docs were clear - then they16:14
tsymanczykdon't really have an excuse for confusion. (imo)16:14
rosmaitatsymanczyk: cool, thanks16:15
tsymanczyki don't even really disagree with his issue, but it's odd to me to block a change this late in the game for a complaint that can be equally made about the current codebase. if we were making things WORSE, then okay yeah sure block it. but status quo? c'mon.16:15
rosmaitayes, we get some nonintuitive behavior no matter what, so my preference is to go with what makes the most sense16:16
rosmaitabut that's kind of in the eye of the beholder16:16
*** tshefi has quit IRC16:17
tsymanczykrosmaita : i also agree re you assessment of why we shouldn't hide "has_members" from non-shared.16:18
rosmaitaok, thanks16:19
tsymanczykanyone want to make some sidebets about how this plays out re tomorrow's deadline :)16:19
rosmaitatsymanczyk: after last week, i'm not willing to make bets about anything! :)16:20
*** belmoreira has quit IRC16:22
*** kfox1111_away is now known as kfox111116:28
sigmavirustsymanczyk: rosmaita hopefully the email I just sent will get some more eyes on this16:29
*** e0ne has quit IRC16:33
*** e0ne has joined #openstack-glance16:34
rosmaitasigmavirus: ty16:37
sigmavirusIt's my job?16:37
rosmaitathat's your answer to everything!16:39
tsymanczyki appreciate the positive feedback in your email. sometimes it's easy to conflate all the -1s with nothing-but-negativity.16:39
rosmaitasigmavirus: anyway, i was just starting to write up a message to the ML, so you saved me some time16:40
sigmavirustsymanczyk: the trick is that I don't want anyone to feel like they've done something wrong16:40
rosmaitatsymanczyk: yes, please try to take this positively ... erno's not criticizing your work, he's worried about the effect the change will have on consumers16:41
sigmavirusRight, this isn't personal16:41
sigmavirusI've done this to others as well16:41
sigmavirusIt's kind of a trademark of Glance16:41
sigmavirusmostly because our preliminary communication is often not thorough enough and we don't know how to improve upon it16:41
rosmaitamaybe we need a -2-with-a-smile vs -2-with-a-frown ratings16:41
sigmavirusAlso Glance is not a priority at any company, so all of us are kind of limited in the amount of time we can squirrel away to do reviews in a timely manner16:42
*** ckonstanski has joined #openstack-glance16:59
*** haplo37 has quit IRC17:03
*** groen692 has quit IRC17:03
* stevelle is trying to catch up with the latest on this17:06
* rosmaita is looking forward to stevelle's input17:07
* stevemar pokes a bunch of glancers17:15
stevemarglancites?17:16
stevemarwhat do you call yourselves?17:16
stevemarcan i get another look at https://review.openstack.org/#/c/396695/17:16
stevemarits searchlight, but it seems like a lot of overlap between the two groups17:16
*** e0ne has quit IRC17:21
tsymanczyki prefer glancistas17:22
*** mvk has quit IRC17:38
jokke_tsymanczyk, sigmavirus, rosmaita: yes indeed, the shared by default is my only concern left17:41
tsymanczykcool. thanks for confirming.17:43
*** haplo37_ has joined #openstack-glance17:44
jokke_tsymanczyk: sorry that I did not catch that earlier ... just too busy on too many things17:44
*** walharth_ has quit IRC17:47
*** lin_yang has joined #openstack-glance17:48
tsymanczyki appreciate your insightful feedback regardless.17:48
jokke_tsymanczyk: to explain the translations part. The translation functions flags the changed strings to the translations team. Who in change work the correct translations and we will get automated patch providing a) removed strings from the .po-files if they are not translated in time and the strings not used anywhere in our project b) corrected translations for the new strings17:49
jokke_tsymanczyk: so we should never touch the .po files manually. They all gets synced from the translation system used by the translators17:50
tsymanczykperfect. i hadn't understood that, thanks for spelling it out.17:51
jokke_tsymanczyk: no problem, I thought that would be the case when I saw your question about it17:58
jokke_just forgot to put that on the comments in the review17:58
openstackgerritMerged openstack/python-glanceclient: Move old oslo-incubator code out of openstack/common  https://review.openstack.org/39478017:58
openstackgerritDharini Chandrasekar proposed openstack/glance-specs: Return 409 if removing/replacing image locations.  https://review.openstack.org/36819218:00
*** hemanth is now known as hemanth|lunch18:04
openstackgerritAlexander Bashmakov proposed openstack/glance: Add expand/contract commands to glance-manage CLI.  https://review.openstack.org/39299318:06
openstackgerritAlexander Bashmakov proposed openstack/glance: Port Glance Migrations to Alembic  https://review.openstack.org/38295818:06
*** e0ne has joined #openstack-glance18:11
*** Dong_Zhi has joined #openstack-glance18:22
*** e0ne has quit IRC18:23
*** e0ne has joined #openstack-glance18:37
*** harlowja has quit IRC18:38
tsymanczykstevelle: i have not formed an opinion yet, need to think further - but your 'shared' v 'sharable' idea is interesting. bloody interesting.18:42
*** hemanth|lunch is now known as hemanth18:42
stevelletsymanczyk: :shrug: let's see where it goes. I think we might be able to build a patch on your current to get there but I'm not entirely clear how it would work yet.18:42
*** walharthi has joined #openstack-glance18:57
*** rcernin has joined #openstack-glance19:02
*** harlowja has joined #openstack-glance19:06
*** walharthi has quit IRC19:09
*** e0ne has quit IRC19:31
tsymanczykspitballing here.... i agree that if we release it as is, SOMEBODY is going to have the bad day that jokke_ predicts ("what do you mean all my images are SHARED!? this is a disaster!"). but what if, at least for now, we were to rename the state unilaterally to "sharable" ? just the literal word "shared" means something very specific (this image IS BEING19:36
tsymanczykSHARED). "sharable" implies no su ch thing. since the users already know that "private" means "potentially shared" - having the new equivalent state literally be "sharable" would be a lateral move. no?19:36
tsymanczykthis would not be intended to prevent or subvert any of the suggestions already posed which add value for the future. (shared v sharable, searching via membership, etc)19:38
*** bpokorny has joined #openstack-glance19:49
openstackgerritOpenStack Proposal Bot proposed openstack/glance: Updated from global requirements  https://review.openstack.org/39790519:49
*** bpokorny has quit IRC19:49
*** bpokorny has joined #openstack-glance19:50
*** ckonstanski has quit IRC20:00
*** ckonstanski has joined #openstack-glance20:04
*** flwang1 has quit IRC20:06
*** TravT has quit IRC20:10
rosmaitatsymanczyk: you may be onto something ... maybe instead of 'shared' we should name the visibility 'nonprivate'20:10
rosmaitabut maybe 'sharable' is better, then instead of has_members, we could have is_shared20:12
alex_bash"shareable" is better20:12
*** e0ne has joined #openstack-glance20:13
alex_bashit's more intuitive for the user to understand that their images are shareable after upgrade, but not necessarily shared20:17
rosmaitayes, but once they are shared, the will still show as 'shareable'20:23
rosmaitaplus, the image-list filter is visibility=shared20:23
rosmaitasince 2.2, i think20:24
stevellerosmaita and tsymanczyk that is in the range of stuff I wanted to see discussed, happy to see it might not be as terrible as I feared :)20:36
alex_bashthen let's make shareable a separate field in the schema and remove 'shared' completely from visibility20:37
stevellethat might be a step too far :)20:37
alex_bashdefault to visibility=private, shareable=True20:37
stevellebut I'm trying to make lunch so ...20:37
*** walharthi has joined #openstack-glance20:38
tsymanczykoh geez, i'd be against that. a separate column would be warranted if shareable had any meaning for a visibility other than private - but under the current paradigm what would it mean for a public image to have sharable=true or false? community? if the shareable flag only impacted the private visibility state, i'd argue that we'd get the same affect by20:52
tsymanczykrenaming 'shared' to 'private-kinda' (or whatever).20:52
*** bpokorny has quit IRC20:52
tsymanczykrosmaita : regarding showing has-been-shared images still as 'shareable' for now doesn't concern me, as it's equivalent to what happens today (they show up as 'private' with or without members) - and just the literal word 'sharable' doesn't directly state that it isn't already being shared. the 'shared' filter ... hmm... that does make things less clean.20:58
*** takedakn has joined #openstack-glance20:59
*** takedakn has quit IRC20:59
*** bpokorny has joined #openstack-glance20:59
tsymanczykinternally though, even in the future if we did sharable v shared, i would expect that the actual visibility value in the database row would not change? internally it would be "shared" either way, the difference in display value would depend on whether or not the image has members. no?21:00
rosmaitatsymanczyk: that's what i'm thinking, too, but I'm not 100% sure21:00
rosmaitadoes it make sense to filter your image list by 'shareable' in addition to 'shared' ?21:02
*** MattMan has quit IRC21:02
*** MattMan has joined #openstack-glance21:03
tsymanczyki can certainly see a case where a person would want all their images that are currently-being-shared. other than contrived examples, i'm not sure why i'd want to see "all my images that are sharable but not-currently"...21:03
*** e0ne has quit IRC21:04
rosmaitaon your current implementation, if I want to see the shared images that I own, what query do i make?21:04
tsymanczykbut going back to your idea from this morning, if the visibility value were 'sharable' - period - then we added the "has_members" filter, that'd address both cases with a single visibility. just alias shared / sharable to each other filterwise maybe21:04
tsymanczykvisibility=shared&owner=pretty_me21:04
rosmaitaok21:05
tsymanczyki think i like your idea more and more21:06
tsymanczykvisibility=sharable&owner=pretty_me&has_members=true21:06
tsymanczykwhat's wrong with that?21:06
openstackgerritDharini Chandrasekar proposed openstack/glance-specs: Return 409 if removing/replacing image locations.  https://review.openstack.org/38895021:06
rosmaitawell, the only thing is that we already have visibility=shared is already defined in the API21:06
tsymanczykhave a little piece of code that silently interprests shared as sharable21:07
tsymanczyklet them specify either one21:07
tsymanczykwe've done grosser things for backwards compat21:07
rosmaitathe problem is, if we call it 'shared', then people wonder, is it already available to other people, and if we call it 'shareable', the owner wonders the same thing21:08
*** ccesario has joined #openstack-glance21:09
tsymanczykare you sure about that? the users already live in a world where 'private' doesn't mean PRIVATE.  if anything i'd think 'shareable' is less ambiguous.21:09
tsymanczyki'm totally onboard with jokke's issue though. 'shared' would scare people.21:10
rosmaitayeah21:12
rosmaitaso you like 'shareable' as the visibility identifier, plus adding has_members or member_count to indicate whether it's actually available to other users or not21:12
tsymanczykof all the options i'm aware of, that seems to me to be the cleanest. yes.21:14
tsymanczykplus, as you've already pointed out, if member_count is included as a field in all image-detail-calls, then (as you already implied earlier?) it addresses the nagging potential issue where non-shared images still maintain their user lists / but non-shared they're inaccessible. so a person with a currently private image when switching to 'shared' has no way21:16
tsymanczykto know ahead of time (short of db inspection) how many, if any, members they're going to START with.21:16
tsymanczykhm.... it's kind of gross though.21:19
* alex_bash is worried about the complexity of the db trigger growing exponentially21:19
tsymanczykif we SHOW the user that this private image has a non-zero member count, then we're kind of being .... arbitrary? by not allowing them to edit it.21:20
tsymanczykotherwise it's "here is the situation - you can't DO anything about it. but here it is."21:20
rosmaitawell, you can do something, but you have to change the visibility first21:21
rosmaitaproblem is that you can't remove members unless you make the image in viz shared21:21
rosmaitawhich opens the image to someone you don't want to have it until you remove them21:22
tsymanczyki'm worried we're about to step into the rabbit hole that we explicitly jumped over for the original spec. the "state-transition-affect-on-member-list" section that was deemed complex enough to warrant its own spec later on.21:22
rosmaitayeah21:23
tsymanczykwould it be so bad if we let people edit the membership list regardless of visibility? things got complicated back then because we were expecting to use the same table and mechanism for community images bookmarking.21:23
tsymanczykif it were CLEAR that "the membership list of any private/public/community image can be editted but has no effect at all outside of the shared visibility" - then ... maybe?21:24
rosmaitai think you are right that this is a rabbit hole we should avoid ATM21:24
tsymanczykdone21:25
*** hemanth is now known as hemanth|away21:26
tsymanczykokay, realistically, speaking only about the one very real current objection.21:27
tsymanczykswitching from the word 'shared' to the word 'sharable', and internally aliasing shared/sharable to be the same... what is lacking in that solution? it addresses the immediate problem, and leaves the future plans wide open.21:27
rosmaitasuppose we go with viz='shareable' and has_members=<bool> on the image object21:27
tsymanczyk(to be the same visibility filter wise)21:27
rosmaitaright21:28
tsymanczykeven if the operator panics, not understanding the literal word, they're two calls away from seeing that nothing has changed. (has_members=false, has_members=true).21:31
tsymanczykthat's not awful21:31
*** pcaruana has quit IRC21:32
stevelleI'm pretty happy with 'shareable' as the visibility identifier, plus (later) adding has_members or member_count.  I'm not adverse to allowing DELETE of members on private images also.21:38
tsymanczykif this is the path forward, i can take care of pushing a new patchset immediately.21:41
stevelleif we can get feedback from jokke_ first that would be helpful.21:42
*** walharthi has quit IRC21:43
*** flwang1 has joined #openstack-glance21:49
tsymanczyknot that this should affect anyone's decisions or process, but after O-1 is cut, i won't be nearly as available or responsive. i've argued to my company "for this time now" so i can make a clean break for the future rather than devoting ~X% a week to polishing this forever.21:52
tsymanczykon the assumption that being extremely-responsive now would give the best chance of merging into o-121:53
*** walharthi has joined #openstack-glance21:54
*** harlowja has quit IRC21:55
stevelleit's really helpful that you have been able to continue being responsive still, tsymanczyk.21:59
rosmaitatsymanczyk: i second what stevelle said22:03
tsymanczykthank you both - i'm happy to do it, i want to see this succeed. i'm just saying the real world is about to cave in on me.22:04
*** harlowja has joined #openstack-glance22:13
*** mvk has joined #openstack-glance22:14
*** catinthe_ has joined #openstack-glance22:18
*** catintheroof has quit IRC22:21
*** walharthi has quit IRC22:27
*** catintheroof has joined #openstack-glance22:35
*** catinthe_ has quit IRC22:36
*** edmondsw has quit IRC22:36
*** rcernin has quit IRC22:42
*** rrecio_ has quit IRC23:05
*** walharthi has joined #openstack-glance23:08
*** ducttape_ has quit IRC23:27
*** ckonstanski has quit IRC23:39
*** ckonstanski has joined #openstack-glance23:40
*** lujinluo has joined #openstack-glance23:46
*** catintheroof has quit IRC23:52
*** catintheroof has joined #openstack-glance23:54
*** bpokorny has quit IRC23:55
*** catintheroof has quit IRC23:58

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!