Friday, 2016-09-23

*** ducttape_ has joined #openstack-glance00:14
*** ducttape_ has quit IRC00:15
*** ctrath has joined #openstack-glance00:15
*** ducttape_ has joined #openstack-glance00:15
*** btully has quit IRC00:19
*** ctrath has quit IRC00:20
*** btully has joined #openstack-glance00:21
*** ducttape_ has quit IRC00:40
*** mtanin___ has joined #openstack-glance00:52
*** mtanino has quit IRC00:53
*** markvoelker has joined #openstack-glance00:55
*** btully has quit IRC00:56
*** btully has joined #openstack-glance00:57
*** liwei has joined #openstack-glance00:58
*** bpokorny_ has joined #openstack-glance01:00
*** jamielennox is now known as jamielennox|away01:03
*** bpokorny has quit IRC01:04
*** bpokorny_ has quit IRC01:05
*** namnh has joined #openstack-glance01:07
*** ducttape_ has joined #openstack-glance01:09
*** lujinluo has quit IRC01:09
*** lujinluo has joined #openstack-glance01:10
*** ducttape_ has quit IRC01:13
*** ducttape_ has joined #openstack-glance01:16
*** lujinluo has quit IRC01:17
*** jamielennox|away is now known as jamielennox01:22
openstackgerritliwei proposed openstack/glance: Add more resource url in readme.rst  https://review.openstack.org/36552501:27
openstackgerritliwei proposed openstack/glance: Correct url in doc source  https://review.openstack.org/36816801:31
*** hemanthm|afk is now known as hemanthm01:39
*** btully has quit IRC01:40
*** btully has joined #openstack-glance01:41
*** ducttape_ has quit IRC02:01
openstackgerritJin Li proposed openstack/glance-specs: change the example URLs in narrative-style API docs for glance-specs  https://review.openstack.org/35378702:05
*** tsymanczyk has quit IRC02:13
*** mtanino has joined #openstack-glance02:16
openstackgerritJin Li proposed openstack/glance: change the example URLs in api-ref for Glance  https://review.openstack.org/35367602:17
*** mtanin___ has quit IRC02:17
*** ducttape_ has joined #openstack-glance02:19
*** mtanino has quit IRC02:22
*** TravT has joined #openstack-glance02:33
*** mugsie has quit IRC02:33
*** mugsie has joined #openstack-glance02:35
*** jamielennox is now known as jamielennox|away02:37
*** jamielennox|away is now known as jamielennox02:51
openstackgerritTony Xu proposed openstack/glance: Fixed a W503 pep8 issue  https://review.openstack.org/37520402:53
*** ducttape_ has quit IRC03:01
openstackgerritliwei proposed openstack/glance_store: Remove debtcollector in requirements.txt  https://review.openstack.org/37520603:03
*** btully has quit IRC03:04
*** david-lyle has quit IRC03:04
*** btully has joined #openstack-glance03:05
*** btully has quit IRC03:11
*** btully has joined #openstack-glance03:12
*** prateek has joined #openstack-glance03:19
*** mtanino has joined #openstack-glance03:26
*** namnh has quit IRC03:31
*** mtanino has quit IRC03:41
*** sdake has quit IRC04:02
*** GB21 has joined #openstack-glance04:10
*** prateek has quit IRC04:47
*** flwang1 has quit IRC04:55
*** bhagyashri has quit IRC05:01
*** sabari has quit IRC05:17
*** pdeore has joined #openstack-glance05:28
*** bhagyashri has joined #openstack-glance05:35
*** sabari has joined #openstack-glance05:36
*** lujinluo has joined #openstack-glance05:40
*** groen692 has joined #openstack-glance05:51
*** groen692 has quit IRC05:52
*** groen692 has joined #openstack-glance05:55
*** prateek has joined #openstack-glance05:57
*** prateek has quit IRC06:01
*** prateek has joined #openstack-glance06:01
*** rcernin has joined #openstack-glance06:15
*** aswadr_ has joined #openstack-glance06:25
*** GB21 has quit IRC06:45
*** rrecio_ has quit IRC06:45
*** GB21 has joined #openstack-glance06:57
*** ejat has joined #openstack-glance07:05
ejathi .. what is the replacement for --copy-from option in image v2 ?07:06
openstackgerritliwei proposed openstack/glance: Rename get_repo to get_image_repo in gateway.py  https://review.openstack.org/36267907:26
openstackgerritliwei proposed openstack/glance: Change SafeConfigParser into ConfigParser  https://review.openstack.org/36840507:27
openstackgerritliwei proposed openstack/glance: Add programming language python3 in classifier  https://review.openstack.org/35390507:28
*** dshakhray has joined #openstack-glance07:29
*** zzzeek has quit IRC08:00
*** zzzeek has joined #openstack-glance08:00
*** dshakhray has quit IRC08:08
Jokke_ejat: there isn't, at least yet08:30
openstackgerritYAMADA Hideki proposed openstack/glance_store: Sheepdog: fix command execution failure  https://review.openstack.org/36556408:39
*** GB21 has quit IRC08:42
*** GB21 has joined #openstack-glance08:46
*** lujinluo has quit IRC08:57
*** openstackgerrit has quit IRC09:03
*** openstackgerrit has joined #openstack-glance09:03
*** GB21 has quit IRC09:06
*** dshakhray has joined #openstack-glance09:20
openstackgerritJuan Antonio Osorio Robles proposed openstack/python-glanceclient: Send HTTP headers with hyphens to API server  https://review.openstack.org/37535709:42
*** jaosorior has joined #openstack-glance09:47
*** GB21 has joined #openstack-glance09:49
*** Dinesh_Bhor has joined #openstack-glance09:54
*** TravT has quit IRC10:04
*** liwei has quit IRC10:15
*** GB21 has quit IRC10:53
jaosoriorJokke_: hey, so I ended up stumbling on a bug that you were assigned to https://bugs.launchpad.net/glance/+bug/1276887 and took a stab at it https://review.openstack.org/#/c/375357/ can you check it out?11:07
openstackLaunchpad bug 1276887 in Glance "Glance uses underscores in header names - stripped by many proxies" [High,Opinion] - Assigned to Erno Kuvaja (jokke)11:07
*** ccesario has joined #openstack-glance11:09
*** smatzek has joined #openstack-glance11:12
Jokke_jaosorior: will do11:17
*** smatzek has quit IRC11:17
jaosoriorJokke_: thanks11:17
*** aswadr_ has quit IRC11:22
*** sabari has quit IRC11:56
*** zul has quit IRC12:07
*** GB21 has joined #openstack-glance12:07
*** pdeore has quit IRC12:08
*** catintheroof has quit IRC12:08
*** sabari has joined #openstack-glance12:23
*** prateek has quit IRC12:26
sigmavirusjamielennox: so there's no good replacement then?12:28
*** zul has joined #openstack-glance12:32
*** rcernin has quit IRC12:38
*** takedakn has quit IRC12:42
*** ducttape_ has joined #openstack-glance12:44
*** pcaruana|afk| has joined #openstack-glance12:44
*** ducttape_ has quit IRC12:45
*** ducttape_ has joined #openstack-glance12:46
*** sdake has joined #openstack-glance12:48
*** GB21 has quit IRC12:54
*** david-lyle has joined #openstack-glance12:56
*** prateek has joined #openstack-glance12:58
*** pcaruana|afk| has quit IRC13:00
*** pcaruana has quit IRC13:01
*** pcaruana has joined #openstack-glance13:02
*** rcernin has joined #openstack-glance13:05
*** prateek_ has joined #openstack-glance13:06
*** prateek has quit IRC13:07
*** e0ne has joined #openstack-glance13:11
*** jaosorior has quit IRC13:13
*** e0ne has quit IRC13:14
*** jaosorior has joined #openstack-glance13:14
*** mtanino has joined #openstack-glance13:19
*** parora has joined #openstack-glance13:22
*** e0ne has joined #openstack-glance13:22
*** prateek_ has quit IRC13:24
*** ctrath has joined #openstack-glance13:25
*** prateek_ has joined #openstack-glance13:25
*** rcernin has quit IRC13:26
*** parora has quit IRC13:27
*** parora has joined #openstack-glance13:28
*** prateek_ has quit IRC13:32
*** pdeore has joined #openstack-glance13:34
*** ducttape_ has quit IRC13:36
*** ekarlso_ has joined #openstack-glance13:37
*** kragniz has quit IRC13:48
*** kragniz has joined #openstack-glance13:48
*** rcernin has joined #openstack-glance13:52
*** e0ne has quit IRC13:53
*** ctrath has quit IRC13:55
*** hussain_c has quit IRC13:56
*** ctrath has joined #openstack-glance13:58
*** ducttape_ has joined #openstack-glance14:02
*** ducttape_ has quit IRC14:06
*** parora has quit IRC14:06
*** ctrath has quit IRC14:19
*** ctrath has joined #openstack-glance14:24
*** TravT has joined #openstack-glance14:25
*** pdeore has quit IRC14:28
openstackgerritHemanth Makkapati proposed openstack/glance: cpu and address space limitations on qemu-img  https://review.openstack.org/37552614:36
*** pdeore has joined #openstack-glance14:48
*** rrecio has joined #openstack-glance14:48
*** rrecio_ has joined #openstack-glance14:50
*** pdeore has quit IRC14:52
*** pdeore has joined #openstack-glance14:53
*** rrecio has quit IRC14:53
*** burgerk has joined #openstack-glance14:59
*** pdeore has quit IRC15:00
*** jistr is now known as jistr|call15:03
*** ducttape_ has joined #openstack-glance15:07
*** rvasilets___ has joined #openstack-glance15:07
*** ducttape_ has quit IRC15:12
*** burgerk has quit IRC15:13
*** rcernin has quit IRC15:19
*** Dinesh_Bhor has quit IRC15:24
*** jistr|call is now known as jistr15:26
*** jistr is now known as jistr|biab15:28
*** bhagyashri has quit IRC15:30
sigmavirusrosmaita: meeting about release things?15:31
rosmaitahello release team!15:31
*** groen692 has quit IRC15:31
rosmaitasigmavirus: too quick for me!15:31
rosmaitaJokke_: yt?15:31
sigmavirusflaper87: and nikhil too, right?15:32
rosmaitanikhil: hello!15:32
rosmaitanot sure flaper87 can make it, he was traveling15:32
rosmaitai will update him via email15:32
Jokke_rosmaita: yeah15:32
nikhil\o15:33
rosmaitaJokke_: hello15:33
rosmaitanikhil: o/15:33
nikhil:)15:33
Jokke_I have not seen anything coming from the proposal bot15:33
rosmaitaok15:33
rosmaitaflaper87: yt? (just in case)15:34
sigmavirusI suspect he'd have answered me15:34
Jokke_so I'm assuming we're good. OFC I don't think we're in crazy rush so I can double check Mon morning again15:34
rosmaitacool15:34
rosmaitaso, this is for my edification15:34
* sigmavirus has forgotten what we're looking for15:34
rosmaitai haven't paid as close attention as i should, until it's necessarey15:35
Jokke_sigmavirus: translations warranting RC215:35
rosmaitaright, that's what we're looking for15:35
Jokke_ar delaying it15:35
rosmaitaother possibility would be late-breaking security bug into ocata, would ahve to be backported to stable/newton?15:36
*** jistr|biab is now known as jistr15:36
Jokke_well that. Or something other seriously critical bug wise15:36
rosmaitaok15:36
rosmaitaand then there's a possible RC3 also, is that correct?15:37
sigmavirusright15:37
Jokke_as long as time permits we "can" roll as many as we need15:37
rosmaitaok15:37
sigmavirusYeah although the Release managers might not appreciate it unless they're really critical15:37
Jokke_obviously something is seriously wrong if we need to roll 4-5 RCs15:37
rosmaitagotcha15:37
sigmavirusSo like there's a change to stable/newton proposed to stabilize how we sort drivers in our config file and I'm not sure that's suitable yet15:38
* sigmavirus was hoping Jokke_ would weigh in ;)15:38
sigmavirusJokke_: https://review.openstack.org/36505815:38
sigmavirusOh, I also fast-tracked a translations patch a couple days ago fwiw15:39
* sigmavirus was under the impression stable translation patches can get fast-tracked with one core15:39
Jokke_sigmavirus: yeah15:39
rosmaitasigmavirus: that sounds fine15:39
* sigmavirus had only seen one prior to this one15:39
Jokke_sigmavirus: was that backported and merged to Newton?15:39
Jokke_what comes to https://review.openstack.org/#/c/365058/ I'd tempted to -1 it15:40
rosmaitasigmavirus: do you have a link to the translastions patch?  (just curious to see what it looks like)15:40
sigmavirusJokke_: the translations patch? it was sent by the proposal bot15:40
sigmavirusrosmaita: hold please15:40
Jokke_I don't actually mind getting it in, but I'd like to see up to date config files with it15:40
Jokke_sigmavirus: yeah so it was targeted to master or to stable/newton?15:40
sigmavirushttps://review.openstack.org/37404115:41
sigmavirusstable/newton15:41
Jokke_cool so that's fine then15:41
Jokke_no need to worry about it15:41
sigmavirusseems to be the only one with that change-id15:41
nikhilhttps://review.openstack.org/#/q/project:openstack/glance+branch:stable/newton15:42
*** parora has joined #openstack-glance15:42
nikhilso, we definitely need a rc215:43
Jokke_yeah15:43
Jokke_In principle I'm against releasing anything at Fri but that isn't my call15:43
Jokke_;)15:43
nikhilas per http://lists.openstack.org/pipermail/openstack-dev/2016-September/104373.html15:43
nikhilwe need the rc2 before sept 2915:43
nikhilI think we'd delay it until that date and get as much as we can15:44
nikhilrather than having to spin rc315:44
rosmaitayeah, i would like to see https://review.openstack.org/371618 get in15:44
Jokke_how about I merge any translations that might come in by/at Monday and we request RC2 after merge/when sufficient people are awake/online?15:44
nikhilI saw rc2 from Ceilometer and trove and trove-dashboard already, but that's just a reference15:45
rosmaitadumb question ... how does this work? we merge, tag, and then request release team to cut rc2 ?15:45
nikhilthe above doesn't need us to rush the rc2 (but aware that community is moving fwd)15:45
nikhilrosmaita: no, it's much straightforward than that15:46
nikhilJokke_: I was thinking wednesday for rc2 though15:46
nikhilrosmaita: just need to specify the information as a gerrit review against release repo15:46
*** edmondsw has quit IRC15:46
*** ctrath has quit IRC15:46
Jokke_nikhil: that is just fine as well15:47
*** ctrath has joined #openstack-glance15:47
Jokke_nikhil: I was more worried that you wanted one now ;)15:47
nikhilrosmaita: https://github.com/openstack/releases , the README is great. and you can use https://github.com/openstack/releases/blob/master/deliverables/newton/glance.yaml and https://github.com/openstack/releases/blob/master/deliverables/mitaka/glance.yaml and https://github.com/openstack/releases/blob/master/deliverables/mitaka/nova.yaml15:47
Jokke_rosmaita: we do not tag15:47
nikhilas good references15:47
Jokke_^^15:48
rosmaitaok, thanks15:48
nikhilJokke_: ah15:48
nikhilrosmaita: the "hash" field and the "version" number are important15:48
Jokke_so the tooling around releases repo has improved hugely as well, so that's not much manual work from the release management anymore. it's all around specially formatted yamls in the repo15:49
sigmavirusyep15:49
*** parora has quit IRC15:49
Jokke_and if there is merge commit from the last commit, need to use the hash from the merge rather than the commit itself15:49
*** edmondsw has joined #openstack-glance15:49
nikhilrosmaita: only these lines will do https://github.com/openstack/releases/blob/master/deliverables/newton/glance.yaml#L59-L62 and some co-ordination with the release team (make sure to run "tox -e validate" before/in parallel when hitting git review)15:50
*** MattMan has quit IRC15:50
* nikhil shuts up15:50
*** MattMan has joined #openstack-glance15:50
nikhilJokke_ is right15:50
rosmaitaok, so wed is one day before the deadline15:50
nikhilmake sure you do a "git show" on latest stable/newton and use that hash15:51
sigmavirusrosmaita: re 371618, master hasn't merged adn I just re-reviewed that for you, sorry and you're welcome15:51
rosmaitamaybe aim for 16:00 wed? or is the gate going to be really slow because everyone else has the same plan?15:51
sigmavirusrosmaita: no clue15:51
nikhilrosmaita:  I'm okay with either, whoever is doing it needs to make sure the 4 release muskateers are aware of our plans.15:52
nikhilmusketeers*15:53
Jokke_rosmaita: the release jobs are fine and quick. and the Rel management takes care of the timing anyways15:53
rosmaitaJokke_: how does your wednesday look?15:53
rosmaitaor is this sigmavirus 's thing (i am getting confused on who's responsible for what)15:53
Jokke_14:00 to 15:00 booked15:54
nikhilrosmaita: glance-release team, we look out for each other :)15:54
Jokke_rosmaita: ping me at your Wed morning and we'll walk through it so you know the process for Ocata15:55
nikhilrosmaita: just a maybe-non-useful suggestion , if you wanted to open the mtg agenda for next week and mention rc2 tentative plans, it may hint fly-by reviewers to bring imp reviews to notice https://etherpad.openstack.org/p/glance-team-meeting-agenda15:55
rosmaitaJokke_: sounds good15:55
Jokke_unless sigmavirus insists15:55
Jokke_;)15:55
rosmaitanikhil: maybe the ML? since wed is before the meeting?15:56
nikhilrosmaita: yeah both are ideal, out developers are fragmented. some read the ML on time and some prefer mtgs :)15:57
nikhilour*15:57
sigmavirusheh, I don't insist but I can help where necessary15:57
nikhilrosmaita: but it's your call, you run the things now so no one gets to question you. muhahahah. jk :)15:58
sigmavirusnikhil: rosmaita might need to borrow your iron fist ;)15:58
nikhilrosmaita: it's hard to keep cross posting, so one most convenient place should help ;-)15:58
nikhilsigmavirus: heh :D15:58
nikhilwell the thing is...15:59
rosmaitaok, to summarize: our plan is to have rc2 ready on wed15:59
*** tsymanczyk has joined #openstack-glance15:59
rosmaitaand it looks like we need a rc2 because there have been some translations merged, and possibly more trans15:59
nikhilif we provide options people will get confortable of sourcing from either places and in case of rush someone misses a cross post we have big issue. so, better to make it a habit to stick to one particular process. whichever one it may be.16:00
rosmaitaand maybe some bugs16:00
rosmaitanikhil: understood ... my problem with the thurs meeting is that it occurs after the rc2 deadline we've set for ourselves16:00
sigmavirusI'd like to get the qemu-img review hemanthm is working on merged for rc2 but it's critical enough that it could be merged after newton is tagged too16:00
tsymanczykbuenos dias personas de glance, y bonita viernes16:00
rosmaitasigmavirus: ++16:01
nikhilrosmaita: correct, whatever gets in gets in. i18n are already there so rc2 is mandatory. if nothing more gets in, we will have it (rc2) so.16:01
rosmaitatsymanczyk: hang on a minute, please16:01
tsymanczykyeah np.16:01
rosmaitaok, so it sounds like we are ok. i will send out a ML update on RC2 after community images sync16:01
rosmaitathanks nikhil sigmavirus Jokke_ (and flaper87 wherever you are)16:02
nikhilrosmaita: yeah, I'm just saying don't make it your problem otherwise problems may pile on you. people are expected to read the final meeting agenda 24 hrs before thurs meeting anyway (re: best practices)16:02
sigmavirusyw rosmaita16:02
rosmaitanikhil: i appreciate the advice!16:02
nikhil:)16:03
rosmaitaok, thanks release team!16:04
rosmaitatsymanczyk: thanks for waiting16:04
rosmaitayou have the floor16:04
Jokke_:)16:05
tsymanczyksweet. so for everyone's reference, https://review.openstack.org/#/c/369110/ is the change we're talking about.16:05
tsymanczykit is the first of two changesets for community images - and its sole purpose in life is to replace the is_public db images column with an enum to allow for the new values.16:05
tsymanczykoverall i'm happy with the state of it (in my bubble), except for ONE remaining thing16:06
tsymanczykfor a lot of unit tests, i needed to change their success conditions from testing the dict attribute of is_public to visilibility16:06
tsymanczykand for the little fake tests that create internal dicts (fixtures) and just modify them a little, that doesn't bother me.16:07
tsymanczykbut there are a few tests that go through a full spin of the interface16:07
tsymanczykand (imo) it isn't okay that those tests needed to be altered to pass16:07
tsymanczykit has the identical consequence to an end user who has code relying on the v1 interface returning the is_public header16:07
tsymanczykthey would currently break16:07
Jokke_tsymanczyk: so we cannot break v1 to support this16:08
Jokke_if needed we need some bubblegum on the v1 code to translate that visibility back16:08
tsymanczyknow going forward, once the second patch enabling the new shared and community visibility values gets in it isn't clear to me that v1 would be able to utilize these new values at all. and especially with the new 'shared' value, i'm not sure how that's going to work with v1. but this patch at least seems like it shouldn't break v116:09
tsymanczykjokke_ agreed.16:09
rosmaitai think the idea is that community images are is_public == 016:09
tsymanczykjokke_ my current thought is to just decorate the headers as they get emitted from the v1 api with an the additional is_public value16:09
tsymanczykrosmaita : certainly. but i'm wondering without the v1 ability to set anything but true or false, how are they going to be able to specify shared / community ?16:10
rosmaitatsymanczyk: v1 users can't do it16:10
rosmaitait will be weird in installations that use both v1 and v216:10
rosmaitabut now that nova uses v2, shouldn't be much of an issue, i don't think16:11
tsymanczykrosmita : okay. how are you picturing "not breaking" v1 image sharing then?16:11
tsymanczykbecause i have no concept atm.16:11
rosmaitawell, current v1 sharing has is_public == 016:11
nikhiltsymanczyk: that's exactly I was referring to for compat layers besides any admin_as_user magic.16:11
openstackgerritDharini Chandrasekar proposed openstack/glance: Fixing inconsistency in Glance store names.  https://review.openstack.org/35940216:11
rosmaitatsymanczyk: i should prob shut up and read through this patch to get a better grasp of your concerns16:12
nikhiltsymanczyk: not breaking v1 will need some translation of the visibility understanding in terms of is_public but that is likely going to be different for different use cases.16:12
tsymanczykrosmaita : not at all. my concerns for this patch have been resolved. once i fix the headers it'll be 100% back compat. the current issue is for the next patch - since the v2 workflow is going to change to have an explicit "shared" visibility value, and v1 relies on the implicit behaviour of is_public=0 -- this ... needs some thought.16:13
nikhiltsymanczyk: for example, the is_public flag is hacked for admin_as_user but is not for simply admin.16:13
*** bkopilov has quit IRC16:14
rosmaitatsymanczyk: i think i understand the problem16:14
nikhilanyway, I am sorta in this state where I've seen the patch details just enough to realize this is the right direction but still pondering conceptually of what the code needs to look like.16:15
tsymanczyknikhil : thanks for reminding me. the last issue i wanted to bring up is that i'm going to need explicit instruction on how to utilize your kind guide in the etherpad. regarding the difference between user-admin and glance-admin -- my only understanding is when "this" user has the "admin" role. how that applies to user-admin and glance-admin and the16:15
tsymanczykdifference between the two is lost to me.16:15
rosmaitav1 sharing uses membership only, v2 will use memberhip + visibility16:15
nikhilthis is certainly induction effect of markwash!16:15
tsymanczykrosmaita : exactly.16:15
tsymanczykthere may be some gross hacky code until v1 dies.16:15
rosmaitaso if we dont' adjust v1, images wiht members will show up as shared in v1 but not in v216:15
rosmaitagotcha16:15
tsymanczykcertainly nobody wants that, but as discussed earlier we certainly can't break v1.16:16
rosmaitai think gross hacky code on a deprecated api is acceptable (and i said that in a logged channel!)16:17
tsymanczyk:)16:17
nikhiltsymanczyk: yep yep yep! the gross hacky code needs to live outside of the regular modules please!!!! we need strong documentation of the hacks / why, when, where/ and keep them packed in a separate packing-box, just like we've moved the house but don't want to open that box!16:17
rosmaitain the release notes we can say, if you intend to use community images, we strongly suggest that you have a v2-only glance deployment16:17
tsymanczykcertainly. i have no interest in leaving mystery work for whoever succeeds me.16:18
*** jistr is now known as jistr|afk16:18
nikhilwell...if hierarchical images is next, guess who's that!?16:18
nikhil:D16:18
tsymanczykin even the most perfect of worlds, i can't picture how v1 would ever actaully allow the use of the community value. right now my goal is to not break shared behaviour.16:18
tsymanczyksanta claus?16:19
rosmaitatsymanczyk: that's the correct goal16:19
tsymanczykwhen will v1 officially be flushed?16:19
nikhiltsymanczyk: totally on translating the membership+visibility understanding separately for v1 (hint hint: the compat layer)16:19
nikhiltsymanczyk: To be *really* honest, never. but optimistically, 2-4 years.16:20
tsymanczykactually one more question / clarification. so the plan is yes to ensure "is_public" gets emitted by the v1 api, yes? And beyond that, should I trim out the visibility value? or is having that one new value also there cool and/or desired?16:21
*** jaosorior has quit IRC16:21
nikhil(we say pike http://docs.openstack.org/releasenotes/glance/newton.html#deprecation-notes , but that's just being hopeful)16:21
Jokke_no we should not send visibility in v116:21
rosmaitatsymanczyk: we dont' emit visibility now, do we? (in v1 response)16:21
rosmaitaJokke_: ++16:21
nikhil== Jokke_16:21
tsymanczykin the current state, (to the best of my understanding) we emit is_public in v1 but not visibility. then v2 we emit visibility but not is_public.16:22
rosmaitadon't want to encourage people to hack something together16:22
tsymanczykokay cool. i'll take care of both of those things then.16:22
Jokke_thanks tsymanczyk!16:22
rosmaitatsymanczyk: ok, that was my understanding ... so no visibility for v1 !16:22
tsymanczykthank you jokke_.16:22
rosmaitaif you want visibility, you must upgrade to v216:22
rosmaitayou == operators16:22
Jokke_these two discussions back to back just made my Fri lots better ;)16:22
tsymanczykso the only other blocker i have re this patch is instructions on user-admin / glance-admin, and how to do these in devstack. i really am lost on how to do a FULL manual test for these cases.16:23
tsymanczykonce those two things are cleared then i'll stop -1wf16:23
nikhilthe admin that ships with devstack is the project/glance-admin16:24
tsymanczykbecause of the 'admin' role? or being in the admin project?16:24
nikhilfor user admin, we will need to set owner_is_tenant=False in glance-api.conf16:24
nikhilthen see what the demo user's role is, I think it's not admin (we then need to create another user under the demo project namespace that has admin role for that tenancy).16:25
nikhildevstack has both project and user as demo, afaik16:25
nikhil'being in the admin project'16:26
nikhiloops16:26
nikhilNO16:26
nikhilbeing admin "in" the project :)16:26
rosmaitayeah, i change the name of the project to 'demo_project' otherwise it gets too confusing16:27
*** ctrath has quit IRC16:28
tsymanczyknikhil : so just to reiterate what you're saying. to test the project / glance-admin behaviour, it is only necessary to use the default 'admin' user within the admin project of a default devstack install. to test the user-admin behaviour, change owner_is_tenant=False in glance-api.conf, then assign the admin role to a user that is not 'admin'(username) ?16:28
tsymanczykand not within the admin project?16:28
nikhiltsymanczyk: yes!16:28
nikhiland yes16:28
tsymanczykperfect, thank you for being explicit.16:28
tsymanczyki think that resolves everything i wanted to bring up this time then? hopefully by next glance meeting or commimg sync the first patch will be ready for reviews.16:29
tsymanczykor perhaps already have some reviews on it. :)16:29
nikhilthis is great news!16:29
nikhilbut I'm packing and travelling in the coming days16:29
tsymanczykanything else from anyone else?16:29
tsymanczyknikhil : save travels!16:30
nikhilyeah, I may not be available for 2 weeks I think16:30
nikhiltsymanczyk: thanks!16:30
rosmaitatsymanczyk: sounds good, thanks for the update16:30
tsymanczykanytime. thank you for the great feedback.16:30
tsymanczykfeedback / input16:30
nikhilI will try to think more about the compat layer design pattern as time permits.16:31
nikhilBut I really think that you're DB change may not need it, we need to think about that for the next/community images API centric review.16:31
Jokke_sigmavirus, rosmaita, hemanthm, nikhil: ref mailing list, sorry just did not want to let that go second time.16:31
sigmavirusJokke_: hasn't come through to me yet16:32
tsymanczyknikhil : agreed. the next patch will very likely need it. but my gut feel is that this one should be able to resolve all of the extremely valid points brought up without a compat layer.16:32
nikhilme neither16:33
rosmaitaJokke_: just catching up16:33
nikhiltsymanczyk: feel free to text me for a stuck patch on a +2 (will give you my number and personal email)16:33
nikhiltsymanczyk: would love to see this moving forward rather than a patch sitting with one +2 and waiting on the other onefor weeks.16:34
tsymanczyknikhil : perfect, thank you.16:34
sigmavirusJokke_: got it, I hope my response helps clarify my intent in the email too. This wasn't to call you out.16:41
Jokke_sigmavirus: never taken as such, that one quote just jumped out second time and I hoped it was something I could just let slip ;)16:42
*** dshakhray has quit IRC16:52
*** jistr|afk is now known as jistr16:59
*** markvoelker has quit IRC17:02
*** markvoelker has joined #openstack-glance17:02
openstackgerritMerged openstack/glance: Add note to docs on release notes prelude section  https://review.openstack.org/36506317:06
*** ducttape_ has joined #openstack-glance17:08
*** catintheroof has joined #openstack-glance17:09
*** ducttape_ has quit IRC17:12
openstackgerritAlexander Bashmakov proposed openstack/glance-specs: Update ``updated_at`` field on image member change  https://review.openstack.org/37562917:14
ejatJokke_: so how can i create image from URL into glance?17:19
*** rvasilets___ has quit IRC17:28
*** ctrath has joined #openstack-glance17:32
sigmavirusnikhil: rosmaita I think dharinic updated https://review.openstack.org/#/c/359402/27 asap for us so we could approve it. Given they adjusted the release notes for us and the rest looked good, care to +2+A?17:39
openstackgerritHemanth Makkapati proposed openstack/glance: CPU and address space limitations on qemu-img info  https://review.openstack.org/37552617:49
*** ctrath has quit IRC17:51
*** ctrath has joined #openstack-glance17:55
*** btully has quit IRC17:55
*** hemanthm is now known as hemanthm|lunch17:55
*** btully has joined #openstack-glance17:56
dharinicThanks sigmavirus, hemanthm|lunch18:00
sigmavirusdharinic: good work on that btw18:01
dharinicThanks :)18:01
*** ducttape_ has joined #openstack-glance18:16
*** prateek has joined #openstack-glance18:23
*** e0ne has joined #openstack-glance18:29
*** ducttape_ has quit IRC18:31
*** e0ne has quit IRC18:43
*** e0ne has joined #openstack-glance18:47
*** hemanthm|lunch is now known as hemanthm18:50
*** dshakhray has joined #openstack-glance18:53
*** prateek has quit IRC18:55
openstackgerritHemanth Makkapati proposed openstack/glance: CPU and address space limitations on qemu-img info  https://review.openstack.org/37552619:01
rosmaitahemanthm: you are too fast!19:01
*** ckonstanski has joined #openstack-glance19:01
hemanthmrosmaita: oops, were you reviewing it?19:02
rosmaitanp19:02
hemanthmJokke_: it's all good :)19:02
rosmaitahemanthm: left a question on your patch19:08
hemanthmlooking19:09
rosmaitait may be out of scope19:09
*** david-lyle_ has joined #openstack-glance19:10
hemanthmrosmaita: let me look into what qemu-img convert is doing19:12
rosmaitathanks19:13
*** david-lyle has quit IRC19:13
*** ctrath has quit IRC19:14
*** ctrath has joined #openstack-glance19:15
*** e0ne_ has joined #openstack-glance19:16
hemanthmrosmaita: maybe #4. How about specifying the current image format with -f to the qemu-img convert command?19:17
*** e0ne has quit IRC19:17
hemanthmthat will avoid the infering19:17
*** e0ne_ has quit IRC19:17
*** catintheroof has quit IRC19:17
*** e0ne has joined #openstack-glance19:18
rosmaitahemanthm: not sure ... is that info available?19:19
*** e0ne has quit IRC19:19
*** e0ne_ has joined #openstack-glance19:19
rosmaitaalso, i wonder whether it needs to read info out of the image even if it knows what the format is19:19
*** e0ne_ has quit IRC19:19
hemanthmrosmaita: in that case, we are doomed isn't it?19:19
rosmaita(i may have been misleading by focusing on the info call)19:19
rosmaitahemanthm: probably19:20
rosmaitai think we can do a probe by making  the info call with limits19:20
hemanthmrosmaita: yeah, I'm open to doing that19:20
*** e0ne has joined #openstack-glance19:20
rosmaitabut, we probably need to allow limits to be set for the actual conversion19:20
rosmaitain case something slips by with 1.9999999 CPU sec19:21
*** e0ne has quit IRC19:21
rosmaitabut that seems a bigger change19:21
hemanthmyeah19:21
rosmaitamaybe the probe + tasks are for admins is enough19:21
hemanthmalright, I'll look into adding the info call just before convert19:22
rosmaitathanks19:22
hemanthmor maybe we should reproduce the info attack with convert first19:22
rosmaitagood idea19:22
rosmaitathere are some recipes in the bug report19:23
hemanthmyeah19:23
rosmaitathat's a good idea, my concern may be misplaced19:23
hemanthmthis will probably apply to nova as well https://github.com/openstack/nova/blob/master/nova/virt/xenapi/vm_utils.py#L1128-L112919:26
hemanthmfungi ^19:26
*** burgerk has joined #openstack-glance19:27
*** ducttape_ has joined #openstack-glance19:32
*** ctrath has quit IRC19:32
fungihemanthm: can you summarize? i'm not quite sure i understand the suggestion19:33
hemanthmfungi: rosmaita pointed out that "qemu-img convert" may also try to infer the format of input image19:34
*** ctrath has joined #openstack-glance19:34
hemanthmso, is convert uses info internally, convert will also be susceptible to the same attack19:34
hemanthmto guard against it, we are planning to add an info call with process limits before we make the convert call19:35
fungihemanthm: oh, that makes sense. can you mention that in the bug report? i'll see if we can get input from nova and cinder devs to see if they need to do the same19:36
hemanthmit's all a theory at this point, I'm trying to replicate the info attack with convert19:36
fungigood deal. i guess update the bug with that once you're more sure19:37
hemanthmsure19:37
fungiwhile i want to get the advisory out soon, i want even more not to have to issue a second one because we had an incomplete fix ;)19:37
*** ducttape_ has quit IRC19:37
hemanthmfungi: commented on the bug19:42
*** thiagolib has joined #openstack-glance19:46
fungithanks!19:46
*** burgerk has quit IRC19:53
*** sdake has quit IRC20:00
openstackgerritMerged openstack/glance: Fixing inconsistency in Glance store names.  https://review.openstack.org/35940220:05
*** david-lyle_ is now known as david-lyle20:06
*** ducttape_ has joined #openstack-glance20:15
*** ducttape_ has quit IRC20:30
openstackgerritNikhil Komawar proposed openstack/glance: Move deprecated store name mapping to resp. method  https://review.openstack.org/37572220:53
*** ducttape_ has joined #openstack-glance20:54
*** ccesario has quit IRC21:06
*** ducttape_ has quit IRC21:07
*** kberger has quit IRC21:13
*** kberger has joined #openstack-glance21:13
*** thumpba has joined #openstack-glance21:31
*** ctrath has quit IRC21:44
*** thumpba has quit IRC21:46
*** kberger has quit IRC22:02
*** ducttape_ has joined #openstack-glance22:08
*** ducttape_ has quit IRC22:13
dharinicHey nikhil22:20
*** rrecio_ has quit IRC22:20
nikhildharinic: \o22:20
dharinicI had a question regarding the bug for Swift multi tenancy https://bugs.launchpad.net/glance/+bug/162507522:20
openstackLaunchpad bug 1625075 in Glance "Shared & public images no working with multi-tenant swift backend" [Critical,Triaged] - Assigned to Dharini Chandrasekar (dharini-chandrasekar)22:20
dharinicSo as we were discussing the other day, a possible way of a fix would be to have the ACL set up..22:20
dharinicI am still figuring a way to do this.. But I wanted to access the glance-db if we were to set the ACLs. I wasnt sure how to do that without editing requirements.txt22:22
nikhilyes, and I disagree with it :)22:22
nikhilI disagree with setting ACLs22:22
dharinicHmmm.. kairat had mentioned we could fix it with ACLs. So I was just looking into that.. for which we might need access to glance-db22:23
nikhilbut I also gave a reason why we shouldn't set ACLs!22:23
dharinicyess. I do remember that. :)22:24
nikhiland a pretty serious one, which has been ignored!22:24
nikhil(shame)22:24
nikhilnot necessarily on you but on the entire set of people who managed to do so22:25
dharinicAhhh not at all. I was just seeing how things work with ACLs (exploring) :D22:26
nikhildharinic: http://eavesdrop.openstack.org/irclogs/%23openstack-glance/%23openstack-glance.2016-09-22.log.html#t2016-09-22T15:04:3422:27
dharinicI do have that very link saved :)22:27
dharinicSo the issue here is that the catalog from the request context is used for authentication.. https://github.com/openstack/glance_store/blob/master/glance_store/_drivers/swift/store.py#L1279-L128322:29
dharinicso even if the sharing is public/shared, the context.tenant is still scoped to the request22:30
dharinicI was just playing around with few tests locally with respect to this for which i thought I might access glance-db and see..22:31
dharinicHence the question22:31
nikhildharinic: I don't have objections to accessing the glance-db22:32
nikhildharinic: in fact, that's what I suggest22:33
nikhildharinic: what we need is a pass by value of the sharing model to the multi tenant store logic22:33
nikhildharinic: rather than setting the ACL everytime, you see a change in glance-db membership22:34
nikhildharinic: the later being extremely racy, non-deterministic and an operation which does not provide consistency22:34
nikhil s/everytime, you see/everytime you see22:35
dharinicSo we check the db for a change in membership and update the catalog every time there is a change?22:35
nikhilwhy do you need to update the catalog22:35
nikhilyou cannot and should not22:35
nikhildharinic: andrew's patch is just replacing the tenant value while authentication (not updating the catalog)22:36
dharinicYeahh.. he fetches the storage_url and then replaces the tenant22:36
dharinicokayyy..22:37
dharinicSo coming back to the question of accessing the glance-db. How can I do it in glance_store?22:39
dharinicnikhil^22:41
nikhildharinic: you cannot and should not22:42
nikhildharinic: we will need glance pass that info to the store22:42
dharinicI know I am missing something here..22:43
dharinicAhhhh22:43
nikhilyou cannot (now) and should not (design in the future)22:43
dharinicgotcha22:43
*** cdelatte has joined #openstack-glance22:43
dharinicThank you nikhil22:46
nikhilyw22:46
nikhilgood work dharinic22:46
nikhilkeep going like this!22:46
dharinicThank you for sharing this bug with me. I am really enjoying working on this (though now I am just exploring things for this)22:47
dharinicThank you :)22:47
*** markvoelker has quit IRC22:47
*** thiagolib has quit IRC22:58
*** dshakhray has quit IRC23:01
*** tsymanczyk has quit IRC23:13
*** sdake has joined #openstack-glance23:17
*** ducttape_ has joined #openstack-glance23:18
*** ducttape_ has quit IRC23:22
*** ducttape_ has joined #openstack-glance23:41
*** ducttape_ has quit IRC23:45
nikhil:)23:46
*** markvoelker has joined #openstack-glance23:48
*** markvoelker has quit IRC23:52

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