Friday, 2018-11-16

*** Sravan has joined #openstack-glance00:01
*** Sravan has quit IRC00:05
*** _alastor_ has quit IRC00:06
*** Sravan has joined #openstack-glance00:13
*** Sravan has quit IRC00:14
*** Sravan has joined #openstack-glance00:20
*** Liang__ has joined #openstack-glance00:33
*** _alastor_ has joined #openstack-glance00:35
*** _alastor_ has quit IRC00:39
*** rmcallis has joined #openstack-glance00:42
*** rmcallis has quit IRC00:45
*** rmcallis has joined #openstack-glance00:49
*** rmcallis has quit IRC00:51
*** Liang__ is now known as LiangFang01:01
*** Sravan has quit IRC01:15
*** trident has quit IRC01:31
*** trident has joined #openstack-glance01:35
openstackgerritzhouxinyong proposed openstack/glance master: Replacing the link in HACKING.rst  https://review.openstack.org/61836801:55
*** Sravan has joined #openstack-glance02:14
*** Sravan has quit IRC02:19
*** openstackgerrit has quit IRC02:22
*** _alastor_ has joined #openstack-glance03:00
*** _alastor_ has quit IRC03:05
*** openstackgerrit has joined #openstack-glance03:06
openstackgerritLiang Fang proposed openstack/glance master: Fix for FK constraint violation  https://review.openstack.org/61788903:06
LiangFangAbhishek, thank you that you had approved my review: show store info03:20
*** udesale has joined #openstack-glance03:51
*** Sravan has joined #openstack-glance03:52
*** abhishekk has joined #openstack-glance04:25
openstackgerritLiang Fang proposed openstack/glance master: Fix for FK constraint violation  https://review.openstack.org/61788905:07
*** ratailor has joined #openstack-glance05:22
*** pooja_jadhav has joined #openstack-glance05:25
openstackgerritAbhishek Kekane proposed openstack/glance master: Data remains in staging area if 'file' store is not enabled  https://review.openstack.org/61846805:35
*** LiangFang has quit IRC06:01
*** Liang__ has joined #openstack-glance06:02
*** Sravan has quit IRC06:39
*** mosulica has joined #openstack-glance06:54
*** _alastor_ has joined #openstack-glance07:02
*** _alastor_ has quit IRC07:07
*** Sravan has joined #openstack-glance07:10
*** Sravan has quit IRC07:14
*** Luzi has joined #openstack-glance07:15
*** Sravan has joined #openstack-glance07:51
*** Sravan has quit IRC07:55
*** pcaruana has joined #openstack-glance08:39
*** udesale has quit IRC09:18
*** mosulica has quit IRC09:33
*** Liang__ has quit IRC09:43
*** openstackgerrit has quit IRC09:52
*** jmlowe has quit IRC09:53
*** w|zzy has quit IRC09:53
*** w|zzy has joined #openstack-glance09:54
*** mosulica has joined #openstack-glance10:00
*** udesale has joined #openstack-glance10:10
*** udesale has quit IRC10:21
*** abhishekk has quit IRC10:26
*** imacdonn has quit IRC11:01
*** imacdonn has joined #openstack-glance11:01
*** _alastor_ has joined #openstack-glance11:04
*** _alastor_ has quit IRC11:08
*** pooja_jadhav has quit IRC11:19
*** _alastor_ has joined #openstack-glance12:32
*** ratailor has quit IRC12:50
*** mordred has quit IRC12:55
*** rosmaita has left #openstack-glance13:26
*** rosmaita has joined #openstack-glance13:31
*** _alastor_ has quit IRC13:33
*** Sravan has joined #openstack-glance13:48
*** Sravan has quit IRC13:53
*** MattMan_ has quit IRC14:05
*** MattMan_ has joined #openstack-glance14:05
*** mosulica has quit IRC14:08
*** imacdonn has quit IRC14:52
*** Luzi has quit IRC14:56
*** _alastor_ has joined #openstack-glance14:57
*** ratailor has joined #openstack-glance15:02
*** jistr is now known as jistr|call15:29
*** ratailor has quit IRC15:39
*** pcaruana has quit IRC15:56
*** jistr|call is now known as jistr|biab15:59
*** gyee has joined #openstack-glance16:29
*** jistr|biab is now known as jistr16:43
*** imacdonn has joined #openstack-glance17:16
*** mordred has joined #openstack-glance17:21
*** Sravan has joined #openstack-glance17:33
*** Sravan has quit IRC17:34
*** Sravan has joined #openstack-glance17:34
imacdonnrosmaita: ping?19:57
*** Dinesh_Bhor has joined #openstack-glance20:00
rosmaitaimacdonn: pong20:08
imacdonnrosmaita: hi. I was having OpenStack-doc-rage .... I sortof figured it out, though20:08
rosmaitawhich docs?20:09
imacdonnI was trying to use the web-download import method, and failing to find anything that adequately describes how to do it20:09
imacdonnpart of the problem was an old version of glanceclient that made my guesses fail ... but I really shouldn't have to guess20:09
imacdonne.g. (I know this is "experimental"): https://docs.openstack.org/python-glanceclient/latest/cli/details.html#glance-image-create-via-import20:10
imacdonnthere's nothing there that says you can add: --import-method web-download --uri <foo>20:10
imacdonnand I haven't found anything that describes the multi-step process (from a user perspective) at all, for web-download20:11
rosmaitayeah, the CLI docs don't get much love20:11
imacdonnvery frustrating20:11
rosmaitawell the api-ref has a pretty good description of what's supposed to happen20:11
imacdonnI'm being a user right now :P20:11
rosmaitai always think of "user" as "API user"20:12
imacdonnthat may be a problem ... many users are just CLI users20:12
*** Dinesh_Bhor has quit IRC20:12
rosmaitaanyway, i suppose you could adapt https://developer.openstack.org/api-ref/image/v2/index.html#interoperable-image-import to the CLI20:12
imacdonn(or horizon, even... but I'm thinking of typical sysadmins in a private cloud context)20:13
rosmaitayeah, you are probably right20:13
imacdonnthe part I was getting frustrated about is "where do I put the image URI?" (when using the CLI)20:14
rosmaitai just noticed that we don't even have a link to the glanceclient CLI docs from the glance.oo.org landing page20:14
imacdonnI guess I know better than to look for a logical path to docs .. I just start with Google, cos I'll end up there anyway :)20:15
imacdonnso the reason I went on this little adventure .... I wanted to see how the "backend" appears in metadata, when using a store other than http20:17
imacdonnI'm not yet sure that using the default backend when adding a location is the right thing to do (although it will work OK for my use-case)20:17
rosmaitawell, you are right that locations are weird20:18
rosmaitabut in general, we don't want the user to have to worry about backend for the "normal" image operations20:18
rosmaitaso in that sense, having the default is consistent with general expectations20:19
imacdonnI'm thinking of a possibly typical case of having, say, swift as the default store .. for anyone randomly creating an image and needing it stored somewhere .. but also having the http store available for published images20:19
imacdonnin that case, defaulting to swift when adding locations via patch isn't really ideal20:19
rosmaitai see what you mean20:19
rosmaitawell, messing with locations should be restricted to operators anyway20:20
rosmaitaso maybe the thing to do is make them be explicit about which store they want to use20:20
rosmaitaafter all, the admin will know all the store ids etc20:21
imacdonnyeah, I kinda sorta lean that way .... except it'll introduce incompatibility20:21
rosmaitayeah, but i think you have a good point20:22
imacdonnthat's why I'm worrying about this now ... if it does go that way, I'll have to ask the developers of our provisioning system to add that metadata to their image creation proceess before we get to Stein20:22
rosmaitai mean, the whole idea of adding locations is to do something non-standard with glance's treatment of the backend20:22
rosmaitaso in that way, it makes sense to require the backend be specified20:23
imacdonnexcept there's no (other) standard way to employ the http backend .... (?)20:23
rosmaitatrue, but the http backend is a pretty weird one20:25
rosmaitabut i think the key thing here is, what makes for a good user experience?20:27
rosmaitathinking back to your swift example, i think if you try to set a http:// location for the swift backend, the call will fail because of an incorrect scheme for the store20:28
imacdonnright ... so is there any way to determine (in code) which schemes each backend supports ?20:30
rosmaitaeach store has to implement a get_schemes() method20:30
rosmaitabut there are some other restrictions, e.g., can't set a file:// or swift+config:// (for security reasons)20:31
imacdonnpondering if there could be a way to iterate over the enabled backends and pick the (first?) one that supports the scheme presented? That'd probably be a "can or worms"20:32
imacdonnof*20:32
imacdonnor have a config option like ... default_backend_by_scheme20:33
imacdonn("thinking out loud")20:33
* rosmaita is liking forcing the user to specify which backend more and more20:34
rosmaitai'm going to put a note on that bug so that erno, abhishek, and sean think about this issue20:34
imacdonnit does kinda seem like the right thing to do ... "if you're smart enough to be diddling with locations, you should be smart enough to know which backend you want"20:35
rosmaitaexactly ... i think asking glance to be smart about this is simply asking for trouble!20:36
imacdonnI'm sorta shooting myself in the foot here, because it'll be incompatible with what we've implemented for Rocky (using patch to add a location - "we" = my "day job") ... but I think there's time to get that addressed before stein20:37
imacdonnthe other thing I was wondering about ... haven't yet tested .... does the "backend" in metadata get used for anything after the image becomes active? If so, what happens to images that were created prior to enabling multi, which wouldn't have it?20:38
rosmaitathat is a good question.  I'm pretty sure if there's no backend specified, glance uses the default20:39
rosmaitaabhishek did have a proposal to look through all backends with that scheme20:40
rosmaitabut i can't remember for sure which one was implemented, i think *not* the search20:40
imacdonnif it uses the default, that could be a problem20:41
rosmaitayou mean if the operator changes which backend is the current default?20:41
imacdonnthe operator is going to be forced to enable multi in stein, right ?20:42
rosmaitai believe so20:42
imacdonnso say my configuration has always had swift as the default store, and http enabled20:43
imacdonnwith multi, I'm forced to specify a "default_backend"20:43
imacdonnnow all of the http images will default to using the swift backend ?!?20:44
imacdonnor vice-versa20:44
rosmaitayeah, that doesn't make sense.  i'm pretty sure i'm wrong.  glance currently uses the scheme of the location to determine wihch backend20:45
rosmaitathat's why you couldn't have >1 of the same kind of backend before multistore in rocky20:45
imacdonnbut isn't that "current" logic going away ?20:46
rosmaitai don't think so, because i don't think there's a migration for image locations20:47
rosmaitai need to go back and read the multistore spec, all this stuff was discussed in there20:47
imacdonnI guess I should do that too20:48
rosmaitahttps://specs.openstack.org/openstack/glance-specs/specs/rocky/implemented/glance/multi-store.html20:48
imacdonn"A very little hit on the performance of downloading the image from the old stores. For example, if existing user is using single rbd (say ceph) backend and now he has upgraded the environment and introduced two additional rbd stores as ceph1 and ceph2 with default store as ‘ceph1’ then if image which needs to be download from old store (ceph) will take some time as it needs to be looked in all the enabled backends."20:54
rosmaitaok, that makes sense20:55
imacdonnI wonder how it searches? like ... how would it determine if a given image "exists" in the http store ?21:04
rosmaitanot sure.  you may want to look at the tests21:07
rosmaitathey probably don't test http store, but should give you an idea of whether there's a potential problem or not21:08
rosmaitabut you know, since you are the biggest known http store user, you might want to add some tests just to protect yourself from regressions21:09
imacdonnthat probably implies figuring out more about how the rest of glance works than I'd planned on21:18
imacdonnhttps://github.com/openstack/glance_store/blob/master/glance_store/multi_backend.py#L473-L48921:28
_alastor_rosmaita: Is there a way to either restrict the type of images that can be store on a backend or auto-convert them to the correct type on upload?21:39
_alastor_For example, our backend can only quick-clone images into bootable volumes if they're stored in RAW format21:39
_alastor_Currently I'm having users perform the conversions themselves, but ideally I'd like to have either Glance or my plugin do that conversion automagically21:40
rosmaita_alastor_: well, there is an image conversion plugin for the new image import process; or you can use the old glance tasks, which have a conversion task22:01
_alastor_rosmaita: Are glance tasks due to be deprecated?22:21
rosmaitanot sure what the plan is22:22
rosmaitaif you think you might be interested, would be good to ask at the weekly glance meeting22:22
_alastor_rosmaita: Ah, sorry.  I still thought you were PTL22:23
rosmaitanp, it's erno (jokke_) for rocky & stein22:24
*** jmlowe has joined #openstack-glance23:46

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