Thursday, 2018-10-18

*** markvoelker has joined #openstack-meeting-400:05
*** mjturek has quit IRC00:05
*** markvoelker has quit IRC00:10
*** diablo_rojo has quit IRC00:39
*** njohnston has quit IRC00:48
*** bobh has quit IRC01:00
*** markvoelker has joined #openstack-meeting-401:05
*** markvoelker has quit IRC01:09
*** yamahata has quit IRC01:14
*** lei-zh has joined #openstack-meeting-401:48
*** hongbin has joined #openstack-meeting-402:29
*** psachin has joined #openstack-meeting-402:53
*** lei-zh has quit IRC02:57
*** lei-zh has joined #openstack-meeting-402:58
*** bnemec has joined #openstack-meeting-403:05
*** bnemec has quit IRC03:10
*** isq_ has joined #openstack-meeting-403:37
*** yamahata__ has quit IRC03:39
*** hongbin has quit IRC03:57
*** yamamoto has quit IRC04:34
*** yamamoto has joined #openstack-meeting-404:34
*** yboaron_ has quit IRC04:42
*** lei-zh has quit IRC05:15
*** liuyulong has quit IRC05:24
*** lei-zh has joined #openstack-meeting-405:38
*** Luzi has joined #openstack-meeting-406:15
*** itzikb has joined #openstack-meeting-406:23
*** e0ne has joined #openstack-meeting-406:38
*** yboaron_ has joined #openstack-meeting-406:39
*** janki has joined #openstack-meeting-406:51
*** celebdor has joined #openstack-meeting-407:14
*** janki has quit IRC07:19
*** persia has quit IRC07:19
*** persia has joined #openstack-meeting-407:21
*** e0ne has quit IRC08:02
*** slaweq has joined #openstack-meeting-408:02
*** dougsz has joined #openstack-meeting-408:08
*** e0ne has joined #openstack-meeting-408:13
*** salmankhan has joined #openstack-meeting-408:54
*** salmankhan has quit IRC08:56
*** salmankhan has joined #openstack-meeting-408:56
*** gkadam has joined #openstack-meeting-409:21
*** gkadam has quit IRC09:21
*** ktibi has joined #openstack-meeting-409:23
*** itzikb has quit IRC09:40
*** yamamoto has quit IRC10:11
*** yamamoto has joined #openstack-meeting-410:12
*** yamamoto has quit IRC10:16
*** yamamoto has joined #openstack-meeting-410:16
*** dave-mccowan has joined #openstack-meeting-410:19
*** ktibi_ has joined #openstack-meeting-410:55
*** ktibi__ has joined #openstack-meeting-410:57
*** ktibi has quit IRC10:58
*** ktibi_ has quit IRC11:00
*** lei-zh has quit IRC11:05
*** yamamoto has quit IRC11:20
*** yamamoto has joined #openstack-meeting-411:21
*** yamamoto has quit IRC11:25
*** icey has quit IRC11:30
*** icey has joined #openstack-meeting-411:34
*** ktibi__ has quit IRC11:38
*** e0ne has quit IRC11:50
*** yamamoto has joined #openstack-meeting-412:03
*** ktibi has joined #openstack-meeting-412:03
*** salmankhan has quit IRC12:11
*** ktibi has quit IRC12:16
*** yamamoto has quit IRC12:20
*** yamamoto has joined #openstack-meeting-412:20
*** seajay has joined #openstack-meeting-412:27
*** liuyulong has joined #openstack-meeting-412:27
*** yboaron_ has quit IRC12:29
*** yboaron_ has joined #openstack-meeting-412:29
*** dims has quit IRC12:30
*** dims has joined #openstack-meeting-412:33
*** gkadam has joined #openstack-meeting-412:34
*** dougsz has left #openstack-meeting-412:42
*** salmankhan has joined #openstack-meeting-412:49
*** psachin has quit IRC12:50
*** bobh has joined #openstack-meeting-413:01
*** e0ne has joined #openstack-meeting-413:07
*** mjturek has joined #openstack-meeting-413:22
*** LiangFang has joined #openstack-meeting-413:42
*** mjturek has quit IRC13:43
*** bnemec has joined #openstack-meeting-413:43
LiangFangthanks erno13:44
*** yboaron_ has quit IRC13:47
*** rosmaita has joined #openstack-meeting-413:52
*** gkadam has quit IRC13:59
*** gkadam has joined #openstack-meeting-413:59
jokke_#startmeeting glance14:00
openstackMeeting started Thu Oct 18 14:00:23 2018 UTC and is due to finish in 60 minutes.  The chair is jokke_. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
jokke_#topic roll-call14:00
*** openstack changes topic to "roll-call (Meeting topic: glance)"14:00
jokke_#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:00
jokke_o/14:00
LiangFanghi14:00
rosmaitao/14:00
Luzio/14:00
rosmaitaabhishek is on holiday today14:01
jokke_yeah14:01
jokke_I guess we're all here then14:02
jokke_#topic updates14:02
*** openstack changes topic to "updates (Meeting topic: glance)"14:02
*** lixiaoy1 has joined #openstack-meeting-414:03
jokke_more of a quick clarification before I merge this https://review.openstack.org/#/c/597648/14:03
jokke_As it's not obvious from the spec, is the validation_data going to be part of the location patch call?14:04
*** hongbin has joined #openstack-meeting-414:05
rosmaitaYes, it's a new write-only element of the image schema14:05
rosmaitabut it's an optional element14:05
jokke_like we discussed, or is it going to be it's own endpoint and how does the final version affect our mime?14:05
jokke_ok14:05
rosmaitano change to mime type for patch14:05
jokke_ok, so touching the parent object is ok with the json-patch?14:06
rosmaitait's an optional element, but all 3 of checksum, os_hash_algo, os_hash_value are required14:06
rosmaitayeah, as far as i can tell, it's OK14:06
*** slaweq has quit IRC14:06
jokke_and how is this gonna affect if there is no supported hash-algo configured in glance?14:07
rosmaitaummm ... i forget14:07
rosmaitai think you get a 4xx of some type14:08
*** slaweq has joined #openstack-meeting-414:08
rosmaitamay be worth asking that on the spec, tough14:08
rosmaita*though14:08
rosmaitato be clear, though ...14:08
jokke_so if the hash-algo is not configured this is just gonna fail, you're not going to be able to set just checksum14:08
rosmaitathe user making the call can specify a different hash_algo than is configured in glance14:08
rosmaitajust has to be a recognized hash_algo14:09
rosmaitaiain somehow convinced me that was a good idea14:09
*** yboaron_ has joined #openstack-meeting-414:09
rosmaitai was thinking we should only allow configured algo, but then we'd need a way to tell the user what that was, maybe a new /v2/info/hash_algo call14:09
jokke_ok, I won't be merging it yet today then and will put my questions in there14:09
*** imacdonn has joined #openstack-meeting-414:10
jokke_lets move on, we have a lot in agenda14:10
jokke_#topic periodic test patches14:10
*** openstack changes topic to "periodic test patches (Meeting topic: glance)"14:10
jokke_so I ninja approved the comment on the store (I think it was store)14:11
rosmaitaty14:11
jokke_You had anything else on this?14:13
rosmaitanope14:13
jokke_#link  https://review.openstack.org/#/c/599837/14:14
jokke_#link  https://review.openstack.org/#/c/59984414:14
jokke_#topic specify image size to avoid resize on backend14:14
*** openstack changes topic to "specify image size to avoid resize on backend (Meeting topic: glance)"14:14
LiangFanghi14:15
LiangFangabout this BP, I created the patch for solution214:15
*** hamzy has quit IRC14:15
LiangFangdo you have a chance to try this?:)14:15
LiangFang Implementation(glance part) https://review.openstack.org/#/c/609997/14:16
LiangFangImplementation(cinder part) https://review.openstack.org/#/c/609994/14:16
LiangFangspec: https://review.openstack.org/#/c/608400/14:16
LiangFangIf you guys accept solution 2, then I will begin to update the spec14:17
jokke_No i have not tried it yet14:17
LiangFangOK14:17
lixiaoy1do we need a spec for solution 2?14:17
LiangFangHow do you think? erno and rosmaita14:18
LiangFangdo we need a spec for solution 2?14:18
lixiaoy1as it is to update glance logic about updating the field size.14:19
jokke_so if we're going to chenge the behavior we will need at least spec lite for it. We will also need python-glanceclient change I think14:19
rosmaitaLiangFang: sorry, i was distracted14:20
LiangFangsolution 2 don't need glanceclient to change14:20
jokke_I recall us having a lot of logic in the client around this but it likely was for the v1 api as I don't think V2 has ever supported setting the size14:20
imacdonnthis is actually rather similar to the validation_data thing14:20
LiangFangthis is the solution 114:20
rosmaitasolution 2 is to update via json?14:21
*** mjturek has joined #openstack-meeting-414:21
LiangFangsolution 2 is:14:21
LiangFangcinder try to update the image size after created the image but before uploading the image data14:21
*** JamesBenson has joined #openstack-meeting-414:22
LiangFangsolution 1 is convey the image size in the http header with the image data in one http request14:22
jokke_LiangFang: so we will need this into the client as the user will face the very same issue doing for example image-upload14:23
jokke_with image-import we stage the data always in the API node first so we know the size, with image-upload we might know the size at the time of making the call14:24
LiangFangyes14:24
LiangFangwhen cinder trying to upload image, it also know the size14:25
jokke_yes, what I'm saying is that this is by no means cinder specific problem and we should not make just cinder specific solution for it14:25
LiangFangas you said, glance client may need do the similar thing14:25
LiangFangOK14:26
LiangFangglance client may also need to call "update" to set the image size14:26
jokke_but I'll try to dig into it today and give some detailed feedback on the review14:27
LiangFangbefore uploading14:27
LiangFangthank you very much14:27
jokke_and we need to figure out also if we should fail the upload/import in the case size has been set and it does not match with the payload delivered14:27
LiangFangI also will take a look at glance client about this14:27
jokke_thanks14:28
jokke_ok, the next one is yours as well I think14:28
LiangFangyes14:28
jokke_#topic save and show store info14:28
*** openstack changes topic to "save and show store info (Meeting topic: glance)"14:28
LiangFangthis is about the store info save and show14:28
LiangFangthis is just a small enhancement from our partner14:28
LiangFangthings is that: when have multiple backend, we may want to know the backend type, rbd or file14:29
jokke_#link  https://review.openstack.org/#/c/605006/14:29
jokke_#link  https://review.openstack.org/#/c/60501414:29
LiangFangglance -v image-list14:30
rosmaitathere is a stores info call in rocky14:30
LiangFangthis patch want to show the store infor in this cmd14:30
*** mjturek has quit IRC14:31
rosmaitahttps://developer.openstack.org/api-ref/image/v2/index.html#list-stores14:31
LiangFangyes, but store info call only show how many stores in glance14:31
*** sambetts|afk is now known as sambetts14:31
LiangFangIf the store info displayed in glance -v image-list, then it will be easier for user to know the backend type of the image reside14:32
imacdonnis this something that there should be policy control over? maybe a cloud provider doesn't want their users knowing backend details14:32
rosmaitayes, the deployer can explain that as part of the store description14:33
rosmaitait will show up in the info call14:33
*** gkadam_ has joined #openstack-meeting-414:33
jokke_So the store ID is specifically not linked with the driver to avoid leaking backend information14:33
rosmaitaexactly14:33
LiangFangOK14:33
LiangFanghow do you think lisa14:34
jokke_it should be safe to show that, but nothing else14:34
jokke_the details exposed are visible from the info call14:34
lixiaoy1reasonable to not lead backend info14:34
lixiaoy1so can we just allow admin to see the info?14:34
jokke_sec14:35
LiangFangglance image-show can also see the backend info, but it is for one image14:35
*** gkadam has quit IRC14:35
rosmaitai think we need a spec for this to explain the use case and why the current features aren't sufficient14:36
jokke_#link https://specs.openstack.org/openstack/glance-specs/specs/rocky/implemented/glance/multi-store.html14:36
LiangFangOK14:36
jokke_if we do not show the '"store": ["reliable"]' which is returned from the creation response, that is the extent we should go with show as well14:37
jokke_user has then the info call to see the details of that store exposed by the deployment if they don't remember it out of their head14:38
*** mjturek_ has joined #openstack-meeting-414:38
lixiaoy1jokke_: does glance already have the interface to show store info?14:40
rosmaita#link https://developer.openstack.org/api-ref/image/v2/index.html#list-stores14:40
jokke_I thought it was there, but based on your proposal I think it might be missing?14:41
jokke_I thought we returned the store ids14:41
lixiaoy1from the link list-stores, the response includes store lists which has id, description, and default14:41
*** hamzy has joined #openstack-meeting-414:42
jokke_yes, that does exist for sure14:43
jokke_so if the detailed listing and show does not provide the list of store ids, that's something we indeed should add14:43
jokke_but not the full store details14:43
LiangFangis list store the same as "glance stores-info"14:44
LiangFang?14:44
jokke_sorry, yes stores-info not list-stores14:44
rosmaitawell, one is the API call and the other is handled by the CLI14:44
jokke_in client14:45
LiangFangOK, glance stores-info show something like:14:45
LiangFang| stores   | [{"default": "true", "id": "ceph"}, {"id": "locallvm"}] |14:45
LiangFangthis is my environment14:45
jokke_rosmaita: I thought we returned the store id's image is in14:45
rosmaitajokke_: i believe it does appear on the image response14:46
rosmaitaLiangFang: could be that the description is not configured in your environment14:46
rosmaitaor could be that the client does not display it14:46
jokke_LiangFang: yes, and the image-show should give you "stores": ["ceph"] if the store was not specified14:46
LiangFangglance -v image-show 0de67910-661e-4a2c-b5de-bcdc4d4a62db14:47
LiangFangand it seems no store id14:47
jokke_ok, yes we should fix that14:48
jokke_that is bug I believe14:48
jokke_we're running out of time, lets move forward and continue this investigation offline14:49
LiangFangI will update more info in the review14:49
LiangFangOK14:49
LiangFangthanks14:49
jokke_#topic image encryption spec14:49
*** openstack changes topic to "image encryption spec (Meeting topic: glance)"14:49
Luziwe still would appreciate some feedback on our spec and answering any questions there.14:49
jokke_#link https://review.openstack.org/#/c/609667/14:49
Luziand as already mentioned in the ML, we created an etherpad to discuss the location for the proposed image encryption code:14:50
Luzi#link library discussion https://etherpad.openstack.org/p/library-for-image-encryption-and-decryption14:50
Luziwe would like to recieve input and comments from all involved projects, so please participate if possible :)14:50
Luzito make this short: that's all i think14:51
jokke_ok, thanks. Looking the spec discussion it seems that there has been some question about scenarios thrown around already. Lets just make sure that the spec is very clear about the scope14:53
jokke_I'd hate to see bunch of security bugs appearing just because we provided new security feature that doesn't fill it's expectations14:53
Luzijokke_, we will keep this in mind :)14:54
jokke_so everyone interested, please review and participate14:54
rosmaitai still think having glance/cinder/etc have a dependency on openstackSDK seems crazy, but i am having trouble articulating what is so wrong14:54
jokke_moving on to last topic of the day14:54
jokke_#topic upgrade check14:55
*** openstack changes topic to "upgrade check (Meeting topic: glance)"14:55
jokke_#link https://review.openstack.org/#/c/610661/14:55
*** egonzalez has quit IRC14:55
*** egonzalez has joined #openstack-meeting-414:56
rosmaitai put this topic on as a point of information14:56
jokke_So yes, I have eyeballed the discussion and I kind of fail to see the importance of this so it has not been at the top of my priority list14:57
rosmaitado we have anyone on the glance side particularly interested in this stein comunity goal?14:57
jokke_If we have time to dig into it or someone stepping up who is heavily invested into the topic, great14:57
jokke_if both of the above fail, we likely will fail the community goal as well14:58
jokke_time check, last minute14:58
rosmaitai got the impression from mriedem's email that he's willing to work on it with a bit of guidance from someone on the glance side14:58
jokke_rosmaita: yeah, that was the discussion we had in PTG14:59
rosmaitai think lbragstad is interested in just getting the scaffolding in place14:59
lixiaoy1jokke_: this feature, do you mean upgrade check?14:59
jokke_so if Matt finds lbragstad's base work useful to continue on, great15:00
jokke_lixiaoy1: yes15:00
jokke_we're out of the time. We can continue on #openstack-glance15:00
jokke_thanks all!15:00
jokke_#endmeeting15:00
*** openstack changes topic to " (Meeting topic: vitrage)"15:00
openstackMeeting ended Thu Oct 18 15:00:48 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2018/glance.2018-10-18-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2018/glance.2018-10-18-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2018/glance.2018-10-18-14.00.log.html15:00
*** rosmaita has left #openstack-meeting-415:01
*** Luzi has quit IRC15:01
*** admcleod is now known as admcleod_away15:02
*** dklyle has joined #openstack-meeting-415:06
*** lixiaoy1 has left #openstack-meeting-415:06
*** e0ne has quit IRC15:12
*** e0ne has joined #openstack-meeting-415:18
*** yamamoto has quit IRC15:21
*** yamamoto has joined #openstack-meeting-415:22
*** yamamoto has quit IRC15:26
*** gkadam_ has quit IRC15:38
*** yboaron_ has quit IRC15:39
*** hamzy has quit IRC15:42
*** hamzy has joined #openstack-meeting-415:43
*** liuyulong has quit IRC15:46
*** liuyulong has joined #openstack-meeting-415:46
*** LiangFang has quit IRC15:47
*** mjturek_ has quit IRC15:49
*** macza has joined #openstack-meeting-415:56
*** e0ne has quit IRC16:00
*** yamamoto has joined #openstack-meeting-416:11
*** liuyulong is now known as liuyulong_zzz16:13
*** dklyle has quit IRC16:16
*** dklyle has joined #openstack-meeting-416:16
*** macza has quit IRC16:33
*** dklyle has quit IRC16:37
*** yamamoto has quit IRC16:56
*** yamamoto has joined #openstack-meeting-416:56
*** yamahata has joined #openstack-meeting-417:04
*** sambetts is now known as sambetts|afk17:07
*** celebdor has quit IRC17:09
*** mjturek has joined #openstack-meeting-417:16
*** dklyle has joined #openstack-meeting-417:30
*** yamamoto has quit IRC17:33
*** njohnston has joined #openstack-meeting-417:40
*** dklyle has quit IRC17:42
*** diablo_rojo has joined #openstack-meeting-417:44
*** hamzy has quit IRC17:44
*** hamzy has joined #openstack-meeting-417:45
*** salmankhan has quit IRC17:47
*** dklyle has joined #openstack-meeting-417:50
*** dklyle has quit IRC18:02
*** diablo_rojo has quit IRC18:12
*** diablo_rojo has joined #openstack-meeting-418:13
*** yamamoto has joined #openstack-meeting-418:14
*** salmankhan has joined #openstack-meeting-418:17
*** dklyle has joined #openstack-meeting-418:20
*** salmankhan has quit IRC18:23
*** seajay has quit IRC18:24
*** seajay has joined #openstack-meeting-418:26
*** diablo_rojo has quit IRC18:26
*** dklyle has quit IRC18:29
*** salmankhan has joined #openstack-meeting-418:31
*** itzikb has joined #openstack-meeting-418:33
*** mjturek has quit IRC18:35
*** salmankhan has quit IRC18:40
*** caboucha has joined #openstack-meeting-418:43
*** diablo_rojo has joined #openstack-meeting-418:44
*** mjturek has joined #openstack-meeting-418:53
*** hamzy has quit IRC19:07
*** dklyle has joined #openstack-meeting-419:07
*** hamzy has joined #openstack-meeting-419:08
*** dklyle has quit IRC19:14
*** bobh has quit IRC19:17
*** diablo_rojo has quit IRC19:35
*** hamzy has quit IRC19:41
*** e0ne has joined #openstack-meeting-419:52
*** itzikb has quit IRC19:58
*** e0ne has quit IRC20:05
*** hamzy has joined #openstack-meeting-420:10
*** salmankhan has joined #openstack-meeting-420:35
*** salmankhan has quit IRC20:35
*** salmankhan has joined #openstack-meeting-420:36
*** mjturek has quit IRC20:38
*** pcaruana has quit IRC20:44
*** diablo_rojo has joined #openstack-meeting-421:12
*** bnemec is now known as bnemec-bbl21:20
*** dklyle has joined #openstack-meeting-421:36
*** diablo_rojo has quit IRC21:42
*** diablo_rojo has joined #openstack-meeting-421:44
*** dklyle has quit IRC21:45
*** JamesBenson has quit IRC22:01
*** JamesBenson has joined #openstack-meeting-422:02
*** JamesBenson has quit IRC22:07
*** JamesBenson has joined #openstack-meeting-422:10
*** JamesBenson has quit IRC22:14
*** pbourke has quit IRC22:35
*** pbourke has joined #openstack-meeting-422:36
*** bobh has joined #openstack-meeting-422:37
*** bobh has quit IRC22:41
*** diablo_rojo has quit IRC22:52
*** diablo_rojo has joined #openstack-meeting-423:03
*** seajay has quit IRC23:04
*** hongbin has quit IRC23:08
*** mjturek has joined #openstack-meeting-423:17
*** salmankhan has quit IRC23:22
*** diablo_rojo has quit IRC23:37
*** mjturek has quit IRC23:42
*** bnemec has joined #openstack-meeting-423:50
*** bnemec-bbl has quit IRC23:52
*** markvoelker has joined #openstack-meeting-423:57

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